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.
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.
Process Automation 4.3.x
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:
- 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.
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.