Customized output from:
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.
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 2002-2012 Hewlett-Packard Development Company, L.P.
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.
Visit the HP Software Support Online web site at:
http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to:
Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to:
http://h20229.www2.hp.com/passport-registration.html
To find more information about access levels, go to:
http://h20230.www2.hp.com/new_access_levels.jsp
The questions that follow will help you customize the information that will appear in your interactive Deployment Guide.
Please 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.
Select this option if you are setting up a multi-tenancy environment.
Note: If you are deploying Configuration Manager, do not select this option.
Select to install or upgrade the UCMDB Server.
Note:
If you are installing or upgrading the UCMDB Server, you must select a platform.
If you are installing or upgrading the UCMDB Server, you must select a database.
Select a deployment option for HP Configuration Manager.
Note:
You must select one of these options.
High Availability is a mode of running UCMDB on a cluster of two or more servers to ensure system availability. One server is active at any given time, while the others are passive.Communication between the servers in the cluster is managed by a load balancer. For more information, see UCMDB in a High Availability Environment.
Note: High Availability is not supported in a multiple-customer environment.
The Data Flow Probe is used to perform Universal Discovery and Integration. You can select one or both of these options.
Note: If you are upgrading UCMDB and you had Data Flow Probes installed, you must reinstall the Data Flow Probes.
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.
The following steps are customized according to your selections. Check that your selections are correct.
If any selections are not correct, click Change.
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 UCMDB Database Guide |
HP Universal CMDB Deployment Guide |
|
HP Universal CMDB Deployment Guide |
HP UCMDB Hardening Guide |
HP Universal CMDB Deployment 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) |
The installation workflow contains the following main stages:
Set up the CMDB database server.
Set up the Microsoft SQL Server
Set up the Oracle Server.
Obtain the appropriate HP Universal CMDB license
Place the license on a machine that is accessible from the machine on which you are installing HP Universal CMDB.
For details, see HP Universal CMDB Licensing document.
Install the HP Universal CMDB Server.
Install the active HP Universal CMDB Server
Install the UCMDB Server and configure the connection to the database.
Install the passive HP Universal CMDB Server
In a High Availability environment, after you have installed the active UCMDB Server, you need to install the passive UCMDB Server.
Install HP Configuration Manager
Install and configure HP Configuration Manager to analyze and control the data in UCMDB.
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.
Set up access permissions for the UCMDB Server
For details, see the HP UCMDB Hardening Guide.
Set up access permissions for the Data Flow Probe.
For details, see the HP UCMDB Hardening Guide.
Set up the UCMDB Server Service authentication permissions.
Launch HP Universal CMDB.
Note the following prior to installing HP Universal CMDB on Windows:
Important: 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.
The HP Universal CMDB program directory cannot contain non-English characters.
UCMDB User and Login names should not exceed 300 characters.
For details on licensing, see the HP Universal CMDB Licensing document.
In High Availability environments, the machines used for the active and passive UCMDB Servers should have similar hardware (especially 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.
Have the following information ready before beginning installation:
Information for setting the CMDB database parameters.
If you plan to run the UCMDB Server on a hardened platform (including using the HTTPS protocol), review the hardening procedures described in HP UCMDB Hardening Guide.
Administrator’s email address. (Optional)
SMTP mail server name. (Optional)
SMTP sender name. This name appears on alerts sent from UCMDB. (Optional)
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.
Important: 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.
The HP Universal CMDB program directory cannot contain non-English characters.
UCMDB User and Login names should not exceed 300 characters.
For details on licensing, see the HP Universal CMDB Licensing document.
In High Availability environments, the machines used for the active and passive UCMDB Servers should have similar hardware (especially 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.
Have the following information ready before beginning installation:
Information for setting the CMDB database parameters.
If you plan to run the UCMDB server on a hardened platform (including using the HTTPS protocol), review the hardening procedures described in the HP UCMDB Hardening Guide
The following procedure explains how to install a UCMDB Server on a Windows machine.
Note: If you are using two or more servers, and you did not uninstall the 9.05 instance from your machine, you must stop the 9.05 instance before installing version 10.00. (Start > All Programs > HP UCMDB > Stop HP Universal CMDB Server)
Locate the UCMDB executable file: HPUCMDB_Server_10.00.exe.
Double-click the file to open the splash screen.
Note: If the digital signature is not valid, you should not install UCMDB. In this case, contact HP Support.
Choose the locale language and click OK.
The Introduction page opens. Click Next.
The License Agreement page opens.
Accept the terms of the license and click Next.
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 spaces.
Tip: To display the default installation folder again, click Restore Default Folder.
Click Next.
The Select Installation Type page opens. Select New Installation, and click Next.
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.
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.
Click Done to complete the installation.
If you had Data Flow Probes installed on the previous system, continue with the Data Flow Probe installation.
The following procedure explains how to install the UCMDB Server on a Linux machine.
Note: If you are using two or more servers, and you did not uninstall the 9.05 instance from your machine, you must stop the 9.05 instance before installing version 10.00 (/opt/hp/UCMDB/UCMDBServer/bin/server.sh stop).
Prerequisite: Apply one of the following configurations to the Linux machine:
Option 1:
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.
Run the following executable: sh <the path to the installation file>/HPUCMDB_Server_10.00.bin.
The UCMDB installation opens.
Choose the locale language and click OK.
The Introduction page opens. Click Next
The License Agreement page opens.
Accept the terms of the license and click Next.
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 spaces.
Note: To display the default installation folder again, click Restore Default Folder.
Click Next.
The Select Installation Type page opens. Select New Installation, and click Next.
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.
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 the bin subfolder of the installation folder.
Click No. You will set up the database or schema later.
Click Done to complete the installation.
If you had Data Flow Probes installed on the previous system, continue with the Data Flow Probe installation.
On the last page of the installation wizard, click Done to complete the installation.
Start the server.
Note:
If you ran the UCMDB Server Configuration Wizard as part of HP Universal CMDB Server installation, you must start HP Universal CMDB on the 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 Probe after successfully completing the parameter modification process.
When you start the 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.
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:
Access the JMX console.
Select Settings Services under UCMDB.
Select the setSettingValue method.
In the name box, enter enable.high.availability.
In the value box, enter false.
Click Invoke.
This section describes the installation, startup, and configuration procedures for HP Universal CMDB to run in high availability mode.
The information provided below assumes that you have an active UCMDB Server installed and configured..
High Availability mode is not supported in a multiple-customer environment.
Prerequisites
The typical configuration is an active UCMDB server and a passive UCMDB server.
This procedure assumes that you have an active UCMDB server installed and configured.
Install the passive UCMDB Server
The passive UCMDB Server is another machine which is used as a backup for the active UCMDB Server in case of failure.
Note:
The machines used for the active and passive UCMDB Servers should have similar hardware (especially the same amount of memory) and should be running the same operating system.
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.
Install the passive UCMDB Server as you did the active UCMDB Server with one difference: when running the Server Configuration wizard to configuring the database on the passive UCMDB Server, select Connect to an existing schema, and provide the details of the schema you created for the active UCMDB Server.
For details on installing UCMDB Servers, see Installing the UCMDB Server - Installation.
Complete the Server Startup
If the active UCMDB Server is not started, start the process. Wait until the startup process is complete.
Access server_management.bat (the Server Management Tool) located in C:\hp\UCMDB\UCMDBServer\tools\.
Run server_management.sh located in /opt/hp/UCMDB/UCMDBServer/tools/.
On the login page, enter the active UCDMB Server name and credentials.
If the default HTTPS port is being used (port 8443), enter the UCMDB Server name only, for example, localhost.
If the HTTPS port has been changed, enter the Server name and the new port, for example: localhost:443.
Enter the user name and password of the Server Administrator user (the default is sysadmin and sysadmin).
Note: The connection from the tool to the HP Universal CMDB Server is made through HTTPS which is enabled by default, and configured with port 8443.
In the Server Management Tool, in the left menu, select Clusters.
Click the New Cluster button to create a new cluster.
In the Add Server box, enter the machine name of the passive UCMDB Server that you installed, and click Add.
Note: High Availability servers should be configured with short server names (not with IP addresses).
Note: High Availability servers should be configured with the result of Linux command: "hostname -f" which is the fully qualifies domain name.
In the Server Name list, select the UCMDB Server that is to be the active UCMDB Server, click Set Active, and click OK.
When prompted about switching all existing customers to the active UCMDB Server, click Yes.
Start the passive UCMDB Server.
Tip: You can start the passive UCMDB Server from within the Server Management tool.
Note: If, after you have completed this procedure, you want to change the active UCMDB Server, do this as follows (to prevent database inconsistency):
Stop the active UCMDB Server from the machine itself. After a short time, the passive UCMDB Server automatically becomes the active UCMDB Server. Then start up the UCMDB server that was previously active.
Configure the Load Balancer
On the Load Balancer machine, define the virtual IP for the two HP Universal CMDB Servers with the following configuration:
Select the same port as defined for the UCMDB Servers. (In UCMDB go to Administration > Infrastructure Settings).
Verify that the virtual IP is configured per cluster.
The keep alive address for the session is:
http://<UCMDB-Server:port>/ping/?clusterId=<clusterId>.
An active Server in the cluster returns HTTP response 200 (OK). A passive Server returns HTTP response 503 (service unavailable).
Active and Passive are printed to the HTML page when browsing to the keep alive page of the active or passive server, respectively.
Note: Note down the load balancer IP address. When defining the communication settings between the UCMDB Server and other components, such as the Data Flow Probe, always use this load balancer virtual IP when prompted for the UCMDB Server name.
Configure the Probe
When you install the Data Flow Probe, use the load balancer virtual IP address when defining the HP Universal CMDB Server name.
If you already have a Probe installed:
To improve start up times for the passive machines during a transition from the active machine, HP Universal CMDB starts the passive machines in partial mode.
In this case, the Model Topology component on the passive machines is started in read-only mode. Then it is synchronized with the changes occurring on the active Server, by the UCMDB database, every few seconds.
When the passive machine takes over, it starts up quickly because most of the model is already loaded to memory.
The instructions that follow explain how to upgrade HP Universal CMDB (UCMDB) from version 9.05 to version 10.00.
Note:
The upgrade process runs offline, during which time all resources and data are transformed from 9.0x to work with the version 10.00 system.
When upgrading a high-availability environment, ensure that the active UCMDB Server and the passive UCMDB servers in the cluster are upgraded to or are running UCMDB 10.00.
For HP Software-as-a-Service customers, the upgrade runs on all customers at once.
It is recommended to read through the whole procedure before commencing the upgrade process.
If you have any version of HP Universal CMDB earlier than 9.05, upgrade to version 9.05 before upgrading to version 10.00. For details on upgrading HP Universal CMDB from version 8.0x (8.04 and later) to 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.
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.0, the History and CMDB schemas are combined. Back up both schemas individually to ensure correct binding during the version 10.00 upgrade.
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 schema 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.
For all out-of-the-box adapters: If you modified an adapter configuration in version 9.05, it is highly recommended that you save all adapter files from that version, and redo the modifications on the adapter files of version 10.00.
For all non out-of-the-box adapters: You must redeploy the adapters in version 10.00. For details, see the section describing the Package Manager in the HP Universal CMDB Administration Guide.
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.00. Do not copy files from version 9.05 and overwrite the files in version 10.00.
UCMDB uses the encryption key to encrypt credentials information and to send sensitive credentials 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 9.05 server. The encryption key is located in:
C:\hp\UCMDB\UCMDBServer\root\lib\server\discovery\key.bin
Back up the C:\hp\UCMDB\UCMDBServer\conf\security folder. This will be copied into the same location in version 10, after the upgrade.
Note:
Perform the following procedure only if you intend to install UCMDB version 10.00 Server on the same machine where UCMDB version 9.05 is installed.
If you are using two or more servers, you do not need to uninstall 9.05 before upgrading to 10.00 and you can skip to the next step, Upgrading UCMDB - Uninstall the Data Flow Probes.
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 that will be used in the version 10.00 cluster.
Stop the UCMDB Server: Start > All Programs > HP UCMDB > Stop HP Universal CMDB Server.
Uninstall the Server:
In a high-availability environment, you must uninstall the active server and all the passive servers.
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.
When uninstall is complete, a confirmation message is displayed. Click Done to complete the uninstall process.
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.
When uninstall is complete, a confirmation message is displayed. Click Done to complete the uninstall process.
Remove the entire C:\hp\UCMDB folder from the UCMDB Server machine.
Remove the entire opt/hp/UCMDB folder from the UCMDB Server machine.
Restart the machine.
Stop the old Probes: Start > All Programs > HP UCMDB > Stop Data Flow Probe
Stop the old Probes: /opt/hp/UCMDB/DataFlowProbe/bin/ProbeGateway.sh stop
Uninstall all existing Probes.
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
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
The following procedure explains how to install a UCMDB Server on a Windows machine.
Note: If you are using two or more servers, and you did not uninstall the 9.05 instance from your machine, you must stop the 9.05 instance before installing version 10.00. (Start > All Programs > HP UCMDB > Stop HP Universal CMDB Server)
Locate the UCMDB executable file: HPUCMDB_Server_10.00.exe.
Double-click the file to open the splash screen.
Note: If the digital signature is not valid, you should not install UCMDB. In this case, contact HP Support.
Choose the locale language and click OK.
The Introduction page opens. Click Next.
The License Agreement page opens.
Accept the terms of the license and click Next.
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 spaces.
Tip: To display the default installation folder again, click Restore Default Folder.
Click Next.
The Select Installation Type page opens. Select New Installation, and click Next.
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.
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.
Click Done to complete the installation.
If you had Data Flow Probes installed on the previous system, continue with the Data Flow Probe installation.
The following procedure explains how to install the UCMDB Server on a Linux machine.
Note: If you are using two or more servers, and you did not uninstall the 9.05 instance from your machine, you must stop the 9.05 instance before installing version 10.00 (/opt/hp/UCMDB/UCMDBServer/bin/server.sh stop).
Prerequisite: Apply one of the following configurations to the Linux machine:
Option 1:
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.
Run the following executable: sh <the path to the installation file>/HPUCMDB_Server_10.00.bin.
The UCMDB installation opens.
Choose the locale language and click OK.
The Introduction page opens. Click Next
The License Agreement page opens.
Accept the terms of the license and click Next.
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 spaces.
Note: To display the default installation folder again, click Restore Default Folder.
Click Next.
The Select Installation Type page opens. Select New Installation, and click Next.
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.
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 the bin subfolder of the installation folder.
Click No. You will set up the database or schema later.
Click Done to complete the installation.
If you had Data Flow Probes installed on the previous system, continue with the Data Flow Probe installation.
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 Probe installation, you must 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 virtual IP 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 will run 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 integration use only, and cannot be used for discovery.
Only integration with BSM version 9.01 and later is supported on the Probe on Linux.
An instance of MySQL database must not be running on the machine on which you are installing the Data Flow 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.
yum install dos2unix
.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:
Insert the HP Universal CMDB 10.00 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.
Double-click the <DVD root folder>\UCMDB10\HPUCMDB_DataFlowProbe_10.00.exe file.
A progress bar is displayed. After the initial process is complete, the splash screen opens. Choose the locale language and click OK.
The Introduction page opens. Click Next.
The License Agreement page opens.
Accept the terms of the agreement and click Next.
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 Discovery and Integration Content Guide
Click Next.
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.
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 virtual IP 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.
If you do not enter the address of the application server, 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.
Click Next.
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
Select Use Default CMDB Domain to use the default
The Default UCMDB Domain is also configurable in UCMDB's Infrastructure Settings module. For details, see the HP Universal CMDB Administration Guide.
Click Next.
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
Note: For external domains, this value must be identical to the Data Flow Probe Identifier defined in the previous step.
Click Next.
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. You would probably 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.
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.
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 DiscoveryProbe.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 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 Probe.
The Pre-Installation Summary page opens. Review the selections you have made and click Install to complete the installation of the Probe.
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.
Note:
If you installed the Probe on a Windows 2008 machine:
Locate the wrapper.exe file in the C:\hp\UCMDB\DataFlowProbe\bin folder.
Right-click the wrapper.exe file and select Properties.
In the Compatibility tab:
Select Compatibility mode.
Select Run this program in compatibility for: Windows XP (Service Pack 2).
Select Run this program as administrator.
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.
Tip: The Probe is displayed in
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:
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...
The Introduction page opens. Click Next.
The License Agreement page opens.
Accept the terms of the agreement and click Next.
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:
Click Next.
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 virtual IP 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.
If you do not enter the address of the application server, 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.
Click Next.
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.
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.
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.
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 DiscoveryProbe.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 DiscoveryProbe.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 Probe.
The Pre-Installation Summary page opens. Review the selections you have made and click Install to complete the installation of the Probe.
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/.
Activate the Probe.
Note: The user running the Probe service must be a member of the Administrators group.
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.
This section explains how to set up the Data Flow Probe when the Probe Manager and Probe Gateway run as separate processes on two machines.
Note:
Set up the Probe Gateway machine.
Open the following file:
C:\hp\UCMDB\DataFlowProbe\conf\probeMgrList.xml
Locate the line beginning <probeMgr ip=
and add the Manager machine name or IP address, for example:
<probeMgr ip="OLYMPICS08">
Open the following file:
C:\hp\UCMDB\DataFlowProbe\conf\DiscoveryProbe.properties
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
Set up the Probe Manager machine.
In C:\hp\UCMDB\DataFlowProbe\conf\DiscoveryProbe.properties:
Locate the line beginning appilog.collectors.local.ip =
and enter the Manager machine name or IP address, for example:
appilog.collectors.local.ip = OLYMPICS08
Locate the line beginning appilog.collectors.probe.ip =
and enter the Gateway machine name in uppercase, for example:
appilog.collectors.probe.ip = STARS01
Start the services.
On the Probe Manager machine, start the Manager service:
Start > All Programs > UCMDB > Start Data Flow Probe Manager
On the Probe Gateway machine, start the Gateway service:
Start > All Programs > HP UCMDB > Start Data Flow Probe Gateway
You can connect a Data Flow Probe to a customer that is not the default customer. The default customer ID is 1.
Open the following file in a text editor:
Windows: C:\hp\UCMDB\DataFlowProbe\conf\DiscoveryProbe.properties
Linux: ../DataFlowProbe/conf/DiscoveryProbe.properties
Locate the customerID
entry.
Update the value with the customer ID, for example, customerId = 2
.
Restart the Probe so that it is updated with your changes.
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.
Replace the C:\hp\UCMDB\UCMDBServer\conf\discovery\key.bin file with the file you saved earlier.
When upgrading a high-availability environment, you need to clean out the backed up database schema tables and flows.
Connect to the backed up database using a database client tool.
Empty and update the schema tables and flows as follows:
update CUSTOMER_REGISTRATION set CLUSTER_ID=null;
truncate table CLUSTER_SERVER;
truncate table SERVER;
truncate table CLUSTERS;
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.
Launch the upgrade file: C:\hp\UCMDB\UCMDBServer\tools\upgrade.bat
Launch the upgrade file: upgrade.sh
The Preparing to Upgrade wizard opens. Click Next to open the UCMDB Server Upgrade page.
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.
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.
The Advanced Settings page opens.
Enable Multi Tenancy. Select this option if UCMDB is to work in a Multi Tenancy environment.
Note: This setting cannot be enabled after the upgrade.
Enable search. Indexes UCMDB data for efficient search capabilities.
Note: Clear this option if you do not use the UCMDB Browser.
Click Next.
The Run Upgrade page lists the upgrade steps. Click Run to begin the upgrade.
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.
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. |
The following steps may be necessary after the upgrade.
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. During the upgrade, the JMX console username and password are reset to the default sysadmin/sysadmin. If you changed the JMX console username and password in your previous version, you must update these values manually after the upgrade. For 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.00. Do not copy files from version 9.05 and overwrite the files in version 10.00. For all non-out-of-the-box adapters, you must redeploy the adapters. For details, see the section describing the Package Manager in the HP Universal CMDB Administration Guide.
Transform Discovery Wizards into Discovery Activities. Discovery wizards are no longer supported in Universal Discovery. Instead, Universal Discovery use a similar resource called discovery activities. The resource name is the same (discoveryWizard), and is located in Adapter Management under the package it previously resided. 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 the 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.
If you want to rerun the Upgrade tool to rerun all the upgrader steps from the beginning, you must first do the following:
This section describes the installation, startup, and configuration procedures for HP Universal CMDB to run in high availability mode.
The information provided below assumes that you have an active UCMDB Server installed and configured..
High Availability mode is not supported in a multiple-customer environment.
Prerequisites
The typical configuration is an active UCMDB server and a passive UCMDB server.
This procedure assumes that you have an active UCMDB server installed and configured.
Install the passive UCMDB Server
The passive UCMDB Server is another machine which is used as a backup for the active UCMDB Server in case of failure.
Note:
The machines used for the active and passive UCMDB Servers should have similar hardware (especially the same amount of memory) and should be running the same operating system.
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.
Install the passive UCMDB Server as you did the active UCMDB Server with one difference: when running the Server Configuration wizard to configuring the database on the passive UCMDB Server, select Connect to an existing schema, and provide the details of the schema you created for the active UCMDB Server.
For details on installing UCMDB Servers, see Installing the UCMDB Server - Installation.
Complete the Server Startup
If the active UCMDB Server is not started, start the process. Wait until the startup process is complete.
Access server_management.bat (the Server Management Tool) located in C:\hp\UCMDB\UCMDBServer\tools\.
Run server_management.sh located in /opt/hp/UCMDB/UCMDBServer/tools/.
On the login page, enter the active UCDMB Server name and credentials.
If the default HTTPS port is being used (port 8443), enter the UCMDB Server name only, for example, localhost.
If the HTTPS port has been changed, enter the Server name and the new port, for example: localhost:443.
Enter the user name and password of the Server Administrator user (the default is sysadmin and sysadmin).
Note: The connection from the tool to the HP Universal CMDB Server is made through HTTPS which is enabled by default, and configured with port 8443.
In the Server Management Tool, in the left menu, select Clusters.
Click the New Cluster button to create a new cluster.
In the Add Server box, enter the machine name of the passive UCMDB Server that you installed, and click Add.
Note: High Availability servers should be configured with short server names (not with IP addresses).
Note: High Availability servers should be configured with the result of Linux command: "hostname -f" which is the fully qualifies domain name.
In the Server Name list, select the UCMDB Server that is to be the active UCMDB Server, click Set Active, and click OK.
When prompted about switching all existing customers to the active UCMDB Server, click Yes.
Start the passive UCMDB Server.
Tip: You can start the passive UCMDB Server from within the Server Management tool.
Note: If, after you have completed this procedure, you want to change the active UCMDB Server, do this as follows (to prevent database inconsistency):
Stop the active UCMDB Server from the machine itself. After a short time, the passive UCMDB Server automatically becomes the active UCMDB Server. Then start up the UCMDB server that was previously active.
Configure the Load Balancer
On the Load Balancer machine, define the virtual IP for the two HP Universal CMDB Servers with the following configuration:
Select the same port as defined for the UCMDB Servers. (In UCMDB go to Administration > Infrastructure Settings).
Verify that the virtual IP is configured per cluster.
The keep alive address for the session is:
http://<UCMDB-Server:port>/ping/?clusterId=<clusterId>.
An active Server in the cluster returns HTTP response 200 (OK). A passive Server returns HTTP response 503 (service unavailable).
Active and Passive are printed to the HTML page when browsing to the keep alive page of the active or passive server, respectively.
Note: Note down the load balancer IP address. When defining the communication settings between the UCMDB Server and other components, such as the Data Flow Probe, always use this load balancer virtual IP when prompted for the UCMDB Server name.
Configure the Probe
When you install the Data Flow Probe, use the load balancer virtual IP address when defining the HP Universal CMDB Server name.
If you already have a Probe installed:
To improve start up times for the passive machines during a transition from the active machine, HP Universal CMDB starts the passive machines in partial mode.
In this case, the Model Topology component on the passive machines is started in read-only mode. Then it is synchronized with the changes occurring on the active Server, by the UCMDB database, every few seconds.
When the passive machine takes over, it starts up quickly because most of the model is already loaded to memory.
The Configuration Manager deployment instruction provided takes into account special UCMDB deployments you may have in your environment (for example, high availability deployment) and provides the necessary adjustments to the deployment procedure for those deployments.
Note: Installing both UCMDB and Configuration Manager together on the same server is supported. For scaling purposes in a production environment, HP Software recommends that you install these components on separate servers.
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.
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:
Prerequisites:
If UCMDB is set up as a high-availability environment:
Configuration Manager must be installed on a third server (not on either of the UCMDB servers). Use the load balancer virtual IP details when asked for the UCMDB connection details.
Launch the Configuration Manager installation: insert the UCMDB DVD into the machine. Do one of the following:
Accept the terms of the End User License Agreement and click Next..
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.0.
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.
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.
|
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 (_). |
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.
Two types of databases are available – Oracle and MS SQL. The input fields change according to the database type selected.
Note: 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.
Caution: Repopulating the database deletes all existing tables and data.
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. |
Click Test to test the connection settings and then click Next to continue to the Server Ports Configuration page.
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 |
8009 (Apache Java Protocol) |
Application HTTP Port |
8180 |
Application HTTPS Port |
8143 |
JMX HTTP Port |
39900 |
JMX Remote Port |
39600 |
Tomcat Port |
8005 |
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.
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.
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.
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.
Note: High Availability: Ensure that UCMDB and Configuration Manager are both working properly and then restart the passive UCMDB Server.
The upgrade procedure assumes the following before beginning:
that there is a working connection to the UCMDB server.
that the necessary CUP patch has been installed for UCMDB.
If any of these items have not been installed or configured properly, you will see an error message informing you of this. You can fix the indicated problem and then perform the upgrade.
If the upgrade fails because you cannot connect to UCMDB, check that the UCMDB server is up and running.
If the upgrade fails due to the patch not being installed, install the necessary CUP patch according to the instructions found at the HP Software support site: http://support.openview.hp.com/selfsolve/patches
To upgrade, perform the following steps:
Note: Before you begin the upgrade procedure, make sure that:
Back up your Configuration Manager and UCMDB schemas.
To start the installation, insert the Configuration Manager installation media into the machine. Do one of the following:
Click Next to open the End User License Agreement page.
Accept the terms of the license and click Next.
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.0.(on Windows systems) or /root/HP/CM_10.0.0.0 (on Linux systems). Click Next to accept the default location, or click Browse to select a different location and then click Next.
Note: The installation directory must not contain spaces in its name.
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 9.30 (whether you are upgrading from either 9.30 or 9.31).
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.
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.
The following data is included in the upgrade:
Roles
Environments
If a conflict exists with an existing resource group, a new resource group is created with _CM appended to the resource group name.
User groups
If no user group with the existing name is found, a new user group is created.
If a conflict exists with an existing user group, the user groups are merged. The merged information is the associated roles and the group's relations. If the merge fails, errors are reported in the UpgradeUserReport.log file for all user groups.
Users
If no user with the existing name is found, a new user is created.
The UpgradeUserReport.log file (located in the <Configuration Manager installation directory/_installation/logs folder) contains information about the following:
Note: System administrators (who automatically had Automation permission in Configuration Manager version 9.3x) will no longer have such permission after upgrading.
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 support.
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.
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.00.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
VALIDATE_PING_TO_UCMDB=true
# 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_HOST_IP=
UCMDB_DOMAIN=
UCMDB_PROTOCOL=
UCMDB_PORT=
# Enter the full path for the UCMDB Foundation certificate file (.cer file only) UCMDB_CLIENT_CERT_FILE=
UCMDB_CUSTOMER_NAME=
UCMDB_JMX_PORT=
UCMDB_SYSTEM_USER=
UCMDB_SYSTEM_PASSWORD=
# CM host
CM_DOMAIN=
CM_HOSTNAME=
# 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=
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.
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:
In the <Configuration Manager installation directory>/_installation folder, run HPCM_10.00.exe (on Windows systems) or HPCM_10.00.bin (on Linux systems), without repopulating the database. . The End User License Agreement is displayed. Select the radio button and click Next to continue.
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.
Continue with the reconfiguration You can update the following information:
UCMDB Foundation connection information
Field |
Definition |
---|---|
Host Name |
UCMDB deployment location 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
Two types of databases are available – Oracle and MS SQL. The input fields change according to the database type selected.
Note: 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.
Caution: Repopulating the database deletes all existing tables and data.
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 |
8009 (Apache Java Protocol) |
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.
On a Linux system:
Use a command line prompt:
To start the Configuration Manager server:
$ cd /<Configuration Manager installation directory> $ ./start-server-0.sh
You can create a script in the /etc/init.d directory to automatically start Configuration Manager on machine startup.
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.
To uninstall Configuration Manager, do one of the following:
On Windows systems |
From the Start menu:
From the Control Panel:
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. |
During the installation of HP Universal CMDB, a start menu is added to the settings of the machine on which you installed UCMDB. You can start and stop the UCMDB Server and the UCMDB Integration Service, access the Server Configuration wizard and view Server service status, and you can uninstall the Server.
If there is a Data Flow Probe installed on the same machine as the UCMDB Server, you can start and stop the Data Flow Probe, as well as uninstall it, from this menu.
To access the HP Universal CMDB start menu, select Start > Programs > HP UCMDB. The menu includes the following options:
Command | Description |
---|---|
Start HP Universal CMDB Server |
Starts the UCMDB Server service. Note: Alternatively, you can access the Windows Services window and locate the UCMDB_Server service. Open the UCMDB_Server Properties (Local Computer) dialog box and start the service. If required, change the Startup Type to Automatic. |
Stop HP Universal CMDB Server |
Stops the UCMDB Server service. Note: Alternatively, you can access the Windows Services window and locate the UCMDB_Server service. Open the UCMDB_Server Properties (Local Computer) dialog box and stop the service. |
HP Universal CMDB Server Status | Opens a Web page with information about the server. For details, see Getting Started with UCMDB - HP UCMDB Services. To open a Web page with information about the UCMDB UI Server Status, enter the following URL: http://<UCMDB Server Host Name or IP>:8080/ucmdb-ui/status.jsp
Note: The link to the Server Status page is only displayed if the Show Status Page link on first page infrastructure setting is set to True. |
Start HP Universal CMDB Server Configuration Wizard | Enables you to run the wizard to connect to an existing database or schema or to create a new database or schema. For details, see Creating a Database or Connecting to an Existing One?. |
Uninstall HP Universal CMDB Server | Uninstalls the UCMDB Server. |
Start HP Universal CMDB Integration Service
|
Starts the UCMDB Integration Service which allows performance of non-Jython-based integration tasks without using a Data Flow Probe if your remote managed data repositories are accessible from the UCMDB Server machine. Note:The UCMDB Integration Service and the Data Flow Probe (if installed on the UCMDB Server machine) cannot be running at the same time.To start the UCMDB Integration Service, you must first stop the Data Flow Probe. See Stop Data Flow Probe below. |
Stop HP Universal CMDB Integration Service
|
Stops the UCMDB Integration Service. |
Inventory Tools |
Enables you to access the Inventory Tools (and supporting documentation) that are used for viewing and analyzing data discovered by Inventory Discovery. Available: Only when a Data Flow Probe is installed on the UCMDB Server machine. |
Start Data Flow Probe |
Starts the Data Flow Probe on the UCMDB server. If the Data Flow Probe is installed on the UCMDB Server machine: The Data Flow Probe and the UCMDB Integration Service cannot be running at the same time. To start the Data Flow Probe, you must first stop the UCMDB Integration Service. See Stop HP UCMDB Integration Service above. Available: Only when a Data Flow Probe is installed on the UCMDB Server machine. |
Start Data Flow Probe (console) |
Starts the Data Flow Probe on the console. Available: Only when a Data Flow Probe is installed on the UCMDB Server machine. |
Stop Data Flow Probe |
Stops the Data Flow Probe. Available: Only when a Data Flow Probe is installed on the UCMDB Server machine. |
Uninstall Data Flow Probe |
Uninstalls the Data Flow Probe. Available: Only when a Data Flow Probe is installed on the UCMDB Server machine. |
Run the following commands to start and stop the UCMDB Server, to access the Database Configuration wizard, Server service status, and to uninstall the Server.
Note: The following commands assume that UCMDB is installed on the default path, that is, /opt/hp. If the Server is installed elsewhere, substitute that path for /opt/hp.
Command | Path |
---|---|
To start the HP Universal CMDB server | /opt/hp/UCMDB/UCMDBServer/bin/server.sh start |
To stop the HP Universal CMDB server | /opt/hp/UCMDB/UCMDBServer/bin/server.sh stop |
To call the HP Universal CMDB Server Configuration wizard | /opt/hp/UCMDB/UCMDBServer/bin/configure.sh |
To access the UCMDB Server Status Web pages |
Note:
|
To start the HP Universal CMDB Integration Service
|
/opt/hp/UCMDB/UCMDBServer/integrations/bin/service.sh start The UCMDB Integration Service allows performance of non-Jython-based integration tasks without using a Data Flow Probe if your remote managed data repositories are accessible from the UCMDB Server machine. Note:The UCMDB Integration Service and the Data Flow Probe (if installed on the UCMDB Server machine) cannot be running at the same time.To start the UCMDB Integration Service, you must first stop the Data Flow Probe. See Stop Data Flow Probe below. |
To stop the HP Universal CMDB Integration Service
|
/opt/hp/UCMDB/UCMDBServer/integrations/bin/service.sh stop |
To start the Data Flow Probe |
/opt/hp/UCMDB/DataFlowProbe/bin/probegateway.sh start If the Data Flow Probe is installed on the UCMDB Server machine: The Data Flow Probe and the UCMDB Integration Service cannot be running at the same time. To start the Data Flow Probe, you must first stop the UCMDB Integration Service. See Stop HP UCMDB Integration Service above. Available: Only when a Data Flow Probe is installed on the UCMDB Server machine. |
To stop the Data Flow Probe |
/opt/hp/UCMDB/DataFlowProbe/bin/probegateway.sh stop Available: Only when a Data Flow Probe is installed on the UCMDB Server machine. |
To uninstall the UCMDB Server | /opt/hp/UCMDB/UCMDBServer/UninstallerData/Uninstall_UCMDBServer |
To configure the UCMDB Mail server:
The following procedure enables integration of UCMDB with SiteMinder:
Prerequisites:
Set up IIS to enable access to UCMDB.
For details, see Getting Started with UCMDB - Accessing HP Universal CMDB Through the IIS Web Server.
Enable AJP connections.
In the Administration module, select Infrastructure Settings Manager > General Settings, and set Enable AJP Connections to True.
Configure UCMDB to enable LW-SSO:
Enable logging in to UCMDB with LW-SSO. For details, see the HP UCMDB Hardening Guide.
In the JMX console, invoke the setUserName method and set the LW-SSO IDM user name settings as follows:
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.
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.
Problem:
Solution:
In the General tab, ensure that:
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).