HP Operations Manager Dependency Mapping Automation

for UNIX® operating systems

Release Notes

Software version: 8.20 / August 2011

This document provides an overview of HP Operations Manager Dependency Mapping Automation (HPOM DMA) 8.20 (patch DMA_00001). It contains important information not included in the manuals or in the online help.

In This Version
Documentation Updates
Installation Notes
Known Problems, Limitations, and Workarounds
Support
Legal Notices

In This Version

HP Operations Manager Dependency Mapping Automation (HPOM DMA) enables IT Operations teams to align their activities more fully with the business services that the IT infrastructure supports. By providing automated dependency mapping and configuration consistency in environments with multiple HP Operations Manager servers, HPOM DMA optimizes the ability of IT organizations to support their businesses and enables enhanced productivity and efficiency within the Operations teams.

New features in the 8.20 release include:

• Configuring Smart Message Mapping using the console

  You can configure all aspects of the Smart Message Mapper using the Smart Message Mapper page in the HPOM DMA console:

  • Hint separator

    Formerly known as keyword separator. The hint separator is used as the indicator for the Smart Message Mapper to divide an incoming message into the required hints. The default hint separator is a colon (:).

  • Hostname separator

    The hostname separator is used as the indicator for Smart Message Mapping to identify the start of the hostname in an incoming message. The default hostname separator is two at signs (@@).

  • Case sensitivity

    The Smart Message Mapper is by default configured to consider the case of the text in incoming messages.

  • Update delay

    Formerly known as sleep time. The Smart Message Mapping update delay stops the Smart Message Mapper from updating too often when there are multiple service changes in HPOM within a short period of time. The default delay is set to 15 minutes.

  • Polling interval

    The polling interval determines how often the Smart Message Mapper checks the service engine for new, modified, or deleted services. After a change has been detected, the Smart Message Mapper schedules an update of its cache. The schedule is determined by the update delay setting. The default polling interval is set to 60 seconds. The minimum interval is one second.

  • Custom message attributes

    You can use Smart Message Mapping to attach CI attributes as custom message attributes to HPOM messages. In HPOM, you can then look up CI information directly in the message instead of viewing the properties of services. Before Smart Message Mapping can attach CI attributes to messages, the CI attributes must be mapped to service attributes using attribute mapping rules.

• Configuring Smart Message Mapping to ignore messages

  You can specify a filter that uses regular expressions to match certain messages. The Smart Message Mapper ignores all messages that match the filter.

• Customizing the ID of services synchronized from UCMDB or BAC

  You can customize the service ID that HPOM DMA assigns to services synchronized from UCMDB using attribute mapping or scripting.

• Securing the communication with HPOM

  HPOM DMA web service clients by default use SSL HTTP to communicate with the HPOM for UNIX or Windows web services. Also by default, HPOM DMA web service clients trust all certificates issued from HPOM management servers in the environment.

• Pre-mapping scripts

  Pre-mapping scripts enable you to modify the normalized CI hierarchy during the synchronization process, before the mapping rules are applied.

• Setting the IP address for CIs of Type host

  The Default synchronization package now contains a pre-mapping script that sets the ipAddresses attribute for CIs of type host. In HPOM, this information is used to set the IP address of a managed node.

• DNS Mapping synchronization package

  The DNS Mapping synchronization package is deployed as part of the standard installation. It contains a pre-mapping script to map DNS names of hosts.

• HPOM root service

  The default HPOM root service (set in the Content page of the HPOM DMA console), has changed from CMDB to ROOT_DMA_Service. The display name remains CMDB. For more information, see the chapter "Upgrading HPOM DMA" in the HPOM DMA Installation and User's Guide.

• Synchronizing with HP Operations Manager i

  After having synchronized nodes and services from the UCMDB to HPOM with HPOM DMA, you can use HP Operations Manager i to synchronize these nodes and services from HPOM to the source UCMDB. For more information, refer to the Deploying OMi as part of the BSM solution white paper, which is available from the HP Product Manuals web site.

For more detailed technical or ordering information, please go to http://www.hp.com/go/software or contact your HP Software Sales organization.

Documentation Updates

The first page of this release notes document contains the following identifying information:

• Version number, which indicates the software version.
• Publish date, which changes each time the document is updated.

To check for recent updates or to verify that you are using the most recent edition, go to the HP Product Manuals web site.

NOTE: You require an HP Passport account to access this information.

To register for an HP Passport ID, go to the web site:

http://h20229.www2.hp.com/passport-registration.html

Installation Notes

Installation requirements and instructions for installing HPOM DMA are documented in the HP Operations Manager Dependency Mapping Automation Installation and User's Guide provided in Adobe Acrobat (*.pdf) format. The latest version of this document is available from the HP Product Manuals web site.

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 web site:

http://www.adobe.com

Support Matrix

HPOM DMA 8.20 supports the following versions of HP Operations Manager, HP Business Availability Center, and HP Universal CMDB:

