Described below are the manual steps to switch Process Automation from a 32bit JDK to a 64bit JDK and information on modifying the memory allocated toProcess Automation.
For a 32 bit JDK the maximum Heap size is 1536 MB, for a 64bit the limit is imposed by the OS and the amount of physical memory installed and free. Therefore it is recommended to use 64-bit if possible. See below instructions for changing from 32-bit to 64-bit. If you are already on 64-bit, skip to the directions below for increasing the memory.
Directions to change PAM from using a 32bit JDK to a 64bit JDK.
These directions are only applicable under conditions where PAM was installed on a 64bit Server but during the installation a 32bit JDK was specified.
To determine what bitrate JDK PAM is utilizing check the /server/c2o/bin/c2osvcw.conf file for the setting:
Directions to change the amount of memory allowed to CA Process Automation.
The default of allocation of 1024 is enough to get PAM installed, running, and begin designing processes. For almost all production implementations this is insufficient and will need to be increased.
Caution should be exercised when modifying the memory allocation to assure that the OS has enough free memory to allocate during PAM startup. If Java cannot allocate the requested amount of memory it will fail to start. (Remember if you are not using a 64-bit JDK, the maximum setting here is 1536MB)
It is recommended that both init and max be set to the same value, though this is not required. Setting both to the same value will eliminate any negotiation between Java and the OS and provide additional stability and performance.
Both of the above changes need to be made to all CA Process Automation Orchestrators in a cluster individually.