Operations Bridge Manager

For Windows® and Linux operating systems

Software Version: 2020.10

Customized output from:

Operations Bridge Manager 2020.10 Interactive Guide

Document Release Date: May 2020

Software Release Date: October 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 July 2, 2021

About this guide

Welcome to the Operations Bridge Manager 2020.10 Interactive Guide. This guide enables you to first specify the type of installationupgrade that you plan to perform. You can customize your content by selecting requirements and view or print the upgrade procedure.

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

Introduction

This document introduces you to the different methods available to upgrade or update OBM from older version to the latest version.

ClosedUpgrade

You can upgrade OBM from older versions to OBM 2020.10 version using inplace upgrade or side-by-side upgrade type.

Inplace upgrade:

In-place upgrade refers to installing OBM 2020.10 on the original host system. You can continue to use your original databases during the installation. In-place upgrade begin with an uninstallation, as OBM2020.10 replaces your earlier OBM version, resulting in greater downtime.

Side-by-side upgrade:

Side-by-side upgrade refers to installing OBM 2020.10 on different host systems and databases, to allow the original servers to continue functioning while the upgrade is in process. The original servers are referred 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.

ClosedUpdate

You can update OBM 2020.05 to OBM 2020.10 version. By default the update is performed using the inplace method.

You can choose to update OBM using distributed setup or single-server setup. In a distributed environment, there will be one instance of data processing server (DPS) and gateway server installed on different systems. In a Single-server environment, the gateway and the DPS are installed on the same host system.

It is possible to have minimal downtime if you are performing an update on OBM in high availability (HA) mode with minimum two gateway servers (GWS) and two DPS or Single Server in high availability (HA) mode.

You can choose your deployment based on your requirements before you upgrade or update.

ClosedDeployment type

  • Distributed: In this scenario, there will be one instance of gateway server installed on one system and the data processing server installed on another system. Distributed deployments can benefit from high availability and load balancing options.

  • Single-server: In this scenario, the gateway server and data processing server are installed on the same host system.

  • Distributed HA:

    During the upgrade process, the gateway server is installed on one system and the data processing server is installed on another system.

    During the update process, there will be two DPS and atleast two gateway servers running. You start the update process on inactive DPS and one of the gateway servers on HA environment while the remaining servers continue to run as it is. Then, switch over HAC services from non-updated DPS to updated DPS. Update the remaining non-updated servers concurrently.

    The servers used are Active DPS (HAC services are running) and Inactive or Backup DPS (HAC services do not run).

  • Single-server HA:

    During the upgrade process, you configure HA setup by adding a backup single-server.

    During the update process, you begin the update with one part of the OBM HA setup. Start the services on this setup. Switch over services to updated servers and then update the remaining part. In this scenario, updated and non-updated servers run concurrently.

    The servers used are Active server (HAC services are running) and Inactive or Backup server (HAC services do not run).

ClosedDeployment options

You can upgrade OBM from older version to the latest version by choosing one of the deployment methods:

  • Silent deployment: With silent deployment, you can perform both OBM upgrade and the subsequent configuration in a silent mode. The required values to complete the configuration is gathered 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).
  • GUI deployment: With GUI deployment, you can perform upgrade using the respective wizards by providing the required values. After running the upgrade, -gui the uninstallation wizard window is displayed. Perform the uninstallation and installation through the UI. The configuration takes place at the backgound silently. During configuration, the required values are automatically pre-populated in the configuration wizard.

System Requirements: To know more about the requirements for upgrade, read the sections, the hardware, software, network, and database requirements.

For a list of supported platforms, web browsers, and database management systems, select Operations Bridge Manager from the product list in the following document:

Support Matrices for Operations Center products

Choose the type

Upgrade from OBM 2019.11 and earlier
Update from OBM 2020.05

You can upgrade OBM from the following versions to OBM 2020.10:

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

Both in-place upgrade and side-by-side migration are supported.

The OBM upgrade runs in silent mode by default. By default, the Silent deployment option is selected 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 update from OBM 2020.05 to OBM 2020.10.

The OBM upgrade runs in silent mode by default. By default, the Silent deployment option is selected 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.

Choose the upgrade type

In-place upgrade
Side-by-side upgrade

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

During side-by-side upgrade, OBM 2020.10 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.10.

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
Single-server
Distributed HA
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.

A single-server deployment can be used for many upgrade 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.

The minimal downtime update is possible with minimum two gateway servers (GWS) and two data processing servers(DPS).

A Single-server HA deployment has two single server setup on a HA environment. 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.

The Minimal downtime update is possible with Single server HA setup.

Choose the database management system

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

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.

Choose the operating system

Microsoft Windows
Linux

Choose Operating system of OBM where you want to upgrade/update.

Select deployment options

Silent deployment
GUI deployment

We recommend to use the Silent deployment. However, you can choose to upgradeupdate in Silent mode or GUI mode based on your upgradeupdate scenario.

If you have configured symbolic links, select the GUI deployment option.

In GUI deployment mode, the configuration happens silently in the background. If you have configured symbolic links, make a note of it before initiating the upgradeupdate.

Select additional options

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

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.

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 interactive document, refer Online Interactive document for the latest updates.

Legal notice

By selecting not to encrypt credentials in configuration file, 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. The following table lists the CPU requirements. 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.

    Deployment Single Server
    Small (up to 2,000 nodes) Minimum 4
    Recommended 5
    Deployment Single Server Data Processing Server Gateway Server
    Small (up to 2,000 nodes) Minimum 4 3 2
    Recommended 5 4 3
    Medium (up to 5,000 nodes) Minimum 7 5 3
    Recommended 8 6 4
    Large (more than 5,000 nodes) Minimum 11 8 4
    Recommended 12 9 5
    Deployment Single Server Data Processing Server Gateway Server
    Small (up to 2,000 nodes) Minimum 4 3 2
    Recommended 5 4 3
    Medium (up to 5,000 nodes) Minimum 7 5 3
    Recommended 8 6 4
    Large (more than 5,000 nodes) Minimum 11 8 4
    Recommended 12 9 5

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

    Deployment Single Server
    Small (up to 2,000 nodes) Minimum 14
    Recommended 16
    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
    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.

    Note The required memory shown in the Configuration Wizard is calculated dynamically based on the memory that is given to all the processes which make up the OBM server. It also takes into account the overrides which a customer might do in the Advanced section. However, it does not include any other consumers of memory on the system, like the basic OS processes/services or CLIs which also need a considerable amount of the available memory. The memory requirement values provided in the table take these into consideration and are therefore higher.

    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 the single serverdata processing server.

  • Disk Space: If you have problems with your disk space, consider removing non-required files from the file system.

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

    Default Directory Minimum Recommended
    /opt/HP/BSM 31 50
    /opt/OV 1 1
    /var/opt/OV 1118 22212
    /tmp

    1212

    		20

    Note: When using an embedded PostgreSQL database, minimum extra free disk space equal to the file size of /var/opt/OV/databases/omidb is require on /var/opt/OV.

    Note: Embeded PostgreSQL database resides on /var/opt/OV/databases folder, as with time the data grows in database we recommend that you have sufficient free disk space available in /var/opt/OV.

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

    Default Folder Minimum Recommended

    C:\HPBSM

    		31 50

    C:\ProgramFiles\HP\HP BTO Software

    88

    1212

    C:\ProgramData\HP\HP BTO Software

    111

    222

    %TEMP% *

    1212

    		20

    * This is a user environment variable

    Note: When using an embedded PostgreSQL database, minimum extra free disk space equal to the file size of %ovdatadir%/databases/omidb is require on %ovdatadir%.

    Note: Embeded postgresql database resides on %ovdatadir%/databases/omidb folder, as with time the data grows in database we recommend that you have sufficient free disk space available in %ovdatadir%.

  • Supported mount option: The mount option supported is nodev.

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

  • Init scripts. OBM requires the initscripts package.

  • Perl. OBM requires the Perl package.

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

  • PNG support libraries. OBM requires the libpng12 package.

  • libXtst extension library. On all machines on which you want plan to install OBM, you must install the RPM package libXtst.

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

  • M4 packages. The Operations Agent requires this package.

  • Fontconfig package. OBM requires the fontconfig package.

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

Run the following command to install the above mentioned packages:

If you have RHEL 7.x:

yum install -y unzip initscripts perl libaio libpng12.x86_64 libXtst openssl fontconfig m4

If you have RHEL 8.x:

yum install -y unzip initscripts perl libaio libpng12.x86_64 libXtst libnsl ncurses-libs openssl fontconfig m4

Or

dnf install -y unzip initscripts perl libaio libpng12.x86_64 libXtst libnsl ncurses-libs openssl fontconfig m4

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

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

    Run the following command to install this package:

    yum groupinstall "X Window System"

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

    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 getent host 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 agent 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 agent 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 uses its own web server (Apache httpd) and installs it as part of the installation process

    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. OBM uses its own web server (Apache httpd) and installs it as part of the installation process

    OBM deployment requires a web server. OBM uses its own web server (Apache httpd) and installs it as part of the installation process.

    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.10 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.10. Download the archive file to the system where you plan to install OBMwhich you plan to upgrade to OBM 2020.10, 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.

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.2 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.2 or later (Java Control Panel > Advanced > Advanced Security Settings).

  • 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 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 on the productions servers. 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 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 on the productions servers. 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.

  • 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 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 on the productions servers. 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.

  • 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 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 on the productions servers. 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 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 on the productions servers. 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.

  • 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 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 on the productions servers. 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.

  • 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 upgrade OBM and to configure it. The root user account must be allowed to run the sudo command to permit it to run install and configuration commands as the specified (non-root user)., you must update the sudoers file with the following permission: root ALL = ( ALL ) ALL.

    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 installationupgrade must have administrative privileges on the host systems.

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

    • CONNECT

    • CREATE PROCEDURE

    • CREATE SEQUENCE

    • CREATE TABLE

    • CREATE TRIGGER

    • ALTER USER

    • CREATE VIEW

    • UNLIMITED TABLESPACE

    • SELECT ON sys.props$

    • SELECT ON sys.ALL_USERS

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

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

    • Support for your database management system. Check the OBM 2020.10 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.10 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)

    • Backup the L-core certificates on all OBM servers. For example:

      tar czvf /backup/cs.tar.gz /var/opt/OV/shared/server/datafiles/sec/cs

      tar czvf /backup/agent-certs.tar.gz /var/opt/OV/datafiles/sec/ks

      %OvDataDir%\datafiles\sec\ks

      %OvDataDir%\shared\server\datafiles\sec\ks

    • Backup certificates for all OBM-integrated products in your environment.

    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

      OR

      <HPEBSMrootDirectory><OBM_HOME>/\odb/\conf/\jdbc.properties for versions 2018.11 and earlier.

    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 Install the Data Flow Probe.

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

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

      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.

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

      <OBM_HOME>/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:

      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 and continue the upgrade process.

      <OBM_HOME>/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_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. Follow these steps to avoid data loss during the upgrade:

    1. Run the following command to stop 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 and 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.

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

    When you run the checkIndices command, the following options are available:

    -c, --create Create missing indices
    -h, --help Help
    -s, --show Show missing indices
    -v, --verbose Show verbose output

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

OBM Version and Integration Check Tools

If you are planning to installupgrade OBM version to the latest version, you can use the following 2 tools available on ITOM Marketplace , which will ease your installationupgrade 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 LinuxWindows) 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.10.

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

    • Support for your database management system. Check the OBM 2020.10 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.10 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)

    • Backup the L-core certificates on all OBM servers. For example:

      tar czvf /backup/cs.tar.gz /var/opt/OV/shared/server/datafiles/sec/cs

      tar czvf /backup/agent-certs.tar.gz /var/opt/OV/datafiles/sec/ks

      %OvDataDir%\datafiles\sec\ks

      %OvDataDir%\shared\server\datafiles\sec\ks

    • Backup certificates for all OBM-integrated products in your environment.

    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

      OR

      <HPEBSMrootDirectory><OBM_HOME>/\odb/\conf/\jdbc.properties for versions 2018.11 and earlier.

    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 Install the Data Flow Probe.

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

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

      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.

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

      <OBM_HOME>/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:

      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 and continue the upgrade process.

      <OBM_HOME>/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_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. Follow these steps to avoid data loss during the upgrade:

    1. Run the following command to stop 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 and 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.

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

    When you run the checkIndices command, the following options are available:

    -c, --create Create missing indices
    -h, --help Help
    -s, --show Show missing indices
    -v, --verbose Show verbose output

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

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.

Configure event buffering in OM for Windows

  1. Log on to OM.

  2. In the console tree, right-click Operations Manager, and then click Configure > Server.... The Server Configuration dialog box appears.

  3. Click Namespaces, and then click Server-based Flexible Management.

  4. Note the values of Forwarding delivery timeout (in seconds) and Forwarding queue size maximum (in megabytes). Record these values to enable you to restore them after the upgrade.

  5. Change the value of Forwarding delivery timeout (in seconds) (1 hour by default). For example, to set the timeout to 7 days, type 604800.

  6. Change the value of Forwarding queue size maximum (in megabytes) (50 MB by default). For example, to set the buffer size to 2 GB, type 2000.

  7. Optional. Change the value of Forwarding queue size warning threshold (in megabytes) (40 MB by default). For example, to set the warning threshold to 2 GB, type 2000.

  8. Click OK to save the new values and close the dialog box.

Configure event buffering in OM for UNIX or Linux

  1. Optional. To check the current values of the HTTPS-based event forwarding configuration, run the following command:

    ovconfget -ovrg server opc.opcforwm

    The command displays only the non-default values. Record these values to enable you to restore them after the upgrade.

  2. Adjust the timeout. For example, to set the timeout to 7 days, run the following command:

    ovconfchg -ovrg server -ns opc.opcforwm -set REQUEST_TIMEOUT 604800

  3. Optional. In OM for UNIX or Linux, the buffer size is by default unlimited (set to the value 0). To adjust the buffer size, run the following command:

    ovconfchg -ovrg server -ns opc.opcforwm -set MAX_FILE_BUFFER_SIZE <NumberOfBytes>

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

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.

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.10. Therefore, first upgrade all configured servers of the existing deployment to OBM 2020.10, 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.

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

  • Each OBM server should be sized appropriately as per the deployment size and capacity calculator.

Note: You must back up symbolic links in your existing OBM host systems and recreate them manually before the new OBM version is installed.

Note: Select the GUI deployment option on the previous page if you have configured symbolic links.

Database maintenance to expedite the upgrade process

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

Embedded PostgreSQL

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.

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

Set max_locks_transactions DB parameters

For the upgrade process to be successful, the max_locks_per_transaction setting of PostgreSQL DB in postgresql.conf 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 updateupgrade 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 updateupgrade process.

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

Set max_locks_transactions DB parameters

For the upgrade process to be successful, the max_locks_per_transaction setting of PostgreSQL DB in postgresql.conf 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. 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/[sqlserveroracle].

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/opr/support/database/[sqlserveroracle].

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

For options to pass the arguments, see opr-archive-events Command-Line Tool

Prerequisites

  • Storage disk space: Ensure minimum 12GB and recommended 20GB free storage disk space available in /tmp folder.

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

  • Fully qualified domain names (FQDNs). Each OBM server must have a resolvable FQDN. To verify it, run the hostname and getent hostsnslookup 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 (.)

System requirements

  • The hardware, software, network, and database requirements are listed in the OBM Interactive document. To view the requirements page, choose the "Upgrade" option in the selection page.
  • For a list of supported platforms, web browsers, and database management systems, select Operations Bridge Manager from the product list in the following document: Support Matrices for Operations Center products.

System-wide privileges

You must use the root user account to upgrade OBM and to configure it. To permit it to run install and configuration commands as the specified (non-root user), you must update the sudoers file with the following permission: root ALL = ( ALL ) ALL.

Considerations

  • Minimal downtime is possible when you have two DPS and atleast two gateway serverstwo single servers configured on high availability (HA) mode.
  • Each OBM server should be sized appropriately as per the deployment size and capacity calculator.
  • If the integrations are not blocked during the OBM update, the buffered data (events, metrics, topology, incidents) is sent as soon as the OBM server is reachable again.

  • During the update GWS will be updated one by one. The remaining ones should be able to handle user and data traffic.

  • It is advised to take backup of existing DB, and if you are using virtual machines take snapshots before the update.

  • Inform the remaining connected users that they might see a short disruption in their user sessions and may have to log out and log in again.

  • Do not attempt to disable or uninstall OBM before initiating the update process. A disabled or uninstalled OBM might cause loss of events that originate from the monitored environment.

  • When the load balancer’s gateway monitoring detects that one of the GWS is no longer accessible, it will move all connections (including the “sticky session” ones) to an available GWS. TLS connections will be disconnected, and data collectors like OM will try to re-establish to the newly assigned GWS.

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

    • Backup the L-core certificates on all OBM servers. For example:

      tar czvf /backup/cs.tar.gz /var/opt/OV/shared/server/datafiles/sec/cs

      tar czvf /backup/agent-certs.tar.gz /var/opt/OV/datafiles/sec/ks

      %OvDataDir%\datafiles\sec\ks

      %OvDataDir%\shared\server\datafiles\sec\ks

    • Backup certificates for all OBM-integrated products in your environment.

    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.

Database maintenance to expedite the upgrade process

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

Embedded PostgreSQL

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.

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

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/[sqlserveroracle].

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/opr/support/database/[sqlserveroracle].

Overview

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

On a distributed HA environment, there are two data processing server (DPS) and atleast two gateway servers available. The servers used are:

  • Active DPS: On this server the HAC services are running.
  • Inactive DPS (backup DPS): On this server the HAC services are not running.

Below is the overview on how to update your OBM 2020.05 to OBM 2020.10 version. The steps are explained in detail in further documentation.

  1. Start update on inactive DPS and one of the gateway servers. While inactive DPS is updated, all gateways & active DPS still process events.

  2. Remember that the updated DPS will start as a backup DPS and hence HAC services will not be active. Move the HAC services from the active DPS to the updated DPS. During the short time of DPS services switch, gateway servers are buffering data.

  3. Now, the remaining DPS and gateway servers can be updated one after the other or concurrently depending on OBM usage/load. Make sure there are always enough gateway servers running to handle the load.

  4. Remember that the newly updated DPS will start as a backup DPS since the HAC services were moved in step 2, the HAC services will not be active on this.

  5. In case you had reduced the number of concurrent users, allow full concurrent user access again.

Expected downtime for the above update procedure:

Minimal downtime can be comparable to time required for HAC switchover time from non updated to updated server.

On a single-server HA environment, there are two single-server setups and additional gateway servers, if any. The servers used are:

  • Active server: On this server the HAC services are running.
  • Inactive server(backup server): On this server the HAC services are not running.

Below is the overview on how to update your OBM 2020.05 to OBM 2020.10 version. The steps are explained in detail in further documentation.

  1. Start update on inactive server and one of the gateway servers. While inactive server is updated, all gateways & active server still process events.

  2. Remember that the updated server will start as a backup server and hence HAC services will not be active. Move the HAC services from the active server to the updated server. During the short time of server services switch, gateway servers are buffering data.

  3. Now, the remaining server and gateway servers can be updated one after the other or concurrently depending on OBM usage/load. Make sure there are always enough gateway servers running to handle the load.

  4. Remember that the newly updated server will start as a backup server since the HAC services were moved in step 2, the HAC services will not be active on this.

  5. In case you had reduced the number of concurrent users, allow full concurrent user access again.

Expected downtime for the above update procedure:

Minimal downtime can be comparable to time required for HAC switchover time from non updated to updated server.

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 uninstallation of the earlier OBM/OMi version and the invocation of the 2020.10 installation.

  4. Install OBM 2020.10 by following the instructions of the installation wizard.

  5. The configuration of the OBM 2020.10 will take place silently in the background.

  6. Enable OBM services.

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

  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 uninstallation of the earlier OBM/OMi version and the invocation of the 2020.10 installation.

  4. Install OBM 2020.10 on the active system that will host the new version by following the instructions of the installation wizard.

  5. The configuration of the OBM 2020.10 will take place silently in the background.

  6. Enable OBM services.

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

  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 and enable secondary staging server.
  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 OBM/OMi version is enabled (all services are running on the production environment).
  2. On the host system of your staging server, start the 2020.10 installation.
  3. Install OBM 2020.10 by following the instructions of the installation wizard.
  4. On the production server, initiate the upgrade process and attend the initial upgrade phase.
  5. Follow the instructions of the configuration/upgrade wizard on staging server, and conclude the upgrade process.

  1. Make sure that the earlier OBM/OMi version is enabled.

  2. On the single-server of your existing OBM/OMi deployment, initiate the upgrade process.

  3. The uninstallation of older version and the installation and configuration of the new version takes place silently in the background.

  4. Enable the OBM services.

  1. Before initiating the upgrade on DPS, make sure to stop the OBM services on all gateways servers.

  2. Initiate the upgrade process on DPS. The uninstallation of older version and the installation and configuration of the new version takes place silently in the background.

  3. Enable the OBM services.
  4. After DPS upgrade is complete, initiate the upgrade on remaining gateway servers.

  1. Before initiating the upgrade on DPS, make sure to stop the OBM services on all gateways servers.

  2. Initiate the upgrade process on DPS. The uninstallation of older version and the installation and configuration of the new version takes place silently in the background.

  3. Enable the OBM services.
  4. After DPS upgrade is complete, initiate the upgrade on remaining gateway servers.

Upgrade the older OMi/OBM version to OBM 2020.10 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.

ClosedOn primary data processing server (DPS)

When you upgrade the primary DPS, the OBM services on the gateway server and secondary DPS must be down.

Complete the upgrade of Primary DPS before starting gateway server or secondary DPS.

  1. On the host system of the primary (first installed) DPS in your existing OMi/OBM environment, initiate the upgrade process using the upgrade script.
  2. Attend uninstallation of the earlier OMi/OBM version and invocation of the installation wizard.
  3. Install OBM 2020.10 by following the instructions of the installation wizard.
  4. The configuration of the OBM 2020.10 will take place silently in the background.
  5. Start OBM services on the primary DPS.
ClosedOn each gateway server

Make sure you have completed the upgrade of Primary DPS before you start to upgrade gateway server.

  1. Initiate the upgrade process.
  2. Attend uninstallation of the earlier OBM version and invocation of the installation wizard.
  3. Install OBM 2020.10 by following the instructions of the installation wizard.
  4. The configuration of the OBM 2020.10 will take place silently in the background.
  5. Start OBM services on the gateway server.
ClosedOn secondary data processing server (DPS)

Complete the upgrade of Primary DPS before starting gateway server or secondary DPS.

  1. Perform the following steps on secondary DPS:
  2. Initiate the upgrade process.
  3. Attend uninstallation of the earlier OBM version and invocation of the installation wizard.
  4. Install OBM 2020.10 by following the instructions of the installation wizard.
  5. The configuration of the OBM 2020.10 will take place silently in the background.
  6. Start OBM services on the additional DPS.

Upgrade the older OMi/OBM version to OBM2020.10 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.

ClosedOn primary data processing server (DPS)

When you upgrade the primary DPS, the OBM services on the gateway server and secondary DPS must be down.

Complete the upgrade of Primary DPS before starting gateway server or secondary DPS.

  1. On the host system of the primary (first installed) DPS in your existing OMi/OBM environment, initiate the upgrade process using the upgrade script.
  2. Attend uninstallation of the earlier OMi/OBM version and invocation of the installation wizard.
  3. Install OBM 2020.10 by following the instructions of the installation wizard.

  4. The configuration of the OBM 2020.10 will take place silently in the background.

  5. After the configuration/upgrade wizard is complete, start OBM services on the primary DPS.
ClosedOn each gateway server

Make sure you have completed the upgrade of Primary DPS before you start to upgrade gateway server.

  1. Initiate the upgrade process.
  2. Attend uninstallation of the earlier OBM version and invocation of the installation wizard.
  3. Install OBM 2020.10 by following the instructions of the installation wizard.

  4. The configuration of the OBM 2020.10 will take place silently in the background.

  5. After the configuration/upgrade wizard is complete, start OBM services on the gateway server.
ClosedOn secondary data processing server (DPS)

Complete the upgrade of Primary DPS before starting gateway server or secondary DPS.

  1. Perform the following steps on secondary DPS:
  2. Initiate the upgrade process.
  3. Attend uninstallation of the earlier OBM version and invocation of the installation wizard.
  4. Install OBM 2020.10 by following the instructions of the installation wizard.

  5. The configuration of the OBM 2020.10 will take place silently in the background.

  6. After the configuration/upgrade wizard is complete, start OBM services on the additional DPS.

Before you upgradeupdate

The upgradeupdate tool uninstalls all previous OBM versions, including IPs (intermediate patches). The tool temporarily backs up part of the configuration and certificates to help you migrate them to the OBM 2020.10 version. Make sure to close all the files and directory that belongs to <OBM_HOME> 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 upgradeupdate both data processing servers when they are inactive is currently not supported.

Optional. By default, the upgradeupdate installs OBM 2020.10 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. Create the file outside the OBM <installationfiles> directory.

Caution Do not create the ovinstallparams.ini in <TOPAZ_HOME>, IATEMPDIR and %temp% directory, as during the OBM uninstallation, these files will get erased.

Create an empty file and copy the following section to the ovinstallparams.ini file on the OBM staging servers: 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 upgradeupdate installs OBM2020.10 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. Create the file outside the OBM <installationfiles> directory.

                                                                            

                                                                            

                                                                                
Caution Do not create the ovinstallparams.ini in <TOPAZ_HOME>,  IATEMPDIR and %temp% directory, as during the OBM uninstallation, these files will get erased.

                                                                            

                                                                            
Create an empty file and copy the following section to the ovinstallparams.ini file on the OBM staging servers: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 upgradeupdate installs OBM2020.10 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. Create the file outside the OBM <installationfiles> directory.

                                                                                
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. 

                                                                            

                                                                            

                                                                                
Caution Do not create the ovinstallparams.ini in <TOPAZ_HOME>,  IATEMPDIR and %temp% directory. During the OBM uninstallation, these files will get erased.

                                                                            

                                                                            
Create an empty file and copy the following section to the ovinstallparams.ini file on the OBM staging servers:
                                                                            

                                                                            
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.

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            

                                                                                
Optional. By default, the upgradeupdate installs OBM2020.10 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. Create the file outside the OBM <installationfiles> directory.

                                                                                
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. 

                                                                            

                                                                            

                                                                                
Caution Do not create the ovinstallparams.ini in <TOPAZ_HOME>,  IATEMPDIR and %temp% directory, as during the OBM uninstallation, these files will get erased.

                                                                            

                                                                            
Create an empty file and copy the following section to the ovinstallparams.ini file on the OBM staging servers:
                                                                            

                                                                            
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

                                                        

                                                            

                                                                

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user.
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    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 single server, if the live bus running on single server 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 upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh  -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                            
    5. 
                                                                        

                                                                    

                                                                

                                                                

                                                                    

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

                                                                        

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

                                                                        

                                                                        
    
                                                                            
  1. 
                                                                                
    Ensure the HAC services and the live bus are not running on the secondary DPS.
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      
                                                                                            
      To check the status of the HAC services, run the following command:
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                                
      
                                                                                            
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                                
      
                                                                                            
      
                                                                                            
      If the HAC services are running on the secondary DPS, reassign the services from secondary DPS to primary DPS. To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                        
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      To check the live bus status run the following command:
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                            
      
                                                                                        
      
                                                                                        
      If the live bus is running on the secondary DPS, reassign the live bus from secondary DPS to primary DPS. To assign live bus to primary DPS, run the following command:
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                            
      
                                                                                        
      
                                                                                    
      3. 
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    
                                                                                    
    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)
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user on primary DPS.
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Run the following command on the primary DPS of your existing OBM environment:
    
                                                                                
    
                                                                                    
    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 upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh  -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                            
    6. 
                                                                        

                                                                    

                                                                

                                                                

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    For non-root installation, extract the files in / directory.
    
                                                                                    
    
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Run the following command:
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent
                                                                                            
    
                                                                                            
    The -silent command by default, installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -gui
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed after the upgrade has finished and OBM is running.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    
                                                                                        
    upgrade.bat -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent -archive=true
    
                                                                                            
    The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -archive=true -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent -archive=true
                                                                                        
    
                                                                                        
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
     ./upgrade.sh -d -gui -archive=true
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    In GUI upgrade, you need to choose the installation type and the path manually.
    
                                                                                
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Check if the L-Core certificates are present, run the following command:
    
                                                                                
    ovcert -list
                                                                                
    
                                                                                
    If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
    
                                                                                
    Stop agent process:
    
                                                                                
    ovc -kill
                                                                                
    
                                                                                
    To restore agent certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/agent-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    To restore server certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/cs-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    Start the agent process again:
    
                                                                                
    ovc -start
                                                                                
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
    
                                                                                
    
                                                                                    
    Run  the following command to check the process status:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
    
                                                                                
    
                                                                                
    After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.
    
                                                                            
    7. 
                                                                        

                                                                        

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
This section applies only to the host system of the data processing server (DPS) in your BSMOBMexisting OBM deployment.

                                                                        

                                                                        

                                                                            

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

                                                                                
If you want to perform upgrade with minimal downtime, go back to the selection page and choose Distributed HA deployment.

                                                                            

                                                                        

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

                                                                        
Perform the following steps in order - Upgrade primary DPS and enable primary DPS then only start the upgrade of remaining gateway server and enable the gateway server.

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    
                                                                                    
    You must run the following commands  to stop services on the remaining 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 remaining gateway servers as non-root user:
    
                                                                                    
    /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)
    
                                                                                
    
                                                                                
    The  event flow is paused when the gateway server is stopped. It is resumed on the production OBM after the DPS and atleast one of the gateway server upgrade is complete and OBM services is running.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Initiate the upgrade on primary DPS first, then gateway server. 
    
                                                                                
    On the DPS, follow these steps:
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Open a Command Promptterminal window as an administratorthe root user on primary DPS.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package. 
      
                                                                                        
      
                                                                                            
      
                                                                                                
      For non-root installation, extract the files in / directory.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                        
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Run the following command:
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini> 
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui -archive=true
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent-archive=true
                                                                                                    
      
                                                                                                    
      The -silent command, by default installs the ovinstallparams.ini file in the  to the same drive where the previous version is installed.
      
                                                                                                    
      Optional.To customize the ovinstallparams.ini file location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                    
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent -archive=true
                                                                                                
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui -archive=true
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                        
      
                                                                                    
      4. 
                                                                                    
    4. 
                                                                                        
      Check if the L-Core certificates are present, run the following command:
      
                                                                                        
      ovcert -list
                                                                                        
      
                                                                                        
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                        
      Stop agent process:
      
                                                                                        
      ovc -kill
                                                                                        
      
                                                                                        
      To restore agent certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/agent-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      To restore server certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/cs-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      Start the agent process again:
      
                                                                                        
      ovc -start
                                                                                        
      
                                                                                    
      5. 
                                                                                    
    5. 
                                                                                        
      
                                                                                            
      Enable OBM services on primary DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                
      
                                                                                                
      
                                                                                                    
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                
      
                                                                                                
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                            
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                
      
                                                                                                
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                        
      Run the following command to check the process status:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                        
      
                                                                                    
      6. 
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    On gateway server, follow these steps. If there are multiple gateway servers, you can upgrade one gateway server at a time or multiple gateway servers concurrently. 
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Open a Command Promptterminal window as an administratorthe root user on gateway server.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                        
      
                                                                                            
      
                                                                                                
      For non-root installation, extract the files in / directory.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                        
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Run the following command
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                    
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                    
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                                
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      Note 
                                                                                                    
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                    
       
      
                                                                                                    
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      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. 
                                                                                                
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                                
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                            
      
                                                                                            
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                        
      
                                                                                    
      4. 
                                                                                    
    4. 
                                                                                        
      Check if the L-Core certificates are present, run the following command:
      
                                                                                        
      ovcert -list
                                                                                        
      
                                                                                        
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                        
      Stop agent process:
      
                                                                                        
      ovc -kill
                                                                                        
      
                                                                                        
      To restore agent certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/agent-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      To restore server certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/cs-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      Start the agent process again:
      
                                                                                        
      ovc -start
                                                                                        
      
                                                                                    
      5. 
                                                                                    
    5. 
                                                                                        
      
                                                                                            
      Enable OBM services on gateway server. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                
      
                                                                                                
      
                                                                                                    
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                
      
                                                                                                
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                            
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                
      
                                                                                                
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                
      
                                                                                            
      
                                                                                            
      Run the following command to check the process status:
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                                
      
                                                                                            
      
                                                                                            
      
                                                                                                
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      6. 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    On secondary DPS, follow these steps:
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Open a Command Promptterminal window as an administratorthe root user on secondary DPS.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                        
      
                                                                                            
      
                                                                                                
      For non-root installation, extract the files in / directory.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                        
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Run the following command:
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                    
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                    
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                                
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      Note 
                                                                                                    
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                    
       
      
                                                                                                    
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                            
      After the secondary DPS  is upgraded, that is,  after OBM2020.10 is installed and configured on the secondary DPS, start the services on the secondary 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. 
                                                                                                
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                                
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                            
      
                                                                                            
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                        
      
                                                                                    
      4. 
                                                                                    
    4. 
                                                                                        
      Check if the L-Core certificates are present, run the following command:
      
                                                                                        
      ovcert -list
                                                                                        
      
                                                                                        
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                        
      Stop agent process:
      
                                                                                        
      ovc -kill
                                                                                        
      
                                                                                        
      To restore agent certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/agent-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      To restore server certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/cs-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      Start the agent process again:
      
                                                                                        
      ovc -start
                                                                                        
      
                                                                                    
      5. 
                                                                                    
    5. 
                                                                                        
      
                                                                                            
      
                                                                                                
      Enable OBM services on DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                                
      
                                                                                                    
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                    
      
                                                                                                    
      
                                                                                                        
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                    
      
                                                                                                    
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                                
      
                                                                                                
      
                                                                                                    
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                    
      
                                                                                                    
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                    
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                            
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                            
      
                                                                                                
      Run the following command to check the process status:
      
                                                                                                
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                                
      
                                                                                            
      
                                                                                            
      
                                                                                                
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      6. 
                                                                                
    
                                                                            
    6. 
                                                                        

                                                                        

                                                                            
After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
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 OBM host system, follow the steps:

                                                                        
    
                                                                            
  1. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user on active server.
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Run the following command on the active server of your existing OBM environment:
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh -s -silent
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                                
    After the active server is upgraded, that is, after OBM2020.10 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 lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh  -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                            
    4. 
                                                                        

                                                                        
After you initiate the upgrade, follow the order to complete the upgrade process:

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

                                                                    

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    
                                                                                    
    
                                                                                        
    You must run the following commands  to stop services on the remaining inactive single server and gateway servers:
    
                                                                                        
    <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 remaining inactive single server and gateway servers as non-root user:
    
                                                                                        
    /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)
    
                                                                                    
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user on active server.
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    For non-root installation, extract the files in / directory.
    
                                                                                    
    
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Run the following command:
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent
                                                                                            
    
                                                                                            
    The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -gui
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed after the upgrade has finished and OBM is running.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    
                                                                                        
    upgrade.bat -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent-archive=true
                                                                                            
    
                                                                                            
    The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent -archive=true
                                                                                        
    
                                                                                        
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    In GUI upgrade, you need to choose the installation type and the path manually.
    
                                                                                
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    Check if the L-Core certificates are present, run the following command:
    
                                                                                
    ovcert -list
                                                                                
    
                                                                                
    If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
    
                                                                                
    Stop agent process:
    
                                                                                
    ovc -kill
                                                                                
    
                                                                                
    To restore agent certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/agent-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    To restore server certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/cs-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    Start the agent process again:
    
                                                                                
    ovc -start
                                                                                
    
                                                                            
    7. 
                                                                            
  7. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
    
                                                                                
    
                                                                                    
    Run the following command to check the process status:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
    
                                                                                
    
                                                                            
    8. 
                                                                        

                                                                        