For details of the product versions supported with HPOM DMA 8.20, see the support matrix at HP Software Support Online.

Hardware and Software Requirements

These requirements are listed in the HP Operations Manager Dependency Mapping Automation Installation and User's Guide. Before installing HP Operations Manager Dependency Mapping Automation, make sure that your system meets these minimum requirements.

HPOM Patches

This section describes the HPOM patches you must install on the HPOM host system.

Patches are available from the following web site:

http://support.openview.hp.com/selfsolve/patches

Known Problems, Limitations, and Workarounds

Runtime

• Documentation Includes Outdated Information

  The online help and the screenshots in the HPOM DMA documentation have not been updated for patch DMA_00001.

  Solution

  The contents of the HPOM DMA Installation and User’s Guide, Getting Started Guide, and Extensibility Guide have been updated and contain the most current information on support for UCMDB 9.0x.

• UI Launch

  The following limitations apply to UI launch of UCMDB 9.0x:

  • Patch DMA_00001 does not add an entry for UCMDB 9.0x to the UI Launch configuration dropdown list in the Drilldown section of the Connection page of the HPOM DMA console.

    Solution: If you want to configure HPOM DMA for the UI launch using a UCMDB 9.0x system, select UCMDB 8.0.

  • The following UI launch tools do not work with UCMDB 9.0x:

    • Universal CMDB > UCMDB Node UI Launch > Show Change Report

    • Universal CMDB > UCMDB Service UI Launch > Show Change Report in UCMDB

    Solution: The corresponding reports are not available in UCMDB 9.0x. There is no workaround.

  • Users must now authenticate themselves at least once before launching UI tools.

    Solution: When starting a UI launch tool for the first time, you must submit your user name and password before the UCMDB 9.0x web application starts.

• UCMDB and BAC UI launch tools cannot be started on Linux systems (QCCR1A101841)

  The UCMDB and BAC UI launch tools open an empty browser window when started on the HPOM on Linux server in a 64-bit version of Mozilla.

  Solution

  Launching the BAC and UCMDB tools has certain limitations regarding platform and web browser support. With BAC and UCMDB 7.50 and 8.00, Internet Explorer on a Windows system works best. For detailed information about supported client platforms and browser versions, see the BAC and UCMDB documentation.

• HPOM DMA on HPOM 9.0x only. The removal of HPOM DMA breaks opcsvcdisc (QCCR1A102614)

  HPOM 9.00 for UNIX and Linux do not have a dependency on HPOvJsec and HPOvJbbc. Thus the HPOM DMA uninstallation also removes these components, which prevents the Service Discovery Server (opcsvcdisc) from starting.

  Solution

  After removal of HPOM DMA, reinstall HPOvJsec and HPOvJbbc from the HPOM DMA installation medium. On Linux you may use the following commands:

  cd <mount directory>
rpm -i packages/HPOvJbbc-*rpm packages/HPOvJsec-*rpm

• HPOM DMA on HPOM for Solaris only. Launching HPOM DMA on Solaris fails (QCCR1A101761)

  Launching the HPOM DMA console on OVO 8.xx and HPOM 9.xx for Solaris fails with the following error:

  java.lang.NoClassDefFoundError: javax/servlet/jsp/tagext/TagExtraInfo

  Solution

  Use a non-Solaris proxy server to host the HPOM DMA 8.20 web application. On the HPOM for Solaris management server, you only need to install the Smart Message Mapper (and the web services). This scenario is similar to installing HPOM DMA on OVO for UNIX 8.xx PA-RISC.

  Perform the following steps:

  1. Install the HPOM for Solaris host system:

     • OVO 8.xx for Solaris: install Accessories Patch ITOSOL_00710, the Smart Message Mapper, and the web services

     • HPOM 9.xx for Solaris: install the Smart Message Mapper only

  2. Install HPOM DMA without the Smart Message Mapper on a remote HPOM DMA host system (preferably a Windows system).

  3. Perform the required post-installation steps on the Solaris and Windows host systems as described in the Installation and User’s Guide.

  4. Perform a synchronization.

• Synchronization does not stop when BAC or UCMDB is unavailable (QCCR1A93391)

  If BAC or UCMDB are unavailable when you start a synchronization, the console indicates that the synchronization is running successfully. The Start Synchronization button remains disabled. However, the following messages are logged in the synchronization log file:

  Jun 5, 2009 4:05:05 PM INFO ========== Starting synchronization on 6/5/09 at 4:05 PM ========== 
  Jun 5, 2009 4:05:05 PM INFO There are 59 days until your licence expires. 
  Jun 5, 2009 4:05:05 PM INFO Default sync task settings loaded successfully. 
  Jun 5, 2009 4:05:06 PM WARNING Exception caught in controller: java.net.ConnectException: Connection refused: connect 
  Jun 5, 2009 4:05:06 PM INFO ========== Synchronization successfully completed on 6/5/09 at 4:05 PM ==========
  

  Solution

  Start BAC or UCMBD and restart the synchronization:

  1. Log out of the HPOM DMA console.

  2. Stop Tomcat:

     ovc -stop ovtomcatB

  3. Start BAC or UCMDB.

  4. Start Tomcat:

     ovc -start ovtomcatB

  5. Log on to the HPOM DMA console and restart the synchronization.

