HP Universal CMDB Readme

for the Windows and Linux operating systems

Software version: 9.00

Publication date: June 2010

This file provides information about HP Universal CMDB (UCMDB) version 9.00.

Documentation Updates
HP Universal CMDB 9.00 Files/Components
What's New
System Requirements
Installation
Upgrade
Adapter Upgrade
Notes and Limitations
Multilingual Support
HP Software Support
Legal Notices

Documentation Updates

The first page of this 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, visit this URL: HP Software Product Manuals

To retrieve a document, select the:

Product name.
Version list.
Operating System.
Preferred Language.
Document title.
Click Open or Download.

You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.

HP Universal CMDB 9.00 Files/Components

There are two DVDs for version 9.00: HP UCMDB 9.00 Windows and HP UCMDB 9.00 Linux. Each DVD includes the following files/components:

HPUCMDB_Server_9.00.exe. The full installation of the version 9.00 HP UCMDB Server for the Windows platform (HP UCMDB 9.00 Windows DVD only).
HPUCMDB_Server_90.bin. The full installation of the version 9.00 HP UCMDB Server for the Linux platform (HP UCMDB 9.00 Linux DVD only).
HPUCMDB_DataFlowProbe_90.exe. The installation of the version 9.00 Data Flow Probe.
Documentation files:
whatsnew.html. Accessed through the Help menu in HP Universal CMDB.
readme.html. This file.
Product Feature Movies folder. This folder includes a collection of movies demonstrating some of the major features available in this release.
The HP Universal CMDB Deployment Guide PDF, also located in the following directory: C:\hp\UCMDB\UCMDBServer\deploy\ucmdb-docs\docs\eng\pdfs\

What's New

Access a list of new features through the What's New link in the Help menu of HP Universal CMDB.

System Requirements

For a list of system requirements, see the "HP Universal CMDB Support Matrix" chapter in the HP Universal CMDB Deployment Guide PDF.

Installation

For details on installation of HP Universal CMDB and the Data Flow Probe on a Windows or Linux platform, see the HP Universal CMDB Deployment Guide PDF.

Discovery and Integration Content Pack 6.00 is included with HP UCMDB 9.00. There is no need to install it separately.

Upgrade

For details on the upgrade procedure from version 8.0x to 9.00, see "Upgrading HP Universal CMDB to Version 9.00" in the HP Universal CMDB Deployment Guide PDF.

For details on the upgrade procedure from version 7.0x to 8.0x, refer to the version 8.0x deployment guide.

Adapter Upgrade

For all out-of-the-box adapters: if you modified an adapter configuration in a previous version, it is highly recommended that you save all adapter files from that version, and redo the modifications on the adapter files of version 9.00.

For all non out-of-the-box adapters: you must redeploy the adapters in version 9.00. For details, see "Package Manager" in HP UCMDB Administration Guide.

Important: All adapters must be compatible with the new class model (BDM). If you made changes to existing out-of-the-box adapters, you must make the same changes to the adapter files in the 9.00 version. That is, do not copy files from version 8.04 and overwrite the files in version 9.00.

Notes and Limitations

This section includes the following topics:

Installation
Upgrade
HP UCMDB
LDAP
Data Flow Management
Integration
Integration Users
Discovery and Integration Content

Installation

You cannot change the default password of users during installation (for example, the system administrator or the integration user). Use the JMX console to change the password.
High availability is not supported on the Linux environment.
When running high availability on a cluster, you can log in to the Server Management Tool only on the server that the tool is initially run on.

Upgrade

The following resources will not be upgraded during the upgrade process:
Snapshots that are scheduled to run at a certain interval (for example, once a day).
LDAP server settings. You must manually reconfigure the LDAP connection configuration after upgrading to 9.00 (user mappings are upgraded).

HP UCMDB

