When attempting to search for a job in QuickView, it hangs for a while and then returns a "Connection Failed" error. The WAAE server status also shows "Failed" in WCC.
WCC logs showed that the connection to the WAAE Application Server was timing out. When viewing the WAAE Application Server logs, it was showing that it was unable to reach the WCC server. However, a regular ping from the WAAE machine to the WCC server works fine. This typically indicates that the root cause is with the Csam component, which is the communication layer used by WCC's JDK connection back to WAAE.
Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option
This type of issue can sometimes be resolved by cycling the Csam service on the WCC server. In order to cycle the Csam service, you must first stop the WCC services that are using it. Here are the steps...
Go to Services and stop CA-wcc-services and CA-wcc
Stop and restart the CA Connection Broker service
Run 'unisrvcntr stop CA-wcc-services' and then run ustat to ensure both CA-wcc-services and CA-wcc are stopped.
Run '/opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux stop'
Run '/opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux start'
Run 'ps -ef|grep csam' and ensure there is a csampmuxf process running
Run 'unisrvcntr start CA-wcc' and then run ustat to ensure both CA-wcc and CA-wcc-services are running.