Filter
Top Products
Creating and Distributing an Integration Package
Uploading Configuration Information
Chapter 7266
These examples assume that a file tree containing configuration
information has already been created, using either the VPO
administrator’s GUI or the opccfgdwn(1M) command. The configuration
file tree is assumed to be in the directory:
/var/opt/OV/share/tmp/OpC_appl/newConf
Example 1: Uploading in Add Mode (Default)
This is the most straightforward way to use opccfgupld(1M). The entire
configuration information under the directory
/var/opt/OV/share/tmp/OpC_appl/newConf is uploaded into the VPO
internal database. As the Add mode is the default setting, you do not
need to specify the -add option. In this mode, only the entities that are
not already stored in the VPO database are uploaded from the
configuration file tree.
To keep the example output short, the file tree only contains
configuration information for two templates. To demonstrate the effect of
“Add” mode, the example shows what happens when one of the templates
already exists in the VPO internal database. You will see that a warning
message is generated for the existing template, and the new template is
added.
To upload a configuration file in “Add” mode, enter:
/opt/OV/bin/OpC/opccfgupld /var/opt/OV/share/tmp/\
OpC_appl/newConf
You will see the following messages displayed:
parsing index file
“/var/opt/OV/share/tmp/OpC_appl/newConf/C/newConf.idx”
starting upload
uploading logfile templates
Template Bad Logs (HP-UX standalone) already exists
(OpC50-79)
Warning: not all requested objects were processed.
(OpC50-24)
uploading interface templates
opccfgupld terminated with 2 warning(s)/error(s)