Identifying issues between TrueSight Orchestration and TrueSight Server Automation

When you receive an error message from the BMC Server Automation adapter, is it not always clear whether the error is from TrueSight Server Automation or TrueSight Orchestration, but the error message itself gives a few indicators:

• If the error is in the grid.log and not the processes.log, the error is from TrueSight Orchestration. This is because the processes.log contains the adapter request and response, so any messages sent by TrueSight Server Automation will be included there.
• If the error in the processes.log is "An internal error occurred", the error is from TrueSight Orchestration. The grid.log will have more information.
• If the error in the processes.log contains an error number, the error is from TrueSight Server Automation. TrueSight Orchestration does not have error numbers. For more information about logging in TrueSight Orchestration, see Troubleshooting in the TrueSight Orchestration online documentation.
• If the adapter response indicates that the command was run as a "success" but still contains an error, the issue is with the command or with TrueSight Server Automation. This means that the adapter ran the command as expected, and TrueSight Server Automation returned an error message because the command caused an error.

After you have determined the source of the error, there are a few steps you can take to get more information:

• Test your command using BLCLI without using the adapter. If the same command completes successfully, then the adapter is not running the command properly. If the command fails with the same error message, there is an issue with the command or with TrueSight Server Automation. See the 

  TrueSight Server Automation

   BLCLI Help for specific information about commands.

• Verify that 

  TrueSight Server Automation

   is running properly.

  • Log on to the 

    TrueSight Server Automation

     Console to view the status of each application server instance, using the Infrastructure Management view (Configuration > Infrastructure Management).

  • If you cannot log on to the console, you can verify the status of the Application Server Launcher using the following steps:

    • (Windows) Confirm the status of the 

      TrueSight Server Automation

       Application Server service.

    • (UNIX) Confirm the presence of the Application Server Launcher process by executing ps -ef | grep blapp.

• Enable additional logging in 

  TrueSight Server Automation

  . For information, see Working with logs in the 

  TrueSight Server Automation

   online documentation.

• Enable additional logging on the 

  TrueSight Server Automation

   adapter in 

  TrueSight Orchestration

  . For information about how to do this see the Debug level adapter logging steps in topic in the 

  TrueSight Orchestration

   online documentation.