Operations Bridge Manager

For Windows® and Linux operating systems

Software Version: 2020.05

Customized output from:

Operations Bridge Manager 2020.05 Installation and Upgrade Guide

Document Release Date: August 2020

Software Release Date: May 2020

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

Updated on August 19, 2020

About this guide

Welcome to the Operations Bridge Manager 2020.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
Upgrade OBM
Uninstall OBM

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 OBM from the following versions to OBM 2020.05:

  • 10.12 IP6
  • 10.63 IP4
  • 2018.05
  • 2018.11
  • 2019.05 IP1
  • 2019.11

If you want to upgrade from a prior version, you must first upgrade to any version listed above then follow the steps to upgrade to OBM 2020.05.

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

The OBM upgrade runs in silent mode by default. Make sure to select the option Silent deployment in the Select additional options section. To upgrade using the GUI, select the option GUI deployment in the Select additional options section.

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 upgrade

In-place upgrade refers to installing OBM 2020.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.

You can perform in-place upgrade using the silent mode or GUI. OBM recommends the silent mode of upgrade.

Side-by-side upgrade refers to installing OBM 2020.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 and the new servers are referred as staging 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 upgrade, OBM 2020.05 is installed on the staging servers. Side-by-side upgrade begins when both production and staging servers are installed. During the process, event data is forwarded from the earlier OBM version to OBM 2020.05.

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

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

Choose the deployment type

Distributed deployment
Single-server deployment
Single-server HA

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.

Distributed Deployment (HA) is a deployment where there are two instances of DPS (active and backup) and gateway server.

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.

High availability can be implemented in single-server or distributed deployments. You configure high availability by adding a backup data processing server (DPS)/ Single Server. High availability configuration means setting up your OBM servers so that service is continuous despite power outages, machine downtime, and heavy load.

Choose the database management system

