HP Universal CMDB Readme

This file provides information about HP Universal CMDB (UCMDB) version 9.03. For information on UCMDB 9.02, click here. For information on UCMDB 9.01, click here. For information on UCMDB 9.00, click here.

Note: When viewing this file in Internet Explorer 8, numbered or alphabetical lists may appear corrupted.

Documentation Updates

To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals

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.03 Files/Components

HPUCMDB_Server_903.exe. The installation of the version 9.03 HP UCMDB Server for the Windows platform.

HPUCMDB_Server_903.bin. The installation of the version 9.03 HP UCMDB Server for the Linux platform.

HPUCMDB_DataFlowProbe_903.exe. The installation of the version 9.03 Data Flow Probe for the Windows platform.

HPUCMDB_DataFlowProbe_903Linux.bin. The installation of the version 9.03 Data Flow Probe for the Linux platform (for integrations only).

Discovery and Integration Content Pack 8.00 is included with UCMDB version 9.03. There is no need to install it separately.

Note: If you are upgrading from UCMDB version 9.02 with Content Pack 7.00, the Content Pack is not automatically upgraded to Content Pack 8.00, nor is it a requirement. However, if you do want to upgrade to Content Pack 8.00, you must do this manually after completing the UCMDB 9.03 upgrade.

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.

Note: This PDF is also located in the following directory: C:\hp\UCMDB\UCMDBServer\deploy\ucmdb-docs\docs\eng\pdfs\

System Requirements

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

In the Server Database Requirements section, the following additional Microsoft SQL Servers are supported for working with HP Universal CMDB:

UCMDB Server Installation

Choose one of the following procedures to install the UCMDB Server, according to which version is currently installed (if at all):

Database Release
Version	System Type	Service Pack
Microsoft SQL Server 2005 Enterprise Edition	32 BIT	Service Pack 4
Microsoft SQL Server 2005 Enterprise Edition	64 BIT	Service Pack 4

Current Installation: No version is installed. Install according to the Operating System:

Windows platform: Install HP UCMDB 9.03.
Extract UCMDB_00041.zip to a temporary directory. Then launch HPUCMDB_Server_903.exe and follow the instructions in "HP Universal CMDB Installation on a Windows Platform" in the HP Universal CMDB Deployment Guide PDF.

Linux platform: Install HP UCMDB 9.03.
Extract UCMDB_00042.zip to a temporary directory. Then launch HPUCMDB_Server_903.bin and follow the instructions in "HP Universal CMDB Installation on a Linux Platform" in the HP Universal CMDB Deployment Guide PDF.

Current Installation: HP UCMDB 8.x or HP UCMDB 7.x: For details on the upgrade procedure, see "Upgrading HP Universal CMDB from Version 8.0x to Version 9.03" in the HP Universal CMDB Deployment Guide PDF.

Current Installation: HP UCMDB 9.02/9.01/9.00:

Stop the UCMDB 9.0x server before starting the 9.03 installation.

Run the relevant version of the UCMDB 9.03 installer, as described above.

When selecting the installation folder, select the existing 9.0x installation folder.

When selecting the installation type, select Update from 9.0x.

Complete the installation process.

Start up the version 9.03 server. For details on server status, see "HP Universal CMDB Services" in the the HP Universal CMDB Deployment Guide PDF.

Data Flow Probe Installation

Note: Any configurations that were made manually on the Data Flow Probe (such as SSL configurations: certificates, proxy settings, and so on), are not upgraded when you install a new version of the Data Flow Probe.

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.03.

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

Note: All adapters must be compatible with the new 9.0 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.03 version. That is, do not copy files from version 8.0x and overwrite the files in version 9.03.

Notes and Limitations

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.

When running in High Availability mode, you must log on to the Server Management Tool using the address of the active server.

When the Data Flow Probe is configured to be installed in separate mode, so that Manager and Gateway processes are running on separate machines, the following additional configuration is required on Discovery Flow Probe Manager's machine:

Stop the Manager process (if it is already running).

Open <UCMDB installation>\DataFlowProbe\conf\
DiscoveryProbe.properties and locate the following code:


# The Domain name appilog.collectors.domain = ${DefaultDomain}

Change this code to contain the Data Flow Probe's actual domain. For the default domain, DefaultDomain, this code should look as follows:


# The Domain name appilog.collectors.domain = DefaultDomain

Save DiscoveryProbe.properties and start the Manager process.

Upgrade

During the UCMDB 9.03 upgrade, manually imported customer certificates are lost, and must be reimported after the upgrade. It is strongly recommended, before you start the upgrade procedure, to back up C:\hp\UCMDB\UCMDBServer\bin\jre\lib\security\cacert and restore it after performing the upgrade.

After upgrading, the Data Flow Probe will run population jobs immediately for active integration points, even if the integration is not scheduled. If you do not want the integration to run, disable the integration before running the upgrade from 9.0x.

Upgrading from UCMDB versions with Content Pack 8.00 to UCMDB 9.03: To view individual package documentation from the Data Flow Management modules, you must redeploy Content Pack 8 after upgrading to UCMDB 9.03.

After upgrading to UCMDB 9.03, if a job's time zone setting was other than "Discovery probe time zone", it must be reconfigured to the correct time zone.

When upgrading from 8.0x to 9.03, you need to manually copy the encryption key from 8.0x to 9.03. UCMDB uses the encryption key to encrypt credentials information and to send sensitive credentials information to probes. This encryption key is not stored in the database, but on the file system due to security reasons. For details on the encryption key and protecting credentials information, see "Data Flow Probe Hardening" in the HP Universal CMDB Deployment Guide PDF.

Proceed with the following steps:

Copy the encryption key from the UCMDB 8.0x server located at following path: C:\hp\UCMDB\UCMDBServer\root\lib\server\discovery\key.bin

After installing UCMDB 9.03 (step 7 in "Upgrade HP Universal CMDB Summary" in the "Upgrading HP Universal CMDB from Version 8.0x to 9.03" chapter of the HP Universal CMDB Deployment Guide PDF), replace the C:\hp\UCMDB\UCMDBServer\conf\discovery\key.bin file with the file you copied in the previous step.

Continue with step 8 ("Run the Upgrade Tool").

After upgrading from version 8.06 to 9.03, you must restore the SMTP configuration before creating new scheduled reports jobs.

When upgrading from previous versions of UCMDB, if you enabled Update/View permissions in the Data Flow Management modules, but did not enable the Execute permission, you must manually re-enable those modules by selecting the Execute/Update permission for the relevant users. For the Adapter Management, the permission should be set to 'Update'.

LDAP server settings are not upgraded during the upgrade process. You must manually reconfigure the LDAP connection configuration after upgrading to 9.03 (user mappings are upgraded).

When working with Microsoft SQL Server, the CMDB collation and the SQL Server collation must be the same in order for the upgrade to run properly.

When upgrading from 9.0x to 9.03, integration jobs that were scheduled as "Daily" become scheduled as "Day of the month" with no day selected. As long as the Scheduler is not opened, the job continues to run every day as previously scheduled. If you open the dialog box, you need to select Cron Expression so that the job continues to run as defined in the previous version.

HP UCMDB

The UCMDB server may not start up properly when the Max CIs in view supported to rediscover setting in the Infrastructure Settings Manager is set to very high values.

When creating a cron expression in the Job Definition Scheduler, the time and date must be in the future. If the current or a past date is defined it will cause an error.

In the Security Manager, in the Customize tab, there is an Access to SDK option under General Actions in the Resources pane. This option grants users permission to access the SDK.

When Delete permission is assigned for a CIT, all of its subclasses can also be deleted.