Enable OBM services on active server  first. Then upgrade backup server following the steps 1-4 1-5 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.

                                                                        

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                            

                                                                

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    For non-root installation, extract the files in / directory.
    
                                                                                    
    
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Run the following command:
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent
                                                                                            
    
                                                                                            
    The -silent command by default, installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -gui
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed after the upgrade has finished and OBM is running.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    
                                                                                        
    upgrade.bat -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent -archive=true
    
                                                                                            
    The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -archive=true -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent -archive=true
                                                                                        
    
                                                                                        
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
     ./upgrade.sh -d -gui -archive=true
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    In GUI upgrade, you need to choose the installation type and the path manually.
    
                                                                                
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Check if the L-Core certificates are present, run the following command:
    
                                                                                
    ovcert -list
                                                                                
    
                                                                                
    If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
    
                                                                                
    Stop agent process:
    
                                                                                
    ovc -kill
                                                                                
    
                                                                                
    To restore agent certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/agent-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    To restore server certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/cs-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    Start the agent process again:
    
                                                                                
    ovc -start
                                                                                
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
    
                                                                                
    
                                                                                    
    Run  the following command to check the process status:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
    
                                                                                
    
                                                                                
    After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.
    
                                                                            
    7. 
                                                                        

                                                                        

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        
This section applies only to the host system of the data processing server (DPS) in your BSMOBMexisting OBM deployment.

                                                                    

                                                                    

                                                                        

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

                                                                            
If you want to perform upgrade with minimal downtime, go back to the selection page and choose Distributed HA deployment.

                                                                        

                                                                    

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

                                                                    
Perform the following steps in order - Upgrade primary DPS and enable primary DPS then only start the upgrade of remaining gateway server and enable the gateway server.

                                                                    
    
                                                                        
  1. 
                                                                            
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                            
    
                                                                                
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                
    
                                                                            
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    
                                                                                
    You must run the following commands  to stop services on the remaining 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 remaining gateway servers as non-root user:
    
                                                                                
    /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)
    
                                                                            
    
                                                                            
    The  event flow is paused when the gateway server is stopped. It is resumed on the production OBM after the DPS and atleast one of the gateway server upgrade is complete and OBM services is running.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Initiate the upgrade on primary DPS first, then gateway server. 
    
                                                                            
    On the DPS, follow these steps:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on primary DPS.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package. 
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini> 
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      upgrade.bat -d -gui -archive=true
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent-archive=true
                                                                                                
      
                                                                                                
      The -silent command, by default installs the ovinstallparams.ini file in the  to the same drive where the previous version is installed.
      
                                                                                                
      Optional.To customize the ovinstallparams.ini file location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent -archive=true
                                                                                            
      
                                                                                            
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui -archive=true
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Check if the L-Core certificates are present, run the following command:
      
                                                                                    
      ovcert -list
                                                                                    
      
                                                                                    
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                    
      Stop agent process:
      
                                                                                    
      ovc -kill
                                                                                    
      
                                                                                    
      To restore agent certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/agent-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      To restore server certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/cs-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      Start the agent process again:
      
                                                                                    
      ovc -start
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      
                                                                                        
      Enable OBM services on primary DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                            
      
                                                                                            
      
                                                                                                
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                            
      
                                                                                            
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                            
      
                                                                                            
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                            
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                    
      Run the following command to check the process status:
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    On gateway server, follow these steps. If there are multiple gateway servers, you can upgrade one gateway server at a time or multiple gateway servers concurrently. 
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on gateway server.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                            
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      Note 
                                                                                                
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                
       
      
                                                                                                
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      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. 
                                                                                            
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                            
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                        
      
                                                                                        
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Check if the L-Core certificates are present, run the following command:
      
                                                                                    
      ovcert -list
                                                                                    
      
                                                                                    
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                    
      Stop agent process:
      
                                                                                    
      ovc -kill
                                                                                    
      
                                                                                    
      To restore agent certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/agent-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      To restore server certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/cs-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      Start the agent process again:
      
                                                                                    
      ovc -start
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      
                                                                                        
      Enable OBM services on gateway server. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                            
      
                                                                                            
      
                                                                                                
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                            
      
                                                                                            
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                            
      
                                                                                            
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                            
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                            
      
                                                                                        
      
                                                                                        
      Run the following command to check the process status:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    5. 
                                                                        
  5. 
                                                                            
    On secondary DPS, follow these steps:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on secondary DPS.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                            
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      Note 
                                                                                                
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                
       
      
                                                                                                
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      After the secondary DPS  is upgraded, that is,  after OBM2020.10 is installed and configured on the secondary DPS, start the services on the secondary 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. 
                                                                                            
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                            
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                        
      
                                                                                        
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Check if the L-Core certificates are present, run the following command:
      
                                                                                    
      ovcert -list
                                                                                    
      
                                                                                    
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                    
      Stop agent process:
      
                                                                                    
      ovc -kill
                                                                                    
      
                                                                                    
      To restore agent certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/agent-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      To restore server certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/cs-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      Start the agent process again:
      
                                                                                    
      ovc -start
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      
                                                                                        
      
                                                                                            
      Enable OBM services on DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                
      
                                                                                                
      
                                                                                                    
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                
      
                                                                                                
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                            
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                
      
                                                                                                
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                        
      
                                                                                            
      Run the following command to check the process status:
      
                                                                                            
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    6. 
                                                                    

                                                                    

                                                                        
After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.

                                                                        

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

                                                                            

                                                                                
Replace the

                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                

                                                                                
line with the

                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                

                                                                                
line.

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        
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 OBM host system, follow the steps:

                                                                    
    
                                                                        
  1. 
                                                                            
    Open a Command Promptterminal window as an administratorthe root user on active server.
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                            
    cd <OBMInstallationFilesDirectory>
                                                                            
    
                                                                            
    
                                                                                
    Note: You should not have any whitespaces when you enter the path.
    
                                                                            
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Run the following command on the active server of your existing OBM environment:
    
                                                                            
    
                                                                                
    upgrade.bat -s -silent
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    ./upgrade.sh -s -silent
                                                                                
    
                                                                            
    
                                                                            
    The upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                            
    After the active server is upgraded, that is, after OBM2020.10 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 lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                            
    
                                                                                
    upgrade.bat -s -silent  -archive=true
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    ./upgrade.sh  -s -silent  -archive=true
                                                                                
    
                                                                            
    
                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                        
    4. 
                                                                    

                                                                    
After you initiate the upgrade, follow the order to complete the upgrade process:

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

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Initiate the upgrade process

                                                        

                                                            

                                                                

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user.
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    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 single server, if the live bus running on single server 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 upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh  -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                            
    5. 
                                                                        

                                                                    

                                                                

                                                                

                                                                    

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

                                                                        

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

                                                                        

                                                                        
    
                                                                            
  1. 
                                                                                
    Ensure the HAC services and the live bus are not running on the secondary DPS.
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      
                                                                                            
      To check the status of the HAC services, run the following command:
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                                
      
                                                                                            
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                                
      
                                                                                            
      
                                                                                            
      If the HAC services are running on the secondary DPS, reassign the services from secondary DPS to primary DPS. To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                        
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      To check the live bus status run the following command:
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                            
      
                                                                                        
      
                                                                                        
      If the live bus is running on the secondary DPS, reassign the live bus from secondary DPS to primary DPS. To assign live bus to primary DPS, run the following command:
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                            
      
                                                                                        
      
                                                                                    
      3. 
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    
                                                                                    
    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)
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user on primary DPS.
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Run the following command on the primary DPS of your existing OBM environment:
    
                                                                                
    
                                                                                    
    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 upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh  -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                            
    6. 
                                                                        

                                                                    

                                                                

                                                                

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    For non-root installation, extract the files in / directory.
    
                                                                                    
    
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Run the following command:
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent
                                                                                            
    
                                                                                            
    The -silent command by default, installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -gui
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed after the upgrade has finished and OBM is running.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    
                                                                                        
    upgrade.bat -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent -archive=true
    
                                                                                            
    The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -archive=true -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent -archive=true
                                                                                        
    
                                                                                        
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
     ./upgrade.sh -d -gui -archive=true
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    In GUI upgrade, you need to choose the installation type and the path manually.
    
                                                                                
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Check if the L-Core certificates are present, run the following command:
    
                                                                                
    ovcert -list
                                                                                
    
                                                                                
    If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
    
                                                                                
    Stop agent process:
    
                                                                                
    ovc -kill
                                                                                
    
                                                                                
    To restore agent certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/agent-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    To restore server certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/cs-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    Start the agent process again:
    
                                                                                
    ovc -start
                                                                                
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
    
                                                                                
    
                                                                                    
    Run  the following command to check the process status:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
    
                                                                                
    
                                                                                
    After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.
    
                                                                            
    7. 
                                                                        

                                                                        

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
This section applies only to the host system of the data processing server (DPS) in your BSMOBMexisting OBM deployment.

                                                                        

                                                                        

                                                                            

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

                                                                                
If you want to perform upgrade with minimal downtime, go back to the selection page and choose Distributed HA deployment.

                                                                            

                                                                        

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

                                                                        
Perform the following steps in order - Upgrade primary DPS and enable primary DPS then only start the upgrade of remaining gateway server and enable the gateway server.

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    
                                                                                    
    You must run the following commands  to stop services on the remaining 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 remaining gateway servers as non-root user:
    
                                                                                    
    /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)
    
                                                                                
    
                                                                                
    The  event flow is paused when the gateway server is stopped. It is resumed on the production OBM after the DPS and atleast one of the gateway server upgrade is complete and OBM services is running.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Initiate the upgrade on primary DPS first, then gateway server. 
    
                                                                                
    On the DPS, follow these steps:
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Open a Command Promptterminal window as an administratorthe root user on primary DPS.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package. 
      
                                                                                        
      
                                                                                            
      
                                                                                                
      For non-root installation, extract the files in / directory.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                        
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Run the following command:
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini> 
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui -archive=true
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent-archive=true
                                                                                                    
      
                                                                                                    
      The -silent command, by default installs the ovinstallparams.ini file in the  to the same drive where the previous version is installed.
      
                                                                                                    
      Optional.To customize the ovinstallparams.ini file location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                    
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent -archive=true
                                                                                                
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui -archive=true
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                        
      
                                                                                    
      4. 
                                                                                    
    4. 
                                                                                        
      Check if the L-Core certificates are present, run the following command:
      
                                                                                        
      ovcert -list
                                                                                        
      
                                                                                        
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                        
      Stop agent process:
      
                                                                                        
      ovc -kill
                                                                                        
      
                                                                                        
      To restore agent certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/agent-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      To restore server certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/cs-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      Start the agent process again:
      
                                                                                        
      ovc -start
                                                                                        
      
                                                                                    
      5. 
                                                                                    
    5. 
                                                                                        
      
                                                                                            
      Enable OBM services on primary DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                
      
                                                                                                
      
                                                                                                    
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                
      
                                                                                                
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                            
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                
      
                                                                                                
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                        
      Run the following command to check the process status:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                        
      
                                                                                    
      6. 
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    On gateway server, follow these steps. If there are multiple gateway servers, you can upgrade one gateway server at a time or multiple gateway servers concurrently. 
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Open a Command Promptterminal window as an administratorthe root user on gateway server.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                        
      
                                                                                            
      
                                                                                                
      For non-root installation, extract the files in / directory.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                        
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Run the following command
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                    
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                    
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                                
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      Note 
                                                                                                    
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                    
       
      
                                                                                                    
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      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. 
                                                                                                
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                                
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                            
      
                                                                                            
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                        
      
                                                                                    
      4. 
                                                                                    
    4. 
                                                                                        
      Check if the L-Core certificates are present, run the following command:
      
                                                                                        
      ovcert -list
                                                                                        
      
                                                                                        
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                        
      Stop agent process:
      
                                                                                        
      ovc -kill
                                                                                        
      
                                                                                        
      To restore agent certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/agent-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      To restore server certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/cs-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      Start the agent process again:
      
                                                                                        
      ovc -start
                                                                                        
      
                                                                                    
      5. 
                                                                                    
    5. 
                                                                                        
      
                                                                                            
      Enable OBM services on gateway server. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                
      
                                                                                                
      
                                                                                                    
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                
      
                                                                                                
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                            
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                
      
                                                                                                
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                
      
                                                                                            
      
                                                                                            
      Run the following command to check the process status:
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                                
      
                                                                                            
      
                                                                                            
      
                                                                                                
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      6. 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    On secondary DPS, follow these steps:
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Open a Command Promptterminal window as an administratorthe root user on secondary DPS.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                        
      
                                                                                            
      
                                                                                                
      For non-root installation, extract the files in / directory.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                        
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Run the following command:
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                    
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                    
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                                
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      Note 
                                                                                                    
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                    
       
      
                                                                                                    
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                            
      After the secondary DPS  is upgraded, that is,  after OBM2020.10 is installed and configured on the secondary DPS, start the services on the secondary 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. 
                                                                                                
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                                
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                            
      
                                                                                            
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                        
      
                                                                                    
      4. 
                                                                                    
    4. 
                                                                                        
      Check if the L-Core certificates are present, run the following command:
      
                                                                                        
      ovcert -list
                                                                                        
      
                                                                                        
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                        
      Stop agent process:
      
                                                                                        
      ovc -kill
                                                                                        
      
                                                                                        
      To restore agent certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/agent-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      To restore server certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/cs-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      Start the agent process again:
      
                                                                                        
      ovc -start
                                                                                        
      
                                                                                    
      5. 
                                                                                    
    5. 
                                                                                        
      
                                                                                            
      
                                                                                                
      Enable OBM services on DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                                
      
                                                                                                    
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                    
      
                                                                                                    
      
                                                                                                        
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                    
      
                                                                                                    
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                                
      
                                                                                                
      
                                                                                                    
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                    
      
                                                                                                    
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                    
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                            
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                            
      
                                                                                                
      Run the following command to check the process status:
      
                                                                                                
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                                
      
                                                                                            
      
                                                                                            
      
                                                                                                
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      6. 
                                                                                
    
                                                                            
    6. 
                                                                        

                                                                        

                                                                            
After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
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 OBM host system, follow the steps:

                                                                        
    
                                                                            
  1. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user on active server.
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Run the following command on the active server of your existing OBM environment:
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh -s -silent
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                                
    After the active server is upgraded, that is, after OBM2020.10 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 lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh  -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                            
    4. 
                                                                        

                                                                        
After you initiate the upgrade, follow the order to complete the upgrade process:

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

                                                                    

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    
                                                                                    
    
                                                                                        
    You must run the following commands  to stop services on the remaining inactive single server and gateway servers:
    
                                                                                        
    <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 remaining inactive single server and gateway servers as non-root user:
    
                                                                                        
    /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)
    
                                                                                    
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user on active server.
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    For non-root installation, extract the files in / directory.
    
                                                                                    
    
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Run the following command:
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent
                                                                                            
    
                                                                                            
    The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -gui
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed after the upgrade has finished and OBM is running.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    
                                                                                        
    upgrade.bat -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent-archive=true
                                                                                            
    
                                                                                            
    The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent -archive=true
                                                                                        
    
                                                                                        
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    In GUI upgrade, you need to choose the installation type and the path manually.
    
                                                                                
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    Check if the L-Core certificates are present, run the following command:
    
                                                                                
    ovcert -list
                                                                                
    
                                                                                
    If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
    
                                                                                
    Stop agent process:
    
                                                                                
    ovc -kill
                                                                                
    
                                                                                
    To restore agent certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/agent-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    To restore server certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/cs-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    Start the agent process again:
    
                                                                                
    ovc -start
                                                                                
    
                                                                            
    7. 
                                                                            
  7. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
    
                                                                                
    
                                                                                    
    Run the following command to check the process status:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
    
                                                                                
    
                                                                            
    8. 
                                                                        

                                                                        
Enable OBM services on active server  first. Then upgrade backup server following the steps 1-4 1-5 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.

                                                                        

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                            

                                                                

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    For non-root installation, extract the files in / directory.
    
                                                                                    
    
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Run the following command:
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent
                                                                                            
    
                                                                                            
    The -silent command by default, installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -gui
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed after the upgrade has finished and OBM is running.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    
                                                                                        
    upgrade.bat -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent -archive=true
    
                                                                                            
    The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -archive=true -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent -archive=true
                                                                                        
    
                                                                                        
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
     ./upgrade.sh -d -gui -archive=true
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    In GUI upgrade, you need to choose the installation type and the path manually.
    
                                                                                
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Check if the L-Core certificates are present, run the following command:
    
                                                                                
    ovcert -list
                                                                                
    
                                                                                
    If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
    
                                                                                
    Stop agent process:
    
                                                                                
    ovc -kill
                                                                                
    
                                                                                
    To restore agent certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/agent-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    To restore server certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/cs-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    Start the agent process again:
    
                                                                                
    ovc -start
                                                                                
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
    
                                                                                
    
                                                                                    
    Run  the following command to check the process status:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
    
                                                                                
    
                                                                                
    After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.
    
                                                                            
    7. 
                                                                        

                                                                        

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        
This section applies only to the host system of the data processing server (DPS) in your BSMOBMexisting OBM deployment.

                                                                    

                                                                    

                                                                        

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

                                                                            
If you want to perform upgrade with minimal downtime, go back to the selection page and choose Distributed HA deployment.

                                                                        

                                                                    

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

                                                                    
Perform the following steps in order - Upgrade primary DPS and enable primary DPS then only start the upgrade of remaining gateway server and enable the gateway server.

                                                                    
    
                                                                        
  1. 
                                                                            
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                            
    
                                                                                
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                
    
                                                                            
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    
                                                                                
    You must run the following commands  to stop services on the remaining 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 remaining gateway servers as non-root user:
    
                                                                                
    /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)
    
                                                                            
    
                                                                            
    The  event flow is paused when the gateway server is stopped. It is resumed on the production OBM after the DPS and atleast one of the gateway server upgrade is complete and OBM services is running.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Initiate the upgrade on primary DPS first, then gateway server. 
    
                                                                            
    On the DPS, follow these steps:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on primary DPS.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package. 
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini> 
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      upgrade.bat -d -gui -archive=true
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent-archive=true
                                                                                                
      
                                                                                                
      The -silent command, by default installs the ovinstallparams.ini file in the  to the same drive where the previous version is installed.
      
                                                                                                
      Optional.To customize the ovinstallparams.ini file location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent -archive=true
                                                                                            
      
                                                                                            
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui -archive=true
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Check if the L-Core certificates are present, run the following command:
      
                                                                                    
      ovcert -list
                                                                                    
      
                                                                                    
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                    
      Stop agent process:
      
                                                                                    
      ovc -kill
                                                                                    
      
                                                                                    
      To restore agent certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/agent-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      To restore server certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/cs-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      Start the agent process again:
      
                                                                                    
      ovc -start
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      
                                                                                        
      Enable OBM services on primary DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                            
      
                                                                                            
      
                                                                                                
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                            
      
                                                                                            
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                            
      
                                                                                            
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                            
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                    
      Run the following command to check the process status:
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    On gateway server, follow these steps. If there are multiple gateway servers, you can upgrade one gateway server at a time or multiple gateway servers concurrently. 
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on gateway server.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                            
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      Note 
                                                                                                
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                
       
      
                                                                                                
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      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. 
                                                                                            
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                            
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                        
      
                                                                                        
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Check if the L-Core certificates are present, run the following command:
      
                                                                                    
      ovcert -list
                                                                                    
      
                                                                                    
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                    
      Stop agent process:
      
                                                                                    
      ovc -kill
                                                                                    
      
                                                                                    
      To restore agent certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/agent-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      To restore server certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/cs-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      Start the agent process again:
      
                                                                                    
      ovc -start
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      
                                                                                        
      Enable OBM services on gateway server. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                            
      
                                                                                            
      
                                                                                                
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                            
      
                                                                                            
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                            
      
                                                                                            
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                            
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                            
      
                                                                                        
      
                                                                                        
      Run the following command to check the process status:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    5. 
                                                                        
  5. 
                                                                            
    On secondary DPS, follow these steps:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on secondary DPS.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                            
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      Note 
                                                                                                
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                
       
      
                                                                                                
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      After the secondary DPS  is upgraded, that is,  after OBM2020.10 is installed and configured on the secondary DPS, start the services on the secondary 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. 
                                                                                            
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                            
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                        
      
                                                                                        
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Check if the L-Core certificates are present, run the following command:
      
                                                                                    
      ovcert -list
                                                                                    
      
                                                                                    
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                    
      Stop agent process:
      
                                                                                    
      ovc -kill
                                                                                    
      
                                                                                    
      To restore agent certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/agent-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      To restore server certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/cs-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      Start the agent process again:
      
                                                                                    
      ovc -start
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      
                                                                                        
      
                                                                                            
      Enable OBM services on DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                
      
                                                                                                
      
                                                                                                    
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                
      
                                                                                                
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                            
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                
      
                                                                                                
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                        
      
                                                                                            
      Run the following command to check the process status:
      
                                                                                            
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    6. 
                                                                    

                                                                    

                                                                        
After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.

                                                                        

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

                                                                            

                                                                                
Replace the

                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                

                                                                                
line with the

                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                

                                                                                
line.

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        
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 OBM host system, follow the steps:

                                                                    
    
                                                                        
  1. 
                                                                            
    Open a Command Promptterminal window as an administratorthe root user on active server.
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                            
    cd <OBMInstallationFilesDirectory>
                                                                            
    
                                                                            
    
                                                                                
    Note: You should not have any whitespaces when you enter the path.
    
                                                                            
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Run the following command on the active server of your existing OBM environment:
    
                                                                            
    
                                                                                
    upgrade.bat -s -silent
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    ./upgrade.sh -s -silent
                                                                                
    
                                                                            
    
                                                                            
    The upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                            
    After the active server is upgraded, that is, after OBM2020.10 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 lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                            
    
                                                                                
    upgrade.bat -s -silent  -archive=true
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    ./upgrade.sh  -s -silent  -archive=true
                                                                                
    
                                                                            
    
                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                        
    4. 
                                                                    

                                                                    
After you initiate the upgrade, follow the order to complete the upgrade process:

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

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Start the update

                                                            

                                                                

                                                                    
Perform the following steps:

                                                                    
    
                                                                        
  1. 
                                                                            
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                            
    
                                                                                
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                
    
                                                                            
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Ensure the HAC services and the live bus are not running on the inactive DPS.
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      
                                                                                        
      To check the status of the HAC services, run the following command:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                            
      
                                                                                        
      
                                                                                        
      If the HAC services are running on the inactive DPS, reassign the services from inactive DPS to active DPS. To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                    
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      To check the live bus status run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      If the live bus is running on the inactive DPS, reassign the live bus from inactive DPS to active DPS. To assign live bus to active DPS, run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                            
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Update OBM on inactive DPS  and start the OBM services. After inactive DPS update is complete, update one of the gateway servers. Follow the steps:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on the system.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to a location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Assign live bus to the updated DPS:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
      
                                                                                        
      
                                                                                            
      After the upgrade, change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                        
      
                                                                                        
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                        
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    Move the HAC services from the active DPS to the updated DPS. 
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Reassign the services from non-updated to updated server. 
      
                                                                                    
      To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                    
      To check the status of the HAC services, run the following command :
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                        
      
                                                                                    
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      To check the live bus status, run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      Assign live bus to updated DPS:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                            
    
                                                                        
    5. 
                                                                        
  5. 
                                                                            
    After the HAC services are moved successfully, update the remaining non-updated set of gateway servers and data processing servers one after the other or concurrently depending on OBM usage/load. To perform the update, follow the steps:
    
                                                                            
      
                                                                                
    1. Open a Command Promptterminal window as an administratorthe root user on the system.
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to a location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      
                                                                                        
      Update OBM on non-updated DPS and remaining gateway servers. You can perform the update concurrently. Run the following command:
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                    
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
      
                                                                                        
      
                                                                                            
      After the upgrade, change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                        
      
                                                                                        
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      After the update is complete, run the following command to start the OBM services:
      
                                                                                        
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
      
                                                                                        
      
                                                                                            
      Note On Linux systems, OBM does not function properly when the IPv6 protocol stack is not configured (that is, when only the IPv4 protocol stack is available) or when the IPv6 protocol stack is configured but disabled. Under such circumstances, to enable OBM to use IPv4, modify the /opt/HP/BSM/application-server/bin/standalone.conf configuration file as follows:
      
                                                                                            
      
                                                                                                
      Replace the
      
                                                                                                
      -Djava.net.preferIPv4Stack=false
                                                                                                
      
                                                                                                
      line with the
      
                                                                                                
      -Djava.net.preferIPv4Stack=true
                                                                                                
      
                                                                                                
      line.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.
      
                                                                                
      5. 
                                                                            
    
                                                                        
    6. 
                                                                    

                                                                

                                                                

                                                                    
Perform the following steps on inactive server:

                                                                    
    
                                                                        
  1. 
                                                                            
    Ensure the HAC services and the live bus are not running on the inactive server.
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      
                                                                                        
      To check the status of the HAC services, run the following command:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                            
      
                                                                                        
      
                                                                                        
      If the HAC services are running on the inactive server, reassign the services from inactive server to active server. To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                    
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      To check the live bus status run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      If the live bus is running on the inactive server, reassign the live bus from inactive server to active server. To assign live bus to active server, run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                            
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Update OBM and start the OBM services on inactive server. Follow the steps:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to a location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Assign live bus to the updated server:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      
                                                                                            
      After the upgrade, change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                        
      
                                                                                        
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                        
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    
                                                                                
    Move the HAC services from the active server to the updated server. 
    
                                                                            
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Reassign the services from non-updated to updated server. 
      
                                                                                    
      To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                    
      To check the status of the HAC services, run the following command :
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                        
      
                                                                                    
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      To check the live bus status run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      Assign live bus to updated server:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                            
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    After the HAC services are moved successfully, update the remaining active server (non-updated) and update if any additional gateway servers are configured. To perform the update, follow the steps:
    
                                                                            
      
                                                                                
    1. Open a Command Promptterminal window as an administratorthe root user.
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to a location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Update OBM on non-updated server.
      
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      
                                                                                            
      After the upgrade, change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                        
      
                                                                                        
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                        
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
      
                                                                                        
      
                                                                                            
      Note On Linux systems, OBM does not function properly when the IPv6 protocol stack is not configured (that is, when only the IPv4 protocol stack is available) or when the IPv6 protocol stack is configured but disabled. Under such circumstances, to enable OBM to use IPv4, modify the /opt/HP/BSM/application-server/bin/standalone.conf configuration file as follows:
      
                                                                                            
      
                                                                                                
      Replace the
      
                                                                                                
      -Djava.net.preferIPv4Stack=false
                                                                                                
      
                                                                                                
      line with the
      
                                                                                                
      -Djava.net.preferIPv4Stack=true
                                                                                                
      
                                                                                                
      line.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.
      
                                                                                
      5. 
                                                                            
    
                                                                        
    5. 
                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Start the update

                                                            

                                                                

                                                                    
Perform the following steps:

                                                                    
    
                                                                        
  1. 
                                                                            
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                            
    
                                                                                
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                
    
                                                                            
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Ensure the HAC services and the live bus are not running on the inactive DPS.
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      
                                                                                        
      To check the status of the HAC services, run the following command:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                            
      
                                                                                        
      
                                                                                        
      If the HAC services are running on the inactive DPS, reassign the services from inactive DPS to active DPS. To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                    
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      To check the live bus status run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      If the live bus is running on the inactive DPS, reassign the live bus from inactive DPS to active DPS. To assign live bus to active DPS, run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                            
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Update OBM on inactive DPS  and start the OBM services. After inactive DPS update is complete, update one of the gateway servers. Follow the steps:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on the system.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to a location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Assign live bus to the updated DPS:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
      
                                                                                        
      
                                                                                            
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                        
      
                                                                                        
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      After the update is complete, run the following command to start the OB services as non-root user:
      
                                                                                        
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    4. 
                                                                    

                                                                

                                                                

                                                                    
Perform the following steps on inactive server:

                                                                    
    
                                                                        
  1. 
                                                                            
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                            
    
                                                                                
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                
    
                                                                            
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Ensure the HAC services and the live bus are not running on the inactive server.
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      
                                                                                        
      To check the status of the HAC services, run the following command:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                            
      
                                                                                        
      
                                                                                        
      If the HAC services are running on the inactive server, reassign the services from inactive server to active server. To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                    
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      To check the live bus status run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      If the live bus is running on the inactive server, reassign the live bus from inactive server to active server. To assign live bus to active server, run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                            
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Update OBM and start the OBM services on inactive server.
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to a location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Assign live bus to the updated server:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      
                                                                                            
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                        
      
                                                                                        
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      After the update is complete, run the following command to start the OBM services as non-root user::
      
                                                                                        
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    4. 
                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Attend the initial upgradeupdate phase

                                                            

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

                                                                
    
                                                                    
  • 
                                                                        
    	The event queue is emptied in primary DPSactive 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: Skipping backup for non-existent file /opt/HP/BSM/WebServer/conf.d
INFO: Backup file in ZIP: /var/opt/OV/backup/OMibackup.rsp
INFO: (./upgrade.sh) Found backup files in /var/opt/OV/backup/
INFO: (./upgrade.sh) Please copy the file /var/opt/OV/backup/OMiXXXXXcfg-backup.zip to your OBM target machine.

                                                                        

                                                                    

                                                                

                                                                
 

                                                                

                                                                    

                                                                        
INFO: (./upgrade.sh) Updating from OMi/OBM version 1100
INFO: (./upgrade.sh) Checking for multiple DPS setup
INFO: (./upgrade.sh) Multiple DPS detected. Will check for Active/Backup DPS
INFO: (./upgrade.sh) Checking if running on active DPS
INFO: (./upgrade.sh) Backup DPS detected
INFO: (./upgrade.sh) Checking if DB is already upgraded
INFO: (./upgrade.sh) DB has not been upgraded. Continuing upgrade as Minimal Downtime is supported.
INFO: Skipping preupgrade preparations for this upgrade.
INFO: (./upgrade.sh) Backing up config data and DB to /var/opt/OV/backup before upgrade. Please be patient...
INFO: Backup logs present in /var/opt/OV/log/opr-upgradeBackup.log
INFO: (./upgrade.sh) Found backup files in /var/opt/OV/backup/
								

                                                                        

                                                                    

                                                                

                                                                
 

                                                                

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

                                                                        

                                                                    

                                                                

                                                                
 

                                                                

                                                                    

                                                                        
INFO: Updating from OMi/OBM version xxxx in directory C:\HPBSM
INFO: Skipping product_upgrade_wizard.bat installation for OMi/OBM source version 1100
INFO: Updating preuninstall.properties for per uninstall logs
INFO: Updating preuninstall properties completed with return code 0
INFO: Checking for multiple DPS setup
INFO: Multiple DPS detected
INFO: Checking if running on active DPS
INFO: Backup DPS detected
INFO: Checking if DB is already upgraded
INFO: DB has not been upgraded yet. Continuing upgrade as Minimal Downtime is supported.
INFO: Running PreMigration Tool to prepare for Upgrade
INFO: Skipping preupgrade preparations for this upgrade.
INFO: Backing up config data to C:\ProgramData\HP\HP BTO Software\backup\OMi1100 before upgrade. Please be patient...
INFO: Backup logs present in C:\ProgramData\HP\HP BTO Software\log\opr-upgradeBackup.log
INFO: Found backup files in C:\ProgramData\HP\HP BTO Software\backup\
								

                                                                        

                                                                    

                                                                

                                                                

                                                                    
Sometimes the following error may be reported as well:
Pre-upgrade process executed with some errors.


                                                                    
If this occurs, press N to cancel pending uninstallation, restart the host system, and then initiate the upgradeupdate 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. 
                                                                    
  2. 
                                                                        
    Removes the Monitoring Automation feature of BSM, if installed.
    
                                                                    
    3. 
                                                                    
  3. 
                                                                        
    Uninstalls OMi/OBM, including LCore/Agent. The configuration data in the %OvDataDir%/var/opt/OV directory is preserved.
    
                                                                    
    4. 
                                                                

                                                                

                                                                    

                                                                        
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 OA
INFO: Stopping OMi/OBM for Uninstallation
INFO: Skipping installation-wixard.jar installation for OMi/OBM source version 1100
INFO: Starting uninstallation. Please be patient and do not interrupt as it will take some time especially if your system does not have internet access which is used for certificate validity checks..
INFO: Uninstalling OMi...please check the log file in %temp% for uninstallation details
INFO: Uninstallation completed
INFO: Cleaning up installed policies suceeded...
INFO: Uninstallation done - Starting installation of OBM

                                                                

                                                                
 

                                                                

                                                                    
INFO: (./upgrade.sh) Found backup files in /var/opt/OV/backup/
INFO: (./upgrade.sh) Stopping OA...
INFO: (./upgrade.sh) Stopping OBM for Uninstallation...
INFO: (./upgrade.sh) Skipping installation-wizard.jar hotfix installation for source version 1100
INFO: (./upgrade.sh) No OMi patches installed...
INFO: (./upgrade.sh) Uninstalling OMi... Please check the log file in temp location for uninstallation details
INFO: (./upgrade.sh) Uninstallation done


                                                                    

                                                                    
 

                                                                    
INFO: Stopping OA
INFO: Stopping OMi/OBM for Uninstallation
INFO: Skipping installation-wizard.jar installation for OMi/OBM source version 1100
INFO: Starting uninstallation. Please be patient and do not interrupt as it will take some time especially if your system does not have internet access which is used for certificate validity checks.
INFO: Uninstalling OMi... Please check the log file in %temp% for uninstallation details
INFO: Uninstallation completed
INFO: Cleaning up installed policies succeeded...
INFO: Uninstallation done - Starting installation of OBM

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Attend invocation of the OBM 2020.10 installation

                                                            

                                                                
After your earlier OMi/OBM version is uninstalled, the upgradeupdate process invokes the installation of OBM 2020.10. 
                                                                

                                                                

                                                                    

                                                                        
If you had symbolic links before upgrade, recreate them manually before proceeding with the upgrade. Invoke the installation of OBM 2020.10. 

                                                                    

                                                                

                                                                

                                                                    

                    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

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Start the OBM2020.10 installation

                                                    

                                                        
Invocation of the OBM2020.10 installation is the same for single server deployment typedata processing and gateway server in distributed deployment types. Previously prepared ovinstallparams.ini file defines the type of the installed OBM server. Specify the path of the ovinstallparams.ini when you run the installation as shown. 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. 
                                                            
  2. 
                                                                
    Change the current directory as follows:
    
                                                                
    cd <OBMInstallationFilesDirectory>
                                                                
    
                                                            
    3. 
                                                            
  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 -filepath <path of ovinstallparams.ini>
                                                                    
    
                                                                    
    where, full path of ovinstallparams.ini is the file created in Prepare the installation parameters file step.
    
                                                                
    
                                                            
    4. 
                                                            
  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 -filepath <full path of ovinstallparams.ini>
                                                                    
    
                                                                    
    where, full path of ovinstallparams.ini is the file created in Prepare the installation parameters file step.
    
                                                                
    
                                                            
    5. 
                                                            
  5. 
                                                                
    Attend installation of OBM2020.10. In a virtual environment, this phase might take approximately between 30 and 60 minutes.
    
                                                            
    6. 
                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
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
    
                                                                    
    • 
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Installer Configuration 

                                                            

                                                                
During the OBM 2020.10 install initialization phase, installer configuration window displays if any settings from the previous installer are detected. Click Yes to proceed with the previous values.  You can modify the previous values.

                                                                
If you want to provide new values, click No and enter new values.

                                                                

                                                                    
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Installer Configuration 

                                                        

                                                            
During the OBM 2020.10 install initialization phase, installer configuration window displays if any settings from the previous installer are detected. Click Yes to proceed with the previous values.  You can modify the previous values.

                                                            
If you want to provide new values, click No and enter new values.

                                                            

                                                                
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Attend initialization of OBM 2020.10 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.10 installation

                                                        

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

                                                            
    
                                                                
  • 
                                                                    
    Supported operating system
    
                                                                
    • 
                                                                
  • 
                                                                    
    Sufficient physical memory
    
                                                                
    • 
                                                                
  • 
                                                                    
    Sufficient free storage space at the location the /tmp path points todefined by the %TEMP%  user environment variable
    
                                                                
    • 
                                                            

                                                            

                                                                Installation wizard: Initialization page
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Read the introduction

                                                            

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

                                                                

                                                                    Installation wizard: Introduction (Install) page
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Read the introduction

                                                        

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

                                                            

                                                                Installation wizard: Introduction (Install) page
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Review the license agreement

                                                            

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

                                                                

                                                                    Installation wizard: Product Agreement (License Agreement) page
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Review the license agreement

                                                        

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

                                                            

                                                                Installation wizard: Product Agreement (License Agreement) page
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Choose the server type

                                                    

                                                        

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

                                                            

                                                                Installation wizard: Product Customization page - data processing server
                                                            

                                                        

                                                        

                                                            
