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

This guide references the following sections in the UCMDB Online Help:

• Support Matrix section
• Database section
• Hardening section
• Administer section
• Modeling section
• Data Flow Management section
• Configuration Manager section
• Backup and Recovery section

Pre-deployment Planning

Deploying Universal CMDB in an enterprise network environment is a process that requires resource planning, system architecture design, and a well-planned deployment strategy. The following checklist describes some of the basic issues that should be considered prior to installation. For comprehensive best practices documentation on deployment planning, consult with Professional Services.

Use the following checklist to review the basic issues that your organization should consider when planning the Universal CMDB deployment.

The following recommendations are for increasing the security of your overall infrastructure for informational purposes only. These are only recommendations and are not intended to be a guarantee of protection against all potential vulnerabilities and attacks. Please note that some security measures may impact the features and functionality of your overall system; so, it is recommended that every customer become aware of those impacts when implementing any changes to your environment.

Use of this Micro Focus Software Product [CMS] may require the pre-installation of certain third-party components that are not provided by Micro Focus ("Third Party Components"). It is recommended that its customers check frequently for the most current updates to the Third Party Components, which may include fixes or patches for security vulnerabilities.

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.

   Set up a remote PostgreSQL Server.

   Note: This step is necessary only if you are installing the PostgreSQL server remotely. If your intention is to install a PostgreSQL database locally on the machine where you install UCMDB server, follow the instructions in the UCMDB Server installation procedure.

2. Install the Universal CMDB Server.

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

   Install the Universal CMDB Servers.

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

3. Install Universal CMDB Configuration Manager

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

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

5. Secure the UCMDB Server

   For details, see the Hardening section of the CMS online help.

6. Secure the Data Flow Probe.

   For details, see the Hardening section of the UCMDB online help.

7. Launch Universal CMDB.

Consider the following prior to installing Universal CMDB on Windows:

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

• Do not install 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)

• 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 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 Universal CMDB Server contains underscores, it may not be possible to log in to 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.

• Ensure that the network adapter on the machine on which you are installing Universal CMDB is configured with the desired IP interface (IPv4/IPv6).

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

• 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 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 Universal CMDB servers contain underscores, it may not be possible to log in to 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.

• Ensure that the network adapter on the machine on which you are installing Universal CMDB is configured with the desired IP interface (IPv4/IPv6).

  Note: Configure these settings from the configuration file in /etc/sysconfig/network-scripts/ifcfg-eth0

• Database requirements

  • It is strongly recommended to host database server (Oracle, Microsoft SQL, or PostgreSQL) on a physical machine, and it should be an independent server without other applications (including the UCMDB server) running on it.

    Also, if the database server machine is a virtual machine, the resource MUST be dedicated for the database server.

  • Apart from the embedded PostgreSQL database server, installing UCMDB server and database server (Oracle, Microsoft SQL, or PostgreSQL) together on the same machine is not supported.
  • The hardware requirements could be the same as those for UCMDB server, but the DB SPACE depends on the data scale. For example, for a data scale of 30 million CIs, we recommended 500 GB or more space for data files and 200 GB or more space for log files.
• Embedded PostgreSQL is only supported for small deployments of UCMDB.

• (Embedded PostgreSQL database only) On Linux platform, if you plan to use the embedded PostgreSQL database, make sure you do the following:

  1. Uninstall the local PostgreSQL that comes with the Linux installation.

     Note: On Linux systems, there is a conflict between the embedded PostgreSQL that comes with UCMDB and the local PostgreSQL that comes with the Linux installation. If you don't uninstall the local PostgreSQL that comes with the Linux installation, you won't be able to log in to UCMDB server later due to the conflict.

  2. Install the UCMDB server, and on the Install Local PostgreSQL DB wizard page, select Yes to install the embedded PostgreSQL database that comes with UCMDB server. For detailed instructions, see the Installing the UCMDB Server - Installation section below.
  3. Configure UCMDB server to connect to the embedded PostgreSQL database. For detailed instructions, see the Installing UCMDB - Configure the Database section below.

• In High Availability environments,

  • the machines used for the UCMDB Servers should have similar hardware and the same amount of memory.

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

1. On the first page of the UCMDB Server Configuration wizard, click Next.

2. On the CMDB Schema page, select Create a new schema or Connect to an existing schema and click Next.

   Note: When connecting to an existing schema:

   • The CMDB schema version must match the server version. If the versions do not match, an error message is displayed and you must re-enter the schema settings.

   • The version of the UCMDB Discovery and Integrations Content Pack in the file system (installation folder) must be the same as the version in the schema.

3. The CMDB Schema Settings page opens.

   In the DB Type list, select Oracle and click Next. Additional fields appear in the dialog box.

   In the DB Type list, select MS SQL Server and click Next.

   In the DB Type list, select PostgreSQL Server and click Next.

4. Enter the details of the schema:

   • Schema name. The schema name should be unique.

   • Default tablespace. Update this field.

   • Temporary tablespace. If your database administrator created a non-default temporary tablespace, enter that name; otherwise, enter temp.

   Enter the host name and database name, and decide which authentication Universal CMDB should use to connect to the database server. For details on Windows authentication, see Universal CMDB Deployment Guide in the Database section.

   Enter the details of the schema.

   • If you are installing a local PostgreSQL database, ensure that the details of the PostgreSQL database are defined correctly.

     • Host name. localhost
     • Port. 5431
     • Schema name. Provide a Schema name of your choice, for example, ucmdb_database.
     • Username and Password. Provide the credentials you configured during the UCMDB installation.
   • If you are connecting to a remote PostgreSQL Server, delete the default values, and provide the relevant information.

   Note: Ensure that the Schema name follows the PostgreSQL naming conventions:

   • The name can contain only lowercase letters, numbers, and underscores
   • The first character must be a lowercase letter.
   • Maximum allowed length is 63 characters

   Click Next.

5. The Advanced Settings page opens:

   • Enable Multi Tenancy. Select this option if you are setting up UCMDB to work in a multi-tenancy environment.

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

   • Enable Search. Select this option to enable UCMDB data indexing for efficient search capabilities.

     Note: Select this option if you will use any of the following:

     • UCMDB Browser
     • Service Discovery
     • Consumer-provider dependency adapters
6. Click Finish to close the UCMDB Server Configuration wizard.

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

2. IMPORTANT! Before you start the UCMDB Server, copy the encryption key (key.bin) that you backed up before you started the upgrade procedure to the following folder on the new machine:
   

   C:\hp\UCMDB\UCMDBServer\conf\discovery\

   /opt/hp/UCMDB/UCMDBServer/conf/discovery/

3. Configure the JVM startup parameter:

   1. Open C:\hp\UCMDB\UCMDBServer\bin\wrapper.conf/opt/hp/UCMDB/UCMDBServer/bin/wrapper.conf

   2. Locate the following line:

      wrapper.java.additional.<#>=-Djava.net.preferIPv4Stack=

      • In an IPv4 or IPv4-IPv6 environment:, ensure that the Djava.net.preferIPv4Stack=true

      • In an IPv6-only environment, configure the UCMDB Server machine for IPv6 only by commenting out this whole line.

