HP Operations Manager for Windows

Server-based MSI Policies


The server-based message stream interface (MSI) enables external applications to read and change incoming messages on the management server before they are stored in the database.

Note NOTE:
The policy that generates a message must specify that the management server diverts or copies the message to the MSI. Otherwise, the message bypasses the MSI.

Each external application must be registered with the MSI on the management server using a server-based MSI policy. Normally, if a Smart Plug-in (SPI) uses server-based MSI, it includes the policy for the external applications that it provides.

If you develop your own MSI applications using the C and COM APIs provided, you must install the applications on the management server. You must then create or modify a server-based MSI policy to register them, and then deploy the policy to the management server that you want to configure.

To create a server-based MSI policy:

  1. In the console tree, under Policy managementarrowServer policies grouped by type, right-click Server-based MSI and then click NewarrowPolicy. The server-based MSI policy editor appears.
  2. To add details of an application instance, click New. The MSI instance dialog appears.
  3. Optional. Type a Description of the instance for future reference.
  4. Specify an Order number in the range -127 to 127. This controls the order in which application instances can read and change the stream of incoming messages. An application instance with a lower order number is able to read, change, and delete messages before an application instance with a higher order number.

    If multiple application instances have the same order number, the management server forwards messages to all the application instances at the same time.

    Caution CAUTION:
    Forwarding messages to multiple application instances at the same time can have undesirable results with diverted messages, because there will be two messages in the message stream with the same message ID.

    The same problem can also occur with messages that are copied to the MSI, if at least two application instances receive the same message in parallel and do not modify it.

  5. Type the Instance name of the external application.
  6. Click the Application type that corresponds to the API that the application uses to interact with the MSI. This can either be the Legacy UNIX API (which is the C API), or COM.
  7. Click OK. You return to the server-based MSI policy editor.
  8. Optional. Add further application instances. To reorder the instances, click an instance in the list, and then click Move Up, Move Down, or type a number and click Move to.

  9. Save the policy, and then deploy it to the management server that you want to configure.

Related Topics: