Operations Bridge Manager

For Windows® and Linux operating systems

Software Version: 2019.05

Customized output from:

Operations Bridge Manager 2019.05 Installation and Upgrade Guide

Document Release Date: September 2019

Software Release Date: May 2019

HPE logo

Legal Notices

Warranty

The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Except as specifically indicated otherwise, a valid license from Micro Focus is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice

© Copyright 2015 - 2018 Micro Focus or one of its affiliates

Trademark Notices

Java is a registered trademark of Oracle and/or its affiliates.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft®, Windows®, Lync®, Windows NT®, Windows® XP, and Windows Vista® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

This product includes an interface of the 'zlib' general purpose compression library, which is Copyright © 1995-2002 Jean-loup Gailly and Mark Adler.

 
Distributed
Database Server OMi Servers User Interface Data Providers BSM Connector Integrations Load Balancer Gateway Servers Data Processing Servers Mail Server

About this guide

Welcome to the Operations Bridge Manager 2019.05 Installation and Upgrade Guide. This guide enables you to first specify the type of installation or upgrade that you plan to perform, and then view or print customized content, which includes only the requirements and tasks that apply to you.

You can only select certain combinations of options. Therefore, as you make your selections, you may notice that some options disappear or become unavailable.

OBM deployment

OBM is a universal event-correlation software that uses IT topology to automatically correlate related events for quicker and easier root-cause identification—essential in today's complex virtualized and cloud environments—and for heightened efficiency of ITIL event and incident management.

OBM is part of the Operations Bridge solution. It provides a way for IT administrators to pull together events from different monitoring tools. The monitoring tools can be Micro Focus applications, such as Operations Manager, Operations Agent, ArcSight Logger, and SiteScope, or third-party tools such as IBM Tivoli Enterprise Console (TEC), Microsoft System Center Operations Manager (SCOM), or Nagios. OBM, with its Operations Connectors, can pull that monitoring data together, reduce duplicate event reporting, and prioritize the events by business criticality.

Deploying OBM in an enterprise network environment is a process that requires system architecture design, resource planning, and a well-planned deployment strategy. Micro Focus Software Professional Services offers consulting services to assist customers with OBM strategy, planning, and deployment. For information, contact a Micro Focus representative.

Choose the setup type

Enterprise setup
Express setup

To set up OBM in an enterprise environment, you typically install the OBM software on one or more systems, depending on whether you choose a single-server deployment (all OBM components and servers on the same system) or a distributed deployment (OBM servers on multiple, dedicated systems). Afterward, you configure the application appropriately. In an enterprise environment, the OBM database server typically resides on a remote system. A load balancer distributes the communication to multiple OBM servers.

Express setup enables you to install and configure OBM by using default values with all its components and servers on the same system. OBM deployed with the express setup uses embedded Apache HTTP Server and an embedded PostgreSQL database, enables TLS with OBM-generated certificates, and installs the OBM Management Pack for Infrastructure. We recommend the express setup for environments where you want to demonstrate or evaluate OBM, or for small environments with less than 2,000 nodes.

Choose the installation type

Install and configure OBM 2019.05
Upgrade from OBM 2018.05 or OBM 2018.11
Upgrade from OMi 10.12 (latest IP) or 10.6x
Uninstall OBM 2019.05

To deploy OBM, you must first install the OBM software on one or more servers, depending on whether you choose a single-server or a distributed deployment, and then configure the application for your environment. The configuration includes, for example, communication, database, server, and login settings.

Note To install and configure OBM silently, select the option Silent deployment in the Select additional options section below.

You can upgrade from OMi 10.12 (latest IP) or 10.6x to OBM 2019.05. If you want to upgrade from a version prior to 10.12 (latest IP), you must first upgrade to OMi 10.12 (latest IP) or OMi 10.6x and then follow the steps to upgrade to OBM 2019.05.

Both in-place upgrade and side-by-side migration are supported. In-place upgrades begin with an uninstallation, as OBM 2019.05 replaces your earlier OBM version.

Note During the upgrade, depending on the exact scenario, certain customizations of your original product deployment may be lost. In such cases, you must reapply or adjust them after the upgrade. To retrieve applicable information and instructions, make relevant selections in the Select additional options section below.

You can completely uninstall OBM.

Choose the upgrade type

In-place upgrade
Side-by-side migration

In-place upgrade refers to installing OBM 2019.05 on the original OBM host systems and installing it in such a way that the original OBMdatabasesdatabase schemas continue to be used. This can only be performed after uninstalling the earlier OBM version and therefore results in greater downtime.

Side-by-side migration refers to installing OBM 2019.05 on different host systems and databasesdatabase schemas to allow the original OBM servers to continue functioning while the upgrade is in process. The original servers are referred to as the production environment. This minimizes downtime and allows you to ensure that the new servers are functioning as required before switching to them.

During side-by-side migration, OBM 2019.05 is installed on the staging servers. Side-by-side migration begins when both production and staging servers are installed. During the process, event data is forwarded from the earlier OBM version to OBM 2019.05.

Only changes to the database are transferred during side-by-side migration, configuration changes made to the production servers are not transferred.

Note Perform side-by-side migration if your source and target environments are not running the same operating systems.

Choose the upgrade type

In-place upgrade
Side-by-side migration

In-place upgrade refers to installing OBM 2019.05 on the original OBM host systems and installing it in such a way that the original OBMdatabasesdatabase schemas continue to be used. This can only be performed after uninstalling the earlier OBM version and therefore results in greater downtime.

Side-by-side migration refers to installing OBM 2019.05 on different host systems and databasesdatabase schemas to allow the original OBM servers to continue functioning while the upgrade is in process. The original servers are referred to as the production environment. This minimizes downtime and allows you to ensure that the new servers are functioning as required before switching to them.

During side-by-side migration, OBM 2019.05 is installed on the staging servers. Side-by-side migration begins when both production and staging servers are installed. During the process, event data is forwarded from the earlier OBM version to OBM 2019.05.

Only changes to the database are transferred during side-by-side migration, configuration changes made to the production servers are not transferred.

Note Perform side-by-side migration if your source and target environments are not running the same operating systems.

Choose the deployment type

Distributed deployment
Single-server deployment

Distributed deployment is a deployment where one instance of a gateway server is installed on one system and the data processing server is installed on another system. Distributed deployments can benefit from various high availability and load balancing options.

To set up a distributed deployment, specify the server type you want to install on each system while running the installation wizard. You can install these servers in parallel and in any order but you must configure a data processing server first.

Single-server deployment has the gateway server and data processing server installed on the same host system.

A single-server deployment can be used for many installation scenarios as long as the system has the required hardware to handle the load. For large loads, the single-server deployment might require a system with a very large RAM that will not be recommended or supported by your IT. Single-server deployment is more economic in terms of resources since many of the common components are deployed only once.

Choose the database management system

Microsoft SQL Server (remote DBMS)PostgreSQL (embedded DBMS)
Oracle Database (remote DBMS)
PostgreSQL (remote DBMS)
PostgreSQL (embedded DBMS)

Note The Operations Bridge Express Edition Suite does not entitle you to use Microsoft SQL Server or Oracle Database with OBM.

The process for upgrading from OBM 10.12 (latest IP) or 10.6xOBM 2018.05 or 2018.11 does not allow you to change the database management system. Select the option that matches your current OBM environment.

OBM requires a database to store information. You can use an embedded PostgreSQL database instance, or a database instance on a remote systemmust reuse the existing database instance.

If you decide to use a remote database instance, you can preconfigure it or OBM can configure it for you. For detailed information on deploying the database servers in your system for use with OBM, and creating the databasesdatabase schemas manually, see the OBM Database Guide.

If you decide to use an embedded PostgreSQL database instance, OBM installs and configures the instance for you on the same system that hosts the OBM data processing server. Deployments with an embedded PostgreSQL database instance are limited to only one data processing server.

Note As part of any type of upgrade, OBM supports migrating its databases to a later version of Microsoft SQL Server. However, database migration is not automated. Follow the applicable step of the upgrade instructions in this guide to migrate OBM databases at a proper time during the process.

Note As part of the OBM 10.12 (latest IP) or 10.6x upgrade process, OBM 2019.05 updates the embedded PostgreSQL database management system to the version 9.6.12.

Choose the operating system

Microsoft Windows
Linux

Choose the operating system that runs on the computers where you want to install OBM.

Select additional options

Load balancing
Change of Windows user account for OBM servicesUse of non-root Linux user account for OBM processes
Silent deployment
Collect debug information

Load balancing divides the work load among several computers. As a result, system performance and availability increases. In distributed deployments, OBM requires a load balancer if there are two or more gateway servers configured. For higher security, we recommend load balancing on the OSI model layer 2 or 4 to pass through TLS traffic to the gateway servers.

Note Load balancer-related customizations of your original OBM deployment may need adjustment after the upgrade. To retrieve applicable instructions, select the Load balancing option.

You can change the Windows user accounts that get associated with the OBM services by default.

You can change the Linux user accounts that get associated with the OBM processes by default.

With silent deployment, you perform both OBM installation and the subsequent configuration in a silent mode, without using the respective wizards: the required values are gathered directly from the previously prepared input files. For OBM configuration, the files are either based on the bundled configuration templates (that you edit in advance) or they are created by the configuration wizard itself (during a preparatory session that does not apply any changes).

View or print

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

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

Check your selections

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

 

If any selections are not correct, click Change.

Check the hardware requirements

  • Processor. 4 CPU cores minimum, 8 recommended. We recommend using 2.4 GHz CPU cores or faster.

    In a virtual environment, make sure the number of virtual CPUs is equivalent to the number of physical CPU cores used.

    Tip Because OBM performance is dependent upon processor speed, we recommend getting the fastest possible processor to ensure adequate performance.

  • Memory. The following table lists the physical memory requirements (in GB). The amount of total memory (physical memory and the paging or swap file) should be at least 8 GB bigger than the required minimum.

    Deployment Single Server Data Processing Server Gateway Server
    Small (up to 2,000 nodes) Minimum 12 10 5
    Recommended 14 11 7
    Medium (up to 5,000 nodes) Minimum 14 12 6
    Recommended 18 16 8
    Large (more than 5,000 nodes) Minimum 32 30 10
    Recommended 44 42 12

    In addition, some memory is required for temporary data. If you have problems with your disk space, consider removing all dump files in the following directories: C:\HPBSM\bin and C:\HPBSM\odb\bin/opt/HP/BSM/bin and /opt/HP/BSM/odb/bin

    Embedded PostgreSQL database management system. When deploying OBM with the embedded PostgreSQL database management system, the additional 1 GB of virtual memory is required on either the single server or the data processing server.

  • Free storage space. When installed, OBM requires the following amounts of free storage space (in GB):

    Default Directory Minimum Recommended
    /opt/HP/BSM 20 50
    /opt/OV 1 1
    /var 11111 22222
    /tmp 520 (during installation only)

    If there is not enough free storage space in the /tmp directory, you can change the default temporary directory that OBM uses during installation. To do so, run the following commands in the command shell in which you plan to start the installation wizard later:

    export IATEMPDIR=<DirectoryForTemporaryFiles1>

    export _JAVA_OPTIONS=-Djava.io.tmpdir=<DirectoryForTemporaryFiles2>

    In these instances, <DirectoryForTemporaryFiles1> and <DirectoryForTemporaryFiles2> are absolute paths of the directories with sufficient free storage space. Depending on your configuration, both paths may point to the same directory.

    Note Do not use /opt/HP/BSM as the mount point, but rather /opt/HP (as /opt/HP/BSM is deleted when uninstalling OBM).

    Do not change the location of your original installation directory (the one you used for your previous OBM version).

    Default Folder Minimum Recommended

    C:\HPBSM

    20 50

    C:\Program Files\HP\HP BTO Software

    C:\ProgramData\HP\BSM

    111 222
    %TEMP% * 520 (during installation only)

    * This is a user environment variable

    When using an embedded PostgreSQL database, an additional minimum of 10 GB (recommended are 20 GB) are required on C:\ProgramData\HP\BSM.

    Note Do not change the location of your original installation directory (the one you used for your previous OBM version).

  • Additional requirements:

    • Access control list (ACL) support is required on the file system where OBM and the embedded PostgreSQL database are installed.

    • Uploading Operations Agent deployment packages to the OBM server requires up to 20 GB of additional free storage space.

    • OBM server must not be installed on a drive that is actually a mapped network folder.

      When using Remote Desktop Protocol (RDP) and device redirection, make sure that you do not install OBM server on a local disk of the client system.

    • For the hardware requirements for remote database servers (database management systems), see the OBM Database Guide.

Check the software requirements

  • Basic requirements. The entire distribution (with original equipment manufacturer (OEM) support) and the latest recommended set of patches are required. You can install OBM on a system with minimal Linux installation and with minimal graphical user interface support.

  • Unzip. OBM requires the unzip package.

    You can install this package by running the following command:

    yum install unzip

  • Init scripts. OBM requires the initscripts package.

    You can install this package by running the following command:

    yum install initscripts

  • Perl. OBM requires the Perl package.

    You can install this package by running the following command:

    yum install perl

  • Asynchronous I/O (AIO) libraries. OBM requires the libaio package.

    You can install this package by running the following command:

    yum install libaio

  • PNG support libraries. OBM requires the libpng12 package.

    You can install this package by running the following command:

    yum install libpng12.x86_64

  • libXtst extension library. On all machines on which you want plan to install OBM, you must install the RPM package libXtst. Download the package from any RPM repository site that matches your system specifications (you can use, for example, the RPM search tool to find the correct package), and manually install the package by running the command yum install -y <libXtst package>

  • OpenSSL. To implement advanced hardening (for example, reverse proxy setup), OpenSSL 1.0.1 or later must be installed on the OBM host systems.

  • DISPLAY environment variable. The DISPLAY environment variable must be properly configured on the OBM host system unless you are deploying OBM by using the console or in the silent installation mode.

  • X Window System. The system from which you are invoking OBM installation must host an implementation of X Window System.

    Run the following command to install this package:

    yum groupinstall "X Window System"

  • Console mode or silent installation. You can install OBM without any graphical support using the console mode or the silent installation (-console or -silent), followed by the silent configuration (configuration in the console mode is not possible).

    The following tools are available to check the status of installation in GUI mode:

    • Operations Bridge Manager Status: /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh

      Alternatively, you can use the following utilities in console mode:

      • To print the Nanny status,use the /opt/HP/BSM/opr/support/opr-status.py utility .
      • To print the HAC status, use the /opt/HP/BSM/opr/support/opr-support-utils.sh utility.
    • OBM Database Browser: /opt/HP/BSM/tools/bsmbrowser/bsmbrowser.sh

  • X Window System emulators. We recommend that you do not use third-party X Window System implementations (emulators), for example Exceed, to install OBM. Installing by using an emulator may slow the pace of the installation and may adversely affect the appearance and functionality of the user interface.

  • Windows patch requirement. If you are using a Windows system Windows systems older than Windows Server 2016, you must install Windows Patch KB2999226.
  • TCP setting. We highly recommend that you increase the TCP time delay above its default setting.

    For the Windows registry key entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, create a new DWORD (32-bit) (REG_DWORD) value named TcpTimedWaitDelay, and enter 60 (decimal) for its value data.

    If this change is omitted, a long time delay (configured by default) might result in a problem with exhausting the available TCP resources.

    Caution We recommend that you back up Windows Registry before making any changes to it.

  • User Account Control (UAC). UAC must be disabled before installingupgrading to OBM 2019.05. For information on disabling UAC, see the Microsoft Windows documentation (for example, Microsoft TechNet).

    After the installation, you can reenable UAC.

  • Fully qualified domain names (FQDNs). Each OBM server must have a resolvable FQDN. To verify it, run the hostname and nslookup commands. If either command returns an FQDN, your domain name is supported.

    FQDNs of the server systems must consist only of the following characters: a-z, A-Z, 0-9, hyphen (-), and period (.)

  • Hostname resolution. OBM servers must be able to resolve names of the systems they communicate with. These include all OBM servers, database servers, and data collectors.

  • Application coexistence. OBM servers must be installed on dedicated host systems which must not run other applications.

    Installing OBM servers together with most other Micro Focus products on the same host system may result in port conflicts, performance issues, or other unexpected behavior. Coexistence of OBM servers with Operations Agent and Data Flow Probe (DFP) is supported. For details on the coexistence support, select Operations Bridge Manager from the product list in the following document:

    Support Matrices for Operations Center products

  • Ports. The installation checks whether the following ports are available: 80, 383, 443, 1098, 1099, 4447, 5445, 8009, 8080, and 29000.

    If the installation checks indicate that these ports are in use, the installation does not fail, but we recommend that you free the necessary ports before configuring OBM.

    For a complete list of ports used by OBM, see "Port Usage" in the OBM Administration Guide.

  • Reserved ports. The operating system reserves a range of ports for the use of applications that require outgoing connections to external systems.

    The installation checks if ports up to 30999 are available. We recommend to ensure that the dynamic port range reserved by the operating system starts at 31000 or above.

    1. Check the dynamic port range by running the following command:

      netsh int ipv4 show dynamicport tcp

      sysctl net.ipv4.ip_local_port_range

    2. If the reserved ports do not start at 31000 or above, run the following command to change this setting:

      netsh int ipv4 set dynamicport tcp start=31000 num=16384

      If the reserved ports do not start at 31000 or above, edit the file /etc/sysctl.conf, and add or modify the following setting: net.ipv4.ip_local_port_range=31000 65535

    3. Run the following command for the changes to take effect:

      sysctl -p

  • Time settings. Host systems of all OBM servers and the database management system must have the same settings for the following parameters:

    • Date and time

    • Time zone

    • Daylight saving time configuration

  • L-Core. OBM installs the L-Core packages. If an earlier version of these packages is already installed, the packages are automatically upgraded. Otherwise, the currently installed version is left intact.

    Note Upgrade of the L-Core packages is an irreversible change. You cannot revert to the earlier version of it later.

  • Web server:

    OBM deployment requires a web server. The OBM installation process therefore installs Apache HTTP Server on all gateway servers by default.

    Note There must be only one running web server on a system, and it must use the same port as OBM. For example, during the installation of OBM, if you are installing on a system where Microsoft IIS is already running, make sure to stop the IIS services and set their startup type to Manual before initiating the installation process.

    OBM deployment requires a web server. The OBM installation process therefore by default installs Apache HTTP Server on the OBM host system.

    Note There must be only one running web server on a system, and it must use the same port as OBM.

    OBM deployment requires a web server. The OBM installation process therefore by default installs Apache HTTP Server on all gateway serverson the OBM host system.

    Note There must be only one running web server on a system, and it must use the same port as OBM.

    OBM uses a customized version of Apache HTTP Server.

    By default, the Apache HTTP Server is enabled for TLS use. For additional information on configuring the web server to use TLS, see the Apache SSL/TLS Encryption web page.

    OBM runs its Apache HTTP Server that by default uses port 443. The installation wizard checks whether port 443 is available, and generates a warning if it is already in use. You can change the port in the Connection Settings page of the configuration wizard.

  • Access to the OBM installation files. The unpacked OBM 2019.05 installation files must be available on the BSMOBM host systems that will host new OBM version as well as on the BSM original OBM host systemson all systems that will host OBM.

    The installation package is named OBM_10.80_for_Windows.zipOBM_10.80_for_Linux.zip. Download the archive file to the system where you plan to install OBMwhich you plan to upgrade to OBM 2019.05, and extract all files from the archive.

  • X11 Libraries. If you are doing a silent upgrade, you must ensure that X11 libraries are installed before starting the upgrade.
  • Open files limit. Ensure that open files limit on Linux machines is set to 30000 or higher.

    To verify the current limit, run the following command:

    ulimit -n

    If the value is less than 30000, then modify the /etc/security/limits.conf file. Add or modify following lines:

    * hard nofile 30000

    * soft nofile 30000

    You can also check /etc/profile and the .profile of the OS user that is used to start the OBM processes. Make sure the limit is not overwritten by a "ulimit -n <other limit>" call.