• Synchronization does not stop when wrong password is entered (QCCR1A93522)

  If you specify an incorrect user password for the connection to UCMDB or BAC, the console indicates that the synchronization is running successfully. The Start Synchronization button remains disabled. The synchronization log file indicates "Synchronization successfully completed".

  Solution

  Log out of the HPOM DMA console and restart Tomcat.

  1. Log out of the HPOM DMA console.

  2. Restart Tomcat:

     ovc -restart ovtomcatB

  3. Log on to the HPOM DMA console and restart the synchronization.

• Multibyte Characters Cannot be Stored in the Database

  BAC and UCMDB version 7.50 cannot store multibyte characters in the UCMDB database. Synchronization of localized data is not currently supported.

  Solution

  This is a limitation that is currently being addressed. Support of synchronization of localized data will be available in an update of BAC and UCMDB.

  
  

• Connection page: problem with BAC or UCMDB drop-down list in Internet Explorer (QCCR1A92577)

  When you resize the Connection page in Internet Explorer, the drop-down list for selecting the BAC or UCMDB version for the drilldown tools moves to the top of the page.

  Solution

  Use Mozilla version 3.6 or higher.

  
  

• Running HPOM DMA with clustered HPOM management servers (QCCR1A91636)

  Tomcat requires a server certificate from HPOM to secure the communication with the management server. The HPOM server name is stored in the certificate and you must use exactly the same name when specifying the connection to HPOM.

  When connecting to a clustered HPOM management server, you cannot use the existing HPOM certificate that is stored in the Tomcat keystore. You need a new certificate that has been issued for the virtual hostname.

  Solution

  Perform the following steps to delete and recreate the existing server certificate. (The steps are examples for UNIX systems only. Use the corresponding commands on Windows systems.) In all steps, when asked for the password, type the default password changeit:

  1. Delete the existing certificate stored in the Tomcat keystore, type:

     /opt/OV/nonOV/jre/b/bin/keytool -delete -alias ovtomcatb

  2. Check whether the certificate with the alias ovtomcatb is indeed deleted, type:

     /opt/OV/nonOV/jre/b/bin/keytool -v -list -alias ovtomcatb -keystore /var/opt/OV/certificates/tomcat/b/tomcat.keystore

  3. Regenerate the certificate, for example:

     /opt/OV/nonOV/jre/b/bin/keytool -genkeypair -alias ovtomcatb -dname "CN=<server_name>, OU=OpenView, O=Hewlett-Packard, L=Palo Alto, ST=California, C=US" -keystore /var/opt/OV/certificates/tomcat/b/tomcat.keystore -validity 7200

     Where <server_name> is the virtual hostname.

  4. Check again whether the certificate is installed, type:

     /opt/OV/nonOV/jre/b/bin/keytool -v -list -alias ovtomcatb -keystore /var/opt/OV/certificates/tomcat/b/tomcat.keystore

  5. Restart Tomcat, type:

     ovc -restart ovtomcatB

  6. Connect to the clustered management server using the virtual hostname as specified in the certificate.

Use the same procedure to update the server certificate after having changed the hostname of the management server.

Support

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:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Submit enhancement requests online
• Download software patches
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

Legal Notices

Warranty

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.

Restricted Rights Legend

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 Notices

©Copyright 2007-2011 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
AMD and the AMD Arrow symbol are trademarks of Advanced Micro Devices, Inc.
Google™ and Google Maps™ are trademarks of Google Inc.
Intel®, Itanium®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.
iPod is a trademark of Apple Computer, Inc.
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.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

Acknowledgements

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product includes software developed by the Jaxen Project (http://jaxen.org/).

This product includes software developed by the JDOM Project (http://www.jdom.org/).

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).

This product includes Sentry Spelling-Checker Engine, which is Copyright © 2000 Wintertree Software Inc.

This product includes an interface of the 'zlib' general purpose compression library, which is Copyright © 1995-2002 Jean-loup Gailly and Mark Adler.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

For information about open source license agreements, refer to the documents located in the directory on the product installation media:

<dvd-mountpoint>/License

These documents are also available after installation under <InstallDir>/license_agreements on the HPOM DMA host system.

To view open source code, see the <InstallDir>/nonOV/wiseman/a/src directory on the HPOM DMA host system.

The Open Source Software product packages used by HPOM DMA are as follows:

• WisemanA (wiseman_src.zip)
• JAXB (jaxb-src.zip)
• JAX-WS (jaxws-src.zip)