HP Universal CMDB

For the Windows and Redhat Enterprise Linux operating systems

Software Version: 10.01

Customized output from:

HP Universal CMDB Deployment Guide

HP logo

Document Release Date: October 2012

Software Release Date: November 2012

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice

© Copyright 2002-2012 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe™ is a trademark of Adobe Systems Incorporated.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

 
 
 
 

HP Universal CMDB Deployment Guide

Welcome to the HP Universal CMDB Deployment Guide

How to Work with the Interactive Guide

The questions that follow will help you customize the information that will appear in your interactive Deployment Guide.

Carefully read the instructions to the right of each set of selections—this information will guide you as to which selections are mandatory and when.

Tip: If your customized document seems to be missing information, this might mean that you have not selected a mandatory selection. You can change your selections after viewing your generated document.

What product set do you want to deploy?

HP UCMDB with Universal Discovery and HP Configuration Manager
HP UCMDB with Universal Discovery
HP UCMDB with HP Configuration Manager
HP UCMDB only
Data Flow Probe for Universal Discovery only
HP Configuration Manager only

Select a deployment option.

Note:  

  • If you are installing or upgrading UCMDB, you must select a platform and database below.

  • If you are upgrading UCMDB, and your system has Data Flow Probes defined, select also the relevant Data Flow Probe deployment (Windows/Linux/both). See below.

Do you want to install/upgrade/uninstall HP Universal CMDB?

Install HP UCMDB 10.01
Upgrade from UCMDB 9.0x to HP UCMDB 10.01 (Major Upgrade)
Upgrade from UCMDB 10.00 to HP UCMDB 10.01 (Minor Upgrade)
Uninstall HP UCMDB
Uninstall HP UCMDB and Data Flow Probes

Select a deployment option for the UCMDB Server.

Note: If you are installing or upgrading UCMDB, you must select a platform and database below.

Select a UCMDB Server platform

Windows platform
Red Hat Enterprise Linux platform

Select the platform for your UCMDB Server.

Select a UCMDB Server database

Oracle
MS-SQL

Select your database

Which Data Flow Probes to you want to install for Universal Discovery?

Install Data Flow Probe on Windows
Install Data Flow Probe on Linux

The Data Flow Probe is used to perform Universal Discovery and Integration. You can select one or both of these options.

Do you want to install/upgrade/uninstall HP Universal CMDB Configuration Manager?

Install HP UCMDB Configuration Manager 10.01
Upgrade HP UCMDB Configuration Manager 10.00 to HP UCMDB Configuration Manager 10.01
Uninstall HP UCMDB Configuration Manager

Select a deployment option for Configuration Manager.

Note:  

  • Configuration Manager can not be upgraded on a clean UCMDB Server 10.01 installation.

  • If you have any version of Configuration Manager earlier than 10.00 installed, you must upgrade to version 10.00 before upgrading to version 10.01. For details on upgrading Configuration Manager to version 10.00, refer to the Configuration Manager version 10.00 documentation.

Are you setting up a high-availability environment?

High availability environment
Non High-availability environment

High Availability is a mode of running UCMDB on a cluster of two or more servers to enable load balancing, and to ensure system availability. For more information, see UCMDB in a High Availability Environment.

View or print

You can view your customized document on the screen, or print it.

If you have a PDF print driver installed on your computer, click Print to create PDF documents that are customized according to your selections. PDF print drivers are available from several open source and third-party providers.

Check your selections

The following steps are customized according to your selections. Check that your selections are correct.

 

If any selections are not correct, click Change.

Welcome to the HP UCMDB Deployment Guide

This guide references the following HP UCMDB documentation:

Guide/Document Where can I access this guide?

HP Universal CMDB Support Matrix document

HP Universal CMDB Installation DVD root folder

HP Universal CMDB Licensing document

HP Live Network Web site

HP Universal CMDB Database Guide

HP UCMDB Database Guide

HP UCMDB Upgrader Reference

HP UCMDB Upgrader Reference

HP UCMDB Hardening Guide

HP UCMDB Hardening Guide

HP Universal CMDB Administration Guide

HP Universal CMDB Help Center (after installation)

HP Universal CMDB Modeling Guide

HP Universal CMDB Help Center (after installation)

HP Universal CMDB Data Flow Management Guide

HP Universal CMDB Help Center (after installation)

HP Universal CMDB Configuration Manager User Guide

HP Universal CMDB Help Center (after installation)

Before You Install HP UCMDB

Installation Workflow

The installation workflow contains the following main stages:

  1. Set up the CMDB database server.

    Set up the Microsoft SQL Server

    Set up the Oracle Server.

  2. Install the HP Universal CMDB Server.

    Install the UCMDB Server and configure the connection to the database.

  3. Install the HP Universal CMDB Servers.

    For High Availability, install two or more UCMDB Servers and configure their connection to the database and the load balancer.

  4. Install HP Universal CMDB Configuration Manager

    Install and configure Configuration Manager to analyze and control the data in UCMDB.

  5. Install one or more Data Flow Probes

    The Data Flow Probes are the components that enables the flow of data from the UCMDB to remote machines and back.

  6. Secure the UCMDB Server

    For details, see the HP UCMDB Hardening Guide.

  7. Secure the Data Flow Probe.

    For details, see the HP UCMDB Hardening Guide.

  8. Launch HP Universal CMDB.

Installing the UCMDB Server - Pre-Installation Considerations

Consider the following prior to installing HP Universal CMDB on Windows:

  • It is highly recommended that you plan your deployment properly before commencing installation. For details, see Before You Install HP UCMDB.

  • Do not install HP Universal CMDB on a drive that is mapped to a network resource.

  • Have the following information ready before beginning installation:

    • Information for setting the CMDB database parameters.

    • Administrator’s email address. (Optional)

    • SMTP mail server name. (Optional)

    • SMTP sender name. This name appears on alerts sent from UCMDB. (Optional)

  • HP Universal CMDB must not be installed more than once on a server even if the instances are installed in different folders or are different versions.

  • Due to Web browser limitations, the name of machine running the HP Universal CMDB Server should consist only of alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and periods (.).

    If the names of the machine running the HP Universal CMDB Server contains underscores, it may not be possible to log in to HP Universal CMDB. In this case, you should use the machine’s IP address instead of the machine name.

  • Database user and password names can contain alphanumeric characters from the database character set as well as the underscore sign. Names must begin with an alphabetic character and should not exceed 30 characters.

  • In High Availability environments, the machines used for the UCMDB Servers should have similar hardware and the same amount of memory.

  • In High Availability environments, UCMDB Servers in a cluster must work on the same port number for HTTP, HTTPS, and so on. You cannot configure the two UCMDB Servers to work on different ports.

Note the following prior to installing HP Universal CMDB on Linux:

  • It is highly recommended that you thoroughly read the introduction to this guide before commencing installation. For details, see Before You Install HP UCMDB.

  • Have the following information ready before beginning installation:

    • Information for setting the CMDB database parameters.

    • Administrator’s email address. (Optional)

    • SMTP mail server name. (Optional)

    • SMTP sender name. This name appears on alerts sent from UCMDB. (Optional)

  • HP Universal CMDB must not be installed more than once on a server even if the instances are installed in different folders or are different versions.

  • Due to Web browser limitations, the names of server machines running the HP Universal CMDB server should consist only of alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and periods (.).

    If the names of the machines running the HP Universal CMDB servers contain underscores, it may not be possible to log in to HP Universal CMDB. In this case, you should use the machine’s IP address instead of the machine name.

  • Database user and password names can contain alphanumeric characters from the database character set as well as the underscore sign. Names must begin with an alphabetic character and should not exceed 30 characters.

  • In High Availability environments, the machines used for the active and passive UCMDB Servers should have similar hardware (and the same amount of memory) and should be running the same operating system.

  • In High Availability environments, UCMDB Servers in a cluster must work on the same port number for HTTP, HTTPS, and so on. You cannot configure the two UCMDB Servers to work on different ports.

Installing the UCMDB Server - Installation

The following procedure explains how to install a UCMDB Server on a Windows machine.

Note: If you did not uninstall UCMDB 9.05 and you are installing UCMDB 10.01 on a different machine to where UCMDB 9.05 is installed, you must still stop the 9.05 instance before installing version 10.01 (Start > All Programs > HP UCMDB > Stop HP Universal CMDB Server).

  1. Locate the UCMDB executable file: HPUCMDB_Server_10.01.exe.

  2. Double-click the file to open the splash screen.

    Note: If you get a message that the digital signature is not valid, you should not install UCMDB. In this case, contact HP Software Support.

  3. Choose the locale language and click OK.

  4. The Introduction page opens. Click Next.

  5. The License Agreement page opens. Accept the terms of the end-user license agreement and click Next.

  6. The Select Installation Folder page opens.

    Accept the default destination, C:\HP\UCMDB\UCMDBServer\, or click Choose to select a different installation folder. The installation path must not contain non-English characters or spaces.

    Tip: To display the default installation folder again, click Restore Default Folder.

    Click Next.

  7. The Select Installation Type page opens. Select New Installation, and click Next.

  8. The Pre-Installation Summary page opens displaying the installation options you selected.

    If you are satisfied with the summary, click Install. A message is displayed indicating that the installation is currently being performed.

  9. When the installation is complete, the Configure HP Universal CMDB Server message is displayed.

    Click Yes to continue with the configuration.

    Click No. You will set up the database or schema later.

The following procedure explains how to install the UCMDB Server on a Linux machine.

Note: If you did not uninstall UCMDB 9.05 and you are installing UCMDB 10.01 on a different machine to where 9.05 is installed, you must still stop the 9.05 instance before installing version 10.01 (/opt/hp/UCMDB/UCMDBServer/bin/server.sh stop).

  1. Prerequisite: Apply one of the following configurations to the Linux machine:

    • Option 1:

      • In the /etc/sysctl.conffile, add or update the fs.file-max value to fs.file-max = 300000
      • At the end of the /etc/security/limits.conf file, add:

        * soft nofile 20480

        * hard nofile 20480

    • Option 2:

      Modify the /etc/profile file as follows (through terminal):

      • Old line: ulimit -S -c 0 > /dev/null 2>&1

      • New line: ulimit -n 200000 >/dev/null 2>&1

      Note: You probably need privileges to modify these files. You may need to restart the Linux machine for the changes to take effect.

  2. The HP Universal CMDB Linux installation works as a graphic-based installation. Before running the installer, configure the DISPLAY environment variable to point to a running instance of an X Windows Server.

  3. Locate the UCMDB executable file: HPUCMDB_Server_10.01.bin.

  4. Run the following executable: sh <the path to the installation file>/HPUCMDB_Server_10.01.bin.

  5. The UCMDB installation opens. Choose the locale language and click OK.

  6. The Introduction page opens. Click Next.

  7. The License Agreement page opens. Accept the terms of the end-user license agreement and click Next.

  8. The Select Installation Folder page opens.

    Accept the default path, opt/hp/UCMDB/UCMDBServer/, or click Choose to select a different installation folder. The installation path must not contain non-English characters or spaces.

    Note: To display the default installation folder again, click Restore Default Folder.

    Click Next.

  9. The Select Installation Type page opens. Select New Installation, and click Next.

  10. The Pre-Installation Summary page opens, and displays the installation options you selected.

    If you are satisfied with the summary, click Install. A message is displayed indicating that the installation is currently being performed.

  11. When the installation is complete, the Configure HP Universal CMDB Server message is displayed.

    Click Yes to continue with the configuration.

    Note: If you prefer, you can set up the database or schema later. In that case, run the configure.sh script located in opt/hp/UCMDB/UCMDBServer/bin/.

    Click No. You will set up the database or schema later.

Installing UCMDB - Configure the Database

