Filter
Top Products
Integrating Solutions with VPO
Defining an Integration Strategy
Chapter 2 79
Obtaining Coexistence of NNM and VPO Integrations
If you plan to integrate your product into both NNM and VPO, you can
choose between the following two strategies:
1. Develop an integration package for NNM and transform this into an
VPO integration package.
The VPO integration package resulting from this approach is not
improved.
2. Develop an integration package for NNM and develop a separate
integration package for VPO.
It is always possible to develop the NNM integration package first,
transform this to a VPO integration package, and then use the result
as a starting point for an independent VPO integration package.
Figure 2-3 on page 80 illustrates the two strategies. Using strategy 1
only the NNM migration package needs to be maintained; the
corresponding VPO integration package is always generated from the
NNM integration package. You will need to use strategy 2 if you want to
achieve a tight VPO integration that takes full advantage of the VPO
features, you will need to use strategy 2. A tight integration provides
maximum benefit to customers and is a prerequisite for achieving VPO
certification.
Figure 2-3 on page 80 also shows that there are no other strategies
available, as soon as you start to modify the VPO integration resulting
from the migration process, you are using strategy 2. Consequently, the
modified VPO integration can no longer be generated from the NNM
integration and needs to be maintained separately. It is not possible to
design a VPO integration first and to leverage from this for an NNM
integration.