Filter
Top Products
Creating and Distributing an Integration Package
Downloading Configuration Information
Chapter 7264
5. Advise the VPO administrator, for example, in the documentation of
the integration package, to distribute the new configuration
information to the required managed nodes.
In the Install/Update VPO Software and Configuration window,
the administrator must distribute Actions, Monitors or Commands,
depending on the requirements of the integration.
Warnings
It is important to consider the following issues when distributing
executables using VPO:
❏ Names of executable files must not exceed a length of 12 characters.
❏ Names of executables must be unique; the names must not conflict
with executables in other integration packages.
To achieve this, it is recommended to use the naming conventions
that are part of the certification requirements for VPO integration
packages. These naming conventions require integrators to prefix
object names with a unique string to identify their solution.
❏ Only small executable files may be distributed by VPO
Distribution to managed nodes depends on the vendor, platform, and
OS characteristics of the managed node and not on the templates or
monitors distributed to the managed node.
For example, you might provide a monitoring script for a business
application running on HP-UX 10.x machines. If you put the script
into the corresponding directory, download it, and then upload it onto
the customer’s management server, this script will be distributed to
any s800 machine running HP-UX 10.x, provided the administrator
distributes “Monitors” to these nodes. This will happen even if the
managed node doesn’t run any part of the business application
meaning that the monitor will never be used.