Only an integration user can connect to the UCMDB through the UCMDB Java API set. A connection attempt by other types of users may cause errors, even when using LDAP verification.
System Health is not available with version 9.00, but will be added in version 9.01.
In Modeling Studio, the Changed during or Unchanged during operators for date attributes are supported only if you change the query to ACTIVE. By default, once these operators are added, the query is automatically set to NOT ACTIVE.
In the Reports module, you cannot drag a report from the tree and drop it on the canvas to open it. You must double-click the report or select Open Report from the toolbar.
In IT Universe Manager, when you try to create an empty model CI (a CI of type Business Service or CI Collection), an error is generated.
In the Reports module, the search functionality (Find Next, Find Previous, Highlight) does not work properly if you change the query to ACTIVE (the default is NOT ACTIVE).
When working with federated CITs in the Modeling Studio, the Add Related Query Node wizard does not identify CITs with instances. If the Show only CITs with instances check box is selected, no tree is displayed. If you clear the Show only CITs with instances check box, a CIT tree is displayed with zero instances showing for all CITs, even though there may be instances for some CITs.
In the Users and Roles module, the Update recipient link in the Details tab does not work.
The Get Related CIs Report in IT Universe Manager is not available in version 9.00. To work around this limitation, export the results of the related CIs in text mode.
In IT Universe Manager, the Export Data to File option does not work in Text mode for CSV, Excel, or XML reports from the View Results tab. You can export data to a PDF file from there. In the Related in View and Related in DB tabs, all the export options work.
In the CI Lifecycle module, the Filter option is not supported and the Clear Filter button is not active.
The Direct Links functionality to a perspective-based view is not supported.
When deleting a template in the Modeling Studio, there is no option to detach the dependent views from the template.
When deleting a template in the Modeling Studio, the TQL query on which it is based is not automatically deleted.
When deleting a perspective in the Modeling Studio, there is no option to detach the dependent views from the perspective.
When deleting a perspective-based view in the Modeling Studio, the TQL query on which it is based is not deleted.
The View Snapshot and View Statistics functionality is missing in the View Change report.
In the CI Type Manager, you cannot remove CITs, even if they have no instances.
When accessing HP Universal CMDB through the IIS Web server, the JMX Console cannot be accessed through the IIS Server URL. You must access the JMX Console directly through the UCMDB server URL.
The UCMDB Server Configuration Wizard fails when trying to connect to schemas created manually or by the SQL script. To work around this limitation, perform the following procedure:
Run the UCMDB Server Configuration Wizard. For details, see "Access the UCMDB Server Configuration Wizard" in the HP Universal CMDB Deployment Guide PDF. In the CMDB Schema dialog box, select Connect to an existing schema.

Enter the necessary connection information. Click OK.

Ignore any error messages.

Close the Configuration Wizard by clicking Cancel.

Verify that the cmdb.conf file exists in the conf directory.

Start the HP Universal CMDB Server. For details, see "Starting and Stopping the Server" in the HP Universal CMDB Deployment Guide PDF.

The Server does not start and throws an exception.

Run the Configuration Wizard again.

Input the missing parameters again.

This time Configuration Wizard finishes successfully.

Start the HP Universal CMDB Server as normal.

LDAP

Configuring LDAP for Active Directory: The following settings must be added to Infrastructure Settings (Administration > Infrastructure Settings):
In the LDAP General category, change the value of Enable User Synchronization to true.
Change the value of LDAP server URL to ldap://LDAP-SERVER:389/DC=consult,DC=example,DC=com??sub;
Change the value of Users filter to (&(sAMAccountName=*)(objectclass=user));
In the LDAP General Authentication category, change the value of Distinguished Name of Search-Entitled User to CN=AD Connector,CN=Users,DC=consult,DC=example,DC=com;
Enter the password for the search-entitled user.
In the LDAP Group Definition category, change the value of Groups base DN to CN=Users,DC=consult,DC=example,DC=com;
Change the value of Groups search filter to (|(objectclass=groupOfNames)(objectclass=group)(objectclass=groupOfUniqueNames)(objectclass=groupOfUrls)(objectclass=access Group)(objectclass=accessRole));
Change the value of Root groups base DN to CN=Users,DC=consult,DC=example,DC=com;
Change the value of Root groups filter to (|(objectclass=groupOfNames)(objectclass=group)(objectclass=groupOfUniqueNames)(objectclass=groupOfUrls)(objectclass=access Group)(objectclass=accessRole));
In the LDAP Options for Classes and Attributes category, change the value of Group class object to group;
Change the value of Groups member attribute to member;
Change the value of UUID attribute to sAMAccountName;
Change the value of Users object class to user
Set Remote users repository mode to Enable.
All other parameters should be left at their default value.

Data Flow Management

Enable SSL Between UCMDB Server and UCMDB Data Flow Probe with Mutual Authentication: In version 9.00, this functionality is not supported, but will be added in a future release.

Instead, you should use basic authentication. For details, see "Enable SSL on the Data Flow Probe with Basic Authentication" in HP Universal CMDB Data Flow Management Guide.