4. Start the UCMDB Server:

   Start > All Programs > UCMDB > Start Universal CMDB Server

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

   Note:  

   • If you ran the UCMDB Server Configuration Wizard as part of Universal CMDB Server installation, you must start 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 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.

5. (CyberArk integration only)

   Check if new hash value is the same as the one you configured in the CyberArk server. If different, re-generate the hash value using the following command:

   java -Xms500m -Xmx1200m -jar JavaAIMGetAppInfo.jar GetHash /AppExecutablesPattern="C:\hp\UCMDB\DataFlowProbe\lib" /OnlyExecutablesWithAIMAnnotation=yes /LogFileDirectory="c:\temp"

   And then fill the newly generated hash value into the CyberArk server.

1. To uninstall Universal CMDB:

   Windows

   On the UCMDB Server machine, select Start > All Programs > UCMDB > Uninstall Universal CMDB Server. The Uninstall Universal CMDB Server wizard opens. Click Uninstall. The Remove Configuration Files dialog box opens. Select whether or not to remove the server configuration files. If UCMDB has an embedded PostgreSQL database, the Remove PostgreSQL Directory dialog box opens. Select whether or not to remove the embedded (local) PostgreSQL database file. When uninstall is complete, a confirmation message is displayed. Click Done to complete the uninstall process.

   Linux

   On the UCMDB Server machine, execute the Uninstall_UCMDBServer script from the UninstallerData subfolder of the Installation folder. From the same location, select Uninstall to uninstall the Universal CMDB Server. The Remove Configuration Files dialog box opens. Select whether or not to remove the server configuration files. If UCMDB has an embedded PostgreSQL database, the Remove PostgreSQL Directory dialog box opens. Select whether or not to remove the embedded (local) PostgreSQL database file. When uninstall is complete, a confirmation message is displayed. Click Done to complete the uninstall process.

2. To uninstall a Data Flow Probe:

   Windows

   Note: Starting with version 10.33, the probe auto upgrade mechanism supports upgrading Data Flow Probes on Windows directly for versions 10.22 (with or without a CUP) and later (union and non-FIPS mode). Only for probes of unsupported versions, you need to uninstall the old version and then install the latest version manually. On the machine where the Probe is installed: Stop the Probe: Start > All Programs > HP UCMDB > Stop Data Flow Probe 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

   Linux

   On the machine where the Probe is installed: Stop the Probe: /opt/hp/UCMDB/DataFlowProbe/bin/ProbeGateway.sh stop 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.

• The following diagram may help you understand the overall UCMDB server and Data Flow Probes upgrade process:

  

• It is recommended that you back up your original environment (UCMDB Server and database) prior to upgrading your environment.

• If you enabled HTTP communication for UCMDB server before the upgrade, or you are upgrading UCMDB server from a version earlier than 10.30, after you have upgraded the UCMDB server to version 10.33 successfully, make sure you enable HTTP communication and change the master key before you restart the UCMDB server for the probe auto upgrade agent to perform probe auto upgrade.

• It is recommended, prior to upgrading your environment, to clone your original environment (UCMDB Server and database) to a new environment and perform the upgrade on the cloned environment. This way, the original server can continue to be up and running during the upgrade procedure. Performing the upgrade on a cloned database also enables you to deal with upgrade issues while not affecting the down time of the original server.

  Once everything is up and running on the upgraded cloned environment, you can upgrade the original Server, and then connect it to the database on the upgraded cloned environment.

  In summary:

  1. Clone the original (current) environment.

     Note: It is strongly recommended, after the database schema has been cloned, not to make any changes on the original environment as those changes will not be migrated to the upgraded environment.

  2. Upgrade the cloned environment to 10.33.
  3. Once everything is up and running on the upgraded cloned environment, disconnect the original Server and database, and uninstall the UCMDB Server from the original machine.
  4. Disconnect the Server and the database on the upgraded cloned environment.
  5. Install UCMDB 10.33 on the original machine, connecting it to the cloned 10.33 database.

  

This section provides estimated upgrade durations, based on tested environments. Upgrade durations will vary depending on your hardware configuration, UCMDB data set, and database performance.

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

Back up the encryption key that is on the UCMDB Server. The encryption key is located in:

Back up the C:\hp\UCMDB\UCMDBServer\conf\security/opt/hp/UCMDB/UCMDBServer/conf/security folder.

Back up the following:

• The C:\hp\UCMDB\UCMDBServer\integrations\conf\DataFlowProbe.properties/opt/hp/UCMDB/UCMDBServer/integrations/conf/DataFlowProbe.properties file
• The C:\hp\UCMDB\UCMDBServer\integrations\conf\security/opt/hp/UCMDB/UCMDBServer/integrations/conf/security folder

If the Java JMX access hardening was performed:

1. Edit the file permissions for the following file, so that the user you are logged in with can edit it:

   C:\hp\UCMDB\UCMDBServer\bin\jre\lib\management\jmxremote.password

   /opt/hp/UCMDB/UCMDBServer/bin/jre/lib/management/jmxremote.password

2. Save the file outside of the UCMDB installation folder.

1. Stop the UCMDB 10.xx Server.

   Note:  

   • High-availability environment: If your current environment is a high-availability environment, stop all the UCMDB Servers in the UCMDB Server cluster.

   • Standalone environment: If the UCMDB Integration Service is running, stop the service.