When Create permission is assigned for a CIT, it can be updated and all of its subclasses can also be created.

When generating a direct link using an embedded link, the link opens the user interface with distortions.

When searching for a string in a report, the search results only include exposed items in the report. Strings in collapsed nodes are not found.

In Enrichment Manager, Impact Analysis Manager. And CIT Manager, when you select several CITs and their connecting relationships and select Export Map to Image with the Selected Object Only option, the resulting image does not display the relationship names.

In Impact Analysis Manager, if you select an Impact rule and try to delete it, and then select Cancel in the Confirm Deletion dialog box, the Impact rule is deleted.

When exporting an Enrichment rule or Impact rule to XML, you can export the rule itself from the Export to XML dialog box, but the underlying TQL query of the rule should be exported using the JMX console as follows:

Select UCMDB Service = TQL Services and select the exportTqlWrappedAsPattern method.

Enter the query name as the patternName value and click Invoke.

Rename the created xml file to queryName.xml.

When working in Linux, no error message appears when you attempt to send a report to an email server that is not working.

It is possible to edit CITs even if they are assigned the READ_ONLY_CLASS qualifier.

The Screen Capture tool cannot capture a screenshot when the UCMDB browser is running in a multi-display environment.

In the CI Lifecycle module, when you select a CI in the list and perform an operation, such as Postpone Deletion, the next CI in the list is sometimes selected.

In the Scheduler, when you select Run an Enrichment Rule in the Actions Definition dialog box, Enrichment rules that have been deleted still appear in the list of available rules.

The Clear Filter button in the Job List dialog box (for scheduled reports and scheduled snapshots) does not work properly.

When creating a new Impact rule in Impact Analysis Manager, the created Impact rule can be run within IT Universe Manager even if the UCMDB check box on the Impact Rule Groups page of the wizard is not selected.

If you create an Enrichment rule to update an attribute value with a string exceeding the maximum character limit, no error message is displayed and the attribute value is not updated.

If you encounter either a Couldn't connect to database or Error getting connection from pool error message in the UCMDB error.log file (located in the C:\hp\UCMDB\UCMDBServer\runtime\log\ directory), do the following:

Open the connection_pool.conf file (located in the C:\hp\UCMDB\UCMDBServer\conf\ directory).

Note: If your system was upgraded from UCMDB version 9.01 or 9.00, create the file using a text editor.

Add or unmark the following parameter:

maxPoolSize=100

The Connection_pool.conf file configures properties related to the database connection pool. Its default content is:


# DB Connection pool defaults. #maxPoolSize=100 #minPoolSize=2 #maxWaitForConnectionSec=10 # 0=FAIL, 1=BLOCK, 2=GROW #whenExhaustedAction=1

You can configure:

minimum and maximum number of connections in the pool.

whenExhaustedAction - what to do when requesting a new connection and there are no free connections in the pool. Valid values are fail, wait (BLOCK), or add new connection to pool (GROW).

maxWaitForConnectionSec - the maximum time to wait, when whenExhaustedAction=BLOCK.

After restarting the server, it may not be possible to log in for several minutes even though the login page is available.

System Health is not available with version 9.03, but will be added in a future version.

When you generate a direct link from IT Universe Manager to a perspective based view, the link does not work.

The dbtool consistency tool runs without any introductory messages. For example, users are not given tips about backing up data or stopping the Server before running the tool. Furthermore, schemas affected by the tool are not listed.

When directly embedding UCMDB applets using a direct link, you can encrypt the password contained within the direct link using the JMX console as follows:

Launch your Web browser and enter the following address: http://<server_name>:<port number>/jmx-console, where <server_name> is the name of the machine on which HP Universal CMDB is installed.

Under UCMDB-UI, locate UCMDB Integration.

Under encryptString, enter your password in the Value box.

Click Invoke to view the encrypted string.

The new retrieveAllActiveUsers() method is now available in the UCMDB-UI:name=UCMDB Integration section of the JMX console. This is equivalent to the getAllActiveUsers() method that was available in UCMDB version 8.0x.

When viewing HP Universal CMDB online documentation in Internet Explorer 8, numbered or alphabetical lists may appear corrupted.

(In the UCMDB_JavaAPI) In cases where an attribute type was of type string or integer list, the Attribute#getDefaultValue() method, which had returned strings in XML format, now returns a collection of string or integer objects.

In the Views tab in the Security Manager, when the Delete permission is set and a view is deleted, the query on which the view depends is also deleted.

When the UCMDB Server is deployed on Windows 2008 and User Account Control (UAC) is enabled, the server does not start or stop when you click the Start menu icons.

In the case where the server was installed properly, but the wrapper cannot start it for lack of permissions, use the following workaround:

Right-click C:\hp\UCMDB\UCMDBServer\bin\wrapper.exe to open the wrapper.exe properties. In the Compatibility tab, under Privilege Level, select Run this program as an administrator. Alternatively, this can be accomplished by setting a registry entry.

Stopped customers do not show in the server management tool. To start a customer, use the JMX console.

Modeling

User is unable to to create CI instances of CI types marked as federated.

User without admin permissions are able to create a relationship between two CIs.

It is not possible to import calculated relationships to the CI Type Manager from an XML file.

It is not possible to paste values in a list format into the Value field of the Attribute tab in the Query Node Properties dialog box when the In operator is selected.

The Show Differences option for Configuration Document CIs is not documented in the IT Universe Manager shortcut menu. When two such CIs are selected, the option is active. Selecting it displays the differences between the two configuration documents in a popup window.

When applying perspectives to a CI in the Get Related CIs pane in IT Universe Manager, the results do not display related CIs that are arranged in a hierarchy. Only related CIs on the same layer as the selected CI are displayed.

In the Modeling Studio, it is not possible to create more than one pattern-based model of the same CI type, based on the same query. When you try to create a new one, it overwrites the existing one.

In the Modeling Studio, any changes made to one pattern-based model are saved in all pattern-based models based on the same query.

In the Query Node Properties dialog box in Modeling Studio, the Up and Down buttons in the toolbar of the Attributes tab sometimes do not work properly when the NOT operator is selected for one or more of the specified conditions.

The Must and Weight fields appear in the New CI and Insert Relationship dialog boxes in IT Universe Manager in the UCMDB standalone, but they are only relevant for HP Business Service Management. Ignore the descriptions for these fields in the documentation.

Deprecated CI types do not appear in strikethrough font if the font size is less than 14 points.

In the Multiple Template Based Views wizard in Modeling Studio, when you import values from a CSV file, values for an attribute of type Enumeration are not loaded automatically.

The filter in the Show Element Instances dialog box does not work properly when the Is null operator is selected.

In the Routing tab in the Layout Properties dialog box, (accessed by selecting Layout > Layout Properties), all the options seem to be available, but only some of them are actually used in the layout of the map.

In the Impact Analysis Manager, if an XML file is imported with the same file name as an existing Impact Rule, a confirmation message saying that an Impact Rule of that name already exists is not displayed before replacing the existing Impact rule.

When exporting CI instances found for a selected TQL, you can now manually enter up to 150,000 CIs per page.

If you have Delete permissions for views and you delete a view, the TQL query on which the view depends is also deleted.

In the Modeling Studio, no informative error message is displayed when you import an invalid XML file for views or queries.

PDF export is best visible in a small number of columns ~10 columns.

In the Modeling Studio, in the Query Node Properties dialog box, if you select a criterion, and then select a different criterion, the latter criterion's label is sometimes changed.

In the Impact Analysis manager, when you try to save an Impact rule for which you defined a subgraph, a generic error message appears without giving detailed information regarding the problem.

Printing semi-transparent graphics using the Run Screen Capture Tool produces poor quality results.