In the Product Customization page, select the 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.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            

                                                                
Specify the installation folders

                                                                

                                                                    
Select the following folders for the installation:

                                                                    
    
                                                                        
  • 
                                                                            
    Installation folder and data folder for the Closedshared content.
                                                                                
    
                                                                                    
    The following components are included in the  shared content:
    
                                                                                    
      
                                                                                        
    • 
                                                                                            
      Certificate Management Client
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Certificate Management Server
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Cross Platform Component
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Cross Platform Component Java
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Graphing Component
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      HTTP Communication
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      HTTP Communication Java
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Performance Access Java
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Process Control
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Security Core
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Security Core Java
      
                                                                                        
      • 
                                                                                    
    
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    Note  
    
                                                                                
      
                                                                                    
    • There is additional shared data in the %ALLUSERSPROFILE%\HP\BSM directory.
      • 
                                                                                    
    • During the installation of OBM 2020.10, 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:

                                                                    
    
                                                                        
  • 
                                                                            
    Installation folder and data folder for the Closedshared content.
                                                                                
    
                                                                                    
    The following components are included in the  shared content:
    
                                                                                    
      
                                                                                        
    • 
                                                                                            
      Certificate Management Client
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Certificate Management Server
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Cross Platform Component
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Cross Platform Component Java
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Graphing Component
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      HTTP Communication
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      HTTP Communication Java
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Performance Access Java
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Process Control
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Security Core
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Security Core Java
      
                                                                                        
      • 
                                                                                    
    
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    Note  
    
                                                                                
      
                                                                                    
    • There is additional shared data in the %ALLUSERSPROFILE%\HP\BSM directory.
      • 
                                                                                    
    • During the installation of OBM 2020.10, 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.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Initiate OBM 2020.10 installation

                                                            

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

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Initiate OBM 2020.10 installation

                                                        

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

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Attend OBM 2020.10 installation

                                                            

                                                                
While the Installing page is visible, attend the installation of OBM 2020.10. The configuration starts running in the background silently. Wait until the configuration is complete.

                                                                
Wait for the  configuration wizard to appear. Once the installation is complete, quit the configuration wizard and complete the installation.
                                                                

                                                                

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

                                                        

                                                            
While the Installing page is visible, attend the installation of OBM 2020.10. The configuration starts running in the background silently. Wait until the configuration is complete.

                                                            
Wait for the  configuration wizard to appear. Once the installation is complete, quit the configuration wizard and complete the installation.
                                                            

                                                            

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

                                                            

                                                            

                                                                Installation wizard: Installing page
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            

                                                                
Optional. Configure OBM 2020.10 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.10. For more information, see Support for Oracle Real Application Cluster.

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Optional. Configure OBM 2020.10 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.10. For more information, see Support for Oracle Real Application Cluster.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Complete the installation wizard

                                                            

                                                                
In GUI mode, the configuration continues silently in the background. This process happens in the Post install phase. Wait until the configuration is complete. 

                                                                
When OBM is successfully installed and configured, the installation wizard displays the Install Complete (Installation Complete) page with a summary of the  installation process. After the configuration is complete, click Done to complete the installation.

                                                                
Verify if the configuration wizard is run successfully by checking the configuration log file.

                                                                

                                                                    
<TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                    

                                                                

                                                                

                                                                    
<TOPAZ_HOME>/log/configserver/configserver_all.log
                                                                    

                                                                

                                                                
If the OBM configuration wizard is successful, skip the below configuration wizard steps till Ready to Configure and go to the Review the summary and conclude the upgrade  section.

                                                                

                                                                    
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.
                                                                

                                                                
If the configuration fails to complete silently, you can try to rerun the configuration wizard manually. For instructions, see Start the configuration wizard manually.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Complete the installation wizard

                                                            

                                                                
In GUI mode, the configuration continues silently in the background. This process happens in the Post install phase. Wait until the configuration is complete. 

                                                                
When OBM is successfully installed and configured, the installation wizard displays the Install Complete (Installation Complete) page with a summary of the  installation process. After the configuration is complete, click Done to complete the installation.

                                                                
Verify if the configuration wizard is run successfully by checking the configuration log file.

                                                                

                                                                    
<TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                    

                                                                

                                                                

                                                                    
<TOPAZ_HOME>/log/configserver/configserver_all.log
                                                                    

                                                                

                                                                
If the OBM configuration wizard is successful, skip the below configuration wizard steps till Ready to Configure and go to the Review the summary and conclude the upgrade  section.

                                                                

                                                                    
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.
                                                                

                                                                
If the configuration fails to complete silently, you can try to rerun the configuration wizard manually. For instructions, see Start the configuration wizard manually.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Initiate the upgrade process

                                                        

                                                            

                                                                

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user.
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    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 single server, if the live bus running on single server 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 upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh  -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                            
    5. 
                                                                        

                                                                    

                                                                

                                                                

                                                                    

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

                                                                        

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

                                                                        

                                                                        
    
                                                                            
  1. 
                                                                                
    Ensure the HAC services and the live bus are not running on the secondary DPS.
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      
                                                                                            
      To check the status of the HAC services, run the following command:
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                                
      
                                                                                            
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                                
      
                                                                                            
      
                                                                                            
      If the HAC services are running on the secondary DPS, reassign the services from secondary DPS to primary DPS. To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                        
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      To check the live bus status run the following command:
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                            
      
                                                                                        
      
                                                                                        
      If the live bus is running on the secondary DPS, reassign the live bus from secondary DPS to primary DPS. To assign live bus to primary DPS, run the following command:
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                            
      
                                                                                        
      
                                                                                    
      3. 
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    
                                                                                    
    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)
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user on primary DPS.
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Run the following command on the primary DPS of your existing OBM environment:
    
                                                                                
    
                                                                                    
    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 upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh  -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                            
    6. 
                                                                        

                                                                    

                                                                

                                                                

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    For non-root installation, extract the files in / directory.
    
                                                                                    
    
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Run the following command:
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent
                                                                                            
    
                                                                                            
    The -silent command by default, installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -gui
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed after the upgrade has finished and OBM is running.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    
                                                                                        
    upgrade.bat -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent -archive=true
    
                                                                                            
    The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -archive=true -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent -archive=true
                                                                                        
    
                                                                                        
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
     ./upgrade.sh -d -gui -archive=true
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    In GUI upgrade, you need to choose the installation type and the path manually.
    
                                                                                
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Check if the L-Core certificates are present, run the following command:
    
                                                                                
    ovcert -list
                                                                                
    
                                                                                
    If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
    
                                                                                
    Stop agent process:
    
                                                                                
    ovc -kill
                                                                                
    
                                                                                
    To restore agent certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/agent-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    To restore server certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/cs-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    Start the agent process again:
    
                                                                                
    ovc -start
                                                                                
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
    
                                                                                
    
                                                                                    
    Run  the following command to check the process status:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
    
                                                                                
    
                                                                                
    After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.
    
                                                                            
    7. 
                                                                        

                                                                        

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
This section applies only to the host system of the data processing server (DPS) in your BSMOBMexisting OBM deployment.

                                                                        

                                                                        

                                                                            

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

                                                                                
If you want to perform upgrade with minimal downtime, go back to the selection page and choose Distributed HA deployment.

                                                                            

                                                                        

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

                                                                        
Perform the following steps in order - Upgrade primary DPS and enable primary DPS then only start the upgrade of remaining gateway server and enable the gateway server.

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    
                                                                                    
    You must run the following commands  to stop services on the remaining 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 remaining gateway servers as non-root user:
    
                                                                                    
    /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)
    
                                                                                
    
                                                                                
    The  event flow is paused when the gateway server is stopped. It is resumed on the production OBM after the DPS and atleast one of the gateway server upgrade is complete and OBM services is running.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Initiate the upgrade on primary DPS first, then gateway server. 
    
                                                                                
    On the DPS, follow these steps:
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Open a Command Promptterminal window as an administratorthe root user on primary DPS.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package. 
      
                                                                                        
      
                                                                                            
      
                                                                                                
      For non-root installation, extract the files in / directory.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                        
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Run the following command:
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini> 
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui -archive=true
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent-archive=true
                                                                                                    
      
                                                                                                    
      The -silent command, by default installs the ovinstallparams.ini file in the  to the same drive where the previous version is installed.
      
                                                                                                    
      Optional.To customize the ovinstallparams.ini file location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                    
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent -archive=true
                                                                                                
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui -archive=true
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                        
      
                                                                                    
      4. 
                                                                                    
    4. 
                                                                                        
      Check if the L-Core certificates are present, run the following command:
      
                                                                                        
      ovcert -list
                                                                                        
      
                                                                                        
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                        
      Stop agent process:
      
                                                                                        
      ovc -kill
                                                                                        
      
                                                                                        
      To restore agent certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/agent-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      To restore server certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/cs-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      Start the agent process again:
      
                                                                                        
      ovc -start
                                                                                        
      
                                                                                    
      5. 
                                                                                    
    5. 
                                                                                        
      
                                                                                            
      Enable OBM services on primary DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                
      
                                                                                                
      
                                                                                                    
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                
      
                                                                                                
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                            
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                
      
                                                                                                
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                        
      Run the following command to check the process status:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                        
      
                                                                                    
      6. 
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    On gateway server, follow these steps. If there are multiple gateway servers, you can upgrade one gateway server at a time or multiple gateway servers concurrently. 
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Open a Command Promptterminal window as an administratorthe root user on gateway server.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                        
      
                                                                                            
      
                                                                                                
      For non-root installation, extract the files in / directory.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                        
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Run the following command
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                    
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                    
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                                
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      Note 
                                                                                                    
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                    
       
      
                                                                                                    
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      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. 
                                                                                                
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                                
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                            
      
                                                                                            
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                        
      
                                                                                    
      4. 
                                                                                    
    4. 
                                                                                        
      Check if the L-Core certificates are present, run the following command:
      
                                                                                        
      ovcert -list
                                                                                        
      
                                                                                        
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                        
      Stop agent process:
      
                                                                                        
      ovc -kill
                                                                                        
      
                                                                                        
      To restore agent certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/agent-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      To restore server certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/cs-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      Start the agent process again:
      
                                                                                        
      ovc -start
                                                                                        
      
                                                                                    
      5. 
                                                                                    
    5. 
                                                                                        
      
                                                                                            
      Enable OBM services on gateway server. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                
      
                                                                                                
      
                                                                                                    
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                
      
                                                                                                
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                            
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                
      
                                                                                                
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                
      
                                                                                            
      
                                                                                            
      Run the following command to check the process status:
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                                
      
                                                                                            
      
                                                                                            
      
                                                                                                
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      6. 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    On secondary DPS, follow these steps:
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Open a Command Promptterminal window as an administratorthe root user on secondary DPS.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                        
      
                                                                                            
      
                                                                                                
      For non-root installation, extract the files in / directory.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                        
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Run the following command:
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                    
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                    
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                                
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      Note 
                                                                                                    
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                    
       
      
                                                                                                    
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                            
      After the secondary DPS  is upgraded, that is,  after OBM2020.10 is installed and configured on the secondary DPS, start the services on the secondary 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. 
                                                                                                
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                                
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                            
      
                                                                                            
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                        
      
                                                                                    
      4. 
                                                                                    
    4. 
                                                                                        
      Check if the L-Core certificates are present, run the following command:
      
                                                                                        
      ovcert -list
                                                                                        
      
                                                                                        
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                        
      Stop agent process:
      
                                                                                        
      ovc -kill
                                                                                        
      
                                                                                        
      To restore agent certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/agent-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      To restore server certificates from backup:
      
                                                                                        
      
                                                                                            
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                            
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                        
      
                                                                                        
      
                                                                                            
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                            
      
                                                                                            
      cd/
                                                                                            
      
                                                                                            
      tar xzvf /backup/cs-certs.tar.gz
                                                                                            
      
                                                                                        
      
                                                                                        
      Start the agent process again:
      
                                                                                        
      ovc -start
                                                                                        
      
                                                                                    
      5. 
                                                                                    
    5. 
                                                                                        
      
                                                                                            
      
                                                                                                
      Enable OBM services on DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                                
      
                                                                                                    
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                    
      
                                                                                                    
      
                                                                                                        
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                    
      
                                                                                                    
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                                
      
                                                                                                
      
                                                                                                    
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                    
      
                                                                                                    
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                    
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                            
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                            
      
                                                                                                
      Run the following command to check the process status:
      
                                                                                                
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                                
      
                                                                                            
      
                                                                                            
      
                                                                                                
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      6. 
                                                                                
    
                                                                            
    6. 
                                                                        

                                                                        

                                                                            
After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
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 OBM host system, follow the steps:

                                                                        
    
                                                                            
  1. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user on active server.
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Run the following command on the active server of your existing OBM environment:
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh -s -silent
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                                
    After the active server is upgraded, that is, after OBM2020.10 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 lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    upgrade.bat -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    ./upgrade.sh  -s -silent  -archive=true
                                                                                    
    
                                                                                
    
                                                                                
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                            
    4. 
                                                                        

                                                                        
After you initiate the upgrade, follow the order to complete the upgrade process:

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

                                                                    

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    
                                                                                    
    
                                                                                        
    You must run the following commands  to stop services on the remaining inactive single server and gateway servers:
    
                                                                                        
    <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 remaining inactive single server and gateway servers as non-root user:
    
                                                                                        
    /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)
    
                                                                                    
    
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user on active server.
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    For non-root installation, extract the files in / directory.
    
                                                                                    
    
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Run the following command:
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent
                                                                                            
    
                                                                                            
    The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -gui
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed after the upgrade has finished and OBM is running.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    
                                                                                        
    upgrade.bat -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent-archive=true
                                                                                            
    
                                                                                            
    The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent -archive=true
                                                                                        
    
                                                                                        
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    In GUI upgrade, you need to choose the installation type and the path manually.
    
                                                                                
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    Check if the L-Core certificates are present, run the following command:
    
                                                                                
    ovcert -list
                                                                                
    
                                                                                
    If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
    
                                                                                
    Stop agent process:
    
                                                                                
    ovc -kill
                                                                                
    
                                                                                
    To restore agent certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/agent-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    To restore server certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/cs-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    Start the agent process again:
    
                                                                                
    ovc -start
                                                                                
    
                                                                            
    7. 
                                                                            
  7. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
    
                                                                                
    
                                                                                    
    Run the following command to check the process status:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
    
                                                                                
    
                                                                            
    8. 
                                                                        

                                                                        
Enable OBM services on active server  first. Then upgrade backup server following the steps 1-4 1-5 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.

                                                                        

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                            

                                                                

                                                                    

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

                                                                        
    
                                                                            
  1. 
                                                                                
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                                
    
                                                                                    
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                    
    
                                                                                
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Open a Command Promptterminal window as an administratorthe root user.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                                
    cd <OBMInstallationFilesDirectory>
                                                                                
    
                                                                                
    
                                                                                    
    Note: You should not have any whitespaces when you enter the path.
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    For non-root installation, extract the files in / directory.
    
                                                                                    
    
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Run the following command:
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent
                                                                                            
    
                                                                                            
    The -silent command by default, installs OBM 2020.10 to the same drive where the previous version is installed.  Run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -gui
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -gui
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The upgrade script stops the event flow. The event flow is resumed after the upgrade has finished and OBM is running.
    
                                                                                
    If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                                
    
                                                                                    
    
                                                                                        
    upgrade.bat -d -gui -archive=true
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    
                                                                                            
    upgrade.bat -d -silent -archive=true
    
                                                                                            
    The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
    
                                                                                            
    Optional.If you want OBM to be installed to a different location, run the following command:
    
                                                                                            
    upgrade.bat -d -silent -archive=true -filepath <full path of ovinstallparams.ini>
                                                                                            
    
                                                                                            
    where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
    
                                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
    ./upgrade.sh -d -silent -archive=true
                                                                                        
    
                                                                                        
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    
                                                                                        
     ./upgrade.sh -d -gui -archive=true
    
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    In GUI upgrade, you need to choose the installation type and the path manually.
    
                                                                                
    
                                                                                
    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. 
                                                                                    
    2.  Select Performance Engine, right-click and click Uninstall.
      3. 
                                                                                    
    3. Return to the upgrade script and type y to continue.
      4. 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Check if the L-Core certificates are present, run the following command:
    
                                                                                
    ovcert -list
                                                                                
    
                                                                                
    If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
    
                                                                                
    Stop agent process:
    
                                                                                
    ovc -kill
                                                                                
    
                                                                                
    To restore agent certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/agent-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    To restore server certificates from backup:
    
                                                                                
    
                                                                                    
    Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
    
                                                                                    
    Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
    
                                                                                
    
                                                                                
    
                                                                                    
    mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                    
    
                                                                                    
    cd/
                                                                                    
    
                                                                                    
    tar xzvf /backup/cs-certs.tar.gz
                                                                                    
    
                                                                                
    
                                                                                
    Start the agent process again:
    
                                                                                
    ovc -start
                                                                                
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    
                                                                                    
    Enable OBM services. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
    
                                                                                    
    
                                                                                        
    <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
    
                                                                                        
    
                                                                                            
    Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
    
                                                                                        
    
                                                                                        
    To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
    
                                                                                    
    
                                                                                    
    
                                                                                        
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
    
                                                                                        
    After the update is complete, run the following command to start the OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    
                                                                                
    
                                                                                
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
    
                                                                                
    
                                                                                    
    Run  the following command to check the process status:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                
    
                                                                                
    
                                                                                    
    To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
    
                                                                                
    
                                                                                
    After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.
    
                                                                            
    7. 
                                                                        

                                                                        

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        
This section applies only to the host system of the data processing server (DPS) in your BSMOBMexisting OBM deployment.

                                                                    

                                                                    

                                                                        

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

                                                                            
If you want to perform upgrade with minimal downtime, go back to the selection page and choose Distributed HA deployment.

                                                                        

                                                                    

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

                                                                    
Perform the following steps in order - Upgrade primary DPS and enable primary DPS then only start the upgrade of remaining gateway server and enable the gateway server.

                                                                    
    
                                                                        
  1. 
                                                                            
    If you have changed keysize or SHA algorithm of your L-core certificate (for example, from 2048 to 4096) you must upload the certificate to the database again. On the primary DPS, run the following commands:
    
                                                                            
    
                                                                                
    %TOPAZ_HOME%\opr\bin\opr-configure-certificates.bat -il
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    /opt/HP/BSM/opr/bin/opr-configure-certificates.sh -il
                                                                                
    
                                                                            
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    
                                                                                
    You must run the following commands  to stop services on the remaining 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 remaining gateway servers as non-root user:
    
                                                                                
    /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)
    
                                                                            
    
                                                                            
    The  event flow is paused when the gateway server is stopped. It is resumed on the production OBM after the DPS and atleast one of the gateway server upgrade is complete and OBM services is running.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Initiate the upgrade on primary DPS first, then gateway server. 
    
                                                                            
    On the DPS, follow these steps:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on primary DPS.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package. 
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini> 
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      If you have lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      upgrade.bat -d -gui -archive=true
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent-archive=true
                                                                                                
      
                                                                                                
      The -silent command, by default installs the ovinstallparams.ini file in the  to the same drive where the previous version is installed.
      
                                                                                                
      Optional.To customize the ovinstallparams.ini file location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent -archive=true
                                                                                            
      
                                                                                            
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui -archive=true
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Check if the L-Core certificates are present, run the following command:
      
                                                                                    
      ovcert -list
                                                                                    
      
                                                                                    
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                    
      Stop agent process:
      
                                                                                    
      ovc -kill
                                                                                    
      
                                                                                    
      To restore agent certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/agent-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      To restore server certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/cs-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      Start the agent process again:
      
                                                                                    
      ovc -start
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      
                                                                                        
      Enable OBM services on primary DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                            
      
                                                                                            
      
                                                                                                
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                            
      
                                                                                            
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                            
      
                                                                                            
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                            
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                    
      Run the following command to check the process status:
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    On gateway server, follow these steps. If there are multiple gateway servers, you can upgrade one gateway server at a time or multiple gateway servers concurrently. 
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on gateway server.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                            
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      Note 
                                                                                                
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                
       
      
                                                                                                
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      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. 
                                                                                            
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                            
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                        
      
                                                                                        
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Check if the L-Core certificates are present, run the following command:
      
                                                                                    
      ovcert -list
                                                                                    
      
                                                                                    
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                    
      Stop agent process:
      
                                                                                    
      ovc -kill
                                                                                    
      
                                                                                    
      To restore agent certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/agent-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      To restore server certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/cs-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      Start the agent process again:
      
                                                                                    
      ovc -start
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      
                                                                                        
      Enable OBM services on gateway server. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                        
      
                                                                                            
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                            
      
                                                                                            
      
                                                                                                
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                            
      
                                                                                            
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                        
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                            
      
                                                                                            
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                            
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                            
      
                                                                                        
      
                                                                                        
      Run the following command to check the process status:
      
                                                                                        
      
                                                                                            
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    5. 
                                                                        
  5. 
                                                                            
    On secondary DPS, follow these steps:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Open a Command Promptterminal window as an administratorthe root user on secondary DPS.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                            
      To view the console messages, refer the section Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      In GUI upgrade, you need to choose the installation type and the path manually.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      Note 
                                                                                                
      If the upgrade.sh -d -silent command does not start the uninstallation process, run the following command instead:
                                         
      
                                                                                                
       
      
                                                                                                
      "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      After the secondary DPS  is upgraded, that is,  after OBM2020.10 is installed and configured on the secondary DPS, start the services on the secondary 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. 
                                                                                            
      2.  Select Performance Engine, right-click and click Uninstall.
        3. 
                                                                                            
      3. Return to the upgrade script and type y to continue.
        4. 
                                                                                        
      
                                                                                        
      After the uninstallation completes, access the installation folder OBM_2020.10._for_Windows and manually run install.bat.
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Check if the L-Core certificates are present, run the following command:
      
                                                                                    
      ovcert -list
                                                                                    
      
                                                                                    
      If the certificates are not present, or the local agent certificate is missing, restore the certificates. 
      
                                                                                    
      Stop agent process:
      
                                                                                    
      ovc -kill
                                                                                    
      
                                                                                    
      To restore agent certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/agent-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      To restore server certificates from backup:
      
                                                                                    
      
                                                                                        
      Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old
      
                                                                                        
      Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks
      
                                                                                    
      
                                                                                    
      
                                                                                        
      mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                                        
      
                                                                                        
      cd/
                                                                                        
      
                                                                                        
      tar xzvf /backup/cs-certs.tar.gz
                                                                                        
      
                                                                                    
      
                                                                                    
      Start the agent process again:
      
                                                                                    
      ovc -start
                                                                                    
      
                                                                                
      5. 
                                                                                
    5. 
                                                                                    
      
                                                                                        
      
                                                                                            
      Enable OBM services on DPS. Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                            
      
                                                                                                
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                                
      
                                                                                                
      
                                                                                                    
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                                
      
                                                                                                
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                            
      
                                                                                            
      
                                                                                                
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                                
      
                                                                                                
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                                
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified time stamp.
      
                                                                                        
      
                                                                                            
      Run the following command to check the process status:
      
                                                                                            
      /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.
      
                                                                                        
      
                                                                                    
      
                                                                                
      6. 
                                                                            
    
                                                                        
    6. 
                                                                    

                                                                    

                                                                        
After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.

                                                                        

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

                                                                            

                                                                                
Replace the

                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                

                                                                                
line with the

                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                

                                                                                
line.

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        
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 OBM host system, follow the steps:

                                                                    
    
                                                                        
  1. 
                                                                            
    Open a Command Promptterminal window as an administratorthe root user on active server.
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Change the current directory to the location where you have extracted files from the OBM 2020.10 installation package to as follows:
    
                                                                            
    cd <OBMInstallationFilesDirectory>
                                                                            
    
                                                                            
    
                                                                                
    Note: You should not have any whitespaces when you enter the path.
    
                                                                            
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Run the following command on the active server of your existing OBM environment:
    
                                                                            
    
                                                                                
    upgrade.bat -s -silent
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    ./upgrade.sh -s -silent
                                                                                
    
                                                                            
    
                                                                            
    The upgrade script stops the event flow. The event flow is resumed on the production OBM after replicating the database and configuring event forwarding to the staging OBM.
    
                                                                            
    After the active server is upgraded, that is, after OBM2020.10 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 lot of closed events in the database, you can use  -archive=true parameter. If you do not set -archive parameter, by default no closed events will archive.
    
                                                                            
    
                                                                                
    upgrade.bat -s -silent  -archive=true
                                                                                
    
                                                                            
    
                                                                            
    
                                                                                
    ./upgrade.sh  -s -silent  -archive=true
                                                                                
    
                                                                            
    
                                                                            
    You can refer the console messages in Silent upgrade console output under Optional. Review the log files and console output, and enable IPv6 section.
    
                                                                        
    4. 
                                                                    

                                                                    
After you initiate the upgrade, follow the order to complete the upgrade process:

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

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Attend the initial upgradeupdate phase

                                                        

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

                                                            
    
                                                                
  • 
                                                                    
    	The event queue is emptied in primary DPSactive 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: Skipping backup for non-existent file /opt/HP/BSM/WebServer/conf.d
INFO: Backup file in ZIP: /var/opt/OV/backup/OMibackup.rsp
INFO: (./upgrade.sh) Found backup files in /var/opt/OV/backup/
INFO: (./upgrade.sh) Please copy the file /var/opt/OV/backup/OMiXXXXXcfg-backup.zip to your OBM target machine.

                                                                    

                                                                

                                                            

                                                            
 

                                                            

                                                                

                                                                    
INFO: (./upgrade.sh) Updating from OMi/OBM version 1100
INFO: (./upgrade.sh) Checking for multiple DPS setup
INFO: (./upgrade.sh) Multiple DPS detected. Will check for Active/Backup DPS
INFO: (./upgrade.sh) Checking if running on active DPS
INFO: (./upgrade.sh) Backup DPS detected
INFO: (./upgrade.sh) Checking if DB is already upgraded
INFO: (./upgrade.sh) DB has not been upgraded. Continuing upgrade as Minimal Downtime is supported.
INFO: Skipping preupgrade preparations for this upgrade.
INFO: (./upgrade.sh) Backing up config data and DB to /var/opt/OV/backup before upgrade. Please be patient...
INFO: Backup logs present in /var/opt/OV/log/opr-upgradeBackup.log
INFO: (./upgrade.sh) Found backup files in /var/opt/OV/backup/
								

                                                                    

                                                                

                                                            

                                                            
 

                                                            

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

                                                                    

                                                                

                                                            

                                                            
 

                                                            

                                                                

                                                                    
INFO: Updating from OMi/OBM version xxxx in directory C:\HPBSM
INFO: Skipping product_upgrade_wizard.bat installation for OMi/OBM source version 1100
INFO: Updating preuninstall.properties for per uninstall logs
INFO: Updating preuninstall properties completed with return code 0
INFO: Checking for multiple DPS setup
INFO: Multiple DPS detected
INFO: Checking if running on active DPS
INFO: Backup DPS detected
INFO: Checking if DB is already upgraded
INFO: DB has not been upgraded yet. Continuing upgrade as Minimal Downtime is supported.
INFO: Running PreMigration Tool to prepare for Upgrade
INFO: Skipping preupgrade preparations for this upgrade.
INFO: Backing up config data to C:\ProgramData\HP\HP BTO Software\backup\OMi1100 before upgrade. Please be patient...
INFO: Backup logs present in C:\ProgramData\HP\HP BTO Software\log\opr-upgradeBackup.log
INFO: Found backup files in C:\ProgramData\HP\HP BTO Software\backup\
								

                                                                    

                                                                

                                                            

                                                            

                                                                
Sometimes the following error may be reported as well:
Pre-upgrade process executed with some errors.


                                                                
If this occurs, press N to cancel pending uninstallation, restart the host system, and then initiate the upgradeupdate 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.10 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.10 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:

                                                                

                                                                    
Go to Start > Programs > Operations Bridge Manager > Enable Operations Bridge Manager.

                                                                    
Check the service status window to ensure all listed services are appeared. Go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                

                                                                

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

                                                                

                                                            

                                                            

                                                                
(Optional) Configure OBM for Oracle Real Application Clusters

                                                                
If the Oracle Database is configured in an Oracle Real Application Clusters (Oracle RAC) environment, then you must perform the additional configuration steps on the production servers. For more information, see Support for Oracle Real Application Cluster.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure event forwarding in the OBM production environment

                                                        

                                                            
ClosedConfigure the OBM production environment server to forward events to the staging OBM server
                                                                

                                                                    
Events coming into the BSMOBM production environment should also be forwarded to the OBM 2020.10 staging environment. These events will be queued in the  EVENT_SYNC_BUFFER database table until the OBM 2020.10 staging server is up and running.

                                                                    

                                                                        
Note Make sure the Event database has enough storage space available to hold the events until the OBM 2020.10 staging server is ready to receive them. As a general estimate, 2 KB to 20 KB per new event depending on the amount of data in the event attributes, the number of annotations and history lines.

                                                                    

                                                                    
    
                                                                        
  1. 
                                                                            
    Log on to BSMthe OBM production server.
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Go to Admin > Platform > Setup and Maintenance > Infrastructure SettingsAdministration > Setup and Maintenance > Infrastructure Settings.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Locate the Operations Management – Staging Upgrade Settings option group.
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    Set the Forward All Target Server option to the DNS name of the OBM 2020.10 staging gateway server.
    
                                                                        
    5. 
                                                                        
  5. 
                                                                            
    Set the Forward All option to true.
    
                                                                        
    6. 
                                                                    

                                                                

                                                            

                                                            
ClosedEnable event reception in BSMthe  production OBM environment
                                                                

                                                                    
    
                                                                        
  1. 
                                                                            
    Log on to BSMthe  production OBM server.
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Go to Admin > Platform > Setup and Maintenance > Infrastructure SettingsAdministration > Setup and Maintenance > Infrastructure Settings.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
     Locate the Operations Management – Event Pipeline Receiver Settings option group.
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    Set the Disable Receiving of Events option to false.
    
                                                                        
    5. 
                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Optional. Start the configuration wizard manually

                                                            

                                                                

                                                                    
If the OBM configuration wizard is successful, skip the below configuration wizard steps till Ready to Configure and go to the Review the summary and conclude the upgrade. Incase the OBM configuration wizard fails to complete silently, you can start the configuration wizard manually.

                                                                

                                                                

                                                                    
If the OBM configuration wizard is successful, skip the below configuration wizard step and go to Log on to OBM section. Incase the OBM configuration wizard fails to complete 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.

                                                                

                                                                    
Run the configuration wizard on primary DPS. 

                                                                

                                                                

                                                                    

                                                                        
Run the configuration wizard on primary DPS. 

                                                                    

                                                                    

                                                                        
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. Follow the steps below:
    
                                                                            
    For Windows Server 2008:
    
                                                                            
    Select Start > Programs > Operations Bridge Manager > Administration > Disable Operations Bridge Manager
    
                                                                            
    For Windows Server 2012:
    
                                                                            
    In Windows Search, start typing Disable Operations Bridge Manager, and then click Disable Operations Bridge Manager in the search results.
    
                                                                            
    
                                                                                
    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss or severe integrity problems.
    
                                                                            
    
                                                                        
    2. 
                                                                        
  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. 
                                                                                        
      2. 
                                                                                            
        Change the current directory as follows:
        
                                                                                            
        cd <OBM_HOME>\bin
                                                                                            
        
                                                                                        
        3. 
                                                                                        
      3. 
                                                                                            
        Run the following command:
        
                                                                                            
        config-server-wizard.bat
                                                                                            
        
                                                                                        
        4. 
                                                                                    
      
                                                                                
      • 
                                                                            
    
                                                                        
    3. 
                                                                    

                                                                

                                                                

                                                                    
To manually start the configuration wizard, follow the steps:

                                                                    
    
                                                                        
  1. 
                                                                            
    If this is not the first time you are starting the wizard, disable OBM. Run the following command:
    
                                                                            
    /opt/HP/BSM/scripts/run_hpbsm stopall
    
                                                                            
    
                                                                                
    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss and severe integrity problems.
    
                                                                            
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Open a command shell  as the root user.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Change the current directory as follows:
    
                                                                            
    cd /opt/HP/BSM/bin
                                                                            
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    Run the following command:
    
                                                                            
    ./config-server-wizard.sh.
    
                                                                            
    The configuration wizard starts.
    
                                                                        
    5. 
                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Optional. Start the configuration wizard manually

                                                        

                                                            

                                                                
If the OBM configuration wizard is successful, skip the below configuration wizard steps till Ready to Configure and go to the Review the summary and conclude the upgrade. Incase the OBM configuration wizard fails to complete silently, you can start the configuration wizard manually.

                                                            

                                                            

                                                                
If the OBM configuration wizard is successful, skip the below configuration wizard step and go to Log on to OBM section. Incase the OBM configuration wizard fails to complete 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.

                                                            

                                                                
Run the configuration wizard on primary DPS. 

                                                            

                                                            

                                                                

                                                                    
Run the configuration wizard on primary DPS. 

                                                                

                                                                

                                                                    
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. Follow the steps below:
    
                                                                        
    For Windows Server 2008:
    
                                                                        
    Select Start > Programs > Operations Bridge Manager > Administration > Disable Operations Bridge Manager
    
                                                                        
    For Windows Server 2012:
    
                                                                        
    In Windows Search, start typing Disable Operations Bridge Manager, and then click Disable Operations Bridge Manager in the search results.
    
                                                                        
    
                                                                            
    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss or severe integrity problems.
    
                                                                        
    
                                                                    
    2. 
                                                                    
  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. 
                                                                                    
      2. 
                                                                                        
        Change the current directory as follows:
        
                                                                                        
        cd <OBM_HOME>\bin
                                                                                        
        
                                                                                    
        3. 
                                                                                    
      3. 
                                                                                        
        Run the following command:
        
                                                                                        
        config-server-wizard.bat
                                                                                        
        
                                                                                    
        4. 
                                                                                
      
                                                                            
      • 
                                                                        
    
                                                                    
    3. 
                                                                

                                                            

                                                            

                                                                
To manually start the configuration wizard, follow the steps:

                                                                
    
                                                                    
  1. 
                                                                        
    If this is not the first time you are starting the wizard, disable OBM. Run the following command:
    
                                                                        
    /opt/HP/BSM/scripts/run_hpbsm stopall
    
                                                                        
    
                                                                            
    Caution Modifying connection parameters for the Management, RTSM, and Event databases while OBM is enabled may cause data loss and severe integrity problems.
    
                                                                        
    
                                                                    
    2. 
                                                                    
  2. 
                                                                        
    Open a command shell  as the root user.
    
                                                                    
    3. 
                                                                    
  3. 
                                                                        
    Change the current directory as follows:
    
                                                                        
    cd /opt/HP/BSM/bin
                                                                        
    
                                                                    
    4. 
                                                                    
  4. 
                                                                        
    Run the following command:
    
                                                                        
    ./config-server-wizard.sh.
    
                                                                        
    The configuration wizard starts.
    
                                                                    
    5. 
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Choose configuration options

                                                        

                                                            

                                                                
This section is applicable for data processing server and  gateway server.

                                                            

                                                            
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 of upgradeupdate. Then click Next to continue.

                                                            

                                                                
By default, the OBM processes run by using the root account. You can configure OBM to run by using a different user account.

                                                                
    
                                                                    
  1. 
                                                                        
    Create a non-root user account on all OBM servers, for example, by using the operating system's useradd or adduser command.
    
                                                                        
    Configure the maximum number of processes for this user account by adding the following line to the existing *nproc.conf file in the /etc/security/limits.d directory.
    
                                                                        
    <UserName>       soft    nproc     unlimited
                                                                        
    
                                                                        
    Replace <UserName> with the non-root user account.
    
                                                                    
    2. 
                                                                    
  2. 
                                                                        
    In the Configuration Options page, click Run OBM processes as non-root user to configure OBM to run by using a different user account.
    
                                                                    
    3. 
                                                                    
  3. 
                                                                        
    Type the User name of the non-root user account you created earlier.
    
                                                                    
    4. 
                                                                    
  4. Click Next.
    5. 
                                                                

                                                            

                                                            

                                                                Upgrade wizard: Database Connection page
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Choose configuration options

                                                        

                                                            

                                                                
This section is applicable for data processing server and  gateway server.

                                                            

                                                            
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 of upgradeupdate. Then click Next to continue.

                                                            

                                                                
By default, the OBM processes run by using the root account. You can configure OBM to run by using a different user account.

                                                                
    
                                                                    
  1. 
                                                                        
    Create a non-root user account on all OBM servers, for example, by using the operating system's useradd or adduser command.
    
                                                                        
    Configure the maximum number of processes for this user account by adding the following line to the existing *nproc.conf file in the /etc/security/limits.d directory.
    
                                                                        
    <UserName>       soft    nproc     unlimited
                                                                        
    
                                                                        
    Replace <UserName> with the non-root user account.
    
                                                                    
    2. 
                                                                    
  2. 
                                                                        
    In the Configuration Options page, click Run OBM processes as non-root user to configure OBM to run by using a different user account.
    
                                                                    
    3. 
                                                                    
  3. 
                                                                        
    Type the User name of the non-root user account you created earlier.
    
                                                                    
    4. 
                                                                    
  4. Click Next.
    5. 
                                                                

                                                            

                                                            

                                                                Upgrade wizard: Database Connection page
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure the database settings

                                                        

                                                            
This section is applicable for data processing server and gateway server.

                                                        

                                                        

                                                            
This section is applicable for both the data processing servers and gateway 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. The credentials for the administrative access are auto-populated for  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
                                                                

                                                                
Click Next to continue.

                                                            

                                                            

                                                                

                                                                    
Select Upgrade database from a previous version of OBM on the Database Settings page to start the upgrade. The credentials for the administrative access are auto-populated for Microsoft SQL Server databaseOracle Database instancePostgreSQL database. Click Browse and choose the backup zip file located at <TOPAZ_HOME>/backup/OMi<Previous_Version>cfg-backup.zip.

                                                                

                                                                

                                                                    
Select Upgrade database from a previous version of OBM on the Database Settings page to start the upgrade. The credentials for the administrative access are auto-populated for Microsoft SQL Server databaseOracle Database instancePostgreSQL database. Click Browse and choose the backup zip file located at /var/opt/OV/backup/OMi<Previous_Version>cfg-backup.zip.

                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                
Click Next to continue.

                                                            

                                                        

                                                        

                                                            

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

                                                                
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 for Microsoft SQL Server databaseOracle Database instancePostgreSQL database. Click Browse and choose the backup zip file located at /var/opt/OV/backup/OMi<Previous_Version>cfg-backup.zip<TOPAZ_HOME>/backup/OMi<Previous_Version>cfg-backup.zip.

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                
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 data processing server and gateway server.

                                                        

                                                        

                                                            
This section is applicable for both the data processing servers and gateway 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. The credentials for the administrative access are auto-populated for  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
                                                                

                                                                
Click Next to continue.

                                                            

                                                            

                                                                

                                                                    
Select Upgrade database from a previous version of OBM on the Database Settings page to start the upgrade. The credentials for the administrative access are auto-populated for Microsoft SQL Server databaseOracle Database instancePostgreSQL database. Click Browse and choose the backup zip file located at <TOPAZ_HOME>/backup/OMi<Previous_Version>cfg-backup.zip.

                                                                

                                                                

                                                                    
Select Upgrade database from a previous version of OBM on the Database Settings page to start the upgrade. The credentials for the administrative access are auto-populated for Microsoft SQL Server databaseOracle Database instancePostgreSQL database. Click Browse and choose the backup zip file located at /var/opt/OV/backup/OMi<Previous_Version>cfg-backup.zip.

                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                
Click Next to continue.

                                                            

                                                        

                                                        

                                                            

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

                                                                
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 for Microsoft SQL Server databaseOracle Database instancePostgreSQL database. Click Browse and choose the backup zip file located at /var/opt/OV/backup/OMi<Previous_Version>cfg-backup.zip<TOPAZ_HOME>/backup/OMi<Previous_Version>cfg-backup.zip.

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                

                                                                    Upgrade wizard: Database Connection page
                                                                

                                                                
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 TLS setup

                                                        

                                                            

                                                                
This section is applicable for data processing server and gateway server.

                                                            

                                                            
The TLS Setup page enables you to configure OBM to accept only secure connections to its web server and the JMX consoles.

                                                            

                                                                
If you do not want to use HTTPS (not recommended), clear the Enable HTTPS option.

                                                            

                                                            

                                                                
When upgrading from OMi 2020.05 to OBM 2020.10, the following options are available to configure your TLS setup:
				
  • Enable TLS by following the next steps. Note that you have to reupload the certificates that you used for your former BSM TLS setup.
  • Disable TLS by clearing the Enable HTTPS option (not recommended).

                                                            

                                                            

                                                                
