ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
AWA v11.2 v12 Troubleshooting Service Manager
Article ID: 105918
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
The Service Manager is a very useful tool for the automation engine, it gives a view of all the worker and communication processes as well as agents. For many businesses, agents are installed on multiple servers. For the agents to be started remotely, a service manager needs to be installed there. Once this is done, access all agents listed in the service manager dialog or any preferred interface (Java or Web-based).
Environment
Automic Workload Automation version 11.2 -> 12.1
Resolution
When troubleshooting the service manager, it is best to use a service manager dialog as an interface. It gives a very basic overview of the system. If the service manager is remote, enter the <computer name or ip address>:<port> then press tab.
If it displays the agents or cps and wps, there is no need to troubleshoot. If it freezes, there are some guidelines that needs to be covered to make sure that the proper information has been provided to the service manager and the service manager dialogue to communicate with each other.
1. Make sure that the service manager is running. In Linux, use the ps -ef | grep uc and see if the service manager is currently running. The output lists the service manager and the phase name. In Windows, it is listed in Services.msc
2. Once it has been confirmed that the service manager is running, the port number it's running under needs to be verified. It can be found in the UCYBSMgr.ini file located in the bin folder of the Service Manager folder. Confirm if the correct port number has been used for the service manager dialog. If any changes needs to be made, the Service Manager service needs to be restarted.
3. Last step is running a low level communication to make sure that the ports are able to communicate. Using telnet, attempt to communicate with the service manager from your remote computer. If it fails contact the system administrator.
If it displays the agents or cps and wps, there is no need to troubleshoot. If it freezes, there are some guidelines that needs to be covered to make sure that the proper information has been provided to the service manager and the service manager dialogue to communicate with each other.
1. Make sure that the service manager is running. In Linux, use the ps -ef | grep uc and see if the service manager is currently running. The output lists the service manager and the phase name. In Windows, it is listed in Services.msc
2. Once it has been confirmed that the service manager is running, the port number it's running under needs to be verified. It can be found in the UCYBSMgr.ini file located in the bin folder of the Service Manager folder. Confirm if the correct port number has been used for the service manager dialog. If any changes needs to be made, the Service Manager service needs to be restarted.
3. Last step is running a low level communication to make sure that the ports are able to communicate. Using telnet, attempt to communicate with the service manager from your remote computer. If it fails contact the system administrator.
Feedback
Yes
No
Powered by