Microsoft SQL Server (remote 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.

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

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 IP6 upgrade process, OBM 2020.05 updates the embedded PostgreSQL database management system to the version 9.6.12.

Choose the database management system

Microsoft SQL Server (remote 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.

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

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 OBM10.12 IP6 upgrade process, OBM2020.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
GUI 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.

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.

We recommend to upgrade using the Silent deployment. However, you can choose to upgrade in Silent mode or GUI mode based on your install/upgrade scenario.

With GUI deployment, you can perform upgrade using the respective wizards by providing the required values. After running the upgrade, -d -gui the uninstallation wizard window is displayed. Perform the uninstallation, installation and configuration through the UI. During configuration, you must provide the required values manually in the configuration wizard.

In GUI deployment mode, make a note of the following:

  • Database connection details (Database hostname, username and password)
  • Server certificate details and keystore password
  • Backup file generated during the initial phase of upgrade, located at <OVDATADIR>/backup(For embedded postgres only)

You are required to re-enter the above details during the upgrade.

If you are upgrading from OBM 10.12IP6 to OBM 2020.05, the upgrade process requires some registry cleanup where the installation directory is non-default.

It is recommended to choose Silent deployment, if you want to avoid the above tasks.

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

Legal notice

By selecting not to encrypt credentials in configuration file option, you are disabling or bypassing security features, thereby exposing the system to increased security risks. By using this option, you understand and agree to assume all associated risks and hold Micro Focus harmless for the same.

Micro Focus encourages the customer to delete the configuration file following successful installation, which is not provided by Micro Focus. By not deleting the configuration file following successful installation you may exposing the system to increased security risks. You understand and agree to assume all associated risks and hold Micro Focus harmless for the same. It remains at all times the Customer’s sole responsibility to assess its own regulatory and business requirements. Micro Focus does not represent or warrant that its products comply with any specific legal or regulatory standards applicable to Customer in conducting Customer's business.

Select additional options

Load balancing
Change of Windows user account for OBM servicesUse of non-root Linux user account for OBM processes
Silent deployment
GUI 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.

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.

We recommend to upgrade using the Silent deployment. However, you can choose to upgrade in Silent mode or GUI mode based on your install/upgrade scenario.

With GUI deployment, you can perform upgrade using the respective wizards by providing the required values. After running the upgrade, -d -gui the uninstallation wizard window is displayed. Perform the uninstallation, installation and configuration through the UI. During configuration, you must provide the required values manually in the configuration wizard.

In GUI deployment mode, make a note of the following:

  • Database connection details (Database hostname, username and password)
  • Server certificate details and keystore password
  • Backup file generated during the initial phase of upgrade, located at <OVDATADIR>/backup(For embedded postgres only)

You are required to re-enter the above details during the upgrade.

If you are upgrading from OBM 10.12IP6 to OBM 2020.05, the upgrade process requires some registry cleanup where the installation directory is non-default.

It is recommended to choose Silent deployment, if you want to avoid the above tasks.

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

Legal notice

By selecting not to encrypt credentials in configuration file option, you are disabling or bypassing security features, thereby exposing the system to increased security risks. By using this option, you understand and agree to assume all associated risks and hold Micro Focus harmless for the same.

Micro Focus encourages the customer to delete the configuration file following successful installation, which is not provided by Micro Focus. By not deleting the configuration file following successful installation you may exposing the system to increased security risks. You understand and agree to assume all associated risks and hold Micro Focus harmless for the same. It remains at all times the Customer’s sole responsibility to assess its own regulatory and business requirements. Micro Focus does not represent or warrant that its products comply with any specific legal or regulatory standards applicable to Customer in conducting Customer's business.

View or print

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

After you select View, scroll up to check the hardware and software requirements.

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. If you are using a printed copy of the upgrade document, refer Online Interactive document for the latest updates.

Legal notice

By selecting not to encrypt credentials in configuration file option, you are disabling or bypassing security features, thereby exposing the system to increased security risks. By using this option, you understand and agree to assume all associated risks and hold Micro Focus harmless for the same.

Micro Focus encourages the customer to delete the configuration file following successful installation, which is not provided by Micro Focus. By not deleting the configuration file following successful installation you may exposing the system to increased security risks. You understand and agree to assume all associated risks and hold Micro Focus harmless for the same. It remains at all times the Customer’s sole responsibility to assess its own regulatory and business requirements. Micro Focus does not represent or warrant that its products comply with any specific legal or regulatory standards applicable to Customer in conducting Customer's business.

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 14 12 6
    Recommended 16 14 8
    Medium (up to 5,000 nodes) Minimum 16 14 8
    Recommended 20 18 10
    Large (more than 5,000 nodes) Minimum 32 30 10
    Recommended 44 42 12

    In addition, some memory is required for temporary data.

    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.

  • Disk Space: If you have problems with your disk space, consider removing all dump files in the following directories: <OBM_Home>\bin and for 10.12 IP6 versions: <OBM_HOME>\odb\bin, for 2018.11 and later versions: <OBM_HOME>\<ucmdb folder>\bin/opt/HP/BSM/bin and for 10.12 IP6 versions: /opt/HP/BSM/odb/bin, for 2018.11 and later versions:/opt/HP/BSM/ucmdb/bin

  • Free storage space. Before performing installation or upgrade of OBM, make sure the following amount of free storage space (in GB) is available:

    Default Directory Minimum Recommended
    /opt/HP/BSM 25 50
    /opt/OV 1 1
    /var 11111 22222
    /tmp

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

    export CHECK_DISK_SPACE=OFF

    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.

    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

    25 50

    C:\Program Files\HP\HP BTO Software

    C:\ProgramData\HP\BSM

    111

    222

    %TEMP% *

    2020 (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) is required on C:\ProgramData\HP\BSM.

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

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>

  • libnsl and libncurses packages library. On machines with RHEL 8 platform, on which you want plan to install OBM, you must install the RPM package libnsl and libncurses as a requirement for Operations Agent 12.12. Download the package from any RPM repository site that matches your system specifications.

    You can install the packages by running the following command:

    yum install -y libnsl ncurses-libs

  • M4 packages. The Operations Agent requires this package. You can install the packages by running the following command:

    yum install -y m4.

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

  • Fontconfig package. If you are doing an upgrade, ensure to install fontconfig package before starting the upgrade.

    Run the following command to install this package:

    yum install fontconfig

  • 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 and reboot the system.
  • 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 2020.05.

    To turn off UAC via registry, change the DWORD "EnableLUA" from 1 to 0 in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system".

    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:

    Operations Bridge Manager Integration portal.

    For more information on the supported versions for OBM, see SUMA link below:

    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.

  • 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

  • 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 must log in and log out to view the changes made to the .conf file. 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.

  • 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 2020.05 installation files must be available on the staging 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.

    For side-by-side upgrade, the installation files must be on all staging OBM servers. The installation files must also be on the production DPS. In an Ha environment, this is the primary data processing server.

    For side-by-side upgrade, the installation files must be on single server production OBM.

    The installation package is named OBM_<version>_for_Windows.zipOBM_<version>_for_Linux.zip where version is 2020.05. Download the archive file to the system where you plan to install OBMwhich you plan to upgrade to OBM 2020.05, and extract all files from the archive.

Optional. Obtain certificates for OBM

If your company uses a certificate authority (CA) that can generate certificates for OBM, request certificates that include the staging OBM server.

Optional. Obtain certificates for OBM

If your company uses a certificate authority (CA) that can generate certificates for OBM, request certificates that include the staging OBM server.

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. 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 information, see Enable OBM to use IPv6.

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

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 Support for Oracle Real Application Cluster.

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

  • 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 Workflow for Microsoft SQL Server deployment.

  • Tablespaces. Before setting database parameters, ensure that you have created at least one tablespace for each user schema for application data persistency purposes, and that you have set at least one temporary tablespace according to the requirements. For details on creating and sizing the tablespaces for OBM user schemas, see Oracle Server configuration and sizing guidelines.

  • Oracle Real Application Clusters (Oracle RAC). If your Oracle Database is configured in an Oracle Real Application Clusters (Oracle RAC) environment, you must perform additional configuration steps. For details, see Support for Oracle Real Application Cluster.

  • 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 Oracle Server deployment.

  • Oracle Database patch. For Oracle 19c, you must install the Oracle Patch ID 27935464 on the Oracle database server.

  • 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 amount of storage space consumed by your original (production) database depends on the number of events that flow. More the number of events, more the storage required. 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 Oracle Server deployment.

  • 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 amount of storage space consumed by your original (production) database depends on the number of events that flow. More the number of events, more the storage required.

  • 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 Oracle Server deployment.

  • 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 Support for Oracle Real Application Cluster.

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

  • 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 Workflow for Microsoft SQL Server deployment.

  • Tablespaces. Before setting database parameters, ensure that you have created at least one tablespace for each user schema for application data persistency purposes, and that you have set at least one temporary tablespace according to the requirements. For details on creating and sizing the tablespaces for OBM user schemas, see Oracle Server configuration and sizing guidelines.

  • Oracle Real Application Clusters (Oracle RAC). If your Oracle Database is configured in an Oracle Real Application Clusters (Oracle RAC) environment, you must perform additional configuration steps. For details, see Support for Oracle Real Application Cluster.

  • 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 Oracle Server deployment.

  • Oracle Database patch. For Oracle 19c, you must install the Oracle Patch ID 27935464 on the Oracle database server.

  • 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 amount of storage space consumed by your original (production) database depends on the number of events that flow. More the number of events, more the storage required. 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 Oracle Server deployment.

  • 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 amount of storage space consumed by your original (production) database depends on the number of events that flow. More the number of events, more the storage required.

  • 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 Oracle Server deployment.

  • 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 Support for Oracle Real Application Cluster.

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

  • 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 Workflow for Microsoft SQL Server deployment.

  • Tablespaces. Before setting database parameters, ensure that you have created at least one tablespace for each user schema for application data persistency purposes, and that you have set at least one temporary tablespace according to the requirements. For details on creating and sizing the tablespaces for OBM user schemas, see Oracle Server configuration and sizing guidelines.

  • Oracle Real Application Clusters (Oracle RAC). If your Oracle Database is configured in an Oracle Real Application Clusters (Oracle RAC) environment, you must perform additional configuration steps. For details, see Support for Oracle Real Application Cluster.

  • 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 Oracle Server deployment.

  • Oracle Database patch. For Oracle 19c, you must install the Oracle Patch ID 27935464 on the Oracle database server.

  • 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 amount of storage space consumed by your original (production) database depends on the number of events that flow. More the number of events, more the storage required. 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 Oracle Server deployment.

  • 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 amount of storage space consumed by your original (production) database depends on the number of events that flow. More the number of events, more the storage required.

  • 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 Oracle Server deployment.

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

    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 Create Oracle schemas manually.

Plan the upgrade process

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

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

    • Support for your database management system. Check the OBM 2020.05 support matrix 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.

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

  • Backup. The following files are required to take a backup manually from your original BSMOBM host systems:

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

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

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

    The following files will be automatically taken a backup:

    • 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>/ucmdb/\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 OBM, 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. Run the following command to stop OBM on all DPS and gateway servers as non-root user:

      OBM versions before 2018.11:

      On a side-by-side > single server HA, run the following command to stop OBM versions before 2018.11 on all production backup server:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database:

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

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

      %ovdatadir%\databases\omidb\postgresql.conf /var/opt/OV/databases/omidb/postgresql.conf

      Set the max_locks_per_transaction parameter to 512 and uncomment the line.

    4. Start the PostgreSQL database:

      <OBM_Home>\bin\opr-pgctl.bat –start/opt/HP/BSM/bin/opr-pgctl.sh –start

    5. Start OBM services on primary DPS. Continue the upgrade process.

      /HPBSM/scripts/run_hpbsm start/opt/HP/BSM/scripts/run_hpbsm start

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

    1. Run the following command to stop OBM on all on all production backup server:

      OBM versions before 2018.11:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database:

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

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

      %ovdatadir%\databases\omidb\postgresql.conf/var/opt/OV/databases/omidb/postgresql.conf

      Set the max_locks_per_transaction parameter to 512 and uncomment the line.

    4. Start the PostgreSQL database:

      <OBM_Home>\bin\opr-pgctl.bat –start/opt/HP/BSM/bin/opr-pgctl.sh –start

    5. Start OBM services on active server. Continue the upgrade process.

      /HPBSM/scripts/run_hpbsm start/opt/HP/BSM/scripts/run_hpbsm start

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

    1. Run the following command to stop OBM versions before 2018.11 on all DPS and gateway servers:

      On a side-by-side > single server HA, run the following command to stop OBM versions before 2018.11 on all production backup server:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database on the DB host system:

    3. Edit the postgresql.conf file at the database host system:

      Set the max_locks_per_transaction parameter to 512.

    4. Start the PostgreSQL database on the DB host system.
    5. Start the OBM services on the primary DPS. Continue the upgrade process.

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

    1. Run the following command to stop OBM versions before 2018.11 on all production backup server:

      OBM versions before 2018.11:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database on the DB host system:

    3. Edit the postgresql.conf file at the database host system:

      Set the max_locks_per_transaction parameter to 512.

    4. Start the PostgreSQL database on the DB host system.
    5. Start the OBM services on the active server. Continue the upgrade process.
  • 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.
  • The OPEN_CURSORS parameter of Oracle Database. For the upgrade, set the Oracle Database parameter OPEN_CURSORS to 10,000 on the staging Oracle Database. You can revert this parameter to the original value after the upgrade is complete.

  • Integrations. For details on product versions that are supported with OBM 2020.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.

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

OBM Version and Integration Check Tools

If you are planning to install or upgrade OBM/OMi version to the latest version, you can use the following 2 tools available on ITOM Marketplace , which will ease your installation or upgrade planning exercise. For details, see Operations Brigde Manager (OBM) Version and Integration Check Tools.

Make sure to regularly check ITOM Marketplace for the latest revision of this package.

opr-version-check

You can run opr-version-check (based on Perl) on the OBM Gateway Server or Data Processing Server (on Linux or Windows) to determine details about your current deployment, installed Management Packs, installed Operations Connectors and other integrated products such as APM or OBR.

In case any of the detected versions should get upgraded, opr-version-check will provide you proper guidelines. You can also run this tool in offline mode by providing previously collected information from opr-checker, opr-support-utils and other standard OBM CLIs.

The tool analyzes non-containerized OBM deployments from OMi10.12 and above.

Excel-based OBM-Integration Checker

This Excel-based tool helps you plan the key integrations into OBM by visualizing the support matrix information for APM, SiteScope, NNMi, external UCMDB and OO (Operations Orchestration).

Plan the upgrade process

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

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

    • Support for your database management system. Check the OBM 2020.05 support matrix 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.

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

  • Backup. The following files are required to take a backup manually from your original BSMOBM host systems:

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

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

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

    The following files will be automatically taken a backup:

    • 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>/ucmdb/\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 OBM, 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. Run the following command to stop OBM on all DPS and gateway servers as non-root user:

      OBM versions before 2018.11:

      On a side-by-side > single server HA, run the following command to stop OBM versions before 2018.11 on all production backup server:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database:

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

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

      %ovdatadir%\databases\omidb\postgresql.conf /var/opt/OV/databases/omidb/postgresql.conf

      Set the max_locks_per_transaction parameter to 512 and uncomment the line.

    4. Start the PostgreSQL database:

      <OBM_Home>\bin\opr-pgctl.bat –start/opt/HP/BSM/bin/opr-pgctl.sh –start

    5. Start OBM services on primary DPS. Continue the upgrade process.

      /HPBSM/scripts/run_hpbsm start/opt/HP/BSM/scripts/run_hpbsm start

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

    1. Run the following command to stop OBM on all on all production backup server:

      OBM versions before 2018.11:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database:

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

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

      %ovdatadir%\databases\omidb\postgresql.conf/var/opt/OV/databases/omidb/postgresql.conf

      Set the max_locks_per_transaction parameter to 512 and uncomment the line.

    4. Start the PostgreSQL database:

      <OBM_Home>\bin\opr-pgctl.bat –start/opt/HP/BSM/bin/opr-pgctl.sh –start

    5. Start OBM services on active server. Continue the upgrade process.

      /HPBSM/scripts/run_hpbsm start/opt/HP/BSM/scripts/run_hpbsm start

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

    1. Run the following command to stop OBM versions before 2018.11 on all DPS and gateway servers:

      On a side-by-side > single server HA, run the following command to stop OBM versions before 2018.11 on all production backup server:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database on the DB host system:

    3. Edit the postgresql.conf file at the database host system:

      Set the max_locks_per_transaction parameter to 512.

    4. Start the PostgreSQL database on the DB host system.
    5. Start the OBM services on the primary DPS. Continue the upgrade process.

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

    1. Run the following command to stop OBM versions before 2018.11 on all production backup server:

      OBM versions before 2018.11:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database on the DB host system:

    3. Edit the postgresql.conf file at the database host system:

      Set the max_locks_per_transaction parameter to 512.

    4. Start the PostgreSQL database on the DB host system.
    5. Start the OBM services on the active server. Continue the upgrade process.
  • 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.
  • The OPEN_CURSORS parameter of Oracle Database. For the upgrade, set the Oracle Database parameter OPEN_CURSORS to 10,000 on the staging Oracle Database. You can revert this parameter to the original value after the upgrade is complete.

  • Integrations. For details on product versions that are supported with OBM 2020.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.

  • 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 upgrade process

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

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

    • Support for your database management system. Check the OBM 2020.05 support matrix 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.

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

  • Backup. The following files are required to take a backup manually from your original BSMOBM host systems:

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

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

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

    The following files will be automatically taken a backup:

    • 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>/ucmdb/\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 OBM, 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. Run the following command to stop OBM on all DPS and gateway servers as non-root user:

      OBM versions before 2018.11:

      On a side-by-side > single server HA, run the following command to stop OBM versions before 2018.11 on all production backup server:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database:

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

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

      %ovdatadir%\databases\omidb\postgresql.conf /var/opt/OV/databases/omidb/postgresql.conf

      Set the max_locks_per_transaction parameter to 512 and uncomment the line.

    4. Start the PostgreSQL database:

      <OBM_Home>\bin\opr-pgctl.bat –start/opt/HP/BSM/bin/opr-pgctl.sh –start

    5. Start OBM services on primary DPS. Continue the upgrade process.

      /HPBSM/scripts/run_hpbsm start/opt/HP/BSM/scripts/run_hpbsm start

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

    1. Run the following command to stop OBM on all on all production backup server:

      OBM versions before 2018.11:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database:

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

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

      %ovdatadir%\databases\omidb\postgresql.conf/var/opt/OV/databases/omidb/postgresql.conf

      Set the max_locks_per_transaction parameter to 512 and uncomment the line.

    4. Start the PostgreSQL database:

      <OBM_Home>\bin\opr-pgctl.bat –start/opt/HP/BSM/bin/opr-pgctl.sh –start

    5. Start OBM services on active server. Continue the upgrade process.

      /HPBSM/scripts/run_hpbsm start/opt/HP/BSM/scripts/run_hpbsm start

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

    1. Run the following command to stop OBM versions before 2018.11 on all DPS and gateway servers:

      On a side-by-side > single server HA, run the following command to stop OBM versions before 2018.11 on all production backup server:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database on the DB host system:

    3. Edit the postgresql.conf file at the database host system:

      Set the max_locks_per_transaction parameter to 512.

    4. Start the PostgreSQL database on the DB host system.
    5. Start the OBM services on the primary DPS. Continue the upgrade process.

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

    1. Run the following command to stop OBM versions before 2018.11 on all production backup server:

      OBM versions before 2018.11:

      <OBM_HOME>/scripts/run_hpbsm stop/opt/HP/BSM/scripts/run_hpbsm stop

      OBM version 2018.11 and higher:

      <OBM_HOME>/scripts/run_hpbsm stopall/opt/HP/BSM/scripts/run_hpbsm stopall

    2. Shut down the PostgreSQL database on the DB host system:

    3. Edit the postgresql.conf file at the database host system:

      Set the max_locks_per_transaction parameter to 512.

    4. Start the PostgreSQL database on the DB host system.
    5. Start the OBM services on the active server. Continue the upgrade process.
  • 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.
  • The OPEN_CURSORS parameter of Oracle Database. For the upgrade, set the Oracle Database parameter OPEN_CURSORS to 10,000 on the staging Oracle Database. You can revert this parameter to the original value after the upgrade is complete.

  • Integrations. For details on product versions that are supported with OBM 2020.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.

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

Configure event buffering in OM

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

During the upgrade, OM continues to attempt sending events to BSMthe already installed production OMi/OBM version. If BSMthe production OMi/OBM 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 upgrade process

Before you initiate the upgrade process:

  • Make sure that no other installations or processes that require Windows Installer are running. If there are, OBM installation cannot complete and you must terminate it by clicking Cancel in the OBM installation wizard.
  • Make sure to close all the folders and directories before running the uninstall script.

Make a note of the embedded postgres database password during the initial stage of installation. You will be prompted to use this password during upgrade.

Note The embedded postgres database backup and restore takes a large amount of time without any progress bar. Do not quit the process until complete.

Ensure to make a note of the following:

  • Database connection details (Database hostname, username and password)
  • Server certificate details and keystore password
  • Backup file generated during the initial phase of upgrade before the uninstallation starts. This file is located at <OVDATADIR>/backup

You are required to re-enter the above details during the upgrade. If you are upgrading from OBM 10.12IP6 to OBM 2020.05, the upgrade process requires some registry cleanup.

It is recommended to choose Silent deployment, if you want to avoid the above tasks.

Considerations

Before you begin to upgrade your BSMOBM servers, consider the following:

  • You can extend your existing BSMOBM environment with additional servers only after it is upgraded to OBM 2020.05. Therefore, first upgrade all configured servers of the existing deployment to OBM 2020.05, and then install and configure additional OBM servers.

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

  • Do not attempt to disable or uninstall BSMOBM before initiating the upgrade process. A disabled or uninstalled BSMOMi might cause loss of events that originate from your monitored 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.

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

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

Database maintenance to expedite the upgrade process

This section helps to optimize the downtime and expedite your upgrade process.

Make sure that your PostgreSQL database is well maintained. The below maintenance steps can be performed while OBM is running and please note that they could take a long time if they have never been performed before. Performing these operations puts a certain load on your system. Hence we recommend to run the steps when system load is low. However, it is not required to shut down the OBM services every time you run a database maintenance.

Embedded PostgreSQL

  1. Run <TOPAZ_HOME>/pgsql/bin/vacuumlo -v -h localhost -p 5433 -U postgres <Schema_Name> where, Schema_Name depend on the your installation. You need to run these commands three times. Once for your OBM event schema name, once for OBM RTSM schema name, and once with the value of postgres. The exact schema names will depend on your installation.

    Wait until the process completes. This may take a while. Do not execute vacuumlo on management schema name.

  2. Run <TOPAZ_HOME>/pgsql/bin/vacuumdb -v --all --full -h localhost -p 5433 -U postgres.

  1. Run /opt/HP/BSM/pgsql/bin/vacuumlo -v -h localhost -p 5433 -U postgres <Schema_Name> where, Schema_Name depend on the your installation. You need to run these commands three times. Once for your OBM event schema name, once for OBM RTSM schema name, and once with the value of postgres. The exact schema names will depend on your installation.

    Wait until the process completes. This may take a while. Do not execute vacuumlo on management schema name.

  2. Run /opt/HP/BSM/pgsql/bin/vacuumdb -v --all --full -h localhost -p 5433 -U postgres.

Remote PostgreSQL

Work with your PostgreSQL DBA to perform the recommended periodic DB maintenance that includes running vacuumlo and vacuumdb. This maintenance should be scheduled to run before your OBM upgrade. For more details, see Database maintenance.

Adjust the embedded PostgreSQL DB parameters

For the upgrade process to be successful, the max_locks_per_transaction setting of PostgreSQL DB needs to be set to 512 before the upgrade tool makes the initial backup of your database.

  1. Click Disable OBM to stop OBM services (check the service status window to ensure all listed services are disappeared). Select Start > Applications > Disable Operations Bridge Manager.

  2. Run <TOPAZ_HOME>/bin/opr-pgctl.bat –stop to stop the embedded postgres DB.

  3. Modify <OVDATADIR>/databases/omidb/postgresql.conf, uncomment the line which has max_locks_per_transaction set to 64, and increase the value up to 512. This prevents the silent DB-backup failure during the update/upgrade process.

  4. Run <TOPAZ_HOME>/bin/opr-pgctl.bat –start to start the embedded postgres DB.
  5. Click Enable OBM to start OBM services (check the service status window to ensure all listed services are appeared). Select Start > Applications > Enable Operations Bridge Manager.
  1. Run /opt/HP/BSM/scripts/run_hpbsm stop to stop the OBM services.

  2. Run /opt/HP/BSM/bin/opr-pgctl.sh –stop to stop the embedded postgres DB.

  3. Modify <OVDATADIR>/databases/omidb/postgresql.conf, uncomment the line which has max_locks_per_transaction set to 64, and increase the value up to 512. This prevents the silent DB-backup failure during the update/upgrade process.

  4. Run /opt/HP/BSM/opr-pgctl.sh –start to start the embedded postgres DB.
  5. Run /opt/HP/BSM/scripts/run_hpbsm start to start OBM services.

Adjust the remote PostgreSQL DB parameters

For the upgrade process to be successful, the max_locks_per_transaction setting of PostgreSQL needs to be set to 512. You need to have your DBA make this change and restart PostgreSQL before the upgrade. Since this parameter change require a restart of PostgreSQL to take effect, you need to schedule this change during a shutdown of OBM.

  1. Completely shut down your entire OBM deployment. To stop the services, run the following command: /opt/HP/BSM/scripts/run_hpbsm stop
  2. Your DBA, after having changed the max_locks_per_transaction value to 512, restart the PostgreSQL DB for this parameter to take effect.
  3. Start the OBM deployment. To start the services, run the following command:/opt/HP/BSM/scripts/run_hpbsm start
  1. Completely shut down your entire OBM deployment. Click Disable OBM to stop OBM services (check the service status window to ensure all listed services are disappeared). Select Start > Applications > Disable Operations Bridge Manager.
  2. Your DBA, after having changed the max_locks_per_transaction value to 512, restart the PostgreSQL DB for this parameter to take effect.
  3. Start the OBM deployment. Click Enable OBM to start OBM services (check the service status window to ensure all listed services are appeared). Select Start > Applications > Enable Operations Bridge Manager.

There are also utilities shipped with OBM for rebuilding entire indexes or rebuilding just fragmented indexes, which can be used for tuning and improving the performance in OBM deployments with MSSQL/Oracle databases. They are located at <TOPAZ_HOME>/opr/support/database/[sqlserver|oracle].

There are utilities shipped with OBM for rebuilding entire indexes or rebuilding just fragmented indexes, which can be used for tuning and improving the performance in OBM deployments with MSSQL/Oracle databases. They are located at /opt/HP/BSM/bin/opr/support/database/[sqlserver|oracle].

Optional. Archiving of closed events

When you have large number of closed events, run the following tool (on primary DPS only) before starting the upgrade to archive the closed events:

<TOPAZ_HOME>\bin\opr-archive-events.bat

When you have large number of closed events, run the following tool (on primary DPS only) before starting the upgrade to archive the closed events:

/opt/HP/BSM/bin/opr-archive-events.sh

Overview

Based on your deployment selection, follow the steps in the document carefully to complete the upgrade process successfully.

Upgradeyour older OMi/OBM version toOBM 2020.05 as follows:

During upgrade, perform the following steps on the primary data processing server (DPS) first. When the primary DPS is running the secondary DPS and the gateway servers should be down. After the primary DPS upgrade is complete, run the upgrade script on gateway server. Run the upgrade script on secondary DPS after the gateway server is upgraded.

  1. Make sure that the earlier OMi/OBM version is enabled (all servicesprocesses are running).
  2. On the existing production 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 2020.05 installation.

  5. Install OBM2020.05 on the staging 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.

On single-server HA, upgrade the active server first. Make sure that all the services (including UCMDB, bus etc) are running on the active server. Ensure the backup server and any gateway servers are stopped. Once the active server upgrade is complete, upgrade the backup server and then upgrade any gateway server.

  1. Make sure that the earlier OMi/OBM version is enabled (all servicesprocesses are running).
  2. On the existing production 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 2020.05 installation.

  5. Install OBM2020.05 on the active 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.

If there are any additional gateway servers, perform the above steps on the gateway servers.

  1. Make sure that the earlier OBM/OMi version is enabled (all services are running on the OMi host systems).
  2. On the primary active server, initiate the upgrade process.
  3. Attend the initial upgrade phase. Perform steps 4 to 6 on the OBM staging active server.
  4. On the host system of your staging active server, start the 2020.05 installation.
  5. Install OBM 2020.05 by following the instructions of the installation wizard.
  6. Follow the instructions of the configuration/upgrade wizard, and conclude the upgrade process.
  1. Install the OBM software in the staging environment.
  2. On the primary DPS of your existing OBM/OMi deployment, initiate the upgrade process.
  3. Replicate the database to the staging environment.
  4. Configure event forwarding from the production OBM environment to the staging OBM gateway.
  5. Run the configuration wizard in the staging environment.

Note A side-by-side upgrade requires a short downtime in the production OBM environment. The down time is the time it takes to stop OBM, run the upgrade script, replicate the database, start OBM and change two Infrastructure Settings.

  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 staging primary data processing server (DPS), start the 2020.05installation.

  5. Install OBM 2020.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.

Upgrade the older OMi/OBM version to OBM 2020.05 as follows:

During upgrade, perform the upgrade in the following order. Upgrade the primary data processing server (DPS) first followed by gateway server and secondary DPS.

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 2020.05. Thus, first upgrade all configured servers of the existing deployment to OBM 2020.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 2020.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 2020.05 installation.

  5. Install OBM2020.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 2020.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 2020.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. 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 2020.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 2020.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.

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

  1. On the BSMOBM host systemnew system that will host OBM, create an empty file called ovinstallparams.iniin the same directory as the HPOMi_<VersionAndBuild>_setup.exeHPOMi_<VersionAndBuild>_setup.bin executable file, for examplein 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

Before you 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 OBM2020.05 version. Make sure to close all the files and directory that belongs to HPBSM directory before running the upgrade script. 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.

Optional. By default, the upgrade installs OBM 2020.05 to the same drive where the previous version is installed. If you want OBM to be installed to a different location instead, create an empty file called ovinstallparams.ini in the same directory as the HPOMi_<VersionAndBuild>_setup.exe executable file, for example:

<OBMInstallationFiles>\Software\HPOMi_<VersionAndBuild>_setup.exe

<OBMInstallationFiles>\Software\ovinstallparams.ini

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

[installer.properties]
setup=HPOMi
group=typical

                                                                            

To change the default installation directories, add the following lines at the end of the 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.
Assuming that the OBM install drive is C:, following 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. The quotation marks (" ") are not supported.

Optional. By default, the upgrade installs OBM2020.05 to the same drive where the previous version is installed. If you want OBM to be installed to a different location instead, create an empty file called ovinstallparams.ini in the same directory as the HPOMi_<VersionAndBuild>_setup.exe executable file, for example:

<OBMInstallationFiles>\Software\HPOMi_<VersionAndBuild>_setup.exe

<OBMInstallationFiles>\Software\ovinstallparams.ini

Depending on whether the host system is a data processing server or gateway server, copy the following lines at the end of ovinstallparams.ini file located at <OBMInstallationFiles>/Software/ovinstallparams.ini:

Data processing server:

[installer.properties]
setup=HPOMi
group=process
 

Gateway server:

[installer.properties]
setup=HPOMi
group=gateway

                                                                            

To change the default installation directories, add the following lines at the end of the 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.
Assuming that the OBM install drive is C:, following 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. The quotation marks (" ") are not supported.

Initiate the upgrade process

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

To initiate the first phase of the upgrade process for the production systemexisting BSM OBM host system, follow the steps:

Perform the following steps in order - Upgrade Primary DPS and enable Primary DPS then only start the upgrade of gateway server and enable the gateway server. After you complete upgrade on the gateway, start upgrade on the secondary DPS and enable the same.

Log in to the active data processing server of the production OBM environment. The active DPS is the one where the live bus is running. To determine the live bus server, run the following command on one of the data processing servers:

/opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver

Log in to the active data processing server of the production OBM environment. The active DPS is the one where the live bus is running. To determine the live bus server, run the following command on one of the data processing servers:

<OBM_HOME>/opr/support/opr-support-utils.bat -bus -getserver

Log in to the active data processing server of the production OBM environment. The active DPS is the one where the live bus is running. To determine the live bus server, run the following command on one of the data processing servers:

/opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver

Log in to the active data processing server of the production OBM environment. The active DPS is the one where the live bus is running. To determine the live bus server, run the following command on one of the data processing servers:

<OBM_HOME>/opr/support/opr-support-utils.bat -bus -getserver

Note Make sure to stop gateway servers and secondary DPS before you run the upgrade on primary DPS .

  1. You must run the following commands to stop services on the secondary DPS and gateways:

    <OBM_HOME>\bin\SupervisorStopAll (for OBM 2018.11 and later versions)

    <OBM_HOME>\SupervisorStop (for OBM 2018.05 and previous versions)

    You must run the following commands to stop services on the secondary DPS and gateways:

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

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

  2. Open a Command Promptterminal window as an administratorthe root user on primary DPS.

  3. Change the current directory to the location where you have extracted files from the OBM2020.05 installation package to as follows:

    cd <OBMInstallationFilesDirectory>

  4. Run the following command:

    upgrade.bat -s -silent

    upgrade.sh -s -silent

    Note The upgrade script changes the Event Forwarding Expiration to 336 hours (14 days). If you have previously modified the default value, make a note of the value before starting the upgrade so that you can restore the value in the later step. To make a note of the value, go to Administration > Setup and Maintenance > Infrastructure Settings > Operations Management - Event Synchronization Settings > Event Forwarding Expiration.

    The -s command runs the preliminary checks for the all services running on active DPS, if the live bus running on active DPS or not. It runs the pre-upgrade tool to stop the incoming events and wait for the event queue to be cleared. If you have an external database, the OBM services do not start or stop. If you are using embedded PostgreSQL, the upgrade script also stops OBM, backs up the database and starts OBM.

    The event flow is paused when the gateway server is stopped. The event flow is resumed on the production OBM after the primary DPS and atleast one of the gateway server upgrade is complete and OBM services is running.

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

    upgrade.bat -s -silent -archive=true

    upgrade.sh -s -silent -archive=true

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

    If you choose Y, you can archive the closed events in 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.bat -d-gui

    upgrade.sh -d-gui

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

    upgrade.bat -d -silent -gui -archive=true

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

    In GUI upgrade, you need to choose the installation type and the path manually.

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

    If you choose Y, you can archive the closed events in 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.bat -d -s

    upgrade.sh -d -s

    Note The upgrade script changes the Event Forwarding Expiration to 336 hours (14 days). If you have previously modified the default value, make a note of the value before starting the upgrade so that you can restore the value in the later step. To make a note of the value, go to Administration > Setup and Maintenance > Infrastructure Settings > Operations Management - Event Synchronization Settings > Event Forwarding Expiration.

    The -s command runs the preliminary checks for the all services running on active DPS, if the live bus running on active DPS or not. It runs the pre-upgrade tool to stop the incoming events and wait for the event queue to be cleared. If you have an external database, the OBM services do not start or stop. If you are using embedded PostgreSQL, the upgrade script also stops OBM, backs up the database and starts OBM.

    The event flow is paused when the gateway server is stopped. The event flow is resumed on the production OBM after the primary DPS and atleast one of the gateway server upgrade is complete and OBM services is running.

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

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

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

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

    If you choose Y, you can archive the closed events in 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.

    Initiate the upgrade on primary DPS first, then gateway server and then on secondary DPS as shown in the following table:

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

    Run the following command:

    upgrade.bat -d -silent -gui

    upgrade.sh -d -silent -gui

    Note Make sure the gateway server and secondary DPS are down.

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

    upgrade.bat -d -silent -archive=true -gui

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

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

    If you choose Y, you can archive the closed events in 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 2020.05 is installed and configured on the primary DPS, start the services on the primary DPS.

    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_2020.05._for_Windows and manually run install.bat.
     

    Note Do not proceed to upgrade the gateway servers and the secondary DPS until the primary DPS is upgraded and the services are started.

    For a gateway server

    You must the run the following command to stop the services:

    <OBM_HOME>\bin\SupervisorStopAll (for OBM 2018.11 and later versions)

    <OBM_HOME>\SupervisorStop (for OBM 2018.05 and previous versions)

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

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

    Run the following command:

    upgrade.bat -d -silent -gui

    upgrade.sh -d -silent -gui

    Note

    If the upgrade.bat.sh -d -silent 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 2020.05 is installed and configured on the gateway server, start the services on the gateway server. Do not proceed to upgrade the secondary DPS until the gateway servers are upgraded and the services are started.

    Note You can upgrade multiple gateway server concurrently to shorten the OBM server outage.

    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_2020.05._for_Windows and manually run install.bat.

    For a secondary DPS

    You must the run the following command to stop the services:

    <OBM_HOME>\bin\SupervisorStopAll (for OBM 2018.11and later versions)

    <OBM_HOME>\SupervisorStop (for OBM 2018.05 and previous versions)

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

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

    Run the following command:

    upgrade.bat -d -silent -gui

    upgrade.sh -d -silent -gui

    Note

    If the upgrade.bat.sh -d -silent 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_2020.05._for_Windows and manually run install.bat.

    After the secondary DPS is upgraded, that is, after OBM2020.05 is installed and configured on the secondary DPS, start the services on the secondary DPS.

     

    Run the following command on the active server of your existing OBM environment:

    upgrade.bat -s

    upgrade.sh -s

    The event flow is paused when the gateway server is stopped. The event flow is resumed on the production OBM after the active server and atleast one of the gateway server upgrade is complete and OBM services is running.

    After the active server is upgraded, that is, after OBM2020.05 is installed and configured on the active server, start the services on the active server. Do not proceed to upgrade the backup servers and any additional gateway servers until the active server is upgraded and the services are started.

    Note The upgrade script changes the Event Forwarding Expiration to 336 hours (14 days). If you have previously modified the default value, make a note of the value before starting the upgrade so that you can restore the value in the later step. To make a note of the value, go to Administration > Setup and Maintenance > Infrastructure Settings > Operations Management - Event Synchronization Settings > Event Forwarding Expiration.

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

    upgrade.bat -s -silent -archive=true

    upgrade.sh -s -silent -archive=true

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

    If you choose Y, you can archive the closed events in 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.

    Verify if the configuration wizard has run successfully by checking the configuration log file:

    The configuration wizard runs silently in the background.

    HPBSM\log\configserver\configserver_all.log

    Note If the upgrade fails before the configuration, you must run the upgrade in GUI mode again. If the configuration fails, you are required to run the configuration wizard manually.

    Verify if the configuration wizard has run successfully by checking the configuration log file:

    The configuration wizard runs silently in the background.

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

    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 you initiate the upgrade, follow the order to complete the upgrade process (for Single-server HA only):

    1. Stop the services on secondary production server
    2. Start upgrade process on primary production server
    3. Install and configure primary staging server. Wait until the primary staging server is completely installed and configured.
    4. Install and configure secondary staging server
    5. Enable primary staging server
    6. Enable secondary staging server

    Run the following command:

    upgrade.bat -d-gui

    upgrade.sh -d-gui

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

    upgrade.bat -d -silent -gui -archive=true

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

    In GUI upgrade, you need to choose the installation type and the path manually.

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

    If you choose Y, you can archive the closed events in 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.

    Verify if the configuration wizard has run successfully by checking the configuration log file:

    The configuration wizard runs silently in the background.

    HPBSM\log\configserver\configserver_all.log

    Note If the upgrade fails before the configuration, you must run the upgrade in GUI mode again. If the configuration fails, you are required to run the configuration wizard manually.

    Verify if the configuration wizard has run successfully by checking the configuration log file:

    The configuration wizard runs silently in the background.

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

    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.

Enable OBM services on primary DPS first. Then upgrade gateway server following the steps 1-3 and then enable OBM services on the gateway server . After you complete the upgrade primary DPS and gateway server , start the upgrade process on secondary DPS .

Enable OBM services on active server first. Then upgrade backup server following the steps 1-3 and then enable OBM services on the backup server. After you complete the upgrade active server and backup server, start the upgrade process on gateway server.

Attend the initial upgrade phase

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

  • The event queue is emptied on the primary DPS or active server.

  • 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: (./upgrade.sh) Upgrading from OMi/OBM version 1082
INFO: (./upgrade.sh) Checking for multiple DPS setup
INFO: Multiple DPS configured
INFO: More than one DPS connected
INFO: (./upgrade.sh) Multiple DPS detected. Will check for Active/Backup DPS
INFO: (./upgrade.sh) Checking if running on active DPS

 

INFO: (./upgrade.sh) Upgrading from OMi/OBM version 1063
INFO: Embedded Postgres database detected.
INFO: (./upgrade.sh) Running PreMigration Tool to prepare for Upgrade
INFO: (./upgrade.sh) Starting Pre Upgrade tool. Logs present in %OVDataDir%/log/opr-upgradeBackup.log
INFO: (./upgrade.bat) Upgrading from OMi/OBM version 1063
INFO: Embedded Postgres database detected.
INFO: (./upgrade.bat) Running PreMigration Tool to prepare for Upgrade
INFO: (./upgrade.bat) Starting Pre Upgrade tool. Logs present in %OVDataDir%/log/opr-upgradeBackup.log
 
INFO: (./upgrade.bat) Upgrading from OMi/OBM version 1082
INFO: (./upgrade.bat) Checking for multiple DPS setup
INFO: Multiple DPS configured
INFO: More than one DPS connected
INFO: (./upgrade.bat) Multiple DPS detected. Will check for Active/Backup DPS
INFO: (./upgrade.bat) Checking if running on active DPS

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/OBM 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/OBM, if installed.

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

Note During the uninstallation process, there are some packages or RPMs which are not removed sometimes. The following message appears in the command prompt:

Do you want to forcibly remove the left-over RPMs? (Y/N)

Choose Y to remove.

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

After your earlier OMi/OBM version is uninstalled, the upgrade process invokes the installation of OBM 2020.05. Invoke the installation of OBM 2020.05.

In GUI mode, the upgrade process requires certain registry cleanup. Once uninstallation is complete and installation of 2020.05 is launched, cancel the installation window and do the following:

Delete the registry entry along with all sub keys, if its present:

HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\BSM and HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP OpenView

Invoke a new instance of command prompt and run install.bat.

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

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

Attend invocation of the OBM 2020.05 installation

After your earlier OMi/OBM version is uninstalled, the upgrade process invokes the installation of OBM 2020.05. Invoke the installation of OBM 2020.05.

In GUI mode, the upgrade process requires certain registry cleanup. Once uninstallation is complete and installation of 2020.05 is launched, cancel the installation window and do the following:

Delete the registry entry along with all sub keys, if its present:

HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\BSM and HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP OpenView

Invoke a new instance of command prompt and run install.bat.

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

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

Plan the installation process

Considerations

Before you begin to install OBM, consider the following:

  • You can install and configure OBM in one of the following ways:

    • Parallel installation and serial configuration. You can run the installation for all servers (on all host systems) in parallel. The configuration wizard, however, must be run for a data processing server (DPS) first. This server becomes the primary DPS in OBM. It creates the certificates required for secure communication and stores them in the database. After you configure the primary DPS, continue with the configuration of the secondary data processing server (optional), and finally configure the gateway servers.

      For parallel installation and serial configuration, select the Quit option in the last page of the post-installation wizard. Such selection enables you to finish installing all OBM servers first and to configure them at a later time.

    • Serial installation and configuration. You can install and configure the OBM servers in a sequence. In this case, install and configure an OBM data processing server (DPS) first. This server becomes the primary DPS. Then install and configure OBM on the other DPSs. Finally complete the deployment by installing and configuring the gateway servers. The wizard will direct you as to when to begin the installation on the gateway server.

      For serial installation and configuration, select the Configure OBM option in the last page of the post-installation wizard. Such selection automatically invokes the configuration wizard after the installation of each server.

    • Console mode or silent installation. You can install OBM 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

  • You can verify whether the installation files contain the original Micro Focus-provided code and have not been manipulated by a third-party. For instructions on how to do so, see the GPG or RPM Signature Verification website.

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

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

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

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

Prerequisites

Before you initiate the installation process, check the following:

  • Ensure that no other installations or processes that require Windows Installer are running. If there are, OBM installation cannot complete and you must terminate it by clicking Cancel in the OBM installation wizard.

Prerequisites

Before you initiate the installation process, make sure that no other installations are running.

Before you initiate the installation process, make sure there is no ovinstallparams.ini file in /tmp/.

Install and configuration sequence

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

Install and configuration sequence

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

  1. On the BSMOBM host systemnew system that will host OBM, create an empty file called ovinstallparams.iniin the same directory as the HPOMi_<VersionAndBuild>_setup.exeHPOMi_<VersionAndBuild>_setup.bin executable file, for examplein 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

Start the OBM 2020.05 installation

Invocation of the OBM 2020.05 installation is the same for both single server deployment types and gateway and data processing server in distributed deployment 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 staging 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

      You can run the install command on all the gateway and data processing servers concurrently.

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

      Note During inplace upgrade, do not quit the configuration wizard. Complete the configuration steps on primary DPS first, and then on each gateway servers and then on secondary DPS.

      Note During side-by-side upgrade, after the GUI-mode installation completes, exit the wizard and run the configuration wizard later.

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

    ./install.sh -silent

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

When you choose to run the OBM installation on console mode, make sure to follow the instructions on the command shell. After the steps on the console window is complete, go to Initiate the upgrade process section to continue with the upgrade.

The below steps are applicable for GUI upgrade only. If you chose to run on console mode, then skip these steps and go to Initiate the upgrade process section.

Start the OBM 2020.05 installation

Invocation of the OBM 2020.05 installation is the same for both single server deployment types and gateway and data processing server in distributed deployment 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 staging 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

      You can run the install command on all the gateway and data processing servers concurrently.

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

      Note During inplace upgrade, do not quit the configuration wizard. Complete the configuration steps on primary DPS first, and then on each gateway servers and then on secondary DPS.

      Note During side-by-side upgrade, after the GUI-mode installation completes, exit the wizard and run the configuration wizard later.

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

    ./install.sh -silent

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

When you choose to run the OBM installation on console mode, make sure to follow the instructions on the command shell. After the steps on the console window is complete, go to Initiate the upgrade process section to continue with the upgrade.

The below steps are applicable for GUI upgrade only. If you chose to run on console mode, then skip these steps and go to Initiate the upgrade process section.

Start the OBM 2020.05 installation

Invocation of the OBM 2020.05 installation is the same for both single server deployment types and gateway and data processing server in distributed deployment 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 staging 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

      You can run the install command on all the gateway and data processing servers concurrently.

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

      Note During inplace upgrade, do not quit the configuration wizard. Complete the configuration steps on primary DPS first, and then on each gateway servers and then on secondary DPS.

      Note During side-by-side upgrade, after the GUI-mode installation completes, exit the wizard and run the configuration wizard later.

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

    ./install.sh -silent

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

When you choose to run the OBM installation on console mode, make sure to follow the instructions on the command shell. After the steps on the console window is complete, go to Initiate the upgrade process section to continue with the upgrade.

The below steps are applicable for GUI upgrade only. If you chose to run on console mode, then skip these steps and go to Initiate the upgrade process section.

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

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

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

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 Single Server option. This option installs the active server and the backup server on the same system. Click Next to continue.

On a side-by-side > single server HA upgrade, this option installs primary production server and primary staging server on the same system.

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.

In GUI upgrade, you need to choose the installation type and the path manually.

Note If a previous version of OBM 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 Single Server option. This option installs the active server and the backup server on the same system. Click Next to continue.

On a side-by-side > single server HA upgrade, this option installs primary production server and primary staging server on the same system.

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.

In GUI upgrade, you need to choose the installation type and the path manually.

Note If a previous version of OBM 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 2020.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.

    In GUI upgrade, you need to choose the installation path manually as the settings are not populated from the previous installer values.

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

    In GUI upgrade, you need to choose the installation path manually as the settings are not populated from the previous installer values.

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

    In GUI upgrade, you need to choose the installation path manually as the settings are not populated from the previous installer values.

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

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 2020.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 2020.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 2020.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 2020.05 installation

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

In GUI mode, if you are upgrading from OBM 10.12IP6 to OBM 2020.05 the upgrade process requires certain registry cleanup where the installation directory is non-default. Once uninstallation is complete and installation of 2020.05 is launched, cancel the installation window and do the following:

Delete the registry entry along with all sub keys, if its present:

HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\BSM and HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP OpenView

Invoke a new instance of command prompt and run install.bat.

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

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

In GUI mode, if you are upgrading from OBM 10.12IP6 to OBM 2020.05 the upgrade process requires certain registry cleanup where the installation directory is non-default. Once uninstallation is complete and installation of 2020.05 is launched, cancel the installation window and do the following:

Delete the registry entry along with all sub keys, if its present:

HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\BSM and HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP OpenView

Invoke a new instance of command prompt and run install.bat.

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

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

In GUI mode, if you are upgrading from OBM 10.12IP6 to OBM 2020.05 the upgrade process requires certain registry cleanup where the installation directory is non-default. Once uninstallation is complete and installation of 2020.05 is launched, cancel the installation window and do the following:

Delete the registry entry along with all sub keys, if its present:

HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\BSM and HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP OpenView

Invoke a new instance of command prompt and run install.bat.

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

Installer Configuration

During the OBM 2020.05 install initialization phase, installer configuration window displays if any settings from the previous installer are detected. Click Yes to proceed.

Installation wizard: Install Config

Installer Configuration

During the OBM 2020.05 install initialization phase, installer configuration window displays if any settings from the previous installer are detected. Click Yes to proceed.

Installation wizard: Install Config

Installer Configuration

During the OBM 2020.05 install initialization phase, installer configuration window displays if any settings from the previous installer are detected. Click Yes to proceed.

Installation wizard: Install Config

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.

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.

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. Configure OBM 2020.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), the special configuration changes required to use the Oracle Database are automatically restored during silent upgrade. For more information, see Support for Oracle Real Application Cluster.

If the Oracle Database of your previous OBM environment is installed in a computer cluster based on Oracle Real Application Clusters (Oracle RAC), you had to specially configure your earlier OBM version to be able to use it. In this case, reapply these special configuration changes in OBM 2020.05. For more information, see Support for Oracle Real Application Cluster.

Optional. Configure OBM 2020.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), the special configuration changes required to use the Oracle Database are automatically restored during silent upgrade. For more information, see Support for Oracle Real Application Cluster.