Note Your TLS setup should be consistent for every server.

                                                            

                                                            

                                                                Configuration wizard: TLS Setup page
                                                            

                                                            
If your company uses a certification authority (CA) that can generate certificates for OBM, click the Upload certificates option. Alternatively, click OBM-generated certificates to make OBM generate the certificates required for the configuration.

                                                            

                                                                
Note For maximum security, we recommend to use certificates that were issued by the certification authority of your company.

                                                                
If you choose to use OBM-generated certificates, the CA will be retained. Make sure to establish trust in the web browser from which you will log on to OBM. For instructions on how to do that, see the Establish Trust in the Browser.

                                                            

                                                            
ClosedRecommended. Upload custom certificates
                                                                

                                                                    

                                                                        
                                                                    

                                                                    
Proceed as follows:

                                                                    
    
                                                                        
  1. 
                                                                            
    Obtain server certificates from your CA. 
    
                                                                            
    Generally, server certificates must be issued to the name of the external access point (FQDN) of OBM. This is the name that users and data collectors use to access OBM.
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Make sure Enable HTTPS is selected.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Click Upload certificates and then click Next.
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
     In the Certificate Upload page, specify the certificates you received from the CA used by your company:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Specify the server certificate  issued for the server you are currently configuring. The uploaded file must include both the certificate and private key and must be in .p12 or .pfx format.
      
                                                                                    
      Enter the password for the .p12 or .pfx file.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Specify the CA root certificate (PEM format). 
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Optional. Specify the certificate chain without the root CA if the server certificate was issued by a subordinate CA. The certificate file must be PEM-encoded. Click Clear to remove the selected file.
      
                                                                                
      4. 
                                                                            
    
                                                                        
    5. 
                                                                        
  5. 
                                                                            
    Click Next to continue.
    
                                                                        
    6. 
                                                                    

                                                                

                                                            

                                                            
ClosedUse certificates generated by OBM
                                                                

                                                                    
Proceed as follows:

                                                                    
    
                                                                        
  1. 
                                                                            
    Make sure Enable HTTPS is selected.
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Make sure OBM-generated certificates is selected and click Next.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Optional. In the OBM Certificate Generation page, you can customize the key options and contents of the certificates generated by the OBM CA. You can define certificate settings for the OBM root CA and for the OBM server for which the certificate is issued:
    
                                                                            
      
                                                                                
    • 
                                                                                    
      Key length: Size of the RSA key. 
      
                                                                                
      • 
                                                                                
    • 
                                                                                    
      Certificate validity (days): Time period after which the issued certificates will expire.
      
                                                                                
      • 
                                                                                
    • 
                                                                                    
      Organization: Legal name of your business or organization.
      
                                                                                
      • 
                                                                                
    • 
                                                                                    
      Country: Country where your business is registered with the government.
      
                                                                                
      • 
                                                                                
    • 
                                                                                    
      Common name: Name of the OBM CA that issues the certificates.
      
                                                                                
      • 
                                                                            
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    Click Next to continue.
    
                                                                        
    5. 
                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure the TLS setup

                                                        

                                                            

                                                                
This section is applicable for data processing server and gateway server.

                                                            

                                                            
The TLS Setup page enables you to configure OBM to accept only secure connections to its web server and the JMX consoles.

                                                            

                                                                
If you do not want to use HTTPS (not recommended), clear the Enable HTTPS option.

                                                            

                                                            

                                                                
When upgrading from OMi 2020.05 to OBM 2020.10, the following options are available to configure your TLS setup:
				
  • Enable TLS by following the next steps. Note that you have to reupload the certificates that you used for your former BSM TLS setup.
  • Disable TLS by clearing the Enable HTTPS option (not recommended).

                                                            

                                                            

                                                                
Note Your TLS setup should be consistent for every server.

                                                            

                                                            

                                                                Configuration wizard: TLS Setup page
                                                            

                                                            
If your company uses a certification authority (CA) that can generate certificates for OBM, click the Upload certificates option. Alternatively, click OBM-generated certificates to make OBM generate the certificates required for the configuration.

                                                            

                                                                
Note For maximum security, we recommend to use certificates that were issued by the certification authority of your company.

                                                                
If you choose to use OBM-generated certificates, the CA will be retained. Make sure to establish trust in the web browser from which you will log on to OBM. For instructions on how to do that, see the Establish Trust in the Browser.

                                                            

                                                            
ClosedRecommended. Upload custom certificates
                                                                

                                                                    

                                                                        
                                                                    

                                                                    
Proceed as follows:

                                                                    
    
                                                                        
  1. 
                                                                            
    Obtain server certificates from your CA. 
    
                                                                            
    Generally, server certificates must be issued to the name of the external access point (FQDN) of OBM. This is the name that users and data collectors use to access OBM.
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Make sure Enable HTTPS is selected.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Click Upload certificates and then click Next.
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
     In the Certificate Upload page, specify the certificates you received from the CA used by your company:
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Specify the server certificate  issued for the server you are currently configuring. The uploaded file must include both the certificate and private key and must be in .p12 or .pfx format.
      
                                                                                    
      Enter the password for the .p12 or .pfx file.
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      Specify the CA root certificate (PEM format). 
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Optional. Specify the certificate chain without the root CA if the server certificate was issued by a subordinate CA. The certificate file must be PEM-encoded. Click Clear to remove the selected file.
      
                                                                                
      4. 
                                                                            
    
                                                                        
    5. 
                                                                        
  5. 
                                                                            
    Click Next to continue.
    
                                                                        
    6. 
                                                                    

                                                                

                                                            

                                                            
ClosedUse certificates generated by OBM
                                                                

                                                                    
Proceed as follows:

                                                                    
    
                                                                        
  1. 
                                                                            
    Make sure Enable HTTPS is selected.
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    Make sure OBM-generated certificates is selected and click Next.
    
                                                                        
    3. 
                                                                        
  3. 
                                                                            
    Optional. In the OBM Certificate Generation page, you can customize the key options and contents of the certificates generated by the OBM CA. You can define certificate settings for the OBM root CA and for the OBM server for which the certificate is issued:
    
                                                                            
      
                                                                                
    • 
                                                                                    
      Key length: Size of the RSA key. 
      
                                                                                
      • 
                                                                                
    • 
                                                                                    
      Certificate validity (days): Time period after which the issued certificates will expire.
      
                                                                                
      • 
                                                                                
    • 
                                                                                    
      Organization: Legal name of your business or organization.
      
                                                                                
      • 
                                                                                
    • 
                                                                                    
      Country: Country where your business is registered with the government.
      
                                                                                
      • 
                                                                                
    • 
                                                                                    
      Common name: Name of the OBM CA that issues the certificates.
      
                                                                                
      • 
                                                                            
    
                                                                        
    4. 
                                                                        
  4. 
                                                                            
    Click Next to continue.
    
                                                                        
    5. 
                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Configure client certificate authentication

                                                            

                                                                

                                                                    
This section is applicable on each gateway server.

                                                                

                                                                

                                                                    
Note For a side-by-side upgrade, the staging OBM must use the same settings as the production OBM.  For example, if the production OBM is not using client certificates, then select "No client certificate based authentication".  If the production OBM is using client certificates, then configure the staging OBM exactly the same. You can change the client authentication after the upgrade is completed and the staging OBM is  enabled at least once.

                                                                

                                                                
The Client Certificate Authentication page enables you to configure OBM to require a client certificate when users log on to OBM or when web services connect to OBM. Depending on the deployment type, you can configure OBM to authenticate the client on the OBM web server or, if available, on the load balancer.

                                                                

                                                                    
Caution Do not enable client certificate authentication if you are configuring OBM for the first time. Before enabling client-certificate authentication, OBM must be already configured and the superuser must exist.

                                                                

                                                                

                                                                    Configuration wizard: Client Certificate Authentication page
                                                                

                                                                
ClosedNo client certificate based authentication (default)
                                                                    

                                                                        
Make sure the No client certificate based authentication option is selected if this type of security is not required in your environment or if you want to configure client authentication later. 

                                                                    

                                                                

                                                                

                                                                    
ClosedAuthentication on OBM web server
                                                                        

                                                                            

                                                                                
                                                                            

                                                                            
    
                                                                                
  1. 
                                                                                    
    Click  Authentication on OBM web server.
    
                                                                                
    2. 
                                                                                
  2. 
                                                                                    
    Select the certificate of the CA that issued the client certificate. The certificate file must be PEM-encoded.
    
                                                                                
    3. 
                                                                                
  3. 
                                                                                    
    Choose how OBM checks whether the client certificate has been revoked:
    
                                                                                    
      
                                                                                        
    • 
                                                                                            
      None: OBM does not check the revocation status.
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      OCSP URL from certificate: OBM sends an OCSP request to the URL provided in the client certificate and evaluates the OCSP response to determine the revocation status of the certificate.
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Local CRL file (PEM format): OBM checks the revocation status in a CRL file local to the gateway server. Make sure the CRL file on the gateway server is the latest one available from your CA. 
      
                                                                                        
      • 
                                                                                    
    
                                                                                
    4. 
                                                                                
  4. 
                                                                                    
    Specify the certificate data that is used for authentication:
    
                                                                                    
      
                                                                                        
    • 
                                                                                            
      Attribute used to identify users: Use the drop-down list to select the attribute that OBM uses to identify users, for example SubjectDN or SubjectAlternativeName.
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Relevant element of attribute field (for example, CN): Specify the element of the attribute  that OBM uses to identify users, for example CN.
      
                                                                                        
      • 
                                                                                    
    
                                                                                
    5. 
                                                                                
  5. 
                                                                                    
    Optional. Click Enforce use of smart card certificates to configure OBM to always require a smart card when a user logs on.
    
                                                                                
    6. 
                                                                                
  6. 
                                                                                    
    Click Next to continue.
    
                                                                                
    7. 
                                                                            

                                                                        

                                                                    

                                                                    
ClosedAuthentication on load balancer
                                                                        

                                                                            

                                                                                
                                                                            

                                                                            
    
                                                                                
  1. 
                                                                                    
    Click  Authentication on load balancer.
    
                                                                                
    2. 
                                                                                
  2. 
                                                                                    
    Specify the certificate data that is used for authentication:
    
                                                                                    
      
                                                                                        
    • 
                                                                                            
      Attribute used to identify users: Use the drop-down list to select the attribute that OBM uses to identify users, for example SubjectDN or SubjectAlternativeName.
      
                                                                                        
      • 
                                                                                        
    • 
                                                                                            
      Relevant element of attribute field (for example, CN): Specify the element of the attribute  that OBM uses to identify users, for example CN.
      
                                                                                        
      • 
                                                                                    
    
                                                                                
    3. 
                                                                                
  3. 
                                                                                    
    Optional. Click Enforce use of smart card certificates to configure OBM to always require a smart card when a user logs on.
    
                                                                                
    4. 
                                                                                
  4. 
                                                                                    
    Click Next to continue.
    
                                                                                
    5. 
                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure client certificate authentication

                                                        

                                                            

                                                                
This section is applicable on each gateway server.

                                                            

                                                            

                                                                
Note For a side-by-side upgrade, the staging OBM must use the same settings as the production OBM.  For example, if the production OBM is not using client certificates, then select "No client certificate based authentication".  If the production OBM is using client certificates, then configure the staging OBM exactly the same. You can change the client authentication after the upgrade is completed and the staging OBM is  enabled at least once.

                                                            

                                                            
The Client Certificate Authentication page enables you to configure OBM to require a client certificate when users log on to OBM or when web services connect to OBM. Depending on the deployment type, you can configure OBM to authenticate the client on the OBM web server or, if available, on the load balancer.

                                                            

                                                                
Caution Do not enable client certificate authentication if you are configuring OBM for the first time. Before enabling client-certificate authentication, OBM must be already configured and the superuser must exist.

                                                            

                                                            

                                                                Configuration wizard: Client Certificate Authentication page
                                                            

                                                            
ClosedNo client certificate based authentication (default)
                                                                

                                                                    
Make sure the No client certificate based authentication option is selected if this type of security is not required in your environment or if you want to configure client authentication later. 

                                                                

                                                            

                                                            

                                                                
ClosedAuthentication on OBM web server
                                                                    

                                                                        

                                                                            
                                                                        

                                                                        
    
                                                                            
  1. 
                                                                                
    Click  Authentication on OBM web server.
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Select the certificate of the CA that issued the client certificate. The certificate file must be PEM-encoded.
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Choose how OBM checks whether the client certificate has been revoked:
    
                                                                                
      
                                                                                    
    • 
                                                                                        
      None: OBM does not check the revocation status.
      
                                                                                    
      • 
                                                                                    
    • 
                                                                                        
      OCSP URL from certificate: OBM sends an OCSP request to the URL provided in the client certificate and evaluates the OCSP response to determine the revocation status of the certificate.
      
                                                                                    
      • 
                                                                                    
    • 
                                                                                        
      Local CRL file (PEM format): OBM checks the revocation status in a CRL file local to the gateway server. Make sure the CRL file on the gateway server is the latest one available from your CA. 
      
                                                                                    
      • 
                                                                                
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Specify the certificate data that is used for authentication:
    
                                                                                
      
                                                                                    
    • 
                                                                                        
      Attribute used to identify users: Use the drop-down list to select the attribute that OBM uses to identify users, for example SubjectDN or SubjectAlternativeName.
      
                                                                                    
      • 
                                                                                    
    • 
                                                                                        
      Relevant element of attribute field (for example, CN): Specify the element of the attribute  that OBM uses to identify users, for example CN.
      
                                                                                    
      • 
                                                                                
    
                                                                            
    5. 
                                                                            
  5. 
                                                                                
    Optional. Click Enforce use of smart card certificates to configure OBM to always require a smart card when a user logs on.
    
                                                                            
    6. 
                                                                            
  6. 
                                                                                
    Click Next to continue.
    
                                                                            
    7. 
                                                                        

                                                                    

                                                                

                                                                
ClosedAuthentication on load balancer
                                                                    

                                                                        

                                                                            
                                                                        

                                                                        
    
                                                                            
  1. 
                                                                                
    Click  Authentication on load balancer.
    
                                                                            
    2. 
                                                                            
  2. 
                                                                                
    Specify the certificate data that is used for authentication:
    
                                                                                
      
                                                                                    
    • 
                                                                                        
      Attribute used to identify users: Use the drop-down list to select the attribute that OBM uses to identify users, for example SubjectDN or SubjectAlternativeName.
      
                                                                                    
      • 
                                                                                    
    • 
                                                                                        
      Relevant element of attribute field (for example, CN): Specify the element of the attribute  that OBM uses to identify users, for example CN.
      
                                                                                    
      • 
                                                                                
    
                                                                            
    3. 
                                                                            
  3. 
                                                                                
    Optional. Click Enforce use of smart card certificates to configure OBM to always require a smart card when a user logs on.
    
                                                                            
    4. 
                                                                            
  4. 
                                                                                
    Click Next to continue.
    
                                                                            
    5. 
                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure general OBM connection settings

                                                        

                                                            

                                                                
This section is applicable to each gateway server.

                                                            

                                                        

                                                        

                                                            

                                                                
The Connection (Connection Settings) page informs you that Apache HTTP Server will be used as the web server for OBM.  Additionally, you can configure the URL that  users use to access OBM.

                                                            

                                                            

                                                                
In the Connection (Connection Settings) page, you can choose the web server to be used by OBM. Additionally, you can configure the URL that  users use to access OBM.

                                                            

                                                            

                                                                
Note The configuration wizard displays the Connection (Connection Settings) page only during configuration of an single-server OBM installation or an OBM gateway server. The wizard skips it during configuration of an OBM data processing server.

                                                            

                                                            

                                                                Upgrade wizard: Connection Settings page
                                                            

                                                            

                                                                Upgrade wizard: Connection Settings page
                                                            

                                                            

                                                                
Under Web server, enter the port for the web server that you want to use with your OBM deployment. 

                                                                
OBM installs Apache HTTP Server on all gateway servers during the installation. By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server.  If the default port is already in use, specify a different port.

                                                            

                                                            

                                                                
Web server. In Linux environments, OBM uses Apache HTTP Server.

                                                                
Apache HTTP Server.   OBM installs Apache HTTP Server on the gateway server during the installation.

                                                                
By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server.  If the default port is already in use, specify a different port.

                                                            

                                                            

                                                                
OBM URL. By default, users access OBM through the fully qualified domain name and web server port of the single or gateway server. If the default port is changed, update the port number in the OBM URL text box, for example, https://obmweb.company.com:8000.

                                                                

                                                                    
Note Do not provide short hostname. It is not supported. 

                                                                

                                                                

                                                                    
If you have a load balancer that is used to access the OBM site, enter the fully qualified domain name and port of the load balancer.

                                                                

                                                            

                                                            
Click Next.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure general OBM connection settings

                                                        

                                                            

                                                                
This section is applicable to each gateway server.

                                                            

                                                        

                                                        

                                                            

                                                                
The Connection (Connection Settings) page informs you that Apache HTTP Server will be used as the web server for OBM.  Additionally, you can configure the URL that  users use to access OBM.

                                                            

                                                            

                                                                
In the Connection (Connection Settings) page, you can choose the web server to be used by OBM. Additionally, you can configure the URL that  users use to access OBM.

                                                            

                                                            

                                                                
Note The configuration wizard displays the Connection (Connection Settings) page only during configuration of an single-server OBM installation or an OBM gateway server. The wizard skips it during configuration of an OBM data processing server.

                                                            

                                                            

                                                                Upgrade wizard: Connection Settings page
                                                            

                                                            

                                                                Upgrade wizard: Connection Settings page
                                                            

                                                            

                                                                
Under Web server, enter the port for the web server that you want to use with your OBM deployment. 

                                                                
OBM installs Apache HTTP Server on all gateway servers during the installation. By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server.  If the default port is already in use, specify a different port.

                                                            

                                                            

                                                                
Web server. In Linux environments, OBM uses Apache HTTP Server.

                                                                
Apache HTTP Server.   OBM installs Apache HTTP Server on the gateway server during the installation.

                                                                
By default, OBM runs Apache HTTP Server so that it listens on port 443 (HTTPS). Click Check Port to verify the connection to the web server.  If the default port is already in use, specify a different port.

                                                            

                                                            

                                                                
OBM URL. By default, users access OBM through the fully qualified domain name and web server port of the single or gateway server. If the default port is changed, update the port number in the OBM URL text box, for example, https://obmweb.company.com:8000.

                                                                

                                                                    
Note Do not provide short hostname. It is not supported. 

                                                                

                                                                

                                                                    
If you have a load balancer that is used to access the OBM site, enter the fully qualified domain name and port of the load balancer.

                                                                

                                                            

                                                            
Click Next.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure the license

                                                        

                                                            

                                                                
This section is applicable for data processing server and gateway server.

                                                            

                                                            
In the License page, you can configure the license that OBM uses.

                                                            

                                                                Upgrade wizard: License page
                                                            

                                                            
Depending on your recent actions, you have different options:

                                                            
    
                                                                
  • 
                                                                    
    If the wizard is running for the first time, you can choose to use the evaluation license or to upload your new license to the server.
    
                                                                
    • 
                                                                
  • 
                                                                    
    If this is not the first time the wizard is running, you can select to skip this step or upload additional licenses.
    
                                                                
    • 
                                                            

                                                            

                                                                
To update your licenses after the upgrade, make the necessary changes in the License Management page of the OBM user interface 

                                                            

                                                            

                                                                
Note The license file has the .dat file name extension and must reside at a local or network location accessible to the host system where the wizard is running.

                                                            

                                                            
Click Next.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure the license

                                                        

                                                            

                                                                
This section is applicable for data processing server and gateway server.

                                                            

                                                            
In the License page, you can configure the license that OBM uses.

                                                            

                                                                Upgrade wizard: License page
                                                            

                                                            
Depending on your recent actions, you have different options:

                                                            
    
                                                                
  • 
                                                                    
    If the wizard is running for the first time, you can choose to use the evaluation license or to upload your new license to the server.
    
                                                                
    • 
                                                                
  • 
                                                                    
    If this is not the first time the wizard is running, you can select to skip this step or upload additional licenses.
    
                                                                
    • 
                                                            

                                                            

                                                                
To update your licenses after the upgrade, make the necessary changes in the License Management page of the OBM user interface 

                                                            

                                                            

                                                                
Note The license file has the .dat file name extension and must reside at a local or network location accessible to the host system where the wizard is running.

                                                            

                                                            
Click Next.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure the login settings

                                                        

                                                            

                                                                
This section is applicable for  data processing server.

                                                            

                                                            
In the Login Settings page, you can set the passwords for the OBM users.

                                                            
OBM supports central user management and corporate password policies, it can communicate with the directory services by using LDAP. We recommend such configuration to enforce compliance of OBM user passwords with the respective security policy in your company.  To configure the LDAP integration, navigate to Administration > Users > Authentication Management in the OBM user interface.

                                                            
LDAP authentication of all users is possible only when the mixed mode authentication is disabled in the OBM LDAP infrastructure settings. For instructions on how to adjust this setting, see the "LDAP Authentication" section in Authentication Management.

                                                            

                                                                Upgrade wizard: Update Environment - Login Settings page
                                                            

                                                            
To configure OBM passwords, specify the following options:

                                                            
    
                                                                
  • 
                                                                    
    Administrator password, Confirm. Type the password of the OBM administrator (user name: admin) for the OBM user interface. This  password is required to log on to OBM, and can be changed in the OBM user interface at a later time.
    
                                                                
    • 
                                                                
  • 
                                                                    
    JMX password, Confirm. Type the password to be used by the OBM administrator  for all OBM JMX consoles (user name: admin) and for the RTSM JMX console (user name: sysadmin). If there is a default password already present, re-enter the new password. 
    
                                                                    
    
                                                                        
    Note The JMX password is valid on all host systems that constitute your OBM environment.
    
                                                                    
    
                                                                
    • 
                                                            

                                                            
Click Next.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure the login settings

                                                        

                                                            

                                                                
This section is applicable for  data processing server.

                                                            

                                                            
In the Login Settings page, you can set the passwords for the OBM users.

                                                            
OBM supports central user management and corporate password policies, it can communicate with the directory services by using LDAP. We recommend such configuration to enforce compliance of OBM user passwords with the respective security policy in your company.  To configure the LDAP integration, navigate to Administration > Users > Authentication Management in the OBM user interface.

                                                            
LDAP authentication of all users is possible only when the mixed mode authentication is disabled in the OBM LDAP infrastructure settings. For instructions on how to adjust this setting, see the "LDAP Authentication" section in Authentication Management.

                                                            

                                                                Upgrade wizard: Update Environment - Login Settings page
                                                            

                                                            
To configure OBM passwords, specify the following options:

                                                            
    
                                                                
  • 
                                                                    
    Administrator password, Confirm. Type the password of the OBM administrator (user name: admin) for the OBM user interface. This  password is required to log on to OBM, and can be changed in the OBM user interface at a later time.
    
                                                                
    • 
                                                                
  • 
                                                                    
    JMX password, Confirm. Type the password to be used by the OBM administrator  for all OBM JMX consoles (user name: admin) and for the RTSM JMX console (user name: sysadmin). If there is a default password already present, re-enter the new password. 
    
                                                                    
    
                                                                        
    Note The JMX password is valid on all host systems that constitute your OBM environment.
    
                                                                    
    
                                                                
    • 
                                                            

                                                            
