How to verify, upgrade or change the Java JDK being used by Process Automation.


Article ID: 39011


Updated On:


CA Process Automation Base Process Automation Manager


Need to verify the release of JDK that is being used in PAM, and potentially update the Java JDK that Process Automation is using.


The PAM functionality retains its JDK configuration in file c2osvcw.conf, on *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 ( on *unix systems) show entries that indicate that the Orchestrator is starting using the 1.8.0 81 Java JDK version. files/java/jdk1.8.0_81/bin/java files/java/jdk1.8.0_81/lib/tools.jar


Release: 4.3-Process Automation


To change the Java version being used by the Orchestartor:

1.  Stop CA Process Automation Orchestrator

2.  Install JDK acquired from

3.  Update the CA\PAM\server\c2o\bin\c2osvcw.conf ( on *unix systems) file to point at the newly installed JDK, commenting out the existing lines to use as a reference: files/java/jdk1.8.0_81/bin/java files/java/jdk1.8.0_192/bin/java files/java/jdk1.8.0_81/lib/tools.jar files/java/jdk1.8.0_192/lib/tools.jar

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: files/adoptopenjdk/jdk- files/adoptopenjdk/jdk-

Please note, there are different versions of the AdoptOpenJDK so your AdoptOpenJDK jdbc lines may vary slightly.

Additional Information

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.