If the Oracle Database of your previous OBM environment is installed in a computer cluster based on Oracle Real Application Clusters (Oracle RAC), you had to specially configure your earlier OBM version to be able to use it. In this case, reapply these special configuration changes in OBM 2020.05. For more information, see Support for Oracle Real Application Cluster.

Initiate the upgrade process

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

To initiate the first phase of the upgrade process for the production systemexisting BSM OBM host system, follow the steps:

Perform the following steps in order - Upgrade Primary DPS and enable Primary DPS then only start the upgrade of gateway server and enable the gateway server. After you complete upgrade on the gateway, start upgrade on the secondary DPS and enable the same.

Log in to the active data processing server of the production OBM environment. The active DPS is the one where the live bus is running. To determine the live bus server, run the following command on one of the data processing servers:

/opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver

Log in to the active data processing server of the production OBM environment. The active DPS is the one where the live bus is running. To determine the live bus server, run the following command on one of the data processing servers:

<OBM_HOME>/opr/support/opr-support-utils.bat -bus -getserver

Log in to the active data processing server of the production OBM environment. The active DPS is the one where the live bus is running. To determine the live bus server, run the following command on one of the data processing servers:

/opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver

Log in to the active data processing server of the production OBM environment. The active DPS is the one where the live bus is running. To determine the live bus server, run the following command on one of the data processing servers:

<OBM_HOME>/opr/support/opr-support-utils.bat -bus -getserver

Note Make sure to stop gateway servers and secondary DPS before you run the upgrade on primary DPS .

  1. You must run the following commands to stop services on the secondary DPS and gateways:

    <OBM_HOME>\bin\SupervisorStopAll (for OBM 2018.11 and later versions)

    <OBM_HOME>\SupervisorStop (for OBM 2018.05 and previous versions)

    You must run the following commands to stop services on the secondary DPS and gateways:

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

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

  2. Open a Command Promptterminal window as an administratorthe root user on primary DPS.

  3. Change the current directory to the location where you have extracted files from the OBM2020.05 installation package to as follows:

    cd <OBMInstallationFilesDirectory>

  4. Run the following command:

    upgrade.bat -s -silent

    upgrade.sh -s -silent

    Note The upgrade script changes the Event Forwarding Expiration to 336 hours (14 days). If you have previously modified the default value, make a note of the value before starting the upgrade so that you can restore the value in the later step. To make a note of the value, go to Administration > Setup and Maintenance > Infrastructure Settings > Operations Management - Event Synchronization Settings > Event Forwarding Expiration.

    The -s command runs the preliminary checks for the all services running on active DPS, if the live bus running on active DPS or not. It runs the pre-upgrade tool to stop the incoming events and wait for the event queue to be cleared. If you have an external database, the OBM services do not start or stop. If you are using embedded PostgreSQL, the upgrade script also stops OBM, backs up the database and starts OBM.

    The event flow is paused when the gateway server is stopped. The event flow is resumed on the production OBM after the primary DPS and atleast one of the gateway server upgrade is complete and OBM services is running.

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

    upgrade.bat -s -silent -archive=true

    upgrade.sh -s -silent -archive=true

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

    If you choose Y, you can archive the closed events in 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.bat -d-gui

    upgrade.sh -d-gui

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

    upgrade.bat -d -silent -gui -archive=true

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

    In GUI upgrade, you need to choose the installation type and the path manually.

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

    If you choose Y, you can archive the closed events in 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.bat -d -s

    upgrade.sh -d -s

    Note The upgrade script changes the Event Forwarding Expiration to 336 hours (14 days). If you have previously modified the default value, make a note of the value before starting the upgrade so that you can restore the value in the later step. To make a note of the value, go to Administration > Setup and Maintenance > Infrastructure Settings > Operations Management - Event Synchronization Settings > Event Forwarding Expiration.

    The -s command runs the preliminary checks for the all services running on active DPS, if the live bus running on active DPS or not. It runs the pre-upgrade tool to stop the incoming events and wait for the event queue to be cleared. If you have an external database, the OBM services do not start or stop. If you are using embedded PostgreSQL, the upgrade script also stops OBM, backs up the database and starts OBM.

    The event flow is paused when the gateway server is stopped. The event flow is resumed on the production OBM after the primary DPS and atleast one of the gateway server upgrade is complete and OBM services is running.

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

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

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

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

    If you choose Y, you can archive the closed events in 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.

    Initiate the upgrade on primary DPS first, then gateway server and then on secondary DPS as shown in the following table:

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

    Run the following command:

    upgrade.bat -d -silent -gui

    upgrade.sh -d -silent -gui

    Note Make sure the gateway server and secondary DPS are down.

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

    upgrade.bat -d -silent -archive=true -gui

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

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

    If you choose Y, you can archive the closed events in 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 2020.05 is installed and configured on the primary DPS, start the services on the primary DPS.

    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_2020.05._for_Windows and manually run install.bat.
     

    Note Do not proceed to upgrade the gateway servers and the secondary DPS until the primary DPS is upgraded and the services are started.

    For a gateway server

    You must the run the following command to stop the services:

    <OBM_HOME>\bin\SupervisorStopAll (for OBM 2018.11 and later versions)

    <OBM_HOME>\SupervisorStop (for OBM 2018.05 and previous versions)

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

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

    Run the following command:

    upgrade.bat -d -silent -gui

    upgrade.sh -d -silent -gui

    Note

    If the upgrade.bat.sh -d -silent 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 2020.05 is installed and configured on the gateway server, start the services on the gateway server. Do not proceed to upgrade the secondary DPS until the gateway servers are upgraded and the services are started.

    Note You can upgrade multiple gateway server concurrently to shorten the OBM server outage.

    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_2020.05._for_Windows and manually run install.bat.

    For a secondary DPS

    You must the run the following command to stop the services:

    <OBM_HOME>\bin\SupervisorStopAll (for OBM 2018.11and later versions)

    <OBM_HOME>\SupervisorStop (for OBM 2018.05 and previous versions)

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

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

    Run the following command:

    upgrade.bat -d -silent -gui

    upgrade.sh -d -silent -gui

    Note

    If the upgrade.bat.sh -d -silent 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_2020.05._for_Windows and manually run install.bat.

    After the secondary DPS is upgraded, that is, after OBM2020.05 is installed and configured on the secondary DPS, start the services on the secondary DPS.

     

    Run the following command on the active server of your existing OBM environment:

    upgrade.bat -s

    upgrade.sh -s

    The event flow is paused when the gateway server is stopped. The event flow is resumed on the production OBM after the active server and atleast one of the gateway server upgrade is complete and OBM services is running.

    After the active server is upgraded, that is, after OBM2020.05 is installed and configured on the active server, start the services on the active server. Do not proceed to upgrade the backup servers and any additional gateway servers until the active server is upgraded and the services are started.

    Note The upgrade script changes the Event Forwarding Expiration to 336 hours (14 days). If you have previously modified the default value, make a note of the value before starting the upgrade so that you can restore the value in the later step. To make a note of the value, go to Administration > Setup and Maintenance > Infrastructure Settings > Operations Management - Event Synchronization Settings > Event Forwarding Expiration.

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

    upgrade.bat -s -silent -archive=true

    upgrade.sh -s -silent -archive=true

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

    If you choose Y, you can archive the closed events in 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.

    Verify if the configuration wizard has run successfully by checking the configuration log file:

    The configuration wizard runs silently in the background.

    HPBSM\log\configserver\configserver_all.log

    Note If the upgrade fails before the configuration, you must run the upgrade in GUI mode again. If the configuration fails, you are required to run the configuration wizard manually.

    Verify if the configuration wizard has run successfully by checking the configuration log file:

    The configuration wizard runs silently in the background.

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

    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 you initiate the upgrade, follow the order to complete the upgrade process (for Single-server HA only):

    1. Stop the services on secondary production server
    2. Start upgrade process on primary production server
    3. Install and configure primary staging server. Wait until the primary staging server is completely installed and configured.
    4. Install and configure secondary staging server
    5. Enable primary staging server
    6. Enable secondary staging server

    Run the following command:

    upgrade.bat -d-gui

    upgrade.sh -d-gui

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

    upgrade.bat -d -silent -gui -archive=true

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

    In GUI upgrade, you need to choose the installation type and the path manually.

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

    If you choose Y, you can archive the closed events in 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.

    Verify if the configuration wizard has run successfully by checking the configuration log file:

    The configuration wizard runs silently in the background.

    HPBSM\log\configserver\configserver_all.log

    Note If the upgrade fails before the configuration, you must run the upgrade in GUI mode again. If the configuration fails, you are required to run the configuration wizard manually.

    Verify if the configuration wizard has run successfully by checking the configuration log file:

    The configuration wizard runs silently in the background.

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

    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.

