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

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

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

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

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

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

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

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

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

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

  export IATEMPDIR=<DirectoryForTemporaryFiles1>

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

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

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

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

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

  Default Folder	Minimum	Recommended
  C:\HPBSM	20	50
  C:\Program Files\HP\HP BTO Software C:\ProgramData\HP\BSM	11	22
  %TEMP% *	520 (during installation only)

  ^* This is a user environment variable

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

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

• Additional requirements:

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

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

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

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

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

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

• Unzip.OBM requires the unzip package.

  You can install this package by running the following command:

  yum install unzip

• Init scripts. OBM requires the initscripts package.

  You can install this package by running the following command:

  yum install initscripts

• Perl. OBM requires the Perl package.

  You can install this package by running the following command:

  yum install perl

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

  You can install this package by running the following command:

  yum install libaio

• PNG support libraries. OBM requires the libpng12 package.

  You can install this package by running the following command:

  yum install libpng12.x86_64

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

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

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

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

  Run the following command to install this package:

  yum groupinstall "X Window System"

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

  The following tools are not available when using the console or in the silent installation mode:

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

    To print the Nanny status,use the /opt/HP/BSM/opr/support/opr-status.py utility .

    To print the HAC status, use the /opt/HP/BSM/opr/support/opr-support-utils.sh utility.

  • OBM Database Browser: /opt/HP/BSM/tools/bsmbrowser/bsmbrowser.sh

    There is currently no alternative tool available.

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

• 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 2018.05. For information on disabling UAC, see the Microsoft Windows documentation (for example, Microsoft TechNet).

  After the installation, you can reenable UAC.

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

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

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

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

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

  Support Matrices for Operations Center products

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

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

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

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

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

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

     netsh int ipv4 show dynamicport tcp

     sysctl net.ipv4.ip_local_port_range

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

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

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

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

     sysctl -p
     

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

  • Date and time

  • Time zone

  • Daylight saving time configuration

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

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

• Web server:

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

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

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

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

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

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

  OBM uses a customized version of Apache HTTP Server.

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

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

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

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

• Open files limit. Ensure that open files limit on Linux machines is set to 30000 or higher.

  To verify the current limit, run the following command:

  ulimit -n

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

  * hard nofile 30000

  * soft nofile 30000

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

• Web browser configuration:

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

  • The browser must be set to enable JavaScript execution.

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

  • Internet Explorer users must:

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

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

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

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

• Flash Player. Make sure to install the latest version of Flash Player.

• Fonts. The following fonts must be installed:

  • Arial
  • Meiryo (for Japanese locales)
  • Malgun Gothic or Arial (for Korean locales)
  • SimHei or SimSun (for Simplified Chinese locales)

• Screen resolution. 1600x900 or higher (recommended); 1280x1024 (supported).

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

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

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

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

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

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

  1. Replace the

     -Djava.net.preferIPv4Stack=false

     line with the

     -Djava.net.preferIPv4Stack=true

     line.

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

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

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

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

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

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

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

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

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

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

    Support Matrices for Operations Center products

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  <DataFlowProbeInstallationDirectory>/\conf/\security

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

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

  1. Shut down the PostgreSQL database:

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

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

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

     Set the max_locks_per_transaction parameter to 1000 and uncomment the line.

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

  1. Start the database:

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

  2. Run vacuumlo on event and rtsm schemas:

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

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

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

  3. Run vacuumdb:

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

  4. Stop the database:

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

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

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

  Support Matrices for Operations Center products

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

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

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

  • OBM Management Pack for Oracle Database 1.00

  • OBM Management Pack for Infrastructure 1.00

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

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

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

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

The service pack is available on the Software Support Online portal:

1. Back up your database as specified by the database manufacturer.

2. Access the following website and download the OMI_00186.zipOMI_00187.zip file:

   Software Support Online OBM 10.63 Service Pack

   Software Support Online OBM 10.63 Service Pack

