Need to verify the release of JDK or JRE that is being used in PAM, and potentially update the Java JDK or JRE that Process Automation is using.
Process Automation 4.3.x
The PAM functionality retains its JDK/JRE configuration in file c2osvcw.conf in Windows and c2osvrd.sh in *unix systems. A default PAM install will have this config file located under C:\Program Files\CA\PAM\server\c2o\bin\
The following two lines from c2osvcw.conf (c2osvrd.sh on *unix systems) show entries that indicate that the Orchestrator is starting using the 1.8.0 81 Java JDK/JRE version.
To change the Java version being used by the Orchestrator:
1. Stop CA Process Automation Orchestrator
2. Install JDK acquired from Java.com
3. Update the CA\PAM\server\c2o\bin\c2osvcw.conf (c2osvrd.sh on *unix systems) file to point at the newly installed JDK, commenting out the existing lines to use as a reference:
4. Start CA Process Automation Orchestrator.
Once Process Automation is verified as working using the new Java the commented lines can be removed without the need to restart the Orchestrator.
Alternatively, the latest release of Process Automation, 4.3 sp5, supports AdoptOpenJDK an open source Java release:
The JDK lines in the c2osvc would look similar to:
Additionally, update the PasswordEncryption.bat and SignC2OJars.bat to reflect the change in JDK. These files are located in the PAM install, under server\c2o directory.
These two batch files have a line that reads:
set JAVA_HOME="C:\Program Files\Java\jdk1.8.0_201"
The above line should be updated to reflect the updated JDK.
- Please be aware that all versions of Process Automation exhibit issues using any Oracle Java newer than 1.8.0_192 due to changes Oracle has made.
See KB 139723 Java Compatibility with IT Process Automation for details.
ORACLE 8 JDK:
Due to changes Oracle made to the security within the Java starting with JDK 1.8.0_202 IT Process Automation has issues when attempting to run using any JDK newer than the 1.8.0_192 JDK. Issues include installation failures, multiple startup issues, agent connectivity problems, and other issues of varying levels of severity.
For 4.3 sp1 through 4.3 sp5 the most current ORACLE JDK that has not shown issues is1.8.0_192.
Starting with 4.3 Sp5 we have introduced support for AdoptOpenJDK: JDK Prerequisites Documentation
For 4.3 Sp5 we have confirmed up to AdoptOpenJDK version 1.8.0_265 allows the software to function without issue.
Uninstalling the original Java is recommended best practice, but if the Java major version number is changing - for instance from 1.7 to 1.8 - you must uninstall the older version.
Note: Be sure the contents of your JAVA_HOME and PATH environment variables are correct.