This document provides an overview of the changes made to HP Operations Manager for Windows for the 9.00 release (HPOM for Windows). It contains important information not included in the manuals or in online help.
In This Version
Documentation Updates
Installation Notes
Obsolescence Announcements
Known Problems, Limitations, and Workarounds
Documentation Errors
Local Language Support
Support
Legal Notices
HPOM for Windows is a distributed client/server IT operations solution that enables an IT organization to manage business services from centralized control points. HPOM for Windows is a management solution that snaps into the Microsoft Management Console (MMC). Through this console, HPOM for Windows supplies the information and tools for prioritizing and responding to problems that can affect your business.
HPOM for Windows manages your information technology environment by managing nodes and the services running on these managed nodes. It provides graphical user interfaces to configure policies, nodes, services, service types, tools, and user roles. These components work together to automate detection, evaluation, and responses to events and simplify the process of analyzing and resolving problems.
The HPOM for Windows media kit contains a number of CDs and DVDs required to install the HPOM for Windows foundation product and add-on products.
The HPOM for Windows media kit does not include the following products:
HPOM 9.00 for Windows includes the following new features:
Management server and remote console
The management server is available as 64-bit version, the remote console as both 32-bit and 64-bit version. Map views of nodes and services are only available in remote consoles on computers that have a 32-bit operating system.
The 64-bit version of HPOM for Windows no longer includes the DCE agent packages. You cannot install new DCE agents with HPOM 9.00 for Windows but you can continue to monitor nodes with existing DCE agents.
The 64-bit version of HPOM for Windows no longer includes the HP Performance Agent deployables. You cannot deploy the HP Performance Agent from the HPOM console. To install the HP Performance Agent software on nodes, manually install the HP Performance Agent software as described in the HP Performance Agent Installation and Configuration Guide.
Microsoft SQL Server
HPOM 9.00 for Windows supports a remote SQL Server database installed on 32-bit or 64-bit operating systems.
HP Performance Manager 8.20
HP Performance Manager 8.20 can be installed on 64-bit operating systems, on the same computer as your HPOM management server or on a different computer. If you install HP Performance Manager on the same computer as your HPOM management server, the installation configures the integration between HPOM and HP Performance Manager automatically.
HP Reporter 3.80
HP Reporter 3.80 can only be installed on computers that have a 32-bit operating system and can therefore not be installed on 64-bit management servers.
Simplified procedure
You can migrate an OVO 7.50, HPOM 8.1x, or HPOM 9.00 installation to HPOM 9.00 for Windows by inserting the HPOM 9.00 for Windows installation media and downloading the HPOM migration data using the export option. The installation automatically uploads the specified migration data to the new management server. (You cannot install HPOM 9.00 for Windows on computers with a 32-bit operating system.)
Interactive installation and migration guide
The interactive installation and migration guide enables you to specify the type of installation or migration that you want to perform, and then view or print a customized guide, which includes only the requirements and tasks that apply to you.
Event correlation is a technique to reduce the number of events reported in the IT environment so that only events that have more significance or a higher value are passed on. When analyzing an event stream, event correlation uses filters and searches for patterns to identify relationships between events. Related events can be consolidated into a single event, can be annotated with additional information, or can be replaced by a new event.
ECS on management server and managed nodes
HPOM 9.00 for Windows offers event correlation on both the management server and the managed nodes. The event correlation engine accesses the message flow through the message stream interface (MSI).
HP ECS Designer and HP Correlation Composer
HP ECS Designer is a graphical user interface for designing, verifying, simulating, and compiling EC circuits. The license to use HPOM does not include a license to use HP ECS Designer.
HP Correlation Composer is a light-weight version of HP ECS Designer. HP Correlation Composer enables you to customize a predefined correlation logic to meet your correlation requirements. It is easier to use than HP ECS Designer because you only modify correlation parameters rather than creating the correlation logic yourself. HP Correlation Composer runs inside the HP ECS Engine and is installed automatically with HPOM for Windows on the management server and with remote consoles. A separate license is not required.
Event correlation policies
Event correlation policies introduce a new policy type to HPOM 9.00 for Windows. Event correlation policies can be deployed to both the management server and to managed nodes.
HPOM for Windows uses the concept of virtual nodes to represent cluster resource groups. A virtual node can be regarded as a group of physical nodes linked by a common resource group name. The agents on these physical nodes automatically enable and disable policies on a physical node when the state of the resource group changes. You can deploy policies and instrumentation to a virtual node and you can execute tools as well as automatic and operator-initiated actions on a virtual node.
Configuration in node properties
To make a node a virtual node, configure the virtualization properties of the node by linking the node to the physical nodes on which it is hosted and by adding the name of the cluster resource group to the node.
Message enrichment
By default, messages that are generated by cluster-aware applications are associated with the physical nodes, not with the virtual node. To associate messages with the virtual node, configure the agents to replace the name of the physical node with the name of the virtual node in the message before sending the message to the management server. You can do this by deploying config file policies that HPOM for Windows provides to the physical nodes, and by adding special custom message attributes to the outgoing message in the policy.
Management server as virtual node
When you install the HPOM management server in a cluster, the installation automatically creates a virtual node to represent the HPOM resource group.
User-defined service discovery policies
You can create new service auto-discovery policies to discover services in your environment and automatically populate your service hierarchy. The services that you discover can belong to any existing service type, including any new service types that you have configured.
Discovery data forwarding
In an environment with multiple servers (HP Operations Manager and HP Operations Manager i), you can automatically synchronize node and service data with other servers by forwarding the information from one server to one or more other servers. The synchronized data includes nodes, external nodes, node groups, services, and service types.
MMC console
You can now select multiple nodes in the Configure Managed Nodes dialog box. This enables you to modify, copy, and delete multiple nodes at once. When you modify multiple nodes, you can change only those properties that must not be unique for a node.
The Console Properties dialog box now enables you to do the following:
Message Browser tab: Click Always apply my changes in message properties if you do not want to be asked to refresh the message when other processes or users have modified it. With this check box selected, HPOM always applies your changes to the message's properties and discards all other updates.
Misc tab: Select Ask for server name on each start to always be prompted for the name of the management server in the Connect to Server dialog.
Misc tab: Select Display properties on open editor to display the properties of the currently selected node, node group, service, or tool when the corresponding editor opens. You can configure this setting for the node, service, and tools editors.
The Policy management folder in the console tree can now show policies grouped by category. The policies grouped by type have been enhanced to include a new policy type for event correlation policies.
The status bars now show the total number of objects or the number of selected objects.
Finding nodes, services, tools, and policies can now be performed on groups. If multiple objects are found, the results provide detailed information about each object.
You can now specify thresholds in process monitor policies for the number of processes, CPU utilization, and memory usage.
Web console
The web console by default uses HTTPS to communicate with the management server. The first time you start a web console, you must download a certificate from https://<management_server>/ovoweb/certificate and import it into your web browser.
You can now configure IIS to use anonymous authentication (instead of the default Windows authentication). With anonymous authentication enabled, a logout button appears in the web console. The logged in user is logged off when the session ends.
A new default skin promotes the new HP look and feel.
The icons for nodes and services in the tree by default display the current status.
The node and service tree for operators has been aligned to the tree shown in the MMC console.
Map views offer new shortcut menus; the status in map views now updates dynamically.
The filter functionality has been aligned to the functionality offered by MMC consoles. Old web console filters are not migrated.
The number of columns that can be shown in the message browser has been increased so that you show more message details in the browser. You can now sort by up to three columns.
You can put nodes and services into unplanned outage mode.
You can assign ownership of messages to other users.
HPOM Web Services enable you to develop remote clients that access HPOM management servers using industry-standard terminology and technical standards, instead of product-specific interfaces.
HPOM Incident Web Service
The Incident Web Service now offers commands to start and stop automatic and operator-initiated actions on messages.
HPOM Tool Web Service
The HPOM Tool Web Service enables remote clients that you develop to start applications, scripts, and commands on managed nodes using the HPOM action system.
External nodes
The match pattern no longer differentiates whether a fully qualified domain name is DNS resolvable or not.
mib2policy
The mib2policy utility is a command line tool, used for converting MIB files to SNMP Interceptor policies.
Generate message keys automatically
You can configure the management server to automatically add message keys to messages without message keys. The management server calculates the message key based on the criteria that a message must meet to be considered a duplicate.
Send message when messages are discarded because of an unknown node
To track discarded messages, you can temporarily set the new server configuration variable "Send warning message for each discarded message" in the Message Action Server Message Filter namespace. If set to true, the management server sends a warning message that contains the name of the originating node in the message text. You can use this variable to detect systems that are not configured on the management server but that send many messages and hence slow down message processing.
| Module | New policy groups | New policies |
|---|---|---|
| Sample Policies |
|
|
|
|
|
|
|
|
| Module | Changed policies | |
| HPOM Self Management |
|
|
The first page of this release notes document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition,
go to the following web site:
http://h20230.www2.hp.com/selfsolve/manuals
NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader, go to the following web site:
http://www.adobe.com
Installation requirements, as well as instructions for installing HPOM for Windows, are documented in the interactive HP Operations Manager for Windows Installation and Migration Guide provided in HTML format. The document file is included on the product's installation media as:
\Documentation\HPOM Guides\<language>\HPOM Installation Guide.htm
NOTE: For information about migrating Smart Plug-ins (SPIs) from previous versions of HPOM to HPOM 9.00 SPI DVD (2010.3), see the Migration of Smart Plug-ins for HP Operations Manager white paper, which is available at HP Software Product Manuals.
The HPOM Installation and Migration Guide contains some incorrect or incomplete information"
Database user permissions are incomplete
Symptom: The task Check user account requirements contains a list of permissions that the installing user must have on SQL Server. This list is incomplete.
Solution: To install HPOM using an SQL Server database, the installing user must have permission to perform the following actions:
Downloading data to a network drive is not possible.
Symptom: In Japanese and Chinese locales, the task Export the migration data is incorrect.
Solution: The following note contains the correct information:
"The folder must already exist. You must specify a folder on a local drive on the management server."
Missing software requirements for cluster environments.
Symptom: In Japanese and Chinese locales, the task Check the software requirements is incomplete.
Solution: HPOM requires the following hotfixes for Windows Server 2008 R2:
KB953652 (see http://support.microsoft.com/kb/974930)
KB971403 (see http://support.microsoft.com/kb/981314)
Internet Information Services (IIS) requires the additional role service HTTP Errors.
Migrating HP Performance Manager graphs
Symptom: In Japanese and Chinese locales, the task Back up customized default templates of HP Performance Manager is incorrect.
Solution: If you want to continue using HP Performance Manager after the migration, create backup copies of any customized default templates in the following folders:
<install_dir>\newconfig\OVPM
<share_dir>\www\OVPM
Software and hardware requirements can be found in the HP Operations Manager for Windows Installation and Migration Guide.
Supported platforms are specified in detail in the support matrix available at this location:
http://support.openview.hp.com/selfsolve/document/KM323488
NOTE: If you are upgrading from previous versions of HP Operations Manager for Windows, be sure to read the HP Operations Manager for Windows Installation and MIgration Guide, available in .htm format on the product media. You must take certain steps before installing the current release.
Migration from OVO 7.50 or HPOM 8.1x fails because of corrupt policies (QCCR1A20287)
Symptom: The migration process stops during the migration data download. The following error description appears in the HPOM_Foundation_Download_detail.txt file:
2010.08.05 09:16:15.000 - STDOUT : Exporting of all policy versions to directory C:\Export\Policies\ has failed 2010.08.05 09:16:15.000 - STDOUT : (PMD1048) Checksum error: The policy header of the policy with the version id '2BF05436-A657-4644-9DB8-4A2011EE53CC' was manipulated in the database! 2010.08.05 09:16:15.015 - STDOUT : failed
Solution: Request a hotfix from your HP Support contact.
Migrating an HPOM 9.00 cluster installation migrates virtual nodes hosted on the source server (QCCR1A109845)
Symptom: When migrating an HPOM 9.00 cluster installation, virtual nodes that are hosted on the source management server are migrated to the target management server, but without their associations to physical nodes.
Solution: On the target management server, manually delete the virtual nodes that were hosted on the source management server.
Failed deployment jobs appear after migration (QCCR1A110558 and QCCR1A111143)
Symptom QCCR1A110558: Migration to a management server with a local SQL Server database: After the migration, failed deployment jobs are displayed for the management server or one of the cluster nodes. The agent on the management server or one of the cluster nodes fails to install.
Symptom QCCR1A111143: Migration to a management server with a remote SQL Server database: After the migration, failed deployment jobs are displayed for the management server.
The log files show the following error message:
2010.08.17 17:20:44.720 - STDOUT : Info : Got ManagementServer name from registry: mgmtsv.example.com 2010.08.17 17:20:44.751 - STDOUT : Info : Connecting to SQL Server... 2010.08.17 17:21:05.820 - STDERR : C:\OMW_APP\lbin\OvOW\SelfManagerInstall\InstallHTTPSAgtOnSvr.vbs(14, 1) Microsoft SQL Native Client: Unable to complete login process due to delay in opening server connection
Solution: Restart the failed deployment jobs after the installation.
After upgrading from OVO for Windows 7.50 errors occur while uninstalling Reporter packages for SPIs (QCCR1A24866)
Symptom: After upgrading from OVO for Windows 7.50 to HPOM 9.00 for Windows, one of the following error messages appears while uninstalling Reporter packages for any of the SPIs:
The errors occur because the upgrade process removes the ReporterLite component.
Solution: Before you upgrade OVO for Windows 7.50 to HPOM 9.00 for Windows, manually remove all Reporter packages for all installed SPIs using the Smart Plug-ins, New and Upgraded CD, for use with HP OpenView Operations 7.5 for Windows.
To remove Reporter packages on the management server:
For example, to remove the Reporter package for the SPI for SAP, double-click the file sapspi_reporter.msi in the folder \SPIs\SAP SPI Reporter Package.
Uninstallation of the management server hangs (QCCR1A108791)
Symptom: The uninstallation hangs while removing the package HP Software - E/A Consolidated Package. This happens only when the management server services were stopped before the uninstall was started.
Solution: When the uninstallation hangs, run vpstat.exe -3 -r start to start the management server services. The uninstallation will continue when the services are running.
Re-installation of the management server with different user account fails (QCCR1A111991)
Symptom: Re-installing the management server with different user accounts causes the installation to roll back during the installation of the HP Software - Embedded Licensing package.
Solution: Before attempting to re-install a management server with different user accounts, perform the following steps:
Change to the following folder on the management server, type:
cd %OvShareDir%\server\OprEl\AutoPass\
Delete the following files:
.backup
HttpProxy.properties
LicFile.txt
If you have already encountered this problem, allow the installation to roll back, delete the files, and restart the installation.
The following platforms are obsolete with HP Operations Manager 9.00 for Windows.
NOTE: The HP Obsolescence Policy provides you with the guidelines about the obsolescence of this product. To see the published policy, go to:
http://support.openview.hp.com/pdf/obsolescence_policy_v4.3.pdf
Also review the support matrix available at:
http://support.openview.hp.com/selfsolve/document/KM323488
HP discontinues support of the following agent platforms with the release of HP Operations Manager 9.00 for Windows.
DCE agents
DCE agents cannot be installed remotely or manually. For migration purposes, you can continue to monitor your already deployed DCE agents, for example you can continue to receive messages, start actions, and deploy policies. You cannot deploy any DCE agent package.
Support for DCE agents will be discontinued on August 31st, 2011.
None. (HPOM 9.00 for Windows is the first native release for the Windows Server 2008 R2 64-bit platform.)
Service Packs will become obsolete as per Microsoft lifecycle policy.
The following console platforms are not supported with HPOM 9.00 for Windows. Service Packs will become obsolete as per Microsoft lifecycle policy.
Microsoft Windows XP (all Service Packs)
Microsoft Windows Vista
The following web console platforms are not supported with HPOM 9.00 for Windows:
Microsoft Internet Explorer 6.x, 7.x
Mozilla Firefox 2.x, 3.0
HP discontinues support of the following databases:
Microsoft SQL Server 2005 Express
HPOM 9.00 for Windows does not support the following integrations:
HP Performance Manager 8.1
HP Performance Agent 4.x
HP Smart Plug-ins 2007.2, 2009
HP Dependency Mapping Automation 8.1
HP Business Availability Center 6.x, 7,x
HP Sitescope 8.x, 9.x
HP Performance Insight 5.3
HP Internet Services
HP Service Desk
HP Service Center
HP Network Node Manager/Windows 7.5x
HP Dashboard
HP does not offer HPOM 9.00 for Windows in the following language:
Korean
Occasionally the previous HP OpenView Operations product name or its OVO abbreviation may appear as an application name in a message browser message, in error messages, or in a policy name. This is not a cause for concern.
Reinstalling packages on the management server prevents the management server from restarting correctly, and causes the console to close suddenly (QCCR1A19359 and QCCR1A110914)
Symptom: If you create a job to reinstall all packages on a management server, the agent reinstallation downgrades some of the existing agent subpackages on the management server. The package reinstallation can cause two problems:
QCCR1A19359: Misleading error messages may appear and the console may close suddenly. You may be unable to reopen the console for several minutes. If you are also reinstalling policies, the policy deployment jobs fail.
QCCR1A110914: If you subsequently attempt to restart the management server, the policy management and deployment service (OvPmad) will not start.
Solution: If you need to reinstall the agent package on the management server, start the agent installation from a command prompt using opc_inst:
Copy the HTTPS agent installation packages into a temporary directory using the following command:
ovpmutil dnl pkg Operations-agent [<package version>] [/d <target directory>] /pnn <management server primary node name>
Navigate to the temporary directory that you copied the installation packages into. The directory contains opc_inst, which you use to start the installation.
cscript opc_inst.vbs -srv <management_server_host_name> -cert_srv <certificate_server_host_name>
NOTE: Do not use the -force option when you start opc_inst. Using this option will downgrade some of the existing agent subpackages on the management server.
After migrating a DCE agent to an HTTPS agent, the agent buffers messages for the old management server (QCCR1A112956)
Symptom: If you migrate a management server to a computer with a different hostname, and then use the new management server to install the HTTPS agent on a node that currently has the DCE agent, the migrated agent then attempts to send all messages to the old management server.
Solution: After the agent migrate completes successfully, you can use the Switch Agent's Certificate Server tool to correct the problem.
Select the node, and then click Launch.... The Tool Status dialog box opens and shows the results of the tool execution. After the tool successfully switches each node's certificate server, the Status column shows "Succeeded".
"Can't store message in database" message appears when uploading messages with ovowmsgutil (QCCR1A107182)
Symptom: When uploading messages with ovowmsgutil on a cluster node, the following events are logged in the application event log:
(MS232) Can't store message in database. (MS231) StoreToDB failed ((ITF32872E) Error 0x80048068 (FAILURE, Facility: ITF, Code: 32872)). (MS360) DB Access failure in method OvEpDBStoreMessage. Reason: (MS329) Failed to execute SQL command. DBMS error message: The statement has been terminated. SQLSTATE = 01000 SQLSTATE = 23000.
Solution: The problem occurs when the message and action service OvEpMessageActionServer is started before ovowmsgutil finishes. In many cases the self-management policy VP_SM_OVOWServices restarts the message and action service. To avoid this, disable the policy VP_SM_OVOWServices before starting ovowmsgutil. Do not enable the policy before ovowmsgutil has completed.
Deployment error when installing the HP Operations Agent on Windows 7 32-bit (QCCR1A94583)
Symptom: When installing the HP Operations agent on Windows 7, 32-bit, the deployment job fails because no agent binaries for Windows 7 32-bit are available.
Solution: To install the HP Operations agent on Windows 7, 32-bit computers, perform the following steps:
In the System tab of the Node Properties dialog box, select Vista (6.0) as version and 32 as bit length.
Deploy the HP Operations agent to the node.
Request hotfix QCCR1A94583 from your HP Support contact and install the hotfix on the Windows 7 32-bit node.
Remote deployment of HP Operations Agent fails if HP Performance Agent 5.0 is already installed on that node (QCCR1A112942)
Symptom: When you try to deploy the HP Operations Agent (using the console) to a Windows Server 2008 R2 managed node on which the HP Performance Agent 5.0 is already installed, the job will fail. The detailed error message states that the package could not be deployed, because a file could not be copied to the new node.
Solution: Install the HP Operations Agent manually on that node. For details on manual agent installation, see the online help topic Manual installation of HTTPS agents.
Text-based license report cannot be generated (QCCR1A112641)
Symptom: If you launch the Text-Based License Report tool from the console, it fails. The tool output contains the following message:
ERROR: (oprel-411) Exception:
(oprel-163) Error: LicenseReporter Constructor failed:
'(oprel-165) Error: Creation of ID Mapping list failed:
'(oprel-24) Error in ELIDMapXmlParser Parser: '(oprel-31) Error:
Checking feature IDs failed: '(oprel-29) Getting license details
from AutoPass failed. 'Error in reading the license file:C:\
ProgramData\HP\HP BTO Software\shared\server\OprEl\AutoPass\\
LicFile.txt: Permission denied'. '. '. '. '.
Solution: In Windows Explorer on the management server, give the agent user (which is by default SYSTEM) permission to read the following file:
%OvShareDir%server\OprEl\AutoPass\LicFile.txt
HP SiteScope Administrator integration does not work (QCCR1A112288)
Symptom: After you install HP SiteScope Administrator integration, and launch the SiteScope Administrator tool, a browser window opens. The browser window contains numerous error messages.
Solution: After you install HP SiteScope Administrator integration, complete the following steps:
Log in to the management server as a user with administrative rights.
Open a command prompt, and then type the following command:
ovcert -list -ovrg server
Make a note of the alias of the management server certificate. The alias of the management server certificate is the long sequence of characters, which appears under the heading "Certificates" and is followed by an asterisk (*).
For example:
3d6cb862-9fbb-753e-0600-e88eb3c82c16
Export the certificates, using the following command:
ovcert -exportcert -file <filename>
Replace <filename> with any name for the file, for example, cert.p12.
You are prompted to specify a password to secure the exported certificate. Type a password of your choice (for example lwssoomw), and make sure you can recall it.
You see a message confirming that the certificate has been successfully exported to the the file you specified (cert.p12, in our example).
Store the certificate in a new file, by running the keytool.exe tool from the %OvInstallDir%\nonOV\jre\b\bin\ folder.
To store the certificate in a new file, type the following command:
keytool -export -alias <certificate_alias> -keystore cert.p12 -storepass <password> -storetype PKCS12 -file new.cer
Replace <certificate_alias> with the alias of the management server certificate that you noted previously. Replace <password> with the password you specified when you exported the certificates.
This command takes the certificate from the file you created (in our example, cert.p12), and stores it in the file new.cer.
Type the following command:
keytool -import -alias <certificate_alias> -file new.cer -keystore lwsso.jks -storepass <password>
At the prompt Trust this certificate? [no]:, type y to add the certificate to the keystore.
Copy the file lwsso.jks to the following folder:
%OvInstallDir%\nonOV\tomcat\b\www\webapps\topaz\WEB-INF\classes
In the same folder, edit the file lwssofmconf.xml as follows:
Find and replace all instances of the filename keyStoreFileName="java.keystore" with keyStoreFileName="lwsso.jks".
Find and replace all instances of the password keyStorePassword="mercurypw" with keyStorePassword="<password>"
Replace <password> with the password you specified when you exported the certificates.
Find the string <saml2Validation useGZIPCompression="false"> and replace it with <saml2Validation useGZIPCompression="false" publicKeyAlias="<certificate_alias>">
Replace <certificate_alias> with the alias of the management server certificate that you noted previously.
Save and close lwssofmconf.xml.
In Windows Explorer, double click the following file to open the Tomcat(B) Servlet Container Service Properties dialog box:
%OvInstallDir%\nonOV\tomcat\b\bin\OvTomcatB.exe
In the Java tab, append the following lines to the Java Options:
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Ducf.webapp.root=/topaz -DrepositoryApiClass=com.mercury.sitescope.ucf.api.repository.SamRepositoryImpl
In the Startup tab, add the following path in Working Path:
C:\Program Files\HP\HP BTO Software\nonOV\tomcat\b
Add a version of the log4j package higher than log4j-1.2.12 to the following folder:
%OvInstallDir%\nonOV\tomcat\b\www\webapps\topaz\WEB-INF\lib
You can download an archive that contains the log4j package from the following location:
http://logging.apache.org/log4j/1.2/download.html
After you download the archive from this location, extract the JAR file that contains the package (for example log4j-1.2.16.jar) and copy it the folder mentioned above.
To restart the Tomcat servlet container, type the following command:
ovc -restart ovtomcatB
Policy "Update_HierarchicalNodes" fails if the database is on a remote system (QCCR1A111708)
Symptom: The policy "Update_HierarchicalNodes", which is by default deployed to the management server, cannot handle remote databases. Therefore, the hierarchical nodes are not updated. On the computer that hosts the remote database, the Windows event log contains entries relating to failed logins.
Solution: Perform the following steps to work around this problem:
Uninstall the policy "Update_HierarchicalNodes" from the management server.
Extract the script from the policy and save it to a VB Script file.
Create a new scheduled task policy that starts the VB Script using an account that has administrative permissions on the SQL Server instance .
Deploy the new policy to the management server node.
HPOM for Windows services on the management server fail to start (QCCR1A37349)
Symptom: After a reboot of the HPOM for Windows management server with the HP BAC Adapter installed, the HPOM for Windows services may take a long time to start or may fail to start.
Solution:
Open the Start menu and select Run. Then type regedit and click OK.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HPOvOpc2Bac
DependsOnService to modify it, add the following string at the end of the list (in a new line), then click OK:
OvEpMessageActionServer
Generic Service in the HPOM for Windows resource group, then click Next.HPOvOpc2Bac in the Generic Service Parameters page, then click Next.For more information about certificate management and problems related to certificate handling, see the Certificate Management in Environments with Multiple HP BTO Software Products white paper. This document is located on the product media, in the Documentation\Whitepapers directory.
Incident and Tool Web Services fail if .NET is installed before Microsoft Internet Information Services (IIS)
Symptom: IIS and .NET are prerequisites for the HPOM for Windows management server. If you install .NET before IIS, the Incident and Tool Web Services fail. For example, you get a page not found error if you type the following URL in a web browser:
https://<HPOM_server_name>:<IIS_HTTPS_port>/opr-webservice/Incident.svc
(the default IIS HTTPS port is 443).
Solution: Make sure that you install IIS before .NET if possible. Otherwise, after you install IIS, remove the .NET Framework 3.5.1 feature manually using the Server Manager, and then add it again.
Additionally, if you have already installed HPOM for Windows on the management server:
Open a command prompt, and type the following command, which ensures that .NET is registered with IIS:
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
Insert the HPOM for Windows installation media on the management server. In the command prompt, navigate to the following folder:
\x64\Packages\Web Services
Type the following command, which uninstalls the Incident and Tool Web Services:
msiexec /x HPOprWsInc-09.10.050-Win5.2_64-release.msi ZBIGNORECONDITIONS=TRUE
Type the following command, which reinstalls the Incident and Tool Web Services:
msiexec /i HPOprWsInc-09.10.050-Win5.2_64-release.msi
Restart the World Wide Web Publishing Service.
On Simplified Chinese computers, the command ovocomposer does not work (QCCR1A112781)
Symptom: If you start the command ovocomposer on a Simplified Chinese computer, the command outputs an error message.
Solution: Use the English version of ovocomposer on Simplified Chinese computers. Use the following command:
"%OvInstallDir%\nonOV\perl\a\bin\perl" "%OvInstallDir%\lbin\OvOW\en\ovocomposer.pl"
32-bit versions of Infrastructure SPIs are not compatible with 64-bit versions of HPOM (QCCR1A114384)
Symptom: Infrastructure SPIs version 1.60 are available in 32-bit and 64-bit packages. Both the 32-bit and 64-bit packages have the same version number, but the 32-bit packages are not compatible with management servers that run a 64-bit version of HPOM.
Solution: If you are installing Infrastructure SPIs, make sure that you install the 64-bit packages on management servers that run a 64-bit version of HPOM.
The online help contains the following incorrect information:
Cluster awareness: messages should not be sent during cluster failover
Symptom: The online help topic Customize resource group state mappings incorrectly states that the agent parameter ClusterGroupPartialOnline in the namespace conf.cluster.RGState.MSCS has the default value online. The default value is actually offline.
Policies that monitor cluster resources in Microsoft Windows clusters may therefore send messages during a failover.
Solution: When you install the agent on a node that is part of a Microsoft Windows cluster, manually set the agent parameter ClusterGroupPartialOnline in the namespace conf.cluster.RGState.MSCS to online.
There are several different ways to set agent parameters:
ovconfchg at a command prompt on the node.Using ovconfpar at a command prompt on the management server.
For more details on setting agent parameters, see the online help.
Users cannot view Tools tree and Policies tree in the web console.
Symptom: In Japanese and Chinese locales, the online help topic Security Settings is incomplete.
Solution: The following note is missing from the help topic:
"If you connect to the web console using Internet Explorer on the management server, you may also need to add the URL to the list of trusted sites in the Internet Options dialog box, and then restart Internet Explorer completely."
Flexible management configuration in cluster environments
Symptom: In Japanese and Chinese locales, the online help topic Configure action-allowed and secondary managers is incomplete.
Solution: The following text is missing from the help topic:
"For management servers in clusters, specify the IP address or host name of the virtual management server. In addition, you must add the core ID of the virtual management server."
Policy deployment to virtual nodes
Symptom: In Japanese and Chinese locales, the online help topics Create virtual nodes and Deploy a policy or policy group are incomplete.
Solution: The following text is missing from the help topics:
Create virtual nodes
Step 11: "The management server always deploys all policies to a virtual node, even if a more recent version of the policy already exists on the virtual node. Selecting Deploy policy only if version is newer in the Deploy policies on dialog box has no effect. "
Deploy a policy or policy group
Step 4: "For virtual nodes, the management server always deploys all policies, even if a more recent version of the policy already exists on the virtual node. Selecting this check box has no effect when deploying policies to a virtual node."
Config file policy deployment to manage cluster-aware applications
Symptom: In Japanese and Chinese locales, the online help topic Receive messages for virtual nodes is incomplete.
Solution: The following step is missing from the help topic:
Step 7: "Assign the category ClAw to the policy to associate the config file instrumentation with the policy. This ensures that the management server automatically deploys the config file instrumentation when it deploys the config file policy:
Click File > Properties in the menu bar of the config file policy. A dialog box opens and displays the properties of the policy.
In the Category field, type ClAw.
Click OK to save your changes and close the properties dialog box."
Event correlation
Symptom: In Japanese and Chinese locales, the location of global data and fact stores is missing from the online help.
Solution: "You must store global data store (dstore.ds) and fact store (fstore.fs) files in the following folders:
Management server: %OvShareDir%\conf\ec
Nodes with a UNIX or Linux operating system: <OvDataDir>/conf/ec
Nodes with a Windows operating system: %OvDataDir%\conf\ec"
Symptom: In Japanese and Chinese locales, the location of Perl libraries is incorrect in the online help.
Solution: "If the fact stores call external Perl functions, store the Perl scripts in the following folder:
Management server: %OvDataDir%\contrib\ecs\external\perl
Nodes with a UNIX or Linux operating system: <OvInstallDir>/contrib/ecs/external/perl
Nodes with a Windows operating system: %OvInstallDir%\contrib\ecs\external\perl"
HPOM 9.00 for Windows includes localized versions for the Japanese and Simplified Chinese languages.
NOTE: HP does not offer HPOM 9.00 for Windows in the Korean language.
You can visit the HP Software Support web site at:
http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP offers.
HP Software online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to do the following:
NOTE: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to the following URL:
http://h20230.www2.hp.com/new_access_levels.jsp
To register for an HP Passport ID, go to the following URL:
http://h20229.www2.hp.com/passport-registration.html
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
For information about third-party and/or open source license agreements, see the \Open Source Licenses directory on the product installation media.
To view open source code, see the \x64\Redist and \x86\Redist directories on the product installation media.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
© Copyright 1999-2010 Hewlett-Packard Development Company, L.P.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java is a registered trademark of Oracle and/or its affiliates.
Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
This product includes software developed by the JDOM Project (http://www.jdom.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes an interface of the 'zlib' general purpose compression library, which is Copyright © 1995-2002 Jean-loup Gailly and Mark Adler.