Installing UCMDB - Complete the installation

  1. On the last page of the installation wizard, click Done to complete the installation.

  2. Start the UCMDB Server.

    Start > Programs > HP UCMDB > Start HP Universal CMDB Server

    /opt/hp/UCMDB/UCMDBServer/bin/server.sh start

    Note:  

    • If you ran the UCMDB Server Configuration Wizard as part of HP Universal CMDB Server installation, you must start HP Universal CMDB Server only after successfully setting the parameters for all the databases.

      If you ran the UCMDB Server Configuration Wizard to modify previously defined database types or connection parameters, restart the HP Universal CMDB Server and the Data Flow Probes after successfully completing the parameter modification process.

    • When you start the UCMDB Server, it may take several minutes for the process to finish and for the Server to be up and running. This period of time increases with the size of the database schema.

  3. By default, UCMDB is installed in high-availability mode. If you are not working in a High Availability environment and you want to disable high-availability mode, do the following:

    1. Access the JMX console.

    2. Select Settings Services under UCMDB.

    3. Select the setSettingValue method.

    4. In the name box, enter enable.high.availability.

    5. In the value box, enter false.

    6. Click Invoke.

Set Up High Availability Mode

A typical configuration for a High Availability environment is two or more UCMDB Servers connecting to the same database server. The server are configured to work behind a load balancer, that is, the load balancer serves as the entry point to the UCMDB Servers. All of the UCMDB Servers are active at any given time and can handle both read and write requests. Requests are distributed to the UCMDB Servers in the cluster by the load balancer. While read requests are shared evenly among all of the UCMDB Servers (Readers), only one UCMDB Server (Writer) is also responsible for write requests at one time. Any write requests received by a Reader are passed to the Writer. Moreover, any of the UCMDB Servers can take over the Writer role in the case that the Writer becomes unavailable.

Note:

  • The load balancer used for High Availability must have the ability to insert cookies and must be able to do health checks ("keepalive").

  • The instructions defined below are certified over the load balancer, F5 BIG-IP version 10.x. (F5 BIG-IP version 11.x is also supported.)

    If you are using a different load balancer, the configuration should be performed by a network administrator who has a wide knowledge about how to configure your load balancer, and similar principles should be applied.

  • The set up procedure below assumes that you already have at least one UCMDB Server installed and configured.

To set up a high availability environment:

To set up a high availability environment after upgrading from UCMDB 10.00 to UCMDB 10.01:

  1. Install one or more additional UCMDB Servers to create a cluster

    Note:  

    • The machines used for all of the UCMDB Servers in the cluster should have similar hardware (and the same amount of memory) and should be running the same operating system.

    • UCMDB Servers in the cluster must work on the same port number for HTTP, HTTPS, and so on. You cannot configure the two UCMDB Servers to work on different ports.

    Install the UCMDB Servers as you did the first UCMDB Server with one difference: when running the Server Configuration wizard to configure the database on the additional UCMDB Server, select Connect to an existing schema, and provide the details of the schema you created for the first UCMDB Server.

    For details on installing UCMDB Servers, see Installing the UCMDB Server - Installation.

  2. Complete the Server Startup

    1. If the first UCMDB Server is not started, start the process. Wait until the startup process is complete.

    2. Start the other UCMDB Servers.

  3. Configure the Load Balancer

    The load balancer is used to balance load sent to the UCMDB Servers in the cluster. Configure the load balancer as follows:

    1. Configure VIP addresses.

      On the load balancer:

      • Configure a Cluster VIP address to send requests to the whole UCMDB Server cluster.

      • Configure a Writer VIP address to send requests to the Writer only (for Universal Discovery only).

      Note: Keep a note of the defined VIP addresses.

      • When defining the communication settings between the UCMDB Server and the Data Flow Probes, always use the Writer VIP address when prompted for the UCMDB Server name.

      • When defining the communication settings between the UCMDB Server and other applications, always use the Cluster VIP address when prompted for the UCMDB Server name.

    2. Configure two identical pools of backend servers that represent all of the UCMDB Servers in the cluster. The two pools will be monitored by different health monitors. One pool will be sent requests that are intended solely for the Writer server (only for Universal Discovery), and the other pool will be sent requests that can be processed by any server in the cluster.

    3. Configure the health monitors (keepalive addresses). The health monitors check for the keepalive page of each of the UCMDB Servers.

      • Configure the following URL for the Cluster VIP address:

        /ping/

      • Configure the following URL for the Writer VIP address:

        /ping/?restrictToWriter=true

      • Possible responses from both of these URLs are Up or Down with http response codes 200 OK or 503 Service unavailable respectively.

        The expected response should be Up.

    4. Connect the health monitors to the respective UCMDB Server pools configured above.

    5. Configure "session stickiness" on the load balancer:

      1. Configure the load balancer to insert cookies to the responses sent back to UCMDB clients.

        Using the Insert method, add a persistence profile of type cookie for each VIP address.

        Note: The cookie name and value are unimportant, as long as the load balancer knows how to maintain stickiness with the cookies it sends out.

      2. Important! If the UCMDB clients are behind a forward proxy that re-uses client connections, the load balancer must be configured to read all request headers so that the correct session cookie will be parsed and the request will be routed to the correct UCMDB backend server. On the F5 BigIP load balancer this is done as follows:

        1. Create a OneConnect profile, with the following mask: 255.255.255.255

        2. Attach the OneConnect profile to the Virtual Server that represents the whole cluster.

    6. If the VIP is configured to accept secure connections and the load balancer forwards the requests to the UCMDB servers over HTTP, you must configure redirect rewrites. In the F5 UI, configure the HTTP profile associated with the VIP to rewrite all redirects by enabling the following option: Redirect Rewrite select All.

  4. Configure Data Flow Probes

    When you install a Data Flow Probe, use the load balancer's Writer VIP address when defining the HP Universal CMDB Server name.

    If you already have a Data Flow Probe installed:

    1. Stop the Probe.

    2. In the <probe installation directory>/conf/DataFlowProbe.properties file, change the serverName attribute to point to the Writer VIP address.

    3. Restart the Probe.

Uninstalling UCMDB

  1. To uninstall HP Universal CMDB:

    Windows
    1. On the UCMDB Server machine, select Start > All Programs > HP UCMDB > Uninstall HP Universal CMDB Server. The Uninstall HP Universal CMDB Server dialog box appears together with a message giving you the option of either removing the server configuration files or not.

    2. Click Uninstall.

    3. When uninstall is complete, a confirmation message is displayed. Click Done to complete the uninstall process.

    Linux
    1. On the UCMDB Server machine, execute the Uninstall_UCMDBServer script from the UninstallerData subfolder of the Installation folder. The Uninstall HP Universal CMDB Server dialog box appears together with a message giving you the option of either removing the server configuration files or not.

    2. From the same location, select Uninstall to uninstall the HP Universal CMDB Server.

    3. When uninstall is complete, a confirmation message is displayed. Click Done to complete the uninstall process.

  2. To uninstall a Data Flow Probe:

    On Windows

    On the machine where the Probe is installed:

    1. Stop the Probe: Start > All Programs > HP UCMDB > Stop Data Flow Probe

    2. Uninstall the Probe: Start > All Programs > HP UCMDB > Uninstall Data Flow Probe. When the Probe has finished being uninstalled, delete the folder that contained the Probe: C:\hp\UCMDB\DataFlowProbe

    On Linux

    On the machine where the Probe is installed:

    1. Stop the Probe: /opt/hp/UCMDB/DataFlowProbe/bin/ProbeGateway.sh stop

    2. Uninstall the Probe. Do one of the following:

      • In shell, execute:

        sh /opt/hp/UCMDB/DataFlowProbe/UninstallerData/Uninstall_Discovery_Probe

      • Double-click the Uninstall_Discovery_Probe file in the file system.

      • Delete the /opt/hp/UCMDB/DataFlowProbe/ folder.

Upgrading UCMDB to Version 10.01 - Introduction

The instructions that follow explain how to upgrade HP Universal CMDB 9.0x to HP Universal CMDB 10.01.

The instructions that follow explain how to upgrade HP Universal CMDB 10.00 to HP Universal CMDB 10.01.

Note:  

  • The upgrade process runs offline, during which time all resources and data are transformed from 9.0x to work with the version 10.01 system.

  • When upgrading a high availability environment to the 10.01 environment, the active and passive servers in the cluster all become active servers, that is, they all run as active servers while providing high availability at the same time.

  • It is recommended to read through the whole procedure before commencing the upgrade process.

Upgrading UCMDB - Prerequisites

  • If you have any version of HP Universal CMDB lower than 9.05, you must upgrade to version 9.05 before upgrading to version 10.01. For details on upgrading HP Universal CMDB to version 9.05, refer to the UCMDB 9.05 deployment documentation.

  • Check Hardware and OS requirements. For details, see the HP Universal CMDB Support Matrix document.

Upgrading UCMDB - Prepare the Databases

  • The upgrade requires approximately 250% of the space normally required for the CMDB schema. Make sure you allocate this space.

  • Back up the version 9.05 CMDB and History schemas. In UCMDB 10.01, the History and CMDB schemas are combined into one schema. Back up both schemas individually to ensure correct binding during the upgrade to version 10.01.

  • Make sure that the database user with which you are connecting to the old schemas (both CMDB and History schemas) has the CREATE TYPE privileges.

    If not, grant the privileges with a database admin user: GRANT CREATE TYPE TO <USER_NAME>

  • Make sure that the character set of the backed up database schemas matches the character set of the destination database server.

Note: As an added precaution, run your current UCMDB version against the backed up schemas to verify that they are not corrupt. Ensure that the database settings for the backed schemas are the same as those for the original schemas.

For details on working with the CMDB, see the HP UCMDB Database Guide.

Upgrading UCMDB - Save Modified Integration (Federation) Adapters

For all out-of-the-box adapters: If you modified an adapter configuration in your previous version, it is strongly recommended that you save all adapter files from that version, and redo the modifications on the adapter files of version 10.01.

For example, if you had saved adapter defaults, copy aside the relevant part of the adapter XML (the tag “<adapterTemplates>”). After the deployment, copy this tag back to the XML of the relevant adapter.

Note: All adapters must be compatible with the new Universal Data Model. If you made changes to existing out-of-the-box adapters, you must make the same changes to the adapter files in version 10.01. Do not copy files from your previous version and overwrite the files in version 10.01.

Upgrading UCMDB - Save the Encryption Key

UCMDB uses the encryption key to encrypt credential information and to send sensitive credential information to probes. For security reasons, this encryption key is stored on the file system, and not in the database.

Copy the encryption key from the UCMDB Server. The encryption key is located in:

C:\hp\UCMDB\UCMDBServer\root\lib\server\discovery\key.bin

Upgrading UCMDB - Back up the secure keystore

Back up the C:\hp\UCMDB\UCMDBServer\conf\security folder. This will be copied into the same location in version 10.01, after the upgrade.

Upgrading UCMDB - Save JMX Hardening Configuration

If the Java JMX access hardening was performed:

  1. Edit the file permissions for c:\hp\UCMDB\UCMDBServer\bin\jre\lib\management\jmxremote.password so that the user you are logged in with can edit it.
  2. Save the file outside of the UCMDB installation folder.

Upgrading UCMDB - Uninstall previous versions of UCMDB

Note:  

  • If you intend to install the UCMDB 10.01 Server on the machine where the UCMDB 9.05 Server is installed, you must first uninstall the UCMDB 9.05 Server, as described in the procedure below.

    If you intend to install the UCMDB 10.01 Server on a different machine to where the UCMDB 9.05 Sever is installed, you do not need to uninstall the UCMDB 9.05 Server but you must stop the server before beginning the UCMDB 10.01 Server installation, as described in Step 1 below.

  • When upgrading an environment that is in high-availability mode, uninstall all the UCMDB Servers (the active server and the passive servers) in the cluster. All the server in the upgraded UCMDB 10.01 cluster will be active servers, while providing high availability at the same time.

  1. Stop the UCMDB Server:

    Start > All Programs > HP UCMDB > Stop HP Universal CMDB Server.

    /opt/hp/UCMDB/UCMDBServer/bin/server.sh stop

  2. Uninstall the UCMDB Server:

    Note: In a high-availability environment, you must uninstall the active server and all the passive servers.

    Note: If you intend to install the UCMDB 10.01 Server on a different machine to where the UCMDB 9.05 Sever is installed, you do not need to uninstall the UCMDB 9.05 Server. Skip to the next step: Upgrading UCMDB - Uninstall the Data Flow Probes.

    1. From the Start menu, choose All Programs > HP UCMDB > Uninstall HP Universal CMDB Server. The Uninstall HP Universal CMDB Server dialog box appears together with a message giving you the option of either removing the server configuration files or not.

    2. Click Uninstall.

    3. When uninstall is complete, a confirmation message is displayed. Click Done to complete the uninstall process.

    1. Execute the Uninstall_UCMDBServer script from the UninstallerData subfolder of the Installation folder. The Uninstall HP Universal CMDB Server dialog box appears together with a message giving you the option of either removing the server configuration files or not.

    2. From the same location, select Uninstall to uninstall the UCMDB Server.

    3. When uninstall is complete, a confirmation message is displayed. Click Done to complete the uninstall process.

  3. Remove the entire C:\hp\UCMDB folder from the UCMDB Server machine.

  4. Remove the entire opt/hp/UCMDB folder from the UCMDB Server machine.

  5. Restart the machine.

