HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

24.3 Policy, Template, and Service Data Exchange

When the environment supports multiple management servers, it is practical for OVO Administrators to develop policies and templates that are shared among the servers. In other words, if you build the policy for one server it is transferred to other servers as required. The OV commands to facilitate the policy and template data exchange are executed from the command line and or the GUI.

24.3.1 OVOW to OVOU

For example, to distribute a policy from the OVOW server to the OVOU server, use the following guidelines:

• Use the utility program

  ovpmutil to download the policy from the OVOW server.

• Use the utility program

  ovpmutil to extract the policy data into a file.

• Transfer the policy file to the OVOU server.

• Use the utility program

  iconv to convert the codeset from OVOW to OVOU.

• Use the utility program

  opctempl to upload ( import) the OVOW policy.

• Use the command

  ovpmutil to extract the service tree into an XML file.

24.3.2 OVOU to OVOW

Template exchange from OVOU to OVOW should follow the guidelines listed here:

• Use the command

  opccfgdwn to download the template from OVOU (this can also be done via the GUI by selecting

  ActionsServerConfiguration Download ).

• Transfer the template file from OVOU to the OVOW server.

• Use the utility program

  importpolicies to import the OVOU template.

24.3.3 Interoperability Commands

Several programs help facilitate the interoperability between OVOW and OVOU. The definitions of some of the OVOW commands are shown here for reference; these commands are also found in the online help. The OVOU commands are also listed without full syntax (refer to Appendix A).

ovpmutil
ovpmutil is a tool that allows you to perform some configuration tasks from the command line. The tool can be used to

• Deploy policies.

• Download or upload policy, tool, or service information from the management server.

• Convert downloaded information between structured storage format and ASCII format.

• Register policies or policy groups.

Command syntax:

OvPMUtil [<flag-list>] <parameter-list>

Flag list:

[ -[?] [HELP] ] = Usage information

Parameter list:

DEP [(/p | /pg) /<policynamev] [(/n | /ng)<nodename>] [/c
(TRUE|FALSE)] [/e (TRUE|FALSE)][/t <type>][/v <versionv]
PCV [/x]|[/c [/v <version>][/n <name>][/i]] <filenamelistv
REG <policyfilename> /g <policygrouppath>
CFG <conftype> [UPL <configfilename>]|[DNL [/p <subtree>]
[/t <targetdir>][/a]]

DEP (deploy) options:

DEP [(/p | /pg) /<policyname>] [(/n | /ng)<nodename>] [/c
(TRUE|FALSE)][/e (TRUE|FALSE)][/t <type>][/v <version>]
<policyname>

This required parameter indicates the name of the policy or policy group to be deployed. It must contain the path to the policy as shown in the console tree, starting under Policy groups. Use /p to indicate a policy, or /pg to indicate a policy group. The path must begin with a backslash ("\"), and policy groups within the path are separated with a backslash ("\"). If the name of a policy group contains spaces, the entire path must be enclosed in quotation marks.

<nodename>

This required parameter indicates the name of the node or node group on which the policy will be deployed. It must contain the path to the node as shown in the console tree, starting under Nodes. Use /n to indicate a node, or /ng to indicate a node group. The path must begin with a backslash ("\"), and node groups within the path are separated with a backslash ("\"). If the name of a node group contains spaces, the entire path must be enclosed in quotation marks.

/c

(check version) If this optional parameter is set to FALSE, no version check is made, and the policy is deployed even if a newer version of that policy is already deployed on the node. If the parameter is TRUE (or absent), the policy will only be deployed if no newer version of the policy is deployed on the node.

/e

(enable) If this optional parameter is set to FALSE, the policies are disabled on the node after deployment. If this parameter is TRUE (or absent), the policy or policy group is enabled after deployment.

/t <type>

If this optional parameter is set, the policy will only be deployed if it is a policy of the given policy type. Only the original English names may be used, and must be enclosed in quotation marks, for example "Logfile Entry" or "Windows Management Interface". This parameter is not valid when a policy group is deployed.

/v <version>

If this optional parameter is set, the policy will only be deployed if it matches the given version. This parameter is not valid when a policy group is deployed.

PCV (Policy Conversion) Options:

Converts a policy structured storage file into two ASCII files (*.header and *.data), or converts the ASCII files into a policy structured storage file.

PCV [(/x <filenamelist> | /c <filenamelistv)]] [/v
<version>] [/n <name>][/i]] <filenamelistv
/x <filenamelist>

Extracts the structured policy store from <filenamelist>, which is a list of policy files (downloaded using ovpmutil CFG DNL) to be converted. The downloaded policy (which is a structured storage file) will be extracted into the header stream (*.header) containing the policy management information (for example, name, version, LogicalID, InstanceID and Checksum) and the data stream (*.data) containing the policy definition. Multiple structured storage files can be extracted by listing them separated with a space.

/c <filenamelist>