Enable OBM services on primary DPS first. Then upgrade gateway server following the steps 1-3 and then enable OBM services on the gateway server . After you complete the upgrade primary DPS and gateway server , start the upgrade process on secondary DPS .

Enable OBM services on active server first. Then upgrade backup server following the steps 1-3 and then enable OBM services on the backup server. After you complete the upgrade active server and backup server, start the upgrade process on gateway server.

Attend the initial upgrade phase

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

  • The event queue is emptied on the primary DPS or active server.

  • 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: (./upgrade.sh) Upgrading from OMi/OBM version 1082
INFO: (./upgrade.sh) Checking for multiple DPS setup
INFO: Multiple DPS configured
INFO: More than one DPS connected
INFO: (./upgrade.sh) Multiple DPS detected. Will check for Active/Backup DPS
INFO: (./upgrade.sh) Checking if running on active DPS

 

INFO: (./upgrade.sh) Upgrading from OMi/OBM version 1063
INFO: Embedded Postgres database detected.
INFO: (./upgrade.sh) Running PreMigration Tool to prepare for Upgrade
INFO: (./upgrade.sh) Starting Pre Upgrade tool. Logs present in %OVDataDir%/log/opr-upgradeBackup.log
INFO: (./upgrade.bat) Upgrading from OMi/OBM version 1063
INFO: Embedded Postgres database detected.
INFO: (./upgrade.bat) Running PreMigration Tool to prepare for Upgrade
INFO: (./upgrade.bat) Starting Pre Upgrade tool. Logs present in %OVDataDir%/log/opr-upgradeBackup.log
 