Check the OBM client system requirements

  • Web browser configuration:

    • The browser must be set to accept third-party cookies and allow session cookies.

    • The browser must be set to enable JavaScript execution.

    • The browser must allow pop-ups from the OBM application.

    • Internet Explorer users must:

      • Configure the caching mechanism to automatically check for newer versions of stored web pages (Internet options > General > Browsing history > Settings > Temporary Internet Files > Check for newer versions of stored pages: Automatically).

      • Enable the use of TLS 1.0 or later (Internet Options > Advanced > Security)

      • Turn off Compatibility View (in Internet Explorer 11 only)

  • Java Runtime Environment (JRE) configuration. JRE must be configured to use TLS 1.0 or later (Java Control Panel > Advanced > Advanced Security Settings).

  • Flash Player: Make sure to install the latest version of Flash Player.
  • Fonts. The following fonts must be installed:

    • Arial
    • Meiryo (for Japanese locales)
    • Malgun Gothic or Arial (for Korean locales)
    • SimHei or SimSun (for Simplified Chinese locales)
  • Screen resolution. 1600x900 or higher (recommended); 1280x1024 (supported).

Check the network configuration requirements

  • Network segments. We recommend that all OBM servers, including the database server, are installed on hosts in the same network segment.

    If OBM servers are installed in multiple network segments, we highly recommend that the number of hops and the latency between the servers are minimal. Network-induced latency may cause adverse effects to the OBM application and can result in performance and stability issues. We recommend the network latency should remain below 5 milliseconds, regardless of the number of hops.

  • IPv6 and dual IP stack support. You can install OBM on host systems that have either the IPv4 or the IPv6 protocol stack or both of them configured.

    Where both IP protocol stacks are configured, OBM uses IPv4 by default.

    To enable OBM operation on a host system that has only the IPv6 protocol stack configured, or to configure OBM to use IPv6 on a host system that has both IP protocol stacks configured, you must modify an appropriate OBM configuration file after OBM is installed. For instructions on how to do that, see Enable OBM to use IPv6.

    Note On Linux systems, OBM does not function properly when the IPv6 protocol stack is not configured (that is, when only the IPv4 protocol stack is available) or when the IPv6 protocol stack is configured but disabled. Under such circumstances, to enable OBM to use IPv4, modify the /opt/HP/BSM/application-server/bin/standalone.conf configuration file as follows:

    1. Replace the

      -Djava.net.preferIPv4Stack=false

      line with the

      -Djava.net.preferIPv4Stack=true

      line.

    2. Save your changes and then restart local OBM processes.

  • Firewalls. Because OBM uses Java Remote Method Invocation (Java RMI) calls between servers, placing firewalls between OBM servers is not supported.

    If an operating system firewall is active on any OBM server (gateway or data processing server), a channel must be left open to allow all traffic between all OBM gateway or data processing servers.

    Additionally, to enable OBM users and data collectors to communicate with the OBM gateway servers, you must leave open the relevant ports depending on your OBM configuration. The required ports are typically 443 or 80, and 383. For details, see "Port Usage" in the OBM Administration Guide.

Check the database requirements

  • Instance location. With a local PostgreSQL database instance, OBM installs and configures the instance for you on the same system that hosts the OBM data processing server.
  • Instance location. OBM installs and configures the local PostgreSQL database instance for you on the same system that hosts the OBM data processing server.
  • Remote instance configuration. If you use a remote database instance, OBM can configure it for you or you can configure it directly in the database management system (for example, if your organization does not allow the usage of administrator credentials during setup).

    For detailed database requirements and instructions on creating database instances manually, see https://docs.microfocus.com/itom/Operations_Bridge_Manager:2019.05/AppSupportRealCluster.

  • Remote instance configuration. If you use a remote database instance, OBM can configure it for you or you can configure it directly in the database management system (for example, if your organization does not allow the usage of administrator credentials during setup).

    For detailed database requirements and instructions on creating database instances manually, see https://docs.microfocus.com/itom/Operations_Bridge_Manager:2019.05/PsqlOvwDep.

  • Remote instance configuration. If you use a remote database instance, OBM can configure it for you or you can configure it directly in the database management system (for example, if your organization does not allow the usage of administrator credentials during setup).

    For detailed database requirements and instructions on creating database instances manually, see https://docs.microfocus.com/itom/Operations_Bridge_Manager:2019.05/SqlSerDep.

  • Host operating system. OBM supports changing the operating system of your database server during the upgrade assuming that this is also supported by your database management system vendor.

  • Storage space requirement. The database replication requires 1.5 times the amount of storage space consumed by your original (production) database. During side-by-side migration, you will require double the amount of your original database storage space.

  • Oracle Database settings. Make sure Oracle Database is configured as follows:

    • The RECYCLEBIN parameter is set to Off.

    • The UTF8 character set is used for encoding characters.

    For more information, see the OBM Database Guide.

  • Collation. If you are performing a side-by-side migration, the collation must be identical in both the staging and the production environment.

  • Administrator's services. During the upgrade process, you might need your database administrator's services.

    For instructions on how to set up your OBM database server, see Prepare the database environment.

  • Host operating system.OBM supports changing the operating system of your database server during the upgrade assuming that this is also supported by your database management system vendor.

  • Storage space requirement. The database replication requires 1.5 times the amount of storage space consumed by your original (production) database. During side-by-side migration, you will require double the amount of your original database storage space.

  • Oracle Database settings. Make sure Oracle Database is configured as follows:

    • The RECYCLEBIN parameter is set to Off.

    • The UTF8 character set is used for encoding characters.

    For more information, see the OBM Database Guide.

  • Collation. If you are performing a side-by-side migration, the collation must be identical in both the staging and the production environment.

  • Administrator's services. During the upgrade process, you might need your database administrator's services.

    For instructions on how to set up your OBM database server, see Prepare the database environment.

Check the database requirements

  • Instance location. With a local PostgreSQL database instance, OBM installs and configures the instance for you on the same system that hosts the OBM data processing server.
  • Instance location. OBM installs and configures the local PostgreSQL database instance for you on the same system that hosts the OBM data processing server.
  • Remote instance configuration. If you use a remote database instance, OBM can configure it for you or you can configure it directly in the database management system (for example, if your organization does not allow the usage of administrator credentials during setup).

    For detailed database requirements and instructions on creating database instances manually, see https://docs.microfocus.com/itom/Operations_Bridge_Manager:2019.05/AppSupportRealCluster.

  • Remote instance configuration. If you use a remote database instance, OBM can configure it for you or you can configure it directly in the database management system (for example, if your organization does not allow the usage of administrator credentials during setup).

    For detailed database requirements and instructions on creating database instances manually, see https://docs.microfocus.com/itom/Operations_Bridge_Manager:2019.05/PsqlOvwDep.

  • Remote instance configuration. If you use a remote database instance, OBM can configure it for you or you can configure it directly in the database management system (for example, if your organization does not allow the usage of administrator credentials during setup).

    For detailed database requirements and instructions on creating database instances manually, see https://docs.microfocus.com/itom/Operations_Bridge_Manager:2019.05/SqlSerDep.

  • Host operating system. OBM supports changing the operating system of your database server during the upgrade assuming that this is also supported by your database management system vendor.

  • Storage space requirement. The database replication requires 1.5 times the amount of storage space consumed by your original (production) database. During side-by-side migration, you will require double the amount of your original database storage space.

  • Oracle Database settings. Make sure Oracle Database is configured as follows:

    • The RECYCLEBIN parameter is set to Off.

    • The UTF8 character set is used for encoding characters.

    For more information, see the OBM Database Guide.

  • Collation. If you are performing a side-by-side migration, the collation must be identical in both the staging and the production environment.

  • Administrator's services. During the upgrade process, you might need your database administrator's services.

    For instructions on how to set up your OBM database server, see Prepare the database environment.

  • Host operating system.OBM supports changing the operating system of your database server during the upgrade assuming that this is also supported by your database management system vendor.

  • Storage space requirement. The database replication requires 1.5 times the amount of storage space consumed by your original (production) database. During side-by-side migration, you will require double the amount of your original database storage space.

  • Oracle Database settings. Make sure Oracle Database is configured as follows:

    • The RECYCLEBIN parameter is set to Off.

    • The UTF8 character set is used for encoding characters.

    For more information, see the OBM Database Guide.

  • Collation. If you are performing a side-by-side migration, the collation must be identical in both the staging and the production environment.

  • Administrator's services. During the upgrade process, you might need your database administrator's services.

    For instructions on how to set up your OBM database server, see Prepare the database environment.

Check the installing user account requirements

  • System-wide privileges. You must use the root user account to install or upgrade OBM and to configure it. The root user account must be allowed to run the sudo command, which is used to initiate the embedded PostgreSQL database.

    To run OBM processes by using a user account other than root, start the configuration wizard as root, and then specify a different user account in the Configuration Options page.

  • System-wide privileges. The user account that is used for OBM installation or upgrade must have administrative privileges on the host systems.

  • Privileges in Oracle Database. The user account that is used for OBM installation or upgrade must be granted the following system privileges within the Oracle Database instance:

    • CONNECT

    • CREATE PROCEDURE

    • CREATE SEQUENCE

    • CREATE TABLE

    • CREATE TRIGGER

    • CREATE USER

    • CREATE VIEW

    • UNLIMITED TABLESPACE

    • SELECT ON sys.props$

    If the schema is being used for the RTSM database, then the following permission is also needed: CREATE TYPE TO <OBM Oracle User Schema for RTSM>

    The permissions and privileges are needed by OBM so that it can configure user schemas in the OBM databases.

    For more information, see "Chapter 9: Manually Creating the Oracle Schemas" in the OBM Database Guide.

Check the upgrade requirements and considerations

  • Upgrade plan. Based on your requirements, create an upgrade plan. The plan can include the decision about the upgrade type (whether you will perform side-by-side migration or in-place upgrade), the estimated downtime, and other aspects that influence your operation.

  • Information gathering. To speed up the upgrade process and ensure it is correct and complete, we strongly recommend that you have the following information prepared before initiating the upgrade:

    • Architecture of your existing environment. Knowledge of your original BSMOBM environment, including data collectors, components, and servers.

    • Original and new host systems. Location, credentials, and access to files on all original BSMOBM host systems and on the systems that will host OBM 2019.05.

    • Host systems. Location, credentials, and access to files on all BSMOBM host systems.

    • Support for your database management system. Check the OBM 2019.05 support for the database management system version used in the BSMoriginal OBM environment. For more information, see the following document:

      Support Matrices for Operations Center products

    • User management. Permissions for individual OBM users are granted through the role assignment. Such a design reduces the complexity of the authorization system and the related configuration effort. The upgrade process migrates users, user groups, and the user group membership configuration. Permission information itself is not migrated by the upgrade. For this reason, take note of the permission assignments in your BSM environment. Afterward, in OBM, create the required roles, grant permissions to them, and finally assign the roles to users or user groups.

    • RTSM or CMDB. Locations, credentials, and the configuration of RTSM or CMDB (for example, internal RTSM, external CMDB, or both).

    • Data collectors and integrated components. Access to all data collectors and components integrated with the original BSMOBM servers.

    • Microsoft SQL Server. Credentials for a member of the sysadmin group or a user account with select permissions for the syslogins system view.

    • Oracle Database. Credentials for a user account with the DBA or SELECT_CATALOG_ROLE role.

  • Upgrade sequence for distributed deployments. Pay special attention to follow the upgrade procedure in a proper sequence. The upgrade process involves all host systems of your existing BSMOBM deployment.

    You can install and configure additional OBM servers after the upgrade by using the OBM installation and configuration wizards.

  • Optional. Operating system switch. Side-by-side migration to OBM 2019.05 supports changing the operating systems on your gateway and data processing server hosts (for example, switching from Microsoft Windows to Linux).

  • Backup. Back up the following data from your original BSMOBM host systems:

    • <GatewayServerInstallationDirectory>/\JRE/\lib/\security/\cacerts (file)

    • <GatewayServerInstallationDirectory>/\odb/\conf/\security

    • <DataProcessingServerInstallationDirectory>/\BLE/\rules/\<CustomRulesJar> (file)

    • Files in the <HPEBSMrootDirectory><OBM_HOME>/\WebServer/\conf directory

    • <HPEBSMrootDirectory><OBM_HOME>/\conf/\jdbc.drivers.properties

    • <HPEBSMrootDirectory><OBM_HOME>/\conf/\omi-tnsnames.ora

    • <HPEBSMrootDirectory><OBM_HOME>/\odb/\conf/\jdbc.properties

    If you have named instances (for example RAC), save the file and the connection (which you specified in the jdbc.drivers.properties file and the RTSM).

    In addition, if Data Flow Probe (DFP) is integrated with BSMOBM, back up the certificates from the following directory:

    <DataFlowProbeInstallationDirectory>/\conf/\security

    For more information, see the Install the Data Flow Probe.

  • Recommended. Follow these steps to avoid data loss during the upgrade:

    1. Shut down the PostgreSQL database:

      <OBM_Home>\bin\opr-pgctl.bat –stop<OBM_Home>/bin/opr-pgctl.sh –stop

    2. Edit the postgresql.conf file at the following location:

      %ovinstalldir%\databases\omidb\postgresql.conf%ovinstalldir%/databases/omidb/postgresql.conf

      Set the max_locks_per_transaction parameter to 1000 and uncomment the line.

  • Recommended. DatabaseDatabase schema safety backup. For an increased safety of data, we recommend backing up the databasesdatabase schemas. To minimize the scope of the potential data loss, back them up as late before the BSMOBM uninstallation as possible.
  • Recommended. Database cleanup to speed up the upgrade.
    Follow these steps:
    1. Start the database:

      <OBM_Home>\bin\opr-pgctl.bat -start<OBM_Home>/bin/opr-pgctl.sh -start

    2. Run vacuumlo on event and rtsm schemas:

      <OBM_Home>\pgsql\bin\vacuumlo -h <host> -p <port> -U postgres <Schema_Name><OBM_Home>/pgsql/bin/vacuumlo -h <host> -p <port> -U postgres <Schema_Name>

      Where Schema_Name is the schema name of the event or rtsm database.

      Important Do not run vacuumlo on the mgmt database as it will create a database inconsistency.

    3. Run vacuumdb:

      <OBM_Home>\pgsql\bin\vacuumdb --all --full -h <host> -p <port> -U postgres<OBM_Home>/pgsql/bin/vacuumdb --all --full -h <host> -p <port> -U postgres

    4. Stop the database:

      <OBM_Home>\bin\opr-pgctl.bat -stop<OBM_Home>/bin/opr-pgctl.sh -stop

  • The OPEN_CURSORS parameter of Oracle Database. For the upgrade, set the Oracle Database parameter OPEN_CURSORS to 10,000. You must revert this parameter to the original value after the upgrade is complete.

  • Integrations. For details on product versions that are supported with OBM 2019.05, select Operations Bridge Manager from the product list in the following document:

    Support Matrices for Operations Center products

  • Optional. RTSM integrations disablement. If integrations are configured in RTSM Integration Studio (for example, between the central UCMDB and RTSM), Data Flow Probe will run population jobs immediately after the upgrade for active integration points, even if the integration process is not scheduled. If you do not want the integrations to run, disable them before starting the upgrade.

  • Uninstallation of Data Flow Probe. If Data Flow Probe (DFP) is installed on one of the BSMOBM gateway servers, uninstall it separately before starting the upgrade process.

  • Management packs. If you plan to install the latest OBM management packs after the upgrade, uninstall the following management packs first:

    • OBM Management Pack for Oracle Database 1.00

    • OBM Management Pack for Infrastructure 1.00

    Later versions of these management packs do not have to be uninstalled. For uninstallation information, see the management pack documentation.

  • Predefined indices. The database schema upgrade fails if indices of the former database model have been removed. You can make sure that your installation does not miss any predefined indices by running the checkIndices tool and recreating the missing indices: <OBM_HOME>/\opr/\support/\checkIndices.batsh

  • Empty backup folder. PostgreSQL configuration data is backed up into the folder %OvDataDir%\backup/var/opt/OV/backup
    Make sure that the folder does not contain backup files from previous upgrades or installations. We recommend to empty this folder completely before running the upgrade.

  • Back up and re-install symbolic links. You must back up symbolic links in your existing OBM host systems and re-install them manually before the new OBM version is installed.