Upgrading UCMDB - Uninstall the Data Flow Probes

To uninstall a Data Flow Probe:

On Windows

On the machine where the Probe is installed:

  1. Stop the Probe: Start > All Programs > HP UCMDB > Stop Data Flow Probe

  2. Uninstall the Probe: Start > All Programs > HP UCMDB > Uninstall Data Flow Probe. When the Probe has finished being uninstalled, delete the folder that contained the Probe: C:\hp\UCMDB\DataFlowProbe

On Linux

On the machine where the Probe is installed:

  1. Stop the Probe: /opt/hp/UCMDB/DataFlowProbe/bin/ProbeGateway.sh stop

  2. Uninstall the Probe. Do one of the following:

    • In shell, execute:

      sh /opt/hp/UCMDB/DataFlowProbe/UninstallerData/Uninstall_Discovery_Probe

    • Double-click the Uninstall_Discovery_Probe file in the file system.

    • Delete the /opt/hp/UCMDB/DataFlowProbe/ folder.

Upgrading UCMDB - Install the UCMDB 10.01 Server

The following procedure explains how to install a UCMDB Server on a Windows machine.

Note: If you did not uninstall UCMDB 9.05 and you are installing UCMDB 10.01 on a different machine to where UCMDB 9.05 is installed, you must still stop the 9.05 instance before installing version 10.01 (Start > All Programs > HP UCMDB > Stop HP Universal CMDB Server).

  1. Locate the UCMDB executable file: HPUCMDB_Server_10.01.exe.

  2. Double-click the file to open the splash screen.

    Note: If you get a message that the digital signature is not valid, you should not install UCMDB. In this case, contact HP Software Support.

  3. Choose the locale language and click OK.

  4. The Introduction page opens. Click Next.

  5. The License Agreement page opens. Accept the terms of the end-user license agreement and click Next.

  6. The Select Installation Folder page opens.

    Accept the default destination, C:\HP\UCMDB\UCMDBServer\, or click Choose to select a different installation folder. The installation path must not contain non-English characters or spaces.

    Tip: To display the default installation folder again, click Restore Default Folder.

    Click Next.

  7. The Select Installation Type page opens. Select New Installation, and click Next.

  8. The Pre-Installation Summary page opens displaying the installation options you selected.

    If you are satisfied with the summary, click Install. A message is displayed indicating that the installation is currently being performed.

  9. When the installation is complete, the Configure HP Universal CMDB Server message is displayed.

    Click Yes to continue with the configuration.

    Click No. You will set up the database or schema later.

The following procedure explains how to install the UCMDB Server on a Linux machine.

Note: If you did not uninstall UCMDB 9.05 and you are installing UCMDB 10.01 on a different machine to where 9.05 is installed, you must still stop the 9.05 instance before installing version 10.01 (/opt/hp/UCMDB/UCMDBServer/bin/server.sh stop).

  1. Prerequisite: Apply one of the following configurations to the Linux machine:

    • Option 1:

      • In the /etc/sysctl.conffile, add or update the fs.file-max value to fs.file-max = 300000
      • At the end of the /etc/security/limits.conf file, add:

        * soft nofile 20480

        * hard nofile 20480

    • Option 2:

      Modify the /etc/profile file as follows (through terminal):

      • Old line: ulimit -S -c 0 > /dev/null 2>&1

      • New line: ulimit -n 200000 >/dev/null 2>&1

      Note: You probably need privileges to modify these files. You may need to restart the Linux machine for the changes to take effect.

  2. The HP Universal CMDB Linux installation works as a graphic-based installation. Before running the installer, configure the DISPLAY environment variable to point to a running instance of an X Windows Server.

  3. Locate the UCMDB executable file: HPUCMDB_Server_10.01.bin.

  4. Run the following executable: sh <the path to the installation file>/HPUCMDB_Server_10.01.bin.

  5. The UCMDB installation opens. Choose the locale language and click OK.

  6. The Introduction page opens. Click Next.

  7. The License Agreement page opens. Accept the terms of the end-user license agreement and click Next.

  8. The Select Installation Folder page opens.

    Accept the default path, opt/hp/UCMDB/UCMDBServer/, or click Choose to select a different installation folder. The installation path must not contain non-English characters or spaces.

    Note: To display the default installation folder again, click Restore Default Folder.

    Click Next.

  9. The Select Installation Type page opens. Select New Installation, and click Next.

  10. The Pre-Installation Summary page opens, and displays the installation options you selected.

    If you are satisfied with the summary, click Install. A message is displayed indicating that the installation is currently being performed.

  11. When the installation is complete, the Configure HP Universal CMDB Server message is displayed.

    Click Yes to continue with the configuration.

    Note: If you prefer, you can set up the database or schema later. In that case, run the configure.sh script located in opt/hp/UCMDB/UCMDBServer/bin/.

    Click No. You will set up the database or schema later.

Installing UCMDB - Complete the installation

  1. On the last page of the installation wizard, click Done to complete the installation.

  2. Start the UCMDB Server.

    Start > Programs > HP UCMDB > Start HP Universal CMDB Server

    /opt/hp/UCMDB/UCMDBServer/bin/server.sh start

    Note:  

    • If you ran the UCMDB Server Configuration Wizard as part of HP Universal CMDB Server installation, you must start HP Universal CMDB Server only after successfully setting the parameters for all the databases.

      If you ran the UCMDB Server Configuration Wizard to modify previously defined database types or connection parameters, restart the HP Universal CMDB Server and the Data Flow Probes after successfully completing the parameter modification process.

    • When you start the UCMDB Server, it may take several minutes for the process to finish and for the Server to be up and running. This period of time increases with the size of the database schema.

  3. By default, UCMDB is installed in high-availability mode. If you are not working in a High Availability environment and you want to disable high-availability mode, do the following:

    1. Access the JMX console.

    2. Select Settings Services under UCMDB.

    3. Select the setSettingValue method.

    4. In the name box, enter enable.high.availability.

    5. In the value box, enter false.

    6. Click Invoke.

Upgrading UCMDB - Upgrade UCMDB Version 10.00 to 10.01

The following procedure explains how to upgrade HP UCMDB 10.00 to HP UCMDB 10.01 on a Windows platform.

The following procedure explains how to upgrade HP UCMDB 10.00 to HP UCMDB 10.01 on a Linux platform.

  1. Stop the active and passive UCMDB 10.00 Servers.

    Stop the UCMDB 10.00 Server before starting the 10.01 installation.

  2. If the Integration Service is running, stop the service.

  3. Run the UCMDB 10.01 installer on each of the UCMDB Servers:

    Run the UCMDB 10.01 installer:

    1. Locate the UCMDB executable file: HPUCMDB_Server_10.01.exe, and double-click it to open the splash screen.

      Note: If you get a message that the digital signature is not valid, you should not install UCMDB. In this case, contact HP Software Support.

      Locate the UCMDB executable file: HPUCMDB_Server_10.01.bin, and run the following executable:

      sh <the path to the installation file>/HPUCMDB_Server_10.01.bin

    2. Choose the locale language and click OK.

    3. The Introduction page opens. Click Next.

    4. The License Agreement page opens. Accept the terms of the end-user license agreement and click Next.

    5. On the Select Installation Folder page, select the existing UCMDB 10.00 installation folder.

    6. On the Select Installation Type page of the installer, select Update from 10.00.

  4. Complete the installation process.

    Note: The minimum supported HP Discovery and Integration Content Pack version for UCMDB 10.01, Content Pack 12.00, is automatically installed.

  5. You do not need to run the Server Configuration wizard, because the system uses the schemas from the previous installation.

  6. If you imported SSL certificates in UCMDB 10.00, extract the certificates from

    C:\hp\UCMDB\UCMDBServer\old

    /opt/hp/UCMDB/UCMDBServer/old

    and import them into

    C:\hp\UCMDB\UCMDBServer\bin\jre\lib\security\cacert

    /opt/hp/UCMDB/UCMDBServer/bin/jre/lib/security/cacert

    For details, see the section describing enabling SSL on the Client SDK in the HP UCMDB Hardening Guide.

  7. If you stopped the Integration Service above you must clear the Probe data:

    In C:\hp\UCMDB\UCMDBServer\integrations\tools run clearProbeData.bat

    Run /opt/hp/UCMDB/UCMDBServer/integrations/tools/clearProbeData.sh

  8. Start one of the UCMDB Servers. When the UCMDB Server is up (has the Up status), start the other UCMDB Server.

    Note: In UCMDB 10.01, all UCMDB Servers in a High Availability environment are active, while also providing High Availability in case of server failure.

    Start up the UCMDB 10.01 server.

    For details on server status, see HP UCMDB Services.

  9. If you stopped the Integration Service, restart it.

Set Up High Availability Mode

A typical configuration for a High Availability environment is two or more UCMDB Servers connecting to the same database server. The server are configured to work behind a load balancer, that is, the load balancer serves as the entry point to the UCMDB Servers. All of the UCMDB Servers are active at any given time and can handle both read and write requests. Requests are distributed to the UCMDB Servers in the cluster by the load balancer. While read requests are shared evenly among all of the UCMDB Servers (Readers), only one UCMDB Server (Writer) is also responsible for write requests at one time. Any write requests received by a Reader are passed to the Writer. Moreover, any of the UCMDB Servers can take over the Writer role in the case that the Writer becomes unavailable.

Note:

  • The load balancer used for High Availability must have the ability to insert cookies and must be able to do health checks ("keepalive").

  • The instructions defined below are certified over the load balancer, F5 BIG-IP version 10.x. (F5 BIG-IP version 11.x is also supported.)

    If you are using a different load balancer, the configuration should be performed by a network administrator who has a wide knowledge about how to configure your load balancer, and similar principles should be applied.

  • The set up procedure below assumes that you already have at least one UCMDB Server installed and configured.

To set up a high availability environment:

To set up a high availability environment after upgrading from UCMDB 10.00 to UCMDB 10.01:

  1. Install one or more additional UCMDB Servers to create a cluster

    Note:  

    • The machines used for all of the UCMDB Servers in the cluster should have similar hardware (and the same amount of memory) and should be running the same operating system.

    • UCMDB Servers in the cluster must work on the same port number for HTTP, HTTPS, and so on. You cannot configure the two UCMDB Servers to work on different ports.

    Install the UCMDB Servers as you did the first UCMDB Server with one difference: when running the Server Configuration wizard to configure the database on the additional UCMDB Server, select Connect to an existing schema, and provide the details of the schema you created for the first UCMDB Server.

    For details on installing UCMDB Servers, see Installing the UCMDB Server - Installation.

  2. Complete the Server Startup

    1. If the first UCMDB Server is not started, start the process. Wait until the startup process is complete.

    2. Start the other UCMDB Servers.

  3. Configure the Load Balancer

    The load balancer is used to balance load sent to the UCMDB Servers in the cluster. Configure the load balancer as follows:

    1. Configure VIP addresses.

      On the load balancer:

      • Configure a Cluster VIP address to send requests to the whole UCMDB Server cluster.

      • Configure a Writer VIP address to send requests to the Writer only (for Universal Discovery only).

      Note: Keep a note of the defined VIP addresses.

      • When defining the communication settings between the UCMDB Server and the Data Flow Probes, always use the Writer VIP address when prompted for the UCMDB Server name.

      • When defining the communication settings between the UCMDB Server and other applications, always use the Cluster VIP address when prompted for the UCMDB Server name.

    2. Configure two identical pools of backend servers that represent all of the UCMDB Servers in the cluster. The two pools will be monitored by different health monitors. One pool will be sent requests that are intended solely for the Writer server (only for Universal Discovery), and the other pool will be sent requests that can be processed by any server in the cluster.

    3. Configure the health monitors (keepalive addresses). The health monitors check for the keepalive page of each of the UCMDB Servers.

      • Configure the following URL for the Cluster VIP address:

        /ping/

      • Configure the following URL for the Writer VIP address:

        /ping/?restrictToWriter=true

      • Possible responses from both of these URLs are Up or Down with http response codes 200 OK or 503 Service unavailable respectively.

        The expected response should be Up.

    4. Connect the health monitors to the respective UCMDB Server pools configured above.

    5. Configure "session stickiness" on the load balancer:

      1. Configure the load balancer to insert cookies to the responses sent back to UCMDB clients.

        Using the Insert method, add a persistence profile of type cookie for each VIP address.

        Note: The cookie name and value are unimportant, as long as the load balancer knows how to maintain stickiness with the cookies it sends out.

      2. Important! Since F5 BIG-IP version 10.x only adds a session cookie to first request per connection to the server, you must do the following:

        1. Log into UCMDB.

        2. Go to Administration > Infrastructure Settings, and change the Force connection closing for SDK clients to true.

          When this setting is set to true, the UCMDB SDK clients add a Connection:close header to each authentication request and class download request sent to the server. This way the load balancer will think this is a first request in a connection and add the session cookie to the response.

        Note: This is relevant to load balancers which, like F5 BIG-IP version 10.x, add a session cookie to the first request per connection to the server only.

        If the load balancer you are using adds a session cookie to every response, Force connection closing for SDK clients should be set to false (as is the default). In this case, setting it to true can lead to a decline in system performance.

  4. Configure Data Flow Probes

    When you install a Data Flow Probe, use the load balancer's Writer VIP address when defining the HP Universal CMDB Server name.

    If you already have a Data Flow Probe installed:

    1. Stop the Probe.

    2. In the <probe installation directory>/conf/DataFlowProbe.properties file, change the serverName attribute to point to the Writer VIP address.

    3. Restart the Probe.

Data Flow Probe - Notes Before you install

Note the following before installing the Data Flow Probe:

  • HP UCMDB and the Data Flow Probe should be installed within the company’s firewall and should not be deployed via the Internet.

  • The Probe can be installed before or after you install the HP Universal CMDB Server. However, during the installation of the Probe, you need to provide the UCMDB Server name, so it is preferable to install the UCMDB Server before installing the Probe.

  • When setting up a high availability environment, have your load balancer's Writer virtual IP address available because you will need this when defining the UCMDB Server name.

  • Verify that you have enough hard disk space available before beginning installation. For details, see the section about Data Flow Probe requirements in the HP Universal CMDB Support Matrix document.

  • For details on licensing, see the HP Universal CMDB Licensing document.

Data Flow Probe on Windows

  • Before installing the Probe on a Windows 2008 machine, a user must have full control permissions on the file system. In addition, after installing the Probe, verify that the user who is running the Probe has full administration permissions on the file system where the Probe is installed.

Data Flow Probe on Linux

  • The Probe on Linux is intended for the CMS Sync integration only.

  • The Probe on Linux cannot be used for discovery.

  • An instance of MySQL database must not be running on the machine on which you are installing the Probe. If an instance exists, you must disable it.

  • To install the Data Flow Probe on Linux, you must have root permissions to the Linux machine.

Data Flow Probe - Ports

Before you install the Data Flow Probe, ensure that the relevant ports are open.

Data Flow Probe - Windows Installation

The following procedure explains how to install the Data Flow Probe on a Windows machine.

Note: Ensure that you have read the important notes and considerations above before you install the Data Flow Probe.

To install the Data Flow Probe:

  1. Insert the HP Universal CMDB 10.01 Setup Windows DVD into the drive from which you are installing the Probe. If you are installing from a network drive, connect to the drive.

  2. Double-click the <DVD root folder>\UCMDB10\HPUCMDB_DataFlowProbe_10.01.exe file.

  3. A progress bar is displayed. After the initial process is complete, the splash screen opens. Choose the locale language and click OK.

  4. The Introduction page opens. Click Next.

  5. The License Agreement page opens.

    Accept the terms of the end-user license agreement and click Next.

  6. The Setup Type page opens.

    Select Full Probe installation. This installs the Data Flow Probe with all its components, including the Inventory Tools (Analysis Workbench, Viewer, SAI Editor, and MSI Scanner) required for application teaching.

    Note: The Inventory Tools option is used to install only the Inventory Tools. For details about application teaching, see the HP Universal CMDB Data Flow Management Guide.

    Click Next.

  7. The Select Installation Folder page opens.

    Accept the default installation folder, c:\hp\UCMDB\DataFlowProbe, or click Choose to select a different installation folder.

    Note:  

    • The installation folder that you select must be empty.

    • To restore the default installation folder, after selecting a different folder, click Restore Default Folder.

  8. The Data Flow Probe Configuration page opens,enabling you to configure the details of the application server to which the Data Flow Probe will report.

    • Under Application to report to select HP Universal CMDB and in the Application Server address box, enter the name or the IP address of the HP Universal CMDB server with which the Probe is to connect.

      Note: For a High Availability environment, use the Writer virtual IP address of the load balancer.

    • In the Data Flow Probe address box, enter the IP address or DNS name of the machine on which you are currently installing the Probe, or accept the default.

      Note: If the Data Flow Probe machine has more than one IP address, enter a specific IP address, and not the DNS name.

    Click Next.

    Note: If you do not enter the address of the application server, or if there is no TCP connection to the application server via default ports (8080,8443,80) (possibly because the application server has not fully started yet), a message is displayed. You can choose to continue to install the Probe without entering the address, or return to the previous page to add the address.

  9. A second configuration page opens, enabling you to configure an identifier for the Probe.

    • In the Data Flow Probe Identifier box, enter a name for the Probe that is used to identify it in your environment.

      Note:  

      • The Probe identifier is case sensitive, must be unique for each Probe in your deployment, and it must not exceed 50 characters.

      • When installing the Probe in separate mode, that is, the Probe Gateway and Probe Manager are installed on separate machines, you must give the same name (case-sensitive) to the Probe Gateway and all its Probe Managers. This name appears in UCMDB as a single Probe node. Failure to give the same name may prevent jobs from running.

    • Select Use Default CMDB Domain to use the default UCMDB IP address or machine name, as defined in the UCMDB Server installation.

      The Default UCMDB Domain is also configurable in UCMDB's Infrastructure Settings module. For details, see the HP Universal CMDB Administration Guide.

    Click Next.

  10. If you cleared the Use Default CMDB Domain box in the previous step, the Domain Configuration page opens.

    • Data Flow Probe domain type. Select the type of domain on which the Probe is to run:

      • Customer. Select if you are installing one or more Probes in your deployment.

        Note: Always use this option for new installations.

      • External. Select this option for upgraded 6.x systems.

    • Data Flow Probe domain. If you are not using the default domain defined in UCMDB enter the name of the domain here.

      Note: For external domains, this value must be identical to the Data Flow Probe Identifier defined in the previous step.

    Click Next.

  11. The HP UCMDB Data Flow Probe Working Mode page opens.

    You can run the Probe Gateway and Probe Manager as one Java process or as separate processes. Run them as separate processes in deployments that need better load balancing and to overcome network issues.

    Click No to run the Probe Gateway and Probe Manager as one process.

    Click Yes to run the Probe Gateway and Probe Manager as two processes on separate machines.

    Note: When running the Probe Gateway and Probe Manager as two processes ensure the following:

    • At least one Probe Gateway component must be installed. The Probe Gateway is connected to the UCMDB Server. It receives tasks from the Server and communicates with the collectors (Probe Managers).

    • Several Probe Managers can be installed. The Probe Managers run jobs and gather information from networks.

    • The Probe Gateway should contain a list of attached Probe Managers.

    • The Probe Managers must know to which Probe Gateway they are attached.

    Click Next.

  12. The HP UCMDB Data Flow Probe Memory Size page opens.

    Define the minimum and maximum memory, in megabytes, to be allocated to the Probe.

    Note: For information about changing the maximum heap size value at a later point in time, see the HP Universal CMDB Data Flow Management Guide.

    Click Next.

  13. The MySQL Account Configuration page opens.

    • The MySQL Data Flow Probe account is used by the Data Flow Probe to connect to the MySQL database. This account is less privileged compared to the MySQL root account. Its password is encrypted in the DataFlowProbe.properties configuration file.

      Enter the password for the MySQL Data Flow Probe account and enter it a second time for confirmation.

      Note: Changing this password requires an update to the DataFlowProbe.properties file.

    • The MySQL root account is the account used to administer the MySQL database. When set, it may need to be provided to scripts under the Probe's installation.

      Enter the password for the MySQL Data Flow Probe account, and enter it a second time for confirmation.

      Note: Changing the root account password does not affect operation of the Probe.

    Click Next.

  14. The Account Configuration for Uploading Scan Files page opens. This is used for Manual Scanner Deployment mode. It enables uploading scan files directly to the XML Enricher's incoming directory on the Data Flow Probe using HTTP or HTTPS.

    Enter the user name and password for this account, and enter the password a second time for confirmation. The default user name is UploadScanFile.

    Click Next.

  15. The Pre-Installation Summary page opens.

    Review the selections you have made and click Install to complete the installation of the Probe.

  16. When the installation is complete, the Install Complete page opens.

    Note: Any errors occurring during installation are written to the following file: C:\hp\UCMDB\DataFlowProbe\HP_UCMDB_Data_Flow_Probe_InstallLog.log

    Click Done.

  17. Note:  

    • If you installed the Probe on a Windows 2008 machine:

      1. Locate the wrapper.exe file in the C:\hp\UCMDB\DataFlowProbe\bin folder.

      2. Right-click the wrapper.exe file and select Properties.

      3. In the Compatibility tab:

        1. Select Compatibility mode.

        2. Select Run this program in compatibility for: Windows XP (Service Pack 2).

        3. Select Run this program as administrator.

    • After installing the Probe, we recommend disabling virus scanning on the main directory that is used to store your MySQL table data. The default directory is C:\hp\UCMDB\DataFlowProbe\MySQL\.

  18. Start the Probe: Select Start > All Programs > HP UCMDB > Start Data Flow Probe.

    To start the Probe from the console, at the command prompt execute the following script: C:\hp\UCMDB\DataFlowProbe\bin\gateway.bat console.

    Note:  

    • In order for the Probe to connect to the application server, the application server must be fully started.

    • The Probe is displayed in UCMDB in the Data Flow Management module, under Data Flow Probe Setup > <Domain> > Probes.

  19. If you selected to run the Probe Gateway and Probe Manager as two processes on separate machines, you must configure the Probe Gateway and Probe Manager components. For details, see Data Flow Probe - Configure the Gateway and Manager Components below.

Data Flow Probe - Linux Installation

The following procedure explains how to install the Data Flow Probe on a Linux platform.

Note: Ensure that you have read the important notes and considerations above before you install the Data Flow Probe.