Click Next.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure the server deployment

                                                        

                                                            
This section is applicable for data processing and gateway sever.

                                                        

                                                        

                                                            
In the Server Deployment page, you can  define the expected size of the environment monitored by OBM.

                                                            

                                                                
                                                            

                                                            

                                                                
Note When configuring a gateway server, the number of nodes cannot be configured because the selections are taken from the data processing server.

                                                            

                                                            
    
                                                                
  1. 
                                                                    
    Select the Number of monitored nodes that send events to OBM. This includes all nodes that are present as CIs and that send events to OBM  (for example, nodes connected to HP Operations Manager (OM), nodes sending events via other domain managers (For example: NNMi, SCOM, etc).
    
                                                                
    2. 
                                                                
  2. 
                                                                    
    Optional. Click Advanced to adjust the maximum memory that the Java Virtual Machine (JVM) allocates to the OBM processes. To change the allocated memory, click Manual override and type the new values in the text boxes.
    
                                                                
    3. 
                                                                
  3. 
                                                                    
    Click Next.
    
                                                                
    4. 
                                                            

                                                            
The required memory shown in the Configuration Wizard is calculated dynamically based on the memory that is given to all the processes which make up the OBM server. It also takes into account the overrides which a customer might do in the Advanced section. However, it does not include any other consumers of memory on the system, like the basic OS processes/services or CLIs which also need a considerable amount of the available memory.  The memory requirements specified in Check the hardware requirements section take these into consideration and are therefore higher.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Configure the server deployment

                                                        

                                                            
This section is applicable for data processing and gateway sever.

                                                        

                                                        

                                                            
In the Server Deployment page, you can  define the expected size of the environment monitored by OBM.

                                                            

                                                                
                                                            

                                                            

                                                                
Note When configuring a gateway server, the number of nodes cannot be configured because the selections are taken from the data processing server.

                                                            

                                                            
    
                                                                
  1. 
                                                                    
    Select the Number of monitored nodes that send events to OBM. This includes all nodes that are present as CIs and that send events to OBM  (for example, nodes connected to HP Operations Manager (OM), nodes sending events via other domain managers (For example: NNMi, SCOM, etc).
    
                                                                
    2. 
                                                                
  2. 
                                                                    
    Optional. Click Advanced to adjust the maximum memory that the Java Virtual Machine (JVM) allocates to the OBM processes. To change the allocated memory, click Manual override and type the new values in the text boxes.
    
                                                                
    3. 
                                                                
  3. 
                                                                    
    Click Next.
    
                                                                
    4. 
                                                            

                                                            
The required memory shown in the Configuration Wizard is calculated dynamically based on the memory that is given to all the processes which make up the OBM server. It also takes into account the overrides which a customer might do in the Advanced section. However, it does not include any other consumers of memory on the system, like the basic OS processes/services or CLIs which also need a considerable amount of the available memory.  The memory requirements specified in Check the hardware requirements section take these into consideration and are therefore higher.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Deploy management packs

                                                        

                                                            

                                                                

                                                                    
Caution This section is applicable for data processing server.

                                                                

                                                            

                                                            
In the Management Packs page, you can select additional OBM Management Packs to install in your OBM environment. Default Management Packs will be selected automatically. Dependencies between them are resolved automatically. You can choose not to install dependent management packs. However, if you do so, the functional scope of the selected management packs might reduce.

                                                            

                                                                
                                                            

                                                            
Management packs provide add-on content on top of OBM. They deliver automatic and end-to-end monitoring solutions of infrastructure and applications. Management packs enable users to monitor, detect, troubleshoot, and remediate issues in the IT domain. They increase the productivity of users by optimizing and automating various tasks, and reduce the mean time to resolve (MTTR) incidents.

                                                            
Management packs discover application domains and proactively monitor the domains for availability and performance issues. They include, for example, management templates, aspects, policy templates, performances graphs, troubleshooting tools, auto remediation flows, and topology-based event correlation (TBEC) rules.

                                                            

                                                                
To install management packs after the first configuration, start the configuration wizard again and select the management packs you want to install. The list of management packs already installed are automatically selected and cannot be de-selected.  With a distributed deployment, start the configuration wizard first on the data processing servers and subsequently on all gateway servers. Note though that the Management Packs page does not appear during the gateway server configuration.

                                                                

                                                                    
Tip We recommend to disable OBM before starting the configuration wizard, and to enable it after the configuration:

                                                                    

                                                                        
    
                                                                            
  • 
                                                                                
    Windows Server 2008:
    
                                                                                
    Select Start > Programs > Operations Bridge Manager > Administration > Disable Operations Bridge Manager.
    
                                                                            
    • 
                                                                            
  • 
                                                                                
    Windows Server 2012:
    
                                                                                
    In Windows Search, start typing Disable Operations Bridge Manager, and then click Disable Operations Bridge Manager in the search results.
    
                                                                            
    • 
                                                                        

                                                                    

                                                                    

                                                                        
Run the following command:

                                                                        
/opt/HP/BSM/scripts/run_hpbsm stopall
                                                                        

                                                                    

                                                                    
 Alternatively, use the opr-mp-installer command-line utility to install management packs without having to disable OBM. For more information, see opr-mp-installer.

                                                                

                                                            

                                                            

                                                                
To install management packs after the upgrade, start the configuration wizard again or use the opr-mp-installer command-line utility. For more information, see opr-mp-installer.

                                                            

                                                            
The pre-selected management packs are selected on the source version of OBM. In GUI upgradeupdate, you can choose additional management packs from the list. Once installed, management packs cannot be removed, even though their entries appear in the Management Packs page.

                                                            

                                                                
To verify the installed management packs on the production server, run the following command:

                                                                
<OBM_HOME>/bin/opr-mp-installer -le
                                                                

                                                            

                                                            

                                                                
To verify the installed management packs on the production server, run the following command:

                                                                
/opt/HP/BSM/bin/opr-mp-installer -le
                                                                

                                                            

                                                            

                                                                
Note To update a management pack to a later version than the one included with OBM, download its installation package from the ITOM Marketplace and install the management pack manually. You can also install additional management packs that are not bundled with OBM. However, such additions are not reflected in the OBM configuration wizard.

                                                            

                                                            
For more information about the management packs, see the management pack documentation.

                                                            
Select the management packs that you want to install in your OBM environment and then click Next.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Deploy management packs

                                                        

                                                            

                                                                

                                                                    
Caution This section is applicable for data processing server.

                                                                

                                                            

                                                            
In the Management Packs page, you can select additional OBM Management Packs to install in your OBM environment. Default Management Packs will be selected automatically. Dependencies between them are resolved automatically. You can choose not to install dependent management packs. However, if you do so, the functional scope of the selected management packs might reduce.

                                                            

                                                                
                                                            

                                                            
Management packs provide add-on content on top of OBM. They deliver automatic and end-to-end monitoring solutions of infrastructure and applications. Management packs enable users to monitor, detect, troubleshoot, and remediate issues in the IT domain. They increase the productivity of users by optimizing and automating various tasks, and reduce the mean time to resolve (MTTR) incidents.

                                                            
Management packs discover application domains and proactively monitor the domains for availability and performance issues. They include, for example, management templates, aspects, policy templates, performances graphs, troubleshooting tools, auto remediation flows, and topology-based event correlation (TBEC) rules.

                                                            

                                                                
To install management packs after the first configuration, start the configuration wizard again and select the management packs you want to install. The list of management packs already installed are automatically selected and cannot be de-selected.  With a distributed deployment, start the configuration wizard first on the data processing servers and subsequently on all gateway servers. Note though that the Management Packs page does not appear during the gateway server configuration.

                                                                

                                                                    
Tip We recommend to disable OBM before starting the configuration wizard, and to enable it after the configuration:

                                                                    

                                                                        
    
                                                                            
  • 
                                                                                
    Windows Server 2008:
    
                                                                                
    Select Start > Programs > Operations Bridge Manager > Administration > Disable Operations Bridge Manager.
    
                                                                            
    • 
                                                                            
  • 
                                                                                
    Windows Server 2012:
    
                                                                                
    In Windows Search, start typing Disable Operations Bridge Manager, and then click Disable Operations Bridge Manager in the search results.
    
                                                                            
    • 
                                                                        

                                                                    

                                                                    

                                                                        
Run the following command:

                                                                        
/opt/HP/BSM/scripts/run_hpbsm stopall
                                                                        

                                                                    

                                                                    
 Alternatively, use the opr-mp-installer command-line utility to install management packs without having to disable OBM. For more information, see opr-mp-installer.

                                                                

                                                            

                                                            

                                                                
To install management packs after the upgrade, start the configuration wizard again or use the opr-mp-installer command-line utility. For more information, see opr-mp-installer.

                                                            

                                                            
The pre-selected management packs are selected on the source version of OBM. In GUI upgradeupdate, you can choose additional management packs from the list. Once installed, management packs cannot be removed, even though their entries appear in the Management Packs page.

                                                            

                                                                
To verify the installed management packs on the production server, run the following command:

                                                                
<OBM_HOME>/bin/opr-mp-installer -le
                                                                

                                                            

                                                            

                                                                
To verify the installed management packs on the production server, run the following command:

                                                                
/opt/HP/BSM/bin/opr-mp-installer -le
                                                                

                                                            

                                                            

                                                                
Note To update a management pack to a later version than the one included with OBM, download its installation package from the ITOM Marketplace and install the management pack manually. You can also install additional management packs that are not bundled with OBM. However, such additions are not reflected in the OBM configuration wizard.

                                                            

                                                            
For more information about the management packs, see the management pack documentation.

                                                            
Select the management packs that you want to install in your OBM environment and then click Next.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Ready to Configure

                                                    

                                                        
This section is applicable on data processing server and gateway server.

                                                    

                                                    

                                                        
The Ready to Configure page displays the current settings. Check whether your selections are correct. To change a setting, click Edit.

                                                        

                                                            Configuration wizard: Ready to Configure (Confirmaton) page
                                                        

                                                        
When you are ready, click Next to initiate the configuration actions.

                                                    

                                                    

                                                        

                                                            
Check if the L-Core certificates are present, run the following command:

                                                            
ovcert -list
                                                            

                                                            
If the certificates are not present, or the local agent certificate is missing, restore the certificates. 

                                                            
Stop agent process:

                                                            
ovc -kill
                                                            

                                                            
To restore agent certificates from backup:

                                                            

                                                                
Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old

                                                                
Copy the backed up files back to %OvDataDir%\datafiles\sec\ks

                                                            

                                                            

                                                                
mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                

                                                                
cd/
                                                                

                                                                
tar xzvf /backup/agent-certs.tar.gz
                                                                

                                                            

                                                            
To restore server certificates from backup:

                                                            

                                                                
Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old

                                                                
Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks

                                                            

                                                            

                                                                
mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                

                                                                
cd/
                                                                

                                                                
tar xzvf /backup/cs-certs.tar.gz
                                                                

                                                            

                                                            
Start the agent process again:

                                                            
ovc -start
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Review the summary and conclude the upgradeupdate

                                                        

                                                            
This section is applicable for data processing server and  gateway server.

                                                        

                                                        

                                                            
In the Configuration Summary page, read the summary of the OBM upgradeupdate process.

                                                            

                                                                Configuration wizard: Configuration Summary page
                                                            

                                                            
Click Finish to close the configuration wizard.

                                                        

                                                        

                                                            

                                                                
Check if the L-Core certificates are present. Run the following command:

                                                                
ovcert -list
                                                                

                                                                
If the certificates are not present, or the local agent certificate is missing, restore the certificates. 

                                                                
Stop agent process:

                                                                
ovc -kill
                                                                

                                                                
To restore agent certificates from backup:

                                                                

                                                                    
Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old

                                                                    
Copy the backed up files back to %OvDataDir%\datafiles\sec\ks

                                                                

                                                                

                                                                    
mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                    

                                                                    
cd/
                                                                    

                                                                    
tar xzvf /backup/agent-certs.tar.gz
                                                                    

                                                                

                                                                
To restore server certificates from backup:

                                                                

                                                                    
Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old

                                                                    
Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks

                                                                

                                                                

                                                                    
mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                    

                                                                    
cd/
                                                                    

                                                                    
tar xzvf /backup/cs-certs.tar.gz
                                                                    

                                                                

                                                                
Start the agent process again:

                                                                
ovc -start
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Review the summary and conclude the upgradeupdate

                                                        

                                                            
This section is applicable for data processing server and  gateway server.

                                                        

                                                        

                                                            
In the Configuration Summary page, read the summary of the OBM upgradeupdate process.

                                                            

                                                                Configuration wizard: Configuration Summary page
                                                            

                                                            
Click Finish to close the configuration wizard.

                                                        

                                                        

                                                            

                                                                
Check if the L-Core certificates are present. Run the following command:

                                                                
ovcert -list
                                                                

                                                                
If the certificates are not present, or the local agent certificate is missing, restore the certificates. 

                                                                
Stop agent process:

                                                                
ovc -kill
                                                                

                                                                
To restore agent certificates from backup:

                                                                

                                                                    
Rename %OvDataDir%\datafiles\sec\ks to %OvDataDir%\datafiles\sec\ks.old

                                                                    
Copy the backed up files back to %OvDataDir%\datafiles\sec\ks

                                                                

                                                                

                                                                    
mv /var/opt/OV/datafiles/sec/ks /var/opt/OV/datafiles/sec/ks.old
                                                                    

                                                                    
cd/
                                                                    

                                                                    
tar xzvf /backup/agent-certs.tar.gz
                                                                    

                                                                

                                                                
To restore server certificates from backup:

                                                                

                                                                    
Rename %OvDataDir%\shared\server\datafiles\sec\ks to %OvDataDir%\shared\server\datafiles\sec\ks.old

                                                                    
Copy the backed up files back to %OvDataDir%\shared\server\datafiles\sec\ks

                                                                

                                                                

                                                                    
mv /var/opt/OV/shared/server/datafiles/sec/cs /var/opt/OV/shared/server/datafiles/sec/cs.old
                                                                    

                                                                    
cd/
                                                                    

                                                                    
tar xzvf /backup/cs-certs.tar.gz
                                                                    

                                                                

                                                                
Start the agent process again:

                                                                
ovc -start
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Configure OBM silently

                                                            

                                                                

                                                                    

                                                                        

                                                                            
Caution This section is applicable on   each OBM gateway server.

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        
Note In a single-server HA, to configure the backup server in the database connect page connect to existing database which was created in primary server.

                                                                    

                                                                

                                                                

                                                                    
Disable OBM on the primary data processing server.

                                                                

                                                                

                                                                    

                                                                        
To switch to root user, run the configuration wizard on the primary DPS.

                                                                    

                                                                

                                                                
    
                                                                    
    
                                                                        
  1. 
                                                                            
    Create a non-root user account on all OBM servers, for example, by using the operating system's useradd or adduser command.
    
                                                                            
    Configure the maximum number of processes for this user account by adding the following line to the existing *nproc.conf file in the /etc/security/limits.d directory.
    
                                                                            
    <UserName>       soft    nproc     unlimited
                                                                            
    
                                                                            
    Replace <UserName> with the non-root user account.
    
                                                                        
    2. 
                                                                    
    
                                                                    
  2. 
                                                                        
    Optional. For additional security, you can generate encrypted passwords for the configuration files. To do this, perform the following:
    
                                                                        
      
                                                                            
    1. 
                                                                                
      Open a Command Prompt windowcommand shell.
      
                                                                            
      2. 
                                                                            
    2. 
                                                                                
      Change the current directory as follows:
      
                                                                                
      
                                                                                    
       cd <OBM_HOME>\bin
      
                                                                                
      
                                                                                
      
                                                                                    
       cd /opt/HP/BSM/bin
      
                                                                                
      
                                                                            
      3. 
                                                                            
    3. 
                                                                                
      Invoke the password encryption utility:
      
                                                                                
      
                                                                                    
       encrypt-password.bat
      
                                                                                
      
                                                                                
      
                                                                                    
       ./encrypt-password.sh
      
                                                                                
      
                                                                            
      4. 
                                                                            
    4. 
                                                                                
      Enter your password. The encryption utility returns a string.
      
                                                                            
      5. 
                                                                            
    5. 
                                                                                
      In the configuration files, set the property IsEncrypted="true" and enter the encrypted password as the line key="password" value="<EncryptedPassword>".
      
                                                                                
      
                                                                                    
      Note Encrypted passwords are valid on the system where the encryption utility was run.
      
                                                                                    
      To remove password encryption at a later time, enter the passwords in the configuration files as usual and set the value of IsEncrypted="false".
      
                                                                                
      
                                                                            
      6. 
                                                                        
    
                                                                    
    3. 
                                                                    
  3. 
                                                                        
    Create the configuration files for the silent configuration in one of the following ways: 
    
                                                                        
      
                                                                            
    • 
                                                                                
      
                                                Start the Closedconfiguration wizard to generate the configuration files:
                                                                                    
      
                                                                                        
        
                                                                                            
      1. 
                                                                                                
        Start the OBM configuration wizard:
        
                                                                                                
          
                                                                                                    
        1. 
                                                                                                        
           If you are not starting the wizard for the first time, disable OBM. Proceed as follows:
          
                                                                                                        
          
                                                                                                            
            
                                                                                                                
          • 
                                                                                                                    
            Windows Server 2008:
            
                                                                                                                    
            Select Start > Programs > Operations Bridge Manager > Administration > Disable Operations Bridge Manager.
            
                                                                                                                
            • 
                                                                                                                
          • 
                                                                                                                    
            Windows Server 2012:
            
                                                                                                                    
            In Windows Search, start typing Disable Operations Bridge Manager, and then click Disable Operations Bridge Manager in the search results.
            
                                                                                                                
            • 
                                                                                                            
          
                                                                                                        
          
                                                                                                        
          
                                                                                                            
          If this is not the first time you are starting the wizard, disable OBM. Open a command shell and run the following command:
          
                                                                                                            
          /opt/HP/BSM/scripts/run_hpbsm stop
                                                                                                            
          
                                                                                                        
          
                                                                                                    
          2. 
                                                                                                    
        2. 
                                                                                                        
          To invoke the configuration wizard from the operating system desktop, proceed as follows:
          
                                                                                                        
          In Windows Search, start typing Configure Operations Bridge Manager. Then click Configure Operations Bridge Manager in the search results.
          
                                                                                                    
          3. 
                                                                                                    
        3. 
                                                                                                        
          To invoke the configuration wizard from the command line, open a Command Prompt window and run the following command:
          
                                                                                                        
          <OMi_HOME>\bin\config-server-wizard.bat
                                                                                                        
          
                                                                                                    
          4. 
                                                                                                    
        4. 
                                                                                                        
          To invoke the configuration wizard, open a command shell and run the following command:
          
                                                                                                        
          /opt/HP/BSM/bin/config-server-wizard.sh.
          
                                                                                                    
          5. 
                                                                                                
        
                                                                                            
        2. 
                                                                                            
      2. 
                                                                                                
        In the Configuration Options page, click Create configuration file for silent configuration. Enter the pathname of the configuration file or click Browse to select a path and the filename with the .xml file name extension. Then click Next.
        
                                                                                                
        
                                                                                                    Configuration wizard: Configuration Options page
                                                                                                
        
                                                                                            
        3. 
                                                                                            
      3. 
                                                                                                
        Follow instructions in other configuration wizard pages.
        
                                                                                            
        4. 
                                                                                            
      4. 
                                                                                                
        After the configuration wizard completes, OBM generates the configuration file at the location you specified. The file contains the values that you selected in the wizard pages.
        
                                                                                            
        5. 
                                                                                            
      5. 
                                                                                                
        Change the user account of the running OBM processes to a non-root user account. In the generated configuration file, set the value for nonRootEnabled to true and replace the nonRootUserName default value root with the non-root user account:
        
                                                                                                
        <property key="nonRootEnabled" value="false"/>
                                                                                                    
        <property key="nonRootUserName" value="root"/>
                                                                                                
        
                                                                                                
        For example, if the non-root user account is called "user", set the values as follows:
        
                                                                                                
        <property key="nonRootEnabled" value="true"/>
                                                                                                    
        <property key="nonRootUserName" value="user"/>
                                                                                                
        
                                                                                            
        6. 
                                                                                        
      
                                                                                    
      
                                                                                
      
                                                                            
      • 
                                                                            
    • 
                                                                                
      Copy the following template files to a location of your choice manually, and then add the missing values into the copycopycopies:
      
                                                                                
      
                                                                                    
      
                                                                                        
      <OBM_HOME>/opr/examples/silent-configuration/SilentConfiguration_Blank.xml
                                                                                        
      
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      
                                                                                        
      <OBM_HOME>/opr/examples/silent-configuration/SilentConfiguration_Blank.xml
                                                                                        
      
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      
                                                                                        
      <OBM_HOME>/opr/examples/silent-configuration/Oracle_DPS.xml
                                                                                        
      
                                                                                        
      <OBM_HOME>/opr/examples/silent-configuration/Oracle_GW.xml
                                                                                        
      
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      
                                                                                        
      <OBM_HOME>/opr/examples/silent-configuration/SQL_Server_DPS.xml
                                                                                        
      
                                                                                        
      <OBM_HOME>/opr/examples/silent-configuration/SQL_Server_GW.xml
                                                                                        
      
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      
                                                                                        
      <OBM_HOME>/opr/examples/silent-configuration/Postgres_SingleServer.xml
                                                                                        
      
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      
                                                                                        
      <OBM_HOME>/opr/examples/silent-configuration/PostgresEmbedded_SingleServer.xml
                                                                                        
      
                                                                                    
      
                                                                                
      
                                                                                
      The template files containscontainscontain comments that help you to add appropriate values.
      
                                                                                
      
                                                                                    
      Note You can set the sslEnabled attribute to true or false. If you set it to true, you must specify the additional attributes dbCertificate and dbTruststorePassword. For more information about these attributes, refer OracleMicrosoft SQL ServerPostgreSQL database documentation.
      
                                                                                
      
                                                                                
      
                                                                                    
      
                                                                                        
      Caution Leave the  names of the PostgreSQL database schemas (the dbName keys) set to their default values.
      
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      ClosedOptional. Manually configure Windows authentication for Microsoft SQL Server database schemas
                                                                                        
      
                                                                                            
      For Microsoft SQL Server databases, you can configure OBM to take the database credentials directly from the Windows authentication credentials. To enable this feature when manually creating a configuration file, leave the UserName and Password keys for each relevant database blank.
      
                                                                                            
      The following example shows the Event database section of the configuration file formatted to use Windows authentication:
      <!-- Specify the details of the event database. -->
         <database name="opr">
         <property key="dbType" value="SQL Server"/>
         <property key="operation" value="connect"/>
         <property key="hostName" value=""/>
         <property key="port" value=""/>
         <property key="userName" value=""/>
         <property isEncrypted="true" key="password" value=""/>
         <property key="dbName" value=""/>
      </database>
      
                                                                                        
      
                                                                                    
      
                                                                                
      
                                                                            
      • 
                                                                        
    
                                                                    
    4. 
                                                                    
  4. 
                                                                        
    Configure OBM in the silent mode:
    
                                                                        
    
                                                                            
    <OBM_HOME>\bin\silentConfigureBSM.bat <Full path of ConfigurationFilename>
    
                                                                        
    
                                                                        
    
                                                                            
    /opt/HP/BSM/bin/silentConfigureBSM.sh <Full path of ConfigurationFilename>
    
                                                                        
    
                                                                        
    The command first runs the post-installation task and then the configuration tasks. Before starting the configuration tasks, the command validates the configuration file to ensure valid XML syntax. Validation errors are logged in the following log file:
    
                                                                        
    
                                                                            
    <OBM_HOME>\log\configserver\configserver_all.log
                                                                            
    
                                                                        
    
                                                                        
    
                                                                            
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                            
    
                                                                        
    
                                                                        
    After the validation succeeds, the configuration starts.
    
                                                                        
    
                                                                            
    Tip You can also run the post-installation and configuration processes separately by specifying the corresponding parameter:
    
                                                                            
      
                                                                                
    • 
                                                                                    
      Post-installation only. To invoke the OBM post-installation phase, run the following command:
      
                                                                                    
      
                                                                                        
      <OBM_HOME>\bin\silentConfigureBSM.bat <Full path of ConfigurationFilename> postinstall
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/bin/silentConfigureBSM.sh <Full path of ConfigurationFilename> postinstall 
      
                                                                                    
      
                                                                                
      • 
                                                                                
    • 
                                                                                    
      Configuration only. To  reconfigure OBM after the initial configuration, run the following command:
      
                                                                                    
      
                                                                                        
      <OBM_HOME>\bin\silentConfigureBSM.bat <Full path of ConfigurationFilename> configserver
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/bin/silentConfigureBSM.sh <Full path of ConfigurationFilename> configserver
                                                                                        
      
                                                                                    
      
                                                                                
      • 
                                                                            
    
                                                                        
    
                                                                    
    5. 
                                                                

                                                                
Repeat each step above for the remaining servers.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Change the Windows service user account

                                                        

                                                            
The main OBM services (HP Operations Manager i, HP Operations Manager i web console) are installed when you start the configuration wizard. By default, they run by using the Local System user account. However, you may have to assign a different user account to the HP Operations Manager i service (for example, if you use NTLM authentication).

                                                            
The user account of this service must have the following privileges:

                                                            
    
                                                                
  • 
                                                                    
    Sufficient database permissions (as defined by the database administrator)
    
                                                                
    • 
                                                                
  • 
                                                                    
    Sufficient network privileges
    
                                                                
    • 
                                                                
  • 
                                                                    
    Administrative privileges on the local system
    
                                                                
    • 
                                                            

                                                            
Additionally, the HP OpenView Ctrl Service must be running with an account that has access to SQL server, and the agent account requires access to the OBM directories (for example C:\HPBSM on Windows).

                                                            

                                                                
Note HP Operations Manager i is initially installed as a service that can be started manually. When you enable OBM for the first time, it becomes a service that is started automatically.

                                                            

                                                            
To change the OBM service user account:

                                                            
    
                                                                
  1. 
                                                                    
    Disable OBM:
    
                                                                    
      
                                                                        
    • 
                                                                            
      Windows Server 2008:
      
                                                                            
      Select Start > Programs > Operations Bridge Manager > Administration > Disable Operations Bridge Manager.
      
                                                                        
      • 
                                                                        
    • 
                                                                            
      Windows Server 2012:
      
                                                                            
      In Windows Search, start typing Disable Operations Bridge Manager, and then click Disable Operations Bridge Manager in the search results.
      
                                                                        
      • 
                                                                    
    
                                                                
    2. 
                                                                
  2. 
                                                                    
    In the Windows Services window, double-click HP Operations Manager i. The HP Operations Manager i Properties (Local Computer) dialog box opens.
    
                                                                
    3. 
                                                                
  3. 
                                                                    
    Click the Log On tab.
    
                                                                
    4. 
                                                                
  4. 
                                                                    
    Select This account and browse to choose another user account from the list of the available user accounts on the system.
    
                                                                
    5. 
                                                                
  5. 
                                                                    
    Enter the object name as  domain\username. Click  Check Names (should be an administrator).
    
                                                                
    6. 
                                                                
  6. 
                                                                    
    Enter the selected user account’s Windows password and confirm this password.
    
                                                                
    7. 
                                                                
  7. 
                                                                    
    Click Apply to save your settings and then OK to close the dialog box.
    
                                                                    
    
                                                                        
    Note The below steps are applicable only for DPS. 
    
                                                                    
    
                                                                
    8. 
                                                                
  8. 
                                                                    
    In the Windows Services window, double-click UCMDB_Server. The UCMDB_Server Properties (Local Computer) dialog box opens.
    
                                                                
    9. 
                                                                
  9. 
                                                                    
    Click the Log On tab.
    
                                                                
    10. 
                                                                
  10. 
                                                                    
    Select This account and browse to choose another user account from the list of the available user accounts on the system.
    
                                                                
    11. 
                                                                
  11. Enter the object name as  domain\username. Click  Check Names (should be an administrator).
    12. 
                                                                
  12. 
                                                                    
    Enter the selected user account’s Windows password and confirm this password.
    
                                                                
    13. 
                                                                
  13. 
                                                                    
    Click Apply to save your settings and then OK to close the dialog box.
    
                                                                
    14. 
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Optional. Update configuration variables

                                                    

                                                        

                                                            
You may have modified the configuration variables on the OBM production servers for various reasons, such as to support communications to agents via proxies or non-standard ports.  These are typically modified using the ovconfchg CLI.  You may want to apply the same changes to the OBM staging servers.  You can compare the settings between production and staging OBM servers by running the ovconfget CLI on each server.

                                                            
Note: If you have deployed nodeinfo policies to the OBM production servers, then you need to assign and deploy the policies to your OBM staging servers after they are started.  Use ovconfchg to modify the policies and override the same variable that is set using a nodeinfo policy.

                                                            
To compare the changes from the production server to staging server, run the following command:
/opt/OV/bin/ovconfget

                                                            
To apply the changes from the production server to staging server, run the following command:
/opt/OV/bin/ovconfchg

                                                            
Run the above command once on production server and once on staging server. If there are multiple DPS or gateway servers, run the command on each of them.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Enable OBM

                                                    

                                                        

                                                            

                                                                

                                                                    

                                                                        

                                                                            
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                        

                                                                        

                                                                            
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                            
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                            
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                        

                                                                        

                                                                            
To start the OBM processes and enable OBM, do the following:

                                                                            
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                            
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                            

                                                                                
    
                                                                                    
  • 
                                                                                        
    Run the following command:
    
                                                                                        
    /etc/init.d/hpbsmd start
    
                                                                                        
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                        
    start, stop, and restart
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                        
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                        

                                                                                        
You can also monitor the below log files:

                                                                                        
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                        

                                                                                        
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                        

                                                                                    

                                                                                    
Run the following command:

                                                                                    
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                    

                                                                                    
The script supports the following command-line options:

                                                                                    
start, stop, stopall, and restart

                                                                                    

                                                                                        
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                    

                                                                                

                                                                            

                                                                            
You can view the status of the OBM services from the below log file:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                            
Run the following command to check the process status:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            
To enable OBM, do the following:

                                                                            
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                            

                                                                                
Note You can also monitor the below log files:

                                                                                
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                

                                                                                
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                

                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                            
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                        

                                                                        

                                                                            
To start the OBM processes and enable OBM, do the following:

                                                                            

                                                                                
    
                                                                                    
  • 
                                                                                        
    Run the following command:
    
                                                                                        
    /etc/init.d/hpbsmd start 
    
                                                                                        
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                        
    start, stop, and restart
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                        
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                        

                                                                                        
You can also monitor the below log files:

                                                                                        
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                        

                                                                                        
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                        

                                                                                    

                                                                                    
Run the following command:

                                                                                    
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                    

                                                                                    
The script supports the following command-line options:

                                                                                    
start, stop, stopall, and restart

                                                                                    

                                                                                        
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                    

                                                                                

                                                                            

                                                                            
You can view the status of the OBM services from the below log file:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                            
Run the following command to check the process status:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            
To enable OBM, do the following:

                                                                            
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                            

                                                                                
Note You can also monitor the below log files:

                                                                                
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                

                                                                                
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                

                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                            
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                        

                                                                        

                                                                            

                                                                                
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                
    
                                                                                    
  • 
                                                                                        
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                        
    Restart all OBM servers and data collectors.
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    If you modified databases on a running OBM deployment:
    
                                                                                        
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                        
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                        
      
                                                                                            
    1. 
                                                                                                
      Navigate to the following directory: 
      
                                                                                                
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                
      
                                                                                                
      It contains two subdirectories: /loaded and /toload.
      
                                                                                            
      2. 
                                                                                            
    2. 
                                                                                                
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                            
      3. 
                                                                                            
    3. 
                                                                                                
      Restart OBM servicesprocesses.
      
                                                                                            
      4. 
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                        

                                                                        

                                                                            
 After you enable the active server, the upgrade process on active server is complete. 

                                                                            
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                            
After you upgrade active server and gateway servers, start the upgrade process on backup server. Go to Initiate the upgrade process section and follow the steps. Enable OBM on backup server. The upgrade process on backup server is complete.

                                                                        

                                                                        

                                                                            
To start the OBM processes and enable OBM, do the following:

                                                                            
In an HA environment, run the start command on the active server. Wait until the process is complete. After the active server is fully up, enable the gateway servers and backup server. 

                                                                            

                                                                                
    
                                                                                    
  • 
                                                                                        
    Run the following command:
    
                                                                                        
    /etc/init.d/hpbsmd start 
    
                                                                                        
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                        
    start, stop, and restart
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                        
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                        

                                                                                        
You can also monitor the below log files:

                                                                                        
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                        

                                                                                        
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                        

                                                                                    

                                                                                    
Run the following command:

                                                                                    
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                    

                                                                                    
The script supports the following command-line options:

                                                                                    
start, stop, stopall, and restart

                                                                                    

                                                                                        
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                    

                                                                                

                                                                            

                                                                            
You can view the status of the OBM services from the below log file:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                            
Run the following command to check the process status:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            

                                                                                
Applicable only for High Availability environment.
                                                                                

                                                                                
In a high availability environment, first enable the active server and wait until this process is completed before starting the gateway servers and the backup server. Make sure that all HAC processes are running. 

                                                                                
Run the following command to check the status of the HAC processess:

                                                                                
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                

                                                                            

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            
To enable OBM, do the following:

                                                                            
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                            

                                                                                
Note You can also monitor the below log files:

                                                                                
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                

                                                                                
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                

                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                            
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            

                                                                

                                                                    
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                

                                                                

                                                                    

                                                                        

                                                                            
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                            
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                            
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                            

                                                                        

                                                                    

                                                                    

                                                                        
Before starting the OBM servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already being applied on the production OBM server.  Run this command on the staging OBM primary data processing server:

                                                                        
<OBM_HOME>\opr\support\opr-support-utils.bat -set_setting -context opr -set opr.staging.mode.enabled true
                                                                        

                                                                    

                                                                

                                                                
To start the OBM processes and enable OBM, do the following:

                                                                

                                                                    
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                

                                                                

                                                                    
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                

                                                                

                                                                    

                                                                        
    
                                                                            
  • 
                                                                                
    Run the following command:
    
                                                                                
    /etc/init.d/hpbsmd start 
    
                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                
    start, stop, and restart
    
                                                                            
    • 
                                                                            
  • 
                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                
    The script supports the following command-line options:
    
                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                
    
                                                                            
    • 
                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                

                                                                                
You can also monitor the below log files:

                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                

                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                

                                                                            

                                                                            
Run the following command:

                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                            

                                                                            
The script supports the following command-line options:

                                                                            
start, stop, stopall, and restart

                                                                            

                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                            

                                                                        

                                                                    

                                                                    
You can view the status of the OBM services from the below log file:

                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                    

                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                    
Run the following command to check the process status:

                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                    

                                                                    

                                                                        
Applicable only for High Availability environment.
                                                                        

                                                                        
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                        
Run the following command to check the status of the HAC processess:

                                                                        
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                        

                                                                    

                                                                    

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

                                                                        

                                                                            
Replace the

                                                                            
-Djava.net.preferIPv4Stack=false
                                                                            

                                                                            
line with the

                                                                            
-Djava.net.preferIPv4Stack=true
                                                                            

                                                                            
line.

                                                                        

                                                                    

                                                                

                                                                

                                                                    
To enable OBM, do the following:

                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                    

                                                                        
Note You can also monitor the below log files:

                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                        

                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                        

                                                                    

                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                

                                                                

                                                                    

                                                                        
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                        
    
                                                                            
  • 
                                                                                
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                
    Restart all OBM servers and data collectors.
    
                                                                            
    • 
                                                                            
  • 
                                                                                
    If you modified databases on a running OBM deployment:
    
                                                                                
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Navigate to the following directory: 
      
                                                                                        
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                        
      
                                                                                        
      It contains two subdirectories: /loaded and /toload.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Restart OBMservicesprocesses.
      
                                                                                    
      4. 
                                                                                
    
                                                                            
    • 
                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        
After the active server is upgraded, enable the active server. Upgrade the backup server and enable the backup server.  If there are any additional gateway servers, repeat the steps to complete the upgrade for gateway servers.

                                                                    

                                                                

                                                                

                                                                    

                                                                        
For a side-by-side upgrade, after you enable primary staging server, repeat the steps to upgrade secondary staging server and enable the secondary staging server. 

                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            

                                                                

                                                                    
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                

                                                                

                                                                    
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s).

                                                                    
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS.

                                                                

                                                                

                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                    

                                                                        
    
                                                                            
  • 
                                                                                
    Run the following command:
    
                                                                                
    /etc/init.d/hpbsmd start 
    
                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                
    start, stop, and restart
    
                                                                            
    • 
                                                                            
  • 
                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command:
    
                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                
    The script supports the following command-line options:
    
                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                
    
                                                                            
    • 
                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                

                                                                                
You can also monitor the below log files:

                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                

                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                

                                                                            

                                                                            
Run the following command:

                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                            

                                                                            
The script supports the following command-line options:

                                                                            
start, stop, stopall, and restart

                                                                            

                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        
Applicable only for High Availability environment.
                                                                        

                                                                        
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                        
Run the following command to check the status of the HAC processess:

                                                                        
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                        

                                                                    

                                                                    

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

                                                                        

                                                                            
Replace the

                                                                            
-Djava.net.preferIPv4Stack=false
                                                                            

                                                                            
line with the

                                                                            
-Djava.net.preferIPv4Stack=true
                                                                            

                                                                            
line.

                                                                        

                                                                    

                                                                

                                                                

                                                                    
To enable OBM, do the following:

                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                    

                                                                        
Note You can also monitor the below log files:

                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                        

                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                        

                                                                    

                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                

                                                                

                                                                    

                                                                        
Note Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                        
    
                                                                            
  • 
                                                                                
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                
    Restart all OBM servers and data collectors.
    
                                                                                
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                            
    • 
                                                                            
  • 
                                                                                
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                
      
                                                                                    
    1. 
                                                                                        
      Navigate to the following directory: 
      
                                                                                        
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                        
      
                                                                                        
      It contains two subdirectories: /loaded and /toload.
      
                                                                                    
      2. 
                                                                                    
    2. 
                                                                                        
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                    
      3. 
                                                                                    
    3. 
                                                                                        
      Restart OBM servicesprocesses.
      
                                                                                    
      4. 
                                                                                
    
                                                                            
    • 
                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            

                                                                

                                                                    

                                                                        
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                    

                                                                    

                                                                        
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                        
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                        
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                    

                                                                    

                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                        
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                        
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                        

                                                                            
    
                                                                                
  • 
                                                                                    
    Run the following command:
    
                                                                                    
    /etc/init.d/hpbsmd start
    
                                                                                    
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                    
    start, stop, and restart
    
                                                                                
    • 
                                                                                
  • 
                                                                                    
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                    
    The script supports the following command-line options:
    
                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                    
    
                                                                                
    • 
                                                                            

                                                                        

                                                                        

                                                                            

                                                                                

                                                                                    
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                    
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                    

                                                                                    
You can also monitor the below log files:

                                                                                    
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                    

                                                                                    
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                    

                                                                                

                                                                                
Run the following command:

                                                                                
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                

                                                                                
The script supports the following command-line options:

                                                                                
start, stop, stopall, and restart

                                                                                

                                                                                    
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                

                                                                            

                                                                        

                                                                        
You can view the status of the OBM services from the below log file:

                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                        

                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                        
Run the following command to check the process status:

                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                        

                                                                        

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

                                                                            

                                                                                
Replace the

                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                

                                                                                
line with the

                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                

                                                                                
line.

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        
To enable OBM, do the following:

                                                                        
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                        

                                                                            
Note You can also monitor the below log files:

                                                                            
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                            

                                                                            
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                            

                                                                        

                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                        
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            

                                                                

                                                                    

                                                                        
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                    

                                                                    

                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                        

                                                                            
    
                                                                                
  • 
                                                                                    
    Run the following command:
    
                                                                                    
    /etc/init.d/hpbsmd start 
    
                                                                                    
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                    
    start, stop, and restart
    
                                                                                
    • 
                                                                                
  • 
                                                                                    
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                    
    The script supports the following command-line options:
    
                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                    
    
                                                                                
    • 
                                                                            

                                                                        

                                                                        

                                                                            

                                                                                

                                                                                    
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                    
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                    

                                                                                    
You can also monitor the below log files:

                                                                                    
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                    

                                                                                    
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                    

                                                                                

                                                                                
Run the following command:

                                                                                
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                

                                                                                
The script supports the following command-line options:

                                                                                
start, stop, stopall, and restart

                                                                                

                                                                                    
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                

                                                                            

                                                                        

                                                                        
You can view the status of the OBM services from the below log file:

                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                        

                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                        
Run the following command to check the process status:

                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                        

                                                                        

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

                                                                            

                                                                                
Replace the

                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                

                                                                                
line with the

                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                

                                                                                
line.

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        
To enable OBM, do the following:

                                                                        
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                        

                                                                            
Note You can also monitor the below log files:

                                                                            
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                            

                                                                            
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                            

                                                                        

                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                        
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                    

                                                                    

                                                                        

                                                                            
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                            
    
                                                                                
  • 
                                                                                    
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                    
    Restart all OBM servers and data collectors.
    
                                                                                
    • 
                                                                                
  • 
                                                                                    
    If you modified databases on a running OBM deployment:
    
                                                                                    
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                    
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                    
      
                                                                                        
    1. 
                                                                                            
      Navigate to the following directory: 
      
                                                                                            
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                            
      
                                                                                            
      It contains two subdirectories: /loaded and /toload.
      
                                                                                        
      2. 
                                                                                        
    2. 
                                                                                            
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                        
      3. 
                                                                                        
    3. 
                                                                                            
      Restart OBM servicesprocesses.
      
                                                                                        
      4. 
                                                                                    
    
                                                                                
    • 
                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            

                                                                
Enable OBM

                                                                

                                                                    

                                                                        

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                                    

                                                                                    

                                                                                        
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                                        
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                        
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                                    

                                                                                    

                                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                                        
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                                        
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                                        

                                                                                            
    
                                                                                                
  • 
                                                                                                    
    Run the following command:
    
                                                                                                    
    /etc/init.d/hpbsmd start
    
                                                                                                    
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                    
    start, stop, and restart
    
                                                                                                
    • 
                                                                                                
  • 
                                                                                                    
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                                    
    The script supports the following command-line options:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                    
    
                                                                                                
    • 
                                                                                            

                                                                                        

                                                                                        

                                                                                            

                                                                                                

                                                                                                    
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                    
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                    

                                                                                                    
You can also monitor the below log files:

                                                                                                    
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                    

                                                                                                    
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                    

                                                                                                

                                                                                                
Run the following command:

                                                                                                
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                                

                                                                                                
The script supports the following command-line options:

                                                                                                
start, stop, stopall, and restart

                                                                                                

                                                                                                    
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                                

                                                                                            

                                                                                        

                                                                                        
You can view the status of the OBM services from the below log file:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                        
Run the following command to check the process status:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        

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

                                                                                            

                                                                                                
Replace the

                                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                                

                                                                                                
line with the

                                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                                

                                                                                                
line.

                                                                                            

                                                                                        

                                                                                    

                                                                                    

                                                                                        
To enable OBM, do the following:

                                                                                        
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                        

                                                                                            
Note You can also monitor the below log files:

                                                                                            
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                            

                                                                                            
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                            

                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                        
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                    

                                                                                    

                                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                                        

                                                                                            
    
                                                                                                
  • 
                                                                                                    
    Run the following command:
    
                                                                                                    
    /etc/init.d/hpbsmd start 
    
                                                                                                    
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                    
    start, stop, and restart
    
                                                                                                
    • 
                                                                                                
  • 
                                                                                                    
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                    
    The script supports the following command-line options:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                    
    
                                                                                                
    • 
                                                                                            

                                                                                        

                                                                                        

                                                                                            

                                                                                                

                                                                                                    
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                    
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                    

                                                                                                    
You can also monitor the below log files:

                                                                                                    
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                    

                                                                                                    
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                    

                                                                                                

                                                                                                
Run the following command:

                                                                                                
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                                

                                                                                                
The script supports the following command-line options:

                                                                                                
start, stop, stopall, and restart

                                                                                                

                                                                                                    
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                                

                                                                                            

                                                                                        

                                                                                        
You can view the status of the OBM services from the below log file:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                        
Run the following command to check the process status:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        

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

                                                                                            

                                                                                                
Replace the

                                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                                

                                                                                                
line with the

                                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                                

                                                                                                
line.

                                                                                            

                                                                                        

                                                                                    

                                                                                    

                                                                                        
To enable OBM, do the following:

                                                                                        
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                        

                                                                                            
Note You can also monitor the below log files:

                                                                                            
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                            

                                                                                            
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                            

                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                        
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                    

                                                                                    

                                                                                        

                                                                                            
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                            
    
                                                                                                
  • 
                                                                                                    
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                                    
    Restart all OBM servers and data collectors.
    
                                                                                                
    • 
                                                                                                
  • 
                                                                                                    
    If you modified databases on a running OBM deployment:
    
                                                                                                    
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                                    
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                                    
      
                                                                                                        
    1. 
                                                                                                            
      Navigate to the following directory: 
      
                                                                                                            
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                            
      
                                                                                                            
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                        
      2. 
                                                                                                        
    2. 
                                                                                                            
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                        
      3. 
                                                                                                        
    3. 
                                                                                                            
      Restart OBM servicesprocesses.
      
                                                                                                        
      4. 
                                                                                                    
    
                                                                                                
    • 
                                                                                            

                                                                                        

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                    

                                                                                    

                                                                                        
 After you enable the active server, the upgrade process on active server is complete. 

                                                                                        
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                        
After you upgrade active server and gateway servers, start the upgrade process on backup server. Go to Initiate the upgrade process section and follow the steps. Enable OBM on backup server. The upgrade process on backup server is complete.

                                                                                    

                                                                                    

                                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                                        
In an HA environment, run the start command on the active server. Wait until the process is complete. After the active server is fully up, enable the gateway servers and backup server. 

                                                                                        

                                                                                            
    
                                                                                                
  • 
                                                                                                    
    Run the following command:
    
                                                                                                    
    /etc/init.d/hpbsmd start 
    
                                                                                                    
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                    
    start, stop, and restart
    
                                                                                                
    • 
                                                                                                
  • 
                                                                                                    
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                    
    The script supports the following command-line options:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                    
    
                                                                                                
    • 
                                                                                            

                                                                                        

                                                                                        

                                                                                            

                                                                                                

                                                                                                    
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                    
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                    

                                                                                                    
You can also monitor the below log files:

                                                                                                    
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                    

                                                                                                    
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                    

                                                                                                

                                                                                                
Run the following command:

                                                                                                
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                                

                                                                                                
The script supports the following command-line options:

                                                                                                
start, stop, stopall, and restart

                                                                                                

                                                                                                    
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                                

                                                                                            

                                                                                        

                                                                                        
You can view the status of the OBM services from the below log file:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                        
Run the following command to check the process status:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        

                                                                                            
Applicable only for High Availability environment.
                                                                                            

                                                                                            
In a high availability environment, first enable the active server and wait until this process is completed before starting the gateway servers and the backup server. Make sure that all HAC processes are running. 

                                                                                            
Run the following command to check the status of the HAC processess:

                                                                                            
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                            

                                                                                        

                                                                                        

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

                                                                                            

                                                                                                
Replace the

                                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                                

                                                                                                
line with the

                                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                                

                                                                                                
line.

                                                                                            

                                                                                        

                                                                                    

                                                                                    

                                                                                        
To enable OBM, do the following:

                                                                                        
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                        

                                                                                            
Note You can also monitor the below log files:

                                                                                            
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                            

                                                                                            
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                            

                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                        
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                                        
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                                        
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
Before starting the OBM servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already being applied on the production OBM server.  Run this command on the staging OBM primary data processing server:

                                                                                    
<OBM_HOME>\opr\support\opr-support-utils.bat -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                    

                                                                                

                                                                            

                                                                            
To start the OBM processes and enable OBM, do the following:

                                                                            

                                                                                
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                            

                                                                            

                                                                                
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                            

                                                                            

                                                                                

                                                                                    
    
                                                                                        
  • 
                                                                                            
    Run the following command:
    
                                                                                            
    /etc/init.d/hpbsmd start 
    
                                                                                            
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                            
    start, stop, and restart
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                            
    The script supports the following command-line options:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        

                                                                                            
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                            
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                            

                                                                                            
You can also monitor the below log files:

                                                                                            
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                            

                                                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                            

                                                                                        

                                                                                        
Run the following command:

                                                                                        
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                        

                                                                                        
The script supports the following command-line options:

                                                                                        
start, stop, stopall, and restart

                                                                                        

                                                                                            
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                        

                                                                                    

                                                                                

                                                                                
You can view the status of the OBM services from the below log file:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                
Run the following command to check the process status:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                

                                                                                    
Applicable only for High Availability environment.
                                                                                    

                                                                                    
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                                    
Run the following command to check the status of the HAC processess:

                                                                                    
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                    

                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
To enable OBM, do the following:

                                                                                
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                

                                                                                    
Note You can also monitor the below log files:

                                                                                    
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                    

                                                                                    
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                    

                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                            

                                                                            

                                                                                

                                                                                    
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                    
    
                                                                                        
  • 
                                                                                            
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                            
    Restart all OBM servers and data collectors.
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    If you modified databases on a running OBM deployment:
    
                                                                                            
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                            
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      Navigate to the following directory: 
      
                                                                                                    
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                    
      
                                                                                                    
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                
      3. 
                                                                                                
    3. 
                                                                                                    
      Restart OBMservicesprocesses.
      
                                                                                                
      4. 
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    
After the active server is upgraded, enable the active server. Upgrade the backup server and enable the backup server.  If there are any additional gateway servers, repeat the steps to complete the upgrade for gateway servers.

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    
For a side-by-side upgrade, after you enable primary staging server, repeat the steps to upgrade secondary staging server and enable the secondary staging server. 

                                                                                

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                            

                                                                            

                                                                                
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s).

                                                                                
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS.

                                                                            

                                                                            

                                                                                
To start the OBM processes and enable OBM, do the following:

                                                                                

                                                                                    
    
                                                                                        
  • 
                                                                                            
    Run the following command:
    
                                                                                            
    /etc/init.d/hpbsmd start 
    
                                                                                            
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                            
    start, stop, and restart
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    Log off from the OBM host system, log on as a new user, and then run the following command:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                            
    The script supports the following command-line options:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        

                                                                                            
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                            
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                            

                                                                                            
You can also monitor the below log files:

                                                                                            
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                            

                                                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                            

                                                                                        

                                                                                        
Run the following command:

                                                                                        
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                        

                                                                                        
The script supports the following command-line options:

                                                                                        
start, stop, stopall, and restart

                                                                                        

                                                                                            
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
Applicable only for High Availability environment.
                                                                                    

                                                                                    
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                                    
Run the following command to check the status of the HAC processess:

                                                                                    
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                    

                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
To enable OBM, do the following:

                                                                                
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                

                                                                                    
Note You can also monitor the below log files:

                                                                                    
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                    

                                                                                    
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                    

                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                            

                                                                            

                                                                                

                                                                                    
Note Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                    
    
                                                                                        
  • 
                                                                                            
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                            
    Restart all OBM servers and data collectors.
    
                                                                                            
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      Navigate to the following directory: 
      
                                                                                                    
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                    
      
                                                                                                    
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                
      3. 
                                                                                                
    3. 
                                                                                                    
      Restart OBM servicesprocesses.
      
                                                                                                
      4. 
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                                

                                                                                

                                                                                    
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                                    
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                    
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                                    
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start 
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                                

                                                                                    

                                                                                        
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                        
    
                                                                                            
  • 
                                                                                                
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                                
    Restart all OBM servers and data collectors.
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    If you modified databases on a running OBM deployment:
    
                                                                                                
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                                
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                                
      
                                                                                                    
    1. 
                                                                                                        
      Navigate to the following directory: 
      
                                                                                                        
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                        
      
                                                                                                        
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                    
      2. 
                                                                                                    
    2. 
                                                                                                        
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                    
      3. 
                                                                                                    
    3. 
                                                                                                        
      Restart OBM servicesprocesses.
      
                                                                                                    
      4. 
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            

                                                                
Enable OBM

                                                                

                                                                    

                                                                        

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                                    

                                                                                    

                                                                                        
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                                        
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                        
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                                    

                                                                                    

                                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                                        
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                                        
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                                        

                                                                                            
    
                                                                                                
  • 
                                                                                                    
    Run the following command:
    
                                                                                                    
    /etc/init.d/hpbsmd start
    
                                                                                                    
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                    
    start, stop, and restart
    
                                                                                                
    • 
                                                                                                
  • 
                                                                                                    
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                                    
    The script supports the following command-line options:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                    
    
                                                                                                
    • 
                                                                                            

                                                                                        

                                                                                        

                                                                                            

                                                                                                

                                                                                                    
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                    
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                    

                                                                                                    
You can also monitor the below log files:

                                                                                                    
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                    

                                                                                                    
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                    

                                                                                                

                                                                                                
Run the following command:

                                                                                                
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                                

                                                                                                
The script supports the following command-line options:

                                                                                                
start, stop, stopall, and restart

                                                                                                

                                                                                                    
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                                

                                                                                            

                                                                                        

                                                                                        
You can view the status of the OBM services from the below log file:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                        
Run the following command to check the process status:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        

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

                                                                                            

                                                                                                
Replace the

                                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                                

                                                                                                