Check the upgrade requirements and considerations

  • Upgrade plan. Based on your requirements, create an upgrade plan. The plan can include the decision about the upgrade type (whether you will perform side-by-side migration or in-place upgrade), the estimated downtime, and other aspects that influence your operation.

  • Information gathering. To speed up the upgrade process and ensure it is correct and complete, we strongly recommend that you have the following information prepared before initiating the upgrade:

    • Architecture of your existing environment. Knowledge of your original BSMOBM environment, including data collectors, components, and servers.

    • Original and new host systems. Location, credentials, and access to files on all original BSMOBM host systems and on the systems that will host OBM 2019.05.

    • Host systems. Location, credentials, and access to files on all BSMOBM host systems.

    • Support for your database management system. Check the OBM 2019.05 support for the database management system version used in the BSMoriginal OBM environment. For more information, see the following document:

      Support Matrices for Operations Center products

    • User management. Permissions for individual OBM users are granted through the role assignment. Such a design reduces the complexity of the authorization system and the related configuration effort. The upgrade process migrates users, user groups, and the user group membership configuration. Permission information itself is not migrated by the upgrade. For this reason, take note of the permission assignments in your BSM environment. Afterward, in OBM, create the required roles, grant permissions to them, and finally assign the roles to users or user groups.

    • RTSM or CMDB. Locations, credentials, and the configuration of RTSM or CMDB (for example, internal RTSM, external CMDB, or both).

    • Data collectors and integrated components. Access to all data collectors and components integrated with the original BSMOBM servers.

    • Microsoft SQL Server. Credentials for a member of the sysadmin group or a user account with select permissions for the syslogins system view.

    • Oracle Database. Credentials for a user account with the DBA or SELECT_CATALOG_ROLE role.

  • Upgrade sequence for distributed deployments. Pay special attention to follow the upgrade procedure in a proper sequence. The upgrade process involves all host systems of your existing BSMOBM deployment.

    You can install and configure additional OBM servers after the upgrade by using the OBM installation and configuration wizards.

  • Optional. Operating system switch. Side-by-side migration to OBM 2019.05 supports changing the operating systems on your gateway and data processing server hosts (for example, switching from Microsoft Windows to Linux).

  • Backup. Back up the following data from your original BSMOBM host systems:

    • <GatewayServerInstallationDirectory>/\JRE/\lib/\security/\cacerts (file)

    • <GatewayServerInstallationDirectory>/\odb/\conf/\security

    • <DataProcessingServerInstallationDirectory>/\BLE/\rules/\<CustomRulesJar> (file)

    • Files in the <HPEBSMrootDirectory><OBM_HOME>/\WebServer/\conf directory

    • <HPEBSMrootDirectory><OBM_HOME>/\conf/\jdbc.drivers.properties

    • <HPEBSMrootDirectory><OBM_HOME>/\conf/\omi-tnsnames.ora

    • <HPEBSMrootDirectory><OBM_HOME>/\odb/\conf/\jdbc.properties

    If you have named instances (for example RAC), save the file and the connection (which you specified in the jdbc.drivers.properties file and the RTSM).

    In addition, if Data Flow Probe (DFP) is integrated with BSMOBM, back up the certificates from the following directory:

    <DataFlowProbeInstallationDirectory>/\conf/\security

    For more information, see the Install the Data Flow Probe.

  • Recommended. Follow these steps to avoid data loss during the upgrade:

    1. Shut down the PostgreSQL database:

      <OBM_Home>\bin\opr-pgctl.bat –stop<OBM_Home>/bin/opr-pgctl.sh –stop

    2. Edit the postgresql.conf file at the following location:

      %ovinstalldir%\databases\omidb\postgresql.conf%ovinstalldir%/databases/omidb/postgresql.conf

      Set the max_locks_per_transaction parameter to 1000 and uncomment the line.

  • Recommended. DatabaseDatabase schema safety backup. For an increased safety of data, we recommend backing up the databasesdatabase schemas. To minimize the scope of the potential data loss, back them up as late before the BSMOBM uninstallation as possible.
  • Recommended. Database cleanup to speed up the upgrade.
    Follow these steps:
    1. Start the database:

      <OBM_Home>\bin\opr-pgctl.bat -start<OBM_Home>/bin/opr-pgctl.sh -start

    2. Run vacuumlo on event and rtsm schemas:

      <OBM_Home>\pgsql\bin\vacuumlo -h <host> -p <port> -U postgres <Schema_Name><OBM_Home>/pgsql/bin/vacuumlo -h <host> -p <port> -U postgres <Schema_Name>

      Where Schema_Name is the schema name of the event or rtsm database.

      Important Do not run vacuumlo on the mgmt database as it will create a database inconsistency.

    3. Run vacuumdb:

      <OBM_Home>\pgsql\bin\vacuumdb --all --full -h <host> -p <port> -U postgres<OBM_Home>/pgsql/bin/vacuumdb --all --full -h <host> -p <port> -U postgres

    4. Stop the database:

      <OBM_Home>\bin\opr-pgctl.bat -stop<OBM_Home>/bin/opr-pgctl.sh -stop

  • The OPEN_CURSORS parameter of Oracle Database. For the upgrade, set the Oracle Database parameter OPEN_CURSORS to 10,000. You must revert this parameter to the original value after the upgrade is complete.

  • Integrations. For details on product versions that are supported with OBM 2019.05, select Operations Bridge Manager from the product list in the following document:

    Support Matrices for Operations Center products

  • Optional. RTSM integrations disablement. If integrations are configured in RTSM Integration Studio (for example, between the central UCMDB and RTSM), Data Flow Probe will run population jobs immediately after the upgrade for active integration points, even if the integration process is not scheduled. If you do not want the integrations to run, disable them before starting the upgrade.

  • Uninstallation of Data Flow Probe. If Data Flow Probe (DFP) is installed on one of the BSMOBM gateway servers, uninstall it separately before starting the upgrade process.

  • Management packs. If you plan to install the latest OBM management packs after the upgrade, uninstall the following management packs first:

    • OBM Management Pack for Oracle Database 1.00

    • OBM Management Pack for Infrastructure 1.00

    Later versions of these management packs do not have to be uninstalled. For uninstallation information, see the management pack documentation.

  • Predefined indices. The database schema upgrade fails if indices of the former database model have been removed. You can make sure that your installation does not miss any predefined indices by running the checkIndices tool and recreating the missing indices: <OBM_HOME>/\opr/\support/\checkIndices.batsh

  • Empty backup folder. PostgreSQL configuration data is backed up into the folder %OvDataDir%\backup/var/opt/OV/backup
    Make sure that the folder does not contain backup files from previous upgrades or installations. We recommend to empty this folder completely before running the upgrade.

  • Back up and re-install symbolic links. You must back up symbolic links in your existing OBM host systems and re-install them manually before the new OBM version is installed.

Plan the upgradeupgrade process

Upgrade your earlier OMi/OBM version to OBM 2019.05 as follows:

  1. Make sure that the earlier OMi/OBM version is enabled (all servicesprocesses are running).
  2. On the existing OMi/OBM host system, initiate the upgrade process.

  3. Attend the initial upgrade phase.

  4. Attend the uninstallation of the earlier OBM/OMi version and the invocation of the 2019.05 installation.

  5. Install OBM 2019.05 on the system that will host the new version by following the instructions of the installation wizard.

  6. Conclude the upgrade process by following the instructions of the configuration/upgrade wizard.

  1. Make sure that the earlier OMi/OBM version is enabled (all servicesprocesses are running).
  2. On the existing OMi/OBM host system, initiate the upgrade process.

  3. Attend the initial upgrade phase.

  4. Install OBM2019.05 on the system that will host the new version by following the instructions of the installation wizard.

  5. Conclude the upgrade process by following the instructions of the configuration/upgrade wizard.

  1. Make sure that the earlier OMi version is enabled (all servicesprocesses are running on the OMi host systems).

  2. On the primary DPS of your existing OBM/OMi deployment, initiate the upgrade process.

  3. Attend the initial upgrade phase. Perform steps 4 to 6 on the OBM staging server.

  4. On the host system of your future primary data processing server (DPS), start the 2019.05 installation.

  5. Install OBM 2019.05 by following the instructions of the installation wizard.

  6. Follow the instructions of the configuration/upgrade wizard, and conclude the upgrade process.

  7. After the primary DPS is upgraded, repeat all the above steps to upgrade gateways and secondary DPS.
  1. Make sure that the earlier OMi/OBM version is enabled (all servicesprocesses must be running on the primary DPS and the secondary DPS and gateways must be brought down). Depending on the earlier OMi/OBM version, run one of the following commands to stop services on the secondary DPS and gateways:

    /opt/HP/BSM/scripts/run_hpbsm stop

    HPBSM\bin\SupervisorStop

  2. On the host system of the primary (first installed) data processing server (DPS) in your existing OMi/OBM environment, initiate the upgrade process.

    1. Attend uninstallation of the earlier OMi/OBM version and invocation of the installation wizard.

    2. Install OBM 2019.05 by following the instructions of the installation wizard.

      After the installation is complete, the Configuration/Upgrade wizard is displayed.

    3. Conclude the upgrade process by following instructions on the configuration/upgrade wizard.
    4. After the configuration/upgrade wizard is complete, start OBM services on the primary DPS.
  3. Perform the following steps on each GWS:

    1. Initiate the upgrade process.

    2. Attend uninstallation of the earlier OMi version and invocation of the installation wizard.

    3. Install OBM 2019.05 by following the instructions of the installation wizard.

      After the installation is complete, the Configuration/Upgrade wizard is displayed.

    4. Conclude the upgrade process by following instructions on the configuration/upgrade wizard.
    5. After the configuration/upgrade wizard is complete, start OBM services on the gateway server.
  4. Perform the following steps on each secondary DPS:

    1. Initiate the upgrade process.

    2. Attend uninstallation of the earlier OMi version and invocation of the installation wizard.

    3. Install OBM2019.05 by following the instructions of the installation wizard.

      After the installation is complete, the Configuration/Upgrade wizard is displayed.

    4. Conclude the upgrade process by following instructions on the configuration/upgrade wizard.
    5. After the configuration/upgrade wizard is complete, start OBM services on the additional DPS.
  1. Make sure that the earlier OMi version is enabled (all servicesprocesses are running on the OMi host systems).

  2. On the primary DPS of your existing OBM/OMi deployment, initiate the upgrade process.

  3. Attend the initial upgrade phase. Perform steps 4 to 6 on the OBM staging server.

  4. On the host system of your future primary data processing server (DPS), start the 2019.05installation.

  5. Install OBM 2019.05 by following the instructions of the installation wizard.

  6. Follow the instructions of the configuration/upgrade wizard, and conclude the upgrade process.

  7. After the primary DPS is upgraded, repeat all the above steps to upgrade gateways and secondary DPS.

Run the Pre-Upgrade Tool

The pre-upgrade tool ensures the event queue is emptied. If you do not run the pre-upgrade tool before shutting down or uninstalling OBM, events from your environment may be lost. On Linux systems, the pre-upgrade tool can be run as non-root user.

Important If you have only one data processing server, running the pre-upgrade tool is not required.

  1. Make sure OBM is running on all data processing and gateway servers.

  2. On the active data processing server, run the following command to invoke the pre-upgrade tool:

    Note The pre-upgrade tool will stop the event flow. The event flow will be started again once the upgrade wizard is finished on all data processing servers.

    <OBM_HOME>\opr\bin\PreUpgradeTool.bat -d-s

    <OBM_HOME>/opr/bin/PreUpgradeTool.sh -d-s

    If there are a large number of closed events stored in the database, the upgrade may take a long time. If recommended by the tool, and you want to archive closed events before the upgrade starts, enter "yes" (y) when prompted and specify the target location for the archive file.

  3. On each gateway server, invoke the pre-upgrade tool by running the following command:

    <OBM_HOME>\opr\bin\PreUpgradeTool.bat -d-s

    <OBM_HOME>/opr/bin/PreUpgradeTool.sh -d-s

  1. Make sure OBM is running.

  2. To invoke the pre-upgrade tool on the OBM server, run the following command:

    <OBM_HOME>\opr\bin\PreUpgradeTool.bat -d-s

    <OBM_HOME>/opr/bin/PreUpgradeTool.sh -d-s

Fulfill the upgrade prerequisites and pPlan the upgrade process

Before you start with the upgrade of your BSMOBM servers, consider the following:

  • You can only extend your existing BSMOBM environment with additional servers once it is upgraded to OBM 2019.05. Thus, first upgrade all configured servers of the existing deployment to OBM 2019.05. Afterward, install and configure additional OBM servers as desired by following the ordinary installation procedure.

  • You can verify that the installation files are original Micro Focus-provided code and have not been manipulated by a third-party. For instructions, see the GPG or RPM Signature Verification web site.

  • Do not attempt to disable or uninstall BSMOBM before initiating the upgrade process. In the opposite case, you might lose events from your BSMOBM environment.

  • To utilize silent mode during the OBM installation and configuration, prepare the OBM installation parameters file at the beginning of the upgrade sequence. At that time, you can also direct OBM to use non-default installation directories.

    Full silent upgrade is not supported. As part of the upgrade, only uninstall of previous version and install of new version of OBM can run in silent mode. The configuration wizard for upgrade needs to always be run in non-silent mode.

  • Installing OBM in the console mode (using the ‑console command line option) is not supported.

  • If anti-virus software is running locally, you can leave it running also during the upgrade. While you might receive an anti-virus warning, you can safely ignore it and proceed with the upgrade without taking any action.

  • Modifying or repairing the installed OBM 2019.05 is not supported, therefore the Modify and Repair options are unavailable if the OBM installation wizard is invoked after the upgrade.

Before you initiate the upgrade process, make sure the following prerequisites are fulfilled:

  • Make sure that no other installations or processes that require Windows Installer are running. In the opposite case, OBM installation cannot complete and you must terminate it by clicking Cancel in the OBM installation wizard

Perform the upgrade actions according to the below sequence, which is based on your single-serverdistributed BSMOBM deployment and the selected upgrade type (in-place upgradeside-by-side-migration).

Caution Make sure to consistently follow the steps of the procedure in the order they are documented.

  1. Make sure that BSMthe earlier OBM version is enabled (all servicesprocesses are running).

  2. On the existing BSMOBM host system, initiate the upgrade process.

  3. Attend the initial upgrade phase.

  4. Attend uninstallation of BSMthe earlier OBM version and invocation of the 2019.05 installation.

  5. Install OBM2019.05 by following the instructions of the installation wizard.

  6. Start the configuration wizard. The configuration wizard cannot be run in silent mode for upgrade.

  7. Conclude the upgrade process by following the instructions of the configuration wizard.

  1. Make sure that BSMthe earlier OBM version is enabled (all servicesprocesses are running on the BSMOBM host systems).

  2. On each new system that will host an OBM server, prepare the OBM installation parameters file.

  3. On each system of your existing OBM deployment, initiate the upgrade process.

  4. On the host system of your future primary (first installed) data processing server (DPS), start the 2019.05 installation.

  5. Start the configuration wizard. The configuration wizard cannot run in silent mode for upgrade.

  6. Follow instructions of the configuration wizard, and conclude the upgrade process.

  7. On each system that will host an additional DPS or a gateway server (GS), follow the steps:

    1. Start the OBM 2019.05 installation.

    2. Start the configuration wizard.

    3. Follow instructions of the configuration wizard and configure OBM.
  1. Make sure that BSMthe earlier OBM version is enabled (all servicesprocesses must be running on the primary DPS and the secondary DPS and gateways must be brought down). Run the following command to stop servicesprocesses on the secondary DPS and gateways:

    /opt/HP/BSM/scripts/run_hpbsm stop

    HPBSM\bin\SupervisorStop

  2. On each host system of your BSMexisting OBM environment, prepare the OBM installation parameters file.

  3. On the host system of the primary (first installed) data processing server (DPS) of your BSMexisting OBM environment, initiate the upgrade process.

  4. Attend the initial upgrade phase.
  5. Attend the uninstallation of BSMyour earlier OBM version and the invocation of the OBM 2019.05 installation.

  6. On each system that hosts an additional DPS or a gateway server (GS), follow the steps:

    1. Initiate the upgrade process.
    2. Attend uninstallation of BSMthe earlier OBM version and invocation of the OBM 2019.05 installation.

  7. On the host system of the primary (first installed) DPS, start the configuration wizard. The configuration wizard cannot run in silent mode for upgrade.

  8. Follow the instructions of the configuration wizard and conclude the upgrade process.

  9. To switch to non-root user, run the configuration wizard on the primary DPS.
  10. On each system that hosts an additional DPS or a GS, follow the steps:

    1. Start the configuration wizard silently.

    2. Follow the instructions for the silent configuration to configure OBM.

Configure event buffering in OM

If you have been using OM to forward events to BSMthe already installed OMi version, configure OM event buffering.