Combines the *.header and *.data files into a structured policy store. The filename list has the same format as for /x.

/v <version>

This optional parameter changes the version information of the policy to <version> during combination (the InstanceID and Checksum are also be updated). This option is not valid when the /x option is used.

/n <name>

This optional parameter changes the name given to the policy (new LogicalID, InstanceID is created and Checksum is updated).

i

If this optional parameter is specified, just the InstanceID (and Checksum) information of the policy is updated. If not specified and the Checksum does not match the data stream, an error is generated.

<filenamelist>

See previous description of /x.

CFG (Configuration Upload/Download) options:

CFG (POL|SVC|TLS)[UPL <configfilename>]|[DNL [/p <subtree>]
[/t <targetdir>][/a]]
CFG (POL|SVC|TLS)

Uploads or downloads the policy, service, or tool configuration.

POL = policy configuration

SVC = service configuration

TLS = tools configuration

UPL <configfilename>

Uploads a structured storage file created with the DNL option.

DNL

Downloads the policy, service, or tools configuration from PMAD and puts it into Structured Storage Files

/p <subtree>

This parameter is only valid for configuration download. For policies, it must contain a PATH from which policies are downloaded recursively. It must contain the path to the policy as shown in the console tree, starting under Policy groups. The path must begin with a backslash ("\"), and policy groups within the path are separated with a backslash ("\"). If the name of a policy group contains spaces, the entire path must be enclosed in quotation marks.

For services/tools configuration this parameter is the RELPATH of the item at which the recursive enumeration will begin. It defaults to the respective root item.

/t <targetdir>

This optional parameter indicates where the downloaded structured storage files should be written. If not specified, the configuration information is stored in the root directory (".") of the current drive.

/a

If this optional parameter is specified, all registered policies with all registered versions are downloaded into the file system.

REG (register) options:

REG <policyfilename> /g <policygrouppath>

The REG option is only useful when you want to upload a policy that does not have a structured storage file, or that should be uploaded to a location that is different from the policy's original location.

<policyfilename>

Name of a policyfile (structured store containing policy name and version information in the header as well as the stream in the data part) to be registered in the system.

<policygrouppath>

This is an optional parameter. It must contain PATH. If specified, the registered policy is also assigned to the group specified in <policygrouppath>.

Examples of using ovpmutil:

Download a policy and convert to ASCII format:

Import Policies
The tool Import Policies imports OpenView Operations for UNIX templates into OpenView Operations for Windows. The templates must be from OpenView Operations for UNIX version 5.33 or higher.

Usage:

ImportPolicies/f <policy file>
[/g <policy group>]
[/r | /d]
[/c ASCII|/c UTF8|/c ISO81|/c ISO82|/c ISO85|
/c ROMAN8|
/c SJIS|/c EUCJP|/c GB2312|/c BIG5|/c EUCTW|
/c EUCKR]

All imported policies are stored in subdirectories of the policy directory Policy Management\Policy Groups\Imports From File.

Policy File (/f)
The policy file contains one or more templates that will be imported as policies into OpenView Operations for Windows. This file is created by the config download command (opccfgdwn) on an OpenView Operations for UNIX server. For every template contained in the file, a new policy will be added to OpenView Operations for Windows.

Note

Refer to the

HP OpenView Operations for UNIX Administrator's Reference Volume I for information about downloading template files.

This table shows the OpenView Operations for UNIX message source types and shows the policy type to which they are converted:

Other OVOU message source types cannot be imported into OVOW.

Policy Group (/g)
If this optional parameter is given, the policies of the file are stored in the policy group "...\Imports From File\<policy group>". If the given group doesn't exist, it will be created.

If the /g option is omitted, a new policy group named with the current date and time will be created and used.

Replace (/r) Flag
Use this option if you want to replace any existing policies within <policy group> that have the same name as any template that you are importing.

CAUTION

The old policy is replaced and cannot be recovered. If neither the /r nor /d flag is used, policies that have the same name as an existing policy contained in<policy group> will not be imported.

Duplicate (/d) Flag
Use this option if you want to import policies that have the same name as existing polices in the same <policy group> without overwriting them. The policies will have different GUIDs.

If neither the /r nor /d flags is used, policies to be imported that have the same name as a policy contained in <policy group> will not be imported.

Codeset (/c)
This parameter must be set if the policy file contains non-ASCII characters (for example, a download file from an English OVOU server is encoded in iso8859-1, a download file from a Japanese OVOU server is encoded in Shift-JIS). In this case, the policies will be converted to the multibyte Unicode encoding UTF8 before adding to OVOW. (This is necessary because within OVOW all polices are stored in a Unicode encoding.)

If omitted, it is assumed that the given file (<policy file>) only contains ASCII data.

Convert OVOU Operations templates to OVOW policies:

OVO UNIX Interoperability Commands:

opctempl

opccfgdwn

opccfgupld