INFO: (./upgrade.bat) Upgrading from OMi/OBM version 1082
INFO: (./upgrade.bat) Checking for multiple DPS setup
INFO: Multiple DPS configured
INFO: More than one DPS connected
INFO: (./upgrade.bat) Multiple DPS detected. Will check for Active/Backup DPS
INFO: (./upgrade.bat) Checking if running on active DPS

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.

Replicate the database schemasdatabasesCopy the database backup image

You must replicate (back up) the database schemasdatabases manually before continuing.

For embedded Postgres database, the upgrade script takes the backup of the database to %OVDataDir%/backup directory.

For embedded Postgres database, the upgrade script takes the backup of the database to /var/opt/OV/backup directory.

Replicate the following original OMi database schemas databases onto the staging OBM staging 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 new OBM2020.05 databases. Other BSM database schemasdatabases do not require replication, as they are not used in OBM and therefore not migrated.

Create a backup directory on OBM staging server using the command:

mkdir /var/opt/OV/backup

mkdir %OVDataDir%\backup

Copy the following file, which includes the database schema backup image, from the production OBM database host system to %OvDataDir%/OV/backup on the staging OBM database host system:

%OvDataDir%\backup\OMi10cfg-backup.zip

Copy the following file, which includes the database schema backup image, from the production OBM database host system to /var/opt/OV/backup on the staging OBM database host system:

/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 2020.05 databases.

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

Start OBM on production DPS and gateway servers as follows:

Check the service status window to ensure all listed services are appeared.

Run the following command: /opt/HP/BSM/scripts/run_hpbsm start

Configure event forwarding in the OBM production environment

Configure event forwarding in the OBM production environment

Replicate the database schemasdatabasesCopy the database backup image

You must replicate (back up) the database schemasdatabases manually before continuing.

For embedded Postgres database, the upgrade script takes the backup of the database to %OVDataDir%/backup directory.

For embedded Postgres database, the upgrade script takes the backup of the database to /var/opt/OV/backup directory.

Replicate the following original OMi database schemas databases onto the staging OBM staging 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 new OBM2020.05 databases. Other BSM database schemasdatabases do not require replication, as they are not used in OBM and therefore not migrated.

Create a backup directory on OBM staging server using the command:

mkdir /var/opt/OV/backup

mkdir %OVDataDir%\backup

Copy the following file, which includes the database schema backup image, from the production OBM database host system to %OvDataDir%/OV/backup on the staging OBM database host system:

%OvDataDir%\backup\OMi10cfg-backup.zip

Copy the following file, which includes the database schema backup image, from the production OBM database host system to /var/opt/OV/backup on the staging OBM database host system:

/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 2020.05 databases.

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

