Filter
Top Products
Integrating Solutions with VPO
Defining an Integration Strategy
Chapter 2 81
Strategy 1: Use Transformed NNM Integration in VPO
This strategy has the following advantages:
❏ Requires little integration effort
You don’t need all the advanced features of VPO, and you don’t need
to identify new integration capabilities.
❏ The VPO integration will work in the same way as the NNM
integration.
This means an easy switchover for operators that used NNM and will
continue with VPO.
❏ Easy to maintain
You need only maintain the NNM integration package.
The VPO integration package is always generated from an NNM
integration package, using the recommended migration process.
This strategy has the following disadvantages:
❏ You do not achieve a tight VPO integration as VPO integration points
and features are not exploited.
❏ It is unlikely that this type of integration will satisfy the
requirements for VPO certification because of the large amount of
unused VPO functionality.
Strategy 2: Develop a Separate VPO Integration
This strategy has the following advantages:
❏ Use VPO features to increase the customer benefit of your
integration, for example, by providing detailed instructions to
operators. For more information, see “Leveraging From an
Integration into NNM” on page 73.
❏ Tight VPO integration can be achieved. This is also a prerequisite for
VPO certification of your integration.
This strategy has the following disadvantages:
❏ The resulting VPO integration package must be maintained as a
separate package
❏ Increased integration effort and planning required