In the Hierarchical tab in the Layout Properties dialog box, (accessed by selecting Layout > Layout Properties), the Minimum Backward Edges and Optimize For Feedback Flow options do not work properly.

In Modeling Studio, when you make a change in the hierarchy definition of a template, the template based views based on that template cannot be accessed.

The impact rule group, RC_DIRECTLY_AFFECTED, does not appear in the Impact Analysis Manager.

Reports

In a Delete Candidates report, when you attempt to drill down into the deleted CIs, an error is generated.

In Goldmaster reports, the Include Similar Items check box does not work properly.

In the CI Change report, no relationship attributes are shown for relationships. To resolve this, replace the default value with an empty value in the Change Report link name setting in Infrastructure Settings manager.

There is no option to disable hyperlinks in reports.

Confidential Manager

If you change the default domain name on the UCMDB server, you must first verify that the Data Flow Probe is not running. After the default domain name is applied, you must execute the DataFlowProbe\tools\clearProbeData.bat script on the Data Flow Probe side.

Note: Execution of the clearProbeData.bat script will cause a discovery cycle on the Probe side once the Probe is up.

Lightweight Single Sign-On

For details on security when working with LW-SSO, see "Lightweight Single Sign-On (LW-SSO) Authentication – General Reference" in the HP Universal CMDB Deployment Guide PDF.

Discovery

SQL Protocol: The Encryption Method field enables you to choose SSL support for Oracle connections.

SNMP Protocol: The Privacy Algorithm now supports both DES and AES algorithms.

If you want to connect a new Data Flow Probe to UCMDB with an identifier of a Data Flow Probe that is already defined on a different domain, you must remove the existing Probe from UCMDB (from the Data Flow Probe Setup module), prior to installing the new Probe.

To prevent an overload on the Data Flow Probe machine, you can limit the number of remote processes that run simultaneously. Locate the appilog.agent.local.services.maxRemoteProcesses parameter in the DiscoveryProbe.properties file. The default value is unlimited (-1). Change the value to the maximum number of processes that can be run simultaneously. If you change this value, you must restart the Probe. (This overload can occur when activating certain out-of-the-box jobs that launch a Java process for each destination, for example, J2EE or SAP jobs.)

Downloaded jar file resources can cause the Probe to restart before all the other resources of an adapter package have downloaded. To prevent this occurring, the reset time is, by default, 40 minutes. You can change this time:

Access the appilog.agent.probe.restartProbeAfterJarDownload.interval parameter in the DiscoveryProbe.properties file. The delay until a restart on the first resource download (that is, for a first start or after clearing the Probe data) is 10 milliseconds.

In the Dependency Map, when selecting to show all instances of a selected CI, the instances are not displayed.

When you try to filter triggered CIs by probe in the Discovery Control Panel - Status pane, the triggered CIs are not filtered.

Discovery job error and warning messages are displayed in the language of your client's operating system, independent of browser language settings.

Integration

When running a history-based push job (for changes), you can incorrectly select any integration TQL query, even those that are federated or contain virtual links.

To simplify the creation of integration points, the following adapters are supplied with template configurations which include default options and queries: Service Manager, DDMi, and Microsoft SCCM/SMS. This is relevant for users of Content Pack 8.00 or later.

The Service Manager adapters do not support calculated links for the data push flow.

When configuring the Generic Database Adapter, the fixed_values.txt configuration file now supports constant lists. To define a constants list, use the following syntax:

entity[<entityName>] attribute[<attributeName>] value[{<Val1>, <Val2>, <Val3>, ... }]

When configuring the Generic Database Adapter, there is now an out-of-the-box transformer class to transform a single string list to an integer/string list in UCMDB. For details, see the class: com.mercury.topaz.fcmdb.adapters.dbAdapter.dal.transform.impl.StringDelimitedListTransformer. In the Developer Reference Guide in the task for "Use Eclipse to Map Between CIT Attributes and Database Tables" appearing in the Developing Generic Database Adapters chapter, there is an incorrect file name under step 3 "Prepare the Work Environment". The correct file is workspaces_gdb.zip (not what currently appears: workspaces_gdb.rar).

When working with an integration point that is based on a Jython adapter, you cannot edit the Description or Is integration activated? fields.

If you start a population job (for the first time) on a TQL query that is currently being edited, saving the query may remove its "Active" status and cause the job to fail. If this occurs, running a full population job again will fix the problem.

A population job that uses the UCMDB 9.x adapter to retrieve federated data can retrieve only added or updated CIs, but cannot remove deleted CIs from the CMDB.

An instance of an abstract or federated CIT cannot be successfully created using either the IT Universe Manager or the Trigger CI wizard.

The EMC Control Center (ECC) database does not contain WWN (World Wide Name) information for FCHBAs (Fiber Channel Host Bus Adapters) attached to Storage Arrays. Therefore, this discovery populates the WWN attribute of FCHBA CIs with the ECC ID (internal to ECC) of the HBA. The script also populates the data_note attribute of each such FCHBA CI with a note that ECC does not have WWN info and duplication of this CI is possible.

Reconciliation

UCMDB fails to create an instance of the CIT when adding the root class attribute to the CIT identification criteria, due to missing reconciliation information.

The identification rule schema now supports the conditionType attribute for the attribute-condition element. Valid values for this attribute are:

approveAndContradict – the condition is used for both approving and contradicting CIs (default).

contradictOnly – the condition may only be used to contradict two CIs.

Federation

When you use a federated CIT in the creation of a TQL query for integration and no option is selected in the Select Data Stores window, descendants of that federated node are not federated when the query runs. If you want the descendants of the node to be federated, you must select either the All Data Sources or the Select Data Sources radio buttons.

If you set a property condition on a query node that may bring data from external data sources (federation) and the condition is not supported by one of the data sources, the TQL query calculation will fail.

When federation takes place to UCMDB through an intermediary server, the federation will fail if the CIT that is linked to the federated CIT is identified topologically, in part or in whole, by the federated CIT. For example, there may be a setup with three servers, where Server 1 is the local machine, which federates the IP CIT from Server 2, which in turn federates the same IP CIT from Server 3. When running the TQL query of node CIT linked to IP CIT, the query will fail, since a node CIT is identified by instances of IP CIT that are connected to it.

Federated nodes incorrectly show suggested values from the local CMDB, even when their only data sources are external.

If an integration point that supports a CIT that is being queried by the CI Selector in the IT Universe Manager, and this integration point does not support conditions on the display label, no results are shown.

UCMDB Fixed Defects

Content Pack Documentation Updates

To read the latest versions of the relevant documents, access the following URLs:

Description	Change Request Global ID
Fixed the issue where the server did not start up after applying 9.0x as a patch.	QCCR1H33122
Installing Configuration Management 9.10 on a UCMDB passive machine in HA no longer causes a UCMDB inconsistency.	QCCR1H34305
Fixed the issue where you could not update/create/delete lists in System Type Manager due to the following: [ErrorCode [732] Action is not allowed because the list contains duplicate entries. This error occured in 9.02 upgraded system only.	QCCR1H34358
Fixed problem of getting an error when inserting a CI of type Organization with a name containing a question mark (?)	QCCR1H31685
Fixed the problem of scheduling integration jobs to SM9	QCCR1H32752
Fixed the issue where the server was not rocessing results from the Probe	QCCR1H34397
Fixed the problem where new alerts are not received and views are not updated until the CMDB service is restarted	QCCR1H32419
You can now customize the shortcut menu of a CI as often as necessary	QCCR1H33619
An attribute added to a class can now be deleted after restarting the UCMDB server	QCCR1H33682
Fixed issue where where you cannot open a saved TQL anymore due to the following error 'Unexpected error occured: java.lang.Float cannot be cast to java.lang.Integer'	QCCR1H32152
"Menu Item Name" now correctly displays in the CI popup menu	QCCR1H33425
"Generate Direct Link" no longer makes duplicate CIs	QCCR1H33846
When exporting CI instances found for a selected TQL, you can now enter up to 150,000 CIs per page.	QCCR1H30383
Fixed the issue where modifying the Set Data Source in a federated pattern view cannot be saved	QCCR1H30780
Fixed the problem of getting a ClassCastException when opening a query with an un/changed float value	QCCR1H32179
LDAP mapping: The default role was changed from <Guest> to empty	QCCR1H32683
Correlation: The Severity relative to trigger severity % option is now working as expected	QCCR1H32614
When changing "Default Value" of "Actual Deletion Period" or "Deletion Candidate Period", the pop-up window "You are not permitted to update this class" may be displayed. This can be ignored by clicking the "OK" button.	QCCR1H34401
Fixed the issue where LDAP authentication stopped working after restarting UCMDB processes.	QCCR1H33449
Display name and descriptions are now displayed correctly while navigating through CI Type hierarch	QCCR1H32455
Exporting a report to CSV format now fills the table's cells with the correct data	QCCR1H32900
When entering the details of a new user, you can now enter 20 digits in the Business Tel field	QCCR1H33803
Join relationships can now be used with the Set Element Invisible option	QCCR1H33294
Fixed problem of getting the error "[ErrorCode [502] Maximum number of CIs allowed to be removed exceeded" at the step "Clean Invalid Interfaces" when upgrading from 8.04 + CP7 to UCMDB 9.02	QCCR1H33535
Fixed the issue where reconciliation cannot identify entities that have a boolean attribute	QCCR1H33039
Service Manager Integration: Fixed issue where an error was returned when defining a filter with a NOT operator	QCCR1H32188
CI Types with string_list key attributes can now be populated by Java adapters	QCCR1H32717
GDBA: It is now possible to define a fixed value for string_list or integer_list properties	QCCR1H32309
Fixed issue where object condition results exceeded the maximum allowed value of 2000000 when upgrading 8.04 + CP7 to UCMDB 9.02	QCCR1H33588
Fixed issue where "Last Access Time" of most of the Memory/Cpu CIs is not updated when running the "Host Resources by Shell" job.	QCCR1H32138
Fixed the issue where CI were falsely triggered when rerunning a discovery job.	QCCR1H31098
Fixed issue of getting the following error when creating a custom AM integration adapter using a discovery script: "[JobExecuterWorker-0:CSSInstSW_10.163.209.210] (DynamicService.java:81) - DynamicService failed processing tables on destination: 10.163.209.210(ID=48a518acdbdb86e84eed1b7300b156fc)java.lang.NullPointerException"	QCCR1H32144
Probe Manager can now retrieve credentials from Probe Gateway when HTTPS is used	QCCR1H34143
Re-initializing a DDMA probe (clearing it completely) no longer causes other jobs and Probes to run	QCCR1H33851
Discovery Job "Host Resources and Application by WMI" can now discover all the InstallSoftware CIs when using a 64-bit probe	QCCR1H31626
Fixed problem in which an error used to occur when updating the configuration using the UCMDB API	QCCR1H33571
When defining a schedule for runing discovery using Basic Mode, use a number that is greater than 0 (zero) in the "Repeat Every" box.	QCCR1H30178
"Host connection by" jobs are now working properly	QCCR1H34340
Fixed issue where when you excluded an IP from one of the network ranges, the IP was excluded from all ranges containing that IP	QCCR1H32759
The database no longer disconnects from the MySQL database while running long discovery jobs	QCCR1H33292
Data Flow Probe no longer becomes disconnected from the UCMDB App Server	QCCR1H32974
During touch process, a delete notification may not be sent to the Probe for every CI deleted in UCMDB. Solution: Update the IDs in the Probe's tables manually.	QCCR1H32704
The Deployment Guide's description about load balancer's session stickiness settings for High Availability Mode has been updated	QCCR1H34063

<http://SERVER_NAME:PORT/ucmdb-ui>/docs/DDMContent.jsp – Discovery and Integration Content Guide

<http://SERVER_NAME:PORT/ucmdb-ui>/docs/permissions.jsp – the Permissions document

<http://SERVER_NAME:PORT/ucmdb-ui>/docs/readme.jsp – the Release Notes (this file)

<http://SERVER_NAME:PORT/ucmdb-ui>/docs/whatsnew.jsp – What's New in this release

Multilingual Support

The Uprgrade Wizard for version 9.03 now supports the non-English user interface.

For reasons of compatibility, 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.

In Enrichment Manager, required attributes in the Node Definition dialog box are not marked in bold for the Japanese, Chinese, and Korean versions.

Non-English characters should not be used in the UCMDB installation path or in paths to different properties or adapter files.

Multi-byte characters should not be used in user passwords.

The action names in scheduled jobs are stored with localized names (according to the locale being used), but those names are displayed with no dependence on locale. Those action names may be user-modified and therefore will be user-specific.

You can now configure email settings using multi-byte characters. These settings were moved to the Infrastructure Settings Manager.

Excel can now open UTF-8 encoded CSV documents correctly.

In the HP Universal CMDB Administration Guide, it states that you cannot create a new user if the name of the new user contains more than 20 Asian characters. This limitation no longer exists.

HP Universal CMDB does not fully support surrogate pairs and combining characters.

HP Universal CMDB Readme 9.02

for the Windows and Linux operating systems

Software version: 9.02

Publication date: October 2010

This file provides information about HP Universal CMDB (UCMDB) version 9.02. For information on UCMDB 9.01, click here. For information on UCMDB 9.00, click here.

Documentation Updates

To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals

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.02 Files/Components

HPUCMDB_Server_902.exe. The installation of the version 9.02 HP UCMDB Server for the Windows platform.

HPUCMDB_Server_902.bin. The installation of the version 9.02 HP UCMDB Server for the Linux platform.

HPUCMDB_DataFlowProbe_902.exe. The installation of the version 9.02 Data Flow Probe for the Windows platform.

HPUCMDB_DataFlowProbe_902Linux.bin. The installation of the version 9.02 HP UCMDB Server for the Linux platform.

Discovery and Integration Content Pack 7.00 is included with UCMDB version 9.02. There is no need to install it separately.

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\

System Requirements

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

In the Server Database Requirements section, the following additional Microsoft SQL Servers are supported for working with HP Universal CMDB:

UCMDB Server Installation

Choose one of the following procedures to install the UCMDB Server, according to which version is currently installed (if at all):

Database Release
Version	System Type	Service Pack
Microsoft SQL Server 2005 Enterprise Edition	32-bit	Service Pack 4
Microsoft SQL Server 2005 Enterprise Edition	64-bit	Service Pack 4

Current Installation: No version is installed. Install according to the Operating System:

Windows platform: Install HP UCMDB 9.02.
Extract UCMDB_00033.zip to a temporary directory. Then launch HPUCMDB_Server_902.exe and follow the instructions in "HP Universal CMDB Installation on a Windows Platform" in the HP Universal CMDB Deployment Guide PDF.

Linux platform: Install HP UCMDB 9.02.
Extract UCMDB_00034.zip to a temporary directory. Then launch HPUCMDB_Server_902.bin and follow the instructions in "HP Universal CMDB Installation on a Linux Platform" in the HP Universal CMDB Deployment Guide PDF.

Current Installation: HP UCMDB 8.x or HP UCMDB 7.x: For details on the upgrade procedure from version 8.0x to 9.02, see "Upgrading HP Universal CMDB to Version 9.02" in the HP Universal CMDB Deployment Guide PDF.

Current Installation: HP UCMDB 9.01/9.00:

Stop the UCMDB 9.0x server before starting the 9.02 installation.

Execute the UCMDB 9.02 installer according to the instructions on page 5.

When selecting the installation folder, select the existing 9.0x installation folder.

When selecting the installation type, select Update from 9.0x.

Complete the installation process.

Start up the version 9.02 server. For details on server status, see "HP Universal CMDB Services" in the the HP Universal CMDB Deployment Guide PDF.

Data Flow Probe Installation

Adapter Upgrade

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

Important: All adapters must be compatible with the new 9.0 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.02 version. That is, do not copy files from version 8.0x and overwrite the files in version 9.02.

Notes and Limitations

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.

When running in High Availability mode, you must log on to the Server Management Tool using the address of the active server.

Upgrade

The Validate Class Model and Update Class Model steps in the upgrade process have been combined into one procedure, running one after the other. If the second part (upgrade) fails, then both steps are run again in sequence.

When upgrading from version 8.0x to version 9.02, the Data Flow Probe fails to update the server with job results if the Probe's IP address changes (and its identifier remains the same).

When upgrading from version 9.0x to version 9.02, if you have a larger History database, the first server startup may take some time to complete. Do not interrupt the server startup process until you have confirmed that the server is up and running.

LDAP server settings are not upgraded during the upgrade process. You must manually reconfigure the LDAP connection configuration after upgrading to 9.02 (user mappings are upgraded).

HP UCMDB

If you encounter either a Couldn't connect to database or Error getting connection from pool error message in the UCMDB error.log file (located in the C:\hp\UCMDB\UCMDBServer\runtime\log\ directory), do the following:

Open the connection_pool.conf file (located in the C:\hp\UCMDB\UCMDBServer\conf\ directory).

Note: If your system was upgraded from UCMDB version 9.01 or 9.00, create the file using a text editor.

Add or unmark the following parameter:

maxPoolSize=50

The Connection_pool.conf file configures properties related to the database connection pool. Its default content is:


# DB Connection pool defaults. #maxPoolSize=10 #minPoolSize=2 #maxWaitForConnectionSec=10 # 0=FAIL, 1=BLOCK, 2=GROW #whenExhaustedAction=1

You can configure:

minimum and maximum number of connections in the pool.

whenExhaustedAction - what to do when requesting a new connection and there are no free connections in the pool. Valid values are fail, wait (BLOCK), or add new connection to pool (GROW).

maxWaitForConnectionSec - the maximum time to wait, when whenExhaustedAction=BLOCK.

After restarting the server, it may not be possible to log in for several minutes even though the login page is available.

System Health is not available with version 9.02, but will be added in a future version.

When you generate a direct link from IT Universe Manager to a perspective based view, the link does not work.

To use an exported TQL as the input to the executeTopologyQueryWithParameters Web service, log in to the JMX console: launch the Web browser and enter the following address: http://<UCMDB Server Host Name or IP>:8080/jmx-console. You may have to log in with a user name and password. The default is sysadmin/sysadmin.

Under UCMDB, click UCMDB:service=TQL Services to open the JMX MBEAN View page.

Locate the exportTql operation.

In the customerId parameter box, enter 1 (the default).

In the patternName parameter box, enter a valid TQL name.

Click Invoke.

Use the resulting XML code as input for the executeTopologyQueryWithParameters Web service. For details, see "executeTopologyQueryWithParameters" in the HP Universal CMDB Developer Reference Guide.

By default, you cannot compare configuration files because the Comparable qualifier of the DocumentContent attribute of the ConfigurationDocument CIT is not selected. To enable the comparison of configuration files, double click the attribute to open the Edit Attribute dialog box. In the Advanced tab, select the Comparable check box.

Modeling

When creating a view based on the template that contains a parameter defined using the In operator, if you enter a blank value for that parameter, an error is generated when you try to preview or calculate the template-based view.

When defining the report settings in Modeling Studio, if you delete a CI on one layer, a function on a higher layer based on that CI is not automatically deleted.

When defining attributes in the Query Node Properties dialog box, parameterized values are allowed when the Is null operator is selected.

When you delete a view in Modeling Studio, the associated TQL query is also deleted.

It is not possible to import calculated relationships to the CI Type Manager from an XML file.

It is not possible to paste values in a list format into the Value field of the Attribute tab in the Query Node Properties dialog box when the In operator is selected.

Deprecated CI types do not appear in strikethrough font if the font size is less than 14 points.

In the Multiple Template Based Views wizard in Modeling Studio, when you import values from a CSV file, values for an attribute of type Enumeration are not loaded automatically.

The filter in the Show Element Instances dialog box does not work properly when the Is null operator is selected.

Reports

Any reports scheduled before performing an upgrade will not run after the upgrade is performed and should be rescheduled to run after the upgrade.

The Send Mail button in the Reports module does not work for archived reports when the Direct Link check box in the Schedule Report dialog box was selected.

In a Delete Candidates report, when you attempt to drill down into the deleted CIs, an error is generated.

Confidential Manager

Note: Execution of the clearProbeData.bat script will cause a discovery cycle on the Probe side once the Probe is up.

When running the Data Flow Probe on a Linux machine, Confidential Manager errors appear in the WrapperProbeGW.log file and the Probe fails to retrieve credentials from the UCMDB Server.

To prevent these errors appearing, after Probe installation and before starting the Probe, delete the following files:

/opt/hp/UCMDB/DataFlowProbe/conf/security/secured_storage.bin

/opt/hp/UCMDB/DataFlowProbe/conf/security/cmcache.bin

After Probe startup, an error appears in the WrapperProbeGW.log file: Failed to get CM configuration from secured storage. This error can be disregarded as it does not affect Probe functionality.

Lightweight Single Sign-On

For details on security when working with LW-SSO, see "Lightweight Single Sign-On (LW-SSO) Authentication – General Reference" in the HP Universal CMDB Deployment Guide PDF.

Data Flow Management

After uninstalling the Data Flow Probe, mysqld.exe and associated files are not deleted. To delete all files, restart the machine on which the Data Flow Probe was installed.

SQL Protocol: The Encryption Method field enables you to choose SSL support for Oracle connections.

SNMP Protocol: The Privacy Algorithm now supports both DES and AES algorithms.

When multiple Data Flow Probes send touch information simultaneously to the UCMDB Server, the Server may become overloaded. To enable a manual load balancing between the multiple Data Flow Probes running against the UCMDB Server, you can set the time at which each Probe reports the touch:

Open the DiscoveryProbe.properties file in a text editor.

Locate the lines beginning with # Is touch window mechanism active:


"# Is touch window mechanism active appilog.agent.probe.touchWindowMechanism.isActive = false "# Defines the time when the touch window starts (HH:MM - 00:00-23:59) appilog.agent.probe.touchWindowMechanism.startTime = 10:00 "# Defines the time when the touch window ends (HH:MM - 00:00-23:59) appilog.agent.probe.touchWindowMechanism.endTime = 23:59

Change the appilog.agent.probe.touchWindowMechanism.isActive parameter to true.

Set the time at which the Probe should report the touch.

Save the file.

These parameters enable the Probes to perform "touching" in non-overlapping time frames. For details on touching, see "The Aging Mechanism Overview" in HP UCMDB Administration Guide.

The Adapter Management tab in the Adapter Management application is now named Adapter Configuration.

When attempting to clear Data Flow Probe data on a Probe that is installed on a Linux machine, the following error message is displayed:


/opt/hp/UCMDB/DataFlowProbe/log/probe_setup.log: No such file or directory Cannot establish connection to the database with provided password.

To use the clearProbeData.sh script, execute the following commands in the shell of the Linux running the Integration Probe:


mkdir /opt/hp/UCMDB/DataFlowProbe/log mkdir /opt/hp/UCMDB/DataFlowProbe/runtime/probeManager/discoveryScripts/ touch /opt/hp/UCMDB/DataFlowProbe/runtime/probeManager/discoveryScripts/dummy

Then, manually change the script: write rm -rf instead of rm -r anywhere in the script in order for it to work.

When working with trigger CIs in the Discovery Control Panel, you can view results in a list only, and not in a map. Clicking the Show results as a map button brings up an error message.

Integration

After a job runs successfully, its status remains as "Succeeded" even after the job definition is changed (for example, selecting another TQL query or enabling deletion) and saved.

Since the UCMDB 9.x adapter works with the "changes" population engine, if a population flow retrieves federated data, no removals are made in the CMDB, since the federation brings only added or updated data.

If UCMDB is unable to load an integration point (for example, because the Data Flow Probe is down or a remote host is down), a message is displayed. The user can choose to disable the integration point and all its scheduled jobs and federated classes. The integration point now loads successfully.

When you create an integration with the Integration Studio, after saving and closing the Reconciliation Priority Manager, attribute priority values are reset when you reopen the Reconciliation Priority Manager.

After saving a job in the Integration Studio that has been scheduled as "yearly", the scheduling repeat is displayed in the Cron tab, although the scheduling actually remains as "yearly".

During integration point definition, when selecting a Probe, users see the list of Probe managers and not the list of Probes. This is a display issue only and does not affect work in the Integration Studio.

An instance of an abstract or federated CIT cannot be successfully created using either the IT Universe Manager or the Trigger CI wizard.

When setting or removing federated CITs, changes may take a long time to appear in the UI.

UCMDB Fixed Defects

Discovery and Integration Content

Discovery and Integration Content Pack 7.00 is included with UCMDB version 9.02. There is no need to install it separately.

Description	QC Change Request
BAC is now able to populate SiteScope CIs on Dashboard.	QCCR1H27221
Fixed issue where the action of simultaneous touches by multiple DFM Probes places a high load on the UCMDB Server. Solution: configure the Discovery Probes to perform touches in non-overlapping time frames.	QCCR1H28344
Triggered CI: snmp@<CMDBID> invoked on the Discovery job Host Networking by SNMP now meets the discovery pattern input TQL conditions.	QCCR1H28633
LDAP login is no longer case sensitive.	QCCR1H28979
Fixed problem of getting a Tanuki Java Service Wrapper license error in the eastern time zones from GMT +9.	QCCR1H29390
Fixed problem of getting the error: "Connection to server has been lost" when it does not apply.	QCCR1H29679
Comparing CIs report now works correctly when CIs are in an "Updated Item" state.	QCCR1H29915
Parameterized views created in Modeling Studio now allow changes in the parameters when running the report based on the view.	QCCR1H29869
The encryption key location in the HP Universal CMDB Deployment Guide PDF for version 9.01 has been corrected.	QCCR1H30570
Scheduled change reports are now updating correctly.	QCCR1H30571
The "VLAN Ports by SNMP" job now creates a task when required for the triggered CIs.	QCCR1H30102
UCMDB replication job scheduling is now working correctly when changing the language in Internet Explorer.	QCCR1H30020
Base TQL for Template Based View is now visible in Package Manager.	QCCR1H30678
Views with grouping by attributes using regular expressions are now working correctly.	QCCR1H29441
Templates have replaced parameterized views. Users with "view" privileges have rights to change the values for template results, but not to change the template itself.	QCCR1H30738
Fixed Application-signature GUI problem. Adding a new entry with a product name that exists in another entry now works correctly	QCCR1H30408
Users can no longer click the email button if the SMTP server has not been set up.	QCCR1H30242

Permissions Documentation. Content Pack 7.00 includes an updated document that describes all required credentials for each discovery job. The file is located in the following folder: C:\hp\UCMDB\UCMDBServer\deploy\ucmdb-docs\docs\eng\pdfs\Permissions.pdf.

Each DDM Content Pack is accumulative, that is, each pack includes all content from previous content packs. For example, Content Pack 7.00 includes the content from Content Pack 6.00. Therefore, you can install Content Pack 7.00 without installing Content Pack 6.00.

You cannot install a content pack if you already installed a later content pack. For example, you cannot install Content Pack 6.00 if you have already installed Content Pack 7.00. This is due to current Package Manager deployment limitations.

Each Content Pack installation overrides all out-of-the-box resources with the contents of that Content Pack. This means that any changes you made to these resources are lost. This applies to the following resources: TQLs, Views, Enrichments, Reports, Discovery Jython scripts, Discovery adapters, Discovery resources, Discovery configuration files, Discovery modules, CI Types, and Relationships. (Attributes added to CI Types and Relationships are not overridden).

In general, it is recommended to refrain from making changes to out-of-the-box resources. If you must do so, be sure to track your changes so that they can be re-applied after you install a Content Pack. Important general fixes (not specific to your environment) should be sent to CSO so that they can be analyzed and included as part of one of the next Content Packs.

Changes to HP Universal Discovery and Dependency Mapping Content occur only in Content Packs and not in Service Packs.

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 HP Universal CMDB Discovery and Integration Content Guide.

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

DB2 databases are not discovered by DB connections by a WMI job because DB2 information is not available in the Windows registry.

Fixed defects and escalations:


Description	QC Change Request
Fixed issue where the J2EE Websphere by Shell job has missing classes and attributes previously discovered with the JMX pattern	QCCR1H26843
Fixed issue where Atrium integration does not create a link correctly in Remedy	QCCR1H27263
Fixed issue where the TCP and Host to Host Dependencies discoveries (the Servers by Network Data and Potential Servers by Network Data jobs) do not discover an out-of-scope server	QCCR1H27828
Fixed issue where the SAP Solution Manager Topology by SAP JCO job fails with an out of memory error	QCCR1H26408
Fixed issue where the ms_exchange_folder object has no required root_container attribute	QCCR1H28215
Fixed issue where the MS Cluster by NTCMD job fails on Windows 2008 servers	QCCR1H28405
Fixed issue where the Collect Network Data by Netflow job does not take the listenDurationInMinutes parameter into account	QCCR1H28621
Fixed issue where discovery of Microsoft Exchange 2007 throws a System32 Junction Point error with NTCMD	QCCR1H29479
Fixed issue where the wrong host operating system for the MS Windows 2008 by SNMP job is discovered	QCIM1H29968
Fixed issue where a SQL cluster is not correctly mapped due to Reconciliation ignoring data	QCCR1H27688
Fixed issue where the Mainframe TCP by SNMP job reports a fatal error following discovery	QCIM1H28986
Fixed issue where duplicate hosts are reported	QCIM1H28588
Fixed issue where Siebel CRM 8 is not discovered	QCCR1H28233

Content Pack Documentation Updates

To read the latest versions of the relevant documents, access the following URLs:

<http://SERVER_NAME:PORT/ucmdb-ui>/docs/DDMContent.jsp – Discovery and Integration Content Guide

<http://SERVER_NAME:PORT/ucmdb-ui>/docs/permissions.jsp – the Permissions document

<http://SERVER_NAME:PORT/ucmdb-ui>/docs/readme.jsp – the Release Notes (this file)

<http://SERVER_NAME:PORT/ucmdb-ui>/docs/whatsnew.jsp – What's New in this release

Multilingual Support

The Uprgrade Wizard for version 9.02 now supports the non-English user interface.

For reasons of compatibility, Integration Points names and Data Flow Management job names can include only English letters, numbers, and the underscore character (_).

In Enrichment Manager, required attributes in the Node Definition dialog box are not marked in bold for the Japanese, Chinese, and Korean versions.

Non-English characters should not be used in the UCMDB installation path or in paths to different properties or adapter files.

Multi-byte characters should not be used in user passwords.

The action names in scheduled jobs are stored with localized names (according to the locale being used), but those names are displayed with with no dependence on locale. Those action names may be user-modified and therefore will be user-specific.

You can now configure email settings using multi-byte characters. These settings were moved to the Infrastructure Settings Manager.

Pie charts in scheduled reports are displayed according to the server's locale.
Workaround: Open the pie chart with the desired locale in a browser window, and edit it directly.

Excel can now open UTF-8 encoded CSV documents correctly. The workaround that is documented in page 426 of the the HP Universal CMDB Deployment Guide PDF is no longer necessary.

HP Universal CMDB Readme 9.01

for the Windows and Linux operating systems

Software version: 9.01

Publication date: July 2010

This file provides information about HP Universal CMDB (UCMDB) version 9.01. For information on UCMDB 9.00, click here.

Documentation Updates

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

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.01 Files/Components

HPUCMDB_Server_901.exe. The installation of the version 9.01 HP UCMDB Server for the Windows platform.

HPUCMDB_Server_901.bin. The installation of the version 9.01 HP UCMDB Server for the Linux platform.

HPUCMDB_DataFlowProbe_901.exe. The installation of the version 9.01 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\

System Requirements

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

UCMDB Server Installation

Choose one of the following procedures to install the UCMDB Server, according to which version is currently installed (if at all):

Current Installation: No version is installed. Install according to the Operating System:

Windows platform: Install HP UCMDB 9.01 as a full installation. Extract UCMDB_00029.zip to a temporary directory. Then launch HPUCMDB_Server_901.exe and follow the instructions in "HP Universal CMDB Installation on a Windows Platform" in the HP Universal CMDB Deployment Guide PDF.

Linux platform: Install HP UCMDB 9.01 as a full installation. Extract UCMDB_00030.zip to a temporary directory. Then launch HPUCMDB_Server_901.bin and follow the instructions in "HP Universal CMDB Installation on a Linux Platform" in the HP Universal CMDB Deployment Guide PDF.

Current Installation: HP UCMDB 8.x or HP UCMDB 7.x: For details on the upgrade procedure from version 8.0x to 9.01, see "Upgrading HP Universal CMDB to Version 9.01" in the HP Universal CMDB Deployment Guide PDF.

Current Installation: HP UCMDB 9.00:

Backup the C:\hp\UCMDB\UCMDBServer\runtime\fcmdb folder from the 9.00 installation.

Uninstall version 9.00.

Install version 9.01 according to the instructions above.

Connect version 9.01 to the existing 9.00 database schema using the UCMDB configuration wizard. For details, see "UCMDB Server Configuration" in the the HP Universal CMDB Deployment Guide PDF.

Copy the C:\hp\UCMDB\UCMDBServer\runtime\fcmdb folder from the backup of the version 9.00 installation to the 9.01 installation folder (on the same path).

Start up version 9.01. For details on server status, see "HP Universal CMDB Services" in the the HP Universal CMDB Deployment Guide PDF.

When the server is up, on the UCMDB Server machine, launch the Web browser and enter the following address: http://<UCMDB Server Host Name or IP>:8080/jmx-console. You may have to log in with a user name and password. The default is sysadmin/sysadmin.

Under UCMDB, click UCMDB:service=Packaging Services to open the JMX MBEAN View page.

Locate the updateResources operation. This method accepts the following parameters:

customerId. The customer ID.

In the customerId parameter box, enter 1 (the default).

Click Invoke.

Data Flow Probe Installation

Adapter Upgrade

For all non out-of-the-box adapters: you must redeploy the adapters in version 9.01. 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.01 version. That is, do not copy files from version 8.04 and overwrite the files in version 9.01.

Notes and Limitations

Installation

Upgrade

HP UCMDB

Lightweight Single Sign-On

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.

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 are not 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.01 (user mappings are upgraded).

The resources-only upgrade functionality is not supported in version 9.01. For a solution, contact HP Software Support. The upgrade will be available in version 9.02.

When upgrading from UCMDB 8.x to 9.01 in a Linux environment, using the upgrade utility, follow these instructions to update the upgrade.sh file:

On the Linux 9.01 machine, locate the file in the following directory: <UCMDB installation folder>/ tools.

Backup the upgrade.sh. file.

Open upgrade.sh file on <UCMDB installation folder>/ tools

Replace the original upgrade.sh with the following text:


#!/bin/sh DIRNAME=`dirname $0` PROGNAME=`basename $0` ROOT=$DIRNAME/.. # use 1 to enable or set DEBUG_OPTS to override ENABLE_REMOTE_DEBUG= DEBUG_PORT=5005 DEBUG_SUSPEND=n if [ -n "$ENABLE_REMOTE_DEBUG" ]; then DEBUG_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=$DEBUG_SUSPEND,address=$DEBUG_PORT" fi set JAVA=java if [ -f "$ROOT/bin/jre/bin/java" ]; then JAVA=$ROOT/bin/jre/bin/java fi MEM_OPTS="-Xms256m -Xmx4096m -XX:MaxNewSize=1024m -XX:MaxPermSize=192m -XX:+UseCompressedOops" GC_OPTS="-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+UseAdaptiveGCBoundary" JAVA_OPTS="$MEM_OPTS -XX:+HeapDumpOnOutOfMemoryError" CP="$ROOT/classes:$ROOT/tools/server/:$ROOT/jre/lib/:$ROOT/lib/:$ROOT/deploy/ucmdb-ui/static/appletJars/:$ROOT/tools/upgrade/lib/*" $JAVA $JAVA_OPTS $DEBUG_OPTS -cp $CP -Ducmdb.home=$ROOT -DupgradeMode com.hp.upgrade.ui.frame.UpgradeMain

Save the file

Run the file: ./upgrade.sh.

The upgrade utility opens.

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.01, but will be added in a future version.

In the Modeling Studio, when you select View in the Main menu and try to hide one of the tabs in the Left pane (Resources, CI Selector, or CI Types), all of the tabs are hidden.

In Modeling Studio, the Changed during or Unchanged during operators for date attributes are supported only if you change the query to NOT 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.

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.

The Get Related CIs Report in IT Universe Manager is not available in version 9.01. 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.

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.

In the Query Node Grouping dialog box in the Modeling Studio, the Minimum in Group field is replaced by the Expression capture group index field, which is used to indicate which portion of the regular expression is relevant for the grouping. Enter 0 to indicate that the entire expression is relevant.

To designate a view as a hidden view that does not appear in IT Universe Manager, define a bundle for hidden views, as follows:

In the Infrastructure Settings Manager, select Hidden Bundles Names in CI Selector.

Enter the name of the new bundle as the default value and save the setting.

In the Modeling Studio, open the relevant view and click View Definition Properties in the toolbar.

In the View Definition Properties dialog box, select the hidden views bundle and assign the view to it.

The UCMDB Server Configuration Wizard fails when trying to connect to schemas created manually or by the SQL script. (This will be fixed in version 9.02.) 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 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 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.

When you update an adapter package, use Notepad++ rather than Notepad to edit the template files. This prevents the use of special symbols, which cause the deployment of the prepared package to fail.

When creating an instance-based model in the Modeling Studio, an error is generated if you try to add related CIs before saving the model. You should create the model, save it, and then add the related CIs.

In the Modeling Studio, editing a perspective-based view with the following actions corrupts the perspective-based view:

check/uncheck over model hierarchy

removing perspective from perspective hierarchy

To avoid this problem, create a new perspective-based view.

Lightweight Single Sign-On

For details on security when working with LW-SSO, see "Lightweight Single Sign-On (LW-SSO) Authentication – General Reference" in the the HP Universal CMDB Deployment Guide PDF.

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

The default user name and password for logging in to the Data Flow Probe JMX Console is sysadmin/sysadmin.

Enable SSL Between UCMDB Server and UCMDB Data Flow Probe with Mutual Authentication: In version 9.01, 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 the HP Universal CMDB Deployment Guide PDF.

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.

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.

Fail entire bulks due to invalid CIs. If a set of objects (for example, 1,000 objects) includes even one invalid CI (for example, a node cannot be identified because of missing topological information), the reconciliation engine drops the entire set and does not send it to the CMDB. This is the default behavior.

Clear the check box to have the results sent to the CMDB with only the invalid CIs (and their topology) dropped from the results. In the above example, 999 objects would be processed. UCMDB displays an error message when you view the results.

To access this check box: Data Flow Management > Adapter Management. In the Resources pane, select an adapter. In the Adapter Management tab > Results Management pane, select the Fail entire bulks due to invalid CIs check box, or right-click a job in the Discovery Control Panel window and click Go to Adapter.

Version 9.01 includes a new purging mechanism for managing old Discovery result statistics. This mechanism enables faster display of the discovery results statuses. That is, the old statistics records are merged and therefore they are still available for the user. The new feature is controlled by two system parameters:

appilog.collectors.ResetDiscoveryStatisticsIntervalHours.name=The interval for running the purging mechanism.

appilog.collectors.DiscoveryStatisticsArchiveDays.name=Discovery results statistics archive period (the number of days after which the statistics are considered old).

Integration

The status of a population job can be displayed as Running even though the job is not displayed.

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.

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.

A node is sometimes created without either an IP_ADDRESS or INTERFACE property.

Service Manager 7.1x adapter is now called the Service Manager 7.1x-9.2x adapter, since integrations with Service Manager 7.2 and later can be performed.

The Federation Tab of the Integration Studio displays only those CI Types and attributes that can be federated from the selected data repository.

Automatic completion of reconciliation data:

is enabled by default and cannot be disabled.

always retrieves the Global ID.

enables required reconciliation data that is missing to be ignored rather than causing the entire job to fail.

You cannot modify a disabled integration that does not have a Host name.

Syncing between two CMDB servers fails if the source server has no additional CI types (beyond the ones found on the target server). To prevent this problem, add an additional CI type to the source server.

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.

Discovery and Integration Content

Discovery fails during a Shell-based job execution with a Failed to create System32 junction point error message. This issue may arise if the junction point already exists and the system does not allow its recreation. To resolve the issue, log in to the destination machine and remove the junction point by running the following command:


rmdir %SystemDrive%\ddm_link_system32

Note: The command should be rmdir and not del or deltree, as otherwise the Windows system32 folder is deleted.

Previously-discovered Layer 2 topology is not upgraded to version 9.01, so you must rediscover this topology. You can either delete existing Layer 2 links manually or rely on the aging mechanism to delete them.

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

SAP discovery. For SAP discovery to work correctly, perform the following procedure:

Copy sapjcorfc.dll from the temporary directory to the %winnt%\system32 directory on the machine where the Data Flow Probe is installed. Also copy the file to the C:\hp\UCMDB\DataFlowProbe\content\dll folder.

Copy librfc32.dll from the temporary directory to the %winnt%\system32 directory. Also copy the file to the C:\hp\UCMDB\DataFlowProbe\content\dll folder.

Verify that the MSVCR71.dll and MSVCP71.dll files are located in the %winnt%\system32 directory.

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\SysWOW64\).

