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.

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

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

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

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

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

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

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

Considerations

Before you begin to install OBM, consider the following:

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

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

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

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

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

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

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

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

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

      • To print the Nanny status,use the /opt/HP/BSM/opr/support/opr-status.py utility .
        On systems where only Python 3 is installed, use
        python3 /opt/HP/BSM/opr/support/opr-status.py
        Or
        alternatives --set python /usr/bin/python3
sudo python ./opr-status.py
        
      • To print the HAC status, use the /opt/HP/BSM/opr/support/opr-support-utils.sh utility.

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

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

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

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

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

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

Install and configuration sequence

Invocation of the OBM 2020.10 installation is the same for single server deployment type data 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. Change the current directory as follows:

   cd <OBMInstallationFilesDirectory>

   NoteYou should not have any whitespaces when you enter the path.

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, path of ovinstallparams.ini is the file created in Prepare the installation parameters file step.

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. Attend installation of OBM 2020.10. In a virtual environment, this phase might take approximately between 30 and 60 minutes.

After the configuration has been successfully applied, the configuration wizard displays a summary of the configuration changes. Click Finish to conclude the configuration.

You can log on to OBM from a supported web browser on a client system by using the Login page.

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. 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. 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. 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. In the Certificates dialog box, select the certificate type Secure Site CA and click Import.

   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. In Perform TLS certificate revocation checks on, click Do not check (not recommended).

      Caution This will disable the revocation check for all TLS connections that are established by Java-based applications on this system.

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

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

When you install two or more gateway servers, OBM requires external load balancing mechanisms to help ensure an even distribution of processing and communication activities across the network. This is particularly important in circumstances with high load, to avoid overloading any single server.

If the new OBM uses a different load balancer, then follow these steps to configure load balancing:

1. Create two virtual hostnames. Each virtual hostname must be a fully qualified domain name (FQDN) with the syntax <Hostname>.<DomainName>. This requirement is necessary to support the lightweight single sign-on (LW-SSO) authentication.

   The first hostname is required for accessing the OBM website on the gateway server. It can be distributed to OBM users. The second hostname is used by the data collectors to access the gateway server. It must be used when configuring data collectors to communicate with OBM.

   Alternatively, create one virtual hostname and assign two ports to route the user and data collection traffic to OBM.

2. Enter the relevant load balancer hostnames in the infrastructure settings of the virtual servers. To do so, go to Administration > Setup and Maintenance > Infrastructure Settings > Platform Administration. In the Platform Administration – Host Configuration table, set the following parameters:

   • Default Virtual Gateway Server for Application Users URL. Virtual hostname for the OBM website. The gateway server you are working on must be able to resolve this virtual IP address. This means that the nslookup command for the virtual hostname of the application users returns name and IP address when executed on this gateway server.
   • Default Virtual Gateway Server for Data Collectors URL. Virtual hostname for data collectors. All data collectors must be able to resolve this virtual IP address. This means that the name server lookup for the virtual hostname of a data collector returns name and IP address when executed on any data collector server.

3. Set the relevant parameters in the infrastructure settings. To do so, go to Administration > Setup and Maintenance > Infrastructure Settings > Platform Administration. In the Platform Administration – Reverse Proxy Configuration table, set the following parameters:

   • Enable Reverse Proxy. Set this parameter to true.

   • HTTP Reverse Proxy IPs. Add the internal IP addresses of the load balancers to this setting.

     • If the IP address of the load balancer that sends the HTTP or HTTPS request is included, the URL returned to the client is either the Default Virtual Server URL or the Local Virtual Server URL (when defined).

     • If no IP addresses are defined for this parameter (not recommended), OBM works in Generic Mode. This means that you can only log on to OBM by using the virtual server URL and not directly to the gateway.

     Note If your load balancer and OBM gateway servers are not in the same domain, you must add the IP address of the reverse proxy to the HTTP Reverse Proxy IPs parameter. For details, see "LW-SSO Configuration for Multi-Domain and Nested Domain Installations" in the OBM Administration Guide.

   To determine the internal IP address of your load balancer:

   1. Log on to OBM through the load balancer.

   2. On the gateway server, open the following log file:

      <OBM_HOME>\log\jboss\UserActions.servlets.log

      /opt/HP/BSM/log/jboss/UserActions.servlets.log

   3. Verify that the IP address in the latest logon line of the file matches the internal load balancer IP address. The entry must include your user name.

4. After changing the reverse proxy settings, restart the OBM service on the gateway and data processing servers.

5. If your load balancer enables you to choose between full-NAT (SNAT) and half-NAT (DNAT) topologies, choose full-NAT. If the load balancer and the gateway server are on the same subnet, SNAT must be enabled so that they can communicate.

6. Configure the load balancer for the data collector access.

   All data collectors must be able to access the virtual IP address of the load balancer. Use standard settings for the load balancer, and additionally set the following:

   • Set the persistence type to IP address stickiness or destination address affinity persistence (depending on the load balancer). If neither of these options are available and the choice is between cookie stickiness and stickiness by session, we recommend choosing stickiness by session.

   • The load balancing method should be sticky session by IP address.

   • Use the following keep-alive configuration:

     • Send string: GET /gtw/serviceStatus

     • Receive string: RUNNING

     Note If your OBM environment includes a firewall between the load balancer and the gateway server, and you are using the KeepAlive URL, make sure to open the port used to access the UI (usually 80 or 443).