To install the Data Flow Probe:

  1. To run the installation wizard, execute the following command:

    sh <path to the installer>/HPUCMDB_DataFlowProbe_10.00Linux.bin

    The following commands are executed:

    Preparing to install...
    Extracting the JRE from the installer archive...
    Unpacking the JRE...
    Extracting the installation resources from the installer 
    archive...
    Configuring the installer for this system's environment...
    Launching installer...
  2. When the initial process is complete, the splash screen opens. Choose the locale language and click OK.
  3. The Introduction page opens. Click Next.

  4. The License Agreement page opens.

    Accept the terms of the end-user license agreement and click Next.

  5. The Select Installation Folder page opens.

    Accept the default installation folder, opt/hp/UCMDB/DataFlowProbe, or click Choose to select a different installation folder.

    Note:  

    • You can change the location of the installation, but the folder must be located under /opt/.
    • If you selected a different folder and you want to restore the default installation folder, click Restore Default Folder.

    Click Next.

  6. The Data Flow Probe Configuration page opens, enabling you to configure the details of the application server to which the Data Flow Probe will report.

    • Under Application to report to select HP Universal CMDB and in the Application Server address box, enter the name or the IP address of the HP Universal CMDB server with which the Probe is to connect.

      Note: For a High Availability environment, use the Writer virtual IP address of the load balancer.

    • In the Data Flow Probe address box, enter the IP address or DNS name of the machine on which you are currently installing the Probe, or accept the default.

      Note: If the Data Flow Probe machine has more than one IP address, enter a specific IP address, and not the DNS name.

      Click Next.

      Note: If you do not enter the address of the application server, or if there is no TCP connection to the application server via default ports (8080,8443,80) (possibly because the application server has not fully started yet), a message is displayed. You can choose to continue to install the Probe without entering the address, or return to the previous page to add the address.

  7. A second configuration page opens, enabling you to configure an identifier for the Probe.

    • In the Data Flow Probe Identifier box, enter a name for the Probe that is used to identify it in your environment.

      Note: The Probe identifier is case sensitive, must be unique for each Probe in your deployment, and it must not exceed 50 characters.

    • Select Use Default CMDB Domain to use the default UCMDB IP address or machine name, as defined in the UCMDB Server installation.

      The Default UCMDB Domain is also configurable in UCMDB's Infrastructure Settings module. For details, see the HP Universal CMDB Administration Guide.

    Click Next.

  8. If you cleared the Use Default CMDB Domain box in the previous step, the HP UCMDB Data Flow Probe Domain Configuration page opens.

    • Data Flow Probe domain type. Select the type of domain on which the Probe is to run:

      • Customer. Select if you are installing one or more Probes in your deployment.

        Note: Always use this option for new installations.

      • External. Select this option for upgraded 6.x systems.

    • Data Flow Probe domain. If you are not using the default domain defined in UCMDB enter the name of the domain here.

      Note: For external domains, this value must be identical to the Data Flow Probe Identifier defined in the previous step.

    Click Next.

  9. The HP UCMDB Data Flow Probe Memory Size page opens.

    Define the minimum and maximum memory, in megabytes, to be allocated to the Probe.

    Note: For information about changing the maximum heap size value at a later point in time, see the HP Universal CMDB Data Flow Management Guide.

    Click Next.

  10. The MySQL Account Configuration page opens.

    • The MySQL Data Flow Probe account is used by the Data Flow probe to connect to the MySQL database. This account is less privileged compared to the MySQL root account. Its password is encrypted in the DataFlowProbe.properties configuration file.

      Enter the password for the MySQL Data Flow Probe account and enter it a second time for confirmation.

      Note: Changing this password requires a update to the DataFlowProbe.properties file.

    • The MySQL root account is the one used to administer the MySQL database. When set, it may need to be provided to scripts under the Probe's installation.

      Enter the password for the MySQL Data Flow Probe account and enter it a second time for confirmation.

      Note: Changing the root account password does not affect operation of the Probe.

  11. The Account Configuration for Uploading Scan Files page opens. This is used for Manual Scanner Deployment mode. It enables uploading scan files directly to the XML Enricher's incoming directory on the Data Flow Probe using HTTP or HTTPS.

    Enter the user name and password for this account, and enter the password a second time for confirmation. The default user name is UploadScanFile.

    Click Next.

  12. The Pre-Installation Summary page opens. Review the selections you have made and click Install to complete the installation of the Probe.

  13. When installation is complete the Install Complete page opens.

    Note: Any errors occurring during installation are written to the following file:

    /opt/hp/UCMDB/DataFlowProbe/HP_UCMDB_Data_Flow_Probe_InstallLog.log. If you installed the Probe to another directory under /opt/, the log file is located there.

    Click Done.

    Note: After installing the Probe, we recommend disabling virus scanning on the main directory that is used to store your MySQL table data. The default directory is /opt/hp/UCMDB/DataFlowProbe/MySQL/.

  14. Activate the Probe.

    Note:  

    • The user running the Probe service must be a member of the Administrators group.

    • In order for the Probe to connect to the application server, the application server must be fully started.

    Execute the following command:

    /opt/hp/UCMDB/DataFlowProbe/bin/ProbeGateway.sh start

    To activate the Probe in a console, execute the following command:

    /opt/hp/UCMDB/DataFlowProbe/bin/ProbeGateway.sh console

    Tip: Probes installed on Linux machines are displayed when creating new integration points in Data Flow Management's Integration Studio. That is, this Probe does not appear in the Data Flow Probe Setup window. For details, see the section describing creating integration points in the HP Universal CMDB Data Flow Management Guide.

Data Flow Probe - Configure the Gateway and Manager Components

When the Probe Manager and Probe Gateway run as separate processes on two machines, set up the Data Flow Probe as follows:

Note:  

  • The instructions below are relevant for Probes installed on Windows machines only.
  • The Probe Manager name in both the probeMgrList.xml and DataFlowProbe.properties files must be identical. The name is case sensitive.
  1. Set up the Probe Gateway machine.

    1. Open the following file:

      C:\hp\UCMDB\DataFlowProbe\conf\probeMgrList.xml

    2. Locate the line beginning <probeMgr ip= and add the Manager machine name or IP address, for example:

      <probeMgr ip="OLYMPICS08">
    3. Open the following file:

      C:\hp\UCMDB\DataFlowProbe\conf\DataFlowProbe.properties

    4. Locate the lines beginning appilog.collectors.local.ip = and appilog.collectors.probe.ip = and enter the Gateway machine name or IP address, for example:

      appilog.collectors.local.ip = STARS01
      appilog.collectors.probe.ip = STARS01
  2. Set up the Probe Manager machine.

    In C:\hp\UCMDB\DataFlowProbe\conf\DataFlowProbe.properties:

    1. Locate the line beginning appilog.collectors.local.ip = and enter the Manager machine name or IP address, for example:

      appilog.collectors.local.ip = OLYMPICS08
    2. Locate the line beginning appilog.collectors.probe.ip = and enter the Gateway machine name in uppercase, for example:

      appilog.collectors.probe.ip = STARS01
  3. Start the services.

    1. On the Probe Manager machine, start the Manager service:

      Start > All Programs > UCMDB > Start Data Flow Probe Manager

    2. On the Probe Gateway machine, start the Gateway service:

      Start > All Programs > HP UCMDB > Start Data Flow Probe Gateway

Data Flow Probe - Connect the Data Flow Probe to a Non-Default Customer

Note: This procedure is optional.

You can connect a Data Flow Probe to a customer that is not the default customer. The default customer ID is 1.

  1. Open the following file in a text editor:

    • Windows: C:\hp\UCMDB\DataFlowProbe\conf\DataFlowProbe.properties

    • Linux: ../DataFlowProbe/conf/DataFlowProbe.properties

  2. Locate the customerID entry.

  3. Update the value with the customer ID, for example, customerId = 2.

  4. Restart the Probe so that it is updated with your changes.

Data Flow Probe - Verify the Probe version

Note: This section is relevant for Probes installed on Windows machines only.

The Probe reports its version when connecting to the server. The Probe version is displayed in Data Flow Management, in the Details pane of the Data Flow Probe Setup module. If the Probe version is not compatible with the server version (and there is no supported upgrade), an error is generated and the Probe is forced to shut down.

When you apply a new Cumulative Update Patch (CUP) to the UCMDB Server, the Probes do not shut down automatically, and are able to report new data to the server. However, this is not recommended. Therefore, when you apply a CUP to the server, you must also apply it to the Probes—either manually or automatically.

Data Flow Probe Troubleshooting and Limitations

Upgrading UCMDB - Copy the Encryption Key

Replace the C:\hp\UCMDB\UCMDBServer\conf\discovery\key.bin file with the file you saved earlier.

Upgrading UCMDB - Run the Upgrade tool

Note: Upgrade may take a long time to complete. To terminate the upgrade at any point, click the red Stop button. Steps that either complete with a warning or fail to run are logged in the Upgrade Information pane. To view this information, highlight the row where the upgrade step appears. Relevant information appears on the right.

  1. Launch the upgrade file: C:\hp\UCMDB\UCMDBServer\tools\upgrade.bat

  2. Launch the upgrade file: upgrade.sh

  3. The Preparing to Upgrade wizard opens. Click Next to open the UCMDB Server Upgrade page.

  4. On the CMDB Schema Settings page, select your database type, and fill in the CMDB Schema connection parameters. The Schema name should match the name of your previously replicated UCMDB 9.05 CMDB schema. Click Next.

  5. On the History Schema Settings page, select your database type, and fill in the History Schema connection parameters. The Schema name should match the name of your previously replicated UCMDB 9.05 History schema. Click Next.

  6. The Advanced Settings page opens.

    • Enable Multi Tenancy. Select this option if UCMDB is to work in a multi-tenancy environment.

      Note: After the upgrade, the tenancy environment (single tenancy versus multi-tenancy) cannot be modified.

    • Enable search. Indexes UCMDB data for efficient search capabilities.

      Note: Clear this option if you do not use the UCMDB Browser.

    • Click Next.

  7. The Run Upgrade page lists the upgrade steps. Click Run to begin the upgrade.

  8. The Run Upgrade screen indicates the progress of each step.

    For a comprehensive list of these steps, see the HP UCMDB Upgrader Reference.

    To re-run a specific step, right-click the step in the Steps pane and select Run Selected.

    Note: Rerunning a successful upgrade step should be done for troubleshooting purposes only.

Upgrading UCMDB - Log Files

During the upgrade, the upgrade information is logged in ..\UCMDBServer\runtime-upgrade\log folder, in the following files:

Log (A-Z) Description
cmdb.classmodel.log Failures in this log may indicate which entity in the class model failed to load.
error.log This file is not specific to the upgrade and contains all errors and warnings sent by any other log (unless specifically blocked). It can be used as a map and as a general overview of upgrade success.
mam.packaging.log This log is relevant only for the Basic Packages Deployer step and includes all of that step’s information.
security.authorization.management.log Logs every modification to the authorization model, such as role creation (with the exact permissions), user creation, user role assignments, and so on.
upgrade.short.log This is the main log file for the upgrade procedure. All lines in this file appear in upgrade.detailed.log as well. This file should be used as a table of contents for the more detailed file, or as a general overview or troubleshooting log. Typically this file is less than 5 MB.

Upgrading UCMDB - Post Upgrade Procedures