During the migration, OM continues to attempt sending events to BSMthe already installed OMi version. If BSMthe original OMi servers cannot be reached, OM starts to buffer the events until the new OBM servers are online. Depending on the length of the outage and the number of events, adjust the maximum length of the delivery timeout and the maximum size of the buffer file so that OM does not discard any unsent events.

Note When the upgrade is complete, you can restore the original values of the buffer.

Configure event buffering in OM

If you have been using OM to forward events to BSMthe already installed OMi version, configure OM event buffering.

During the migration, OM continues to attempt sending events to BSMthe already installed OMi version. If BSMthe original OMi servers cannot be reached, OM starts to buffer the events until the new OBM servers are online. Depending on the length of the outage and the number of events, adjust the maximum length of the delivery timeout and the maximum size of the buffer file so that OM does not discard any unsent events.

Note When the upgrade is complete, you can restore the original values of the buffer.

Prepare the OBM installation parameters file

  1. On the BSMOBM host systemnew system that will host OBM, create an empty file called ovinstallparams.ini in the same directory as the HPOMi_<VersionAndBuild>_setup.exeHPOMi_<VersionAndBuild>_setup.bin executable file, for example in the following directory:

    <OBMInstallationFiles>\/Software\/HPOMi_<VersionAndBuild>_setup.exebin

    <OBMInstallationFiles>\/Software\/ovinstallparams.ini

  2. Copy the following section to the ovinstallparams.ini file:

    [installer.properties]
    setup=HPOMi
    group=typical
  3. To change the default installation directories, add the following lines at the end of the file:

    installDir=<SharedComponentsBinaryFilesDirectory>
    dataDir=<SharedComponentsDataDirectory>
    prodInstallDir=<OBMBinaryFilesDirectory>
    prodDataDir=<OBMDataDirectory>

    Note The first two lines apply to the shared data (shared components), and the last two lines apply to OBM.

    The paths can contain space characters. In this case, do not enclose them with quotation marks.

    You may check the following environment variables to determine the above directories:

    Directory Environment variable
    installDir (SharedComponentsBinaryFilesDirectory) OVINSTALLDIR
    dataDir (SharedComponentsDataDirectory) OVDATADIR
    prodInstallDir (OBMBinaryFilesDirectory) TOPAZ_HOME
    prodDataDir (OBMDataDirectory) TOPAZ_HOME

    The installation folder for OBM content must not exist yet, and the directory name that you specify must:

    The OBM binary files directory (<OBMBinaryFilesDirectory>) must not exist yet, and the directory name that you specify must:

    • Be shorter than 16 characters

    • Contain only the following characters: a-z, A-Z, 0-9, underscore (_), hyphen (-), period (.), backslash (\), slash (/), and colon (:)

    • End with the HPBSM string

  1. On each OBM host systemnew system that will host OBM, create an empty file called ovinstallparams.ini in the same directory as the HPOMi_<VersionAndBuild>_setup.exeHPOMi_<VersionAndBuild>_setup.bin executable file, for example in the following directory:

    <OBMInstallationFiles>\/Software\/HPOMi_<VersionAndBuild>_setup.exebin

    <OBMInstallationFiles>\/Software\/ovinstallparams.ini

  2. Depending on whether the host system iswill be a data processing server or a gateway server, copy the appropriate section to the ovinstallparams.ini file:

    • Data processing server:

      [installer.properties]
      setup=HPOMi
      group=process
    • Gateway server:

      [installer.properties]
      setup=HPOMi
      group=gateway
  3. To change the default installation directories, add the following lines at the end of the file:

    installDir=<SharedComponentsBinaryFilesDirectory>
    dataDir=<SharedComponentsDataDirectory>
    prodInstallDir=<OBMBinaryFilesDirectory>
    prodDataDir=<OBMDataDirectory>

    Note The first two lines apply to the shared data (shared components), and the last two lines apply to OBM.

    The paths can contain space characters. In this case, do not enclose them with quotation marks.

    You may check the following environment variables to determine the above directories:

    Directory Environment variable
    installDir (SharedComponentsBinaryFilesDirectory) OVINSTALLDIR
    dataDir (SharedComponentsDataDirectory) OVDATADIR
    prodInstallDir (OBMBinaryFilesDirectory) TOPAZ_HOME
    prodDataDir (OBMDataDirectory) TOPAZ_HOME

    The installation folder for OBM content must not exist yet, and the directory name that you specify must:

    The OBM binary files directory (<OBMBinaryFilesDirectory>) must not exist yet, and the directory name that you specify must:

    • Be shorter than 16 characters

    • Contain only the following characters: a-z, A-Z, 0-9, underscore (_), hyphen (-), period (.), backslash (\), slash (/), and colon (:)

    • End with the HPBSM string

Initiate the upgrade process

Caution This section applies only to the host system of the primary data processing server in your BSMOBMexisting OBM deployment.

Caution This section applies only to the host system of the primary data processing server in your BSMOBMexisting OBM deployment.

To initiate the first phase of the upgrade process for the local systemexisting BSMOBM host system, follow the steps:

  1. Open a Command Promptterminal window as an administratorthe root user.

  2. Change the current directory to the location where you have extracted files from the 2019.05 installation package to as follows:

    cd <OBMInstallationFilesDirectory>

  3. Run the following command:

    upgrade.sh -d -silent -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -d -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    Run the following command:

    upgrade.sh -silent -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    Run the following command on the primary DPS of your existing OBM environment:

    upgrade.sh -d [-silent] -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -d -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

    Perform the following depending on the system for which you are initiating the upgrade:

    For the primary data processing server (DPS) of the existing BSMOBM environment

    Run the following command:

    upgrade.sh -d [-silent] -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -d -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

    After the primary DPS is upgraded, that is, after OBM 2019.05 is installed and configured on the primary DPS, start the services on the primary DPS. Do not proceed to upgrade the gateway servers and the non-primary DPS until the primary DPS is upgraded and the services are started.

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    After the uninstallation completes, access the installation folder OBM_2019.05._for_Windows and manually run install.bat.

    For a gateway server

    Run the following command:

    upgrade.sh -d -silent -s -noprep

    Note

    If the upgrade.sh -d -silent -noprep command does not start the uninstallation process, run the following command instead:  
     
    "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent

    After the gateway server is upgraded, that is, after OBM 2019.05 is installed and configured on the gateway server, start the services on the gateway server. Do not proceed to upgrade the non-primary DPS until the gateway servers are upgraded and the services are started.

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    After the uninstallation completes, access the installation folder OBM_2019.05._for_Windows and manually run install.bat.

    For a non-primary DPS

    Run the following command:

    upgrade.sh -d -silent -s -noprep

    Note

    If the upgrade.sh -d -silent -noprep command does not start the uninstallation process, run the following command instead:  
     
    "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    After the uninstallation completes, access the installation folder OBM_2019.05._for_Windows and manually run install.bat.

    Run the following command on the primary DPS of your existing OBM environment:

    upgrade.sh [-silent] -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

  4. Carefully follow further instructions in this guide.

Initiate the upgrade process

Caution This section applies only to the host system of the primary data processing server in your BSMOBMexisting OBM deployment.

Caution This section applies only to the host system of the primary data processing server in your BSMOBMexisting OBM deployment.

To initiate the first phase of the upgrade process for the local systemexisting BSMOBM host system, follow the steps:

  1. Open a Command Promptterminal window as an administratorthe root user.

  2. Change the current directory to the location where you have extracted files from the 2019.05 installation package to as follows:

    cd <OBMInstallationFilesDirectory>

  3. Run the following command:

    upgrade.sh -d -silent -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -d -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    Run the following command:

    upgrade.sh -silent -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    Run the following command on the primary DPS of your existing OBM environment:

    upgrade.sh -d [-silent] -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -d -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

    Perform the following depending on the system for which you are initiating the upgrade:

    For the primary data processing server (DPS) of the existing BSMOBM environment

    Run the following command:

    upgrade.sh -d [-silent] -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -d -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

    After the primary DPS is upgraded, that is, after OBM 2019.05 is installed and configured on the primary DPS, start the services on the primary DPS. Do not proceed to upgrade the gateway servers and the non-primary DPS until the primary DPS is upgraded and the services are started.

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    After the uninstallation completes, access the installation folder OBM_2019.05._for_Windows and manually run install.bat.

    For a gateway server

    Run the following command:

    upgrade.sh -d -silent -s -noprep

    Note

    If the upgrade.sh -d -silent -noprep command does not start the uninstallation process, run the following command instead:  
     
    "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent

    After the gateway server is upgraded, that is, after OBM 2019.05 is installed and configured on the gateway server, start the services on the gateway server. Do not proceed to upgrade the non-primary DPS until the gateway servers are upgraded and the services are started.

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    After the uninstallation completes, access the installation folder OBM_2019.05._for_Windows and manually run install.bat.

    For a non-primary DPS

    Run the following command:

    upgrade.sh -d -silent -s -noprep

    Note

    If the upgrade.sh -d -silent -noprep command does not start the uninstallation process, run the following command instead:  
     
    "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent

    Applies only if you are upgrading from OMi 10.12 IP6. When you are asked if you really want to start uninstalling Operations Manager i 10.x, do not proceed. Instead, follow these steps:

    1. Go to Control Panel > Programs > Programs and Features> Uninstall a program.
    2. Select Performance Engine, right-click and click Uninstall.
    3. Return to the upgrade script and type y to continue.

    After the uninstallation completes, access the installation folder OBM_2019.05._for_Windows and manually run install.bat.

    Run the following command on the primary DPS of your existing OBM environment:

    upgrade.sh [-silent] -s

    If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade.

    upgrade.sh -silent -archive=true -s

    If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false.

    If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message:

    There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)?

    press Y and accept the default location.

    If you receive the warning

    Failed to query all users from DB.: User is not mapped...

    you can safely ignore it and proceed with the upgrade.

  4. Carefully follow further instructions in this guide.

Attend the initial upgrade phase

During the initial upgrade phase, the following operations are performed:

  • The event queue is emptied.

  • You are given the ability to shorten the upgrade process by choosing not to upgrade closed events.

    If there are numerous closed events stored in the BSMoriginal OMi Event database, the upgrade process might take a very long time. To avoid this situation, OBM offers an automatic archival and purge of the closed events before their upgrade.

  • Configuration data and the data from the embedded PostgreSQL database is backed up into the following file:

    %OvDataDir%\backup\OMi<Previous_Version>cfg-backup.zip

    /var/opt/OV/backup/OMi<Previous_Version>cfg-backup.zip

While the process progresses, the following lines are written into the Command Prompt windowcommand shell:

INFO: Upgrading from OMixx
INFO: Running PreMigration Tool to prepare for upgrade
INFO: Backup config data to /var/opt/OV/backup before uninstalling
INFO: Found created backup files under /var/opt/OV/backup

INFO: Upgrading from OMixx
INFO: Running PreMigration Tool to prepare for upgrade
INFO: Backup config data to \var\opt\OV\backup before uninstalling
INFO: Found created backup files under \var\opt\OV\backup

Sometimes the following error may be reported as well:

Pre-upgrade process executed with some errors.

If this occurs, press N to cancel pending uninstallation, restart the host system, and then initiate the upgrade process again.

Attend the initial upgrade phase

During the initial upgrade phase, the following operations are performed:

  • The event queue is emptied.

  • You are given the ability to shorten the upgrade process by choosing not to upgrade closed events.

    If there are numerous closed events stored in the BSMoriginal OMi Event database, the upgrade process might take a very long time. To avoid this situation, OBM offers an automatic archival and purge of the closed events before their upgrade.

  • Configuration data and the data from the embedded PostgreSQL database is backed up into the following file:

    %OvDataDir%\backup\OMi<Previous_Version>cfg-backup.zip

    /var/opt/OV/backup/OMi<Previous_Version>cfg-backup.zip

While the process progresses, the following lines are written into the Command Prompt windowcommand shell:

INFO: Upgrading from OMixx
INFO: Running PreMigration Tool to prepare for upgrade
INFO: Backup config data to /var/opt/OV/backup before uninstalling
INFO: Found created backup files under /var/opt/OV/backup

INFO: Upgrading from OMixx
INFO: Running PreMigration Tool to prepare for upgrade
INFO: Backup config data to \var\opt\OV\backup before uninstalling
INFO: Found created backup files under \var\opt\OV\backup

Sometimes the following error may be reported as well:

Pre-upgrade process executed with some errors.

If this occurs, press N to cancel pending uninstallation, restart the host system, and then initiate the upgrade process again.

Attend uninstallation of your earlier OMi/OBM version

The uninstallation process performs the following operations locally:

  1. Removes existing OMi intermediate patches (IPs) from the the host system.

  2. Removes the Monitoring Automation feature of BSM, if installed.

  3. Removes the User Engagement feature of OMi, if installed.

  4. Uninstalls OMi, including LCore/Agent. The configuration data in the %OvDataDir%/var/opt/OV directory is preserved.

During the process, the following lines are written into the Command Prompt windowcommand shell:

INFO: Stopping OBM for Uninstallation
INFO: Installing installation-wixard.jar hotfix
INFO: Uninstalling OBM 10.x patches...
INFO: Uninstalling <IP version>
INFO: Re-Installing installation-wizard.jar hotfix
INFO: Uninstalling OBM 10.x main application...
INFO: Uninstallation done - Starting installation of OBM

Attend invocation of the OBM 2019.05 installation

After BSMyour earlier OMi version is uninstalled, the upgrade process invokes the installation of OBM 2019.05. Invoke the installation of OBM 2019.05.

At this time, the following lines are written into the Command Prompt windowcommand shell:

INFO: (install) Starting installation of HP Operations Manager i
INFO: (install) Successfully started installation of HP Operations Manager i

Plan the installation process

Install OBM as follows:

  1. On the system that will host OBM, prepare the OBM installation parameters file.

  2. Start the installation wizard and install OBM 2019.05.

  3. Start the configuration wizard and configure OBM.

    Tip The configuration wizard is invoked automatically when a proper option is selected in the final page of the post-installation wizard.

1. On each system that will host OBM, prepare the OBM installation parameters file.

2. Depending on the preferred OBM installation and configuration sequence, proceed as follows:

  • To install all OBM servers first and configure them afterward, do the following:

    1. On each system that will host either an OBM data processing server (DPS) or an OBM gateway server (GS), start the installation wizard and install OBM 2019.05.

      Do not proceed to perform a post-installation action at this point.

    2. On the system that will host the OBM primary DPS, start the configuration wizard and configure OBM.

    3. On each system that will host either the OBM secondary DPS or an OBM GS, start the configuration wizard and configure OBM.

      You can configure the secondary DPS and the gateway servers in parallel.

  • To install and configure all OBM servers one by one, start the installation wizard and install OBM 2019.05, then manually start the configuration wizard and configure OBM once the installation is complete. Perform these actions in the following systems in sequence:

    1. Each system that will host an OBM data processing server (DPS)

      The DPS that is configured first becomes the primary DPS of your OBM deployment.

    2. Each system that will host an OBM gateway server (GS)

Prepare the OBM installation parameters file

  1. On the BSMOBM host systemnew system that will host OBM, create an empty file called ovinstallparams.ini in the same directory as the HPOMi_<VersionAndBuild>_setup.exeHPOMi_<VersionAndBuild>_setup.bin executable file, for example in the following directory:

    <OBMInstallationFiles>\/Software\/HPOMi_<VersionAndBuild>_setup.exebin

    <OBMInstallationFiles>\/Software\/ovinstallparams.ini

  2. Copy the following section to the ovinstallparams.ini file:

    [installer.properties]
    setup=HPOMi
    group=typical
  3. To change the default installation directories, add the following lines at the end of the file:

    installDir=<SharedComponentsBinaryFilesDirectory>
    dataDir=<SharedComponentsDataDirectory>
    prodInstallDir=<OBMBinaryFilesDirectory>
    prodDataDir=<OBMDataDirectory>

    Note The first two lines apply to the shared data (shared components), and the last two lines apply to OBM.

    The paths can contain space characters. In this case, do not enclose them with quotation marks.

    You may check the following environment variables to determine the above directories:

    Directory Environment variable
    installDir (SharedComponentsBinaryFilesDirectory) OVINSTALLDIR
    dataDir (SharedComponentsDataDirectory) OVDATADIR
    prodInstallDir (OBMBinaryFilesDirectory) TOPAZ_HOME
    prodDataDir (OBMDataDirectory) TOPAZ_HOME

    The installation folder for OBM content must not exist yet, and the directory name that you specify must:

    The OBM binary files directory (<OBMBinaryFilesDirectory>) must not exist yet, and the directory name that you specify must:

    • Be shorter than 16 characters

    • Contain only the following characters: a-z, A-Z, 0-9, underscore (_), hyphen (-), period (.), backslash (\), slash (/), and colon (:)

    • End with the HPBSM string

  1. On each OBM host systemnew system that will host OBM, create an empty file called ovinstallparams.ini in the same directory as the HPOMi_<VersionAndBuild>_setup.exeHPOMi_<VersionAndBuild>_setup.bin executable file, for example in the following directory:

    <OBMInstallationFiles>\/Software\/HPOMi_<VersionAndBuild>_setup.exebin

    <OBMInstallationFiles>\/Software\/ovinstallparams.ini

  2. Depending on whether the host system iswill be a data processing server or a gateway server, copy the appropriate section to the ovinstallparams.ini file:

    • Data processing server:

      [installer.properties]
      setup=HPOMi
      group=process
    • Gateway server:

      [installer.properties]
      setup=HPOMi
      group=gateway
  3. To change the default installation directories, add the following lines at the end of the file:

    installDir=<SharedComponentsBinaryFilesDirectory>
    dataDir=<SharedComponentsDataDirectory>
    prodInstallDir=<OBMBinaryFilesDirectory>
    prodDataDir=<OBMDataDirectory>

    Note The first two lines apply to the shared data (shared components), and the last two lines apply to OBM.

    The paths can contain space characters. In this case, do not enclose them with quotation marks.

    You may check the following environment variables to determine the above directories:

    Directory Environment variable
    installDir (SharedComponentsBinaryFilesDirectory) OVINSTALLDIR
    dataDir (SharedComponentsDataDirectory) OVDATADIR
    prodInstallDir (OBMBinaryFilesDirectory) TOPAZ_HOME
    prodDataDir (OBMDataDirectory) TOPAZ_HOME

    The installation folder for OBM content must not exist yet, and the directory name that you specify must:

    The OBM binary files directory (<OBMBinaryFilesDirectory>) must not exist yet, and the directory name that you specify must:

    • Be shorter than 16 characters

    • Contain only the following characters: a-z, A-Z, 0-9, underscore (_), hyphen (-), period (.), backslash (\), slash (/), and colon (:)

    • End with the HPBSM string

