Filter
Top Products
Integrating Solutions with VPO
The Role of Configuration Data in an Integration
Chapter 284
The Role of Configuration Data in an
Integration
Figure 1-1 on page 32 shows an overview of the integration process in
which it distinguishes between defining an integration strategy and
implementing an integration. The figure shows that the result of an
integration process is an integration package which enables the
partner solution and VPO to work together smoothly.
An integration package always contains VPO configuration information,
which includes definitions for some, or all, of the following object classes:
❏ Applications and application groups
❏ Instruction text interfaces
❏ Managed nodes
❏ Message groups
❏ Node defaults
❏ Node groups
❏ Node Hierarchies
❏ Notification services
❏ Templates and template groups
❏ User and user profiles
❏ Action, command, and monitor executables
❏ Administrator configuration
❏ Database maintenance (configuration of VPO internal database)
❏ Escalation manager configuration
❏ Event correlation libraries
❏ Event correlation modules
❏ Management server configuration
❏ Message forwarding configuration
❏ Regroup conditions
❏ Responsible manager configuration
❏ Trouble ticket configuration
Configuration data in the local database determines the operational
behavior of VPO. Consequently, the configuration data required by VPO
to interact with a partner solution must be incorporated into the VPO
internal database using the configuration download and upload utilities
of VPO.