Place the msvcp71.dll and msvcr71.dll drivers under the Windows installation folder (for example, C:\windows\SysWOW64\).

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

For details on SAP discovery, see "Discover SAP ABAP" in the HP Universal CMDB Data Flow Management Guide.

When using the NTCMD credentials to run discovery, if the following warning is displayed, the remote 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.

This is just a warning and the discovery based on NTCMD functions properly. However, to avoid this warning, open the Registry Editor on a remote machine and edit the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows Set the NoInteractiveServices property to 0.

You can configure discovery so that any object reported by the job and whose CIT is not defined in the adapter's discovered CITs list is marked in red.

To set this parameter:

Select Administration > Infrastructure Settings > General Settings.

Locate the Enable statistics results validation according to adapter parameter.

Change the value to True.

The MQ (Microsoft Message Queue) model has been changed and the following resources are no longer available.

The following CITs have been deprecated:

CIT: mqaliasq, display name: IBM MQ Queue Alias

CIT: mqalias, display name: IBM MQ Alias

CIT: mqchannelof, display name: IBM MQ Channel Of

CIT: mqchannel, display name: IBM MQ Channel

CIT: mqchclntconn, display name: IBM MQ Client Connection Channel

CIT: mqchclusrcvr, display name: IBM MQ Cluster Receiver Channel