line with the

                                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                                

                                                                                                
line.

                                                                                            

                                                                                        

                                                                                    

                                                                                    

                                                                                        
To enable OBM, do the following:

                                                                                        
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                        

                                                                                            
Note You can also monitor the below log files:

                                                                                            
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                            

                                                                                            
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                            

                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                        
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                    

                                                                                    

                                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                                        

                                                                                            
    
                                                                                                
  • 
                                                                                                    
    Run the following command:
    
                                                                                                    
    /etc/init.d/hpbsmd start 
    
                                                                                                    
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                    
    start, stop, and restart
    
                                                                                                
    • 
                                                                                                
  • 
                                                                                                    
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                    
    The script supports the following command-line options:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                    
    
                                                                                                
    • 
                                                                                            

                                                                                        

                                                                                        

                                                                                            

                                                                                                

                                                                                                    
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                    
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                    

                                                                                                    
You can also monitor the below log files:

                                                                                                    
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                    

                                                                                                    
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                    

                                                                                                

                                                                                                
Run the following command:

                                                                                                
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                                

                                                                                                
The script supports the following command-line options:

                                                                                                
start, stop, stopall, and restart

                                                                                                

                                                                                                    
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                                

                                                                                            

                                                                                        

                                                                                        
You can view the status of the OBM services from the below log file:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                        
Run the following command to check the process status:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        

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

                                                                                            

                                                                                                
Replace the

                                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                                

                                                                                                
line with the

                                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                                

                                                                                                
line.

                                                                                            

                                                                                        

                                                                                    

                                                                                    

                                                                                        
To enable OBM, do the following:

                                                                                        
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                        

                                                                                            
Note You can also monitor the below log files:

                                                                                            
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                            

                                                                                            
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                            

                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                        
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                    

                                                                                    

                                                                                        

                                                                                            
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                            
    
                                                                                                
  • 
                                                                                                    
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                                    
    Restart all OBM servers and data collectors.
    
                                                                                                
    • 
                                                                                                
  • 
                                                                                                    
    If you modified databases on a running OBM deployment:
    
                                                                                                    
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                                    
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                                    
      
                                                                                                        
    1. 
                                                                                                            
      Navigate to the following directory: 
      
                                                                                                            
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                            
      
                                                                                                            
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                        
      2. 
                                                                                                        
    2. 
                                                                                                            
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                        
      3. 
                                                                                                        
    3. 
                                                                                                            
      Restart OBM servicesprocesses.
      
                                                                                                        
      4. 
                                                                                                    
    
                                                                                                
    • 
                                                                                            

                                                                                        

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                    

                                                                                    

                                                                                        
 After you enable the active server, the upgrade process on active server is complete. 

                                                                                        
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                        
After you upgrade active server and gateway servers, start the upgrade process on backup server. Go to Initiate the upgrade process section and follow the steps. Enable OBM on backup server. The upgrade process on backup server is complete.

                                                                                    

                                                                                    

                                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                                        
In an HA environment, run the start command on the active server. Wait until the process is complete. After the active server is fully up, enable the gateway servers and backup server. 

                                                                                        

                                                                                            
    
                                                                                                
  • 
                                                                                                    
    Run the following command:
    
                                                                                                    
    /etc/init.d/hpbsmd start 
    
                                                                                                    
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                    
    start, stop, and restart
    
                                                                                                
    • 
                                                                                                
  • 
                                                                                                    
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                    
    The script supports the following command-line options:
    
                                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                    
    
                                                                                                
    • 
                                                                                            

                                                                                        

                                                                                        

                                                                                            

                                                                                                

                                                                                                    
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                    
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                    

                                                                                                    
You can also monitor the below log files:

                                                                                                    
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                    

                                                                                                    
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                    

                                                                                                

                                                                                                
Run the following command:

                                                                                                
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                                

                                                                                                
The script supports the following command-line options:

                                                                                                
start, stop, stopall, and restart

                                                                                                

                                                                                                    
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                                

                                                                                            

                                                                                        

                                                                                        
You can view the status of the OBM services from the below log file:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                        
Run the following command to check the process status:

                                                                                        
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        

                                                                                        

                                                                                            
Applicable only for High Availability environment.
                                                                                            

                                                                                            
In a high availability environment, first enable the active server and wait until this process is completed before starting the gateway servers and the backup server. Make sure that all HAC processes are running. 

                                                                                            
Run the following command to check the status of the HAC processess:

                                                                                            
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                            

                                                                                        

                                                                                        

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

                                                                                            

                                                                                                
Replace the

                                                                                                
-Djava.net.preferIPv4Stack=false
                                                                                                

                                                                                                
line with the

                                                                                                
-Djava.net.preferIPv4Stack=true
                                                                                                

                                                                                                
line.

                                                                                            

                                                                                        

                                                                                    

                                                                                    

                                                                                        
To enable OBM, do the following:

                                                                                        
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                        

                                                                                            
Note You can also monitor the below log files:

                                                                                            
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                            

                                                                                            
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                            

                                                                                        

                                                                                        
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                        
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                                        
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                                        
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
Before starting the OBM servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already being applied on the production OBM server.  Run this command on the staging OBM primary data processing server:

                                                                                    
<OBM_HOME>\opr\support\opr-support-utils.bat -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                    

                                                                                

                                                                            

                                                                            
To start the OBM processes and enable OBM, do the following:

                                                                            

                                                                                
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                            

                                                                            

                                                                                
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                            

                                                                            

                                                                                

                                                                                    
    
                                                                                        
  • 
                                                                                            
    Run the following command:
    
                                                                                            
    /etc/init.d/hpbsmd start 
    
                                                                                            
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                            
    start, stop, and restart
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                            
    The script supports the following command-line options:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        

                                                                                            
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                            
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                            

                                                                                            
You can also monitor the below log files:

                                                                                            
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                            

                                                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                            

                                                                                        

                                                                                        
Run the following command:

                                                                                        
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                        

                                                                                        
The script supports the following command-line options:

                                                                                        
start, stop, stopall, and restart

                                                                                        

                                                                                            
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                        

                                                                                    

                                                                                

                                                                                
You can view the status of the OBM services from the below log file:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                
Run the following command to check the process status:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                

                                                                                    
Applicable only for High Availability environment.
                                                                                    

                                                                                    
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                                    
Run the following command to check the status of the HAC processess:

                                                                                    
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                    

                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
To enable OBM, do the following:

                                                                                
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                

                                                                                    
Note You can also monitor the below log files:

                                                                                    
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                    

                                                                                    
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                    

                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                            

                                                                            

                                                                                

                                                                                    
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                    
    
                                                                                        
  • 
                                                                                            
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                            
    Restart all OBM servers and data collectors.
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    If you modified databases on a running OBM deployment:
    
                                                                                            
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                            
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      Navigate to the following directory: 
      
                                                                                                    
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                    
      
                                                                                                    
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                
      3. 
                                                                                                
    3. 
                                                                                                    
      Restart OBMservicesprocesses.
      
                                                                                                
      4. 
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    
After the active server is upgraded, enable the active server. Upgrade the backup server and enable the backup server.  If there are any additional gateway servers, repeat the steps to complete the upgrade for gateway servers.

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    
For a side-by-side upgrade, after you enable primary staging server, repeat the steps to upgrade secondary staging server and enable the secondary staging server. 

                                                                                

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                            

                                                                            

                                                                                
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s).

                                                                                
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS.

                                                                            

                                                                            

                                                                                
To start the OBM processes and enable OBM, do the following:

                                                                                

                                                                                    
    
                                                                                        
  • 
                                                                                            
    Run the following command:
    
                                                                                            
    /etc/init.d/hpbsmd start 
    
                                                                                            
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                            
    start, stop, and restart
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    Log off from the OBM host system, log on as a new user, and then run the following command:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                            
    The script supports the following command-line options:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        

                                                                                            
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                            
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                            

                                                                                            
You can also monitor the below log files:

                                                                                            
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                            

                                                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                            

                                                                                        

                                                                                        
Run the following command:

                                                                                        
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                        

                                                                                        
The script supports the following command-line options:

                                                                                        
start, stop, stopall, and restart

                                                                                        

                                                                                            
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
Applicable only for High Availability environment.
                                                                                    

                                                                                    
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                                    
Run the following command to check the status of the HAC processess:

                                                                                    
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                    

                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
To enable OBM, do the following:

                                                                                
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                

                                                                                    
Note You can also monitor the below log files:

                                                                                    
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                    

                                                                                    
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                    

                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                            

                                                                            

                                                                                

                                                                                    
Note Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                    
    
                                                                                        
  • 
                                                                                            
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                            
    Restart all OBM servers and data collectors.
    
                                                                                            
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      Navigate to the following directory: 
      
                                                                                                    
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                    
      
                                                                                                    
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                
      3. 
                                                                                                
    3. 
                                                                                                    
      Restart OBM servicesprocesses.
      
                                                                                                
      4. 
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                                

                                                                                

                                                                                    
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                                    
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                    
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                                    
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start 
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                                

                                                                                    

                                                                                        
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                        
    
                                                                                            
  • 
                                                                                                
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                                
    Restart all OBM servers and data collectors.
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    If you modified databases on a running OBM deployment:
    
                                                                                                
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                                
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                                
      
                                                                                                    
    1. 
                                                                                                        
      Navigate to the following directory: 
      
                                                                                                        
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                        
      
                                                                                                        
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                    
      2. 
                                                                                                    
    2. 
                                                                                                        
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                    
      3. 
                                                                                                    
    3. 
                                                                                                        
      Restart OBM servicesprocesses.
      
                                                                                                    
      4. 
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            

                                                                
Enable OBM

                                                                

                                                                    

                                                                        

                                                                            
After you update the DPS and the gateway server, make sure that the live bus is assigned to the updated DPS. Run the following command to check the live bus status:

                                                                            

                                                                                
<TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                

                                                                            

                                                                            

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

                                                                            

                                                                            

                                                                                
To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.

                                                                            

                                                                            

                                                                                
    
                                                                                    
  1. 
                                                                                        
    Run the following command to start OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    2. 
                                                                                    
  2. 
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    start, stop, stopall, and restart
                                                                                        
    
                                                                                    
    3. 
                                                                                    
  3. 
                                                                                        
    You can view the status of the OBM services from the below log file:
    
                                                                                        
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        
    
                                                                                        
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.
    
                                                                                        
    Run the following command to check the process status:
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
    
                                                                                    
    4. 
                                                                                    
  4. 
                                                                                        
    Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:
    
                                                                                        
    tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                        
    
                                                                                        
    You can also monitor the below log files:
    
                                                                                        
    /opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                        
    
                                                                                        
    /opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                        
    
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    start, stop, stopall, and restart
    
                                                                                        
    
                                                                                            
    Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.
    
                                                                                        
    
                                                                                    
    5. 
                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                    

                                                                        

                                                                            
After you update the inactive server, make sure that the live bus is assigned to the updated server. Run the following command to check the live bus status:

                                                                            

                                                                                
<TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                

                                                                            

                                                                            

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

                                                                            

                                                                            

                                                                                
Start the OBM services on inactive server and remaining gateway server, if any.

                                                                                

                                                                                    
To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.

                                                                                

                                                                                
    
                                                                                    
  1. 
                                                                                        
    Run the following command to start OBM services as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
    
                                                                                    
    2. 
                                                                                    
  2. 
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    start, stop, stopall, and restart
                                                                                        
    
                                                                                        
    Make sure that the OBM start up is not interrupted. 
    
                                                                                    
    3. 
                                                                                    
  3. 
                                                                                        
    You can view the status of the OBM services from the below log file:
    
                                                                                        
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                        
    
                                                                                        
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.
    
                                                                                        
    Run the following command to check the process status:
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
    
                                                                                    
    4. 
                                                                                    
  4. 
                                                                                        
    
                                                                                            
    Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:
    
                                                                                            
    tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                            
    
                                                                                            
    You can also monitor the below log files:
    
                                                                                            
    /opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                            
    
                                                                                            
    /opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                            
    
                                                                                            
    The script supports the following command-line options:
    
                                                                                            
    start, stop, stopall, and restart
    
                                                                                            
    
                                                                                                
    Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.
    
                                                                                            
    
                                                                                        
    
                                                                                    
    5. 
                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Enable OBM

                                                            

                                                                

                                                                    

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                                

                                                                                

                                                                                    
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                                    
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                    
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                                    
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start 
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                                

                                                                                    

                                                                                        
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                        
    
                                                                                            
  • 
                                                                                                
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                                
    Restart all OBM servers and data collectors.
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    If you modified databases on a running OBM deployment:
    
                                                                                                
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                                
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                                
      
                                                                                                    
    1. 
                                                                                                        
      Navigate to the following directory: 
      
                                                                                                        
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                        
      
                                                                                                        
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                    
      2. 
                                                                                                    
    2. 
                                                                                                        
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                    
      3. 
                                                                                                    
    3. 
                                                                                                        
      Restart OBM servicesprocesses.
      
                                                                                                    
      4. 
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                

                                                                                

                                                                                    
 After you enable the active server, the upgrade process on active server is complete. 

                                                                                    
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                    
After you upgrade active server and gateway servers, start the upgrade process on backup server. Go to Initiate the upgrade process section and follow the steps. Enable OBM on backup server. The upgrade process on backup server is complete.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    
In an HA environment, run the start command on the active server. Wait until the process is complete. After the active server is fully up, enable the gateway servers and backup server. 

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start 
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

                                                                                        
Applicable only for High Availability environment.
                                                                                        

                                                                                        
In a high availability environment, first enable the active server and wait until this process is completed before starting the gateway servers and the backup server. Make sure that all HAC processes are running. 

                                                                                        
Run the following command to check the status of the HAC processess:

                                                                                        
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                        

                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                        

                                                                        

                                                                            

                                                                                

                                                                                    
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                                    
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                                    
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
Before starting the OBM servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already being applied on the production OBM server.  Run this command on the staging OBM primary data processing server:

                                                                                
<OBM_HOME>\opr\support\opr-support-utils.bat -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                

                                                                            

                                                                        

                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                        

                                                                            
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                        

                                                                        

                                                                            
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                        

                                                                        

                                                                            

                                                                                
    
                                                                                    
  • 
                                                                                        
    Run the following command:
    
                                                                                        
    /etc/init.d/hpbsmd start 
    
                                                                                        
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                        
    start, stop, and restart
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                        
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                        

                                                                                        
You can also monitor the below log files:

                                                                                        
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                        

                                                                                        
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                        

                                                                                    

                                                                                    
Run the following command:

                                                                                    
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                    

                                                                                    
The script supports the following command-line options:

                                                                                    
start, stop, stopall, and restart

                                                                                    

                                                                                        
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                    

                                                                                

                                                                            

                                                                            
You can view the status of the OBM services from the below log file:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                            
Run the following command to check the process status:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            

                                                                                
Applicable only for High Availability environment.
                                                                                

                                                                                
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                                
Run the following command to check the status of the HAC processess:

                                                                                
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                

                                                                            

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            
To enable OBM, do the following:

                                                                            
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                            

                                                                                
Note You can also monitor the below log files:

                                                                                
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                

                                                                                
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                

                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                            
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                        

                                                                        

                                                                            

                                                                                
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                
    
                                                                                    
  • 
                                                                                        
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                        
    Restart all OBM servers and data collectors.
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    If you modified databases on a running OBM deployment:
    
                                                                                        
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                        
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                        
      
                                                                                            
    1. 
                                                                                                
      Navigate to the following directory: 
      
                                                                                                
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                
      
                                                                                                
      It contains two subdirectories: /loaded and /toload.
      
                                                                                            
      2. 
                                                                                            
    2. 
                                                                                                
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                            
      3. 
                                                                                            
    3. 
                                                                                                
      Restart OBMservicesprocesses.
      
                                                                                            
      4. 
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                        

                                                                        

                                                                            

                                                                                
After the active server is upgraded, enable the active server. Upgrade the backup server and enable the backup server.  If there are any additional gateway servers, repeat the steps to complete the upgrade for gateway servers.

                                                                            

                                                                        

                                                                        

                                                                            

                                                                                
For a side-by-side upgrade, after you enable primary staging server, repeat the steps to upgrade secondary staging server and enable the secondary staging server. 

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                        

                                                                        

                                                                            
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s).

                                                                            
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS.

                                                                        

                                                                        

                                                                            
To start the OBM processes and enable OBM, do the following:

                                                                            

                                                                                
    
                                                                                    
  • 
                                                                                        
    Run the following command:
    
                                                                                        
    /etc/init.d/hpbsmd start 
    
                                                                                        
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                        
    start, stop, and restart
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    Log off from the OBM host system, log on as a new user, and then run the following command:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                        
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                        

                                                                                        
You can also monitor the below log files:

                                                                                        
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                        

                                                                                        
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                        

                                                                                    

                                                                                    
Run the following command:

                                                                                    
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                    

                                                                                    
The script supports the following command-line options:

                                                                                    
start, stop, stopall, and restart

                                                                                    

                                                                                        
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
Applicable only for High Availability environment.
                                                                                

                                                                                
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                                
Run the following command to check the status of the HAC processess:

                                                                                
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                

                                                                            

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            
To enable OBM, do the following:

                                                                            
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                            

                                                                                
Note You can also monitor the below log files:

                                                                                
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                

                                                                                
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                

                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                            
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                        

                                                                        

                                                                            

                                                                                
Note Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                
    
                                                                                    
  • 
                                                                                        
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                        
    Restart all OBM servers and data collectors.
    
                                                                                        
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                        
      
                                                                                            
    1. 
                                                                                                
      Navigate to the following directory: 
      
                                                                                                
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                
      
                                                                                                
      It contains two subdirectories: /loaded and /toload.
      
                                                                                            
      2. 
                                                                                            
    2. 
                                                                                                
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                            
      3. 
                                                                                            
    3. 
                                                                                                
      Restart OBM servicesprocesses.
      
                                                                                            
      4. 
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            

                                                                                
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                            

                                                                            

                                                                                
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                                
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                            

                                                                            

                                                                                
To start the OBM processes and enable OBM, do the following:

                                                                                
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                                
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                                

                                                                                    
    
                                                                                        
  • 
                                                                                            
    Run the following command:
    
                                                                                            
    /etc/init.d/hpbsmd start
    
                                                                                            
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                            
    start, stop, and restart
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                            
    The script supports the following command-line options:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        

                                                                                            
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                            
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                            

                                                                                            
You can also monitor the below log files:

                                                                                            
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                            

                                                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                            

                                                                                        

                                                                                        
Run the following command:

                                                                                        
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                        

                                                                                        
The script supports the following command-line options:

                                                                                        
start, stop, stopall, and restart

                                                                                        

                                                                                            
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                        

                                                                                    

                                                                                

                                                                                
You can view the status of the OBM services from the below log file:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                
Run the following command to check the process status:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
To enable OBM, do the following:

                                                                                
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                

                                                                                    
Note You can also monitor the below log files:

                                                                                    
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                    

                                                                                    
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                    

                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            

                                                                                
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                            

                                                                            

                                                                                
To start the OBM processes and enable OBM, do the following:

                                                                                

                                                                                    
    
                                                                                        
  • 
                                                                                            
    Run the following command:
    
                                                                                            
    /etc/init.d/hpbsmd start 
    
                                                                                            
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                            
    start, stop, and restart
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                            
    The script supports the following command-line options:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        

                                                                                            
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                            
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                            

                                                                                            
You can also monitor the below log files:

                                                                                            
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                            

                                                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                            

                                                                                        

                                                                                        
Run the following command:

                                                                                        
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                        

                                                                                        
The script supports the following command-line options:

                                                                                        
start, stop, stopall, and restart

                                                                                        

                                                                                            
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                        

                                                                                    

                                                                                

                                                                                
You can view the status of the OBM services from the below log file:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                
Run the following command to check the process status:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
To enable OBM, do the following:

                                                                                
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                

                                                                                    
Note You can also monitor the below log files:

                                                                                    
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                    

                                                                                    
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                    

                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                            

                                                                            

                                                                                

                                                                                    
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                    
    
                                                                                        
  • 
                                                                                            
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                            
    Restart all OBM servers and data collectors.
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    If you modified databases on a running OBM deployment:
    
                                                                                            
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                            
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      Navigate to the following directory: 
      
                                                                                                    
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                    
      
                                                                                                    
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                
      3. 
                                                                                                
    3. 
                                                                                                    
      Restart OBM servicesprocesses.
      
                                                                                                
      4. 
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Enable OBM

                                                            

                                                                

                                                                    

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                                

                                                                                

                                                                                    
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                                    
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                    
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                                    
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start 
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                                

                                                                                    

                                                                                        
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                        
    
                                                                                            
  • 
                                                                                                
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                                
    Restart all OBM servers and data collectors.
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    If you modified databases on a running OBM deployment:
    
                                                                                                
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                                
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                                
      
                                                                                                    
    1. 
                                                                                                        
      Navigate to the following directory: 
      
                                                                                                        
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                        
      
                                                                                                        
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                    
      2. 
                                                                                                    
    2. 
                                                                                                        
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                    
      3. 
                                                                                                    
    3. 
                                                                                                        
      Restart OBM servicesprocesses.
      
                                                                                                    
      4. 
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            

                                                                                

                                                                                    
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                                

                                                                                

                                                                                    
 After you enable the active server, the upgrade process on active server is complete. 

                                                                                    
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                    
After you upgrade active server and gateway servers, start the upgrade process on backup server. Go to Initiate the upgrade process section and follow the steps. Enable OBM on backup server. The upgrade process on backup server is complete.

                                                                                

                                                                                

                                                                                    
To start the OBM processes and enable OBM, do the following:

                                                                                    
In an HA environment, run the start command on the active server. Wait until the process is complete. After the active server is fully up, enable the gateway servers and backup server. 

                                                                                    

                                                                                        
    
                                                                                            
  • 
                                                                                                
    Run the following command:
    
                                                                                                
    /etc/init.d/hpbsmd start 
    
                                                                                                
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                                
    start, stop, and restart
    
                                                                                            
    • 
                                                                                            
  • 
                                                                                                
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                                
    The script supports the following command-line options:
    
                                                                                                
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                                
    
                                                                                            
    • 
                                                                                        

                                                                                    

                                                                                    

                                                                                        

                                                                                            

                                                                                                
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                                
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                                

                                                                                                
You can also monitor the below log files:

                                                                                                
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                                

                                                                                                
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                                

                                                                                            

                                                                                            
Run the following command:

                                                                                            
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                            

                                                                                            
The script supports the following command-line options:

                                                                                            
start, stop, stopall, and restart

                                                                                            

                                                                                                
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                            

                                                                                        

                                                                                    

                                                                                    
You can view the status of the OBM services from the below log file:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                    
Run the following command to check the process status:

                                                                                    
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    

                                                                                    

                                                                                        
Applicable only for High Availability environment.
                                                                                        

                                                                                        
In a high availability environment, first enable the active server and wait until this process is completed before starting the gateway servers and the backup server. Make sure that all HAC processes are running. 

                                                                                        
Run the following command to check the status of the HAC processess:

                                                                                        
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                        

                                                                                    

                                                                                    

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

                                                                                        

                                                                                            
Replace the

                                                                                            
-Djava.net.preferIPv4Stack=false
                                                                                            

                                                                                            
line with the

                                                                                            
-Djava.net.preferIPv4Stack=true
                                                                                            

                                                                                            
line.

                                                                                        

                                                                                    

                                                                                

                                                                                

                                                                                    
To enable OBM, do the following:

                                                                                    
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                    

                                                                                        
Note You can also monitor the below log files:

                                                                                        
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                        

                                                                                        
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                        

                                                                                    

                                                                                    
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                    
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                        

                                                                        

                                                                            

                                                                                

                                                                                    
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                                    
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    
Before starting the OBM   servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already applied on the production OBM server.  Run the following command on the staging OBM primary data processing server:

                                                                                    
/opt/HP/BSM/opr/support/opr-support-utils.sh -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
Before starting the OBM servers, set Staging Mode Enable to true. This disables event automation rules, deduplication, suppression and correlation on the staging OBM server since these are already being applied on the production OBM server.  Run this command on the staging OBM primary data processing server:

                                                                                
<OBM_HOME>\opr\support\opr-support-utils.bat -set_setting -context opr -set opr.staging.mode.enabled true
                                                                                

                                                                            

                                                                        

                                                                        
To start the OBM processes and enable OBM, do the following:

                                                                        

                                                                            
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                        

                                                                        

                                                                            
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                        

                                                                        

                                                                            

                                                                                
    
                                                                                    
  • 
                                                                                        
    Run the following command:
    
                                                                                        
    /etc/init.d/hpbsmd start 
    
                                                                                        
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                        
    start, stop, and restart
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                        
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                        

                                                                                        
You can also monitor the below log files:

                                                                                        
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                        

                                                                                        
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                        

                                                                                    

                                                                                    
Run the following command:

                                                                                    
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                    

                                                                                    
The script supports the following command-line options:

                                                                                    
start, stop, stopall, and restart

                                                                                    

                                                                                        
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                    

                                                                                

                                                                            

                                                                            
You can view the status of the OBM services from the below log file:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                            
Run the following command to check the process status:

                                                                            
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                            

                                                                            

                                                                                
Applicable only for High Availability environment.
                                                                                

                                                                                
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                                
Run the following command to check the status of the HAC processess:

                                                                                
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                

                                                                            

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            
To enable OBM, do the following:

                                                                            
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                            

                                                                                
Note You can also monitor the below log files:

                                                                                
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                

                                                                                
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                

                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                            
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                        

                                                                        

                                                                            

                                                                                
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                
    
                                                                                    
  • 
                                                                                        
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                        
    Restart all OBM servers and data collectors.
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    If you modified databases on a running OBM deployment:
    
                                                                                        
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                        
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                        
      
                                                                                            
    1. 
                                                                                                
      Navigate to the following directory: 
      
                                                                                                
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                
      
                                                                                                
      It contains two subdirectories: /loaded and /toload.
      
                                                                                            
      2. 
                                                                                            
    2. 
                                                                                                
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                            
      3. 
                                                                                            
    3. 
                                                                                                
      Restart OBMservicesprocesses.
      
                                                                                            
      4. 
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                        

                                                                        

                                                                            

                                                                                
After the active server is upgraded, enable the active server. Upgrade the backup server and enable the backup server.  If there are any additional gateway servers, repeat the steps to complete the upgrade for gateway servers.

                                                                            

                                                                        

                                                                        

                                                                            

                                                                                
For a side-by-side upgrade, after you enable primary staging server, repeat the steps to upgrade secondary staging server and enable the secondary staging server. 

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                        

                                                                        

                                                                            
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s).

                                                                            
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS.

                                                                        

                                                                        

                                                                            
To start the OBM processes and enable OBM, do the following:

                                                                            

                                                                                
    
                                                                                    
  • 
                                                                                        
    Run the following command:
    
                                                                                        
    /etc/init.d/hpbsmd start 
    
                                                                                        
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                        
    start, stop, and restart
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    Log off from the OBM host system, log on as a new user, and then run the following command:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                            

                                                                                

                                                                                    

                                                                                        
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                        
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                        

                                                                                        
You can also monitor the below log files:

                                                                                        
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                        

                                                                                        
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                        

                                                                                    

                                                                                    
Run the following command:

                                                                                    
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                    

                                                                                    
The script supports the following command-line options:

                                                                                    
start, stop, stopall, and restart

                                                                                    

                                                                                        
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
Applicable only for High Availability environment.
                                                                                

                                                                                
In a high availability environment, first enable the primary data processing server and wait until this process is completed before starting the gateway servers and the secondary DPS. Make sure that all HAC processes are running. 

                                                                                
Run the following command to check the status of the HAC processess:

                                                                                
/opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                

                                                                            

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                        

                                                                            
To enable OBM, do the following:

                                                                            
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                            

                                                                                
Note You can also monitor the below log files:

                                                                                
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                

                                                                                
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                

                                                                            

                                                                            
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                            
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                        

                                                                        

                                                                            

                                                                                
Note Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                
    
                                                                                    
  • 
                                                                                        
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                        
    Restart all OBM servers and data collectors.
    
                                                                                        
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                    
    • 
                                                                                    
  • 
                                                                                        
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                        
      
                                                                                            
    1. 
                                                                                                
      Navigate to the following directory: 
      
                                                                                                
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                
      
                                                                                                
      It contains two subdirectories: /loaded and /toload.
      
                                                                                            
      2. 
                                                                                            
    2. 
                                                                                                
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                            
      3. 
                                                                                            
    3. 
                                                                                                
      Restart OBM servicesprocesses.
      
                                                                                            
      4. 
                                                                                        
    
                                                                                    
    • 
                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            

                                                                                
Note Instructions vary based on your deployment. Make sure you read the step carefully before you start the data processing server or gateway server.

                                                                            

                                                                            

                                                                                
 After you enable the primary DPS, the upgrade process on primary DPS is complete. 

                                                                                
To upgrade the gateway server, go to Initiate the upgrade process section and follow the steps. Enable OBM on each gateway server. The upgrade process on each gateway is complete.

                                                                                
After you upgrade primary DPS and gateway servers, start the upgrade process on secondary DPS. Go to Initiate the upgrade process section and follow the steps. Enable OBM on secondary DPS. The upgrade process on secondary DPS is complete.

                                                                            

                                                                            

                                                                                
To start the OBM processes and enable OBM, do the following:

                                                                                
In a distributed environment, run the start command on the DPS first. Wait until the process is complete. After the DPS is fully up, enable the gateway server(s). 

                                                                                
In an HA environment, run the start command on the primary DPS. Wait until the process is complete. After the primary DPS is fully up, enable the gateway servers and secondary DPS. 

                                                                                

                                                                                    
    
                                                                                        
  • 
                                                                                            
    Run the following command:
    
                                                                                            
    /etc/init.d/hpbsmd start
    
                                                                                            
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                            
    start, stop, and restart
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm start
    
                                                                                            
    The script supports the following command-line options:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        

                                                                                            
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                            
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                            

                                                                                            
You can also monitor the below log files:

                                                                                            
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                            

                                                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                            

                                                                                        

                                                                                        
Run the following command:

                                                                                        
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                        

                                                                                        
The script supports the following command-line options:

                                                                                        
start, stop, stopall, and restart

                                                                                        

                                                                                            
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                        

                                                                                    

                                                                                

                                                                                
You can view the status of the OBM services from the below log file:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                
Run the following command to check the process status:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
To enable OBM, do the following:

                                                                                
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                

                                                                                    
Note You can also monitor the below log files:

                                                                                    
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                    

                                                                                    
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                    

                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        

                                                                            

                                                                                
Note Instructions vary based on your deployment. Make sure to follow the procedure carefully before you start the services.

                                                                            

                                                                            

                                                                                
To start the OBM processes and enable OBM, do the following:

                                                                                

                                                                                    
    
                                                                                        
  • 
                                                                                            
    Run the following command:
    
                                                                                            
    /etc/init.d/hpbsmd start 
    
                                                                                            
    The hpbsmd daemon script first switches to the non-root user and then enables OBM. The script supports the following command-line options:
    
                                                                                            
    start, stop, and restart
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    Log off from the OBM host system, log on as a new user, and then run the following command as non-root user:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm start 
    
                                                                                            
    The script supports the following command-line options:
    
                                                                                            
    /opt/HP/BSM/scripts/run_hpbsm (start|stop|restart)
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                                

                                                                                    

                                                                                        

                                                                                            
Note Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:

                                                                                            
tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                            

                                                                                            
You can also monitor the below log files:

                                                                                            
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                            

                                                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                            

                                                                                        

                                                                                        
Run the following command:

                                                                                        
/opt/HP/BSM/scripts/run_hpbsm start
                                                                                        

                                                                                        
The script supports the following command-line options:

                                                                                        
start, stop, stopall, and restart

                                                                                        

                                                                                            
Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.

                                                                                        

                                                                                    

                                                                                

                                                                                
You can view the status of the OBM services from the below log file:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.

                                                                                
Run the following command to check the process status:

                                                                                
/opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                

                                                                                

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

                                                                                    

                                                                                        
Replace the

                                                                                        
-Djava.net.preferIPv4Stack=false
                                                                                        

                                                                                        
line with the

                                                                                        
-Djava.net.preferIPv4Stack=true
                                                                                        

                                                                                        
line.

                                                                                    

                                                                                

                                                                            

                                                                            

                                                                                
To enable OBM, do the following:

                                                                                
In Windows, select Start > Applications >Enable Operations Bridge Manager.

                                                                                

                                                                                    
Note You can also monitor the below log files:

                                                                                    
<TOPAZ_HOME>\log\supervisor\nanny_all.log
                                                                                    

                                                                                    
<TOPAZ_HOME>\ucmdb\runtime\log\startup.log
                                                                                    

                                                                                

                                                                                
The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing for the first time. In BSM status page, the pre-initializer description is periodically updated to show the background task. The last modified time stamp is also shown on the DPS.

                                                                                
To check the BSM status, go to Start > Programs > Operations Bridge Manager > Operations Bridge Manager Status.

                                                                            

                                                                            

                                                                                

                                                                                    
Depending on what you used the configuration wizard for, perform the appropriate post-configuration action after the wizard completes:

                                                                                    
    
                                                                                        
  • 
                                                                                            
    If you added a new gateway server or modified the previously defined database types or connection parameters:
    
                                                                                            
    Restart all OBM servers and data collectors.
    
                                                                                        
    • 
                                                                                        
  • 
                                                                                            
    If you modified databases on a running OBM deployment:
    
                                                                                            
    Keep in mind that the My Workspace and Service Health pages are emptied and the OBM perspectives are removed.
    
                                                                                            
    To restore the pages' contents and the perspectives, do the following:
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      Navigate to the following directory: 
      
                                                                                                    
      <GatewayServerRootDirectory>/conf/uimashup/import
                                                                                                    
      
                                                                                                    
      It contains two subdirectories: /loaded and /toload.
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      Copy the contents of the /loaded directory into the /toload directory.
      
                                                                                                
      3. 
                                                                                                
    3. 
                                                                                                    
      Restart OBM servicesprocesses.
      
                                                                                                
      4. 
                                                                                            
    
                                                                                        
    • 
                                                                                    

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Enable OBM

                                                            

                                                                

                                                                    

                                                                        
After you update the DPS and the gateway server, make sure that the live bus is assigned to the updated DPS. Run the following command to check the live bus status:

                                                                        

                                                                            
<TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                            

                                                                        

                                                                        

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

                                                                        

                                                                        

                                                                            
To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.

                                                                        

                                                                        

                                                                            
    
                                                                                
  1. 
                                                                                    
    Run the following command to start OBM services as non-root user:
    
                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                    
    
                                                                                
    2. 
                                                                                
  2. 
                                                                                    
    The script supports the following command-line options:
    
                                                                                    
    start, stop, stopall, and restart
                                                                                    
    
                                                                                
    3. 
                                                                                
  3. 
                                                                                    
    You can view the status of the OBM services from the below log file:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                    
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.
    
                                                                                    
    Run the following command to check the process status:
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
    
                                                                                
    4. 
                                                                                
  4. 
                                                                                    
    Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:
    
                                                                                    
    tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                    
    
                                                                                    
    You can also monitor the below log files:
    
                                                                                    
    /opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                    
    
                                                                                    
    /opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                    
    
                                                                                    
    The script supports the following command-line options:
    
                                                                                    
    start, stop, stopall, and restart
    
                                                                                    
    
                                                                                        
    Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.
    
                                                                                    
    
                                                                                
    5. 
                                                                            

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                                

                                                                    

                                                                        
After you update the inactive server, make sure that the live bus is assigned to the updated server. Run the following command to check the live bus status:

                                                                        

                                                                            
<TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                            

                                                                        

                                                                        

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

                                                                        

                                                                        

                                                                            
Start the OBM services on inactive server and remaining gateway server, if any.

                                                                            

                                                                                
To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.

                                                                            

                                                                            
    
                                                                                
  1. 
                                                                                    
    Run the following command to start OBM services as non-root user:
    
                                                                                    
    /opt/HP/BSM/scripts/run_hpbsm start
                                                                                    
    
                                                                                
    2. 
                                                                                
  2. 
                                                                                    
    The script supports the following command-line options:
    
                                                                                    
    start, stop, stopall, and restart
                                                                                    
    
                                                                                    
    Make sure that the OBM start up is not interrupted. 
    
                                                                                
    3. 
                                                                                
  3. 
                                                                                    
    You can view the status of the OBM services from the below log file:
    
                                                                                    
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
                                                                                    
    
                                                                                    
    The UCMDB pre-initializer takes a considerable amount of time when you start OBM services after installing it for the first time. In the BSM status page, the pre-initializer description is periodically updated to show the background task and the last modified timestamp.
    
                                                                                    
    Run the following command to check the process status:
    /opt/HP/BSM/tools/bsmstatus/bsmstatus.sh
    
                                                                                
    4. 
                                                                                
  4. 
                                                                                    
    
                                                                                        
    Make sure that the OBM start up is not  interrupted.  Run the following command to check the time taken to configure RTSM:
    
                                                                                        
    tail -F /opt/HP/BSM/ucmdb/runtime/log/cmdb.dal.log
                                                                                        
    
                                                                                        
    You can also monitor the below log files:
    
                                                                                        
    /opt/HP/BSM/log/supervisor/nanny_all.log
                                                                                        
    
                                                                                        
    /opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                                        
    
                                                                                        
    The script supports the following command-line options:
    
                                                                                        
    start, stop, stopall, and restart
    
                                                                                        
    
                                                                                            
    Note For OBM 2018.11 and higher, the run_hpbsm stop command stops all services except the RTSM.  The run_hpbsm stopall command stops all services including the RTSM.
    
                                                                                        
    
                                                                                    
    
                                                                                
    5. 
                                                                            

                                                                            

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

                                                                                

                                                                                    
Replace the

                                                                                    
-Djava.net.preferIPv4Stack=false
                                                                                    

                                                                                    
line with the

                                                                                    
-Djava.net.preferIPv4Stack=true
                                                                                    

                                                                                    
line.

                                                                                

                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Update active DPS and gateway servers

                                                            

                                                                