Start the OBM 2019.05 installation

Invocation of the OBM 2019.05 installation is the same for both deployment types and both server types. Previously prepared ovinstallparams.ini file defines the type of the installed OBM server. You can select the server type (and implicitly choose the deployment) in a dedicated page of the OBM installation wizard.

To start the installation, follow the steps on the new host systems:

  1. Open a Command Promptterminal window as an administratorthe root user.
  2. Change the current directory as follows:

    cd <OBMInstallationFilesDirectory>

  3. To start the installation in the GUI mode (invoke the installation wizard), run the following command:

    install

    To start the installation in the silent mode, run the following command:

    install -silent

  4. Depending on the desired installation mode, proceed as follows:

    • To start the installation in the GUI mode (invoke the installation wizard), run the following command:

      ./install.sh

    • To start the installation in the console mode, run the following command:

      ./install.sh -console

      Alternatively, unset the $DISPLAY shell environment variable and run the command without specifying the ‑console option.

      Note After the console-mode installation completes, start the configuration wizard manually. For instructions on how to do that, see Operations Bridge Manager 2019.05 Installation and Upgrade Guide.

    To start the installation in the silent mode, run the following command:

    ./install.sh -silent

  5. Attend installation of OBM 2019.05. In a virtual environment, this phase might take approximately between 30 and 60 minutes.

Start the OBM 2019.05 installation

Invocation of the OBM 2019.05 installation is the same for both deployment types and both server types. Previously prepared ovinstallparams.ini file defines the type of the installed OBM server. You can select the server type (and implicitly choose the deployment) in a dedicated page of the OBM installation wizard.

To start the installation, follow the steps on the new host systems:

  1. Open a Command Promptterminal window as an administratorthe root user.
  2. Change the current directory as follows:

    cd <OBMInstallationFilesDirectory>

  3. To start the installation in the GUI mode (invoke the installation wizard), run the following command:

    install

    To start the installation in the silent mode, run the following command:

    install -silent

  4. Depending on the desired installation mode, proceed as follows:

    • To start the installation in the GUI mode (invoke the installation wizard), run the following command:

      ./install.sh

    • To start the installation in the console mode, run the following command:

      ./install.sh -console

      Alternatively, unset the $DISPLAY shell environment variable and run the command without specifying the ‑console option.

      Note After the console-mode installation completes, start the configuration wizard manually. For instructions on how to do that, see Operations Bridge Manager 2019.05 Installation and Upgrade Guide.

    To start the installation in the silent mode, run the following command:

    ./install.sh -silent

  5. Attend installation of OBM 2019.05. In a virtual environment, this phase might take approximately between 30 and 60 minutes.

Start the OBM 2019.05 installation

Invocation of the OBM 2019.05 installation is the same for both deployment types and both server types. Previously prepared ovinstallparams.ini file defines the type of the installed OBM server. You can select the server type (and implicitly choose the deployment) in a dedicated page of the OBM installation wizard.

To start the installation, follow the steps on the new host systems:

  1. Open a Command Promptterminal window as an administratorthe root user.
  2. Change the current directory as follows:

    cd <OBMInstallationFilesDirectory>

  3. To start the installation in the GUI mode (invoke the installation wizard), run the following command:

    install

    To start the installation in the silent mode, run the following command:

    install -silent

  4. Depending on the desired installation mode, proceed as follows:

    • To start the installation in the GUI mode (invoke the installation wizard), run the following command:

      ./install.sh

    • To start the installation in the console mode, run the following command:

      ./install.sh -console

      Alternatively, unset the $DISPLAY shell environment variable and run the command without specifying the ‑console option.

      Note After the console-mode installation completes, start the configuration wizard manually. For instructions on how to do that, see Operations Bridge Manager 2019.05 Installation and Upgrade Guide.

    To start the installation in the silent mode, run the following command:

    ./install.sh -silent

  5. Attend installation of OBM 2019.05. In a virtual environment, this phase might take approximately between 30 and 60 minutes.

Choose the preferred language

Your installer may offer additional languages. The language that you choose in the initial installer window is used for the installation wizard.

Windows Installer: Language Selection page

From the available drop-down list, select the preferred language for the installation wizard, and then click OK.

Note Your selection does not affect the following:

  • The language of the configuration wizard (it is determined automatically based on the operating system settings)

  • The language used in the OBM console

Choose the preferred language

Your installer may offer additional languages. The language that you choose in the initial installer window is used for the installation wizard.

Windows Installer: Language Selection page

From the available drop-down list, select the preferred language for the installation wizard, and then click OK.

Note Your selection does not affect the following:

  • The language of the configuration wizard (it is determined automatically based on the operating system settings)

  • The language used in the OBM console

Attend initialization of OBM 2019.05 installation

During the initial phase the installation wizard checks the host system for the following:

  • Supported operating system

  • Sufficient physical memory

  • Sufficient free storage space at the location the /tmp path points todefined by the %TEMP% user environment variable

Installation wizard: Initialization page

Attend initialization of OBM 2019.05 installation

During the initial phase the installation wizard checks the host system for the following:

  • Supported operating system

  • Sufficient physical memory

  • Sufficient free storage space at the location the /tmp path points todefined by the %TEMP% user environment variable

Installation wizard: Initialization page

Read the introduction

The Introduction (Install) page describes the installation wizard in general. Familiarize yourself with the information provided and then click Next.

Installation wizard: Introduction (Install) page

Read the introduction

The Introduction (Install) page describes the installation wizard in general. Familiarize yourself with the information provided and then click Next.

Installation wizard: Introduction (Install) page

Review the license agreement

In the Product Agreement (License Agreement) page, accept the license agreement and click Next to continue with the installation. If you decline, the installation cannot proceed.

Installation wizard: Product Agreement (License Agreement) page

Review the license agreement

In the Product Agreement (License Agreement) page, accept the license agreement and click Next to continue with the installation. If you decline, the installation cannot proceed.

Installation wizard: Product Agreement (License Agreement) page

Choose the server type

In the Product Customization page, select the Single Server option. This option installs the gateway server and the data processing server on the same system. Click Next to continue.

Installation wizard: Product Customization page - data processing server

In the Product Customization page, select the OBM server type you want to install on the local system:

  • Gateway Server. Installs the OBM gateway server.

  • Data Processing Server. Installs the OBM data processing server.

Installation wizard: Product Customization page - data processing server

Click Next to continue.

Note If a previous version of OMi is detected on the system, the installation wizard warns you about losing customized configuration data of that product version.

Choose the server type

In the Product Customization page, select the Single Server option. This option installs the gateway server and the data processing server on the same system. Click Next to continue.

Installation wizard: Product Customization page - data processing server

In the Product Customization page, select the OBM server type you want to install on the local system:

  • Gateway Server. Installs the OBM gateway server.

  • Data Processing Server. Installs the OBM data processing server.

Installation wizard: Product Customization page - data processing server

Click Next to continue.

Note If a previous version of OMi is detected on the system, the installation wizard warns you about losing customized configuration data of that product version.

Verify the installation directories

Verify whether the OBM installation directories can be created at their predefined locations, and check if the respective mount points provide the necessary storage space. The directories are as follows:

  • /opt/HP/BSM (directory of the OBM components)

  • /opt/OV (binary files directory of the Operations Agent components and the shared content)

  • /var/opt/OV (data directory of the Operations Agent components and the shared content)

Click Next.

Verify the installation directories

Verify whether the OBM installation directories can be created at their predefined locations, and check if the respective mount points provide the necessary storage space. The directories are as follows:

  • /opt/HP/BSM (directory of the OBM components)

  • /opt/OV (binary files directory of the Operations Agent components and the shared content)

  • /var/opt/OV (data directory of the Operations Agent components and the shared content)

Click Next.

Specify the installation folders

Select the following folders for the installation:

  • Note  

    • There is additional shared data in the %ALLUSERSPROFILE%\HP\BSM directory.
    • During the installation of OBM 2019.05, verify if the value in the Data folder for shared content text box matches the one that was used for the old OMi installation. If you choose not to do so, backup data cannot be found at the restore time.
  • Installation folder for the product-specific (OBM) content.

    The installation folder for OBM content must not exist yet, and the directory name that you specify must:

    The OBM binary files directory (<OBMBinaryFilesDirectory>) must not exist yet, and the directory name that you specify must:

    • Be shorter than 16 characters

    • Contain only the following characters: a-z, A-Z, 0-9, underscore (_), hyphen (-), period (.), backslash (\), slash (/), and colon (:)

    • End with the HPBSM string

    If the requirements are not met, the installation wizard prompts you to give the folder a different name in the next step.

Installation wizard: Product Customization page - folders

Note If you are installing OBM onto a system running Windows Server 2008 R2, the following message may appear:

The installation folder for shared content is not valid.

This may occur because you do not have administrative privileges on the system, which are necessary to install OBM. Check with your system administrator.

Click Next.

Specify the installation folders

Select the following folders for the installation:

  • Note  

    • There is additional shared data in the %ALLUSERSPROFILE%\HP\BSM directory.
    • During the installation of OBM 2019.05, verify if the value in the Data folder for shared content text box matches the one that was used for the old OMi installation. If you choose not to do so, backup data cannot be found at the restore time.
  • Installation folder for the product-specific (OBM) content.

    The installation folder for OBM content must not exist yet, and the directory name that you specify must:

    The OBM binary files directory (<OBMBinaryFilesDirectory>) must not exist yet, and the directory name that you specify must:

    • Be shorter than 16 characters

    • Contain only the following characters: a-z, A-Z, 0-9, underscore (_), hyphen (-), period (.), backslash (\), slash (/), and colon (:)

    • End with the HPBSM string

    If the requirements are not met, the installation wizard prompts you to give the folder a different name in the next step.

Installation wizard: Product Customization page - folders

Note If you are installing OBM onto a system running Windows Server 2008 R2, the following message may appear:

The installation folder for shared content is not valid.

This may occur because you do not have administrative privileges on the system, which are necessary to install OBM. Check with your system administrator.

Click Next.

Review the product requirements

While the Product Requirements page is visible, the installation wizard performs various checks if the system meets the requirements for installing OBM.

Installation wizard: Product Requirements page

In the Product Requirements page, click Next.

Note If a requirement check fails, review the warning message and revise the product requirements listed in this guide. After updating the problematic resource, click Previous and then Next to continue with the installation.

Review the product requirements

While the Product Requirements page is visible, the installation wizard performs various checks if the system meets the requirements for installing OBM.

Installation wizard: Product Requirements page

In the Product Requirements page, click Next.

Note If a requirement check fails, review the warning message and revise the product requirements listed in this guide. After updating the problematic resource, click Previous and then Next to continue with the installation.

Initiate OBM 2019.05 installation

In the Pre-Install Summary page, review the information and then click Install to start the installation.

Installation wizard: Pre-Install Summary page

Initiate OBM 2019.05 installation

In the Pre-Install Summary page, review the information and then click Install to start the installation.

Installation wizard: Pre-Install Summary page

Attend OBM 2019.05 installation

While the Installing page is visible, attend the installation of OBM 2019.05. In a virtual environment, this phase might take approximately 30 to 60 minutes. Wait for the configuration wizard to appear.

Note If some required VC libraries are used by another process, your system might be rebooted during the installation. Restart the installation wizard after the reboot to continue with the installation.

Installation wizard: Installing page

Attend OBM 2019.05 installation

While the Installing page is visible, attend the installation of OBM 2019.05. In a virtual environment, this phase might take approximately 30 to 60 minutes. Wait for the configuration wizard to appear.

Note If some required VC libraries are used by another process, your system might be rebooted during the installation. Restart the installation wizard after the reboot to continue with the installation.

Installation wizard: Installing page

Optional. Configure OBM 2019.05 for Oracle Real Application Clusters

If the Oracle Database of your BSMprevious OBM environment is installed in a computer cluster based on Oracle Real Application Clusters (Oracle RAC), you had to specially configure BSMyour earlier OMi version to be able to use it. In this case, reapply these special configuration changes in OBM 2019.05. For instructions on how to do that, see "Appendix D: Support for Oracle Real Application Cluster" in the OBM Database Guide.

Choose the next step

When the Post-Install Configuration page of the post-installation wizard appears, the installation is complete. In the subsequent Next Steps page, you can choose to upgrade or configure OBM, or quit to postpone the upgrade or configuration.

Select Configure/Upgrade in the following cases:

  • If you are upgrading OBM on the primary data processing server, a secondary data processing server, or a gateway server.

  • If you want to configure OBM on this host system immediately.

Select Configure/Upgrade in the following cases:

  • If you want to upgrade the OBM server immediately.
  • If you want to configure OBM on this host system immediately.

Select Configure OBM to configure OBM on this host system immediately. Select Quit to postpone the configuration of OBM to a later time.

Select Quit to postpone configuration of OBM or the OBM upgrade completion to a later time. You can complete the configuration later by manually launching the configuration wizard. For information about launching the configuration wizard manually, see the Optional. Start the configuration wizard manually section.

Select Quit to postpone the OBM upgrade completion to a later time.

Installation wizard: Next Steps page

After making a selection, click Next.

Choose the next step

When the Post-Install Configuration page of the post-installation wizard appears, the installation is complete. In the subsequent Next Steps page, you can choose to upgrade or configure OBM, or quit to postpone the upgrade or configuration.

Select Configure/Upgrade in the following cases:

  • If you are upgrading OBM on the primary data processing server, a secondary data processing server, or a gateway server.

  • If you want to configure OBM on this host system immediately.

Select Configure/Upgrade in the following cases:

  • If you want to upgrade the OBM server immediately.
  • If you want to configure OBM on this host system immediately.

Select Configure OBM to configure OBM on this host system immediately. Select Quit to postpone the configuration of OBM to a later time.

Select Quit to postpone configuration of OBM or the OBM upgrade completion to a later time. You can complete the configuration later by manually launching the configuration wizard. For information about launching the configuration wizard manually, see the Optional. Start the configuration wizard manually section.

Select Quit to postpone the OBM upgrade completion to a later time.

Installation wizard: Next Steps page

After making a selection, click Next.

Choose the next step

When the Post-Install Configuration page of the post-installation wizard appears, the installation is complete. In the subsequent Next Steps page, you can choose to upgrade or configure OBM, or quit to postpone the upgrade or configuration.

Select Configure/Upgrade in the following cases:

  • If you are upgrading OBM on the primary data processing server, a secondary data processing server, or a gateway server.

  • If you want to configure OBM on this host system immediately.

Select Configure/Upgrade in the following cases:

  • If you want to upgrade the OBM server immediately.
  • If you want to configure OBM on this host system immediately.

Select Configure OBM to configure OBM on this host system immediately. Select Quit to postpone the configuration of OBM to a later time.

Select Quit to postpone configuration of OBM or the OBM upgrade completion to a later time. You can complete the configuration later by manually launching the configuration wizard. For information about launching the configuration wizard manually, see the Optional. Start the configuration wizard manually section.

Select Quit to postpone the OBM upgrade completion to a later time.

Installation wizard: Next Steps page

After making a selection, click Next.

Optional. Start the configuration wizard manually

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading. Ensure that the configuration wizard is run on the primary OBM data processing server before performing the steps described in this section.

If you previously quit the OBM configuration wizard (or you installed OBM silently), you can later start the configuration wizard manually.

Note The OBM configuration wizard must be used on all systems that host new OBM installationsthe host systems of the primary data processing server, additional data processing server and all gateway servers (in distributed BSMOBM deployments).

You must specify the same database and connection parameters for each OBM server, regardless of whether the servers are at the same location or they are geographically separated.

You can modify any configuration settings at a later time. To change a setting, start the configuration wizard again. Before you restart the wizard, disable OBM.

To start the configuration wizard manually, follow the steps:

  1. If this is not the first time you are starting the wizard, disable OBM.

    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss or severe integrity problems.

  2. Do one of the following:

    • Start the wizard from the operating system desktop:

      • Windows Server 2008:

        Select Start > Programs > Operations Bridge Manager > Administration > Configure Operations Bridge Manager.

      • Windows Server 2012:

        Press Ctrl + Esc and start typing Configure Operations Bridge Manager. Then click Configure Operations Bridge Manager in the search results.

    • Start the wizard from the command line:

      1. Open a Command Prompt window as an administrator.

      2. Change the current directory as follows:

        cd <OBM_HOME>\bin

      3. Run the following command:

        config-server-wizard.bat

To manually start the configuration wizard, follow the steps:

  1. If this is not the first time you are starting the wizard, disable OBM.

    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss and severe integrity problems.

  2. Open a command shell as the root user.

  3. Change the current directory as follows:

    cd /opt/HP/BSM/bin

  4. Run the following command:

    ./config-server-wizard.sh.

    The configuration wizard starts.