3. Extract all files from the archive OMI_00186.zip

4. Extract all files from the archive OMI_00187.zip

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

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

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>

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

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

2. Copy <OBMInstallationFilesDirectory>/Update/commons-cli.jar file to <TOPAZ_HOME>/lib/ and overwrite the existing commons-cli.jar file.
   Copy <OBMInstallationFilesDirectory>\Update\commons-cli.jar file to <TOPAZ_HOME>\lib\ and overwrite the existing commons-cli.jar file.
3. Applies if embedded PostgreSQL database is used.
   Copy <OBMInstallationFilesDirectory>/Update/commons-cli.jar file to <TOPAZ_HOME>/lib/ and overwrite the existing commons-cli.jar file.
   Applies if embedded PostgreSQL database is used.
   Copy <OBMInstallationFilesDirectory>\Update\commons-cli.jar file to <TOPAZ_HOME>\lib\ and overwrite the existing commons-cli.jar file.

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

   cd <OBMInstallationFilesDirectory>

5. Run the following command:

   upgrade.sh -d -silent -s

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

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

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

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

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

   press Y and accept the default location.

   If you receive the warning

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

   you can safely ignore it and proceed with the upgrade.

   Do not proceed to perform a post-installation action on the primary DPS at this point.

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

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

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

   upgrade.sh -d [-silent] -s

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

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

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

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

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

   press Y and accept the default location.

   If you receive the warning

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

   you can safely ignore it and proceed with the upgrade.

   Do not proceed to perform a post-installation action on the primary DPS at this point.

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

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

   Run the following command: upgrade.sh -d [-silent] -s If you have a lot of events in the database and want to archive them to speed up the upgrade process, you can use the –archive parameter. If this parameter is set to true, the upgrade will archive events, resulting in a faster upgrade. upgrade.sh -d -silent -archive=true -s If the -archive parameter is set to false, all the events are kept in the database. If you do not set this parameter, the value is considered to be false. If you do not set this parameter and there is a large number of events in the database, you will be prompted by the following message: There is a large number of closed events stored in the database that will significantly extend the upgrade time. Do you want to archive the closed events before starting the upgrade (y/n)? press Y and accept the default location. If you receive the warning Failed to query all users from DB.: User is not mapped... you can safely ignore it and proceed with the upgrade. Do not proceed to perform a post-installation action on the primary DPS at this point. 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: Go to Control Panel > Programs > Programs and Features> Uninstall a program. Select Performance Engine, right-click and click Uninstall. Return to the upgrade script and type y to continue. After the uninstallation completes, access the installation folder OBM_2018.05._for_Windows and manually run install.bat.

   For a non-primary DPS or a gateway server

   Run the following command: upgrade.sh -d -silent -s -noprep Note If the upgrade.sh -d -silent -noprep command does not start the uninstallation process, run the following command instead:     "%OvInstallDir%\Uninstall\HPBSM\setup" -i silent 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: Go to Control Panel > Programs > Programs and Features> Uninstall a program. Select Performance Engine, right-click and click Uninstall. Return to the upgrade script and type y to continue. After the uninstallation completes, access the installation folder OBM_2018.05._for_Windows and manually run install.bat.

6. Carefully follow further instructions in this guide.

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

• The event queue is emptied.

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

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

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

%OvDataDir%\backup\OMi1060cfg-backup.zip

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

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

INFO: Upgrading from OMixx
INFO: Preparing OMi for Upgrade...
INFO: Backup succeeded or not required for this upgrade.

Sometimes the following error may be reported as well:

Pre-upgrade process executed with some errors.

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

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

To start the installation, follow the steps:

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

2. Change the current directory as follows:

   cd <OBMInstallationFilesDirectory>

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

   install

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

   install -silent

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

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

     ./install.sh

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

     ./install.sh -console

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

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

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

   ./install.sh -silent

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