When the Data Flow Probe is first installed, executing Check credential (for example, Data Flow Management > Data Flow Probe Setup > Domains and Probes pane > Credentials > SQL Protocol > right-click a credential and choose Check credential) may fail with the following error: java.lang.Exception: Traceback (innermost last): File "NNM_Integration_Utils". To work around this problem, restart the Probe.
The name of a discovered CIT sometimes appears in red in the Statistics Results pane (Data Flow Management > Discovery Control Panel > Details tab). This has no affect and can be ignored.
When a Probe Gateway works with two Probe Managers, the request to receive the communication log from the system sometimes fails. Instead, you can retrieve the log file from the relevant Probe Manager file system.
When running the J2EE or Database wizard, you cannot upload jar files from the Wizard to the Probe. You must manually copy the files to the Probe file system and restart the Probe.

Integration

The status of a population job is displayed as Running even though the job has not yet been scheduled.
Sometimes, when a CI is ignored during reconciliation, another CI that needs the first CI for identification purposes is incorrectly inserted into the CMDB. This does not occur when the CIs are connected by a composition link.
TQL queries that contain subgraphs or compound links do not retrieve data for those items, when using the UCMDB 9.0x adapter.
If CIs are merged or deleted during population from another UCMDB, reconciliation data cannot be received for those CIs and a population job containing those CIs may fail. Rerun the job to work around the issue.
You cannot edit the values of attributes that are configured to be retrieved from both an external data repository and UCMDB during federation.
Multiple CIs from different integration points are not merged when the CIs are identified using root_container.
When defining a new integration point in Integration Studio, if the name contains illegal characters (for example, a period), an error message is displayed and the information in the Create New Integration Point dialog box is lost.
The link to a federated CI in an exported report fails to return the user to UCMDB.
Virtual relationships for federation must be mapped in the orm.xml file in reverse order, in cases where the first end is a federated CIT and the second end is a UCMDB CIT. This limitation does not occur for population jobs.
TQL calculation fails if attribute conditions that are defined on a federated node have not had their names mapped in the orm.xml file.

Integration Users

When syncing with other UCMDB servers (during the data population and federation flows), you must supply UCMDB integration user credentials for integration to work correctly. That is, you do not provide LDAP user credentials, even though LDAP authentication may be turned on.
You can create a dedicated user for integrations between other products and UCMDB. This user enables a product that uses the UCMDB client SDK to be authenticated in the server SDK and execute the APIs.

To create an integration user:

Launch a Web browser and enter the server address, as follows: http://<UCMDB Server Host Name or IP>:8080/jmx-console.

You may have to log in with a user name and password.

Under UCMDB, click UCMDB:service=Security Services to open the JMX MBEAN View page.
Locate the CreateIntegrationUser operation. This method accepts the following parameters:
customerId. The customer ID.
username. The integration user's name.
password. The integration user's password.
dataStoreOrigin. The name of the product that is going to use this integration user.

The following operations are useful for integration user management:

DeleteIntegrationUser. Deletes the given integration user.
ExportIntegrationUser. Exports the integration user to an XML file in the given path (on the server machine).
getIntegrationUser. Displays the integration user information.
changeIntegrationUserPassword. Changes the integration user's password.
canUserAuthenticate. isIntegrationUser is true: can the integration user authenticate with the given credentials?

Note:

The integration user is per customer. To create a stronger integration user for cross-customer usage, use a systemUser with the isSuperIntegrationUser flag set to true. Use the systemUser methods (createSystemUser, removeSystemUser, showAllSystemUsers, changeSystemUserPassword, canSuperIntegrationUserAuthenticate, and so on).

There are two out-of-the-box system users; it is recommended to change their passwords after installation using the changeSystemUserPassword method.

sysadmin/sysadmin
UISysadmin/UISysadmin (This user is also the Super Integration User SuperIntegrationUser).

If you change the UISysadmin password using changeSystemUserPassword, you must execute the following method: in the JMX Console, locate the UCMDB-UI:name=UCMDB Integration service. Run setCMDBSuperIntegrationUser with the user name and new password of the integration user.

Discovery and Integration Content

