ovowconfigexchange

The command ovowconfigexchange enables the exchange of configuration data (some specific subset) between cross-platform HPOM management servers (to support message forwarding), between HPOM for Windows and HPOM for UNIX servers in either direction.

This tool operates only on the HPOM for Windows platform. Its counterparts on HPOM for UNIX are opccfgupld/opccfgdwn and opctempl tools. It can upload data from HPOM for UNIX or download local configuration to files, formatted for upload to HPOM for UNIX. Files must be manually copied between the systems.

The following data exchange is supported:

Download of instruction texts from HPOM for Windows (-dnl INSTR_TXT)
A dummy HPOM for UNIX template (ovowhelptext) is generated that can be uploaded to HPOM for UNIX with the following command:

opctempl -add ovowhelptext

If the template already exists on the target HPOM for UNIX server, it must first be deleted and then uploaded again using the following sequence of commands to upload the ovowhelptext template.

opctempl -delete "OVOW_Instruction_Text_Import" MSG
opctempl -add ovowhelptext

NOTE: Do not use opctempl -modify. This results in changing the instruction texts IDs, which makes the uploaded texts unusable.

You do not need to distribute the template to any of the nodes.
Download of nodes and node groups from HPOM for Windows (-dnl NODES)
Data is transferred by using HPOM for UNIX node hierarchies that reflect the hierarchical structure of HPOM for Windows node groups. Generated files must be transferred to the HPOM for UNIX server and uploaded there with the opccfigupld tool.

After the upload, the added nodes are found in the newly created node hierarchy (named CFGX_*) and also in the Node Bank's Holding Area. Make sure that you add these nodes to the operator's responsibilities, so that you are able to see their messages. After using the opccfgupld command on HPOM for UNIX, you must restart HPOM for UNIX server processes with opcsv-start to be able to receive messages for added nodes.
Upload of nodes, node groups, and node hierarchies from HPOM for UNIX (-upl NODES)
Any node-related data (nodes, node groups, and node hierarchies) can be downloaded from HPOM for UNIX with the opccfgdwn tool. When the files (the complete, downloaded directory structure) are transferred to HPOM for Windows, they can be uploaded into HPOM for Windows with this tool.

NOTE:
When new nodes are uploaded to an HPOM for Windows server, then the autodeployment feature automatically deploys some core policies to the newly added nodes. If you do not want this behavior, you can change it by turning off the autodeployment feature, as described in the help topic Disable policy autodeployment. If you plan to turn off autodeployment just for the current node upload, remember to turn it on again afterwards.

The tool can read and write files in several different codesets, most of them being used on UNIX platforms. These are the keywords for codesets, understood by the -src_codeset and -dest_codeset options: ASCII, UTF8, ISO81 (for ISO88591), ISO82 (for ISO88592), ISO85 (for ISO88595), ISO815 (for ISO885915), ROMAN8, SJIS, EUCJP, GB2312, BIG5, EUCTW, EUCKR, and UNICODE (for Windows Unicode). When using files for or from HPOM for UNIX, the selected codeset must be compatible with the HPOM for UNIX server's database codeset.

Command synopsis

  -ent INSTR_TXT -dnl [<directory>] [-dest_codeset <codeset>] 

  -ent NODES
	 ( -dnl [<directory>] [-src_path <OVO_entity_path>]
							[-dest_codeset <codeset>]
						 [-no_ip_detect])|   
	 ( -upl <directory> [-dest_path <OVO_entity_path>] 
						[-src_codeset <codeset>] )

  -help

Options

-ent <entity> Specifies an entity for download or upload. <entity> can be INSTR_TXT or NODES.
-dnl <directory> Specifies the download operation and sets the target directory. If the directory is not given, the current directory is used as default. The following hierarchy will be created in given directory:
```
C
C\NODES
C\NODEHIER
```
-upl <directory> Specifies the upload operation and sets the source directory. The user must specify the path to the .idx file located in the "language" directory (for example, the C subdirectory).
-src_path <OVO_entity_path> Specifies the HPOM hierarchy path of an entity to be downloaded. This is used to select a specific node group for download.
-dest_path <OVO_entity_path> Specifies the HPOM hierarchy path for the upload of an entity. This is used to select the existing target node group where the new uploaded data will be stored. If this option is not set, a new generic path will be created to hold the uploaded data.
-no ip detect Disables IP detection for nodes through DNS during download from HPOM for Windows. By default, the IP is determined through DNS lookup if there is no explicit IP address available.
-dest_codeset <codeset> Specifies the codeset of the resulting files when data is downloaded from HPOM for Windows and formatted for HPOM for UNIX.
-src_codeset <codeset> Specifies the codeset of the source files when data is uploaded into HPOM for Windows.

Exit Values

None.

Restrictions

HPOM for UNIX does not allow nodes to belong to several different node groups. When uploading such configuration data into HPOM for UNIX, opccfgupld will issue warnings that duplicate nodes were found. A node will only be added to the first node group where it appears.

Related Files

None.

Examples

ovowconfigexchange -help
Outputs help and usage of the tool.
ovowconfigexchange -ent INSTR_TXT -dnl c:\data\transf\2 -dest_codeset SJIS
Downloads instruction texts from the HPOM for Windows server and stores them to a dummy HPOM for UNIX template file c:\data\transf\2\ovowhelptext using SJIS encoding.
ovowconfigexchange -ent NODES -dnl c:\temp\1 -src_path \cad\koeln3
Downloads node group \cad\koeln3 (with all its contents) from the HPOM for Windows server and creates the following HPOM for UNIX files:
```
c:\temp\1\C\1.idx
c:\temp\1\C\NODEHIER\nodehier.dat
c:\temp\1\C\NODES\nodes.dat
```
During download, the "language" directory is always set to C, regardless of the chosen destination codeset.

To upload the data into an HPOM for UNIX server, transfer the created files (from the c:\temp\1 directory downward) to the target machine (for example, to /tmp/transf/1 directory) and create the following structure:
```
  /tmp/transf/1/C/1.idx
  /tmp/transf/1/C/NODEHIER/nodehier.dat
  /tmp/transf/1/C/NODES/nodes.dat
  
```
Run the following command on the UNIX machine:

"opccfgupld /tmp/transf/1/" to upload it.
ovowconfigexchange -ent NODES -upl c:\temp\5\JP.SJIS\ -dest_path \cad\ulm -src_codeset SJIS
Uploads the HPOM for UNIX node data into HPOM for Windows, converting the files from the SJIS to the Windows Unicode codeset. HPOM for UNIX configuration files were manually transferred from HPOM for UNIX to HPOM for Windows beforehand and the following structure was created:

c:\temp\5\JP.SJIS\5.idx c:\temp\5\JP.SJIS\NODEHIER\nodehier.dat c:\temp\5\JP.SJIS\NODES\nodes.dat

The node hierarchy will be placed into the existing \cad\ulm node group on the HPOM for Windows server.

Configuration interoperability