After you enable the OBM services on updated DPS and gateway server, update the remaining non-updated servers.

                                                                

                                                                    
Follow the below steps to update and start the OBM services:

                                                                    
    
                                                                        
  1. 
                                                                            
    Move the HAC services from the active DPS to the updated DPS. 
    
                                                                            
      
                                                                                
    1. 
                                                                                    
      Reassign the services from non-updated to updated server. 
      
                                                                                    
      To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                    
      To check the status of the HAC services, run the following command :
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                        
      
                                                                                    
      
                                                                                
      2. 
                                                                                
    2. 
                                                                                    
      To check the live bus status, run the following command:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                        
      
                                                                                    
      
                                                                                    
      Assign live bus to updated DPS:
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                            
    
                                                                        
    2. 
                                                                        
  2. 
                                                                            
    After the HAC services are moved successfully, update the remaining non-updated set of gateway servers and data processing servers one after the other or concurrently depending on OBM usage/load. To perform the update, follow the steps:
    
                                                                            
      
                                                                                
    1. Open a Command Promptterminal window as an administratorthe root user on the system.
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to a location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      
                                                                                        
      Update OBM on non-updated DPS and remaining gateway servers. You can perform the update concurrently. Run the following command:
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -silent
                                                                                                    
      
                                                                                                    
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
      
                                                                                                    
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                    
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                    
      
                                                                                                    
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      
                                                                                                    
      upgrade.bat -d -gui
                                                                                                    
      
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -silent
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                        
      
                                                                                            
      
                                                                                                
      ./upgrade.sh -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>\log\configserver\configserver_all.log
                                                                                        
      
                                                                                        
      
                                                                                            
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                        
      
                                                                                        
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                        
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
      
                                                                                    
      
                                                                                
      5. 
                                                                            
    
                                                                        
    3. 
                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Update active server 

                                                            

                                                                
After enabling the  OBM services on updated server, you can update the remaining non-updated servers concurrently.

                                                                
Follow the below steps to update and start the OBM services:

                                                                
    
                                                                    
  1. 
                                                                        
    
                                                                            
    Move the HAC services from the active server to the updated server. 
    
                                                                        
    
                                                                        
      
                                                                            
    1. 
                                                                                
      Reassign the services from non-updated to updated server. 
      
                                                                                
      To reassign the services with JMX console, see High Availability for the Data Processing Server.
      
                                                                                
      To check the status of the HAC services, run the following command :
      
                                                                                
      
                                                                                    
      /opt/HP/BSM/opr/support/opr-support-utils.sh -lhs
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      <TOPAZ_HOME>\support\opr-support-utils.bat -lhs
                                                                                    
      
                                                                                
      
                                                                            
      2. 
                                                                            
    2. 
                                                                                
      To check the live bus status run the following command:
      
                                                                                
      
                                                                                    
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -getserver
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -getserver
                                                                                    
      
                                                                                
      
                                                                                
      Assign live bus to updated server:
      
                                                                                
      
                                                                                    
      <TOPAZ_HOME>\opr\support\opr-support-utils.bat -bus -setserver <server_name>
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      /opt/HP/BSM/opr/support/opr-support-utils.sh -bus -setserver <server_name>
                                                                                    
      
                                                                                
      
                                                                            
      3. 
                                                                        
    
                                                                    
    2. 
                                                                    
  2. 
                                                                        
    
                                                                            
    After the HAC services are moved successfully, update the remaining activer server (non-updated) and update if any additional gateway servers are configured. To perform the update, follow the steps:
    
                                                                            
      
                                                                                
    1. Open a Command Promptterminal window as an administratorthe root user.
      2. 
                                                                                
    2. 
                                                                                    
      Change the current directory to a location where you have extracted files from the OBM 2020.10 installation package.
      
                                                                                    
      Note: You should not have any whitespaces when you enter the path.
      
                                                                                    
      
                                                                                        
      
                                                                                            
      For non-root installation, extract the files in / directory.
      
                                                                                        
      
                                                                                    
      
                                                                                
      3. 
                                                                                
    3. 
                                                                                    
      Update OBM on non-updated server.
      
                                                                                    
      Run the following command:
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -silent
                                                                                                
      
                                                                                                
      The -silent command, by default, the upgrade installs OBM 2020.10 to the same drive where the previous version is installed.  run the following command:
      
                                                                                                
      Optional.If you want OBM to be installed to a different location, run the following command:
      
                                                                                                
      upgrade.bat -d -silent -filepath <full path of ovinstallparams.ini>
                                                                                                
      
                                                                                                
      where, <full path of ovinstallparams.ini> is the absolute path of the ovinstallparams.ini created in the Before you upgrade section.
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      
                                                                                                
      upgrade.bat -d -gui
                                                                                                
      
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -silent
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                    
      
                                                                                        
      
                                                                                            
      ./upgrade.sh -d -gui
                                                                                            
      
                                                                                        
      
                                                                                    
      
                                                                                
      4. 
                                                                                
    4. 
                                                                                    
      Verify  the configuration wizard is run successfully by checking the configuration log file. The configuration wizard runs silently in the background.
      
                                                                                    
      
                                                                                        
      <TOPAZ_HOME>/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      
                                                                                            
      Change the windows user account for OBM services. For more information, see  Change the Windows service user account section.
      
                                                                                        
      
                                                                                        
      To start the OBM services, go to Start > Applications > Enable Operations Bridge Manager.
      
                                                                                    
      
                                                                                    
      
                                                                                        
      /opt/HP/BSM/log/configserver/configserver_all.log
                                                                                        
      
                                                                                        
      After the update is complete, run the following command to start the OBM services as non-root user:
      
                                                                                        
      /opt/HP/BSM/scripts/run_hpbsm start
                                                                                        
      
                                                                                    
      
                                                                                
      5. 
                                                                            
    
                                                                        
    
                                                                    
    3. 
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            

                                                                
Upgrade on backup server

                                                                

                                                                    

                                                                        
After the gateway server upgrade is complete, repeat the below  steps to complete the upgrade on  backup server

                                                                        
    
                                                                            
  1. Initiate the upgrade process. Go to the section Initiate the upgrade process and follow the steps  backup server.
    2. 
                                                                            
  2. Attend the initial upgrade phase and complete the installation in the UI. 
    3. 
                                                                        

                                                                        
The upgrade is complete. You can proceed and log on to OBM.

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            

                                                                
Optional.Upgrade on each gateway server

                                                                

                                                                    
After the primary DPSactive server upgrade is completed, you can start the upgrade process on each gateway server. Follow the steps: 

                                                                    
    
                                                                        
  1.  Initiate the upgrade process. Go to the section Initiate the upgrade process and follow the steps for gateway server.
    2. 
                                                                        
  2. Attend the initial upgrade phase and complete the installation in the UI. 
    3. 
                                                                    

                                                                    
If there are multiple gateway servers, you can run the upgrade concurrently on each gateway server.

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            

                                                                
Upgrade on secondary data processing server 

                                                                

                                                                    

                                                                        
After the gateway server upgrade is complete, repeat the below  steps to complete the upgrade on secondary DPS 

                                                                        
    
                                                                            
  1. Initiate the upgrade process. Go to the section Initiate the upgrade process and follow the steps for secondary DPS .
    2. 
                                                                            
  2. Attend the initial upgrade phase and complete the installation in the UI. 
    3. 
                                                                        

                                                                        
The upgrade is complete. You can proceed and log on to OBM.

                                                                    

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Log on to OBM

                                                    

                                                        
You can log on to OBM from a supported web browser on a client system by using the Login page. 

                                                        

                                                            
Note After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.

                                                        

                                                        
To access the OBM Login page and log on for the first time:

                                                        
    
                                                            
  1. 
                                                                
    Import the CA certificate to the browser's trusted root certificate store:
    
                                                                
      
                                                                    
    1. Make sure the web browser is configured to support TLS.
      2. 
                                                                    
    2. 
                                                                        
      Export the CA certificate from the OBM certificate inventory:
      
                                                                        
      
                                                                            
      <OBM_HOME>\bin\opr-cert-mgmt.bat ‑export "OBM Webserver CA Certificate" PEM "C:\ca_certificate.crt"
                                                                            
      
                                                                        
      
                                                                        
      
                                                                            
      /opt/HP/BSM/bin/opr-cert-mgmt.sh -export "OBM Webserver CA Certificate" PEM "/tmp/ca_certificate.crt"
                                                                            
      
                                                                        
      
                                                                        
      If applicable, export the intermediate CA certificate:
      
                                                                        
      
                                                                            
      <OBM_HOME>\bin\opr-cert-mgmt.bat ‑export "OBM Webserver Intermediate CA Certificate 0" PEM "C:\ca_intermediate_certificate.crt"
                                                                            
      
                                                                        
      
                                                                        
      
                                                                            
      /opt/HP/BSM/bin/opr-cert-mgmt.sh -export "OBM Webserver Intermediate CA Certificate 0" PEM "/tmp/ca_intermediate_certificate.crt"
                                                                            
      
                                                                        
      
                                                                    
      3. 
                                                                    
    3. 
                                                                        
      Import the CA certificate to the browser's certificate store:
      
                                                                        
        
                                                                            
      • 
                                                                                
        Internet Explorer:
        
                                                                                
        Double-click the CA certificate file (C:\ca_certificate.crt, for example) and click Install Certificate. Make sure to select the Trusted Root Certification Authorities certificate store.
        
                                                                            
        • 
                                                                            
      • 
                                                                                
        Mozilla Firefox:
        
                                                                                
        Navigate to Options > Privacy & Security > Certificates. Click View Certificates. In Authorities tab, click Import. In the Edit Certificate, select the This Certificate can identify websites check box. Click OK.
        
                                                                            
        • 
                                                                        
      
                                                                    
      4. 
                                                                    
    4. 
                                                                        
      Import the CA certificate to the truststore of the browser's JRE:
      
                                                                        
        
                                                                            
      1. 
                                                                                
        Open the Java Control Panel. Open the Security tab and click Manage Certificates.
        
                                                                            
        2. 
                                                                            
      2. 
                                                                                
        In the Certificates dialog box, select the certificate type Secure Site CA and click Import.
        
                                                                            
        3. 
                                                                        
      
                                                                    
      5. 
                                                                    
    5. 
                                                                        
      Optional. Disable TLS certificate revocation checks in the Java Control Panel. 
      
                                                                        
      The Java console displays the following warning for OBM-generated certificates when the certificate revocation check cannot be performed:
      security: Failing over to CRLs: Certificate does not specify OCSP responder
      security: Revocation Status Unknown
      
                                                                        
      To avoid the warning, generate OBM self-signed certificates with an OCSP responder URL or disable the TLS certificate revocation checks in the Java Control panel:
      
                                                                        
        
                                                                            
      1. 
                                                                                
        Open the Java Control Panel and then open the Advanced tab.
        
                                                                            
        2. 
                                                                            
      2. 
                                                                                
        In Perform TLS certificate revocation checks on, click Do not check (not recommended).
        
                                                                            
        3. 
                                                                        
      
                                                                        
      
                                                                            
      Caution This will disable the revocation check for all TLS connections that are established by Java-based applications on this system.
      
                                                                        
      
                                                                    
      6. 
                                                                
    
                                                            
    2. 
                                                            
  2. 
                                                                
    In the web browser's address bar, enter the following URL:
    
                                                                
    http(s)://<FullyQualifiedDomainName>/obm
    
                                                                
    
                                                                    
    <FullyQualifiedDomainName> is the FQDN of the OBM server.
    
                                                                
    
                                                                
    
                                                                    
    
                                                                        
    <FullyQualifiedDomainName> is the FQDN of the OBM server. If there are multiple servers, or if OBM is deployed in a distributed architecture, specify the gateway server URL.
    
                                                                    
    
                                                                    
    
                                                                        
    <FullyQualifiedDomainName> is the FQDN of the OBM server. If there are multiple servers, or if OBM is deployed in a distributed architecture, specify the load balancer or gateway server URL.
    
                                                                    
    
                                                                
    
                                                            
    3. 
                                                            
  3. 
                                                                
    Enter the default administrator user name (admin) and the password specified in the configuration wizard, and then click Log In. After logging in, the user name appears at the top right.
    
                                                            
    4. 
                                                            
  4. 
                                                                
    Recommended. Create additional administrative users to enable OBM administrators to access the system. For details on creating users in the OBM system, see the Users, Groups, and Roles.
    
                                                            
    5. 
                                                        

                                                        

                                                            
Note  

                                                            
    
                                                                
  • For the logon troubleshooting information, see Troubleshooting and Limitations.
    • 
                                                                
  • By default, single sign-on (SSO) logon is disabled. We recommend to use the default setting if no integrations are required for your installation. For details on this as well as other logon authentication strategies, see Authentication Management.
    • 
                                                            

                                                        

                                                        
When you complete your session, we recommend that you log off from the website to prevent unauthorized entry. To log off from OBM, select Logout from the user menu ().

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Log on to OBM

                                                        

                                                            
You can log on to OBM from a supported web browser on a client system by using the Login page. 

                                                            

                                                                
Note After upgrade, make sure to clear all proxies and web browser cache before accessing the OBM UI.

                                                            

                                                            
To access the OBM Login page and log on for the first time:

                                                            
    
                                                                
  1. 
                                                                    
    Import the CA certificate to the browser's trusted root certificate store:
    
                                                                    
      
                                                                        
    1. Make sure the web browser is configured to support TLS.
      2. 
                                                                        
    2. 
                                                                            
      Export the CA certificate from the OBM certificate inventory:
      
                                                                            
      
                                                                                
      <OBM_HOME>\bin\opr-cert-mgmt.bat ‑export "OBM Webserver CA Certificate" PEM "C:\ca_certificate.crt"
                                                                                
      
                                                                            
      
                                                                            
      
                                                                                
      /opt/HP/BSM/bin/opr-cert-mgmt.sh -export "OBM Webserver CA Certificate" PEM "/tmp/ca_certificate.crt"
                                                                                
      
                                                                            
      
                                                                            
      If applicable, export the intermediate CA certificate:
      
                                                                            
      
                                                                                
      <OBM_HOME>\bin\opr-cert-mgmt.bat ‑export "OBM Webserver Intermediate CA Certificate 0" PEM "C:\ca_intermediate_certificate.crt"
                                                                                
      
                                                                            
      
                                                                            
      
                                                                                
      /opt/HP/BSM/bin/opr-cert-mgmt.sh -export "OBM Webserver Intermediate CA Certificate 0" PEM "/tmp/ca_intermediate_certificate.crt"
                                                                                
      
                                                                            
      
                                                                        
      3. 
                                                                        
    3. 
                                                                            
      Import the CA certificate to the browser's certificate store:
      
                                                                            
        
                                                                                
      • 
                                                                                    
        Internet Explorer:
        
                                                                                    
        Double-click the CA certificate file (C:\ca_certificate.crt, for example) and click Install Certificate. Make sure to select the Trusted Root Certification Authorities certificate store.
        
                                                                                
        • 
                                                                                
      • 
                                                                                    
        Mozilla Firefox:
        
                                                                                    
        Navigate to Options > Privacy & Security > Certificates. Click View Certificates. In Authorities tab, click Import. In the Edit Certificate, select the This Certificate can identify websites check box. Click OK.
        
                                                                                
        • 
                                                                            
      
                                                                        
      4. 
                                                                        
    4. 
                                                                            
      Import the CA certificate to the truststore of the browser's JRE:
      
                                                                            
        
                                                                                
      1. 
                                                                                    
        Open the Java Control Panel. Open the Security tab and click Manage Certificates.
        
                                                                                
        2. 
                                                                                
      2. 
                                                                                    
        In the Certificates dialog box, select the certificate type Secure Site CA and click Import.
        
                                                                                
        3. 
                                                                            
      
                                                                        
      5. 
                                                                        
    5. 
                                                                            
      Optional. Disable TLS certificate revocation checks in the Java Control Panel. 
      
                                                                            
      The Java console displays the following warning for OBM-generated certificates when the certificate revocation check cannot be performed:
      security: Failing over to CRLs: Certificate does not specify OCSP responder
      security: Revocation Status Unknown
      
                                                                            
      To avoid the warning, generate OBM self-signed certificates with an OCSP responder URL or disable the TLS certificate revocation checks in the Java Control panel:
      
                                                                            
        
                                                                                
      1. 
                                                                                    
        Open the Java Control Panel and then open the Advanced tab.
        
                                                                                
        2. 
                                                                                
      2. 
                                                                                    
        In Perform TLS certificate revocation checks on, click Do not check (not recommended).
        
                                                                                
        3. 
                                                                            
      
                                                                            
      
                                                                                
      Caution This will disable the revocation check for all TLS connections that are established by Java-based applications on this system.
      
                                                                            
      
                                                                        
      6. 
                                                                    
    
                                                                
    2. 
                                                                
  2. 
                                                                    
    In the web browser's address bar, enter the following URL:
    
                                                                    
    http(s)://<FullyQualifiedDomainName>/obm
    
                                                                    
    
                                                                        
    <FullyQualifiedDomainName> is the FQDN of the OBM server.
    
                                                                    
    
                                                                    
    
                                                                        
    
                                                                            
    <FullyQualifiedDomainName> is the FQDN of the OBM server. If there are multiple servers, or if OBM is deployed in a distributed architecture, specify the gateway server URL.
    
                                                                        
    
                                                                        
    
                                                                            
    <FullyQualifiedDomainName> is the FQDN of the OBM server. If there are multiple servers, or if OBM is deployed in a distributed architecture, specify the load balancer or gateway server URL.
    
                                                                        
    
                                                                    
    
                                                                
    3. 
                                                                
  3. 
                                                                    
    Enter the default administrator user name (admin) and the password specified in the configuration wizard, and then click Log In. After logging in, the user name appears at the top right.
    
                                                                
    4. 
                                                                
  4. 
                                                                    
    Recommended. Create additional administrative users to enable OBM administrators to access the system. For details on creating users in the OBM system, see the Users, Groups, and Roles.
    
                                                                
    5. 
                                                            

                                                            

                                                                
Note  

                                                                
    
                                                                    
  • For the logon troubleshooting information, see Troubleshooting and Limitations.
    • 
                                                                    
  • By default, single sign-on (SSO) logon is disabled. We recommend to use the default setting if no integrations are required for your installation. For details on this as well as other logon authentication strategies, see Authentication Management.
    • 
                                                                

                                                            

                                                            
When you complete your session, we recommend that you log off from the website to prevent unauthorized entry. To log off from OBM, select Logout from the user menu ().

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

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

                                                            

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

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
 Optional. Update your Data Flow Probe

                                                        

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

                                                            

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

                                                                
    
                                                                    
  • Secure the keystore certificates. For details, see Enable mutual (two-way) authentication.
    • 
                                                                    
  • Back up <DFP_install_folder>/conf/DataFlowProbe.properties as the file contains customizations that must be reapplied after the DFP update.
    • 
                                                                

                                                            

                                                        

                                                    

                                                

                                                

                                                    

                                                        

                                                            
Restore certificates of the integrated products

                                                            

                                                                
If you backed up certificates of the BSM OBM-integrated products prior to starting the upgradeupdate process, you must restore them to the appropriate OBM host system at this point. To do so, perform the following:

                                                                
    
                                                                    
  • 
                                                                        
    For integrated data providers, such as  Network Node Manager i, restore the certificates from the corresponding backup location to the following directory:
    
                                                                        
    <GatewayServerInstallationDirectory>/\ucmdb\conf/\security
                                                                        
    
                                                                        
    <GatewayServerInstallationDirectory>/\JRE/\lib/\security/\cacerts (file)
    
                                                                    
    • 
                                                                    
  • 
                                                                        
    For the integrated  Data Flow Probe (DFP), restore the certificates from the corresponding backup location to the following directory:
    
                                                                        
    <DataFlowProbeInstallationDirectory>/\conf/\security
                                                                        
    
                                                                        
    For more information, see the Data Flow Probe Install.
    
                                                                    
    • 
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Optional. Transfer event data to staging OBM

                                                        

                                                            

                                                                
Note Skip this step if you selected Enable APM Integration in the upgrade/configuration wizard and followed the instructions in the OBM Integrate sectionOBM Integrate section to complete the APM integration steps including event integration.
If you did not enable the APM integration, follow this step to  establish event integration.

                                                            

                                                            
To transfer event data to the staging OBM servers:

                                                            
    
                                                                
  1. 
                                                                    
    Verify the trust relationship between production OBM and staging OBM BSM and OBMthe previous and the new OBM environment, which is established automatically by the upgrade/configuration wizard, as follows:
    
                                                                    
      
                                                                        
    • 
                                                                            
      Run the following command on OBM staging gateway serveron single server:
      
                                                                            
      
                                                                                
      %OvInstallDir%\bin\win64\bbcutil -ping https://<OBMServerFQDN>/com.hp.ov.opc.msgr
                                                                                
      
                                                                            
      
                                                                            
      
                                                                                
      /opt/OV/bin/bbcutil -ping https://<OBMServerFQDN>/com.hp.ov.opc.msgr
                                                                                
      
                                                                            
      
                                                                            
      where, OBMServer is OBMProductionGatewayServer for Side-by-Side upgrade.
      
                                                                            
      
                                                                                
      
                                                                                    
      where, OBMServer is OBMProductionPrimaryServer for Side-by-Side upgrade > Single-server HA.
      
                                                                                
      
                                                                            
      
                                                                        
      • 
                                                                        
    • 
                                                                            
      Run the following command on OBM production gateway serveron single server:
      
                                                                            
      
                                                                                
      %OvInstallDir%\bin\win64\bbcutil -ping https://<OBMServerFQDN>/com.hp.ov.opc.msgr
                                                                                
      
                                                                            
      
                                                                            
      
                                                                                
      /opt/OV/bin/bbcutil -ping https://<OBMServerFQDN>/com.hp.ov.opc.msgr
                                                                                
      
                                                                            
      
                                                                            
      
                                                                                
      where, OBMServer is OBMStagingGatewayServer for Side-by-Side upgrade.
      
                                                                            
      
                                                                            
      
                                                                                
      
                                                                                    
      where, OBMServer is OBMPrimaryStagingServer for Side-by-Side upgrade > Single-server HA.
      
                                                                                
      
                                                                            
      
                                                                        
      • 
                                                                    
    
                                                                    
    If the command fails, check for any firewalls.
    
                                                                    
    
                                                                        
    Establish the trust relationship manually as follows:
    
                                                                        
      
                                                                            
    • 
                                                                                
      In the OBM 2020.10 environment, run the following command on a gateway server: 
      
                                                                                
      
                                                                                    
      <OBM_HOME>\opr\bin\BBCTrustServer.bat <OBMServerFQDN> -o
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      /opt/HP/BSM/opr/bin/BBCTrustServer.sh <OBMServerFQDN> -o
                                                                                    
      
                                                                                
      
                                                                                
      
                                                                                    
      where, OBMServer is OBMgatewayServer for Side-by-Side upgrade.
      
                                                                                
      
                                                                                
      
                                                                                    
      
                                                                                        
      where, OBMServer is OBMPrimaryStagingServer for Side-by-Side upgrade > Single-server HA.
      
                                                                                    
      
                                                                                
      
                                                                            
      • 
                                                                        
    
                                                                    
    
                                                                
    2. 
                                                                
  2. 
                                                                    
    In the production OBM consoleBSM console, locate the FQDN from Admin > Platform > Setup and Maintenance > Infrastructure Settings > Foundations > Platform Administration > Default Virtual Gateway Server for Data Collectors URLAdministration > Setup and Maintenance > Infrastructure Settings > Platform Administration - Host Configuration > Default Virtual Gateway Server for Data Collectors URL and copy the FQDN to your clipboard or a temporary location.
    
                                                                
    3. 
                                                                
  3. 
                                                                    
    In the new OBM staging environment, create a new connected server that refers to the current production server:
    
                                                                    
      
                                                                        
    1. 
                                                                            
      Go to Administration > Setup and Maintenance > Connected Servers.
      
                                                                        
      2. 
                                                                        
    2. 
                                                                            
      In the INTRODUCTION TO CONNECTED SERVERS > Operations Bridge Manager pane, click
New. 
      
                                                                        
      3. 
                                                                        
    3. 
                                                                            
      In the General section, do the following:
      
                                                                            
        
                                                                                
      1. 
                                                                                    
        In Display Label section, define a name that identifies the connection to the production OBM server.
        
                                                                                
        2. 
                                                                                
      2. 
                                                                                    
        Change the automatically generated Identifier. The internal name must be unique.
        
                                                                                
        3. 
                                                                                
      3. 
                                                                                    
        Optional. Provide a connection description.
        
                                                                                
        4. 
                                                                                
      4. In the Server Properties section, enter the FQDN of the Default Virtual Gateway Server for Data Collectors URL (saved in step 2) in the Fully Qualified Domain Name field. Remove to the port number and the protocol details from the URL.
        5. 
                                                                                
      5. 
                                                                                    
        In Test Connection, click RUN TEST to confirm a successful connection.
        
                                                                                
        6. 
                                                                                
      6. 
                                                                                    
        Click CREATE.
        
                                                                                
        7. 
                                                                            
      
                                                                        
      4. 
                                                                    
    
                                                                
    4. 
                                                                
  4. 
                                                                    
    On the new OBM staging server, enable the processing of incoming events as follows:
    
                                                                    
      
                                                                        
    1. 
                                                                            
      Go to Administration > Setup and Maintenance > Infrastructure Settings.
      
                                                                        
      2. 
                                                                        
    2. 
                                                                            
      Locate the Operations Management – Event Pipeline Receiver Settings settings group and make sure Disable Receiving of Events is set to false.
      
                                                                        
      3. 
                                                                    
    
                                                                
    5. 
                                                                
  5. 
                                                                    
    Synchronize the events and changes from the BSMprevious OMi environment:
    
                                                                    
      
                                                                        
    1. 
                                                                            
      Allow the events and changes to synchronize. You can monitor that the forwarding queue is being drained and that it is not falling behind and continuously growing. Run the following command on a data processing server in the BSMprevious OMi production environment staging environment:
      
                                                                            
      
                                                                                
      <BSM_HOME>\opr\bin\opr-event-sync.bat -monitor
                                                                                
      
                                                                            
      
                                                                            
      
                                                                                
      /opt/HP/BSM/opr/bin/opr-event-sync.sh -monitor
                                                                                
      
                                                                            
      
                                                                        
      2. 
                                                                        
    2. 
                                                                            
      
                                                                                
      When the buffers are empty, press Ctrl+C to stop the monitor.
      
                                                                            
      
                                                                            
      
                                                                                
      When the buffers are empty,  press Ctrl-C to stop the monitor.
      
                                                                            
      
                                                                        
      3. 
                                                                    
    
                                                                
    6. 
                                                            

                                                            
The new OBM server is configured for a staging upgrade, which prevents notifications and alerts being executed on the staging OBM in order to prevent duplicating notifications and alerts.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Optional. Review the log files and enable IPv6Review the log files, enable IPv6, and configure Automatic FailoverReview the log files and console output, and enable IPv6

                                                    

                                                        
ClosedCheck the installation log files
                                                            

                                                                
The main installation log file and the additional installation log files for individual packages are created  in the following directory on each OBM  serverOBM host system:

                                                                

                                                                    
%TEMP%\..\MicroFocusOvInstaller\HPOMi_<BuildVersion>

                                                                    
In the above instance, %TEMP% is a user environment variable.

                                                                

                                                                

                                                                    
/tmp/MicroFocusOvInstaller/HPOMi_<BuildVersion>
                                                                    

                                                                

                                                                
File names are as follows:

                                                                
    
                                                                    
  • 
                                                                        
    Main installation log file:
    
                                                                        
    HPOMi_<BuildVersion>_<DateTime>_ MicroFocusOvInstallerLog.[html|txt]
                                                                        
    
                                                                        
    (for example, HPOMi_xx.xxx_MicroFocusOvInstallerLog.txt).
    
                                                                    
    • 
                                                                    
  • 
                                                                        
    Installation log files for individual packages:
    
                                                                        
    Package_<PackageType>_<PackageName>_install.log
                                                                        
    
                                                                        
    (for example, Package_msi_HPOMiDoc_install.log).
    
                                                                    
    • 
                                                                

                                                                
The log files in /tmp are deleted as per configuration defined in /usr/lib/tmpfiles.d/tmp.conf, which is by default 10 days. You can modify the file to retain the log files for a required period of time. For example, to retain the log files for 30 days, modify the below entry in the file as follows: 

                                                                
v /tmp 1777 root root 30d 

                                                            

                                                        

                                                        
ClosedCheck the startup log files
                                                            

                                                                
You can find the startup log file on  all the servers at the following location: 

                                                                

                                                                    
/opt/HP/BSM/log/supervisor/nanny_all.log
                                                                    

                                                                    
/opt/HP/BSM/ucmdb/runtime/log/startup.log
                                                                    

                                                                

                                                                

                                                                    
<OBM_HOME>\log\supervisor\nanny_all.log
                                                                    

                                                                    
<OBM_HOME>\ucmdb\runtime\log\startup.log
                                                                    

                                                                

                                                            

                                                        

                                                        
ClosedCheck the post-installation log file
                                                            

                                                                
You can find the post-installation log file on  all the servers at the following location: 

                                                                

                                                                    
<OBM_HOME>\log\configserver\postinstall_all.log
                                                                    

                                                                

                                                                

                                                                    
/opt/HP/BSM/log/configserver/postinstall_all.log
                                                                    

                                                                

                                                            

                                                        

                                                        
ClosedCheck the configuration log file
                                                            

                                                                
You can find the configuration log file on  all the servers at the following location: 

                                                                

                                                                    
<OBM_HOME>\log\configserver\configserver_all.log
                                                                    

                                                                

                                                                

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

                                                                

                                                            

                                                        

                                                        

                                                            
ClosedCheck the certificates
                                                                

                                                                    
During the configuration of OBM, the gateway server sends a certificate request to the data processing server to be granted after startup. To check whether the gateway and data processing servers trust each other, run the following command on each server:

                                                                    

                                                                        
%ovinstalldir%/bin/win64/bbcutil -ping https://<GatewayOrDataProcessingServer>
                                                                        

                                                                    

                                                                    

                                                                        
/opt/OV/bin/bbcutil -ping https://<GatewayOrDataProcessingServer>
                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            
ClosedChange passwords
                                                                

                                                                    
The express configuration sets identical password for the OBM admin user, the embedded PostgreSQL database user, and the JMX console. To change the password, do the following:

                                                                    
    
                                                                        
  • OBM admin user password. Change the password in the OBM Users, Groups and Roles UI. For details, see Users, Groups, and Roles.
    • 
                                                                        
  • Database user password. For information on resetting the password of the postgres user in the embedded PostgreSQL database, see PostgreSQL Deployment. Restart the configuration wizard and specify the new password in the Database Settings page. 
    • 
                                                                        
  • 
                                                                            
    JMX console password. Restart the configuration wizard and specify a new password in the Login Settings page. For details, see JMX Console.
    
                                                                        
    • 
                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            

                                                                
ClosedConfigure Automatic Failover
                                                                    

                                                                        
To make sure that OBM functions properly in the event of a primary data processing server failure, the backup data processing server can take over.

                                                                        
To ensure that services are automatically reassigned to the backup DPS, you must define the backup DPS in the JMX console and enable automatic failover in the Infrastructure Settings. For details, see High Availability for the Data Processing Server.

                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            

                                                                

                                                                    
ClosedSilent upgrade console output
                                                                        

                                                                            
The actual console output may vary based on your deployment. 

                                                                            
Pre-migration : 

                                                                            

                                                                                
Note The console output is applicable for active DPS and active single server. It is not applicable for gateway servers and inactive(backup) DPS.

                                                                            

                                                                            
The pre-upgrade tool disable the incoming events. It observes the event queue and wait until event queue is empty. It runs the forwarding info cleanup, where the tool waits until all event sync buffer entries are processed. If you have  archive=true mentioned while calling upgrade script, all the closed events are archived.
INFO: (./upgrade.sh) Running PreMigration Tool to prepare for Upgrade 
INFO: (./upgrade.sh) Starting Pre Upgrade tool. Logs present in /var/opt/OV/log/opr-upgradeBackup.log 
INFO: (./upgrade.sh) PreUpgradeTool completed  


                                                                            
Backup:

                                                                            
During backup, the upgrade process will back up the DB(for embedded Prostgres only) and configuration. The files  are zipped and placed at <OVDATADIR>/backup. The list of configuration files that are backed up is mentioned in <OBM_Media_location>/Update/preUpdateBackup.txt.
INFO: (./upgrade.sh) Backing up config data and DB to /var/opt/OV/backup before upgrade. Please be patient...
INFO: Backup logs present in /var/opt/OV/log/opr-upgradeBackup.log
INFO: (./upgrade.sh) Found backup files in /var/opt/OV/backup/

                                                                            
Uninstallation of older versions:

                                                                            
During uninstallation, the upgrade process first removes the currently installed version’s patches, followed by the removal of the core software.
INFO: (./upgrade.sh) Stopping OA...
INFO: (./upgrade.sh) Stopping OBM for Uninstallation...
INFO: (./upgrade.sh) Skipping installation-wizard.jar hotfix installation for source version 1071
INFO: (./upgrade.sh) No OMi patches installed...
INFO: (./upgrade.sh) Uninstalling OMi... Please check the log file in temp location for uninstallation details
INFO: (./upgrade.sh) Uninstallation done
										

                                                                            
Installation of newer version:

                                                                            
At this stage, installation of the new version begins as soon as uninstallation of the older version is completed. Install logs are generally written into  HPOMi_11.xx_MicroFocusOvInstaller.txt. As soon as the installation of the product is successful, the configuration takes place in the background. Verify  configserver_all.log to ensure the upgrade is completed.
INFO: (./upgrade.sh) Starting installation of OBM. Check log file HPOMi_11.xx_MicroFocusOvInstaller.txt in temp location for details of Installation process
INFO: (./upgrade.sh) Once Installation process finishes, Upgrade will take place in the background. Check log files in /opt/HP/BSM/log/configserver/ for details
INFO: (./upgrade.sh) Upgrade has finished, please check above mentioned log files to ensure it completed successfully

                                                                        

                                                                    

                                                                

                                                                

                                                                    
ClosedSilent upgrade console output
                                                                        

                                                                            
The actual console output may vary based on your deployment. 

                                                                            
Pre-migration : 

                                                                            

                                                                                
Note The console output is applicable for active DPS and active single server. It is not applicable for gateway servers and inactive(backup) DPS.

                                                                            

                                                                            
The pre-upgrade tool disable the incoming events. It observes the event queue and wait until event queue is empty. It runs the forwarding info cleanup, where the tool waits until all event sync buffer entries are processed. If you have  archive=true mentioned while calling upgrade script, all the closed events are archived.
INFO: Running PreMigration Tool to prepare for Upgrade
INFO: Starting Pre Upgrade tool. Logs present in <OVDATADIR>/log/opr-upgradeBackup.log
INFO: PreUpgradeTool completed

                                                                            
Backup:

                                                                            
During backup, the upgrade process will back up the DB(for embedded Prostgres only) and configuration. The files  are zipped and placed at <OVDATADIR>/backup. The list of configuration files that are backed up is mentioned in <OBM_Media_location>/Update/preUpdateBackup.txt.
INFO: Backing up config data to C:\ProgramData\HP\HP BTO Software\backup\OMi1080 before upgrade. Please be patient...
INFO: Backup logs present in C:\ProgramData\HP\HP BTO Software\log\opr-upgradeBackup.log
INFO: Found backup files in C:\ProgramData\HP\HP BTO Software\backup\

                                                                            
Uninstallation of older versions:

                                                                            
During uninstallation, the upgrade process first removes the currently installed version’s patches, followed by the removal of the core software.
INFO: Stopping OA
INFO: Stopping OMi/OBM for Uninstallation
INFO: Skipping installation-wizard.jar installation for OMi/OBM source version 1080
INFO: Starting uninstallation. Please be patient and do not interrupt as it will take some time especially if your system does not have internet access which is used for certificate validity checks.
INFO: Uninstalling OMi/OBM patches...
INFO: Uninstalling HPOMi1080IP120...
INFO: Reinstalling installation-wizard.jar hotfix
INFO: Skipping installation-wizard.jar installation for OMi/OBM source version 1080
INFO: Uninstalling OMi... Please check the log file in %temp% for uninstallation details
INFO: Uninstallation completed
INFO: Cleaning up installed policies succeeded...
INFO: Uninstallation done

                                                                            
Installation of newer version:

                                                                            
At this stage, installation of the new version begins as soon as uninstallation of the older version is completed. Install logs are generally written into  HPOMi_11.xx_MicroFocusOvInstaller.txt. As soon as the installation of the product is successful, the configuration takes place in the background. Verify  configserver_all.log to ensure the upgrade is completed.
INFO: Created ovinstallparams.ini file for DPS in temp:C:\Users\Administrator\AppData\Local\Temp
Copied the ovinstallparams.ini file to %temp%:C:\Users\ADMINI~1\AppData\Local\Temp\1
INFO: Starting installation of OBM. Check log file HPOMi_11.xx_MicroFocusOvInstaller.txt in temp location for details of Installation process
INFO: Once Installation process finishes, Upgrade will take place in the background. Check log files in <TOPAZ_HOME>\log\configserver\ for details
Upgrade has finished, please check above mentioned log files to ensure it completed successfully


                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            

                                                                

                                                                    
