CA Automation Point places a value of AutomationPoint in the CA NSM Source field of any message it sends to CA NSM. To prevent CA Automation Point and CA NSM from entering an infinite loop, CA Automation Point does not read any messages from the CA NSM event log that have this value.
However, the CA NSM SENDOPER action retains the Source field from the original message. For example, when SENDOPER is used to place an NMFIND or SESSCMD request into the CA NSM event log (in response to a message originally sent from CA Automation Point) the Source field will contain the value AutomationPoint. Therefore, that value in the Source field causes CA Automation Point to ignore the NMFIND or SESSCMD request.
To avoid this situation, we recommend that when CA Automation Point captures an event that requires a notification or host command request, CA Automation Point should issue the request directly from CA Automation Point rules. CA Automation Point can then send a message to CA NSM acknowledging that it encountered the event and took corrective action.
However, if you decide that it is necessary to issue requests directly from CA Automation Point to CA NSM, follow following the procedure to ensure that CA Automation Point will accept the requests. In this procedure you configure the CA NSM message action record that specifies that SENDOPER is the action to be taken.
To configure the CA NSM message action record
Copyright © 2012 CA. All rights reserved. |
|