The update 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 2018.05 version. To find out which files are backed up, see <OBMInstallationFiles>\/Update\/preUpdateBackup.txt

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

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.

1. Uninstall your previous Data Flow Probe:

   <ProbeinstallDirectory>\UninstallerData\Uninstall_Discovery_Probe

   <ProbeinstallDirectory>/UninstallerData/Uninstall_Discovery_Probe

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

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

   OBM_2018.05_DataFlowProbe\Software\Linux\UCMDB_DataFlowProbe-11.10.105.exe

   OBM_2018.05_DataFlowProbe/Software/Linux/UCMDB_DataFlowProbe-11.10.105.bin

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

   <ProbeinstallDirectory>\runtime\probeManager\discoveryResources\Cmdb10xAdapter

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

   and

   <ProbeinstallDirectory>\lib

   <ProbeinstallDirectory>/lib/

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

In the Upgrade Settings page, choose the type of upgrade that you want to perform:

Click Next to continue.

In the Database Connection page, choose the database management system to which you replicated the old databases in Replicate the databases, to store the database schemasdatabases (Management, RTSM, and Event)(Management, RTSM, RTSM History, and Event). Additionally, specify the valid connection properties, access credentials, and other data as requested by the wizard.specify the database access credential and the location of the database backup image.

Click Next to continue.

In the Database Connection (SQL Server Settings)Database Connection (Oracle Server Settings)Database Connection (PostgreSQL Settings) page, provide credentials for the administrative access to the Microsoft SQL Server databaseOracle Database instancePostgreSQL database.

Click Next to continue.

In the Schema Upgrade Execution page, click Next to start the database schema upgrade.

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

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.

Once installed, management packs cannot be removed, even though their entries appear in the Management Packs page.

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.

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

1. Select the Number of monitored nodes that send events to OBM. This includes all nodes that are present as CIs and that send events to OBM (for example, nodes connected to Operations Manager (OM), nodes directly connected to OBM, and target connectors).

2. Optional. Click Advanced to adjust the maximum memory that the Java Virtual Machine (JVM) allocates to the OBM processes. To change the allocated memory, click Manual override and type the new values in the text boxes.

3. Click Next.

In the Update Environment (License) page, you can configure the license that OBM uses.

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

Click Next.

In the Update Environment (Login Settings) page, you can set the passwords for the OBM users.

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

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

To configure OBM passwords, specify the following options:

• Administrator password, Confirm. Type the password of the OBM administrator (user name: admin) for the OBM user interface. This password is required to log on to OBM, and can be changed in the OBM user interface at a later time.

• JMX password, Confirm. Type the password to be used by the OBM administrator for all OBM JMX consoles (user name: admin) and for the RTSM JMX console (user name: sysadmin).

  Note The JMX password is valid on all host systems that constitute your OBM environment.

Click Next.

In the Update Environment/Machine Configuration page, click Next to start the update process.

When the update is complete, the Start OBM page opens and instructs you to enable OBM on this host system.

Follow the steps:

1. To enable OBM on the local system, do the following:

   • Windows Server 2008:

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

   • Windows Server 2012:

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

2. To enable OBM on the local system, run the following command:

   /opt/HP/BSM/scripts/run_hpbsm start

3. To check whether OBM is enabled, click Open Status Page in the Start OBM page of the upgrade wizard.

   Alternatively, perform the following on the OBM host system:

   • Windows Server 2008:

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

   • Windows Server 2012:

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

   Alternatively, run the following command on the OBM host system:

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

4. When OBM is enabled, click Next to continue.

In the Configuration Upgrade page, click Upgrade to invoke the OBM configuration upgrade.

The component upgrade process may take considerable time.

If upgrade of a non-mandatory component fails, you can continue with the upgrade and return to this wizard page later to complete the component upgrade.

When all (mandatory) components are upgraded, click Next to continue.

In the Summary (Upgrade Wizard Summary) page, read the summary of the OBM upgrade process.

Click Finish to close the upgrade wizard.