ClosedSilent update console output
                                                                        

                                                                            
Backup:

                                                                            
During backup, the upgrade process will back up the DB(for embedded Prostgres only) and configuration. The files  are zipped and placed at <OVDATADIR>/backup. The list of configuration files that are backed up is mentioned in <OBM_Media_location>/Update/preUpdateBackup.txt.
INFO: (./upgrade.sh) Backing up config data and DB to /var/opt/OV/backup before upgrade. Please be patient...
INFO: Backup logs present in /var/opt/OV/log/opr-upgradeBackup.log
INFO: (./upgrade.sh) Found backup files in /var/opt/OV/backup/

                                                                            
Uninstallation of older versions:

                                                                            
During uninstallation, the upgrade process first removes the currently installed version’s patches, followed by the removal of the core software.
INFO: (./upgrade.sh) Stopping OA...
INFO: (./upgrade.sh) Stopping OBM for Uninstallation...
INFO: (./upgrade.sh) Skipping installation-wizard.jar hotfix installation for source version 1071
INFO: (./upgrade.sh) No OMi patches installed...
INFO: (./upgrade.sh) Uninstalling OMi... Please check the log file in temp location for uninstallation details
INFO: (./upgrade.sh) Uninstallation done
										

                                                                            
Installation of newer version:

                                                                            
At this stage, installation of the new version begins as soon as uninstallation of the older version is completed. Install logs are generally written into  HPOMi_11.xx_MicroFocusOvInstaller.txt. As soon as the installation of the product is successful, the configuration takes place in the background. Verify  configserver_all.log to ensure the upgrade is completed.
INFO: (./upgrade.sh) Starting installation of OBM. Check log file HPOMi_11.xx_MicroFocusOvInstaller.txt in temp location for details of Installation process
INFO: (./upgrade.sh) Once Installation process finishes, Upgrade will take place in the background. Check log files in /opt/HP/BSM/log/configserver/ for details
INFO: (./upgrade.sh) Upgrade has finished, please check above mentioned log files to ensure it completed successfully

                                                                        

                                                                    

                                                                

                                                                

                                                                    
ClosedSilent update console output
                                                                        

                                                                            
Backup:

                                                                            
During backup, the upgrade process will back up the DB(for embedded Prostgres only) and configuration. The files  are zipped and placed at <OVDATADIR>/backup. The list of configuration files that are backed up is mentioned in <OBM_Media_location>/Update/preUpdateBackup.txt.
INFO: Backing up config data to C:\ProgramData\HP\HP BTO Software\backup\OMi1100 before upgrade. Please be patient...
INFO: Backup logs present in C:\ProgramData\HP\HP BTO Software\log\opr-upgradeBackup.log
INFO: Found backup files in C:\ProgramData\HP\HP BTO Software\backup\

                                                                            
Uninstallation of older versions:

                                                                            
During uninstallation, the upgrade process first removes the currently installed version’s patches, followed by the removal of the core software.
INFO: Stopping OA
INFO: Stopping OMi/OBM for Uninstallation
INFO: Skipping installation-wizard.jar installation for OMi/OBM source version 1100
INFO: Starting uninstallation. Please be patient and do not interrupt as it will take some time especially if your system does not have internet access which is used for certificate validity checks.
INFO: Uninstalling OMi... Please check the log file in %temp% for uninstallation details
INFO: Uninstallation completed
INFO: Cleaning up installed policies succeeded...
INFO: Uninstallation done - Starting installation of OBM

                                                                            
Installation of newer version:

                                                                            
At this stage, installation of the new version begins as soon as uninstallation of the older version is completed. Install logs are generally written into  HPOMi_11.xx_MicroFocusOvInstaller.txt. As soon as the installation of the product is successful, the configuration takes place in the background. Verify  configserver_all.log to ensure the upgrade is completed.
INFO: Starting installation of OBM. Check log file HPOMi_11.xx_MicroFocusOvInstaller.txt in temp location for details of Installation process
INFO: Once Installation process finishes, Upgrade will take place in the background. Check log files in <TOPAZ_HOME>\log\configserver\ for details
Install wizard launched, After the wizard completes please check above mentioned log files to ensure upgrade completed successfully

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                        
ClosedEnable OBM to use IPv6
                                                            

                                                                

                                                                    
Note Completing the procedure in this section is mandatory on host systems with only the IPv6 protocol stack and optional on host systems with both IPv4 and IPv6 protocol stacks configured.

                                                                

                                                                
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, enable the use of IPv6 manually as follows:

                                                                
    
                                                                    
  1. 
                                                                        
    Make sure the local hosts file contains the following line:
    
                                                                        
    127.0.0.1 localhost
                                                                        
    
                                                                    
    2. 
                                                                    
  2. 
                                                                        
    Run the following commands in sequence:
    
                                                                        
    
                                                                            
    /opt/OV/bin/ovconfchg -ns sec.cm.server -set IsIPV6Enabled TRUE
                                                                            
    
                                                                            
    /opt/OV/bin/ovc -kill
                                                                            
    
                                                                            
    /opt/OV/bin/ovc –start
                                                                                
    
                                                                            
    
                                                                        
    
                                                                        
    
                                                                            
    %ovdatadir%\bin\ovconfchg -ns sec.cm.server -set IsIPV6Enabled TRUE
                                                                            
    
                                                                            
    %ovdatadir%\bin\ovc -kill
                                                                            
    
                                                                            
    %ovdatadir%\bin\ovc –start
                                                                            
    
                                                                        
    
                                                                    
    3. 
                                                                    
  3. If OBM uses IPv6 on a host system that has only the IPv6 protocol stack configured, to enable its communication with non-OBM host systems that have both IP protocol stacks configured, configure your DNS server so that it resolves host names only to IPv6 addresses.
    4. 
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Verify the upgrade log files

                                                        

                                                            
When you start OBM on primary DPSsingle-server for the first time, it takes a long  time. You can review the startup.log, mam.packaging.log and wrapper.log files and monitor the progress from the following locations:

                                                            
<OBM_HOME>\ucmdb\runtime\log\startup.log
<OBM_HOME>\ucmdb\runtime\log\wrapper.log
<OBM_HOME>\log\supervisor\nanny_all.log
<OBM_HOME>\ucmdb\runtime\log\mam.packaging.log

                                                            

                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
/opt/HP/BSM/ucmdb/runtime/log/wrapper.log
/opt/HP/BSM/log/supervisor/nanny_all.log
/opt/HP/BSM/ucmdb/runtime/log/mam.packaging.log

                                                            

                                                            

                                                                

                                                                    
The Embedded Postgres DB backup and restore takes a large amount of time without a progress bar. You can monitor the progress in the log files:

                                                                    
Backup

                                                                    

                                                                        
%ovdatadir%\log\opr-upgradeBackup.log
                                                                        

                                                                    

                                                                    

                                                                        
/var/opt/OV/log/opr-upgradeBackup.log
                                                                        

                                                                    

                                                                    
Restore

                                                                    

                                                                        
<OBM_HOME>\log\configserver\configserver_all.log
                                                                        

                                                                    

                                                                    

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

                                                                    

                                                                    
To verify DB backup and restore check all the steps are completed without any exception in configserver_all.log then upgrade is successful.

                                                                

                                                                

                                                                    

                                                                        
When you start OBM on staging server for the first time, it takes a long  time. You can review the startup.log, mam.packaging.log and wrapper.log files and monitor the progress from the following locations:

                                                                        
<OBM_HOME>\ucmdb\runtime\log\startup.log
<OBM_HOME>\ucmdb\runtime\log\wrapper.log
<OBM_HOME>\log\supervisor\nanny_all.log
<OBM_HOME>\ucmdb\runtime\log\mam.packaging.log

                                                                        

                                                                        
/opt/HP/BSM/ucmdb/runtime/log/startup.log
/opt/HP/BSM/ucmdb/runtime/log/wrapper.log
/opt/HP/BSM/log/supervisor/nanny_all.log
/opt/HP/BSM/ucmdb/runtime/log/mam.packaging.log

                                                                        

                                                                    

                                                                

                                                                

                                                                    
ClosedEnable event reception on the OBM server
                                                                        

                                                                            
Enable incoming events to be received by the OBM deployment as follows:

                                                                            
    
                                                                                
  1. 
                                                                                    
    Log on to OBM.
    
                                                                                
    2. 
                                                                                
  2. 
                                                                                    
    Go to Administration > Setup and Maintenance > Infrastructure Settings.
    
                                                                                
    3. 
                                                                                
  3. 
                                                                                    
    Select Operations Management from the Applications drop-down list.
    
                                                                                
    4. 
                                                                                
  4. 
                                                                                    
    Locate the Operations Management – Event Pipeline Receiver Settings settings group and make sure Disable Receiving of Events is set to false.
    
                                                                                
    5. 
                                                                            

                                                                        

                                                                    

                                                                

                                                                
The upgrade log files and their locations on all the OBM servers are as follows: 

                                                                
    
                                                                    
  • 
                                                                        
    Upgrade log files with details on the complete upgrade flow:
    
                                                                        
    
                                                                            
    %ovdatadir%\log\opr-upgradeBackup.log
                                                                            
    
                                                                        
    
                                                                        
    
                                                                            
    <OBM_Home>\log\configserver\configserver_all.log
                                                                            
    
                                                                        
    
                                                                        
    
                                                                            
    /var/opt/OV/log/opr-upgradeBackup.log
                                                                            
    
                                                                        
    
                                                                        
    
                                                                            
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                            
    
                                                                        
    
                                                                    
    • 
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Verify the upgrade log files

                                                        

                                                            
When you start OBM on primary DPSsingle-server for the first time, it takes a long  time. You can review the startup.log, mam.packaging.log and wrapper.log files and monitor the progress from the following locations:

                                                            
<OBM_HOME>\ucmdb\runtime\log\startup.log
<OBM_HOME>\ucmdb\runtime\log\wrapper.log
<OBM_HOME>\log\supervisor\nanny_all.log
<OBM_HOME>\ucmdb\runtime\log\mam.packaging.log

                                                            

                                                            
/opt/HP/BSM/ucmdb/runtime/log/startup.log
/opt/HP/BSM/ucmdb/runtime/log/wrapper.log
/opt/HP/BSM/log/supervisor/nanny_all.log
/opt/HP/BSM/ucmdb/runtime/log/mam.packaging.log

                                                            

                                                            

                                                                

                                                                    
The Embedded Postgres DB backup and restore takes a large amount of time without a progress bar. You can monitor the progress in the log files:

                                                                    
Backup

                                                                    

                                                                        
%ovdatadir%\log\opr-upgradeBackup.log
                                                                        

                                                                    

                                                                    

                                                                        
/var/opt/OV/log/opr-upgradeBackup.log
                                                                        

                                                                    

                                                                    
Restore

                                                                    

                                                                        
<OBM_HOME>\log\configserver\configserver_all.log
                                                                        

                                                                    

                                                                    

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

                                                                    

                                                                    
To verify DB backup and restore check all the steps are completed without any exception in configserver_all.log then upgrade is successful.

                                                                

                                                                

                                                                    

                                                                        
When you start OBM on staging server for the first time, it takes a long  time. You can review the startup.log, mam.packaging.log and wrapper.log files and monitor the progress from the following locations:

                                                                        
<OBM_HOME>\ucmdb\runtime\log\startup.log
<OBM_HOME>\ucmdb\runtime\log\wrapper.log
<OBM_HOME>\log\supervisor\nanny_all.log
<OBM_HOME>\ucmdb\runtime\log\mam.packaging.log

                                                                        

                                                                        
/opt/HP/BSM/ucmdb/runtime/log/startup.log
/opt/HP/BSM/ucmdb/runtime/log/wrapper.log
/opt/HP/BSM/log/supervisor/nanny_all.log
/opt/HP/BSM/ucmdb/runtime/log/mam.packaging.log

                                                                        

                                                                    

                                                                

                                                                

                                                                    
ClosedEnable event reception on the OBM server
                                                                        

                                                                            
Enable incoming events to be received by the OBM deployment as follows:

                                                                            
    
                                                                                
  1. 
                                                                                    
    Log on to OBM.
    
                                                                                
    2. 
                                                                                
  2. 
                                                                                    
    Go to Administration > Setup and Maintenance > Infrastructure Settings.
    
                                                                                
    3. 
                                                                                
  3. 
                                                                                    
    Select Operations Management from the Applications drop-down list.
    
                                                                                
    4. 
                                                                                
  4. 
                                                                                    
    Locate the Operations Management – Event Pipeline Receiver Settings settings group and make sure Disable Receiving of Events is set to false.
    
                                                                                
    5. 
                                                                            

                                                                        

                                                                    

                                                                

                                                                
The upgrade log files and their locations on all the OBM servers are as follows: 

                                                                
    
                                                                    
  • 
                                                                        
    Upgrade log files with details on the complete upgrade flow:
    
                                                                        
    
                                                                            
    %ovdatadir%\log\opr-upgradeBackup.log
                                                                            
    
                                                                        
    
                                                                        
    
                                                                            
    <OBM_Home>\log\configserver\configserver_all.log
                                                                            
    
                                                                        
    
                                                                        
    
                                                                            
    /var/opt/OV/log/opr-upgradeBackup.log
                                                                            
    
                                                                        
    
                                                                        
    
                                                                            
    /opt/HP/BSM/log/configserver/configserver_all.log
                                                                            
    
                                                                        
    
                                                                    
    • 
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Optional. Re-apply event forwarding expiration setting

                                                    

                                                        

                                                            
The upgrade script set the Event Forwarding Expiration to 336 hours (14 days).  On the staging OBM, you can change the value to a different value as set on the original production OBM.  To reset the value, go to Administration > Setup and Maintenance > Infrastructure Settings > Operations Management - Event Synchronization Settings > Event Forwarding Expiration and set the required value.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Optional. Configure additional OBM servers

                                                            

                                                                
Once you have a functional OBM 2020.10 environment, you can configureupdate the secondary data processing server and additional gateway servers.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Optional. Configure additional OBM servers

                                                            

                                                                
Once you have a functional OBM 2020.10 environment, you can configureupdate the secondary data processing server and additional gateway servers.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        

                                                            
Configure HA on staging OBM 

                                                            

                                                                
To allow HAC services to be able to fail over between the primary DPS and the secondary DPS, you need to configure a backup server.  In side-by-side upgrade, since new hostnames are used, you need to apply this configuration in the OBM staging environment.

                                                                
For details, see High Availability for the Data Processing Server.

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Re-apply customizations

                                                        

                                                            
If you customized the web server configuration, or made other customizations specific to your needs, you may need to re-apply those customizations after the upgradeupdate. 

                                                            
For example, if you configured your system to not require certificates for data providers and CLIs, you must re-apply this customization after the upgradeupdate. 

                                                            
The CI context menus with Origin as Predefined(customized) and Custom are not upgraded. You must re-apply the customization after the upgradeupdate. 

                                                            
For information, see the OBM Administer section.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Re-apply customizations

                                                        

                                                            
If you customized the web server configuration, or made other customizations specific to your needs, you may need to re-apply those customizations after the upgradeupdate. 

                                                            
For example, if you configured your system to not require certificates for data providers and CLIs, you must re-apply this customization after the upgradeupdate. 

                                                            
The CI context menus with Origin as Predefined(customized) and Custom are not upgraded. You must re-apply the customization after the upgradeupdate. 

                                                            
For information, see the OBM Administer section.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Reapply parameter values to OBM Self Monitoring Auto-assignment Rule

                                                        

                                                            
When you upgradeupdate OBM to a newer version, the policy parameter values (for example, Email address to send notification for the JMS bus component) in OBM Self Monitoring Auto-assignment Rule are not preserved. You must therefore reapply the parameter values to this auto-assignment rule after the upgradeupdate is done. 

                                                            
For more information, see Management Pack for OBM Server Self-Monitoring. 

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Update data providers

                                                    

                                                        

                                                            
If you have a load balancer or reverse proxy, set it  to communicate with the new servers.

                                                            
If you do not have a load balancer or reverse proxy, you must configure each data provider individually to communicate with the new OBM gateway servers. For details, see the documentation of each data provider. Micro Focus recommends upgrading each data provider to the latest supported version.

                                                        

                                                        

                                                            
Update the existing integrations to connect to the staging OBM server.  No changes are needed if the staging OBM server uses the same load balancer as the production OBM server.

                                                            
However, if the staging OBM server does not use a load balancer or it uses a different load balancer from the production OBM, then update existing integrations to use the FQDN of the new load balancer or gateway server.

                                                            
For example, if a load balancer is not used, then run the following opr-agt command on the staging OBM gateway server to switch the agents to the staging OBM server:

                                                            
opr-agt -username admin -switch_manager -view_name "Hosts with HP Operations Agents"
                                                            

                                                            
For more details, see opr-agt CLI.

                                                        

                                                        
For more information on the integrations, see the Operations Bridge Manager (OBM) community pages of the ITOM Marketplace website.

                                                        
For details on supported integration versions, select Operations Bridge Manager from the product list in the following document:

                                                        
Support Matrices for Operations Center products
                                                        

                                                        

                                                            
ClosedUpdate  Operations Agent installations
                                                                

                                                                    

                                                                        

                                                                            
 Operations Agent starts sending events when it is able to communicate again with the upgraded OBM environment.

                                                                        

                                                                        

                                                                            
 Operations Agent must be reconfigured to communicate with the new OBM2020.10 environment by using the -switch_manager option of the opr-agt command-line utility.

                                                                            
For more information on switching  Operations Agent installations to another server, see the OBM Administration Guide (Administration Guide > Setup and Maintenance > Monitored Nodes > Connecting Operations Agents to OBM > Connecting Existing Operations Agent Installations) or the OBM Help.

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            
ClosedUpdate the Operations Manager server
                                                                

                                                                    

                                                                        

                                                                            
Restore original values of the OM event buffer. For more information, see Configure event buffering in OM.

                                                                        

                                                                        

                                                                            
    
                                                                                
  1. 
                                                                                    
    Restore original values of the OM event buffer. For more information, see Configure event buffering in OM.
    
                                                                                
    2. 
                                                                                
  2. 
                                                                                    
    Configure the OM forwarding policy.
    
                                                                                    
    Update the OM integration by specifying the OBM 2020.10 server in the OM forwarding policy, and—for OM for UNIX or Linux systems only—adding the OBM 2020.10 server as a forwarding target to the node bank.
    
                                                                                    
    ClosedConfigure the OM forwarding policy – Windows systems
                                                                                        
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      Start the OM console as follows:
      
                                                                                                    
      Start > Programs (or All Programs) > HP > HP Operations Manager
                                                                                                    
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      In the left pane of the OM console, select the following: 
      
                                                                                                    
      Policy management > Server policies grouped by type > Server policies > Server-based Flexible Management.
                                                                                                    
      
                                                                                                
      3. 
                                                                                                
    3. 
                                                                                                    
      In the right pane of the OM console, double-click the existing policy that you want to edit. The Server-based Flexible Management Editor dialog opens.
      
                                                                                                
      4. 
                                                                                                
    4. 
                                                                                                    
      Replace the existing message target server to point to the new OBM2020.10 gateway server (or reverse proxy or load balancer) as shown in the following example policy text:
      TIMETEMPLATES
# none
RESPMGRCONFIGS
   RESPMGRCONFIG DESCRIPTION "Forward all messages to OMi"
   SECONDARYMANAGERS
   ACTIONALLOWMANAGERS
   MSGTARGETRULES
      MSGTARGETRULE DESCRIPTION "Forward all messages rule"
         MSGTARGETRULECONDS
         MSGTARGETRULECOND DESCRIPTION "Forward all messages"
         MSGTARGETMANAGERS
            MSGTARGETMANAGER
            TIMETEMPLATE "$OPC_ALWAYS"
            OPCMGR IP 0.0.0.0 "<OBMFullyQualifiedDomainName>"

      
                                                                                                
      5. 
                                                                                                
    5. 
                                                                                                    
      Replace <OBMFullyQualifiedDomainName> in the text with the fully qualified domain name of the OBM2020.10 gateway server that receives OM messages (for example, gwsrv.example.com).
      
                                                                                                    
      In deployments that include a load balancer, a NAT device, or a reverse proxy, use the fully qualified domain name of the system used to access the gateway server (for example, virtualsrv.example.com).
      
                                                                                                
      6. 
                                                                                                
    6. 
                                                                                                    
      Click Check Syntax to check for syntax errors in the new policy text.
      
                                                                                                
      7. 
                                                                                                
    7. 
                                                                                                    
      After correcting any syntax errors, click Save and Close.
      
                                                                                                
      8. 
                                                                                                
    8. 
                                                                                                    
      Redeploy the server-based flexible management policy to the OM management server.
      
                                                                                                
      9. 
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                    
    ClosedConfigure the OM forwarding policy – UNIX and Linux systems
                                                                                        
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      Change to the following directory:
      
                                                                                                    
      cd /etc/opt/OV/share/conf/OpC/mgmt_sv/work_respmgrs
                                                                                                    
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      Edit the existing policy to which you want to add the OBM2020.10 system as a target:
      
                                                                                                    
      vi <PolicyFileName>
                                                                                                    
      
                                                                                                
      3. 
                                                                                                
    3. 
                                                                                                    
      Replace the existing message target server to point to the OBM2020.10 gateway server (or reverse proxy or load balancer) as shown in the following example policy text:
      TIMETEMPLATES
# none
RESPMGRCONFIGS
   RESPMGRCONFIG DESCRIPTION "Forward all messages to OMi"
   SECONDARYMANAGERS
   ACTIONALLOWMANAGERS
   MSGTARGETRULES
      MSGTARGETRULE DESCRIPTION "Forward all messages rule"
         MSGTARGETRULECONDS
         MSGTARGETRULECOND DESCRIPTION "Forward all messages"
         MSGTARGETMANAGERS
            MSGTARGETMANAGER
            TIMETEMPLATE "$OPC_ALWAYS"
            OPCMGR IP 0.0.0.0 "<OBMFullyQualifiedDomainName>"
         MSGTARGETMANAGERS
      
                                                                                                
      4. 
                                                                                                
    4. 
                                                                                                    
      Replace <OBMFullyQualifiedDomainName> in the text with the fully qualified domain name of the gateway server that receives OM messages (for example, gwsrv.example.com).
      
                                                                                                    
      In deployments that include a load balancer, a NAT device, or a reverse proxy, use the fully qualified domain name of the system used to access the gateway server (for example, virtualsrv.example.com).
      
                                                                                                
      5. 
                                                                                                
    5. 
                                                                                                    
      Enter the following command to check for syntax errors in the new policy text:
      
                                                                                                    
      /opt/OV/bin/OpC/opcmomchk -msgforw <PolicyFileName>
                                                                                                    
      
                                                                                                
      6. 
                                                                                                
    6. 
                                                                                                    
      After correcting any syntax errors, copy the policy to the respmgrs directory as follows:
      
                                                                                                    
      cp <PolicyFileName> /etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/

      
                                                                                                
      7. 
                                                                                                
    7. 
                                                                                                    
      Restart the server processes as follows:
      
                                                                                                    
      /opt/OV/bin/OpC/opcsv -stop
                                                                                                    
      
                                                                                                    
      /opt/OV/bin/OpC/opcsv -start
                                                                                                    
      
                                                                                                
      8. 
                                                                                                
    8. 
                                                                                                    
      Set up a Forwarding Target in the OM for UNIX Node Bank.
      
                                                                                                    
      
                                                                                                        
      Note Make sure that the SNMP agent is running before adding a managed node to the OM database.
      
                                                                                                    
      
                                                                                                    
      The forwarding target (OBM gateway server, reverse proxy, or load balancer) must be set up in the Node Bank as a managed node. You must add the managed node by using the opcnode command-line utility, for example:
      
                                                                                                    
      /opt/OV/bin/OpC/utils/opcnode -add_node node_name=<NodeName> net_type=NETWORK_IP mach_type=<MachineType> group_name=<GroupName> node_label=<NodeName>
                                                                                                    
      
                                                                                                    
      <MachineType> stands for the operating system of the OBM host system:
      
                                                                                                    
        
                                                                                                        
      • 
                                                                                                            
        Windows: MACH_BBC_WIN2K3_X64
        
                                                                                                        
        • 
                                                                                                        
      • 
                                                                                                            
        Linux: MACH_BBC_LX26RPM_X64
        
                                                                                                        
        • 
                                                                                                    
      
                                                                                                    
      <GroupName> stands for the operating system of the OM management server host system and must be one of the following:
      
                                                                                                    
        
                                                                                                        
      • 
                                                                                                            
        linux
        
                                                                                                        
        • 
                                                                                                        
      • 
                                                                                                            
        hp_ux
        
                                                                                                        
        • 
                                                                                                        
      • 
                                                                                                            
        solaris
        
                                                                                                        
        • 
                                                                                                    
      
                                                                                                
      9. 
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    3. 
                                                                                
  3. 
                                                                                    
    Replace the BSM servers as target servers for topology synchronization.
    
                                                                                    
    If topology synchronization was configured between BSM and OM, add fully qualified domain names (FQDNs) of the new OBM2020.10 servers to the list of target servers to forward discovery data to. Follow the applicable procedure below.
    
                                                                                    
    ClosedAdd a server to the list of target servers – Windows systems
                                                                                        
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      In the console tree, right-click Operations Manager, and then click Configure > Server. The Server Configuration dialog box opens.
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      In Namespaces, click Discovery Server. A list of values appears.
      
                                                                                                
      3. 
                                                                                                
    3. 
                                                                                                    
      Add FQDN of the OBM2020.10gateway serverload balancer to List of target servers to forward discovery data.
      
                                                                                                    
      
                                                                                                        
      In case of mulitple FQDNs, separate them with semicolons, for example:
      
                                                                                                        
      gwserver1.example.com;gwserver2.example.com
                                                                                                        
      
                                                                                                        
      If a target server uses a port other than port 383, append the port number to the corresponding FQDN, for example:
      
                                                                                                        
      gwserver1.example.com:65530;gwserver2.example.com:65531
                                                                                                        
      
                                                                                                    
      
                                                                                                    
      
                                                                                                        
      If the target server uses a port other than port 383, append the port number to its FQDN, for example:
      
                                                                                                        
      loadbalancer.example.com:65530
                                                                                                        
      
                                                                                                    
      
                                                                                                
      4. 
                                                                                                
    4. 
                                                                                                    
      Make sure that the value of Enable discovery WMI listener is true. This is the default value.
      
                                                                                                
      5. 
                                                                                                
    5. 
                                                                                                    
      Click OK to save your changes and close the Server Configuration dialog box.
      
                                                                                                
      6. 
                                                                                                
    6. 
                                                                                                    
      Restart the OvAutoDiscovery Server process for your changes to take effect.
      
                                                                                                
      7. 
                                                                                                
    7. 
                                                                                                    
      Start the initial synchronization of topology data:
      
                                                                                                    
        
                                                                                                        
      1. 
                                                                                                            
        In the console tree, select Tools > HP Operations Manager Tools.
        
                                                                                                        
        2. 
                                                                                                        
      2. 
                                                                                                            
        Right-click Synchronize Topology and select All Tasks > Launch Tool....
        
                                                                                                        
        3. 
                                                                                                    
      
                                                                                                    
      The startInitialSync.bat utility is started and begins to send all the topology data to the configured target servers.
      
                                                                                                
      8. 
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                    
    ClosedAdding a server to the list of target servers – UNIX and Linux systems
                                                                                        
    
                                                                                            
      
                                                                                                
    1. 
                                                                                                    
      Type the following command to enable topology synchronization:
      
                                                                                                    
      /opt/OV/contrib/OpC/enableToposync.sh -online -target <CommaSeparatedServerList>
                                                                                                    
      
                                                                                                    
      Replace <CommaSeparatedServerList> with FQDNs of the OBM2020.10gateway serversload balancer. In case of multiple FQDNs, separate them with commas, for example:
      
                                                                                                    
      
                                                                                                        
      gwserver1.example.com,gwserver2.example.com
                                                                                                        
      
                                                                                                        
      If a target server uses a port other than port 383, append the port number to the corresponding FQDN, for example:
      
                                                                                                        
      gwserver1.example.com:65530,gwserver2.example.com:65531
                                                                                                        
      
                                                                                                    
      
                                                                                                    
      
                                                                                                        
      If the target server uses a port other than port 383, append the port number to its FQDN, for example:
      
                                                                                                        
      loadbalancer.example.com:65530
                                                                                                        
      
                                                                                                    
      
                                                                                                    
      This command restarts the service discovery server. The source OM server begins to send any topology data changes immediately.
      
                                                                                                
      2. 
                                                                                                
    2. 
                                                                                                    
      Run the following command to start the initial synchronization of the topology data:
      
                                                                                                    
      /opt/OV/bin/OpC/startInitialSync.sh
                                                                                                    
      
                                                                                                
      3. 
                                                                                            
    
                                                                                        
    
                                                                                    
    
                                                                                
    4. 
                                                                            

                                                                        

                                                                    

                                                                

                                                            

                                                        

                                                        

                                                            
ClosedReintegrate Application Performance Management
                                                                

                                                                    
For information on how to complete the integration with APM, see the OBM Integrations Guide.

                                                                

                                                            

                                                        

                                                        

                                                            
Optional. APM event integration

                                                            
If you have APM integrated with production OBM and you have the OprEvent policy deployed on the production OBM gateway server, you need to assign and deploy the OprEvent policy to the staging OBM gateway server:

                                                            
On your staging OBM server:

                                                            
    
                                                                
  1.  Go to Administration > Monitoring > Policy Templates >Templates grouped by type > Events > Event from REST web service.
    2. 
                                                                
  2. Select OprEvent template.
    3. 
                                                                
  3. Right click and select Assign and Deploy Policy Template.
    4. 
                                                                
  4. In the wizard, select the node corresponding to the staging OBM gateway server.
    5. 
                                                                
  5. Click Next.
    6. 
                                                                
  6.  Click Finish.
    7. 
                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Optional. Switch load balancer to point to staging OBM.

                                                        

                                                            

                                                                

                                                                    
If the staging OBM uses the same load balancer as the production OBM, modify the load balancer to use the staging OBM gateway servers instead of the production OBM gateway servers.

                                                                    
Change the keep-alive send string for the data collector access from:

                                                                    
Old URL:  GET /ext/mod_mdrv_wrap.dll?type=test

                                                                    
New URL:  GET /gtw/serviceStatus

                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Exit staging mode on staging OBM 

                                                        

                                                            

                                                                
On the staging OBM server, exit staging mode:

                                                                
    
                                                                    
  1. 
                                                                        
    Go to Administration > Setup and Maintenance > Infrastructure Settings.
    
                                                                    
    2. 
                                                                    
  2. During side-by-side upgrade, the following were set on the staging OBM server to prevent duplicate execution of notification and alerts. Locate the Platform Administration –  OBM Evaluation settings group.
    3. 
                                                                    
  3. 
                                                                        
    Set Enable evaluation (staging) mode to false.
    
                                                                    
    4. 
                                                                    
  4. Set Enable evaluation (staging) mode for customer to false.
    5. 
                                                                    
  5. 
                                                                        
    Locate Operations Management - Staging Upgrade Settings group. 
    
                                                                    
    6. 
                                                                    
  6. Set Staging Mode Enable to false. This allows event automation rules, de-duplication, suppression and correlation.
    7. 
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
 Optional. Update your Data Flow Probe

                                                        

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

                                                            

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

                                                                
    
                                                                    
  • Secure the keystore certificates. For details, see Enable mutual (two-way) authentication.
    • 
                                                                    
  • Back up <DFP_install_folder>/conf/DataFlowProbe.properties as the file contains customizations that must be reapplied after the DFP update.
    • 
                                                                

                                                            

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Stop using the OBM 2020.05production servers

                                                    

                                                        
To stop using the production OBM 2020.05 servers properly, proceed as follows:

                                                        
    
                                                            
  1. 
                                                                
    Keep the OBM 2020.05 production servers online for a grace period.
    
                                                                
    Even though no new events are sent to the production server, you must keep this server online if the new OBM is not using the same Load Balances as the production OBM. Any active events that are forwarded from OM to the  production server continue to send updates to this server. These updates are then forwarded to OBM. If you do not consider these updates important, you can take the production server offline immediately. Otherwise, wait until all events that are still coming to the OBM 2020.05 production server are closed. We estimate that the grace period, in which most events are typically closed, lasts 1 to 2 weeks.
    
                                                            
    2. 
                                                            
  2. 
                                                                
    Take the OBM 2020.05 production servers offline.
    
                                                            
    3. 
                                                            
  3. 
                                                                
    Decommission the OBM 2020.05 servers.
    
                                                            
    4. 
                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Reapply parameter values to OBM Self Monitoring Auto-assignment Rule

                                                        

                                                            
When you upgradeupdate OBM to a newer version, the policy parameter values (for example, Email address to send notification for the JMS bus component) in OBM Self Monitoring Auto-assignment Rule are not preserved. You must therefore reapply the parameter values to this auto-assignment rule after the upgradeupdate is done. 

                                                            
For more information, see Management Pack for OBM Server Self-Monitoring. 

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Optional. Update management pack assignments

                                                    

                                                        
If you have deployed Management Templates and Aspects, update the assignments as described in the OBM Administer section or the corresponding management pack documentation. For more information, see the  Management Packs Overview.

                                                    

                                                

                                            

                                            

                                                

                                                    

                                                        
Optional. Update connectors

                                                        

                                                            
You can upgrade your existing connector. For details, see Connectors.

                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Stop using the OBM 2020.05production servers

                                                    

                                                        
To stop using the production OBM 2020.05 servers properly, proceed as follows:

                                                        
    
                                                            
  1. 
                                                                
    Keep the OBM 2020.05 production servers online for a grace period.
    
                                                                
    Even though no new events are sent to the production server, you must keep this server online if the new OBM is not using the same Load Balances as the production OBM. Any active events that are forwarded from OM to the  production server continue to send updates to this server. These updates are then forwarded to OBM. If you do not consider these updates important, you can take the production server offline immediately. Otherwise, wait until all events that are still coming to the OBM 2020.05 production server are closed. We estimate that the grace period, in which most events are typically closed, lasts 1 to 2 weeks.
    
                                                            
    2. 
                                                            
  2. 
                                                                
    Take the OBM 2020.05 production servers offline.
    
                                                            
    3. 
                                                            
  3. 
                                                                
    Decommission the OBM 2020.05 servers.
    
                                                            
    4. 
                                                        

                                                    

                                                

                                            

                                            

                                                

                                                    
Collect debug information

                                                    

                                                        
This section provides a list of log and configuration files that you can use to collect debug information when updating to OBM 2020.10.

                                                        
Log configuration (Gateways and Data Processing Servers)

                                                        
To create backup log file, c          opy <DVD Root>/Update/update_log.properties to %OvDataDir%/tmp/update_log.properties

                                                        
Log file locations (Data Processing Servers)

                                                        
Backup Log file

                                                        
%OvDataDir%/log/opr-premigration.log
                                                        

                                                        
%OvDataDir%/log/opr-upgradeBackup.x where x=1,2,3...
                                                        

                                                        
Backup location

                                                        
Configuration file backup: %OvDataDir%/backup/OMi107xcfg-backup.zip where x=0 or 1

                                                        
RSP file backup for auto config: %OvDataDir%/backup/OMibackup.rsp

                                                        
Uninstallation Logs:

                                                        
%Temp%\MicroFocusOvInstaller\HPOMi_10.70.007 (for OBM 2018.05)

                                                        
%Temp%\MicroFocusOvInstaller\HPOMi_10.71.016 (for OBM 2018.11)

                                                        
Installation Logs

                                                        
%Temp%\MicroFocusOvInstaller\HPOMi_10.80.005.004
                                                        

                                                        
Log file locations (Gateways)
                                                        

                                                        
Backup Log file:

                                                        
%OvDataDir%/log/opr-upgrade-Backup.log
                                                        

                                                        
%OvDataDir%/log/upgrade-backup.log
                                                        

                                                        
%OvDataDir%/log/upgrade-script.log
                                                        

                                                        
Backup location:

                                                        
Configuration file backup: %OvDataDir%/backup/OMi1070cfg-backup.zip

                                                        
RSP file backup for auto config: %OvDataDir%/backup/OMibackup.rsp

                                                        
Uninstallation Logs:

                                                        
%Temp%\MicroFocusOvInstaller\HPOMi_10.70.007 (for OBM 2018.05)

                                                        
%Temp%\MicroFocusOvInstaller\HPOMi_10.71.016 (for OBM 2018.11)

                                                        
Installation Logs

                                                        
%Temp%\MicroFocusOvInstaller\HPOMi_10.80.005.004
                                                        

                                                        
Default locations
                                                        

                                                        

                                                            
Linux:   %OvDataDir% = /var/opt/OV

                                                        

                                                        

                                                            
Windows: %OvDataDir% = C:\ProgramData\HP\HP BTO Software

                                                        

                                                    

                                                

                                            

                                        

                                        
                                    

                                

                            

                            

                            

                            

                                
                                

                                    

                                        
                                        

                                            

                                                
Last updated (Undefined variable: _HPc_Basic_Variables._HP_Document_Last_Update)

                                                

                                                    
                                                

                                            

                                        

                                    

                                

                            

                            
 

                            

                                
Send Help Center feedback