Automic Workload Automation

  • Private Community
 View Only

  • 1.  java 11 support on v24.4

    Posted 21 days ago
    Edited by Olgun Onur Ozmen 21 days ago
    Hi ,
    • While v24.3.0 (Agent RA Core, Agent SQL, Automation Engine, Automic Web Interface) components all have java 11 / java 17 support .
    • It seems that v24.4.0 (Agent RA Core, Agent SQL, Automation Engine, Automic Web Interface) has only java 17 in its components. 
     
    I was using java 11 in v21 and I was going to use the migration method in "v21 > v24 migration" and use agents and awi machines together (v21 / v24)  for a  certain period of time. Since this java 11 support does not appear in v24.4, I will have to install separate agent/awi servers, I do not want this.
    Is java 11 support really gone on v24.4?  or is it a documentation error?
    Thanks.
     



    ------------------------------
    Olgun Onur Ozmen
    https://www.linkedin.com/in/olgunonurozmen/
    ------------------------------



  • 2.  RE: java 11 support on v24.4

    Broadcom Employee
    Posted 21 days ago

    Hi @Olgun Onur Ozmen

    Be informed the components of Automic Automation v24.4 work only with Java 17 (or up). 

    see https://docs.automic.com/tools/compatibility_matrix?compatibility-mode=component&offering_version_id=components&lifecycle_entity_id=1409143059253

    Michael

    PS:

    e.g. Package Manager v21 runs on Windows with Adoptium JDK 17 (see https://adoptium.net/) when setting the environment variable upfront

    set JDK_JAVA_OPTIONS=--add-opens java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED



    ------------------------------
    Michael K. Dolinek

    Engineering Program Manager | Agile Operation Division
    Broadcom Software
    ------------------------------

    Original Message


  • 3.  RE: java 11 support on v24.4

    Posted 21 days ago
    Edited by Olgun Onur Ozmen 21 days ago

    Hi @Michael Dolinek , 

    Can you detail a bit more on the part you mentioned "Package Manager v21 runs on Windows"?  
    Would the following below assumptions be correct?
     
    If java 17 is installed on the agent machine :
    • we have a options for run v21 agent set the manual java 11 path to start command for example 
      • java11\bin\java -jar D:\Automicv21\Agents\ftp\bin\ucxjcitx.jar
    • OR will it work if we do the following below in the service manager dialog for v21 agents ? 
     
    java --add-opens java.base/java.util=ALL-UNNAMED \ --add-opens java.base/java.net=ALL-UNNAMED \ --add-opens java.base/java.lang=ALL-UNNAMED \ -jar D:\Automicv21\Agents\ftp\bin\ucxjcitx.jar
    If java 17 is installed on the tomcat machine :
     
    • for v21 AWI can I manually add "--add-opens"  parameters for tomcat into setenv.sh or catalina.sh ?

     
    If java 11 is installed on the agent machine :
    • we have a options for run v24.4 agent set the manual java 17 path to start command for example 
      • java17\bin\java -jar D:\Automicv24\Agents\ftp\bin\ucxjcitx.jar

    If java 11 is installed on the tomcat machine :

    • for v24.4 AWI can I manually add java path's parameters for different tomcat into setenv.sh or catalina.sh ?



    ------------------------------
    Olgun Onur Ozmen
    https://www.linkedin.com/in/olgunonurozmen/
    ------------------------------

    Original Message


  • 4.  RE: java 11 support on v24.4

    Broadcom Employee
    Posted 2 days ago
    Personally, I would not have installed several different Java versions on one environment but one Java installation that is configured for all OS-users in the same way.
    Therefore, I would do the following:
    1. save all additional certificates added to the various Java trust stores
    2. uninstall all different Java versions in the different folders 
    3. install only one Java for all users (e.g. Adoptium JDK v21 for Windows https://adoptium.net/temurin/releases/?os=windows  )
    4. set the environment variable (for all users) JDK_JAVA_OPTIONS=--add-opens java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED
    5. add all previously saved additional/custom certificates to the Java trust store
    6. restart the system
     
    Running a component of a previous version in parallel to a component of v24 might lead to a problem as Windows should be switch to "full UTF-8 mode" ( see https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/24.4.0/Automic%20Automation%20Guides/Content/Installation_Common/PreparationSteps/PrepareAEDB_MSSQL.htm) : Windows Settings > Time & language > Language & region > Administrative language settings > Change system locale, and check Beta: Use Unicode UTF-8 for worldwide language support
    I hope this makes my statement clearer!
    Michael


    ------------------------------
    Michael K. Dolinek

    Engineering Program Manager | Agile Operation Division
    Broadcom Software
    ------------------------------

    Original Message


  • 5.  RE: java 11 support on v24.4

    Posted 2 days ago
    Edited by Olgun Onur Ozmen 2 days ago

    Hi @Michael Dolinek ,

    Thanks for explanation .

    We have a this type of environment for v21 ; 

    • linux(engine hosts AE1,AE2) , for automic db exadata(oracle DBNAME1)
    • linux (agents hosts AGENTL1,AGENTL2,AGENTL3) , windows (agents hosts AGENTW1,AGENTW2,AGENTW3) and certificates stores external path for agents hosts : /opt/automic/certsv21/ ... all type of certs ..  (not in java cacerts)
    • linux (tomcat hosts TOM1,TOM2)

    For v24 we set up a structure like this ; (I will install engine, db and tomcat on separate machines but agent machines will be common with v21).

    • linux(engine hosts AE3,AE4) , for automic db exadata(oracle DBNAME2)
    • for agents hosts (same of v21 agent hosts) --> linux (agents hosts AGENTL1,AGENTL2,AGENTL3) , windows (agents hosts AGENTW1,AGENTW2,AGENTW3) and certificates stores external path for agents hosts : /opt/automic/certsv24/ ... all type of certs ..  (not in java cacerts)
    • linux (tomcat hosts TOM3,TOM4)

    So , only agent machines will be common for v21 and v24 , so I don't expect any problems. for these agent machines I will install bash_profile java 17. but for v21's agents I will add it directly in the smdialog with java 11 path . 

    How to run all v21 , v24 agents on same machines: linux (agents hosts AGENTL1,AGENTL2,AGENTL3) , windows (agents hosts AGENTW1,AGENTW2,AGENTW3)

    The “java -version” command will show java 17.

    • for v21 windows hosts agents: --> C:\java11\bin\java -jar D:\Automic\Agents\ftpv21\bin\ucxjcitx.jar
    • for v24 windows hosts agents: --> java -jar D:\Automic\Agents\ftpv24\bin\ucxjcitx.jar
    • for v21 linux hosts agents: --> /opt/automic/java11/bin/java -jar /opt/automic/Agents/ftpv21/bin/ucxjcitx.jar
    • for v24 linux hosts agents: --> java -jar /opt/automic/Agents/ftpv24/bin/ucxjcitx.jar

    Does this look okay to you?  :D

    Just little question. Isn't the "check beta: use unicode UTF-8" setting for windows only valid for the mssql database machine. right? I understood that there is no need for this type of setting for windows agent machines.

    Thanks.



    ------------------------------
    Olgun Onur Ozmen
    https://www.linkedin.com/in/olgunonurozmen/
    ------------------------------

    Original Message