The following steps may be necessary after the upgrade.

  • UCMDB Browser. When upgrading to 10.01, the UCMDB Browser 1.95 is automatically installed. If you are working with a later version of the UCMDB Browser, you must update it manually.

  • Reverse Proxy. If the upgraded system is not going to run on the same server as the previous version, you need to reconfigure the reverse proxy after the upgrade. For configuration details, see the section about Reverse Proxy in the HP UCMDB Hardening Guide.

  • SSL.

    • Reinstall SSL configurations. For details, see the section about enabling SSL communication in the HP UCMDB Hardening Guide.

    • If SSL was activated on the source system, restore the \conf\security folder that you backed up before the upgrade.

  • LW-SSO. Configure LW-SSO. For details, see the general LW-SSO reference and the section about enabling logging in to UCMDB with LW-SSO in the HP UCMDB Hardening Guide.

  • JMX Console. If you configured Java JMX access hardening, copy the file that you saved before the upgrade back into c:\hp\UCMDB\UCMDBServer\bin\jre\lib\management\jmxremote.password, and edit the file's permissions so that:

    • the owner of the file is the same user that runs the UCMDB service

    • only the owner has permission to view the file (Reminder: this file has the JMX protocol password in clear text)

    For more details on hardening the JMX Console,see the HP UCMDB Hardening Guide.

  • Redo modifications on integration (federation) adapters. All adapters must be compatible with the new Universal Data Model. If you made changes to existing out-of-the-box adapters, you must make the same changes to the adapter files in version 10.01. Do not copy files from your previous version and overwrite the files in version 10.01.

  • Transform Discovery Wizards into Discovery Activities. Discovery wizards are no longer supported in Universal Discovery. Instead, Universal Discovery uses a similar resource called discovery activities. The resource name is the same (discoveryWizard), and is located in Adapter Management under a package called DiscoveryActivities. After the upgrade, it can be transformed by aligning the XML with the new activity XML schema.

    Alternatively, you can delete the resource or undeploy the package completely using the Package Manager.

  • Enable Aging. During the upgrade, aging is disabled to prevent CIs from being deleted because of the time during which the Probe is not collecting data (between the running of the upgrade process and until discovery starts reporting all CIs).

    It is very important to re-enable aging. However, it is recommended to wait until the system has stabilized before re-enabling aging. To verify that the system has stabilized, run discovery and monitor all CIs that are marked for deletion.

    Re-enable aging from the Administration > CI Lifecycle module and restart the server. For details about aging, see the section describing the CI lifecycle and the aging mechanism in the HP Universal CMDB Administration Guide.

    For details on running discovery, see the HP Universal CMDB Data Flow Management Guide.

Upgrading UCMDB - Rerunning the Upgrade Tool

If you want to rerun the Upgrade tool to rerun all the upgrader steps from the beginning, you must first do the following:

  1. Remove the runtime-upgrade folder.
  2. Restore the 9.05 CMDB and History databases that you backed up before the upgrade.

Before You Install HP UCMDB Configuration Manager

The Configuration Manager deployment instruction provided takes into account special UCMDB deployments you may have in your environment (for example, high availability) and provides the necessary adjustments to the deployment procedure for those deployments.

Note: For scaling purposes in a production environment, we recommend that you install UCMDB and Configuration Manager on separate machines, though installing both of these components together on the same server is supported.

However, when installing Configuration Manager on a high-availability UCMDB environment Configuration Manager must be installed on a separate machine.

Using Configuration Manager requires that a new UCMDB state is created (Authorized state). This configuration is performed automatically by the deployment procedure.

Be aware that if you are deploying only Configuration Manager (that is, using an existing or upgraded installation of UCMDB), the UCMDB server must be running to complete the installation of Configuration Manager.

Installing Configuration Manager

Note: Configuration Manager can be installed on a Windows or a Linux system. If you are installing on a Linux system, you can either run the installer in GUI mode (using X11 protocol), or run a silent installation. For details, see Installing Configuration Manager - Silent Installation.

To install Configuration Manager:

  1. Prerequisites:

    • Ensure that HP Universal CMDB version 10.01 is installed with Content Pack 12.
    • To allow Configuration Manager to automatically create integration points (used for federating data to UCMDB) in UCMDB during installation, ensure that the UCMDB integration service is started and fully running before installing Configuration Manager.

      If you are using an external probe, or creation of the integration points fails installation, you can create the integration points manually. For details, see the HP Universal CMDB Data Flow Management Guide.

    • If UCMDB is set up as a high-availability environment, Configuration Manager must not be installed on the same machine as any of the UCMDB Servers. When asked for the UCMDB connection details, use the Cluster virtual IP address of the load balancer.

  2. Launch the Configuration Manager installation: insert the UCMDB DVD into the machine. Do one of the following:

    • Windows: Locate the HPCM_10.01.exe file and double-click it to run the Configuration Manager Installation wizard.
    • Linux: Locate the HPCM_10.01.bin file and run it. You can either run the installer in GUI mode (using X11 protocol), or run a silent installation.
  3. Accept the terms of the End User License Agreement and click Next.

  4. On the Installation Configuration page, select the location for the installation:

    • Windows:

      Click Choose to select the directory where Configuration Manager will be installed. The default location is C:\HP\CM_10.0.0.1.

      Note: The installation directory must not contain spaces, and can use only English letters (a-z), digits (0-9), the hyphen sign ('-'), and the underscore sign (_).

      If a previous version of Configuration Manager is detected, you are given the option to perform a new installation or to upgrade the previously existing installation.

      Select New Installation and click Next.

    • Linux:

      Specify the folder where you want to install Configuration Manager.

  5. On the UCMDB Foundation Connection page, provide the following details for connecting to the UCMDB Foundation installation:

    Note: For details about changing the UCMDB server parameters after the installation is complete, see Reconfiguring Configuration Manager.

    Field

    Definition

    Host Name

    UCMDB deployment location address.

    • The UCMDB host name must be specified as the fully qualified domain name (FQDN) of the UCMDB server machine.

    • If UCMDB is configured in high-availability mode, use the load balancer's Cluster virtual IP address.

    Protocol

    HTTP or HTTPS protocol.

    UCMDB Port

    The HTTP or HTTPS port default values are 8080 for HTTP and 8443 for HTTPS.

    Customer Name

    The default UCMDB customer name is Default Client. The customer name value is used during the UCMDB and Configuration Manager integration configuration. The customer name must exist in UCMDB, and this value is not validated by the connection test. If you provides an incorrect value, the deployment will fail.

    Server Certificate File

    This field appears when the HTTPS protocol is selected. You must manually place the UCMDB server certificate file on the Configuration Manager target host, and specify the full file path including the file name in the adjacent input field.

    If UCMDB uses HTTPS, then using a key exchange is required. The key exchange is not validated during the connection test.

    Note: The certificate file must be a *.cer file (other file formats are not supported).

    JMX Port

    The default value is 29601.

    System User (JMX)

    The UCMDB (JMX) system user is used for activating JMX functions such as creating a Configuration Manager integration user and deploying the Configuration Manager package. The out-of-the-box default value is sysadmin.

    System Password

    The UCMDB system user password. The default value is sysadmin.

    Note: The password must not contain spaces, and can use only English letters (a-z), digits (0-9), the hyphen sign ('-'), and the underscore sign (_).

  6. Click Test to test the connection settings and then click Next to continue to the Database Connection Configuration page.

    Note:

    • A database connection must be configured and associated with a standard URL connection. If advanced features are required, such as an Oracle Real Application Cluster, set up a standard connection and then manually edit the database.properties file to configure the advanced features. You can either connect to an existing schema or create a new schema.

    • Configuration Manager uses native drivers for both the Oracle and Microsoft SQL Server databases. All native driver features are supported, provided that these features can be configured using the database URL. The URL is located in the database.properties file.

    Configuration Manager uses a different database schema from UCMDB.

    Two types of databases are available – Oracle and MS SQL. The input fields change according to the database type selected. During installation, you can either create a new schema or connect to an existing schema. For details about the schema requirements, see the HP Universal CMDB Support Matrix.

    For additional details about connecting to different database schemas, see Installing Configuration Manager - Advanced Database Configuration.

    Caution: Repopulating an existing database removes all data from a database schema and recreates all tables.

    Note:  

    • Populating a database schema is performed automatically by the installation procedure when you create a new schema.
    • The Repopulate Database check box is disabled when you create a new database or schema. When you connect to an existing database or schema, the check box is enabled and you can choose whether or not to populate the database.
    • Provide the following details when creating a new Oracle schema:

      Field

      Definition

      Host Name/IP

      The database server location address.

      Port

      The default Oracle database port is 1521.

      SID The Oracle schema ID.
      Admin Username The username of the database administrator.
      Admin Password The password of the database administrator.
      Schema Username The username of the Oracle schema.
      Schema Password The password of the Oracle schema.
      Default Tablespace The default tablespace.
      Temporary Tablespace The temporary tablespace.
    • Provide the following details when connecting to an existing Oracle schema:

      Field

      Definition

      Host Name/IP

      The database server location address.

      Port

      The default Oracle database port is 1521.

      SID The Oracle schema ID.
      Schema Username The name of the existing Oracle schema.
      Schema Password The password of the existing Oracle schema.
    • Provide the following details when creating a new MSSQL database or connecting to an existing database:

      Field

      Definition

      Host Name/IP

      The database server location address.

      Port

      The default MSSQL database port is 1433.

      DB Name The MSSQL database name.
      DB Username The username of the MSSQL database.
      DB Password The password of the MSSQL database.

  7. Click Test to test the connection settings and then click Next to continue to the Server Ports Configuration page.
  8. Specify Configuration Manager settings on the Server Ports Configuration page. When finished, click Next to continue to the User Configuration page.

    Configuration Manager provides out-of-the-box default port settings. If a port number conflicts with an existing installation, consult with an IT manager before changing the port number.

    Field

    Definition

    AJP Port

    8109 (Apache Java Protocol)

    Note: If Configuration Manager and UCMDB are running on the same host and both applications are using SiteMinder, the AJP port of one of the applications should be changed from the default value (8009). If the AJP ports for Configuration Manager and UCMDB are the same, SiteMinder cannot redirect to Configuration Manager during logon.

    Application HTTP Port

    8180

    Application HTTPS Port

    8143

    JMX HTTP Port

    39900

    JMX Remote Port

    39600

    Tomcat Port

    8005

  9. Enter details for the UCMDB integration user on the User Configuration page. When finished, click Next to continue to the Advanced Content page.

    An integration user is created in UCMDB on demand by Configuration Manager to support the integration between these two products.

    If you previously installed Configuration Manager version 10 for this UCMDB instance, you can use the same integration user credentials that you used previously, instead of creating a new integration user.

  10. In the Advanced Content page, the option to install advanced content is enabled by default. For details about the advanced content (out-of-the-box views and policies), see the section about licensed content in the HP Universal CMDB Configuration Manager User Guide. Click Next to continue to the Pre-Installation Summary page.

    Note: You must purchase an Advanced Configuration Manager license to use advanced content in Configuration Manager.

  11. Review your installation and configuration settings on the Pre-Installation Summary page. When finished, click Install to continue to the Installing page.

    The Summary page centralizes all of the configuration details and user input. You can revise the content of the summary, if necessary, by clicking Previous on the pages until you reach the desired page, and adjust the deployment settings. Return to the Summary page by clicking Next as required.

  12. The Installing page shows the progress of your installation. During the installation, the progress bar displays the progress of the installation. When the process finishes, the configuration settings are applied to Configuration Manager. This phase may take several minutes. You can press Cancel during the installation to stop the process and roll back the installation. During the configuration phase, the Cancel button is disabled.

    When the installation process finishes, a message appears indicating that Configuration Manager was successfully installed in the selected folder. In addition, error messages or warnings are displayed, as well as the path of the log file. To finish, press Done.

Upgrading Configuration Manager

The upgrade procedure assumes the following before beginning:

  • there is a working connection to the UCMDB server.

  • the UCMDB server is up and running.
  • the Configuration Manager server is stopped.
  • the communication between Configuration Manager and UCMDB uses HTTP protocol and not HTTPS protocol. For instructions about changing the protocol settings, see Reconfiguring Configuration Manager.
  • If you manually created an integration point using the CM KPI adapter or the CM Policy adapter, remove these integration points before upgrading. Failure to do this may result in duplicate integration points being created during the upgrade procedure, which can cause data federation to fail.

Note: If you have any version of Configuration Manager earlier than 10.00 installed, you must upgrade to version 10.00 before upgrading to version 10.01. For details on upgrading Configuration Manager to version 10.00, refer to the Configuration Manager version 10.00 documentation.