7. Configure the load balancer for the BBC channel on port 383.

   • Port 383 must be open in both directions, that is, from the data collector through the load balancer to the gateway server, and from the gateway and data processing servers (not necessarily through the load balancer) to the data collectors.

   • The load balancing method must be sticky session by IP address for port 383.

   • Network traffic on port 383 should be passed through on the OSI model (network) layer 4 (without using layer 7, without TLS offloading on the load balancer).

     When balancing the load on the OSI model layer 7, the load balancer must validate the certificate.

   • The load balancer's data connector address used for load balancing must be reachable and resolvable from all the OBM servers (gateway and data processing server ) as well.

8. Configure the load balancer for the user access.

   • Use the default settings, and additionally set persistence to stickiness by session or destination address affinity persistence (depending on the load balancer). If neither of these options are available and the choice is between cookie stickiness and IP address stickiness, we recommend choosing IP address stickiness. If this is not configured properly, you may experience intermittent user interface failures.

   • Use the following keep-alive configuration:

     • Send string: GET /topaz/topaz_api/loadBalancerVerify_centers.jsp

     • Receive string: Success

For more information on the integrations, see the Integrations section in Operations Bridge Manager (OBM) community pages of the ITOM Marketplace website.

For details on supported integration versions, see the following document:

Support Matrices for Operations Center products

Connect Operations Agents

To connect an agent-monitored system to OBM, first ensure that the Operations Agent is installed on that system, then connect the agent to OBM, and finally grant the required certificates in OBM. For more information on connecting Operations Agents, see Connect Operations Agent to OBM.

Connect an Operations Manager server

Operations Manager (OM) can be integrated into your OBM environment to become a data provider for OBM.

After you have installed both OBM and OM, follow the procedures documented for the OBM / OM integration in the OBM Integrations Guide to connect OBM and OM. This connection enables bi-directional synchronization of events between the two systems, tool execution, and instruction text retrieval. The connection configuration requires you to configure a connected server for OM in OBM, to establish a trust relationship between OBM and the OM systems, and to configure a message forwarding policy.

Connect a SiteScope server

SiteScope is an agentless monitoring solution that enables you to remotely monitor the availability and performance of your IT infrastructure (for example, servers, operating systems, network devices, network services, applications, and application components). For more information on connecting SiteScope servers to OBM, see "Integrations" in the OBM Integrations Interactive documentation.

Connect an Network Node Manager i server

The NNMi-OBM integration forwards NNMi management event incidents as SNMPv2c traps to the Operations Connector on the NNMi management server. The Operations Connector filters the NNMi traps and forwards them to OBM.

The NNMi-OBM integration can also forward the SNMP traps that NNMi receives to the Operations Connector.

In addition, the NNMi-OBM integration provides the NNMi console for access from within the OBM event browser.

For information on configuring the NNMi-OBM integration, see "Integration" in the OBM Integrations Interactive documentation.

Connect a third-party management tool through Operations Connector

Operations Connector (OpsCx) is a component of Operations Bridge Manager that enables you to collect data from third-party and Micro Focus management tools (typically enterprise management systems) into OBM. You can integrate events, metrics, and topology data.

Third-party management tools are not provided by Micro Focus (for example, Microsoft System Center Operations Manager, Nagios, and Zenoss). Operations Connector also works with some Micro Focus applications (for example, ArcSight Logger, Network Node Manager i, and Systems Insight Manager).

For information on configuring the OBM-Operations Connector integration, see the Operations Connector documentation.

You can download Operations Connector implementations for third-party management tools from the Operations Bridge Manager community pages of the ITOM Marketplace website.

Connect Application Performance Management

For information on integrating Application Performance Management (APM) with OBM, see the OBM Integrations Interactive documentation.

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

Connect Service Manager or other trouble ticket tools

The Service Manager integration enables you to forward events from OBM to Service Manager. Forwarded events and subsequent event changes are synchronized back from Service Manager to OBM. You can also drill down from OBM events to Service Manager incidents.

For information on configuring the OBM-Service Manager integration, see the OBM / SM integration in the OBM Integrations Interactive documentation.

OBM also supports integrations with third-party trouble ticket systems, for example BMC Remedy Action Request System or ServiceNow.

Connect Operations Orchestration or other automation tools

Operations Orchestration (OO) provides a simple way for users to run scripts for automatic actions. The integration with OBM uses the OO capabilities for building investigation tools or service remediation scripts, providing the operators with a simple way to validate a problem, investigate it, or automatically correct it. A run book can be executed manually. OO run books can be launched from the Service Health and Event Browser applications.

For information on configuring the OBM-Operations Orchestration integration, see "Integration" in the OBM Integrations Interactive documentation.

OBM also supports integrations with third-party automation tools, for example xMatters.

Connect Operations Bridge Reporter

Operations Bridge Reporter is business service-driven IT reporting software that provides resource and response time reporting across server and application environments. It consolidates resource metrics, response time data, and business service topology data to enable a unique understanding and perspective on the behavior of dynamic virtualized IT infrastructure and the way it impacts end users. With patterns illustrated across applications, you can plan activities to optimize the performance of your business services to meet or exceed requirements.

For information on configuring the OBM-Operations Bridge Reporter integration, see the Operations Bridge Reporter Integrations Guide.

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