Adapter troubleshooting steps

The general troubleshooting steps for an adapter are:

1. Check the processes.log files for messages returned by the adapter. BMC Atrium Orchestrator uses two processes.log files, one processes.log file for the grid and the other processes.log file for the BMC Atrium Orchestrator Development Studio.
2. If a workflow is executed on the grid, the adapter requests and responses are logged in the processes.log file and the grid.log file for the grid. If a workflow is executed on the grid using a rule or a schedule, the entire wrapper-related information is logged in the processes.log file and the grid.log file for the grid. The processes.log file also contains any debug messages associated with the workflow.

3. If a workflow is executed from the BMC Atrium Orchestrator Development Studio, the adapter requests and responses are logged in the processes.log file for the BMC Atrium Orchestrator Development Studio. 

   Warning

   Note

   The processes.log file for the grid is located in the AO_HOME\tomcat\logs directory and the processes.log file for the BMC Atrium Orchestrator Development Studio is located in the AO_HOME\Studio\logs directory.
   AO_HOME refers to the directory in which BMC Atrium Orchestrator is installed.
   

4. Check the grid.log file on the peer for java exceptions. Verify whether the java exception is known and if a resolution exists. 

   Warning

   Note

   The grid.log file is located in the AO_HOME\tomcat\logs directory.

5. Verify that the adapter configuration in Grid Manager is correct.
6. If none of the above steps help in identifying or resolving the issue, verify that the adapter can connect to the ports used by the target application.
   For verifying connectivity, you can execute telnet, ping, or traceroute commands. If the connectivity does not exist, check whether the ports of the target application are blocked.