Verifying the connection to BMC Remedy ITSM


The Remedy Monitor Adapter has successfully connected to BMC Remedy if the adapter displays as running in the TrueSight Orchestration Grid Manager application. To verify that the adapter is successfully reading alerts, create an alert in BMC Remedy that would be read by the adapter.

If the connection is working, the adapter will see the alert and run any processes associated with the alert. On the BMC Remedy AR System, the alert in the Alert Events form will be marked as Read or Deleted.

If the Remedy Actor Adapter has successfully connected, your first command will run successfully. For your first command, it is best to send a simple request to the adapter, just to verify that the connection is valid. An example is a schema-retrieve command (using a schema that is present in your system):


<remedy-action> 
<schema>Alert Events</schema>
</remedy-action>

 
 If the command completes successfully, the adapter configuration is valid.

If a simple command fails, there is an issue with the adapter configuration or the request that is preventing the adapter from running the command properly. The adapter response will list an error message, and further information might be available in the $PEER_HOME/tomcat/logs/grid.log file. For more information about logging in TrueSight Orchestration, see the Troubleshooting topic in the TrueSight Orchestration online documentation.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*