2. Run the UCMDB 10.33 installer.

   1. Locate the UCMDB executable file: UCMDB_Server_10.33.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 Micro Focus Software Support.

      Locate the UCMDB executable file: UCMDB_Server_10.33.bin, and run the following executable:

      sh <the path to the installation file>/UCMDB_Server_10.33.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.xx installation folder and click Next.

   6. On the Select Installation Type page of the installer, select Update from 10.x or 10.x CUP and click Next.

   7. On the Install Data Flow Probe page, select one of the following:

      • Automatically update Data Flow Probe to 10.33

        Select this option if the existing probes that report to the UCMDB server are of version 10.22 or later (with or without a CUP, union and non-FIPS mode on Windows machine). For supported upgrade paths, see Upgrading UCMDB - Introduction. For more details about Data Flow Probe auto upgrade, see "Data Flow Probe Auto Upgrade" in the Universal CMDB Data Flow Management Guide.

        If you do not choose this option now, but still want to leverage the probe auto upgrade feature after the UCMDB server upgrade, then when you have finished upgrading the UCMDB server, you can go to <UCMDB_Server>\content\probe_patch and copy the probe-patch-10.33-windows.zip package to the <UCMDB_Server>\runtime\probe_upgrade directory. Then restart the UCMDB server. UCMDB server will then perform probe auto upgrade.

      • Update the Data Flow Probe manually

        Select this option if the probes that report to the UCMDB server in your environment are on Linux or of versions not supported for auto upgrade. When you have finished upgrading the UCMDB server to version 10.33, you can uninstall the old version probe first, and then install version 10.33 probe manually. For details, see "Data Flow Probe - Windows Installation", "Data Flow Probe - Linux Installation" or "Data Flow Probe - Unattended Silent Installation".

   8. On the Deploy Content Pack page, select if you want to deploy Content Pack 24 and click Next.

   9. Specify the passwords to be used for keystore and truststore:

      • On the Set Up Keystore Password page, enter the password that you want to use for the keystore, and then enter the password again to validate it.

      • On the Set Up Truststore Password page, enter the password that you want to use for the truststore, and then enter the password again to validate it.

      Note:  

      • The keystore/truststore passwords setup will only be present if default passwords are used. If custom passwords are already in use, the wizard will not ask for them again.

      • The installer encrypts the above keystore/truststore passwords you provided in a newly generated file server-storepass.conf.

      • The keystore/truststore passwords must follow the password policy below:

        The password must contain 8 to 16 characters and include at least one of each of the following four types of characters:

        • Uppercase alphabetic characters
        • Lowercase alphabetic characters
        • Numeric characters
        • Special characters: ,\:/._=+-[](

   10. On the Summary page, click Install to start the installation.

   11. When the installation completes, click Done.

   Note: When upgrading from 10.xx to 10.33, it is not necessary to run the Server Configuration wizard because the system uses the schemas from the 10.xx installation.

3. If you imported SSL certificates in UCMDB 10.xx, 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\cacerts

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

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

4. Standalone environment: If you stopped the Integration Service above you must clear the Integration Service data:

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

5. IMPORTANT!

   Note: This step is relevant only if you are upgrading to 10.33 on a new machine, and if you customized the key.bin in your previous deployment.

   Before you start the UCMDB Server, you must copy the encryption key (key.bin) that you backed up before you started the upgrade procedure to the following folder on the new machine:
   

   C:\hp\UCMDB\UCMDBServer\conf\discovery\

   /opt/hp/UCMDB/UCMDBServer/conf/discovery/

6. If UCMDB patches have been installed on top of your current UCMDB version, you need to remove any Probe patch archive (.zip) files that might be left over in the system:

   Note:  

   • This step is relevant only if you are upgrading UCMDB on top of your current version—that is, on the same machine.
   • In a high-availability environment, repeat this procedure on each machine that is being upgraded.

   In the C:\hp\UCMDB\UCMDBServer\runtime\probe_upgrade/opt/hp/UCMDB/UCMDBServer/runtime/probe_upgrade folder, delete all .zip files that have the probe-patch prefix.

7. Start up the UCMDB 10.33 Server to complete the upgrade.

   Note: It may take several hours for the server to start up. You can follow the progress in the following log files (located in the ..\UCMDBServer\runtime\log folder):

   • servicepack.install.log
   • upgrade.short.log
   • upgrade.detailed.log

8. Standalone environment: If you stopped the Integration Service, restart it.

9. High-availability environment:

   If you are upgrading a high-availability environment, or your upgraded environment is to be a high-availability environment:

   1. Install UCMDB 10.33 on each of the machines that will be included in the UCMDB Server cluster:

      • If your current environment is a high availability environment , follow steps above to upgrade each UCMDB Server in the current the UCMDB 10.xx Server cluster to version 10.33.
      • To install new or additional servers, go back to the selection page of this interactive guide, and select Install UCMDB 10.33 and High Availability and following the generated instructions.
   2. Ensure that one of the UCMDB Servers in the cluster is up and running (has the Up status), and then start the other UCMDB Servers.

   Note: In UCMDB 10.33, all of the UCMDB Servers in a high-availability environment are active, while also providing high availability in case of server failure.

The following steps may be necessary after the upgrade.

• Set Master Key. If the master key is not set in the previous version of UCMDB, you must set the master key after upgrading to 10.33. Otherwise, the UCMDB UI is inaccessible. For more information about how to do this, see "How to Set Master Keys" in the Universal CMDB JMX Reference Guide.

• UCMDB Browser. When upgrading to 10.33, the UCMDB Browser 4.14 is automatically installed. If you are working with an earlier version of the UCMDB Browser, you must update it manually.

• Reverse Proxy. If the upgraded system is not going to run on the same machine as the previous version, you need to reconfigure the reverse proxy after the upgrade. For configuration details, see "Using a Reverse Proxy" in the Universal CMDB Hardening Guide.

• SSL.

  • Reinstall SSL configurations. For details, see "Enabling Secure Sockets Layer (SSL) Communication" in the Universal CMDB 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 "Lightweight Single Sign-On (LW‑SSO) Authentication" and "Enabling Login to Universal CMDB with LW-SSO" in the Universal CMDB 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/opt/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, see "Java JMX Access Hardening" in the Universal CMDB 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.33. Do not copy files from your previous version and overwrite the files in version 10.33.

• 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. For details, see "Universal Discovery " in the Universal CMDB Data Flow Management Guide.

  Re-enable aging from the Administration > CI Lifecycle module and restart the server. For details about aging, see "CI Lifecycle and the Aging Mechanism" in the Universal CMDB Administration Guide.

• CyberArk Integration. Check if new hash value is the same as the one you configured in the CyberArk server. If different, re-generate the hash value using the following command:

  java -Xms500m -Xmx1200m -jar JavaAIMGetAppInfo.jar GetHash /AppExecutablesPattern="C:\hp\UCMDB\DataFlowProbe\lib" /OnlyExecutablesWithAIMAnnotation=yes /LogFileDirectory="c:\temp"

  And then fill the newly generated hash value into the CyberArk server.

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.

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.

We provides the following recommendations for increasing the security of your overall infrastructure for informational purposes only. These are only recommendations and are not intended to be a guarantee of protection against all potential vulnerabilities and attacks. Please note that some security measures may impact the features and functionality of your overall system; so, it is recommended that every customer become aware of those impacts when implementing any changes to your environment.

Use of this Micro Focus Software Product [UCMDB Configuration Manager] may require the pre-installation of certain third-party components that are not provided by Micro Focus ("Third Party Components"). It is recommended that its customers check frequently for the most current updates to the Third Party Components, which may include fixes or patches for security vulnerabilities.

To install Configuration Manager:

1. Prerequisites:

   • Ensure that Universal CMDB is on version 10.22 CUP6 or a later version.

   • Configuration Manager automatically creates the CM New Policy and CM KPI integration points during installation, using the UCMDB Integration Service.

     Since the UCMDB Integration Service is not supported in a high availability environment, these integration points will be created in an unsupported configuration. You must therefore recreate these integration points manually after installation, using a remote Data Flow Probe. For details, see the Data Flow Management section of the UCMDB Help.

   • To allow Configuration Manager to automatically create integration points (used for federating data to UCMDB) in UCMDB, ensure that the UCMDB Integration Service is started and fully running before installing Configuration Manager.

     If you are using a remote Data Flow Probe, or creation of the integration points fails during installation of Configuration Manager, you can create the integration points manually. For details, see the Data Flow Management section of the UCMDB Help.

   • 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 HPECM_10.23.xx.exe file and double-click it to run the Configuration Manager Installation wizard.
   • Linux: Locate the HPECM_10.23.xx.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.2.1.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.

     Note: To continue the installation, you must enter a path that:

     • Is a valid Linux path.
     • Does not contain any spaces.

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 (FQDN)	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 FQDN.
   Protocol	HTTP or HTTPS (default) protocol.
   UCMDB Port	The HTTP or HTTPS port default values are 8080 for HTTP and 8443 (default) for HTTPS.
   Server Certificate	This field is available 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. Note: Note: The path to the certificate file cannot contain spaces. 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).
   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 provide an incorrect value, the deployment will fail.
   UCMDB root context	UCMDB root context, the default value is /. If this value is changed in UCMDB, this needs to be adjusted in CM as well. This way UCMDB-CM communication uses UCMDB root context.
   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.

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 MSSQL. 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 Support Matrix section of the UCMDB Help.

   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
   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 enable advanced content (out-of-the-box views and policies) is available only if you are connected to a UCMDB server on which an advanced license has already been installed.

    If you have not previously purchased and activated an advanced license, you can use the JMX console to enable the advanced content after installation.

    For details, see the section about licensed content in the Configuration Manager section of the CMS Online Help.

    Click Next to continue to the Pre-Installation Summary page.

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.