Start OBM on production DPS and gateway servers as follows:

Check the service status window to ensure all listed services are appeared.

Run the following command: /opt/HP/BSM/scripts/run_hpbsm start

Start the configuration wizard manually

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

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.

Run the configuration wizard on primary DPS first.

On a side-by-side HA environment, run the configuration wizard on the primary DPS of the OBM staging environment.

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:

      In Windows Search, 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.

Start the configuration wizard manually

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

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.

Run the configuration wizard on primary DPS first.

On a side-by-side HA environment, run the configuration wizard on the primary DPS of the OBM staging environment.

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:

      In Windows Search, 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.

Start the configuration wizard manually

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

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.

Run the configuration wizard on primary DPS first.

On a side-by-side HA environment, run the configuration wizard on the primary DPS of the OBM staging environment.

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:

      In Windows Search, 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.

Start the configuration wizard manually

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

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.

Run the configuration wizard on primary DPS first.

On a side-by-side HA environment, run the configuration wizard on the primary DPS of the OBM staging environment.

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:

      In Windows Search, 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.

Choose configuration options

This section is applicable for primary DPS, gateway server and secondary DPS.

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

This section is applicable for primary DPS, gateway server and secondary DPS.

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

This section is applicable for primary DPS, gateway server and secondary DPS.

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

This section is applicable for primary data processing server, gateway server and secondary data processing server.

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. Click Browse and choose the backup zip file.

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.

For side-by side single server HA, on the primary staging server, 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. Click Browse and choose the backup zip file.

For side-by side single server HA, on the secondary staging server, select Connect to an existing database or user schema 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. Click Browse and choose the backup zip file.

Select Connect to an existing database or user schema 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. Click Browse and choose the backup zip file.

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

This section is applicable for primary data processing server, gateway server and secondary data processing server.

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. Click Browse and choose the backup zip file.

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.

For side-by side single server HA, on the primary staging server, 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. Click Browse and choose the backup zip file.

For side-by side single server HA, on the secondary staging server, select Connect to an existing database or user schema 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. Click Browse and choose the backup zip file.

Select Connect to an existing database or user schema 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. Click Browse and choose the backup zip file.

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.