Optional. Start the configuration wizard manually

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading. Ensure that the configuration wizard is run on the primary OBM data processing server before performing the steps described in this section.

If you previously quit the OBM configuration wizard (or you installed OBM silently), you can later start the configuration wizard manually.

Note The OBM configuration wizard must be used on all systems that host new OBM installationsthe host systems of the primary data processing server, additional data processing server and all gateway servers (in distributed BSMOBM deployments).

You must specify the same database and connection parameters for each OBM server, regardless of whether the servers are at the same location or they are geographically separated.

You can modify any configuration settings at a later time. To change a setting, start the configuration wizard again. Before you restart the wizard, disable OBM.

To start the configuration wizard manually, follow the steps:

  1. If this is not the first time you are starting the wizard, disable OBM.

    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss or severe integrity problems.

  2. Do one of the following:

    • Start the wizard from the operating system desktop:

      • Windows Server 2008:

        Select Start > Programs > Operations Bridge Manager > Administration > Configure Operations Bridge Manager.

      • Windows Server 2012:

        Press Ctrl + Esc and start typing Configure Operations Bridge Manager. Then click Configure Operations Bridge Manager in the search results.

    • Start the wizard from the command line:

      1. Open a Command Prompt window as an administrator.

      2. Change the current directory as follows:

        cd <OBM_HOME>\bin

      3. Run the following command:

        config-server-wizard.bat

To manually start the configuration wizard, follow the steps:

  1. If this is not the first time you are starting the wizard, disable OBM.

    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss and severe integrity problems.

  2. Open a command shell as the root user.

  3. Change the current directory as follows:

    cd /opt/HP/BSM/bin

  4. Run the following command:

    ./config-server-wizard.sh.

    The configuration wizard starts.

Complete the installation wizard

When OBM is successfully installed, the installation wizard displays the Install Complete (Installation Complete) page with a summary of the installation process.

UCMDB is installed at the following location: <OBM_Home>/ucmdb

UCMDB is installed at the following location: <OBM_Home>\ucmdb

Note OBM installation wizard remains active in the background during the configuration phase, if the configuration is invoked from the post-installation wizard.

Installation wizard: Install Complete (Installation Complete) page

Click Done to conclude the installation.

Click Done to conclude the installation. The configuration wizard is automatically launched after the installation is complete. You can continue with the configuration or click Cancel and launch it manually later. For information about launching the configuration wizard manually, see the Optional. Start the configuration wizard manually section.

Complete the installation wizard

When OBM is successfully installed, the installation wizard displays the Install Complete (Installation Complete) page with a summary of the installation process.

UCMDB is installed at the following location: <OBM_Home>/ucmdb

UCMDB is installed at the following location: <OBM_Home>\ucmdb

Note OBM installation wizard remains active in the background during the configuration phase, if the configuration is invoked from the post-installation wizard.

Installation wizard: Install Complete (Installation Complete) page

Click Done to conclude the installation.

Click Done to conclude the installation. The configuration wizard is automatically launched after the installation is complete. You can continue with the configuration or click Cancel and launch it manually later. For information about launching the configuration wizard manually, see the Optional. Start the configuration wizard manually section.

Optional. Start the configuration wizard manually

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading. Ensure that the configuration wizard is run on the primary OBM data processing server before performing the steps described in this section.

If you previously quit the OBM configuration wizard (or you installed OBM silently), you can later start the configuration wizard manually.

Note The OBM configuration wizard must be used on all systems that host new OBM installationsthe host systems of the primary data processing server, additional data processing server and all gateway servers (in distributed BSMOBM deployments).

You must specify the same database and connection parameters for each OBM server, regardless of whether the servers are at the same location or they are geographically separated.

You can modify any configuration settings at a later time. To change a setting, start the configuration wizard again. Before you restart the wizard, disable OBM.

To start the configuration wizard manually, follow the steps:

  1. If this is not the first time you are starting the wizard, disable OBM.

    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss or severe integrity problems.

  2. Do one of the following:

    • Start the wizard from the operating system desktop:

      • Windows Server 2008:

        Select Start > Programs > Operations Bridge Manager > Administration > Configure Operations Bridge Manager.

      • Windows Server 2012:

        Press Ctrl + Esc and start typing Configure Operations Bridge Manager. Then click Configure Operations Bridge Manager in the search results.

    • Start the wizard from the command line:

      1. Open a Command Prompt window as an administrator.

      2. Change the current directory as follows:

        cd <OBM_HOME>\bin

      3. Run the following command:

        config-server-wizard.bat

To manually start the configuration wizard, follow the steps:

  1. If this is not the first time you are starting the wizard, disable OBM.

    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss and severe integrity problems.

  2. Open a command shell as the root user.

  3. Change the current directory as follows:

    cd /opt/HP/BSM/bin

  4. Run the following command:

    ./config-server-wizard.sh.

    The configuration wizard starts.

Optional. Migrate to a later supported version of Oracle DatabasePostgreSQLMicrosoft SQL Server

To use a later Oracle DatabasePostgreSQLMicrosoft SQL Server version that is supported by OBM 2019.05, migrate your Oracle Database dataremote PostgreSQL databasesMicrosoft SQL Server databases. For instructions on the migration, see the Oracle DatabasePostgreSQLMicrosoft SQL Server documentation.

Optional. Migrate to a later supported version of Oracle DatabasePostgreSQLMicrosoft SQL Server

To use a later Oracle DatabasePostgreSQLMicrosoft SQL Server version that is supported by OBM 2019.05, migrate your Oracle Database dataremote PostgreSQL databasesMicrosoft SQL Server databases. For instructions on the migration, see the Oracle DatabasePostgreSQLMicrosoft SQL Server documentation.

Start the upgrade

The upgrade tool uninstalls all previous OBM versions, including IPs (intermediate patches). The tool temporarily backs up part of the configuration and certificates to help you migrate them to the OBM 2019.05 version. To find out which files are backed up, see <OBMInstallationFiles>\/Update\/preUpdateBackup.txt

Note The minimal downtime process during which you switch the processes from one server to another and upgrade both data processing servers when they are inactive is currently not supported.


To avoid interruptions, close all open applications before starting the upgrade.

In a single-server OBM deployment, follow these steps:

  1. On the BSMOBM host systemnew system that will host OBM, create an empty file called ovinstallparams.ini in the same directory as the HPOMi_<VersionAndBuild>_setup.exeHPOMi_<VersionAndBuild>_setup.bin executable file, for example:

    <OBMInstallationFiles>\/Software\/HPOMi_<VersionAndBuild>_setup.exebin

    <OBMInstallationFiles>\/Software\/ovinstallparams.ini

  2. Copy the following section to the .ini file on the OBM server:

    [installer.properties]
    setup=HPOMi
    group=typical

    By default, the upgrade installs OBM 2019.05 to the C: drive. If you want OBM to be installed to a different location instead, add the following lines at the end of the .ini file:

    installDir=<SharedComponentsBinaryFilesDirectory>
    dataDir=<SharedComponentsDataDirectory>
    prodInstallDir=<OMiBinaryFilesDirectory>
    prodDataDir=<OMiDataDirectory>

    Note The first two lines apply to the shared data (shared components), and the last two lines apply to OBM.
    These are the default locations:

    installDir=C:\Program Files\HP\HP BTO Software\
    dataDir=C:\ProgramData\HP\HP BTO Software\
    prodInstallDir=C:\HPBSM\
    prodDataDir=C:\ProgramData\HP\BSM\

    The paths can contain space characters. In this case, do not enclose them with quotation marks.

  3. To invoke the upgrade tool, run the following command:

    cd <OBMInstallationFiles>

    upgrade.bat -d -silent

    cd <OBMInstallationFiles>

    ./upgrade.sh -d -silent

    The script first automatically uninstalls any previously installed patches and your previous OBM version. This may take some time.

    After your earlier OBM version is uninstalled, the upgrade process invokes the silent installation of OBM 2019.05. After the installation is complete, silent configuration is automatically done.

    Note Ensure that the DISPLAY variable is configured on the OBM host system. The silent configuration fails if it is not configured. If the silent configuration fails and you need to run the upgrade command again, you are required to run the configuration wizard manually. When running the configuration wizard manually, choose Custom configuration/upgrade followed by Upgrade database from a previous version of OBM.

  4. Follow the wizard to install the OBM 2019.05 service pack as follows:

    1. Select the preferred language for the installation wizard, and click OK.
    2. Read the introduction and click Next.
    3. Review and accept the license agreement, then click Next to continue with the installation. If you decline, the installation cannot proceed.
    4. Specify the installation type and click Next.
    5. Click Next after the product requirement checks are complete.
    6. Review the information in the Pre-Install Summary and click Install to start the installation.
    7. Click Done once the installation is complete.

      This completes OBM 2019.05 installation. The configuration wizard is not displayed as the configuration is done automatically.

    8. Optional. If you reboot the server, a Next Steps screen might be displayed. Click Configure/Upgrade OBM.
  5. After the upgrade is over, run the following command to start the services:

    /opt/HP/BSM/scripts/run_hpbsm start

    Note After the upgrade, the initial start of OBM may take a couple of hours. DO NOT stop OBM if the Initializer is in Processing state. Wait for the process to complete.

    After the upgrade is over, start the OBM services:

    • Windows Server 2008:

      Select Start > Programs > Operations Bridge Manager > Administration > Enable Operations Bridge Manager.

    • Windows Server 2012:

      Press Ctrl + Esc, start typing Enable Operations Bridge Manager, and then click Enable Operations Bridge Manager in the search results.

    Note After the upgrade, the initial start of OBM may take a couple of hours. DO NOT stop OBM during the start-up. Wait for the process to complete.

  1. Make sure that all the servicesprocesses are enabled (all servicesprocesses must be running on the primary DPS and the secondary DPS and gateways must be brought down). Depending on the OBM version, run one of the following commands to stop services on the secondary DPS and gateways:

    /opt/HP/BSM/scripts/run_hpbsm stopall (for OBM 2018.11)

    /opt/HP/BSM/scripts/run_hpbsm stop (for OBM 2018.05)

    HPBSM\bin\SupervisorStopAll (for OBM 2018.11)

    HPBSM\bin\SupervisorStop (for OBM 2018.05)

  2. Run the following command on the primary DPS:

    cd <OBMInstallationFiles>

    upgrade.bat -d-silent

    cd <OBMInstallationFiles>

    ./upgrade.sh -d-silent

    The script first automatically uninstalls any previously installed patches and your previous OBM version. This may take some time.

    After your earlier OBM version is uninstalled, the upgrade process invokes the silent installation of OBM2019.05.

  3. The configuration wizard runs silently in the background. Verify if the configuration wizard has run successfully by checking the configuration log file:

    /opt/HP/BSM/log/configserver/configserver_all.log

    The configuration wizard runs silently in the background. Verify if the configuration wizard has run successfully by checking the configuration log file:

    HPBSM\log\configserver\configserver_all.log

    Note Ensure that the DISPLAY variable is configured on the OBM host system. The silent configuration fails if it is not configured. If the silent configuration fails and you need to run the upgrade command again, you are required to run the configuration wizard manually. When running the configuration wizard manually, choose Custom configuration/upgrade followed by Upgrade database from a previous version of OBM.

  4. Start services on the primary DPS.

    /opt/HP/BSM/scripts/run_hpbsm start

    Note After the upgrade, the initial start of OBM may take a couple of hours. DO NOT stop OBM if the Initializer is in Processing state. Wait for the process to complete.

    Start services on the primary DPS:

    • Windows Server 2008:

      Select Start > Programs > Operations Bridge Manager > Administration > Enable Operations Bridge Manager.

    • Windows Server 2012:

      Press Ctrl + Esc, start typing Enable Operations Bridge Manager, and then click Enable Operations Bridge Manager in the search results.

    Note After the upgrade, the initial start of OBM may take a couple of hours. DO NOT stop OBM during the start-up. Wait for the process to complete.

  5. Perform the following steps to complete the upgrade on each gateway server:

    1. Run the following command:

      cd <OBMInstallationFiles>

      upgrade.bat -d-silent

      cd <OBMInstallationFiles>

      ./upgrade.sh -d-silent

    2. The configuration wizard runs silently in the background. Verify if the configuration wizard has run successfully and then start services.

      Run the following command to verify:

      /opt/HP/BSM/log/configserver/configserver_all.log

      \opt\HP\BSM\log\configserver\configserver_all.log

  6. Perform the following steps to complete the upgrade on each secondary DPS:

    1. Run the following command:

      cd <OBMInstallationFiles>

      upgrade.bat -d-silent

      cd <OBMInstallationFiles>

      ./upgrade.sh -d-silent

    2. The configuration wizard runs silently in the background. Verify if the configuration wizard has run successfully and then start services.

      Run the following command to verify:

      /opt/HP/BSM/log/configserver/configserver_all.log

      \opt\HP\BSM\log\configserver\configserver_all.log

Optional. Update your Data Flow Probe

If the Data Flow Probe is used for integration, you must update your existing Data Flow Probe to the newest version. For detailed instructions, see the Data Flow Probe Installation instructions.

Note If the Data Flow Probe is configured with TLS, do the following before starting the uninstallation:

  • Secure the keystore certificates.
  • Back up <DFP_install_folder>/conf/DataFlowProbe.properties as the file contains customizations that must be reapplied after the DFP update.
  1. Uninstall your previous Data Flow Probe:

    <ProbeinstallDirectory>\UninstallerData\Uninstall_Discovery_Probe

    <ProbeinstallDirectory>/UninstallerData/Uninstall_Discovery_Probe

  2. Install the new Data Flow Probe version by running the following .exe.bin file in your installation files, and following the Data Flow Probe Installation instructions:

    Caution The probe's name must be the same as for the previous Data Flow Probe. Otherwise, all integration points will stop working after the new installation.

    OBM_2019.05_DataFlowProbe\Software\Linux\UCMDB_DataFlowProbe-11.50.306.exe

    OBM_2019.05_DataFlowProbe/Software/Linux/UCMDB_DataFlowProbe-11.50.306.bin

  3. Optional. Check the WrapperProbeGw.log file. If you find any JavaLinkage errors, make sure that the following two directories include the same versions of the JAR files (*.jar):

    <ProbeinstallDirectory>\runtime\probeManager\discoveryResources\Cmdb10xAdapter

    <ProbeinstallDirectory>/runtime/probeManager/discoveryResources/Cmdb10xAdapter/

    and

    <ProbeinstallDirectory>\lib

    <ProbeinstallDirectory>/lib/

    If there are any discrepancies, copy the missing JAR files from the lib to the Cmdb10xAdapter directory.

Optional. Update your Data Flow Probe

If the Data Flow Probe is used for integration, you must update your existing Data Flow Probe to the newest version. For detailed instructions, see the Data Flow Probe Installation instructions.

Note If the Data Flow Probe is configured with TLS, do the following before starting the uninstallation:

  • Secure the keystore certificates.
  • Back up <DFP_install_folder>/conf/DataFlowProbe.properties as the file contains customizations that must be reapplied after the DFP update.
  1. Uninstall your previous Data Flow Probe:

    <ProbeinstallDirectory>\UninstallerData\Uninstall_Discovery_Probe

    <ProbeinstallDirectory>/UninstallerData/Uninstall_Discovery_Probe

  2. Install the new Data Flow Probe version by running the following .exe.bin file in your installation files, and following the Data Flow Probe Installation instructions:

    Caution The probe's name must be the same as for the previous Data Flow Probe. Otherwise, all integration points will stop working after the new installation.

    OBM_2019.05_DataFlowProbe\Software\Linux\UCMDB_DataFlowProbe-11.50.306.exe

    OBM_2019.05_DataFlowProbe/Software/Linux/UCMDB_DataFlowProbe-11.50.306.bin

  3. Optional. Check the WrapperProbeGw.log file. If you find any JavaLinkage errors, make sure that the following two directories include the same versions of the JAR files (*.jar):

    <ProbeinstallDirectory>\runtime\probeManager\discoveryResources\Cmdb10xAdapter

    <ProbeinstallDirectory>/runtime/probeManager/discoveryResources/Cmdb10xAdapter/

    and

    <ProbeinstallDirectory>\lib

    <ProbeinstallDirectory>/lib/

    If there are any discrepancies, copy the missing JAR files from the lib to the Cmdb10xAdapter directory.

Configure event forwarding in BSMthe original OBM environment

Configure event forwarding in BSMthe original OBM environment

Replicate the database schemasdatabasesCopy the database backup image

The Side-by-Side - Database Preparation page instructs you to replicate (back up) the database schemasdatabases manually before continuing.

Replicate the following original OMi database schemas databases onto the new OBM database host system:

  • Management

  • Event

  • RTSM

  • RTSM History

The database schemadatabase replicas will be used in the staging environment, they will be upgraded, and finally —except for the RTSM History database—configured as your OBM2019.05 databases. Other BSM database schemasdatabases do not require replication, as they are not used in OBM and therefore not migrated.

Tip Take note of the replication start time. You will need it later during the upgrade process.

Copy the following file, which includes the database schema backup image, from ithe original OMi database host system to a location on the new OBM database host system:

%OvDataDir%\backup\OMi10cfg-backup.zip

/var/opt/OV/backup/OMi10cfg-backup.zip

The included database schema replicas will be used in the staging environment, they will be upgraded, and finally configured as your OBM 2019.05 databases.

Before you proceed to the next step, make sure the database schemadatabase replicas are available on the new OBM database host system. Click Next to continue.

Replicate the database schemasdatabasesCopy the database backup image

The Side-by-Side - Database Preparation page instructs you to replicate (back up) the database schemasdatabases manually before continuing.

Replicate the following original OMi database schemas databases onto the new OBM database host system:

  • Management

  • Event

  • RTSM

  • RTSM History