The upgrade procedure assumes the following before beginning:

• there is a working connection to the UCMDB server, which 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.

To upgrade Configuration Manager:

1. Back up the Configuration Manager installation folder.

2. Back up the Configuration Manager database.

3. Back up the following Windows registry entry:

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

4. Remove the old Configuration Manager service name by running the following command:

   sc [<ServerName>] delete [<ServiceName>]

   For example, sc delete HPUCMDBCM1001

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

   • On a Windows system, locate the HPECM_10.23.xx.exe file in the \Windows folder and double-click it.
   • On a Linux system, locate the HPECM_10.23.xx.bin file and run it. You can either run the installer in GUI mode (using X11 protocol), or run a silent installation.

6. Click Next to open the End User License Agreement page.

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

8. 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.2.1.0 (on Windows systems) or /root/HP/CM_10.2.1.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.

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 example, for the version number, enter 10.22.
   • 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 Micro Focus sales representative or Micro Focus 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 enable advanced content (out-of-the-box views and policies) is available only if you are connected to a UCMDB server on which an advanced license has already been installed.

    If you have not previously purchased and activated an advanced license, you can use the JMX console to enable the advanced content after upgrading.

    For details, see the section about licensed content in the Universal CMDB Configuration Manager User Guide.

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

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

To perform a silent installation of Configuration Manager:

Run the following command:

HPECM_10.23.xx.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_10.23
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=
UCMDB_CMDB_ROOT_CONTEXT=

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

Create a Configuration Manager Database On an Oracle RAC

1. Configuring an Oracle Schema during installation

   During the installation procedure, you specify the database parameters for connecting to the desired Oracle RAC instance (Host Name, Port, and SID). After the installation is complete, you must configure jdbc.url in the database.properties file, as described in Configuring the database.properties file below.

2. Configuring an Oracle Schema during upgrade

   During the upgrade procedure you enable Configuration Manager to connect directly to an Oracle RAC instance. For example:

   jdbc.url=jdbc:oracle:thin:@[instance_name]:1521:[instance_sid]

   After the upgrade is complete, you must configure jdbc.url in the database.properties file, as described in Configuring the database.properties file below.

3. Configuring the database.properties file

   Change jdbc.url in the database.properties file in one of these ways:

   • by Single Client Access Name (SCAN)

     jdbc:mercury:oracle://<server_name>:1521;ServiceName=<service_name>

     where <server_name> is the scan listener hostname or address and <service_name> is the name of the Oracle RAC service.

   • by the tnsnames.ora file

     jdbc.url=jdbc:mercury:oracle:TNSNamesFile=<CM_HOME>\\conf\\tnsnames.ora;TNSServerName=<service_name>

     where <CM_HOME> is the Configuration Manager installation directory, and <service_name> is the name of the Oracle RAC service.

     You must create the tnsnames.ora file in the \conf subfolder of the Configuration Manager installation directory. Here is an example of the contents:

     RACQA = 
      (DESCRIPTION =
         (ADDRESS = (PROTOCOL = TCP)(HOST = labm3amdb17-vip)(PORT = 1521))
         (ADDRESS = (PROTOCOL = TCP)(HOST = labm3amdb18-vip)(PORT = 1521))
         (LOAD_BALANCE = yes)
         (CONNECT_DATA =
           (SERVER = DEDICATED)
           (SERVICE_NAME = RACQA)
             (failover_mode=(type=select)(method=basic))
         )
       )
     

     In this case, set jdbc.url to jdbc:mercury:oracle:TNSNamesFile=<CM_HOME>\\conf\\tnsnames.ora and the TNSServerName to RACQA.

     Note: For details about configuring the Oracle JDBC URL format, see http://www.datadirect.com/resources/jdbc/oracle-rac/connecting.html.

Configure Windows Authentication (NTLM) On an MS-SQL Server

You can create and connect to a database using Windows authentication instead of Microsoft SQL Server authentication. To do so, you must ensure that the Windows user running the Universal CMDB Configuration Manager service has the necessary permissions to access the Microsoft SQL Server database.

• For information on assigning a Windows user to run the Universal CMDB Configuration Manager service, see the section about changing the UCMDB Server Services user, in the Hardening section of the UCMDB Help.
• For information on adding a Windows user to Microsoft SQL Server, see the section describing using Windows authentication to access Microsoft SQL Server databases in the Hardening section of the UCMDB Help.

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:

1. In the <Configuration_Manager_installation_directory>/_installation folder, run HPECM_10.23.xx.exe (on Windows systems) or HPECM_10.23.xx.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 (FQDN)	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 FQDN.
     Protocol	HTTP or HTTPS (default) protocol.
     UCMDB Port	The HTTP or HTTPS port default values are 8080 for HTTP and 8443 (default) for HTTPS.
     Server Certificate	This field is available 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. Note: Note: The path to the certificate file cannot contain spaces. 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).
     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 provide an incorrect value, the deployment will fail.
     UCMDB root context	UCMDB root context, the default value is /. If this value is changed in UCMDB, this needs to be adjusted in CM as well. This way UCMDB-CM communication uses UCMDB root context.
     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.

   • Database configuration information

     Configuration Manager uses a different database schema from UCMDB.

     Two types of databases are available – Oracle and MSSQL. 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 Support Matrix section of the UCMDB Help.

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

You can specify different root contexts on a single Configuration Manager server installation.

To change the root context for Configuration Manager:

1. Stop the Configuration Manager service.

2. Open the <Configuration Manager installation directory>/servers/server-0/webapps/ folder.

   1. Rename the cnc.war file with the desired root context.

      Repeat this step for all .war files in the folder, except for the ds-console.war file.

   2. Delete the /cnc subfolder.

      Repeat this step for the corresponding subfolder of each .war file in the /webapps folder, except for the /ds-console folder.

   Caution: Do not change the name of the ds-console.war file and its corresponding subfolder.

3. Open the <Configuration Manager installation directory>/servers/server-0/webapps/root/ folder.

   In the index.html file, change

   <meta http-equiv='refresh' content='0;url=http://quixy.deu.hp.com/cnc' />

   to

   <meta http-equiv='refresh' content='0;url=http://quixy.deu.hp.com/<context>/cnc' />

