Troubleshooting › Connectors Troubleshooting › How to Troubleshoot Connector Shutdown Behavior › Review the Heartbeat History for the Connector

Review the Heartbeat History for the Connector

CA SOI includes the shutdown message in the connector status notification as part of the heartbeat message that is periodically sent to the SA Manager. By reviewing the heartbeat history for the connector, you can determine the trend in the connector behavior.

The statusDesc property value in the connector debugData logs describes the status of the connector for which the heartbeat is sent. Enable the debugData logging for the connector (enabled in the log4j.xml file). After you enable the debug logging, a file <ConnectorName>_HEARTBEAT_PUB.txt is created and displays the heartbeat history for the connector. The connector writes any published heartbeat messages into this text file.

Follow these steps:

1. Navigate to the SOI_HOME\resources folder.
2. Locate and open the log4j.xml file in a text editor.

   The file opens in a text editor.

3. Modify the com.ca.sam.ifw level to DEBUG.

   The debugData logging is enabled for the connector.

4. Verify that the <ConnectorName>_HEARTBEAT_PUB.txt file is created under the SOI_HOME\log\debugData folder when the connector writes any published heartbeat message.
5. Open the file in a text editor and start reviewing the heartbeat messages in the file.

   An example of how the statusDesc property is displayed in the file is as follows:

statusDesc=Connector was stopped from Administration UI.