Moving configuration information between version HP Operations
Manager (HPOM) 7.x or 8.x management servers on UNIX or Windows can
be expected to function with the exceptions noted below:
Templates/Policies
Special characters and spaces are allowed in template names, but
not in policy names. Rename templates that contain such characters
before attempting to upload them to an HPOM for Windows management
server.
Log file template / Log file Entry policy: Supported.
HPOM for UNIX log file templates with a Windows Event Log source
will be converted to Windows Event Log policies.
Windows Event Log policy: Supported.
HPOM for Windows policies of this type will be converted to log
file templates with source 'Event Log'.
opcmsg template / Open Message Interface policy: Supported.
No restrictions.
SNMP trap template/ SNMP Interceptor policy: Supported.
No restrictions.
Scheduled action template / Scheduled task policy: Supported if
no scripting is used.
HPOM for Windows 7.x policies can only be imported into HPOM for
UNIX if they do not use scripting.
Threshold Monitor template / Measurement Threshold policy:
Conversion is possible from HPOM for UNIX 7.x and 8.x to HPOM for
Windows 8.x.
Agent-based flexible management template/flexible management
policy: Cannot be downloaded or uploaded with command-line tools.
Use the editors to cut and paste instead. Escalation, message
forwarding, and service outage are supported only in HPOM for UNIX
environments.
You cannot exchange the following types of HPOM for UNIX
template, because there are no equivalent policy types in HPOM for
Windows:
Event correlation circuit (EC) templates
MPE/iX console (Console) templates
You cannot exchange the following types of HPOM for Windows
policies, because there are no equivalent template types in HPOM
for UNIX:
Windows Management Interface (WMI) policies
Service auto-discovery policies
Node info policies
Nodes
Use ovowconfigexchange
to exchange configuration data (some specific subset) between HPOM
for Windows and HPOM for UNIX servers in either direction. Use the
tool ovpmutil
to exchange configuration data between two HP Operations management
servers. Nodes with a type that is not supported with HPOM for
Windows cannot be uploaded (for example, Node for External Events,
MPE node).
User Roles
Only possible between two HPOM for UNIX management servers or two
HPOM for Windows management servers. Exchange of user roles is not
possible between HPOM for Windows and HPOM for UNIX.
Tools/Applications
Only possible between two HPOM for UNIX management servers or two
HPOM for Windows management servers. Exchange of tools and
applications is not possible between HPOM for Windows and HPOM for
UNIX.
Services
Only possible for two HPOM for UNIX management servers or two HPOM
for Windows management servers, but not from HPOM for UNIX to HPOM
for Windows. From HPOM for Windows 8.x to HPOM for UNIX, with known
restrictions.
Reports and graphics associated with services on Windows are
ignored when uploaded into UNIX.
GUIDs of hosting nodes are replaced by fully qualified host
names.
Some fields are known on UNIX but not on Windows (depth,
background, title, service attributes, icons) and are not
filled.
Operator assignment must be done manually after uploading a
Windows service configuration into UNIX.
The tool-user field might not be set on Windows, but is a
required field on UNIX. Set this before exporting, or edit the
exported XML file.
The tool-password field on Windows is ignored. (An equivalent
field does not exist in HPOM for UNIX.)
Instrumentation
Although instrumentation, (the contents of the action, monitor, and
command directories) can be copied between servers, the UNIX
management server does not allow subdirectories. This means
categories cannot be established to automatically deploy
instrumentation along with a particular policy.