

Troubleshooting › Connectors Troubleshooting › Alert Synchronization Not Working for a Connector
Alert Synchronization Not Working for a Connector
Symptom:
I am trying to implement alert synchronization (inbound to connector operation) for my connector, but it is not working. How do I troubleshoot this issue?
Solution:
For inbound to connector synchronization, the update() method of connectors is called with the alert details. If the update() method is not getting called, this problem usually means an issue in either the connector configuration or CA Catalyst synchronizer policy. To troubleshoot, perform the following steps:
- Verify that the connector is enabled for the inbound to connector operations. To do so, verify that the value of the isRemotable connector control is set to 1 in the connector configuration file.
- Verify that the connector is exposing Alerts as a supported USM type for synchronization (inbound to connector). You can do so by verifying that the connector configuration file has Alert listed under InboundToConnectorTypes.
- Enable CA Catalyst synchronizer from the CA SOI Administration UI.
- The default synchronization policy that is shipped with the product enables synchronizations (inbound to connector) for a specific connector or (domain manager). You may need to add your connector to this list as follows:
- Open the SOI_HOME\tomcat\registry\topology\physical\node0\sor\syncfilters\alert_filter.xml file in a text editor.
- Add your domain manager product identifier (for example, CA:01234) to the list of domain managers in the file.
An example is provided as follows:
<action defaultBehavior="drop">
<send>
<mdr productName="CA:00003" /> <!-- NSM-DSM -->
<mdr productName="CA:00005" /> <!-- SPIM -->
<mdr productName="CA:00031" /> <!-- SCOM -->
<mdr productName="CA:01234" /> <!— Your connector -->
</send>
</action>
- Reload the registry and restart the CA SAM Application Server service for the change to take effect.
Copyright © 2013 CA.
All rights reserved.
 
|
|