The database schemadatabase replicas will be used in the staging environment, they will be upgraded, and finally —except for the RTSM History database—configured as your OBM2019.05 databases. Other BSM database schemasdatabases do not require replication, as they are not used in OBM and therefore not migrated.

Tip Take note of the replication start time. You will need it later during the upgrade process.

Copy the following file, which includes the database schema backup image, from ithe original OMi database host system to a location on the new OBM database host system:

%OvDataDir%\backup\OMi10cfg-backup.zip

/var/opt/OV/backup/OMi10cfg-backup.zip

The included database schema replicas will be used in the staging environment, they will be upgraded, and finally configured as your OBM 2019.05 databases.

Before you proceed to the next step, make sure the database schemadatabase replicas are available on the new OBM database host system. Click Next to continue.

Choose configuration options

In the Configuration Options page, click Custom configuration/upgrade. This option displays all wizard pages, enabling you to specify custom values for all OBM configuration settings or upgrade. Then click Next to continue.

Upgrade wizard: Database Connection page

Choose configuration options

In the Configuration Options page, click Custom configuration/upgrade. This option displays all wizard pages, enabling you to specify custom values for all OBM configuration settings or upgrade. Then click Next to continue.

Upgrade wizard: Database Connection page

Configure the database settings

Select Upgrade database from a previous version of OBM on the Database Settings page to start the upgrade on the primary data processing server. You must provide credentials for the administrative access to the Microsoft SQL Server databaseOracle Database instancePostgreSQL database.

When upgrading the secondary data processing server, you must select the Connect to an existing database or user schema option.

Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page

Note If you are upgrading from OMi 10.0x that was deployed as part of Operations Manager i Virtual Appliance, click Advanced settings, and then change the RTSM database name from rtsm to cmdb.

Click Next to continue.

Select Upgrade database from a previous version of OBM on the Database Settings page to start the upgrade. You must provide credentials for the administrative access to the Microsoft SQL Server databaseOracle Database instancePostgreSQL database.

Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page

Note If you are upgrading from OMi 10.0x that was deployed as part of Operations Manager i Virtual Appliance, click Advanced settings, and then change the RTSM database name from rtsm to cmdb.

Click Next to continue.

Configure the database settings

Select Upgrade database from a previous version of OBM on the Database Settings page to start the upgrade on the primary data processing server. You must provide credentials for the administrative access to the Microsoft SQL Server databaseOracle Database instancePostgreSQL database.

When upgrading the secondary data processing server, you must select the Connect to an existing database or user schema option.

Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page

Note If you are upgrading from OMi 10.0x that was deployed as part of Operations Manager i Virtual Appliance, click Advanced settings, and then change the RTSM database name from rtsm to cmdb.

Click Next to continue.

Select Upgrade database from a previous version of OBM on the Database Settings page to start the upgrade. You must provide credentials for the administrative access to the Microsoft SQL Server databaseOracle Database instancePostgreSQL database.

Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page
Upgrade wizard: Database Connection page

Note If you are upgrading from OMi 10.0x that was deployed as part of Operations Manager i Virtual Appliance, click Advanced settings, and then change the RTSM database name from rtsm to cmdb.

Click Next to continue.

Configure the TLS setup

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading.

The TLS Setup page enables you to configure OBM to accept only secure connections to its web server and the JMX consoles.

If you do not want to use HTTPS (not recommended), clear the Enable HTTPS option.

When upgrading from OMi 10.12 (latest IP) or 10.6x to OBM 2019.05, the following options are available to configure your TLS setup:

  • Enable TLS by following the next steps. Note that you have to reupload the certificates that you used for your former BSM TLS setup.
  • Disable TLS by clearing the Enable HTTPS option (not recommended).

Note Your TLS setup should be consistent for every server.

Configuration wizard: TLS Setup page

If your company uses a certification authority (CA) that can generate certificates for OBM, click the Upload certificates option. Alternatively, click OBM-generated certificates to make OBM generate the certificates required for the configuration.

Note For maximum security, we recommend to use certificates that were issued by the certification authority of your company.

If you choose to use OBM-generated certificates, make sure to establish trust in the web browser from which you will log on to OBM. For instructions on how to do that, see the "Establishing Trust in the Browser" section in the "Using TLS in OBM" chapter of the OBM Administration Guide.

Configure the TLS setup

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading.

The TLS Setup page enables you to configure OBM to accept only secure connections to its web server and the JMX consoles.

If you do not want to use HTTPS (not recommended), clear the Enable HTTPS option.

When upgrading from OMi 10.12 (latest IP) or 10.6x to OBM 2019.05, the following options are available to configure your TLS setup:

  • Enable TLS by following the next steps. Note that you have to reupload the certificates that you used for your former BSM TLS setup.
  • Disable TLS by clearing the Enable HTTPS option (not recommended).

Note Your TLS setup should be consistent for every server.

Configuration wizard: TLS Setup page

If your company uses a certification authority (CA) that can generate certificates for OBM, click the Upload certificates option. Alternatively, click OBM-generated certificates to make OBM generate the certificates required for the configuration.

Note For maximum security, we recommend to use certificates that were issued by the certification authority of your company.

If you choose to use OBM-generated certificates, make sure to establish trust in the web browser from which you will log on to OBM. For instructions on how to do that, see the "Establishing Trust in the Browser" section in the "Using TLS in OBM" chapter of the OBM Administration Guide.

Configure client certificate authentication

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading.

The Client Certificate Authentication page enables you to configure OBM to require a client certificate when users log on to OBM or when web services connect to OBM. Depending on the deployment type, you can configure OBM to authenticate the client on the OBM web server or, if available, on the load balancer.

Caution Do not enable client certificate authentication if you are configuring OBM for the first time. Before enabling client-certificate authentication, OBM must be already configured and the superuser must exist.

Configuration wizard: Client Certificate Authentication page

Configure client certificate authentication

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading.

The Client Certificate Authentication page enables you to configure OBM to require a client certificate when users log on to OBM or when web services connect to OBM. Depending on the deployment type, you can configure OBM to authenticate the client on the OBM web server or, if available, on the load balancer.

Caution Do not enable client certificate authentication if you are configuring OBM for the first time. Before enabling client-certificate authentication, OBM must be already configured and the superuser must exist.

Configuration wizard: Client Certificate Authentication page

Configure general OBM connection settings

The Connection (Connection Settings) page informs you that Apache HTTP Server will be used as the web server for OBM. Additionally, you can configure the URL that users use to access OBM.

In the Connection (Connection Settings) page, you can choose the web server to be used by OBM. Additionally, you can configure the URL that users use to access OBM.

Note The configuration wizard displays the Connection (Connection Settings) page only during configuration of an single-server OBM installation or an OBM gateway server. The wizard skips it during configuration of an OBM data processing server.

Upgrade wizard: Connection Settings page
Upgrade wizard: Connection Settings page

Under Web server, enter the port for the web server that you want to use with your OBM deployment.

OBM installs Apache HTTP Server on all gateway servers during the installation. By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server. If the default port is already in use, specify a different port.

Web server. In Linux environments, OBM uses Apache HTTP Server.

Apache HTTP Server. OBM installs Apache HTTP Server on the gateway server during the installation.

By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server. If the default port is already in use, specify a different port.

OBM URL. By default, users access OBM through the fully qualified domain name and web server port of the single or gateway server. If the default port is changed, update the port number in the OBM URL text box, for example, https://obmweb.company.com:8000.

If you have a load balancer that is used to access the OBM site, enter the fully qualified domain name and port of the load balancer.

Click Next.

Configure general OBM connection settings

The Connection (Connection Settings) page informs you that Apache HTTP Server will be used as the web server for OBM. Additionally, you can configure the URL that users use to access OBM.

In the Connection (Connection Settings) page, you can choose the web server to be used by OBM. Additionally, you can configure the URL that users use to access OBM.

Note The configuration wizard displays the Connection (Connection Settings) page only during configuration of an single-server OBM installation or an OBM gateway server. The wizard skips it during configuration of an OBM data processing server.

Upgrade wizard: Connection Settings page
Upgrade wizard: Connection Settings page

Under Web server, enter the port for the web server that you want to use with your OBM deployment.

OBM installs Apache HTTP Server on all gateway servers during the installation. By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server. If the default port is already in use, specify a different port.

Web server. In Linux environments, OBM uses Apache HTTP Server.

Apache HTTP Server. OBM installs Apache HTTP Server on the gateway server during the installation.

By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server. If the default port is already in use, specify a different port.

OBM URL. By default, users access OBM through the fully qualified domain name and web server port of the single or gateway server. If the default port is changed, update the port number in the OBM URL text box, for example, https://obmweb.company.com:8000.

If you have a load balancer that is used to access the OBM site, enter the fully qualified domain name and port of the load balancer.

Click Next.

Configure the license

In the License page, you can configure the license that OBM uses.

Upgrade wizard: License page

Depending on your recent actions, you have different options:

  • If the wizard is running for the first time, you can choose to use the evaluation license or to upload your new license to the server.

  • If this is not the first time the wizard is running, you can select to skip this step or upload additional licenses.

To update your licenses after the upgrade, make the necessary changes in the License Management page of the OBM user interface

Note The license file has the .dat file name extension and must reside at a local or network location accessible to the host system where the wizard is running.

Click Next.

Configure the license

In the License page, you can configure the license that OBM uses.

Upgrade wizard: License page

Depending on your recent actions, you have different options:

  • If the wizard is running for the first time, you can choose to use the evaluation license or to upload your new license to the server.

  • If this is not the first time the wizard is running, you can select to skip this step or upload additional licenses.

To update your licenses after the upgrade, make the necessary changes in the License Management page of the OBM user interface

Note The license file has the .dat file name extension and must reside at a local or network location accessible to the host system where the wizard is running.

Click Next.

Configure the logon settings

In the Login Settings page, you can set the passwords for the OBM users.

OBM supports central user management and corporate password policies, it can communicate with the directory services by using LDAP. We recommend such configuration to enforce compliance of OBM user passwords with the respective security policy in your company. To configure the LDAP integration, navigate to Administration > Users > Authentication Management in the OBM user interface.

LDAP authentication of all users is possible only when the mixed mode authentication is disabled in the OBM LDAP infrastructure settings. For instructions on how to adjust this setting, see the "LDAP Authentication and Mappings" section in the OBM Administration Guide.

Upgrade wizard: Update Environment - Login Settings page

To configure OBM passwords, specify the following options:

  • Administrator password, Confirm. Type the password of the OBM administrator (user name: admin) for the OBM user interface. This password is required to log on to OBM, and can be changed in the OBM user interface at a later time.

  • JMX password, Confirm. Type the password to be used by the OBM administrator for all OBM JMX consoles (user name: admin) and for the RTSM JMX console (user name: sysadmin).

    Note The JMX password is valid on all host systems that constitute your OBM environment.

Click Next.

Configure the logon settings

In the Login Settings page, you can set the passwords for the OBM users.

OBM supports central user management and corporate password policies, it can communicate with the directory services by using LDAP. We recommend such configuration to enforce compliance of OBM user passwords with the respective security policy in your company. To configure the LDAP integration, navigate to Administration > Users > Authentication Management in the OBM user interface.

LDAP authentication of all users is possible only when the mixed mode authentication is disabled in the OBM LDAP infrastructure settings. For instructions on how to adjust this setting, see the "LDAP Authentication and Mappings" section in the OBM Administration Guide.

Upgrade wizard: Update Environment - Login Settings page

To configure OBM passwords, specify the following options:

  • Administrator password, Confirm. Type the password of the OBM administrator (user name: admin) for the OBM user interface. This password is required to log on to OBM, and can be changed in the OBM user interface at a later time.

  • JMX password, Confirm. Type the password to be used by the OBM administrator for all OBM JMX consoles (user name: admin) and for the RTSM JMX console (user name: sysadmin).

    Note The JMX password is valid on all host systems that constitute your OBM environment.

Click Next.

Configure the server deployment

In the Server Deployment page, you can define the expected size of the environment monitored by OBM.

Upgrade wizard: Server Deployment page

Note When configuring a gateway server, modules and nodes cannot be configured because the selections are taken from the data processing server.

  1. Select the Number of monitored nodes that send events to OBM. This includes all nodes that are present as CIs and that send events to OBM (for example, nodes connected to Operations Manager (OM), nodes directly connected to OBM, and target connectors).

  2. Optional. Click Advanced to adjust the maximum memory that the Java Virtual Machine (JVM) allocates to the OBM processes. To change the allocated memory, click Manual override and type the new values in the text boxes.

  3. Click Next.

Configure the server deployment

In the Server Deployment page, you can define the expected size of the environment monitored by OBM.

Upgrade wizard: Server Deployment page

Note When configuring a gateway server, modules and nodes cannot be configured because the selections are taken from the data processing server.

  1. Select the Number of monitored nodes that send events to OBM. This includes all nodes that are present as CIs and that send events to OBM (for example, nodes connected to Operations Manager (OM), nodes directly connected to OBM, and target connectors).

  2. Optional. Click Advanced to adjust the maximum memory that the Java Virtual Machine (JVM) allocates to the OBM processes. To change the allocated memory, click Manual override and type the new values in the text boxes.

  3. Click Next.

Deploy management packs

In the Management Packs page, you can select the OBM Management Packs to install in your OBM environment. Dependencies between them are resolved automatically. You can choose not to install dependent management packs. However, if you do so, the functional scope of the selected management packs might reduce.

Upgrade wizard: Management Packs page

Management packs provide add-on content on top of OBM. They deliver automatic and end-to-end monitoring solutions of infrastructure and applications. Management packs enable users to monitor, detect, troubleshoot, and remediate issues in the IT domain. They increase the productivity of users by optimizing and automating various tasks, and reduce the mean time to resolve (MTTR) incidents.

Management packs discover application domains and proactively monitor the domains for availability and performance issues. They include, for example, management templates, aspects, policy templates, performances graphs, troubleshooting tools, auto remediation flows, and topology-based event correlation (TBEC) rules.

To install management packs after the first configuration, start the configuration wizard again and select the management packs you want to install. With a distributed deployment, start the configuration wizard first on the data processing servers and subsequently on all gateway servers. Note though that the Management Packs page does not appear during the gateway server configuration.

Tip We recommend to disable OBM before starting the configuration wizard, and to enable it after the configuration:

  • Windows Server 2008:

    Select Start > Programs > Operations Bridge Manager > Administration > Disable Operations Bridge Manager.

  • Windows Server 2012:

    Press Ctrl + Esc, start typing Disable Operations Bridge Manager, and then click Disable Operations Bridge Manager in the search results.

Run the following command:

/opt/HP/BSM/scripts/run_hpbsm stop

Alternatively, use the opr-mp-installer command-line utility to install management packs without having to disable OBM. For more information about opr-mp-installer, see the OBM Administration Guide.

To install management packs after the upgrade, start the configuration wizard again or use the opr-mp-installer command-line utility. For more information about opr-mp-installer, see the OBM Administration Guide.

Once installed, management packs cannot be removed, even though their entries appear in the Management Packs page.

Note To update a management pack to a later version than the one included with OBM, download its installation package from the ITOM Marketplace and install the management pack manually. You can also install additional management packs that are not bundled with OBM. However, such additions are not reflected in the OBM configuration wizard.

For more information about the management packs, see the management pack documentation.

Select the management packs that you want to install in your OBM environment and then click Next.

Deploy management packs

In the Management Packs page, you can select the OBM Management Packs to install in your OBM environment. Dependencies between them are resolved automatically. You can choose not to install dependent management packs. However, if you do so, the functional scope of the selected management packs might reduce.

Upgrade wizard: Management Packs page

Management packs provide add-on content on top of OBM. They deliver automatic and end-to-end monitoring solutions of infrastructure and applications. Management packs enable users to monitor, detect, troubleshoot, and remediate issues in the IT domain. They increase the productivity of users by optimizing and automating various tasks, and reduce the mean time to resolve (MTTR) incidents.

Management packs discover application domains and proactively monitor the domains for availability and performance issues. They include, for example, management templates, aspects, policy templates, performances graphs, troubleshooting tools, auto remediation flows, and topology-based event correlation (TBEC) rules.

To install management packs after the first configuration, start the configuration wizard again and select the management packs you want to install. With a distributed deployment, start the configuration wizard first on the data processing servers and subsequently on all gateway servers. Note though that the Management Packs page does not appear during the gateway server configuration.

Tip We recommend to disable OBM before starting the configuration wizard, and to enable it after the configuration:

  • Windows Server 2008:

    Select Start > Programs > Operations Bridge Manager > Administration > Disable Operations Bridge Manager.

  • Windows Server 2012:

    Press Ctrl + Esc, start typing Disable Operations Bridge Manager, and then click Disable Operations Bridge Manager in the search results.

Run the following command:

/opt/HP/BSM/scripts/run_hpbsm stop

Alternatively, use the opr-mp-installer command-line utility to install management packs without having to disable OBM. For more information about opr-mp-installer, see the OBM Administration Guide.

To install management packs after the upgrade, start the configuration wizard again or use the opr-mp-installer command-line utility. For more information about opr-mp-installer, see the OBM Administration Guide.

Once installed, management packs cannot be removed, even though their entries appear in the Management Packs page.

Note To update a management pack to a later version than the one included with OBM, download its installation package from the ITOM Marketplace and install the management pack manually. You can also install additional management packs that are not bundled with OBM. However, such additions are not reflected in the OBM configuration wizard.

For more information about the management packs, see the management pack documentation.

Select the management packs that you want to install in your OBM environment and then click Next.

Apply the OBM 2019.05 configuration

The Ready to Configure page displays the current settings. Check whether your selections are correct. To change a setting, click Edit.

Configuration wizard: Ready to Configure (Confirmaton) page

