Verifying the adapter has started successfully

After you have enabled the adapter on a BMC Atrium Orchestrator peer, the adapter will be listed in BMC Atrium Orchestrator Grid Manager application on the Grid Status screen. In Grid Manager, click the Status tab, and then click the name of your grid. This will display a list of all of the adapters on the grid with the status for each.

• If you see a green circle for the Remedy adapter, the adapter is Running has successfully connected.
• If you see a red square, the Remedy adapter is in a Fault State and has not started successfully.
• If you see a gray circle, the adapter is either Stopped and was manually disabled by a user or is Not Enabled and was enabled on a different peer on the grid.
• If you do not see the Remedy adapter in the list, the adapter has not been enabled on a peer. You can enable adapters on a peer by editing that peer in the Manage > Peers screen in Grid Manager.

If the adapter is in a fault state, it should have an associated error message in the grid's error log. This file is normally located at $PEER_HOME/tomcat/logs/grid.log on the file system. Open the file and look for a recent message containing "ERROR" to see what message the grid has logged. If the adapter was enabled some time ago, you can cause the grid to list the error again by disabling and re-enabling the adapter. For more information about logging in BMC Atrium Orchestrator, see the Troubleshooting topic in the BMC Atrium Orchestrator online documentation.

The Remedy Monitor Adapter establishes a connection to the target BMC Remedy system when it is enabled on a peer, and it attempts to maintain that connection as long as it is active. It monitors for notifications in the Alert Event form, sent to the user configured in the adapter configuration.

For the Remedy Actor Adapter, communication with the target BMC Remedy system is on a case-by-case basis, and a persistent connection is not maintained. Because of this, it is unlikely that the adapter will fail to start; if there is an issue, it will occur the first time you attempt to use the adapter to run a command, in which case the grid.log will contain the error message at runtime.