To upgrade, perform the following steps:

  1. Back up the Configuration Manager version 10.00 installation folder.

  2. Back up the Configuration Manager version 10.00 database.
  3. Back up the following Windows registry entry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
    \Uninstall\HP Universal CMDB Configuration Manager 10.00

  4. To start the installation, insert the Configuration Manager installation media into the machine. Do one of the following:

    • On a Windows system, locate the HPCM_10.01.exe file in the \Windows folder and double-click it.
    • On a Linux system, locate the HPCM_10.01.bin file and run it. You can either run the installer in GUI mode (using X11 protocol), or run a silent installation.
  5. Click Next to open the End User License Agreement page.

  6. Accept the terms of the license and click Next.

  7. Select the folder where Configuration Manager will be installed. Make sure that you select a different location than the one that was used for the previous version.

    By default, Configuration Manager is installed in the following directory: c:\hp\CM_10.0.0.1.(on Windows systems) or /root/HP/CM_10.0.0.1 (on Linux systems). Click Next to accept the default location, or click Browse to select a different location and then click Next.

  8. Note: The installation directory must not contain spaces in its name.

  9. Click Next until you are asked whether to perform a new installation of Configuration Manager or to upgrade.

    Note: If you are upgrading on a Linux system, specify the new (target) installation folder, the folder that contains the previous installation folder, and the version number of the previous installation. For the version number, enter 10.00.

    Note: The advanced content that is installed during the upgrade procedure requires the purchase of a license. If you plan to use advanced content features, contact your HP sales representative or HP Software business partner to obtain the appropriate license.

  10. Select Upgrade and click Next to confirm and begin the installation.
  11. In the Advanced Content page, the option to install advanced content is enabled by default. For details about the advanced content (out-of-the-box views and policies), see the section about licensed content in the HP Universal CMDB Configuration Manager User Guide.

    Note: You must purchase an Advanced Configuration Manager license to use advanced content in Configuration Manager.

  12. When the installation finishes, check the installation log file (located in the <Configuration Manager installation directory>/_installation/logs folder) to ensure that the installation completed with no errors.

    If an error occurs during the upgrade process, a message is displayed. If this occurs, contact HP Software Support.

  13. On Windows machines, the Configuration Manager service starts automatically. Wait several minutes for the service to restart.

Note: After upgrading, you must perform the SSL configuration again. For details, see the HP UCMDB Hardening Guide.

Installing Configuration Manager - Silent Installation

Note: Configuration Manager can be installed on a Windows or a Linux system.

To perform a silent installation of Configuration Manager:

Run the following command:

>HPCM_10.01.exe -i silent -f installvariables.properties

An example of the installvariables.properties file is displayed below:

# Enter 1 for a new installation or 0 to upgrade
CM_NEW_INSTALLATION=1
# Logging file
INSTALL_LOG_NAME=HP_Universal_CMDB_Configuration_Manager.log
# User installation directory
# Enter the full absolute path to be used for the installation
# Make sure to use double backslashes; for example, C:\\hp\\cm_9.30
USER_INSTALL_DIR=
# UCMDB connection config:
UCMDB_HOST_NAME=
UCMDB_PROTOCOL=
UCMDB_PORT=
# Enter the full path for the UCMDB Foundation certificate file # (.cer file only) # UCMDB_CLIENT_CERT_FILE should be defined only when connecting # to UCMDB with HTTPS protocol UCMDB_CLIENT_CERT_FILE=
UCMDB_CUSTOMER_NAME=
UCMDB_JMX_PORT=
UCMDB_SYSTEM_USER=
UCMDB_SYSTEM_PASSWORD=
# Database config:
# Enter 1 to create a new schema; otherwise, enter 0
DB_CREATE_NEW_SCHEMA=
# Enter 1 to use an existing schema; otherwise, enter 0 DB_USE_EXISTING_SCHEMA=
# Enter 1 for an Oracle database; otherwise, enter 0 DB_VENDOR_ORACLE=
# Enter 1 for an MSSQL database; otherwise, enter 0 DB_VENDOR_MSSQL= # DB_HOST_NAME should be the fully qualified domain name (FQDN)
DB_HOST_NAME=
DB_PORT=
# For an Oracle database, enter the SID name; for an # MSSQL database, enter the database name ORACLE_SID_OR_MSSQL_DB_NAME=
ORACLE_SCHEMANAME_OR_MSSQL_DB_USERNAME=
ORACLE_SCHEMA_PASSWORD_OR_MSSQL_DB_USER_PASSWORD= # Enter 1 if you want to repopulate the database or when creating # a new schema, or 0 if you are connecting to an existing schema and # do not want to repopulate DB_REPOPULATE_DATABASE=
# Oracle only:
# These four values are required only for the creation of a new 
# Oracle schema
ORACLE_ADMIN_USERNAME=
ORACLE_ADMIN_PASSWORD=
DB_DEFAULT_TABLE_SPACE=
DB_TEMP_TABLE_SPACE=
# Tomcat Ports:
HTTP_PORT=
HTTPS_PORT=
TOMCAT_PORT=
AJP_PORT=
JMX_HTTP_PORT=
JMX_REMOTE_PORT=
# User config:
UCMDB_ADMIN_USERNAME=
UCMDB_ADMIN_PASSWORD=
# Advanced configuration manager content      
# Requires purchase of an ACM license
# Enter 1 to install advanced content
#
INSTALL_CM_ADVANCED_CONTENT_BOOLEAN_1 =

For additional details about the various parameters that can be set, see Installing Configuration Manager.

Installing Configuration Manager - Advanced Database Configuration

Reconfiguring Configuration Manager

Reconfiguring Configuration Manager allows you to change the installation parameters (UCMDB properties, DB properties, and so on) of an existing installation.

To reconfigure an existing installation of Configuration Manager, do the following:

  1. In the <Configuration Manager installation directory>/_installation folder, run HPCM_10.01.exe (on Windows systems) or HPCM_10.01.bin (on Linux systems), without repopulating the database. The End User License Agreement is displayed. Select the radio button and click Next to continue.

  2. The installation process checks if there is a previous installation of Configuration Manager, and displays the following message:

    A previous installation of the product has been detected. 
    This installation will not reinstall the product, but will 
    allow you to reconfigure the product parameters.

    Click Next to continue.

  3. Continue with the reconfiguration You can update the following information:

    • UCMDB Foundation connection information

      Field

      Definition

      Host Name

      UCMDB deployment location address.

      • The UCMDB host name must be specified as the fully qualified domain name (FQDN) of the UCMDB server machine.

      • If UCMDB is configured in high-availability mode, use the load balancer's Cluster virtual IP address.

      Protocol

      HTTP or HTTPS protocol.

      UCMDB Port

      The HTTP or HTTPS port default values are 8080 for HTTP and 8443 for HTTPS.

      Customer Name

      The default UCMDB customer name is Default Client. The customer name value is used during the UCMDB and Configuration Manager integration configuration. The customer name must exist in UCMDB, and this value is not validated by the connection test. If you provides an incorrect value, the deployment will fail.

      Server Certificate File

      This field appears when the HTTPS protocol is selected. You must manually place the UCMDB server certificate file on the Configuration Manager target host, and specify the full file path including the file name in the adjacent input field.

      If UCMDB uses HTTPS, then using a key exchange is required. The key exchange is not validated during the connection test.

      Note: The certificate file must be a *.cer file (other file formats are not supported).

      JMX Port

      The default value is 29601.

      System User (JMX)

      The UCMDB (JMX) system user is used for activating JMX functions such as creating a Configuration Manager integration user and deploying the Configuration Manager package. The out-of-the-box default value is sysadmin.

      System Password

      The UCMDB system user password. The default value is sysadmin.

      Note: The password must not contain spaces, and can use only English letters (a-z), digits (0-9), the hyphen sign ('-'), and the underscore sign (_).

    • Database configuration information

      Configuration Manager uses a different database schema from UCMDB.

      Two types of databases are available – Oracle and MS SQL. The input fields change according to the database type selected. During installation, you can either create a new schema or connect to an existing schema. For details about the schema requirements, see the HP Universal CMDB Support Matrix.

      For additional details about connecting to different database schemas, see Installing Configuration Manager - Advanced Database Configuration.

      Caution: Repopulating an existing database removes all data from a database schema and recreates all tables.

      Note:  

      • Populating a database schema is performed automatically by the installation procedure when you create a new schema.
      • The Repopulate Database check box is disabled when you create a new database or schema. When you connect to an existing database or schema, the check box is enabled and you can choose whether or not to populate the database.
      • Provide the following details when creating a new Oracle schema:

        Field

        Definition

        Host Name/IP

        The database server location address.

        Port

        The default Oracle database port is 1521.

        SID The Oracle schema ID.
        Admin Username The username of the database administrator.
        Admin Password The password of the database administrator.
        Schema Username The username of the Oracle schema.
        Schema Password The password of the Oracle schema.
        Default Tablespace The default tablespace.
        Temporary Tablespace The temporary tablespace.
      • Provide the following details when connecting to an existing Oracle schema:

        Field

        Definition

        Host Name/IP

        The database server location address.

        Port

        The default Oracle database port is 1521.

        SID The Oracle schema ID.
        Schema Username The name of the existing Oracle schema.
        Schema Password The password of the existing Oracle schema.
      • Provide the following details when creating a new MSSQL database or connecting to an existing database:

        Field

        Definition

        Host Name/IP

        The database server location address.

        Port

        The default MSSQL database port is 1433.

        DB Name The MSSQL database name.
        DB Username The username of the MSSQL database.
        DB Password The password of the MSSQL database.

    • Tomcat ports

      Configuration Manager provides out-of-the-box default port settings. If a port number conflicts with an existing installation, consult with an IT manager before changing the port number.

      Field

      Definition

      AJP Port

      8109 (Apache Java Protocol)

      Note: If Configuration Manager and UCMDB are running on the same host and both applications are using SiteMinder, the AJP port of one of the applications should be changed from the default value (8009). If the AJP ports for Configuration Manager and UCMDB are the same, SiteMinder cannot redirect to Configuration Manager during logon.

      Application HTTP Port

      8180

      Application HTTPS Port

      8143

      JMX HTTP Port

      39900

      JMX Remote Port

      39600

      Tomcat Port

      8005

    • User configurations

      An integration user is created in UCMDB on demand by Configuration Manager to support the integration between these two products.

      If you previously installed Configuration Manager version 10 for this UCMDB instance, you can use the same integration user credentials that you used previously, instead of creating a new integration user.

Start or Stop the Configuration Manager Application Server

  • To start the Configuration Manager server:

    $ cd /<Configuration Manager installation directory> $ ./start-server-0.sh

    Running this script this way starts the server in a synchronous process, which means that the server is stopped as soon as you disconnect from the console.

    Note:

    • To start the Configuration Manager server asynchronously, run the script as follows:

      $ ./start-server-0.sh &
    • To keep the Configuration Manager server running even if a user logs out, run the script as follows:

      nohup $ ./start-server-0.sh 

    You can create a script in the /etc/init.d directory to automatically start Configuration Manager on machine startup.

  • On a Linux system:

    Use a command line prompt:

    • To stop the Configuration Manager server:

      $ cd /<Configuration Manager installation directory> $ ./stop-server-0.sh

  • On a Windows system:

    Use the HP Universal CMDB Configuration Manager Windows service to start or stop the server.

Uninstalling Configuration Manager

To uninstall Configuration Manager, do one of the following:

On Windows systems

From the Start menu:

  • Click Start > All Programs > HP Universal CMDB Configuration Manager 10.0 > Uninstall HP Universal CMDB Configuration Manager 10.0.

From the Control Panel:

  • Click Control Panel > Programs and Features > HP Universal CMDB Configuration Manager 10.0, and then click Uninstall.

A notification is displayed that you are about to uninstall. Click Uninstall to continue or click Cancel to exit.

On Linux systems In the <Configuration Manager installation directory>/_installation/ folder, execute CM-Uninstall.bin.

Access Commands for the UCMDB Server

HP UCMDB Services

Accessing and Logging In to HP Universal CMDB

Accessing HP Universal CMDB Through the IIS Web Server

Configuring UCMDB to Integrate with SiteMinder (Optional)