When you are ready, click Next to initiate the configuration actions.

Review the summary and conclude the upgrade

In the Configuration Summary page, read the summary of the OBM upgrade process.

Configuration wizard: Configuration Summary page

Click Finish to close the configuration wizard.

Review the summary and conclude the upgrade

In the Configuration Summary page, read the summary of the OBM upgrade process.

Configuration wizard: Configuration Summary page

Click Finish to close the configuration wizard.

Optional. Start the configuration wizard manually

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading. Ensure that the configuration wizard is run on the primary OBM data processing server before performing the steps described in this section.

If you previously quit the OBM configuration wizard (or you installed OBM silently), you can later start the configuration wizard manually.

Note The OBM configuration wizard must be used on all systems that host new OBM installationsthe host systems of the primary data processing server, additional data processing server and all gateway servers (in distributed BSMOBM deployments).

You must specify the same database and connection parameters for each OBM server, regardless of whether the servers are at the same location or they are geographically separated.

You can modify any configuration settings at a later time. To change a setting, start the configuration wizard again. Before you restart the wizard, disable OBM.

To start the configuration wizard manually, follow the steps:

  1. If this is not the first time you are starting the wizard, disable OBM.

    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss or severe integrity problems.

  2. Do one of the following:

    • Start the wizard from the operating system desktop:

      • Windows Server 2008:

        Select Start > Programs > Operations Bridge Manager > Administration > Configure Operations Bridge Manager.

      • Windows Server 2012:

        Press Ctrl + Esc and start typing Configure Operations Bridge Manager. Then click Configure Operations Bridge Manager in the search results.

    • Start the wizard from the command line:

      1. Open a Command Prompt window as an administrator.

      2. Change the current directory as follows:

        cd <OBM_HOME>\bin

      3. Run the following command:

        config-server-wizard.bat

To manually start the configuration wizard, follow the steps:

  1. If this is not the first time you are starting the wizard, disable OBM.

    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss and severe integrity problems.

  2. Open a command shell as the root user.

  3. Change the current directory as follows:

    cd /opt/HP/BSM/bin

  4. Run the following command:

    ./config-server-wizard.sh.

    The configuration wizard starts.

Optional. Generate the database creation scripts

During the configuration, OBM can do one of the following:

  • Automatically set up new databases for you

  • Connect to the existing databases that were created manually in advance.

    If you not have the required permissions in the remote database management system, you might want to ask the database administrator for assistance with database creation.

OBM requires the following databases:

  • Management. For storage of system-wide and management-related metadata.

  • RTSM (Run-time Service Model). For storage of configuration information that is gathered from various Micro Focus and third-party applications and tools.

  • Event. For storage of events and related data, such as annotations, as well as for storage of configuration data, such as event correlation rules.

After the OBM installation, but before the configuration, generate the scripts on the gateway server to create the required objects for populating these databases. You (or the database administrator) must create the databases and then run the scripts in the database management system to create the required objects.

For details on how to install and configure a database management system, and to populate the databases with the required objects, follow the steps described in the OBM Database Guide.

Choose general configuration options

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading.

After the configuration wizard starts, the Configuration Options page is displayed.

Configuration wizard: Configuration Options page

In the Configuration Options page, click Custom configuration. This option displays all wizard pages, enabling you to specify custom values for all OBM configuration settings. Then click Next to continue.

In the Configuration Options page, click Express configuration with default values to configure OBM by using default settings. Specify a global password that will be used for the OBM web console, the JMX console, and database users, and then click Next.

The express option configures OBM by using the following default settings:

  • Embedded Apache HTTP Server

  • Embedded PostgreSQL database

  • HTTPS for the OBM web server and JMX console (with OBM-generated certificates)

  • OBM Management Pack for Infrastructure installed

  • A single password that you specify for the OBM administrator, OBM JMX console, and database users. To change the default password for each user later, see Change passwords.

We recommend the express deployment for environments where you want to demonstrate or evaluate OBM or for small environments with less than 2,000 nodes.

Chose general configuration options

After the configuration wizard starts, the Configuration Options page displays.

Configuration wizard: Configuration Options page

The express option configures OBM using the following default settings:

  • Embedded Apache HTTP Server

  • Embedded PostgreSQL database

  • HTTPS for the OBM web server and JMX console (with OBM-generated certificates)

  • OBM Management Pack for Infrastructure installed

  • A single password that you specify for the OBM administrator, OBM JMX console, and database users. To change the default password for each user later, see Change passwords.

We recommend the express deployment for environments where you want to demonstrate or evaluate OBM or for small environments with less than 2,000 nodes.

In the Configuration Options page, click Express configuration with default values to configure OBM using default settings. Specify a global password that will be used for the OBM web console, the JMX console, and database users, and then click Next.

Choose general configuration options

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading.

After the configuration wizard starts, the Configuration Options page displays.

Configuration wizard: Configuration Options page
Configuration wizard: Configuration Options page

In the Configuration Options page, click Custom configuration/Upgrade. This option displays all wizard pages, enabling you to specify custom values for all OBM configuration settings. Then click Next to continue.

By default, the OBM processes run by using the root account. You can configure OBM to run by using a different user account.

  1. Create a non-root user account on all OBM servers, for example, by using the operating system's useradd or adduser command.

    Configure the maximum number of processes for this user account by adding the following line to the existing xx-nproc.conf file in the /etc/security/limits.d directory (where xx is a number specific to the Linux version).

    <UserName> soft nproc unlimited

    Replace <UserName> with the non-root user account.

  2. In the Configuration Options page, click Run OBM processes as non-root user to configure OBM to run by using a different user account.

  3. Type the User name of the non-root user account you created earlier.

  4. Click Next.

Configure the database settings

In the Database Settings page, you can select the relational database management system you want to use with OBM, create new database schemas, or connect to existing ones.

Configuration wizard: Database Settings page

Note When entering database parameters, use only alphanumeric characters.

  1. Choose whether you want to connect OBM to already existing database schemas or if you want OBM to create new database schemas for you:

    • Connect to an existing database or user schema. You generally use this option in the following scenarios:

      • When connecting to database schemas you manually created directly on the Oracle Database server.

      • When installing OBM in a distributed environment and running the configuration wizard on servers subsequent to the first server. In this case, you should have run the wizard on the data processing server first and on the gateway servers later.

    • Create a new database or user schema. Use this option when you want OBM to create new database schemas for you on the Oracle Database server.

  2. Select Oracle Server.

  3. In the Host field, type the FQDN of the system where Oracle Database is installed.

    Caution There is a 26-character limit for the Host field while running the configuration wizard. If using a hostname without a domain name is not appropriate in your environment, perform one of these workarounds:

    • Use the IP address instead of the hostname in the Host field.

    • Map the hostname to the IP address in the hosts file. Use the hostname you mapped in the Host field.

  4. The Port field automatically displays the Oracle Database listener default port 1521.

  5. In the SID field, type the Oracle system identifier (SID) that uniquely identifies the Oracle Database instance being used by OBM.

  6. Optional. Click Use TLS to encrypt the communication with Oracle Database.

    The Oracle Database server must be running with TLS communication enabled and it must provide a certificate for use by OBM.

  7. If you are connecting to an existing database, specify the password of the database schemas.

  8. If you are creating new database schemas, specify the following:

    • Password of the database schemas.

    • Name and password of a user with administrative permissions on Oracle Database server (for example, a System user).

    • Tablespaces for every schema:

      • Default tablespace: Name of the dedicated default tablespace you created for the user schema.

      • Temporary tablespace: Name of the temporary tablespace you assigned to the user schema. The default Oracle Database temporary tablespace is temp.

  9. In the SID field, type the Oracle system identifier (SID) that uniquely identifies the Oracle Database instance being used by OBM.

  10. OBM requires the following database schemas:

    • Management. For storage of system-wide and management-related metadata.

    • RTSM (Run-time Service Model). For storage of configuration information that is gathered from various Micro Focus and third-party applications and tools.

    • Event. For storage of events and related data, such as annotations, as well as for storage of configuration data, such as event correlation rules.

    Type a name for each database schema. The names must be unique even when the databases reside on different servers.

    Distributed deployment: You connect to the database schemas that you created during the installation of the first data processing server. After you have connected to the Management database, by specifying the same connection parameters that you set during the installation of the first server, the connection parameters for the other database schemas appear by default. Not all database schemas appear when running on the gateway server.

  11. Click Next.

Configure the database settings

In the Database Settings page, you can select the relational database management system you want to use with OBM, create new databases, or connect to existing ones.

Configuration wizard: Database Settings page

Note When entering database parameters, use only alphanumeric characters.

  1. Choose whether you want to connect OBM to an already existing database or if you want OBM to create a new database for you:

    • Connect to an existing database or user schema. You generally use this option in the following scenarios:

      • When connecting to a database you manually created directly on the Microsoft SQL Server system.

      • When installing OBM in a distributed environment and running the utility on servers subsequent to the first server. In this case, you should have run the wizard on the data processing server first and on the gateway servers later.

    • Create a new database or user schema. Use this option when you want OBM to create new databases for you on the Microsoft SQL Server system.

  2. Select SQL Server.

  3. In the Host field, type the FQDN of the system where Microsoft SQL Server is installed. If you are connecting to a non-default Microsoft SQL Server instance in the dynamic mode, enter the following: <FQDN>\<InstanceName>.

    If you use a Microsoft SQL Server AlwaysOn Availability Group, enter the FQDN of the Availability Group Listener.

    If you use a Failover Cluster, enter the cluster server name.

    Caution There is a 26-character limit for the Host field while running the configuration wizard. If using a hostname without a domain name is not appropriate in your environment, perform one of these workarounds:

    • Use the IP address instead of the hostname in the Host field.

    • Map the hostname to the IP address in the hosts file. Use the hostname you mapped in the Host field.

  4. The Port field automatically displays the Microsoft SQL Server’s TCP/IP default port 1433. Change the port number if one of the following applies:

    • If you connect to a named instance in the static mode, enter the port number.

    • If you connect to a named instance in the dynamic mode, change the port number to 1434. This port can dynamically listen to the correct database port.

  5. Choose the Authentication type you want to use for connecting to the Microsoft SQL Server database:

    • Windows. (on Microsoft Windows systems only) You can create and connect to a database using Windows operating system authentication instead of Microsoft SQL Server authentication. To do so, first ensure that the Windows user account running the OBM service has the necessary permissions to access the Microsoft SQL Server database. For information on adding a Windows user account to Microsoft SQL Server, see "Using Windows Authentication to Access Microsoft SQL Server Databases" in the OBM Database Guide.

      In Linux environments, Windows authentication is not supported.

    • SQL Server. The user name and password of a user with administrative rights on Microsoft SQL Server. A password must be supplied.

      For security reasons, we recommend not to use the default sa user.

  6. Optional. Click Use TLS to encrypt the communication with Microsoft SQL Server.

    The Microsoft SQL Server must be running with TLS communication enabled and it must provide a certificate for use by OBM.

  7. If you selected the option Use TLS, import the certificate of the database server or of the certificate authority that issued the database server certificates. Select one of the two options:

    • Connect and import from server

      Click Retrieve Certificate to import the certificate from the server.

    • Import from file

      Specify the path or click Browse to browse for the certificate file.

    Click Test Connection to test the connection using the imported certificate.

    Click Next.

  8. OBM requires the following databases:

    • Management. For storage of system-wide and management-related metadata.

    • RTSM (Run-time Service Model). For storage of configuration information that is gathered from various Micro Focus and third-party applications and tools.

    • Event. For storage of events and related data, such as annotations, as well as for storage of configuration data, such as event correlation rules.

    Type a name for each database schema. The names must be unique even when the databases reside on different servers.

    Distributed deployment: You connect to the databases that you created during the installation of the first data processing server. After you have connected to the Management database, by specifying the same connection parameters that you set during the installation of the first server, the connection parameters for the other databases appear by default. Not all databases appear when running on the gateway server.

  9. Click Next.

Configure the database settings

In the Database Settings page, you can select the relational database management system you want to use with OBM, create new database schemas, or connect to existing ones.

Configuration wizard: Database Settings page

Note When entering database parameters, use only alphanumeric characters.

  1. Choose whether you want to connect OBM to already existing database schemas or if you want OBM to create new database schemas for you:

    • Connect to existing. You generally use the Connect to existing option in the following scenarios:

      • When connecting to database schemas you manually created directly on the PostgreSQL server.

      • When installing OBM in a distributed environment and running the utility on servers subsequent to the first server. In this case, you should have run the wizard on the data processing server first and on the gateway servers later.

    • Create new. Use this option when you want OBM to create new database schemas for you on the PostgreSQL server.

  2. Select Postgres.

  3. In the Host field, type the FQDN of the system where PostgreSQL is installed.

    Caution There is a 26-character limit for the Host field while running the configuration wizard. If using a hostname without a domain name is not appropriate in your environment, perform one of these workarounds:

    • Use the IP address instead of the hostname in the Host field.

    • Map the hostname to the IP address in the hosts file. Use the hostname you mapped in the Host field.

  4. The Port field automatically displays the PostgreSQL default port 5432.

  5. Optional. Click Use TLS to encrypt the communication with PostgreSQL.

    The PostgreSQL server must be running with TLS communication enabled and it must provide a certificate for use by OBM. For details on configuring PostgreSQL for TLS, see the PostgreSQL documentation.

  6. If you are connecting to existing database schemas, specify the user name and password of the database schemas.

  7. If you are creating new database schemas, specify the following:

    • User name and password of the database schemas.

    • User name and password of an OBM administrative user to access the PostgreSQL database.

  8. OBM requires the following database schemas:

    • Management. For storage of system-wide and management-related metadata.

    • RTSM (Run-time Service Model). For storage of configuration information that is gathered from various Micro Focus and third-party applications and tools.

    • Event. For storage of events and related data, such as annotations, as well as for storage of configuration data, such as event correlation rules.

    Type a name for each database schema. The names must be unique even when the databases reside on different servers.

    Distributed deployment: You connect to the database schemas that you created during the installation of the first data processing server. After you have connected to the Management database, by specifying the same connection parameters that you set during the installation of the first server, the connection parameters for the other databases appear by default. Not all databases appear when running on the gateway server.

  9. Click Next.

Configure the database settings

In the Database Settings page, you can select the relational database management system you want to use with OBM, create new database instances, or connect to existing ones.

Configuration wizard: Database Settings page

The embedded PostgreSQL database runs on the data processing server in distributed deployments:

  • Data processing server configuration. When configuring the embedded PostgreSQL database on the data processing server, select Embedded Postgres and specify the password of an OBM administrative user to access the PostgreSQL database.

  • Gateway server configuration. When configuring a gateway server, select Embedded Postgres again, enter the name of the data processing server in the Host field, and specify the password of the OBM administrative user with access to the PostgreSQL database.

To configure the embedded PostgreSQL database on your single-server installation, select Embedded Postgres and specify the password of an OBM administrative user to access the PostgreSQL database. Then click Next to continue.

Configure the TLS setup

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading.

The TLS Setup page enables you to configure OBM to accept only secure connections to its web server and the JMX consoles.

If you do not want to use HTTPS (not recommended), clear the Enable HTTPS option.

When upgrading from OMi 10.12 (latest IP) or 10.6x to OBM 2019.05, the following options are available to configure your TLS setup:

  • Enable TLS by following the next steps. Note that you have to reupload the certificates that you used for your former BSM TLS setup.
  • Disable TLS by clearing the Enable HTTPS option (not recommended).

Note Your TLS setup should be consistent for every server.

Configuration wizard: TLS Setup page

If your company uses a certification authority (CA) that can generate certificates for OBM, click the Upload certificates option. Alternatively, click OBM-generated certificates to make OBM generate the certificates required for the configuration.

Note For maximum security, we recommend to use certificates that were issued by the certification authority of your company.

If you choose to use OBM-generated certificates, make sure to establish trust in the web browser from which you will log on to OBM. For instructions on how to do that, see the "Establishing Trust in the Browser" section in the "Using TLS in OBM" chapter of the OBM Administration Guide.

Configure client certificate authentication

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading.

The Client Certificate Authentication page enables you to configure OBM to require a client certificate when users log on to OBM or when web services connect to OBM. Depending on the deployment type, you can configure OBM to authenticate the client on the OBM web server or, if available, on the load balancer.

Caution Do not enable client certificate authentication if you are configuring OBM for the first time. Before enabling client-certificate authentication, OBM must be already configured and the superuser must exist.

Configuration wizard: Client Certificate Authentication page

Configure general OBM connection settings

Caution This section is applicable only to the secondary OBM data processing server (optional) and each OBM gateway server that you are upgrading.

In the Connection Settings page, you can configure the URL that users use to access OBM.

Note The configuration wizard displays the Connection Settings page only during configuration of a single-server or gateway server. The page is not shown during configuration of a data processing server.

Configuration wizard: Connection Settings page

Do the following:

  1. Under Web server, enter the port for the web server that you want to use with your OBM deployment.

    OBM installs Apache HTTP Server on all gateway servers during the installation. By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server. If the default port is already in use, specify a different port.

    Web server. In Linux environments, OBM uses Apache HTTP Server.

    Apache HTTP Server. OBM installs Apache HTTP Server on the gateway server during the installation.

    By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server. If the default port is already in use, specify a different port.

  2. Under OBM URL, update the port number in the OBM URL text box if the default web server port is changed. An example of the updated URL is https://obmweb.company.com:8000update the value of the URL text box with the fully qualified domain name and the port number of the load balancer.

    Note You cannot change the OBM URL in the configuration wizard after the initial configuration. Instead, change the setting Default Virtual Gateway Server for Data Collectors URL in Infrastructure Settings > Foundations > Platform Administration.

  3. Click Next.