Filter
Top Products
Creating and Distributing an Integration Package
Downloading Configuration Information
Chapter 7 263
Prepare an executable for distribution by VPO as follows:
1. Place the executable into a source directory from which VPO will
fetch it during the configuration downloading. On the VPO
management server, use the directory:
/var/opt/OV/share/databases/OpC/mgd_node/customer
A 3-level directory hierarchy below this directory is predefined
according to vendor, platform, and OS. Each directory below this
triplet contains subdirectories for monitors, commands, actions, and
package types. The package type is the communication type used by
remote procedure calls (RPCs) of a particular agent platform.
If your executables depend on the communication type, that is on
NCS_RPC, on RPC_DCE_TCP, or on RPC_DCE_UDP, place them in
the directories below the package type level. If they are independent
of the communication type, place them in the appropriate
subdirectory below the triplet.
For example, a monitoring executable suitable for 10.x agents on s700
and s800 machines and using the RPC_DCE_TCP communication
type, needs to be placed into the following subdirectories:
/var/opt/OV/share/databases/OpC/mgd_node/customer
./hp/s700/hp-ux10/RPC_DCE_TCP/monitor
./hp/s800/hp-ux10/RPC_DCE_TCP/monitor
2. When choosing the configuration information to be downloaded, make
sure that your executables are included.
This has the effect that when you download the configuration
information, VPO fetches the executables from the directory where
you put them and includes them in the file tree with the configuration
information.
3. Create the integration package including the configuration
information and ship to the customer.
4. Upload the configuration information at the customer’s site.
This causes VPO to copy the executables into a VPO-maintained
directory on the customer’s management server.