The following procedure enables integration of UCMDB with SiteMinder:

  1. Prerequisites:

    • Ensure that CA SiteMinder is installed on your user environment.
    • Ensure that Microsoft IIS Web Server is installed on the same machine as the CA SiteMinder Client Agent.
  2. Set up IIS to enable access to UCMDB.

    For details, see Accessing HP Universal CMDB Through the IIS Web Server.

  3. Enable AJP connections.

    In the Administration module, select Infrastructure Settings Manager > General Settings, and set Enable AJP Connections to True.

  4. Configure UCMDB to enable LW-SSO:

    1. Enable logging in to UCMDB with LW-SSO. For details, see the HP UCMDB Hardening Guide.

    2. In the JMX console, invoke the setUserName method and set the LW-SSO IDM user name settings as follows:

      • Is inbound handler enabled = True
      • LW-SSO IDM User Name = sm-user
  5. Verify successful integration of UCMDB with SiteMinder.

    Access http://ucmdb-server/ucmdb-ui using the user name and password in your user directory.

    After SiteMinder validates the user credentials, you are forwarded directly to UCMDB with no need to enter your UCMDB user name and password.

Working with UCMDB in Non-English Locales

Configure the UCMDB Mail Server - Optional

To configure the UCMDB Mail server:

  1. Select Administration > Infrastructure Settings > Mail Settings.
  2. Define the SMTP server setting: enter the name of the SMTP server.
  3. Edit the SMTP server port setting: the default value is 25.
  4. As a backup for the main SMTP server, you can provide information about an alternative server. Repeat steps 2 and 3 but provide the name of the Alternate SMTP server and the Alternate SMTP server port.
  5. Edit the setting for Email sender with the name to appear in reports that HP Universal CMDB sends.
  6. To enable users to change the Email sender name inside the form that sends mail, change the value of Sender editability to True. Otherwise, leave its value as False.

Large Capacity Planning for UCMDB

Disaster Recovery

Accessing Configuration Manager

Additional Use Cases for Configuration Manager

Troubleshooting Deployment - Available Troubleshooting Resources for UCMDB

  • Installation troubleshooting. Use to troubleshoot common problems that you may encounter when installing HP Universal CMDB, and the solutions to those problems. See Troubleshooting Deployment - UCMDB Server.
  • Login troubleshooting. Use to troubleshoot possible causes of failure to log in to HP Universal CMDB.
  • HP Software Self-solve knowledge base. Use to search for specific troubleshooting information on a wide variety of topics. Located on the HP Software Support Web site, the HP Software Self-solve knowledge base can be accessed by selecting Troubleshooting & Knowledge Base from the HP Universal CMDB Help menu.

    Note that only registered customers can access the resources on the HP Software Support Web site. Customers who have not yet registered can do so from this site.

  • HP Universal CMDB Log files. Use to troubleshoot CMDB runtime problems. For details, see the section about CMDB log files in the HP Universal CMDB Administration Guide.
  • Data Flow Management log files. Use to troubleshoot DFM problems. For details, see the section about Data Flow Management log files in the HP Universal CMDB Administration Guide.
  • Query log files. Use to view definitions for query parameter log files. For details, see the section about CMDB log files in the HP Universal CMDB Administration Guide.

Troubleshooting Deployment - UCMDB Server

Problem: The UCMDB Server does not start automatically upon system restart.

Solution:

  1. Open the Windows Services dialog box and select the UCMDB_Server service.
  2. Open the UCMDB_Server Properties (Local Computer) dialog box.
  3. In the General tab, ensure that:

    • The Path to executable field points to the correct executable location.
    • The service is configured to automatically start (Startup type is Automatic).
  4. In the Log On tab, ensure that the service uses the correct user for logon. For details on changing the service user, see the HP UCMDB Hardening Guide.
  5. In the Dependencies tab, ensure that the service is configured to have no dependencies (<No Dependencies>).

Troubleshooting Deployment - Logging In to UCMDB

Possible Causes for Failure to Log In to UCMDB

Use the following information to troubleshoot possible causes of failure to log into HP Universal CMDB.

Problem/Possible Causes

Solutions

HP Universal CMDB is not started successfully.

Indication: The jboss_boot.log file does not include the following line:

======== server is up ========

Solution 1: Verify that the HP Universal CMDB Server is up and running by accessing the Web console http://<Server name>:8080/web-console where <server name> is the name of the HP Universal CMDB Server to which you are connecting.

Solution 2: Check the database connection:

To check that the database server is up and running:

  1. Launch the Web browser and navigate to: http://<Server name>:8080/jmx-console, where <Server name> is the name of the machine on which HP Universal CMDB is installed.

  2. Under UCMDB, click UCMDB:service=Dal Services to open the JMX MBean View.

  3. Invoke the function getDbContext with a customerID parameter value of 1.

  4. Check that the operation result shows no problems.

Solution 3: Check that the database connection parameters are correct. Ensure that you can log into Oracle Server or Microsoft SQL Server using the credentials you provided during the installation procedure.

Solution 4: Use the log file C:\hp\UCMDB\UCMDBServer\runtime\log\cmdb.dal.log to verify the database connections.

Solution 5: To verify that the database connection is valid, in the Windows command interpreter (cmd.exe), type sqlplus cmdb/cmdb@skazal.

The CMDB is corrupted (for example, a user record may have been deleted accidentally from the CMDB).

Import a previously backed up database file. For details, see the HP Universal CMDB Database Guide.

Important: The HP Universal CMDB server must be down while importing the database.

Note: When you import a previously backed up database file, you lose all data previously existing in the system.

The HP Universal CMDB login fails. This may be due to an incorrect login name/password combination.

Ensure that you enter a correct login user name/password combination.

HP Universal CMDB login fails due to unexpected errors.

Solution 1: Select Start > Programs > HP UCMDB > HP Universal CMDB Server Status and ensure that the service is running.

Solution 2: Look for errors in the following log files:

  • C:\hp\UCMDB\UCMDBServer\runtime\log\error.log

  • C:\hp\UCMDB\UCMDBServer\runtime\log\ui-server.log

If you find errors that are unfamiliar to you, contact HP Software Support.

Java Not Installed on Client Machine

If Java is not installed on your machine or you have an version older than 6.u10, during login a message is displayed asking you whether to install the correct Java Runtime Environment version. JRE is needed to view HP Universal CMDB applets.

Click the relevant button to allow HP Universal CMDB to install Java from either oracle.com or the HP Universal CMDB Server.

Updating the Java Configuration

The following message is displayed when HP Universal CMDB detects problems with initial memory:

Note: From Java version 6 update 10, this message is no longer displayed as it is no longer relevant.

Troubleshooting Deployment - Configuration Manager Upgrade

  • Problem. The upgrade to version 10.01 fails. To restore to version 9.3x, perform the following steps:

    • Uninstall Configuration Manager version 10.01.
    • Restore the Configuration Manager version 9.3x installation folder (that you backed up before upgrading) to its original location.
    • Restore the database (that you backed up before upgrading).
    • Import the Windows registry entry (that you backed up before upgrading).
  • Troubleshooting Deployment - Logging In to Configuration Manager

    Problem. You have been assigned the appropriate permissions for Configuration Manager but you are not able to log in.

    Solution. Verify that the following parameters are configured correctly in UCMDB:

    • LW-SSO init string: This string must not be empty.
    • LW-SSO domain: Must be set to the same domain as UCMDB.
    • LW-SSO trusted DNS domains: The Configuration Manager domain must be listed here, even if it is the same as the UCMDB domain.

    Problem. There is an error in the UCMDB connection.

    Solution. One of the following may be the cause:

    • The UCMDB server is down. Restart Configuration Manager after UCMDB is fully up (verify that the UCMDB server status is Up).

    • The UCMDB server is up but the Configuration Manager connection credentials or URL is wrong.

    Problem. After changing UCMDB connection settings (such as changes to: host/port/protocol/SRP), the Configuration Manager server fails to start.

    Solution. Reconfigure Configuration Manager and specify the UCMDB connection settings that reflect your latest changes. The reconfiguration wizard (HPCM_10.01.exe) is located in the <Configuration Manager installation directory>\_installation folder.

    Problem. Changes to the UCMDB class model are not detected in Configuration Manager.

    Solution. Restart the Configuration Manager server.

    Problem. The Configuration Manager log contains a UCMDBExecution timeout expired error.

    Solution. This occurs when the UCMDB database is overloaded. To correct this, increase the connection timeout as follows:

    1. Create a jdbc.properties file in the UCMDBServer\conf folder.

    2. Enter the following text: QueryTimeout=<number in seconds>.

    3. Restart the UCMDB server.

    Problem. Configuration Manager does not allow you to add a view to be managed.

    Solution. When a view is added to be managed, a new TQL is created in UCMDB. If the maximum limit of active TQLs is reached, the view cannot be added. Increase the limit of active TQLs in UCMDB by changing the following settings in the Infrastructure Settings Manager:

    • Max Number Of Active TQLs In Server

    • Max Number Of Customer Active TQLs

    Problem. The HTTPS Server certificate is not valid.

    Solution. One of the following may be the cause:

    • The validation date of the certificate has passed. You need to get a new certificate.

    • The certification authority on the certificate is not a trusted authority. Add the certification authority to your Trusted Root Certification Authority list.

    Problem. When logging in from the Configuration Manager login page, you get a login error or access denied page.

    Solution. Check that the LW-SSO settings are correct. For details, see the general LW-SSO reference in the HP UCMDB Hardening Guide.

    Problem. The Configuration Manager server does not start due to entering incorrect database credentials.

    Solution. If you made a change to the database credentials and the server fails to start, the credentials may be wrong. You need to re-encrypt the database password and enter new credentials in the configuration file. Proceed as follows:

    1. From a command line, run the following command to encrypt the updated database password:

      <Configuration Manager installation directory>\bin\encrypt-password.bat –p <password>

      which returns an encrypted password.

    2. Copy the encrypted password (including the {ENCRYPTED} prefix), into the db.password parameter in <Configuration Manager installation directory>\conf\database.properties.

    Problem. The Configuration Manager Tomcat server does not start due to a bind port issue.

    Solution. Try one of the following:

    • Run the Post install wizard and replace the Configuration Manager server ports.

    • Abort the other process that occupies the Configuration Manager ports.

    • Manually change the ports in Configuration Manager configuration files by editing the following file: <Configuration Manager installation directory>\servers\server-0\conf\server.xml and updating the relevant ports:

      • HTTP (8180): line 69

      • HTTPS (8143): lines 71, 90

    Problem. You receive an "out of memory" message.

    Solution. Do the following to change the server startup parameters:

    1. Run the following batch file:

    2. <Configuration Manager installation directory>/bin/edit-server-0.bat

    3. Change the following settings:

    4. -Dapplication.ms=<inital memory pool size>
      -Dapplication.mx=<maximum memory pool size>

    Problem. Changes in CIs in UCMDB are not reflected in Configuration Manager.

    Solution. Configuration Manager runs an offline asynchronous analysis process. The process may not yet have processed the latest changes in UCMDB. To resolve this, try one of the following:

    • Wait a few minutes. The default interval between analysis process executions is 10 minutes. It is configurable in Administration > Settings.

    • Execute a JMX call to run the offline analysis calculation on the relevant view.

    • In Policies, click the Recalculate Policy Analysis button. This invokes the offline analysis process for all views (which may take some time). You may also need to make an artificial change to one policy and save it.

    Troubleshooting Deployment - Configuration Manager General Limitations and Troubleshooting

    Troubleshooting Deployment - Configuration Manager Authentications

    Problem. During authentication of Configuration Manager after redirection to the UCMDB login page, you are not redirected back to Configuration Manager but UCMDB opens instead.

    Solution. The Configuration Manager authentication session cookie is blocked or denied when using Internet Explorer version 6.0, 7.0 or 8.0 browsers. Add the Configuration Manager server to the Intranet/Trusted zone in the Internet Explorer security zones on your computer (Tools > Internet Options > Security > Local Intranet > Sites > Advanced). This allows all cookies to be accepted.

    Solution. Make sure that the LW-SSO configuration in UCMDB settings is correct. For details, see the section about LW-SSO in the HP UCMDB Hardening Guide.

    Possible solution. Make sure that you access the application with the Fully Qualified Domain Name (FQDN) in the login URL (for example: http://myserver.companydomain.com/WebApp).

    © Copyright 2002-2012 Hewlett-Packard Development Company, L.P.