Agent Message Stream Interface (MSI)
The Agent Message Stream Interface allows you to tap the message flow of an HPOM managed node to enable additional message processing by external applications before a message is sent to the management server. This can help to reduce the amount of network traffic considerably. A typical external application might be an event correlation engine, for example ECS.
NOTE:The HP Operations agent API includes support for C/C++ and Java, as well as for every language that supports DCOM automation (for example, VB, VBScript, JScript, and so on). However, the agent message stream interface supports C APIs only. All of the APIs are built using Microsoft Visual Studio 2005.
Enable the Agent Message Stream Interface
The Agent Message Stream interface is disabled per default on the managed nodes. To allow external programs to use the MSI on the agent, you must first enable it. To enable it, create a nodeinfo policy containingOPC_AGTMSI_ENABLE TRUE
on the management server, and deploy it to the managed nodes on which the MSI should be enabled.
Per default it is also not allowed to write messages containing automatic or operator initiated command to the MSI. The message agent discards the actions in the messages.
To allow the definition of automatic actions add the following to the nodeinfo policy:
OPC_AGTMSI_ALLOW_AA TRUE
To allow the definition of operator initiated actions add the following to the nodeinfo policy:
OPC_AGTMSI_ALLOW_OA TRUE
Configure messages to be sent to the Agent Message Stream Interface
Even if the Agent MSI is enabled and an application is registered for messages, you need to specify that a message should be sent to the agent MSI. You can do so in the policy editors on the "Message stream interface and external services" tab of the window "Outgoing Message".To define that a message should be sent to the agent MSI, select "Agent Message Stream Interface" and choose whether message are copied or diverted.