CIT: mqchclussdr, display name: IBM MQ Cluster Sender Channel

CIT: mqchrcvr, display name: IBM MQ Receiver Channel

CIT: mqchrqstr, display name: IBM MQ Requester Channel

CIT: mqchsdr, display name: IBM MQ Sender Channel

CIT: mqchsvrconn, display name: IBM MQ Server Connection Channel

CIT: mqchsvr, display name: IBM MQ Sender Channel

CIT: mqcluster, display name: IBM MQ Cluster

CIT: mqmqichannel, display name: IBM MQ MQI Channel

CIT: mqmqilink, display name: IBM MQ

CIT: mqmsgchannel, display name: IBM MQ Message Channel

CIT: mqmsglink, display name: IBM MQ Message

CIT: mqmsgreceiverchannel, display name: IBM MQ Message Receiver Channel

CIT: mqmsgsenderchannel, display name: IBM MQ Messanger Sender Channel

CIT: mqqueuelocal, display name: IBM MQ Local Queue

CIT: mqqueuemanager, display name: IBM MQ Queue Manager

CIT: mqqueueremote, display name: IBM MQ Remote Queue

CIT: mqqueue, display name: IBM MQ Queue

CIT: mqrepository, display name: IBM MQ Repository

CIT: mqresolve, display name: IBM MQ Resolve

CIT: mqxmitq, display name: IBM MQ Transmission Queue

CIT: webspheremq, display name: IBM WebSphere MQ

The following resources have been removed:

Enrichment rule: Create_Msg_Channel_Link_Host

Enrichment rule: Create_Msg_Channel_Link_IP

Enrichment rule: Create_RemoteQueue_Link

Enrichment rule: Host_Depend_By_MQ

View: MQ_All_Objects

View: MQ_Channels

View: MQ_Clusters

View: MQ_Network_Objects

View: MQ Queue Map

TQLs: All TQLs corresponding to the above Enrichment rules and Views

Multilingual Support

For reasons of compatibility, Integration Points names and Data Flow Management job names can include only English letters, numbers, and the underscore character (_).

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.

XML files cannot be edited in Adapter Management when the user interface uses a Chinese, Korean, or Spanish locale.

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.

HP Universal CMDB Readme 9.00

for the Windows and Linux operating systems

Software version: 9.00

Publication date: June 2010

Documentation Updates

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

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

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).

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 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 Root groups base DN to CN=Users,DC=consult,DC=example,DC=com;

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

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.

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

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.

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.

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 (_).

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

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.

Legal Notices

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.

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.

Intel®, Itanium®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.

Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation.

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