Previously-discovered Layer 2 topology is not upgraded to version 9.00, so you must rediscover this topology. You can either delete existing Layer 2 links manually or rely on the aging mechanism to delete them.
Siebel discovery. If the Data Flow Probe is installed on a 64-bit machine on a Windows platform, place the ntdll.dll, MSVCR70.DLL, and msvcp70.dll drivers together with the Siebel drivers in the Siebel driver folder on the Probe machine. You enter details of this folder in the Siebel set of credentials (Path to Siebel Client). For details, see "Siebel Gateway Protocol" in the Discovery and Dependency Mapping Guide.

These drivers usually exist on a 32-bit machine and can be copied to the 64-bit machine.

SAP discovery. If the Data Flow Probe is installed on a 64-bit machine on a Windows platform, place the standard librfc32.dll and sapjcorfc.dll drivers under the Windows installation folder (for example, C:\windows\SysWOW\).

Place the msvcp71.dll and msvcr71.dll drivers under the Probe installation directory: C:\hp\UCMDB\DataFlowProbe\content\dll\.

These drivers usually exist on a 32-bit machine and can be copied to the 64-bit machine.

To properly discover a Veritas Cluster, go to the CI Type Manager in the Modeling Studio, select Relationships, select the ownership relationship and add the is_owner Boolean attribute to it.
If the Data Flow Probe's My SQL database shuts down or encounters an error, the Probe may appear to be disconnected. Restore the My SQL database then restart the Data Flow Probe.
When using the NTCMD credentials to run discovery, if the following error is displayed, the Windows machine is configured to prevent interactive services from running:

The xCmd Service service is marked as an interactive service. However the system is configured to not allow interactive services. This service may not function properly.

To avoid this error, open the Registry Editor and edit the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows Set the NoInteractiveServices property to 0.

Multilingual Support

For compatibility purposes, Integration Points names and Data Flow Management job names can include only English letters, numbers, and the underscore character (_).
Because the maximum string length for many UCMDB parameters is defined and documented in bytes, the real acceptable value length is shorter when multi-byte or language-specific characters are used. For example, Asian characters with UTF-8 encoding use 3 bytes, whereas some European language characters use 2 bytes.
When exporting a report or other data which contains language-specific characters to a PDF file, multi-byte characters (such as Japanese, Chinese, Korean, and so on) are not displayed in the PDF file.
Following an upgrade from version 8.04 to 9.00, language-specific characters in a query node name appear as gibberish if they are not supported by the system console encoding.
Population jobs that use the UCMDB 9.0x adapter fail if the remote integration query name contains multi-byte characters. For compatibility purposes, integration queries should not contain multi-byte characters in their names.
XML files cannot be edited in Adapter Management when the user interface uses a Chinese, Korean, or Spanish locale.
On localized hosts, Data Flow Probe Uninstaller may leave product files and folders on the disk.
Modeling Studio includes two View folders, one in English and one in the language of the server locale. After a view is created in Modeling Studio, the relevant query is created in the localized View folder. For predefined views, relevant queries are stored in the English View folder.
In Enrichment Manager, required attributes in the Node Definition dialog box are not marked in bold for the Japanese, Chinese, and Korean versions.
If a report is attached to email, the report's file name changes to gibberish or other characters if the original file name includes multi-byte characters.
The content and name of a query or view could be damaged during export to the XML format if the query or view includes multi-byte characters that are not supported by the host on which the operation is being performed. To work around this issue, place any relevant views and queries in a package and export or import them together with their package.

HP Software Support

You can visit the HP Software support web site at:

www.hp.com/go/hpsoftwaresupport

This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

HP 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:

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

To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.

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: Access levels.

To register for an HP Passport ID, go to: HP Passport Registration .

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 2005 - 2010 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.

Java™ is a US trademark of Sun Microsystems, Inc.

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 Apache Software Foundation (http://www.apache.org/licenses).

·       This product includes OpenLDAP code from OpenLDAP Foundation (http://www.openldap.org/foundation/).

·       This product includes GNU code from Free Software Foundation, Inc. (http://www.fsf.org/).

·       This product includes JiBX code from Dennis M. Sosnoski.

·       This product includes the XPP3 XMLPull parser included in the distribution and used throughout JiBX, from Extreme! Lab, Indiana University.

·       This product includes the Office Look and Feels License from Robert Futrell (http://sourceforge.net/projects/officelnfs).

·       This product includes JEP - Java Expression Parser code from Netaphor Software, Inc. (http://www.netaphor.com/home.asp).

If you have any comments or suggestions regarding this document, please send them by e-mail to SW-Doc@hp.com.