4. Restart the Configuration Manager service.

5. Verify that a folder with the new context name (for example, segment#cnc) has been created in the /webapps folder.

To start the Configuration Manager server:

• On a Linux system, use a command line prompt:

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

  • 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 Windows system:

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

To stop the Configuration Manager server:

• On a Linux system, use a command line prompt:

  $ cd /<Configuration_Manager_installation_directory>
  $ ./stop-server-0.sh

• On a Windows system:

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

To uninstall Configuration Manager, do one of the following:

This section includes:

• View the Status of Universal CMDB Server Services
• Check the Universal CMDB Integration Service Status
• Universal CMDB Services

View the Status of Universal CMDB Server Services

On the UCMDB Server machine, open your client browser and enter https://localhost:8443/status. The Status and Detailed Status of all services are displayed, indicating whether the Universal CMDB services are running (Up) or are down (Not Started).

Check the Universal CMDB Integration Service Status

If your remote managed data repositories are accessible from the UCMDB server machine, you can use the UCMDB Integration Service for non-Jython-based integrations instead of a Data Flow Probe.

To ensure that the service is running:

1. Check the status on the UCMDB Server machine:

   Windows	Control Panel > Administration Tools > Services
   Linux	/opt/hp/UCMDB/UCMDBServer/integrations/bin/service.sh status

2. If the service is not running:

   1. Check if there is a Data Flow Probe installed and running on the UCMDB Server machine. If so, you must first stop the Data Flow Probe before you can start the UCMDB Integration Service.

      To stop the Data Flow Probe:

      Windows	Select Start > All Programs > UCMDB > Stop Data Flow Probe
      Linux	Enter the following command: /opt/hp/UCMDB/DataFlowProbe/bin/probegateway.sh stop

   2. Start the UCMDB Integration Service:

      Windows	Use one of the following: Select Start > All Programs > UCMDB > Start Universal CMDB Integration Service Select Start > Control Panel > Administration Tools > Services, and start the UCMDB Integration Service
      Linux	Enter the following command: /opt/hp/UCMDB/UCMDBServer/integrations/bin/service.sh start

Universal CMDB Services

The Universal CMDB services are described in the following table:

This section includes:

• Overview
• Accessing the UCMDB Components
• Enabling Automatic Login

• Launch UCMDB UI from Chrome 43+, Firefox 48+, Microsoft Edge, or Safari 10+

• Change Default Time Limit for User Inactivity Log Out

Overview

You access Universal CMDB using a supported Web browser, from any computer with a network connection (intranet or Internet) to the Universal CMDB Server.

For details about Web browser requirements, as well as minimum requirements to successfully view Universal CMDB, see the Support Matrix section of the CMS Help.

The level of access granted a user depends on the user’s permissions. For details on granting user permissions, see the Administer section of the UCMDB Help.

For details on accessing Universal CMDB securely and login authentication strategies, see the Hardening section of the UCMDB Help.

Accessing the UCMDB Components

1. In the Web browser, enter the URL of the Universal CMDB Server, for example:

   https://<server name or IP address>.<domain name>:8443

   where <server name or IP address>.<domain name> represents the fully qualified domain name (FQDN) of the Universal CMDB Server.

   If Universal CMDB is set up to work through a reverse proxy, enter https://<proxy_server_name>:443 where proxy_server_name is the name or IP address of the proxy server.

   If the correct Java version is not installed on your machine, you can choose to download the version from sun.com or from the UCMDB server. (If you log in without installing Java, you will not be able to view pages that need a Java applet to display correctly.)

2. Click a link to work with Universal CMDB:

   • UCMDB. Opens the login page. After logging in, the module you had open at the end of your last session opens. If your user preferences are deleted, the IT Universe Manager is opened by default.

     Note: You can also access the login page by entering https://<server name or IP address>.<domain name>:8443/ucmdb.

   • User Management. Opens the login page. After logging in, you are taken directly to the Users and Groups module where you can manage your UCMDB users.

   • UCMDB Configuration Manager. Opens the Configuration Manager application. For the link to be active, Configuration Manager must be running and the infrastructure setting Configuration Manager URL must contain the application’s URL.

   • UCMDB Browser. Opens the UCMDB Browser. The UCMDB Browser is a web-based tool for displaying UCMDB information quickly and easily. For the link to be active, UCMDB Browser must be running and the infrastructure setting UCMDB Browser URL must contain the application’s url.

   • UCMDB Class Model. Opens the UCMDB Class Model Reference, which contains information on all packages, CI types, and relationships in the class model.

   • Server Status. Opens the Server Status page.

   • JMX Console. Enables you to perform operations on the CMDB through the JMX console interface.

   • API Connection Test. Displays information about the Universal CMDB Server for you to use when running an API to the CMDB.

   • API Client Download. Downloads the UCMDB API jar file.

   • API Reference. Opens the UCMDB API Reference documentation.

   1. When you click UCMDB or User Management, the login page opens.

      Enter the default superuser login parameters:

      • User Login = admin, User Password = the password for admin.

      • If Universal CMDB is installed in a multiple customer or multiple state environment (for example, Universal CMDB Configuration Manager), a Customer field is displayed. Choose the Customer name from the list.

      • Remember me on this machine. Select for automatic login. That is, the next time you log in to UCMDB, you do not need to enter your user name and password.

3. Click Login. After logging in, your user name appears at the top right of the screen.

   If you have problems logging in, see Troubleshooting Deployment - Logging In to UCMDB below.

   Note: Click the Help button on the Login page for complete help with logging in.

4. (Recommended) Change the superuser password immediately to prevent unauthorized entry. For details, see the Administer section of the CMS Help.

5. (Recommended) Create additional administrative users to enable Universal CMDB administrators to access the system. For details, see the Administer section of the CMS Help.

Enabling Automatic Login

Advanced login options enables you to automate login, limit login access, and provide direct login capabilities to specific pages in Universal CMDB.

When automatic login is enabled from the login page, and when you close the browser tab without using the Logout button at the top of the Universal CMDB page, the next time you enter this URL to access Universal CMDB (https://<server name or IP address>.<domain name>:8443/ucmdb-ui) or access the URL of the Universal CMDB Server (https://<server name or IP address>.<domain name>:8443) to get to the splash screen and then click UCMDB, the login page does not open, the login name and password do not have to be entered, and the default page that is set to open opens automatically.

To enable automatic login:

1. In the Universal CMDB login page, select the option Remember me on this machine.

2. When completing your session, do not click Logout at the top of the page, but close the browser tab.

   When you open a new browser tab and navigate to link https://<server name or IP address>.<domain name>:8443 and then click UCMDB, the login page should be skipped.

Guidelines for Using Automatic Login

Using the Logout option at the top of the Universal CMDB page, the Remember me on this machine option is still enabled with your user name remembered. If you log out using the Logout button, the next time you try to log in, the Login page opens with your login name pre-filled, you only need to enter your password manually.

The Remember me on this machine option can only be manually canceled by the user when he/she logs in next time.

Launch UCMDB UI from Chrome 43+, Firefox 48+, Microsoft Edge, or Safari 10+

You can launch UCMDB UI application from web browsers without support for NPAPI plugins, including Chrome 43+, Firefox 48~51, Microsoft Edge, and Safari 10+.

The JNLP feature allows users who use web browsers without support for NPAPI plugins to launch the UCMDB UI application. Instead of running it in the internet web through the Java plug-in, a JNLP file is saved on the client machine. After launching the JNLP file, it runs in a separate Java process and loads the UCMDB UI as a desktop application.

The following web browsers are supported for accessing UCMDB UI using JNLP:

• Chrome version 43 or later
• Firefox versions 48 to 51
• Microsoft Edge
• Safari version 10 or later

The following scenarios are not supported:

• Login through LW-SSO
• CAC login
• FIPS mode

How to launch UCMDB UI from web browsers without support for NPAPI plugins

To do so, perform the following:

1. Prerequisites

   • Oracle JRE is installed on the client machine (the latest version recommended)

   • Make sure you have enabled JNLP from JMX console

     Otherwise follow the instructions below to enable JNLP:

     1. Access the UCMDB server JMX console: Launch a Web browser and enter the following address: https://<UCMDB machine name or IP address>:8443/jmx-console. You may have to log in with a user name and password. (default username: sysadmin)

     2. Locate the UCMDB:service=Settings Services > setGlobalSettingValue operation.

     3. To enable JNLP, provide values for the following parameters for the setGlobalSettingValue method:

        • name: mam.web.is.jnlp.enabled

        • value: true

          The default value of the mam.web.is.jnlp.enabled setting is false.

     4. Click Invoke. The setting takes effect immediately.
2. Import the certificate to your client

   Note: This is needed only when you do not have a certificate provided by a Certificate Authority.

   1. Export a certificate (for example, ucmdb.cer) and save it to your machine.

      Taking Windows and Chrome as an example,

      1. In the client web browser, enter https://<UCMDB machine name or IP address>:8443/.

      2. Click the lock icon in the address bar.

      3. Click the Details link right under the site address.

         The Details pane opens to the Overview tab page in the right side

      4. Click View Certificate.

      5. In the Certificate dialog box, go to the Details tab, find the certificate which CN = HP Universal CMDB, and click Copy to File.

         The Certificate Export Wizard opens.

      6. Click Next.
      7. On the Export File Format page, select DER encoded binary X.509 (.CER). and click Next.
      8. On the File to Export page, enter a file name (for example, ucmdb) and click Next.
      9. Click Finish.

   2. Import the certificate by executing the following command:

      keytool -importcert -alias ucmdb -file <filepath>\ucmdb.cer -keystore <JRE_HOME>\lib\security\cacerts 

      For example,

      keytool -importcert -alias ucmdb -file C:\Users\Administrator\Desktop\ucmdb.cer -keystore “C:\Program Files (x86)\Java\jre1.8.0_101\lib\security\cacerts”

   3. You may need to enter the default password changeit, and enter yes when prompted "Trust this certificate?".

   4. (Optional) Restart the UCMDB Server.
3. Launch UCMDB UI as a desktop application

   1. In the Web browser, enter the URL of the Universal CMDB Server, for example:

      https://<server name or IP address>.<domain name>:8443

      where <server name or IP address>.<domain name> represents the fully qualified domain name (FQDN) of the Universal CMDB Server.

      For details about the options available on the UCMDB splash screen, see Accessing the UCMDB Components.

      Tip: In case you see a message like "Your connection is not secure", go to the Advanced settings and add a security exception. For example, on Firefox, click Advanced > Add Exception, and then in the Add Security Exception dialog box that pops up, click Confirm Security Exception.

   2. Click UCMDB or User Management.

   3. Click Run as Java Web Start app.

      • On Chrome, a UCMDB.jnlp file is downloaded to your local machine automatically. Double-click the downloaded UCMDB.jnlp file to launch it.

      • On Firefox, the Opening UCMDB.jnlp dialog box pops up.

        • Select Open with Java(TM) Web Start Launcher (default) and click OK if you want to launch UCMDB UI directly.
        • Select Save File and click OK if you would like to save the file and launch UCMDB UI later. Double-click the downloaded UCMDB.jnlp file to launch it.

   4. In the Do you want to run this application? dialog box, click Run.

      The UCMDB.jnlp file runs in a separate Java process and loads the UCMDB UI as a desktop application.

   5. In the Universal CMDB dialog box that pops up, enter your UCMDB server login parameters.

   6. Click Login.

      Universal CMDB launches as a desktop application.

      To exit Universal CMDB, click the Close button at the top right corner of the application window.

4. (Optional) Configure the JNLP memory size

   If necessary, you may want to increase the JNLP memory size.

   1. On the UCMDB server machine, open the <UCMDB_Server_Home>/deploy/ucmdb-ui/jnlp-generate.jsp file using a text editor.

   2. Locate the following line:

      <j2se version="1.5+" initial-heap-size="512M" max-heap-size="1024M"/>

   3. Modify the value of the initial-heap-size or max-heap-size setting to meet your needs, and save the file.
   4. Delete the UCMDB.jnlp file you downloaded in step 3.c, and re-download the UCMDB.jnlp file by refreshing the web page and clicking the Run as Java Web Start app button from the web browser.

   Note: For more details about the JNLP configuration, see JNLP File Syntax.

Change Default Time Limit for User Inactivity Log Out

Universal CMDB includes an automatic logout feature which logs out when the system is inactive for a set time period. The default period is 1440 minutes (24 hours). After that time, a message appears with a 30-second countdown until logout.

This task describes how to adjust the time limit UCMDB stays open without any user input before automatically logging out.

To change the default logout time:

1. Select Administration > Infrastructure Settings > General Settings category > Inactive allowed time setting.

2. In the Value column, enter a new time interval in minutes. All values for inactive allowed time are located in the Properties window (right-click Inactive Allowed Time > Properties or double-click the Inactive Allowed Time setting).

This section includes:

• Installation and Deployment Issues
• Database Environment Issues
• Multi-Lingual User (MLU) Interface Support

Installation and Deployment Issues

• If you use the Japanese, Chinese, or Korean language in your browser, you must ensure that the Universal CMDB server has East Asian languages installed. On the machine on which the Universal CMDB server is installed, you must select Control Panel > Regional and Language Options > Languages > Install files for East Asian languages.

• Universal CMDB in an I18N environment is supported for Universal CMDB installed on a Windows or Linux platform.

• The installation path for all Universal CMDB components must not contain non-English language characters.

• The Upgrade Wizard for version 10.33 does not support the non-English user interface. (The upgrade itself works properly.)

Database Environment Issues

• To work in a non-English language Universal CMDB environment, you can use either an Oracle Server database, Microsoft SQL Server database, or PostgreSQL Server database. The OS Windows regional settings language of the database should be the same as that of the UCMDB Server. When using an Oracle Server database, the encoding of the database can also be UTF-8 or AL32UTF-8, which supports both non-English languages as well as multiple languages.

• When you create a new Oracle instance in an Oracle database, you must specify the character set for the instance. All character data, including data in the data dictionary, is stored in the instance’s character set. For details, see the section describing the Oracle Summary Checklist in the Database section of the UCMDB Help.

• The Database Query Monitor can connect to an Oracle database, but the Oracle user names and passwords must contain only English characters.

Multi-Lingual User (MLU) Interface Support

Use the language preference option in your browser to select how to view Universal CMDB. The language preference chosen affects only your local machine (the client machine) and not the Universal CMDB Server machine or any other user accessing the same Universal CMDB machine.

The Universal CMDB user interface can be viewed in the following languages in your Web browser:

To set up and view Universal CMDB in a specific language:

1. Install the appropriate language’s fonts on your local machine if they are not yet installed. If you choose a language in your Web browser whose fonts have not been installed, Universal CMDB displays the characters as squares.

2. If you are logged in to Universal CMDB, you must log out. Click LOGOUT at the top of the Universal CMDB window.

   Close every open browser window or, alternatively, clear the cache.

3. If Universal CMDB is running on Internet Explorer, configure the Web browser on your local machine to select the language in which you want to view Universal CMDB (Tools > Internet Options).

   1. Click the Languages button and in the Language Preference dialog box, highlight the language in which you want to view Universal CMDB.

   2. If the language you want is not listed in the dialog box, click Add to display the list of languages. Select the language you want to add and click OK.

   3. Click Move Up to move the selected language to the first row.

   4. Click OK to save the settings.

   5. Display the Universal CMDB login window.

   6. From the Internet Explorer menu, select View > Refresh. Universal CMDB immediately refreshes and the user interface is displayed in the selected language.

To enable a localized UCMDB online help:

1. Download the localized online help from the Software Support Downloads site.
2. Extract the package, and replace the files under the <UCMDB_Server>\deploy\ucmdb-docs\docs\eng\doc_lib folder with the localized version.
3. Clear your web browser cache.
4. Restart the UCMDB server.

1. Configure UCMDB mail server

   1. In UCMDB, go to Administration > Infrastructure Settings > Mail Settings.

   2. Configure mail settings as described in the table below:

      Mail Setting	Description
      Activate TLS/SSL connection	If SMTP server requires secure connection via TLS/SSL then the value should be True, and make sure you proceed to 2. Configure UCMDB client to configure communication protocol. Else if SMTP server accepts non-secure connection, the value should be changed to False.
      SMTP server	Enter the address of the SMTP server.
      SMTP server port	Edit the SMTP server port. The default value is 25.
      The username of SMTP server	Enter the user name of the primary SMTP server. If no authentication is required, leave this filed empty.
      The password of SMTP server	Enter the password of the primary SMTP server. If no authentication is required, leave this filed empty.
      Email sender	Enter the name to appear in reports that Universal CMDB sends.
      Sender editability	Setting this value to True enables users to change the Email sender name inside the form that sends mail. Otherwise, leave its value as False.

   3. As a backup for the main SMTP server, you can provide information about an alternative server. Configure the following settings:

      Mail Setting	Description
      Alternate SMTP server	Enter the address of the alternate SMTP server.
      Alternate SMTP server port	Enter the alternate SMTP server port.
      Alternate SMTP server username	Enter the user name of the alternate SMTP server. If no authentication is required, leave this filed empty.
      Alternate SMTP server password	Enter the password of the alternate SMTP server. If no authentication is required, leave this filed empty.

   Note: It is strongly recommended to set both the SMTP server and Alternate SMTP server. In case the SMTP server is not available, the alternative SMTP server will be used by the UCMDB server when sending emails.
2. Configure UCMDB client

   Note: This step is required only when Activate TLS/SSL connection is set to True.

   After configuring the mail server with a certificate, to benefit from secure communication and secure authentication option, you must transfer the certificate to UCMDB server truststores.

   1. Retrieve UCMDB JRE path.

      Example:C:\hp\UCMDB\UCMDBServer\bin\jre

   2. Retrieve your certificate path.

      Example: C:\Users\Administrator.SMTP\Desktop\certs\Keypublic.pem (the file extension could be anything, not just pem)

   3. Retrieve UCMDB server truststore path.

      Examples: 

      C:\hp\UCMDB\UCMDBServer\conf\security\server.truststore, or

      C:\hp\UCMDB\UCMDBServer\conf\security\server-fips.truststore (for FIPS mode)

   4. Retrieve UCMDB JRE truststore path.

      Example: C:\hp\UCMDB\UCMDBServer\bin\jre\lib\security\cacerts

   5. Navigate to the C:\hp\UCMDB\UCMDBServer\bin\jre\bin folder, and open the command prompt.

   6. Run the following commands using keytool to import the certificate to UCMDB server truststore and UCMDB JRE truststore:

      Note: Default truststore passwords are used in the following commands : changeit and hppass. If you configured a specific password for your truststore, just replace hppass or changeit with your password. Also, paths provided in the examples above are used. Make sure you replace them with your specific paths.

      Command for importing the certificate to UCMDB JRE truststore:

      keytool -import -file "C:\Users\Administrator.SMTP\Desktop\certs\Keypublic.pem" -keystore "C:\hp\UCMDB\UCMDBServer\bin\jre\lib\security\cacerts" -alias "give certificate a name" -storepass changeit

      Command for importing the certificate to UCMDB server truststore:

      • For non-FIPS mode:

        keytool -import -file "C:\Users\Administrator.SMTP\Desktop\certs\Keypublic.pem" -keystore "C:\hp\UCMDB\UCMDBServer\conf\security\server.truststore" -alias "give certificate a name" -storepass hppass

      • For FIPS mode:

        keytool -import -fle "C:\Users\Administrator.SMTP\Desktop\certs\Keypublic.pem" -keystore "C:\hp\UCMDB\UCMDBServer\conf\security\server-fips.truststore" -alias "give certificate a name" -storetype PKCS12 -providername JsageJCE -storepass hppass

This section includes:

• Large Capacity Planning Overview
• Configuring the UCMDB Server for Large Capacity
• Configuring the Oracle Database for Large Capacity
• Configuring the Microsoft SQL Database for Large Capacity
• System Capacity Test

Large Capacity Planning Overview

Using the default configuration, Universal CMDB can work with a deployment of more than 25 million CIs and relationships. To work with a larger deployment, you must implement the following configuration:

Depending in the number of CIs and relationships, increase the CMDB heap as follows:

• For capacity planning requirements, see the Support Matrix section of the UCMDB Help.
• For details about the changes you must make to the system configuration to support this capacity, see "Configuring the UCMDB Server for Large Capacity" in the Deployment Guide.
• For details on how to improve performance, see "Configuring the Oracle Database for Large Capacity" and "Configuring the Microsoft SQL Database for Large Capacity" in the Deployment Guide.
• For details about the setup used for capacity testing and performance results, see "System Capacity Test" in the Deployment Guide.

Configuring the UCMDB Server for Large Capacity

For the system to support the desired number of CIs and relationships, update the following parameters on the UCMDB Server:

Configuring the Oracle Database for Large Capacity

When working on a system containing more than 40 million objects and relationships, you can improve performance by increasing the Oracle SGA and PGA to the following suggested sizes:

This improves the performance of both the TQL calculation for several types of TQL queries, as well as for data-in operations performed on the system.

Configuring the Microsoft SQL Database for Large Capacity

When working on a system containing more than 40 million objects and relationships, you can improve performance by increasing the Microsoft SQL Server Memory to the following suggested sizes:

System Capacity Test

Setup

The system capacity test is conducted for Microsoft SQL Server (with 125 million CIs and relationships) and Oracle Database (with 200 million CIs and relationships) separately, by using the following hardware configurations.

The following business flows were tested as part of the system test:

• TQL Calculation

  TQLs were divided into sub groups according to the result size (<100, <1000, and <10000), according to the data set that the TQL retrieves, and according to the TQL configuration:

  • Like Condition
  • Like Ignore case
  • Different number of hierarchies in the TQL results (2-5)
  • Compound
  • Sub-graph

• Data-in

  The data-in scenario in the system test included insertion, updates, and deletion.

• Enrichments

  Enrichment scenarios included insert, update, and delete.

Results

Following the load test in the scenario that includes query execution (2 days), data-in (7 days for Oracle and 10 days for MS SQL), and enrichment execution, the following results were achieved:

• The system was stable throughout the run. No restarts, memory leaks, or any other degradation over time was observed.
• System performance was acceptable.

Logging In to Configuration Manager

You access Configuration Manager using a supported Web browser, from any computer with a network connection (intranet or Internet) to the Configuration Manager server. The level of access granted a user depends on the user's permissions. For details on granting user permissions, see the section on users and roles in the Administer section of the UCMDB Help.

For details on Web browser requirements, as well as minimum requirements for successfully viewing Configuration Manager, see the Support Matrix section of the UCMDB Help.

For details about accessing Configuration Manager securely, see the Hardening section.

For troubleshooting information about accessing Configuration Manager, see Troubleshooting Deployment - Logging In to Configuration Manager.

1. In the Web browser, enter the URL of the Configuration Manager Server, for example, http://<server name>.<domain name>:<port>/cnc, where <server name>.<domain name> represents the fully qualified domain name (FQDN) of the Configuration Manager server and <port> represents the port selected during installation.

2. Click Log In. After logging in, the user name appears at the top right of the screen.

Logging Out

When you have completed your session, it is recommended that you log out of the website to prevent unauthorized entry.

To log out, click Logout at the top of the page.

Accessing the JMX Console for Configuration Manager

For troubleshooting purposes or to modify certain configurations, you may need to access the JMX console.

To access the JMX console:

1. Make sure that Server Administrator privileges have been assigned in UCMDB. For details, see the Administer section of the UCMDB Help.

2. Open the JMX console at http://<server name>:<application_port>/cnc/jmx-console. The port is the port configured during the installation of Configuration Manager.

Port a Configuration Manager Installation Between Machines

This procedure should be used when you want to transfer an installation of Configuration Manager from one machine to another while keeping the database schema intact and connecting to the same UCMDB server.

1. Perform a new installation of Configuration Manager on the target machine.
2. Stop the Configuration Manager servers on both the source and target machines.

3. Copy the \conf and \security folders from the source machine into the relevant location on the target machine.

4. Start the Configuration Manager server on the target machine.

Change Port Numbers After Installation

To change port numbers (or any other installation parameter), see Reconfiguring Configuration Manager.

Copy System Settings Between Systems

1. On the source machine, open Configuration Manager. Go to Administration > Settings and click the Export configuration set to a zip file button.

   Before exporting, you can exclude specific parts of the configuration by unchecking the check box next to the relevant configuration items.

2. Copy the exported configuration to the target machine.

3. On the target machine, open Configuration Manager. Go to Administration > Settings and click the Import configuration set button.

Back Up and Restore

You can back up an installation of Configuration Manager in order to be able to recover from any type of failure that would otherwise require a complete new installation.

• Back up

  Back up the following information:

  • the \conf and \security subfolders in the Configuration Manager installation directory. This can be done while the system is up and running, without interrupting operation.

  • the database schema

  • the registry entry at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\HP Universal CMDB Configuration Manager 10.01 (on Windows systems only)

• Restore

  This procedure should be performed on a new system with that has no Configuration Manager installation on it.

  1. Install Configuration Manager on the target machine by running the HPCM_10.01.exe file (on Windows systems) or HPCM_10.01.bin file (on Linux systems).

  2. Stop the Configuration Manager server.

  3. Restore the \conf and \security directories. Use the matching method to restore that you used to back up. Overwrite the directories created by the installation that you performed in step 1.

  4. Restore the database schema. If you restore to a different database server, you must modify the url property in the database.properties file (located in the \conf directory) to match the new database server name.

  5. Start the Configuration Manager server.

• Installation troubleshooting. Use to troubleshoot common problems that you may encounter when installing Universal CMDB, and the solutions to those problems. See Troubleshooting Deployment - UCMDB Server and Troubleshooting Deployment - Keystore and Truststore below.
• Login troubleshooting. Use to troubleshoot possible causes of failure to log in to Universal CMDB.

• Micro Focus Software Self-solve knowledge base. Use to search for specific troubleshooting information on a wide variety of topics. Located on the Micro Focus Software Support site, the Micro Focus Software Self-solve knowledge base can be accessed by selecting Troubleshooting & Knowledge Base from the Universal CMDB Help menu.

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

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

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 Hardening section of the UCMDB Help.
5. In the Dependencies tab, ensure that the service is configured to have no dependencies (<No Dependencies>).

This section includes the following:

• Possible Causes for Failure to Log In to UCMDB
• Java Not Installed on Client Machine

Possible Causes for Failure to Log In to UCMDB

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

Java Not Installed on Client Machine

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

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

Problem. The upgrade to version 10.23 fails.

Solution: To restore to the previous version, perform the following steps:

• Uninstall Configuration Manager version 10.23.
• Restore the installation folder for the previous version of Configuration Manager (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).

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 Hardening section of the UCMDB Help.

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 the <Configuration_Manager_installation_directory>\conf\database.properties file.

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:

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

2. Change the following settings:

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

Limitations

• The time settings on the UCMDB and Configuration Manager servers must be synchronized, down to the seconds.

• The time zone and time format on the UCMDB and Service Manager servers must be synchronized.

• You will not see a new CI type that you created in UCMDB until you log out of Configuration Manager and then log on again.

• Whenever the time is changed on the Configuration Manager Tomcat server, the server must be restarted to update the time on the server.

Troubleshooting

Problem. When you start the Configuration Manager service, you receive the following error message:

Windows could not start the Universal CMDB Configuration Manager on Local Computer. For more information, review the System Manager Event log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 0.

Solution. Do the following:

1. Go to the <Configuration_Manager_installation_directory>\cnc\bin folder and execute the following command:

edit-server-0.bat

2. Select the Startup tab. In the Mode drop-down list (at the bottom), select jvm instead of exe.

3. Click OK.

4. Run your service.

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 Hardening section of the UCMDB Help.

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