Before any integration module implementations occur, you must ensure the logical management operation is associated to one or more integration modules. The integration module then must have an association with an operational management product. Finally, the logical management operations on each operational management product must be enabled.
Typically, there is a one-to-one communication between a logical management operation and an operational management product function. However, a single logical management operation invocation can cause the integration module to invoke an operational management product multiple times.
An integration module that uses an invocation channel can run logical management operations only in the following circumstances:
The integration module can support multiple logical management operations for an operational management product. When you run the integration module, the name and namespace values of the logical management operation specify the action to perform.
Operational management product and integration module associations are created when the OMPPRODUCTNAME and OMPVERSION values are added to the integration module. If multiple versions of the operational management product are used with the integration module, use a null value for the OMPVERSION.
More than one integration module can implement the same logical management operation on an operational management product. Use the ISPRIMARY attribute to identify the preferred integration module for the logical management operation on the operational management product. Only one integration module can have the ISPRIMARY value set to a true for any given logical management operation - operational management product combination.