Filter
Top Products
Integrating Solutions with VPO
Summary of the Integration Process
Chapter 282
Summary of the Integration Process
The outcome of any integration is an integration package that
contains VPO configuration information. Depending on the product you
are integrating, you may need to modify the software of the partner
solution or even implement additional processes, for example, when
using the VPO APIs. In this case, the integration package would contain
other items in addition to the VPO configuration information.
You may find it useful to answer the following questions as a rough guide
to defining an integration strategy:
❏ What will an operator using VPO see of the partner solution?
❏ Which messages and applications will be available?
❏ Will there be any new message groups?
❏ Can you include automatic and operator-initiated actions?
❏ For which types of message can you provide instructions?
❏ Are there any numeric values that can be monitored by VPO?
❏ Does the partner solution include applications or tools that can be
offered to VPO operators in the application desktop?
The integration process takes the following steps:
1. Select the integration capabilities you need to implement the
required functionality.
You may need to use more than one of the VPO integration
capabilities to implement a certain functionality.
The result of this step is a design plan for the integration.
2. Define the required configuration information using the VPO
administrator’s GUI. This includes:
• Templates for the selected message sources: logfiles, SNMP traps,
MPE/iX console messages, and calls to the VPO APIs. You will
also need to define message and suppress conditions.
• Instructions for operators, automatic actions, and
operator-initiated actions to be coupled with messages.
• Threshold monitors