Description:
In Service Desk r12, CA Workflow tomcat fails to logon to SLUMP and pdm_status output shows the tomcat status as Connecting. The situation can be corrected by matching the values for certain CA Workflow options listed in Options Manager to the corresponding values in the nx.env file.
Solution:
In Service Desk r12, CA Workflow can be installed on the primary server or on a secondary server. Sometimes the CA Workflow tomcat fails to logon to the Service Desk slump process. The pdm_status output shows zero as the PID SLUMP for the CAWF daemon.
DAEMON STATUS HOST PID SLUMP CONNECT TIME --------------------------------------------------------------------------------------------------- Bpvirtdb_srvr (bpvirtdb_srvr) Running server_01 8048 Mon Mar 30 08:50:29 CAWF (pdm_tomcat_nxd) Connecting SERVER_01 0 Confirm Database(confirm_db) Completed server_01
In the above pdm_status output the HOST for the tomcat daemon is in uppercase but the name by which it is known in Service Desk is in lowercase. For this reason tomcat is not able to logon to SLUMP. The hostname case is important and must match the hostname case used by the rest of Service Desk. Tomcat interprets an uppercase hostname as a different machine than a lowercase hostname and attempts to connect to it as if it was a secondary.
The hostname displayed in the pdm_status output for CAWF is retrieved from the value of cawf_hostname in the Service Desk options manager.
A similar error is caused by using the Fully Qualified Domain name instead of just the hostname during the workflow install. The HOST in pdm_status:
CAWF (pdm_tomcat_nxd) Connecting server_01.ca.com 0
Check the Service Desk @NX_SERVER= value and the Workflow @NX_CAWF_HOSTNAME= hostname settings in the \$NX_ROOT\nx.env file and Options Manager. Modify them to match if they do not already.
To change the CAWF hostname in Options Manager: