HPE Operations Manager i

Software Version: 10.10

Customized output from:

HPE Operations Manager i 10.10 Installation and Upgrade Guide

Document Release Date: 08 July 2018

Software Release Date: December 2015

HP logo

Legal Notices

Warranty

The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPE 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. Valid license from HPE 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-2016 Hewlett Packard Enterprise Development Company, L.P.

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.

 
 
 
 

HPE Operations Manager i 10.10 Installation and Upgrade Guide

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

About this guide

Welcome to the HPE Operations Manager i 10.10 Installation and Upgrade Guide. This guide enables you to first specify the type of installation or upgrade that you plan to perform, and then view or print customized contents, which include only the requirements and tasks that apply to you.

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

Note: This guide may have been updated with important corrections or additional information after it was packaged with the installation files. Before reading on, check for an updated version on the HPE Software Support web site.

OMi deployment

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

OMi is one of HPE's Business Service Management (BSM) solutions. It provides a way for IT administrators to pull together events from different monitoring tools. The monitoring tools can be HPE software such as HPE Operations Manager, HPE Operations Agent, HPE ArcSight Logger, and HPE SiteScope, or third-party tools such as IBM Tivoli Enterprise Console (TEC), Microsoft System Center Operations Manager (SCOM), or Nagios. OMi with its BSM connectors can pull that monitoring data together, reduce duplicate event reporting, and prioritize the events by business criticality.

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

Choose the setup type

Enterprise setup
Express setup

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

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

Choose the installation type

Install and configure OMi 10.10
Upgrade from OMi 10.0x
Upgrade from BSM 9.25 or later
Uninstall OMi 10.10

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

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

You can upgrade OMi 10.0x to OMi 10.10. Both in-place upgrade and side-by-side migration are supported. In-place upgrade begins with uninstallation, as OMi 10.10 replaces your earlier OMi version.

You can upgrade BSM 9.25 or a later BSM version to OMi 10.10. Both in-place upgrade and side-by-side migration are supported. In-place upgrade begins with uninstallation, as OMi replaces BSM.

Note: To be able to transition from BSM 9.24 or an earlier BSM version, first patch your installation with a later BSM version and only then initiate the upgrade process. For patching instructions, see the BSM Patch Installation Guide.

Caution: During the upgrade, specific customizations of your original product deployment are lost: hardening, configuration of non-default user account for the BSMOMi servicesconfiguration of non-root user account for the BSMOMi processes, other settings. 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.

The uninstallation process removes OMi from the host systems on which it is installed.

Choose the upgrade type

In-place upgrade
Side-by-side migration

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

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

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

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

Note: Perform side-by-side migration in the following situations:

  • Your source and target environments are not running the same operating systems.

  • You plan to continue using Application Performance Management (APM) and APM-related applications of your BSM environment. After the migration, integrate APM with OMi as described in the OMi Integrations Guide.

Choose the deployment type

Distributed deployment
Single-server deployment

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

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

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

A single-server deployment can be used for many installation scenarios as long as the system has the required hardware to handle the capacity. For large capacities, 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.

To choose single-server deployment, select the Single Server option in the OMi installation wizard.

Choose the database management system

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

Note: The HP Operations Bridge Express Edition Suite does not entitle you to use Microsoft SQL Server or Oracle Database with OMi. Select one of the PostgreSQL options instead.

The process for upgrading from BSMOMi 10.0x does not enable changing the database management system for OMi installation. Select the option that matches your BSMcurrent OMi environment.

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

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

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

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

Note: As part of the OMi 10.0x upgrade process, OMi 10.10 updates the embedded PostgreSQL database management system to the version 9.3.9.

Choose the operating system

Microsoft Windows
Linux

Choose the operating system that runs on the computers on which you want to install OMi.

Select additional options

Load balancing
Change of Windows user account for OMi servicesUse of non-root Linux user account for OMi processes
Silent deployment

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

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

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

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

With silent deployment, you perform both OMi installation and the subsequent configuration in a silent mode, without using the respective wizards: the required values are gathered directly from the previously prepared input files. For OMi 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).

Note: The upgrade wizard is not available in silent mode. You can run the OMi installation and configuration steps silently, but you still have to perform the upgrade by using the wizard.

View or print

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

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

Check Your Selections

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

 

If any selections are not correct, click Change.

Check the hardware requirements

  • Processor. 4 CPU cores minimum, 8 recommended. All CPU cores must run at 2.4 GHz or faster.

    In a virtual environment, make sure the number of virtual CPUs is equivalent to 4 (or 8) physical CPU cores.

    Tip: Beacuse OMi performance is dependent upon processor speed, HPE recommends 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 26 10
    Recommended 32 30 12

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

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

    Default Directory Minimum Recommended
    /opt/HP/BSM 20 50
    /var 1 2
    /tmp 3 (during installation only)

    If there is not enough free storage space in the /tmp directory, you can change the default temporary directory that OMi 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.

    Default Folder Minimum Recommended

    C:\HPBSM

    20 50

    C:\Program Files\HP\HP BTO Software

    C:\ProgramData\HP\BSM

    1 2
    %TEMP% * 2.5 (during installation only)

    * This is a user environment variable

  • Additional requirements:

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

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

    • OMi 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 not to install OMi server on a local disk of the client system.

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

Check the software requirements

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

  • Init scripts. OMi requires the initscripts package.

    You can install this package by running the following command:

    yum install initscripts

  • Perl. OMi requires the Perl package.

    You can install this package by running the following command:

    yum install perl

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

    You can install this package by running the following command:

    yum install libaio

  • PNG support libraries. OMi requires the libpng12 package.

    You can install this package by running the following command:

    yum install libpng12.x86_64

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

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

  • X Window System. The system from which you are installing OMi must host an implementation of X Window System.

    However, you can install OMi 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:

    • HPE Operations Manager i 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.

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

      There is currently no alternative tool available.

  • X Window System emulators. HPE recommends that you do not use third-party X Window System implementations (emulators), for example Exceed, to install OMi. 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. HPE highly recommends that you make the following change in the Windows registry:

    For the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, create a new value TcpTimedWaitDelay (DWORD) and set the value to 60 (decimal).

    If this is not done, a problem with exhausting the available TCP resources might occur, because of a too long time delay configured by default.

    Caution: HPE recommends that you back up Windows Registry before making any changes to it.

  • User Account Control (UAC). UAC must be disabled before installingupgrading to OMi 10.10. UAC is enabled by default in some versions of Windows Server, for example, Windows Server 2008 SP2. For information on disabling UAC, see the Microsoft Windows documentation (for example, Microsoft TechNet).

  • Fully qualified domain names (FQDNs). Each OMi 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. OMi servers must be able to resolve names of the systems they communicate with. These include all OMi servers, database servers, and data collectors.

  • Java Runtime Environment (JRE). Oracle Java 7 is copied onto the system during server installation as part of the OMi installation.

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

    Installing OMi servers together with most other HPE products on the same host system may result in port conflicts, performance issues, or other unexpected behavior. Coexistence of OMi servers with HPE Operations Agent and HPE 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: 443, 1098, 1099, 5445, 8009, 8080, and 29000.

    If the installation checks indicate that these ports are in use, the installation does not fail, but HPE recommends that you free the necessary ports before configuring OMi.

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

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

    • Date and time

    • Time zone

    • Daylight saving time configuration

  • HPE Software L-Core. OMi installs the HPE Software 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. Such an upgrade is an irreversible change.

  • Web server:

    OMi deployment requires a web server. OMi therefore by default installs Apache HTTP Server on all gateway servers. In Microsoft Windows environments, you can alternatively install the Microsoft IIS web server.

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

    OMi deployment requires a web server. OMi therefore by default installs Apache HTTP Server on the only host system.

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

    OMi deployment requires a web server. OMi therefore by default installs Apache HTTP Server on all gateway serverson the only host system.

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

    Apache HTTP Server. OMi uses a version of Apache HTTP Server customized for OMi by HPE.

    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.

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

    Microsoft IIS. To use the Microsoft IIS web server, install it on all gateway servers before installing OMi. The web server must be up and running prior to the OMi installation. During OMi configuration, the Microsoft IIS settings are automatically configured to work with OMi.

    Note that OMi only supports the default application pool of Microsoft IIS.

    The following Microsoft IIS roles must be enabled:

    • Application Development section: ISAPI Extensions

    • Application Development section: ISAPI Filters

    • Common HTTP Features section: Static Content

    • Common HTTP Features section: HTTP Redirection (in IIS 8 only)

    • Management Tools section: IIS Management Scripts and Tools

    Note: Some command-line utilities and UIs may not return detailed error information in the HTTP body. You can configure Microsoft IIS to send detailed errors, as described below:

    1. Open Internet Information Services (IIS) Manager and navigate to the OMi web site.

    2. In Feature View, double-click Error Pages.

    3. Right-click on the Error Pages page and click Edit Feature Settings. In the Error Responses section, select Detailed errors.

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

    The installation package is named HPE_OMi_10.10.<BuildNumber>_for_Windows.zipHPE_OMi_10.10.<BuildNumber>_for_Linux.zip. Download the archive file to the system on which you plan to install OMiwhich you plan to upgrade to OMi 10.10, and extract all files from the archive.

Check the OMi 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 OMi 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).

  • 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. HPE recommends that all OMi servers, including the database server, are installed on hosts in the same network segment.

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

  • IPv6 and dual IP stack support. You can install OMi 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, OMi uses IPv4 by default.

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

    Note: On Linux systems, OMi 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 OMi 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 you changes and then restart local OMi processes.

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

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

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

Check the database requirements

  • Instance location. With a local PostgreSQL database instance, OMi installs and configures the instance for you on the same system that hosts the OMi data processing server.
  • Instance location. OMi installs and configures the local PostgreSQL database instance for you on the same system that hosts the OMi data processing server.
  • Remote instance configuration. If you use a remote database instance, OMi 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 the OMi Database Guide.

  • 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 OMi user schemas, see "Oracle Server Configuration and Sizing Guidelines" in the OMi Database Guide.

  • Oracle Real Application Clusters (Oracle RAC). If your Oracle Database is configured in an Oracle Real Application Clusters (Oracle RAC) environment, special configuration is required. For details, see "Appendix D: Support for Oracle Real Application Cluster" in the OMi Database Guide.

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

    • Partitioning of database tables and indexes is enabled.

    • The RECYCLEBIN parameter is set to Off.

    • The UTF8 character set is used for encoding characters.

    For more information, see the OMi Database Guide.

  • Host operating system. OMi supports switching the operating system of your database server during the upgrade provided that this is also supported by your database management system vendor.

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

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

    • Partitioning of database tables and indexes is enabled.

    • The RECYCLEBIN parameter is set to Off.

    • The UTF8 character set is used for encoding characters.

    For more information, see the OMi Database Guide.

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

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

    For instructions on how to set up your OMi database server, see the OMi Database Guide.

Check the user account privilege requirements

  • System-wide privileges. You must use the root user account to install and configure OMi.

    To run OMi 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. You need administrative privileges on the host systems on which you are installing and configuring OMi servers.

  • Privileges in Oracle Database. For OMi to configure a user schema in a database, you must be granted the following permissions and privileges within the Oracle Database instance:

    • Administrative permissions

    • System privileges:

      • CONNECT

      • CREATE PROCEDURE

      • CREATE SEQUENCE

      • CREATE TABLE

      • CREATE TRIGGER

      • CREATE USER

      • CREATE VIEW

      • UNLIMITED TABLESPACE

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

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

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

Check the upgrade requirements and considerations

  • Upgrade plan. Based on your needs, create an upgrade plan. The plan must 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.

  • User Account Control (UAC). UAC must be disabled before installingupgrading to OMi 10.10. UAC is enabled by default in some versions of Windows Server, for example, Windows Server 2008 SP2. For information on disabling UAC, see the Microsoft Windows documentation (for example, Microsoft TechNet).

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

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

    • Original and new host systems. Location, credentials, and access to files on all original BSMOMi host systems and on the systems that will host OMi 10.10.

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

    • Support for your database management system. Check the official OMi 10.10 support for the database management system version used in the BSMoriginal OMi environment. For information, select Operations Manager i from the product list in the following document:

      Support Matrices for Operations Center products

    • User management. Permissions for individual OMi users are granted through 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 OMi, create the required roles, grant permissions to them, and finally assign the roles to users or user groups.

    • BSM setting values that are not migrated. If you have modified the values of particular infrastructure settings in your BSM environment, keep in mind that you must do the same in OMi, because the modified values are not migrated. This applies to the following infrastructure settings:

      • Polling Interval, in the Operations Management – User Engagement settings group

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

    • Data collectors and integrated components. Access to all data collectors and components integrated with the original BSMOMi 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. The sequence of steps for upgrading distributed deployments is crucial. Pay special attention to follow the upgrade procedure properly. The process involves all host systems of your existing BSMOMi deployment.

    You can install and configure additional OMi servers after the upgrade process completes, using the OMi installation and configuration wizards.

  • Optional. Operating system switch. Side-by-side migration to OMi 10.10 supports switching 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 BSMOMi host systems:

    • <GatewayServerInstallationDirectory>/\AppServer/\webapps/\site.war/\openapi/\excels (directory)

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

    • <DataProcessingServerInstallationDirectory>/\cmdb/\general (directory)

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

    If at least one data provider, such as HPE Network Node Manager i, is integrated with BSMOMi, also back up the certificates from the following directory:

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

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

    <DataFlowProbeInstallationDirectory>/\conf/\security

    For more information, see the Data Flow Probe Installation Guide.

  • Backup of manual file changes. If you made changes to any of the following files on the original BSMOMi gateway servers, back up the changed files:

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

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

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

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

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

    1. Shut down the PostgreSQL database:

      $OMi_HOME / %OMi_HOME%\bin\opr-pgctl.bat –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, HPE recommends backing up the databasesdatabase schemas. You should back them up as late before the BSMOMi uninstallation as possible to minimize the risk of data loss.

  • The OPEN_CURSORS parameter of Oracle Database. For the upgrade, set the Oracle Database parameter OPEN_CURSORS to 10,000.

  • Integrations. For details on product versions that are supported with OMi 10.10, select Operations Manager i from the product list in the following document:

    Support Matrices for Operations Center products

    Note: The following integration application versions are not supported with OMi 10.10:

    • HP BSM Connector 9.2x

    • HPE Data Flow Probe 9.05

    You must upgrade each application to a supported version before you start using it with OMi. For instructions, see the BSM Connector Installation and Upgrade Guide and the OMi Data Flow Probe Installation Guide.

  • Optional. RTSM integrations disablement. If integrations are configured in RTSM Integration Studio (for example, topology synchronization integrations between central UCMDB and RTSM), after upgrading, HPE Data Flow Probe will run population jobs immediately 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 HPE Data Flow Probe. If HPE Data Flow Probe (DFP) is installed on one of the BSMOMi gateway servers, uninstall it separately before starting the upgrade.

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

    • HPE OMi Management Pack for Oracle Database 1.00

    • HPE OMi Management Pack for Infrastructure 1.00

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

    For a list of management packs bundled with OMi 10.10, see the OMi Release Notes.

  • Special prerequisite for the BSM 9.2x and OMi 10.0x User Engagement feature. If you use OMi 10.0x that has User Engagement installed, and if it was previously upgraded from BSM 9.2x in which User Engagement was also used, execute the following SQL statement on the Management database before upgrading to OMi 10.10:

    delete from setting_parameters where sp_context='exc' and sp_name='opr.exc.db.connection.dbname'

Configure event buffering in OM

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

During the migration, OM continues to attempt sending events to BSMthe already installed OMi version. If BSMthe original OMi servers cannot be reached, OM starts to buffer the events until the new OMi 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.

Fulfill the upgrade prerequisites and pPlan the upgrade process

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

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

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

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

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

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

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

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

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

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

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

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

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

  2. On the new system that will host OMiexisting BSMOMi host system, prepare the OMi installation parameters file.

  3. On the new system that will host OMiexisting BSMOMi host system, initiate the upgrade process.

  4. Attend uninstallation of BSMthe earlier OMi versionand invocation of the installation wizard.

  5. Follow instructions of the installation wizard and install OMi 10.10.

  6. In the post-installation wizard, choose the appropriate option and start the upgrade wizard.

  7. Follow instructions of the upgrade wizard and conclude the upgrade process.

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

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

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

  4. Attend invocation of the installation wizard.

  5. Follow instructions of the installation wizard and install OMi 10.10.

  6. In the post-installation wizard, choose the appropriate option and start the upgrade wizard.

  7. Follow instructions of the upgrade wizard, and conclude the upgrade process.

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

    1. Initiate the upgrade process.

    2. Attend invocation of the installation wizard.

    3. Follow instructions of the installation wizard, and install OMi 10.10.

    4. In the post-installation wizard, choose the appropriate option to start the configuration wizard.

    5. Follow instructions of the configuration wizard and configure OMi.
  1. Make sure that BSMthe earlier OMi version is enabled (all servicesprocesses are running on the BSMOMi host systems).

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

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

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

  5. Follow instructions of the installation wizard and install OMi 10.10.

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

  6. Disable OMi (stop all servicesprocesses on the BSMOMi host systems).

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

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

    3. Follow instructions of the installation wizard and install OMi 10.10.

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

  8. On the host system of the primary (first installed) DPS, in the post-installation wizard, choose the appropriate option and start the upgrade wizard.

  9. Follow instructions of the upgrade wizard and conclude the upgrade process.

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

    1. In the post-installation wizard, choose the appropriate option to start the configuration wizard.

    2. Follow instructions of the configuration wizard and configure OMi.

Fulfill the upgrade prerequisites and pPlan the upgrade process

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

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

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

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

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

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

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

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

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

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

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

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

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

  2. On the new system that will host OMiexisting BSMOMi host system, prepare the OMi installation parameters file.

  3. On the new system that will host OMiexisting BSMOMi host system, initiate the upgrade process.

  4. Attend uninstallation of BSMthe earlier OMi version and invocation of the OMi 10.10 installation.

  5. Start the upgrade wizard.

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

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

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

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

  4. Attend invocation of the OMi 10.10 installation.

  5. Start the upgrade wizard.

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

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

    1. Initiate the upgrade process.

    2. Attend invocation of the OMi 10.10 installation.

    3. Start the upgrade wizard.

    4. Follow instructions of the silent configuration and configure OMi.

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

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

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

  4. Attend uninstallation of BSMthe earlier OMi version and invocation of the OMi 10.10 installation.

  5. Disable OMi (stop all servicesprocesses on the BSMOMi host systems).

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

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

  7. On the host system of the primary (first installed) DPS, start the upgrade wizard.

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

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

    1. Start the configuration wizard silently.

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

Prepare the OMi installation parameters file

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

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

    <OMiInstallationFiles>\/Software\/ovinstallparams.ini

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

    [installer.properties]
    setup=HPOMi
    group=typical

  3. Modify the upgrade.sh script as follows:

    1. Original

      if [ -e /opt/HP/BSM/scripts/run_hpbsm ]; then
        echo "INFO: ($0) Stopping OMi for Uninstallation..."
        /opt/HP/BSM/scripts/run_hpbsm stop
      fi

      Replace with

      if [ -e /etc/init.d/hpbsmd ]; then
      echo "INFO: ($0) Stopping OMi for Uninstallation..."
      /etc/init.d/hpbsmd stop
      fi

    2. Original

      if [ -e /opt/HP/BSM ]
      then
      echo "ERROR: ($0) Installation directory of BSM 9.2x/OMi 10.0x is not empty after uninstallation. Please check if OMi/BSM was uninstalled correctly, delete the directory /opt/HP/BSM and re-run this script"
      exit 1
      fi

      Replace with

      if [ -e /opt/HP/BSM ] && [ "$(ls -A /opt/HP/BSM)" ]
      then
      echo "ERROR: ($0) Installation directory of BSM 9.2x/OMi 10.0x is not empty after uninstallation. Please check if OMi/BSM was uninstalled correctly, delete the directory /opt/HP/BSM and re-run this script"
      exit 1
      fi

  4. 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 HPE shared data (shared components), and the last two lines apply to OMi.

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

    The path of the installation folder for OMi content must not exist yet, and its name must:

    The path of the OMi binary files directory (<OMiBinaryFilesDirectory>) must not exist yet, and its name must:

    • Be shorter than 16 characters

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

    • End with the HPBSM string

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

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

    <OMiInstallationFiles>\/Software\/ovinstallparams.ini

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

    • Data processing server:

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

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

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

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

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

    The path of the installation folder for OMi content must not exist yet, and its name must:

    The path of the OMi binary files directory (<OMiBinaryFilesDirectory>) must not exist yet, and its name must:

    • Be shorter than 16 characters

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

    • End with the HPBSM string

  4. Modify the upgrade.sh script as follows:

    1. Original

      #
      # Check arguments
      #
      if [ $# -ge 3 ]; then
      echo "ERROR: ($0) Wrong number of arguments"
      echo "ERROR: ($0) Usage: $0 -d [-noprep] 
      [-silent | -console]|-s [-silent | -console]"
      exit 1										

      Replace with

      #
      # Check arguments
      #
      if [ $# -ge 4 ]; then
      echo "ERROR: ($0) Wrong number of arguments"
      echo "ERROR: ($0) Usage: $0 -d [-noprep] 
      [-silent | -console]|-s [-silent | -console]"
      exit 1										

    2. Original

      if [ -e /opt/HP/BSM/scripts/run_hpbsm ]; then
      echo "INFO: ($0) Stopping OMi for Uninstallation..."
      /opt/HP/BSM/scripts/run_hpbsm stop
      fi

      Replace with

      if [ -e /etc/init.d/hpbsmd ]; then
      echo "INFO: ($0) Stopping OMi for Uninstallation..."
      /etc/init.d/hpbsmd stop
      fi

    3. Original

      if [ -e /opt/HP/BSM ]
      then
      echo "ERROR: ($0) Installation directory of BSM 9.2x/OMi 10.0x is not empty after uninstallation. Please check if OMi/BSM was uninstalled correctly, delete the directory /opt/HP/BSM and re-run this script"
      exit 1
      fi

      Replace with

      if [ -e /opt/HP/BSM ] && [ "$(ls -A /opt/HP/BSM)" ]
      then
      echo "ERROR: ($0) Installation directory of BSM 9.2x/OMi 10.0x is not empty after uninstallation. Please check if OMi/BSM was uninstalled correctly, delete the directory /opt/HP/BSM and re-run this script"
      exit 1
      fi

Initiate the upgrade process

Caution: This section only applies for the following host systems of your BSMOMinew OMi deployment: primary data processing server. Follow these steps during the appropriate phase of the BSMOMi upgrade process.

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

  1. Open a Command Promptterminal window as a user with administrative privilegesthe root user.

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

    cd <OMiInstallationFilesDirectory>

  3. Run the following command:

    upgrade.sh [-silent] -d -s

    The -silent option, when specified, invokes the installation of OMi 10.10 in a silent mode.

    Depending on which system you are initiating the upgrade for, perform the following:

    • For the primary data processing server (DPS) of the existing BSMOMi environment, run the following command:

      upgrade.sh [-silent] -d -s

      upgrade.sh -silent -d -s

      The -silent option, when specified, invokes the installation of OMi 10.10 in a silent mode.

      If prompted by the 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.

    • For a non-primary DPS or a gateway server (GS), run the following command:

      upgrade.sh -d -s -noprep

      upgrade.sh -silent -d -s -noprep

  4. Carefully follow further instructions in this guide.

Attend the initial upgrade phase

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

  • The event queue is emptied.

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

    If there are numerous closed events stored in the BSMoriginal OMi Event database, the upgrade process might take a very long time. To avoid this situation, OMi gives you an option of automatically archiving and purging closed events before the database is upgraded.

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

    %OvDataDir%\backup\OMi10cfg-backup.zip

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

    This operation is based on the configuration file <OMiInstallationFilesDirectory>\/Update\/preUpdateBackup.txt.

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

INFO: (upgrade) Running PreMigration Tool...
<Number> events remain in the event queue=opr_gateway_queue_1 on host <Hostname>.

Under specific circumstances, 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 initiate the upgrade process again.

Attend uninstallation of BSMyour earlier OMi version

The uninstallation process performs the following operations locally:

  1. Removes BSMOMi intermediate patches (IPs), if present on the host system.

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

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

  4. Uninstalls BSMOMi, including LCore/Agent. Configuration data in the %OvDataDir%/var/opt/OV directory is preserved.

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

INFO: (upgrade) Stopping OMi for Uninstallation
INFO: (upgrade) Uninstalling BSM 9.2x/OMi 10.0x patches...
INFO: (upgrade) Uninstalling BSM 9.2x/OMi 10.0x...
INFO: (upgrade) Uninstallation done - Starting installation of OMi 10.10.

Attend invocation of the OMi 10.10 installation

After BSMyour earlier OMi version is uninstalled, tThe upgrade process invokes the installation of OMi 10.10.

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

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

Fulfill the installation prerequisites and pPlan the installation process

Before you start with the OMi installation, consider the following:

  • You can install and configure OMi 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 OMi. 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 OMi servers first and to configure them at a later time.

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

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

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

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

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

  • If 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 OMi is not supported, therefore the Modify and Repair options are unavailable if the OMi installation wizard is invoked when OMi is already installed.

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

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

Perform the installation actions according to the below procedure, which is based on your planned single-serverdistributed OMi deployment and the chosen sequence for installing and configuring OMi servers.

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

  2. Start the installation wizard and install OMi.

  3. In the post-installation wizard, select the proper option to start the configuration wizard and configure OMi.

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

  4. Depending on the preferred OMi installation and configuration sequence, proceed as follows:

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

      1. On each system that will host either an OMi data processing server (DPS) or an OMi gateway server (GS), start the installation wizard and install OMi, without invoking the configuration wizard at the end (in the post-installation wizard).

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

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

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

    • To install and configure all OMi servers one after the other, do the following:

      1. Start the installation wizard and install OMi on the following systems in sequence, while selecting the proper option to start the configuration wizard and configure OMi at the end of the installation (in the post-installation wizard):

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

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

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

Prepare the OMi installation parameters file

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

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

    <OMiInstallationFiles>\/Software\/ovinstallparams.ini

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

    [installer.properties]
    setup=HPOMi
    group=typical

  3. Modify the upgrade.sh script as follows:

    1. Original

      if [ -e /opt/HP/BSM/scripts/run_hpbsm ]; then
        echo "INFO: ($0) Stopping OMi for Uninstallation..."
        /opt/HP/BSM/scripts/run_hpbsm stop
      fi

      Replace with

      if [ -e /etc/init.d/hpbsmd ]; then
      echo "INFO: ($0) Stopping OMi for Uninstallation..."
      /etc/init.d/hpbsmd stop
      fi

    2. Original

      if [ -e /opt/HP/BSM ]
      then
      echo "ERROR: ($0) Installation directory of BSM 9.2x/OMi 10.0x is not empty after uninstallation. Please check if OMi/BSM was uninstalled correctly, delete the directory /opt/HP/BSM and re-run this script"
      exit 1
      fi

      Replace with

      if [ -e /opt/HP/BSM ] && [ "$(ls -A /opt/HP/BSM)" ]
      then
      echo "ERROR: ($0) Installation directory of BSM 9.2x/OMi 10.0x is not empty after uninstallation. Please check if OMi/BSM was uninstalled correctly, delete the directory /opt/HP/BSM and re-run this script"
      exit 1
      fi

  4. 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 HPE shared data (shared components), and the last two lines apply to OMi.

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

    The path of the installation folder for OMi content must not exist yet, and its name must:

    The path of the OMi binary files directory (<OMiBinaryFilesDirectory>) must not exist yet, and its name must:

    • Be shorter than 16 characters

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

    • End with the HPBSM string

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

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

    <OMiInstallationFiles>\/Software\/ovinstallparams.ini

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

    • Data processing server:

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

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

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

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

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

    The path of the installation folder for OMi content must not exist yet, and its name must:

    The path of the OMi binary files directory (<OMiBinaryFilesDirectory>) must not exist yet, and its name must:

    • Be shorter than 16 characters

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

    • End with the HPBSM string

  4. Modify the upgrade.sh script as follows:

    1. Original

      #
      # Check arguments
      #
      if [ $# -ge 3 ]; then
      echo "ERROR: ($0) Wrong number of arguments"
      echo "ERROR: ($0) Usage: $0 -d [-noprep] 
      [-silent | -console]|-s [-silent | -console]"
      exit 1										

      Replace with

      #
      # Check arguments
      #
      if [ $# -ge 4 ]; then
      echo "ERROR: ($0) Wrong number of arguments"
      echo "ERROR: ($0) Usage: $0 -d [-noprep] 
      [-silent | -console]|-s [-silent | -console]"
      exit 1										

    2. Original

      if [ -e /opt/HP/BSM/scripts/run_hpbsm ]; then
      echo "INFO: ($0) Stopping OMi for Uninstallation..."
      /opt/HP/BSM/scripts/run_hpbsm stop
      fi

      Replace with

      if [ -e /etc/init.d/hpbsmd ]; then
      echo "INFO: ($0) Stopping OMi for Uninstallation..."
      /etc/init.d/hpbsmd stop
      fi

    3. Original

      if [ -e /opt/HP/BSM ]
      then
      echo "ERROR: ($0) Installation directory of BSM 9.2x/OMi 10.0x is not empty after uninstallation. Please check if OMi/BSM was uninstalled correctly, delete the directory /opt/HP/BSM and re-run this script"
      exit 1
      fi

      Replace with

      if [ -e /opt/HP/BSM ] && [ "$(ls -A /opt/HP/BSM)" ]
      then
      echo "ERROR: ($0) Installation directory of BSM 9.2x/OMi 10.0x is not empty after uninstallation. Please check if OMi/BSM was uninstalled correctly, delete the directory /opt/HP/BSM and re-run this script"
      exit 1
      fi

Start the OMi 10.10 installation

Caution: This section only applies for the following host systems of your new OMi deployment: additional data processing server, gateway servers. Follow these steps during the appropriate phase of the BSMOMi upgrade process.

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

To start the installation, follow the steps:

  1. Open a Command Promptterminal window as a user with administrative privilegesthe root user.
  2. Change the current directory as follows:

    cd <OMiInstallationFilesDirectory>

  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 this, see HPE Operations Manager i 10.10 Installation and Upgrade Guide.

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

    ./install.sh -silent

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

Start the OMi 10.10 installation

Caution: This section only applies for the following host systems of your new OMi deployment: additional data processing server, gateway servers. Follow these steps during the appropriate phase of the BSMOMi upgrade process.

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

To start the installation, follow the steps:

  1. Open a Command Promptterminal window as a user with administrative privilegesthe root user.
  2. Change the current directory as follows:

    cd <OMiInstallationFilesDirectory>

  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 this, see HPE Operations Manager i 10.10 Installation and Upgrade Guide.

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

    ./install.sh -silent

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

Choose the preferred language

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

Windows Installer: Language Selection page

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

Note: Your selection does not affect the following:

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

  • The language used in the OMi console

Attend initialization of OMi 10.10 installation

During the initial phase, while the Initialization page is visible, the installation wizard checks the 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

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 - single server

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

  • Gateway Server. Installs the OMi gateway server.

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

Installation wizard: Product Customization page - data processing server

Click Next to continue.

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

Verify the installation directories

Verify that the OMi 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 OMi components)

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

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

Specify the installation folders

Select the following folders for installation:

  • Installation folder and data folder for the ClosedHPE shared content.

    Note:  

    • There is additional shared data in the %ALLUSERSPROFILE%\HP\BSM directory.
    • During installation of OMi 10.10, leave the default value in the Data folder for shared content text box. In the opposite case, backup data cannot be found at the restore time.
  • Installation folder for the product-specific (OMi) content.

    The path of the installation folder for OMi content must not exist yet, and its name must:

    The path of the OMi binary files directory (<OMiBinaryFilesDirectory>) must not exist yet, and its name must:

    • Be shorter than 16 characters

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

    • End with the HPBSM string

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

Installation wizard: Product Customization page - folders

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

The installation folder for shared content is not valid.

The root cause of the problem might be may be missing administrative privileges on the system, which are necessary to install OMi. 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 OMi.

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 OMi 10.10 installation

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

Installation wizard: Pre-Install Summary page

Attend OMi 10.10 installation

While the Installing page is visible, attend installation of OMi 10.10. In a virtual environment, this phase might take approximately between 30 and 60 minutes. Wait for the post-installation wizard to appear.

Installation wizard: Installing page

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

To use a later Oracle DatabasePostgreSQLMicrosoft SQL Server version that is officially supported by OMi 10.10, migrate your Oracle Database dataremote PostgreSQL databasesMicrosoft SQL Server databases now. For instructions, see the Oracle DatabasePostgreSQLMicrosoft SQL Server documentation.

Optional. Configure OMi 10.10 for Oracle Real Application Clusters

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

Choose the next steps: configuration or upgrade

When the Post-Install Configuration page of the post-installation wizard appears, the installation is complete. In the subsequent Next Steps page, you can choose to upgrade from BSM 9.25 or later or OMi 10.0x or proceed to configuring OMiproceed to configuring OMi.

Select Upgrade from BSM 9.25 and above or OMi 10.0x in the following case:to upgrade the BSMOMi server immediately.

  • If you are upgrading BSMOMi on the primary data processing server

Caution: Selecting this option during upgrade of any other server of your BSMexisting OMi environment may result in a non-functioning deployment.

Select Configure OMi in the following cases:

  • If you are upgrading BSMOMi on a non-primary data processing server

  • If you are upgrading BSMOMi on a gateway server

Select Configure OMi to configure OMi on this host system immediately.

Select Quit to leave configuration of OMi or BSMits upgrade completion for a later time.

Select Quit to leave BSMOMi upgrade completion for a later time.

Select Quit to leave configuration of OMi for a later time.

Installation wizard: Next Steps page
Installation wizard: Next Steps page

After making a selection, click Next.

Complete the installation wizard

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

Note: OMi installation wizard remains resident in the background during the configuration phase, if configuration is invoked from the post-installation wizard.

Installation wizard: Install Complete (Installation Complete) page

Click Done to conclude the installation.

Start the upgrade wizard (non-silent) Specify your original product and choose the upgrade type

By running the script in silent mode, you uninstalled your previous software version and installed OMi 10.10.

To continue with the upgrade, run the upgrade wizard as root user. Note that the upgrade wizard cannot run in silent mode. Make sure that the system from which you are upgrading OMi hosts an implementation of X Windows System.
cd <OMiInstallationFilesDirectory> upgrade.bat/opt/HP/BSM/bin/upgrade_wizard_run.sh

In the Upgrade Settings page:

  • Select the original product that you will upgrade to OMi 10.10:

    BSMOMi 10.0x

  • Choose the type of upgrade you want to perform:

    Click In-place upgrade to upgrade from BSMan earlier OMi version to OMi10.10 on the same host systems. An in-place upgrade involves installing OMi 10.10 on the same servers and database schemas as BSMthe earlier OMi version. As the previously used product needs to be uninstalled first, this upgrade type therefore results in greater downtime.

    Click Side-by-side upgrade to migrate from BSMan earlier OMi version to OMi10.10 on new host systems. A side-by-side upgrade involves installing OMi on different systems and database schemas to allow the original servers to continue functioning while the migration is in process.

Upgrade wizard: Upgrade Settings page
Upgrade wizard: Upgrade Settings page

Caution: Before proceeding to the next page of the wizard, make sure that on all host systems of your new OMi 10.10 deployment:

  • OMi is installed but not configured

  • OMi is disabled (all servicesprocesses are stopped)

Click Next to continue.

Start the upgrade wizard (non-silent) Specify your original product and choose the upgrade type

By running the script in silent mode, you uninstalled your previous software version and installed OMi 10.10.

To continue with the upgrade, run the upgrade wizard as root user. Note that the upgrade wizard cannot run in silent mode. Make sure that the system from which you are upgrading OMi hosts an implementation of X Windows System.
cd <OMiInstallationFilesDirectory> upgrade.bat/opt/HP/BSM/bin/upgrade_wizard_run.sh

In the Upgrade Settings page:

  • Select the original product that you will upgrade to OMi 10.10:

    BSMOMi 10.0x

  • Choose the type of upgrade you want to perform:

    Click In-pace upgrade to upgrade from BSMan earlier OMi version to OMi10.10 on the same host systems. An in-place upgrade involves installing OMi 10.10 on the same servers and database schemas as BSMthe earlier OMi version. As the previously used product needs to be uninstalled first, this upgrade type therefore results in greater downtime.

    Click Side-by-side upgrade to migrate from BSMan earlier OMi version to OMi10.10 on new host systems. A side-by-side upgrade involves installing OMi on different systems and database schemas to allow the original servers to continue functioning while the migration is in process.

Upgrade wizard: Upgrade Settings page
Upgrade wizard: Upgrade Settings page

Caution: Before proceeding to the next page of the wizard, make sure that on all host systems of your new OMi 10.10 deployment:

  • OMi is installed but not configured

  • OMi is disabled (all servicesprocesses are stopped)

Click Next to continue.

Optional. Start the upgrade wizard manually

If you previously quit the OMi installation wizard without selecting the Upgrade from BSM 9.25 and above or OMi 10.0x option (or installed OMi silently), you can manually start the upgrade wizard later.

Note: The OMi upgrade wizard must be used on:

  • The host system of a single-server BSMOMi deployment

  • The host system of the primary data processing server in a distributed BSMOMi deployment

To manually start the upgrade wizard, follow the steps:

  1. Open a Command Prompt windowcommand shell as a user with administrative privilegesthe root user.

  2. Change the current directory as follows:

    cd /opt/HP/BSM/bin<OMi_HOME>\bin

  3. Run the following command:

    ./upgrade_wizard_run.shupgrade_wizard_run.bat

    The upgrade wizard starts.

Configure event forwarding in BSMoriginal OMi environment

Attend initialization of the upgrade wizard

The upgrade wizard performs the following operations:

  • Migrates data from replicas of the BSMoriginal OMi databases

  • Migrates your OMi configuration

  • Guides you through the manual procedures that are part of the main upgrade process

The upgrade wizard gives you an option of skipping some steps and completing them later by manually restarting the wizard. You can do this as many times as necessary. For example, if you do not have time to perform the upgrade of OMi configuration, you can skip it and complete the rest of the upgrade process. When you manually restart the wizard, it resumes from the your previous progress that is saved. Make sure to proceed through the entire upgrade process from start to finish before starting to use OMi 10.10.

Replicate the database scheamasdatabasesCopy the database backup image

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

Replicate the following BSMoriginal OMidatabase schemasdatabases onto the new OMi database host system:

  • Management

  • Event

  • RTSM

  • RTSM History

The database schemadatabase replicas will be used by the staging environment, upgraded, and eventually—except for the RTSM History database— used as your OMi10.10 databases. Other BSM database schemasdatabases do not need replication, as they are not used in OMi and therefore not migrated.

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

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

%OvDataDir%\backup\OMi10cfg-backup.zip

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

The included database schema replicas will be used by the staging environment, upgraded, and eventually used as your OMi10.10 databases.

Upgrade wizard: Upgrade Settings page

 

Before you proceed to the next step, the database schemadatabase replicas must be available on the new OMi database host system.

Click Next to continue.

Connect to the originalreplicated database schemasdatabasesConnect to the original database schemasRestore the database schemas

In the Database Connection page, choose the database management system that is used in BSMOMi 10.0x to store the database schemasdatabases (Management, RTSM, 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.

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 HPE Operations Manager i Virtual Appliance, click Advanced settings, and then change the RTSM database name from rtsm to cmdb.

Click Next to continue.

Specify administrative database access credentials

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

Upgrade wizard: Database Connection (SQL Server Settings) page
Upgrade wizard: Database Connection (Oracle Database Settings) page

Click Next to continue.

Start the schema upgrade

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

Caution: If you cancel the database schema upgrade and you need to perform it later, before restarting the upgrade wizard remove the marker files that may have been created during the process. These files reside in the %TEMP% * folder/tmp directory and have the .marker file name extension.

* This is a user environment variable

Upgrade wizard: Schema Upgrade Execution page

Tip: The schema upgrade may take a long time. You may want to use this time to familiarize yourself with the OMi 10.10 documentation? The documentation is installed on each host system at the following locations:

  • OMi Help:

    <OMi_HOME>\AppServer\webapps\site.war\amdocs\eng\doc_lib\OMi_Help.htm

    /opt/HP/BSM/AppServer/webapps/site.war/amdocs/eng/doc_lib/OMi_Help.htm

  • OMi guides:

    <OMi_HOME>\AppServer\webapps\site.war\amdocs\eng\pdfs

    /opt/HP/BSM/AppServer/webapps/site.war/amdocs/eng/pdfs

Configure the TLS setup

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

Upgrade wizard: TLS Setup page

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

Note: For maximum security, HPE recommends to use certificates that were issued by the certification authority of your company.

If you choose to use OMi-generated certificates, make sure to establish trust in the web browser from which you will log in to OMi. For instructions on how to do that, see the "Establishing Trust in the Browser" section in the "Using TLS in OMi" chapter of the OMi Administration Guide.

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

Click Next.

Configure general OMi connection settings

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

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

Note: The configuration wizard displays the Connection Settings page only when configuring a single-server or gateway server installation. The page is not shown when configuring a data processing server.

Upgrade wizard: Connection Settings page
Upgrade wizard: Connection Settings page

Web server. Choose the web server you want to use with your OMi deployment:

  • Apache HTTP Server. This is the default web server. OMi installs Apache HTTP Server on all gateway servers during the installation. This is the web server that must be used in Linux environments.

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

  • Microsoft IIS. To use a Microsoft IIS web server in a Windows environment, first install the web server on all gateway servers. The configuration wizard only lists web servers that are already installed on the system you are configuring. During OMi configuration, the IIS settings are automatically configured to work with OMi.

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

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

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

OMi URL. By default, users access OMi 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 OMi URL text box, for example: https://omiweb.company.com:8000.

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

Click Next.

Optional. Integrate BSM with OMi

The APM Integration page asks you for the details of your BSM environment so that the upgrade wizard can create a connected server of the APM type in preparation for the Application Performance Manager (APM) integration. For instructions on how to complete the integration after the upgrade, see the OMi Integrations Guide.

The upgrade wizard extracts the required information from the database. To enable the integration, select Enable APM Integration and verify or update the data in the text boxes as required. Then click Next to continue.

Deploy management packs

In the Management Packs page, you can select the HPE OMi Management Packs to install in your OMi deployment. Dependencies between management packs are resolved automatically. You can choose not to install dependent management packs. If you do so, some functionality may not be available in the installed packs.

Upgrade wizard: Management Packs page

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

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

To install management packs after the first configuration, start the configuration wizard again and select the management packs you want to install. With a distributed deployment, start the configuration wizard first on the data processing servers and subsequently on all gateway servers. Note though that the Management Packs page does not appear during the gateway server configuration.

Tip: HPE recommends to disable OMi before starting the configuration wizard, and to enable it after the configuration:

  • Windows Server 2008: Select Start > Programs > HPE Operations Manager i > Administration > Disable Operations Manager i.

  • Windows Server 2012: Press Ctrl + Esc and start typing Disable Operations Manager i. Then click Disable Operations Manager i in the search results.

Run the following command:

/opt/HP/BSM/scripts/run_hpbsm stop

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

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

Once installed, management packs cannot be removed. They appear in the Management Packs page but are not available for removal.

For details on the management packs that are bundled with OMi, see the OMi Release Notes. To update a management pack to a later version than the one included with OMi, download its installation package from the HPE Live Network Content Marketplace web site and install the management pack manually. You can also download and install additional management packs not included with OMi. However, your updates are not reflected in the OMi 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 OMi environment and then click Next.

Configure the server deployment

In the Server Deployment page, you can enable User Engagement and define the expected size of the environment monitored by OMi.

Upgrade wizard: Server Deployment page

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

  1. Optional. Enable User Engagement.

    The innovative User Engagement feature applies game dynamics to add extra stimulation to OMi users by providing business-enhancing challenges, accelerating operations bridge efficiency and user know-how. Successful progress through the various activities is rewarded with achievements and real-time notifications of great performance, helping to provide extra motivation to better engage with OMi which improves users' performance in their daily work. Timelines are available to record each user’s progress and collection of achievements.

    Tip: If you do not want to enable User Engagement now, you can enable it later in the infrastructure settings (Administration > Setup and Maintenance > Infrastructure Settings > Applications > Operations Management – User Engagement > Enable User Engagement).

  2. Select the Number of monitored nodes that send events to OMi. This includes any nodes that are present as CIs in OMi and that send events to OMi (for example, nodes connected to HPE Operations Manager (OM), nodes directly connected to OMi, and target connectors).

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

  4. Click Next.

Configure the license

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

Upgrade wizard: License page

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.

Note: You can also update your licenses after OMi is installed. in the License Management page in OMi.

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

Click Next.

Configure the login settings

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

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

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

Upgrade wizard: Update Environment - Login Settings page

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

JMX password, Confirm. Type the password to be used by the OMi administrator for all OMi 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 OMi environment.

Click Next.

Update the environment and start OMi

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

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

Upgrade wizard: Update Environment - Start OMi page

 

To enable OMi on the local system:

  • Windows Server 2008: Select Start > Programs > HPE Operations Manager i > Administration > Enable Operations Manager i.

  • Windows Server 2012: Press Ctrl + Esc and start typing Enable Operations Manager i. Then click Enable Operations Manager i in the search results.

To enable OMi on the local system, run the following command:

/opt/HP/BSM/scripts/run_hpbsm start

Before you proceed, check whether OMi is running. Click Open Status Page in the Start OMi wizard page.

Alternatively, perform the following on the OMi host system:

  • Windows Server 2008: Select Start > Programs > HP Operations Manager i > Administration > HP Operations Manager i Status.

  • Windows Server 2012: Press Ctrl + Esc and start typing HP Operations Manager i Status. Then click HP Operations Manager i Status in the search results.

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

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

When OMi is running, click Next to continue.

Upgrade the configuration

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

Upgrade wizard: Configuration Upgrade page

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.

Review the upgrade summary and conclude the upgrade

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

Upgrade wizard: Summary - Upgrade Wizard Summary page

Restart OMi processes (disable and enable OMi) on the OMi host systemprimary data processing server.

Click Finish to close the upgrade wizard.

Optional. Start the configuration wizard manually

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

If you previously quit the OMi installation wizard without selecting the Configure OMi option (or installed OMi silently), you can manually start the configuration wizard later.

Note: The OMi configuration wizard must be used on:

  • All host systems of new OMi installations

  • The host systems of the additional data processing server and all gateway servers (in distributed BSMOMi deployments)

You must specify the same database and connection parameters for each OMi server, either the servers are at the same location or geographically separated.

You can modify any configuration settings at a later time. To change a setting, start the configuration wizard again. OMi must be disabled before the wizard is restarted.

To manually start the configuration wizard, follow the steps:

  1. If you are not starting the wizard for the first time, disable OMi.

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

  2. Do one of the following:

    • Start the wizard from the operating system desktop:

      • Windows Server 2008: Select Start > Programs > HPE Operations Manager i > Administration > Configure Operations Manager i.

      • Windows Server 2012: Press Ctrl + Esc and start typing Configure Operations Manager i. Then click Configure Operations Manager i in the search results.

    • Start the wizard from the command line:

      1. Open a Command Prompt window as a user with administrative privileges.

      2. Change the current directory as follows:

        cd <OMi_HOME>\bin

      3. Run the following command:

        config-server-wizard.bat

To manually start the configuration wizard, follow the steps:

  1. If you are not starting the wizard for the first time, disable OMi.

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

  2. Open a command shell as the root user.

  3. Change the current directory as follows:

    cd /opt/HP/BSM/bin

  4. Run the following command:

    ./config-server-wizard.sh.

    The configuration wizard starts.

Optional. Start the configuration wizard manually

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

If you previously quit the OMi installation wizard without selecting the Configure OMi option (or installed OMi silently), you can manually start the configuration wizard later.

Note: The OMi configuration wizard must be used on:

  • All host systems of new OMi installations

  • The host systems of the additional data processing server and all gateway servers (in distributed BSMOMi deployments)

You must specify the same database and connection parameters for each OMi server, either the servers are at the same location or geographically separated.

You can modify any configuration settings at a later time. To change a setting, start the configuration wizard again. OMi must be disabled before the wizard is restarted.

To manually start the configuration wizard, follow the steps:

  1. If you are not starting the wizard for the first time, disable OMi.

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

  2. Do one of the following:

    • Start the wizard from the operating system desktop:

      • Windows Server 2008: Select Start > Programs > HPE Operations Manager i > Administration > Configure Operations Manager i.

      • Windows Server 2012: Press Ctrl + Esc and start typing Configure Operations Manager i. Then click Configure Operations Manager i in the search results.

    • Start the wizard from the command line:

      1. Open a Command Prompt window as a user with administrative privileges.

      2. Change the current directory as follows:

        cd <OMi_HOME>\bin

      3. Run the following command:

        config-server-wizard.bat

To manually start the configuration wizard, follow the steps:

  1. If you are not starting the wizard for the first time, disable OMi.

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

  2. Open a command shell as the root user.

  3. Change the current directory as follows:

    cd /opt/HP/BSM/bin

  4. Run the following command:

    ./config-server-wizard.sh.

    The configuration wizard starts.

Optional. Generate the database creation scripts

OMi can automatically set up new databases for you during the configuration, or you can connect to manually created, already existing databases. You may need to ask the database administrator to manually create the databases for you, if you as the OMi installing user do not have permissions to create the databases on the remote database server.

After the OMi installation, but before the configuration, the OMi installing user on the gateway server generates the scripts to create the required objects to populate these databases. The database administrator then runs the scripts on the database server to create these objects. When the databases are ready, you can continue with the OMi configuration. For details on installing and configuring a remote database server, see the OMi Database Guide.

OMi requires the following databases:

  • Management. For storage of system-wide and management-related metadata.

  • RTSM (Run-time Service Model). For storage of configuration information that is gathered from various HPE and third-party applications and tools.

  • Event. For storage of events and related data, such as annotations, as well as for storage of configuration data, such as event correlation rules.

Run the following commands to generate the database creation scripts:

  1. Register database extensions by running the following command:

    <OMi_HOME>\AppServer\webapps\site.war\DataBases\Postgres_DB_Utils\postgres_database_extensions.sql

    /opt/HP/BSM/AppServer/webapps/site.war/DataBases/ORA_DB_Utils/postgres_database_extensions.sql

  2. Generate the Management database script:

    <OMi_HOME_GW>\dbverify\bin\generate_create_script.bat EE <OutputFileName>.sql SqlServerOraclePostgres Management

    /opt/HP/BSM/dbverify/bin/generate_create_script.sh EE <OutputFileName>.sql SqlServerOraclePostgres Management

  3. Run the management schema SQL script:

    1. Connect to the management schema and run the script generated in step 1 to deploy the management objects.

    2. Run the following script:

      <OMi_HOME_GW>\AppServer\webapps\site.war\DataBases\ORA_DB_Utils\management_ora_inserts.sql

      /opt/HP/BSM/AppServer/webapps/site.war/DataBases/ORA_DB_Utils/management_ora_inserts.sql

    3. When the script is finished running, commit the change.

  4. Run the Management database SQL script:

    1. Create the Management database. For details, see the OMi Database Guide.

    2. Connect to the Management database and run the script generated in the previous section to deploy the management objects.

    3. Run the following script from the objects scripts directory:

      management_sql_inserts.sql

    1. Connect to the Management database, and then run the generated SQL script to deploy the management objects.

    2. Run the following script:

      <OMi_HOME>\AppServer\webapps\site.war\DataBases\Postgres_DB_Utils\management_postgres_inserts.sql

      /opt/HP/BSM/AppServer/webapps/site.war/DataBases/ORA_DB_Utils/management_postgres_inserts.sql

  5. No scripts are necessary to create the objects to populate the RTSM database.

  6. Generate the Event database script:

    <OMi_HOME>\opr\bin\opr-schema-script-generator.bat -d SQLOraclePostgres -o <OutputFileName>.sql

    /opt/HP/BSM/opr/bin/opr-schema-script-generator.sh -d SQLOraclePostgres -o <OutputFileName>.sql

  7. Make the generated scripts available to the database administrator for running on the database server. For details on running these scripts, see the OMi Database Guide.

  8. Continue with the OMi configuration after the databases have been created.

Make proper selection based on the chosen setup type

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

After the configuration wizard starts, the Configuration Options page displays.

Configuration wizard: Configuration Options page
Configuration wizard: Configuration Options page

In the Configuration Options page, click Custom configuration, based on new or existing database. This option displays all wizard pages, enabling you to specify custom values for all OMi configuration settings. Then click Next to continue.

The express option configures OMi using the following default settings:

  • Embedded Apache HTTP Server

  • Embedded PostgreSQL database

  • HTTPS for the OMi web server and JMX console (with OMi-generated certificates)

  • User Engagement enabled

  • HPE OMi Management Pack for Infrastructure installed

  • A single password that you specify for the OMi administrator, OMi JMX console, and database users. To change the default password for each user later, see Optional. Change passwords.

HPE recommends the express deployment for environments where you want to demonstrate or evaluate OMi or for small environments with less than 2,000 nodes.

In the Configuration Options page, click Express configuration with default values to configure OMi using default settings. Specify a global password that will be used for the OMi web console, the JMX console, and database users, and then click Next.

Make proper selection based on the chosen setup type

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

After the configuration wizard starts, the Configuration Options page displays.

Configuration wizard: Configuration Options page
Configuration wizard: Configuration Options page

In the Configuration Options page, click Custom configuration, based on new or existing database. This option displays all wizard pages, enabling you to specify custom values for all OMi configuration settings. Then click Next to continue.

The express option configures OMi using the following default settings:

  • Embedded Apache HTTP Server

  • Embedded PostgreSQL database

  • HTTPS for the OMi web server and JMX console (with OMi-generated certificates)

  • User Engagement enabled

  • HPE OMi Management Pack for Infrastructure installed

  • A single password that you specify for the OMi administrator, OMi JMX console, and database users. To change the default password for each user later, see Optional. Change passwords.

HPE recommends the express deployment for environments where you want to demonstrate or evaluate OMi or for small environments with less than 2,000 nodes.

In the Configuration Options page, click Express configuration with default values to configure OMi using default settings. Specify a global password that will be used for the OMi web console, the JMX console, and database users, and then click Next.

Make proper selections based on the chosen setup type

After the configuration wizard starts, the Configuration Options page displays.

Configuration wizard: Configuration Options page

The express option configures OMi using the following default settings:

  • Embedded Apache HTTP Server

  • Embedded PostgreSQL database

  • HTTPS for the OMi web server and JMX console (with OMi-generated certificates)

  • User Engagement enabled

  • HPE OMi Management Pack for Infrastructure installed

  • A single password that you specify for the OMi administrator, OMi JMX console, and database users. To change the default password for each user later, see Optional. Change passwords.

HPE recommends the express deployment for environments where you want to demonstrate or evaluate OMi or for small environments with less than 2,000 nodes.

In the Configuration Options page, click Express configuration with default values to configure OMi using default settings. Specify a global password that will be used for the OMi web console, the JMX console, and database users, and then click Next.

Make proper selections based on the chosen setup type

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

After the configuration wizard starts, the Configuration Options page displays.

Configuration wizard: Configuration Options page
Configuration wizard: Configuration Options page

In the Configuration Options page, click Custom configuration. This option displays all wizard pages, enabling you to specify custom values for all OMi configuration settings. Then click Next to continue.

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

  1. Create a non-root user account (if you have not done so already) on all OMi 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 /etc/security/limits.d/90-nproc.conf file:

    <UserName> soft nproc unlimited

    Replace <UserName> with the non-root user account.

  2. In the Configuration Options page, click Run OMi processes as non-root user to configure OMi to run by using a different user account.

  3. Type the User name of the non-root user account you created earlier.

  4. Click Next.

Make proper selections based on the chosen setup type

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

After the configuration wizard starts, the Configuration Options page displays.

Configuration wizard: Configuration Options page
Configuration wizard: Configuration Options page

In the Configuration Options page, click Custom configuration. This option displays all wizard pages, enabling you to specify custom values for all OMi configuration settings. Then click Next to continue.

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

  1. Create a non-root user account (if you have not done so already) on all OMi 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 /etc/security/limits.d/90-nproc.conf file:

    <UserName> soft nproc unlimited

    Replace <UserName> with the non-root user account.

  2. In the Configuration Options page, click Run OMi processes as non-root user to configure OMi to run by using a different user account.

  3. Type the User name of the non-root user account you created earlier.

  4. Click Next.

Configure the database settings

In the Database Settings page, you can select the relational database management system you want to use with OMi, create new database schemas, or connect to existing ones.

Configuration wizard: Database Settings page

Note: When entering database parameters, use only alphanumeric characters.

  1. Choose whether you want to connect OMi to already existing database schemas or if you want OMi to create new database schemas for you:

    • Connect to an existing database or user schema. You generally use this option in the following scenarios:

      • When connecting to database schemas you manually created directly on the Oracle Database server.

      • When installing OMi in a distributed environment and running the configuration wizard on servers subsequent to the first server. In this case, you should have run the wizard on the data processing server first and on the gateway servers later.

    • Create a new database or user schema. Use this option when you want OMi to create new database schemas for you on the Oracle Database server.

  2. Select Oracle Server.

  3. In the Host field, type the hostname of the system on which Oracle Database is installed.

    Caution: There is a 26-character limit for the Host field while running the configuration wizard. If using a hostname without a domain name is not appropriate in your environment, perform one of these workarounds:

    • Use the IP address instead of the hostname in the Host field.

    • Map the hostname to the IP address in the hosts file. Use the hostname you mapped in the Host field.

  4. The Port field automatically displays the Oracle Database listener default port 1521.

  5. In the SID field, type the Oracle system identifier (SID) that uniquely identifies the Oracle Database instance being used by OMi.

  6. If you are connecting to an existing database, specify the password of the database schemas.

  7. If you are creating new database schemas, specify the following:

    • Password of the database schemas.

    • Name and password of a user with administrative permissions on Oracle Database server (for example, a System user).

    • Tablespaces for every schema:

      • Default tablespace: Name of the dedicated default tablespace you created for the user schema.

      • Temporary tablespace: Name of the temporary tablespace you assigned to the user schema. The default Oracle Database temporary tablespace is temp.

  8. In the SID field, type the Oracle system identifier (SID) that uniquely identifies the Oracle Database instance being used by OMi.

  9. OMi requires the following database schemas:

    • Management. For storage of system-wide and management-related metadata.

    • RTSM (Run-time Service Model). For storage of configuration information that is gathered from various HPE and third-party applications and tools.

    • Event. For storage of events and related data, such as annotations, as well as for storage of configuration data, such as event correlation rules.

    Type a name for each database schema. The names must be unique even when the databases reside on different servers.

    Distributed deployment: You connect to the database schemas that you created during the installation of the first data processing server. After you have connected to the Management database, by specifying the same connection parameters that you set during the installation of the first server, the connection parameters for the other database schemas appear by default. Not all database schemas appear when running on the gateway server.

  10. Click Next.

Configure the database settings

In the Database Settings page, you can select the relational database management system you want to use with OMi, create new databases, or connect to existing ones.

Configuration wizard: Database Settings page

Note: When entering database parameters, use only alphanumeric characters.

  1. Choose whether you want to connect OMi to an already existing database or if you want OMi to create a new database for you:

    • Connect to an existing database or user schema. You generally use this option in the following scenarios:

      • When connecting to a database you manually created directly on the Microsoft SQL Server system.

      • When installing OMi in a distributed environment and running the utility on servers subsequent to the first server. In this case, you should have run the wizard on the data processing server first and on the gateway servers later.

    • Create a new database or user schema. Use this option when you want OMi to create new databases for you on the Microsoft SQL Server system.

  2. Select SQL Server.

  3. In the Host field, type the hostname of the system on which Microsoft SQL Server is installed. If you are connecting to a non-default Microsoft SQL Server instance in the dynamic mode, enter the following: <Hostname>\<InstanceName>.

    Caution: There is a 26-character limit for the Host field while running the configuration wizard. If using a hostname without a domain name is not appropriate in your environment, perform one of these workarounds:

    • Use the IP address instead of the hostname in the Host field.

    • Map the hostname to the IP address in the hosts file. Use the hostname you mapped in the Host field.

  4. The Port field automatically displays the Microsoft SQL Server’s TCP/IP default port 1433. Change the port number if one of the following applies:

    • If you connect to a named instance in the static mode, enter the port number.

    • If you connect to a named instance in the dynamic mode, change the port number to 1434. This port can dynamically listen to the correct database port.

  5. Choose the Authentication type you want to use for connecting to the Microsoft SQL Server database:

    • Windows. (on Microsoft Windows systems only) You can create and connect to a database using Windows operating system authentication instead of Microsoft SQL Server authentication. To do so, first ensure that the Windows user account running the OMi service has the necessary permissions to access the Microsoft SQL Server database. For information on adding a Windows user account to Microsoft SQL Server, see "Using Windows Authentication to Access Microsoft SQL Server Databases" in the OMi Database Guide.

      In Linux environments, Windows authentication is not supported.

    • SQL Server. The user name and password of a user with administrative rights on Microsoft SQL Server. A password must be supplied.

      For security reasons, HPE recommends not to use the default sa user.

  6. OMi requires the following databases:

    • Management. For storage of system-wide and management-related metadata.

    • RTSM (Run-time Service Model). For storage of configuration information that is gathered from various HPE and third-party applications and tools.

    • Event. For storage of events and related data, such as annotations, as well as for storage of configuration data, such as event correlation rules.

    Type a name for each database schema. The names must be unique even when the databases reside on different servers.

    Distributed deployment: You connect to the databases that you created during the installation of the first data processing server. After you have connected to the Management database, by specifying the same connection parameters that you set during the installation of the first server, the connection parameters for the other databases appear by default. Not all databases appear when running on the gateway server.

  7. Click Next.

Configure the database settings

In the Database Settings page, you can select the relational database management system you want to use with OMi, create new database schemas, or connect to existing ones.

Configuration wizard: Database Settings page

Note: When entering database parameters, use only alphanumeric characters.

  1. Choose whether you want to connect OMi to already existing database schemas or if you want OMi to create new database schemas for you:

    • Connect to existing. You generally use the Connect to existing option in the following scenarios:

      • When connecting to database schemas you manually created directly on the PostgreSQL server.

      • When installing OMi in a distributed environment and running the utility on servers subsequent to the first server. In this case, you should have run the wizard on the data processing server first and on the gateway servers later.

    • Create new. Use this option when you want OMi to create new database schemas for you on the PostgreSQL server.

  2. Select Postgres.

  3. In the Host field, type the hostname of the system on which PostgreSQL is installed.

    Caution: There is a 26-character limit for the Host field while running the configuration wizard. If using a hostname without a domain name is not appropriate in your environment, perform one of these workarounds:

    • Use the IP address instead of the hostname in the Host field.

    • Map the hostname to the IP address in the hosts file. Use the hostname you mapped in the Host field.

  4. The Port field automatically displays the PostgreSQL default port 5432.

  5. Optional. Click Use SSL to encrypt the communication with PostgreSQL.

    The PostgreSQL server must be started with SSL enabled and must provide a certificate for use by OMi. For details on configuring PostgreSQL for SSL, see the PostgreSQL documentation.

  6. If you are connecting to existing database schemas, specify the user name and password of the database schemas.

  7. If you are creating new database schemas, specify the following:

    • User name and password of the database schemas.

    • User name and password of an OMi administrative user to access the PostgreSQL database.

  8. OMi requires the following database schemas:

    • Management. For storage of system-wide and management-related metadata.

    • RTSM (Run-time Service Model). For storage of configuration information that is gathered from various HPE and third-party applications and tools.

    • Event. For storage of events and related data, such as annotations, as well as for storage of configuration data, such as event correlation rules.

    Type a name for each database schema. The names must be unique even when the databases reside on different servers.

    Distributed deployment: You connect to the database schemas that you created during the installation of the first data processing server. After you have connected to the Management database, by specifying the same connection parameters that you set during the installation of the first server, the connection parameters for the other databases appear by default. Not all databases appear when running on the gateway server.

  9. Click Next.

Configure the database settings

In the Database Settings page, you can select the relational database management system you want to use with OMi, create new database instances, or connect to existing ones.

Configuration wizard: Database Settings page

The embedded PostgreSQL database runs on the data processing server in distributed deployments:

  • Data processing server configuration. When configuring the embedded PostgreSQL database on the data processing server, select Embedded Postgres and specify the password of an OMi administrative user to access the PostgreSQL database.

  • Gateway server configuration. When configuring a gateway server, select PostgresEmbedded again, enter the name of the data processing server in the Host field, and specify the password of the OMi administrative user with access to the PostgreSQL database.

To configure the embedded PostgreSQL database on your single-server installation, select PostgresEmbedded and specify the password of an OMi administrative user to access the PostgreSQL database. Then click Next to continue.

Connect to the upgraded database

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

In the Database Settings page, you can select and connect to the upgraded database you want to use with OMi:

  1. Click Connect to an existing database or user schema.

  2. Select Oracle Server.

  3. Select SQL Server.

  4. Select Embedded Postgres.

  5. Select Postgres.

  6. Complete the Connection fields and specify the database namesschema names.

  7. Click Next.

Configure the TLS setup

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

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

Configuration wizard: TLS Setup page

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

Note: For maximum security, HPE recommends to use certificates that were issued by the certification authority of your company.

If you choose to use OMi-generated certificates, make sure to establish trust in the web browser from which you will log in to OMi. For instructions on how to do that, see the "Establishing Trust in the Browser" section in the "Using TLS in OMi" chapter of the OMi Administration Guide.

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

Configure client certificate authentication

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

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

Caution: Do not enable client certificate authentication if you are configuring OMi for the first time. Before enabling client-certificate authentication, OMi must be configured and a super-admin user must exist.

Configuration wizard: Client Certificate Authentication page

Configure general OMi connection settings

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

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

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

Note: The configuration wizard displays the Connection Settings page only when configuring a single-server or gateway server installation. The page is not shown when configuring a data processing server.

Configuration wizard: Connection Settings page

Web server. Choose the web server you want to use with your OMi deployment:

  • Apache HTTP Server. This is the default web server. OMi installs Apache HTTP Server on all gateway servers during the installation. This is the web server that must be used in Linux environments.

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

  • Microsoft IIS. To use a Microsoft IIS web server in a Windows environment, first install the web server on all gateway servers. The configuration wizard only lists web servers that are already installed on the system you are configuring. During OMi configuration, the IIS settings are automatically configured to work with OMi.

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

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

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

OMi URL. By default, users access OMi 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 OMi URL text box, for example: https://omiweb.company.com:8000.

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

Note: You cannot change the OMi URL in the configuration wizard after the initial configuration. Instead, change the setting Default Virtual Gateway Server for Data Collectors URL in Infrastructure Settings > Foundations > Platform Administration.

Click Next.

Configure general OMi connection settings

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

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

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

Note: The configuration wizard displays the Connection Settings page only when configuring a single-server or gateway server installation. The page is not shown when configuring a data processing server.

Configuration wizard: Connection Settings page

Web server. Choose the web server you want to use with your OMi deployment:

  • Apache HTTP Server. This is the default web server. OMi installs Apache HTTP Server on all gateway servers during the installation. This is the web server that must be used in Linux environments.

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

  • Microsoft IIS. To use a Microsoft IIS web server in a Windows environment, first install the web server on all gateway servers. The configuration wizard only lists web servers that are already installed on the system you are configuring. During OMi configuration, the IIS settings are automatically configured to work with OMi.

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

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

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

OMi URL. By default, users access OMi 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 OMi URL text box, for example: https://omiweb.company.com:8000.

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

Note: You cannot change the OMi URL in the configuration wizard after the initial configuration. Instead, change the setting Default Virtual Gateway Server for Data Collectors URL in Infrastructure Settings > Foundations > Platform Administration.

Click Next.

Configure the license

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

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

Configuration wizard: License page

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.

Note: You can also update your licenses after OMi is installed in the License Management page in OMi.

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

Click Next.

Configure the license

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

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

Configuration wizard: License page

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.

Note: You can also update your licenses after OMi is installed in the License Management page in OMi.

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

Click Next.

Configure the login settings

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

In the Login Settings page, you can set the passwords of the OMi users.

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

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

Configuration wizard: Login Settings page

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

JMX password, Confirm. Type the password to be used by the OMi administrator for all OMi 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 OMi environment.

Click Next.

Configure the login settings

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

In the Login Settings page, you can set the passwords of the OMi users.

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

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

Configuration wizard: Login Settings page

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

JMX password, Confirm. Type the password to be used by the OMi administrator for all OMi 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 OMi environment.

Click Next.

Configure the server deployment

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

In the Server Deployment page, you can enable User Engagement and define the size of your OMi deployment.

Configuration wizard: Server Deployment page

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

  1. Optional. Enable User Engagement.

    The innovative User Engagement feature applies game dynamics to add extra stimulation to OMi users by providing business-enhancing challenges, accelerating operations bridge efficiency and user know-how. Successful progress through the various activities is rewarded with achievements and real-time notifications of great performance, helping to provide extra motivation to better engage with OMi which improves users' performance in their daily work. Timelines are available to record each user’s progress and collection of achievements.

    Tip: If you do not want to enable User Engagement now, you can enable it later in the infrastructure settings (Administration > Setup and Maintenance > Infrastructure Settings > Applications > Operations Management – User Engagement > Enable User Engagement).

  2. Select the Number of monitored nodes that send events to OMi. This includes any nodes that are present as CIs in OMi and that send events to OMi (for example, nodes connected to HP Operations Manager (OM), nodes directly connected to OMi, and target connectors).

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

  4. Click Next.

Configure the server deployment

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

In the Server Deployment page, you can enable User Engagement and define the size of your OMi deployment.

Configuration wizard: Server Deployment page

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

  1. Optional. Enable User Engagement.

    The innovative User Engagement feature applies game dynamics to add extra stimulation to OMi users by providing business-enhancing challenges, accelerating operations bridge efficiency and user know-how. Successful progress through the various activities is rewarded with achievements and real-time notifications of great performance, helping to provide extra motivation to better engage with OMi which improves users' performance in their daily work. Timelines are available to record each user’s progress and collection of achievements.

    Tip: If you do not want to enable User Engagement now, you can enable it later in the infrastructure settings (Administration > Setup and Maintenance > Infrastructure Settings > Applications > Operations Management – User Engagement > Enable User Engagement).

  2. Select the Number of monitored nodes that send events to OMi. This includes any nodes that are present as CIs in OMi and that send events to OMi (for example, nodes connected to HP Operations Manager (OM), nodes directly connected to OMi, and target connectors).

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

  4. Click Next.

Deploy management packs

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

In the Management Packs page, you can select the management packs to install in your OMi deployment. Dependencies between management packs are resolved automatically. You can choose not to install dependent management packs. However, some functionality will then be unavailable in the installed packs.

Configuration wizard: Management Packs page

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

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

To install management packs after the first configuration, start the configuration wizard again and select the management packs you want to install. With a distributed deployment, start the configuration wizard first on the data processing servers and subsequently on all gateway servers. Note though that the Management Packs page does not appear during the gateway server configuration.

Tip: HPE recommends to disable OMi before starting the configuration wizard, and to enable it after the configuration:

  • Windows Server 2008: Select Start > Programs > HPE Operations Manager i > Administration > Disable Operations Manager i.

  • Windows Server 2012: Press Ctrl + Esc and start typing Disable Operations Manager i. Then click Disable Operations Manager i in the search results.

Run the following command:

/opt/HP/BSM/scripts/run_hpbsm stop

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

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

Once installed, management packs cannot be removed. They appear in the Management Packs page but are not available for removal.

For details on the management packs that are bundled with OMi, see the OMi Release Notes. To update a management pack to a later version than the one included with OMi, download its installation package from the HPE Live Network Content Marketplace web site and install the management pack manually. You can also download and install additional management packs not included with OMi. However, your updates are not reflected in the OMi 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 OMi environment and then click Next.

Deploy management packs

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

In the Management Packs page, you can select the management packs to install in your OMi deployment. Dependencies between management packs are resolved automatically. You can choose not to install dependent management packs. However, some functionality will then be unavailable in the installed packs.

Configuration wizard: Management Packs page

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

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

To install management packs after the first configuration, start the configuration wizard again and select the management packs you want to install. With a distributed deployment, start the configuration wizard first on the data processing servers and subsequently on all gateway servers. Note though that the Management Packs page does not appear during the gateway server configuration.

Tip: HPE recommends to disable OMi before starting the configuration wizard, and to enable it after the configuration:

  • Windows Server 2008: Select Start > Programs > HPE Operations Manager i > Administration > Disable Operations Manager i.

  • Windows Server 2012: Press Ctrl + Esc and start typing Disable Operations Manager i. Then click Disable Operations Manager i in the search results.

Run the following command:

/opt/HP/BSM/scripts/run_hpbsm stop

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

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

Once installed, management packs cannot be removed. They appear in the Management Packs page but are not available for removal.

For details on the management packs that are bundled with OMi, see the OMi Release Notes. To update a management pack to a later version than the one included with OMi, download its installation package from the HPE Live Network Content Marketplace web site and install the management pack manually. You can also download and install additional management packs not included with OMi. However, your updates are not reflected in the OMi 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 OMi environment and then click Next.

Apply the OMi 10.10 configuration

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

The Ready to Configure page displays the current settings.

Configuration wizard: Ready to Configure (Confirmaton) page
  1. Check that your selections are correct. To change a setting, click Edit.

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

  3. Review the progress of the configuration.

Apply the OMi 10.10 configuration

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

The Ready to Configure page displays the current settings.

Configuration wizard: Ready to Configure (Confirmaton) page
  1. Check that your selections are correct. To change a setting, click Edit.

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

  3. Review the progress of the configuration.

Attend OMi configuration

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

Attend configuration of OMi10.10. Wait for the configuration wizard to visually mark all its actions as successfully completed.

Configuration wizard: Configuration Summary page

Attend OMi configuration

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

Attend configuration of OMi10.10. Wait for the configuration wizard to visually mark all its actions as successfully completed.

Configuration wizard: Configuration Summary page

Complete the configuration wizard

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

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

Configuration wizard: Configuration Summary page

Complete the configuration wizard

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

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

Configuration wizard: Configuration Summary page

Optional. Generate the database creation scripts

OMi can automatically set up new databases for you during the configuration, or you can connect to manually created, already existing databases. You may need to ask the database administrator to manually create the databases for you, if you as the OMi installing user do not have permissions to create the databases on the remote database server.

After the OMi installation, but before the configuration, the OMi installing user on the gateway server generates the scripts to create the required objects to populate these databases. The database administrator then runs the scripts on the database server to create these objects. When the databases are ready, you can continue with the OMi configuration. For details on installing and configuring a remote database server, see the OMi Database Guide.

OMi requires the following databases:

  • Management. For storage of system-wide and management-related metadata.

  • RTSM (Run-time Service Model). For storage of configuration information that is gathered from various HPE and third-party applications and tools.

  • Event. For storage of events and related data, such as annotations, as well as for storage of configuration data, such as event correlation rules.

Run the following commands to generate the database creation scripts:

  1. Register database extensions by running the following command:

    <OMi_HOME>\AppServer\webapps\site.war\DataBases\Postgres_DB_Utils\postgres_database_extensions.sql

    /opt/HP/BSM/AppServer/webapps/site.war/DataBases/ORA_DB_Utils/postgres_database_extensions.sql

  2. Generate the Management database script:

    <OMi_HOME_GW>\dbverify\bin\generate_create_script.bat EE <OutputFileName>.sql SqlServerOraclePostgres Management

    /opt/HP/BSM/dbverify/bin/generate_create_script.sh EE <OutputFileName>.sql SqlServerOraclePostgres Management

  3. Run the management schema SQL script:

    1. Connect to the management schema and run the script generated in step 1 to deploy the management objects.

    2. Run the following script:

      <OMi_HOME_GW>\AppServer\webapps\site.war\DataBases\ORA_DB_Utils\management_ora_inserts.sql

      /opt/HP/BSM/AppServer/webapps/site.war/DataBases/ORA_DB_Utils/management_ora_inserts.sql

    3. When the script is finished running, commit the change.

  4. Run the Management database SQL script:

    1. Create the Management database. For details, see the OMi Database Guide.

    2. Connect to the Management database and run the script generated in the previous section to deploy the management objects.

    3. Run the following script from the objects scripts directory:

      management_sql_inserts.sql

    1. Connect to the Management database, and then run the generated SQL script to deploy the management objects.

    2. Run the following script:

      <OMi_HOME>\AppServer\webapps\site.war\DataBases\Postgres_DB_Utils\management_postgres_inserts.sql

      /opt/HP/BSM/AppServer/webapps/site.war/DataBases/ORA_DB_Utils/management_postgres_inserts.sql

  5. No scripts are necessary to create the objects to populate the RTSM database.

  6. Generate the Event database script:

    <OMi_HOME>\opr\bin\opr-schema-script-generator.bat -d SQLOraclePostgres -o <OutputFileName>.sql

    /opt/HP/BSM/opr/bin/opr-schema-script-generator.sh -d SQLOraclePostgres -o <OutputFileName>.sql

  7. Make the generated scripts available to the database administrator for running on the database server. For details on running these scripts, see the OMi Database Guide.

  8. Continue with the OMi configuration after the databases have been created.

Configure OMi silently

Caution: This section is applicable only to the secondary OMi data processing server (optional) and each OMi gateway server that you are upgrading.

Disable OMi on the primary data processing server.

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

  1. Create a non-root user account (if you have not done so already) on all OMi 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 /etc/security/limits.d/90-nproc.conf file:

    <UserName> soft nproc unlimited

    Replace <UserName> with the non-root user account.

  2. Optional. For added security, you can generate encrypted passwords for the configuration files. To do this, start the password encryption utility located in:

     <OMi_HOME>\bin\encrypt-password.bat

     /opt/HP/BSM/bin/encrypt-password.sh

    You enter your password and the encryption utility returns a string.

    In the configuration files, set the property IsEncrypted="true" and enter the encrypted password in key="password" value="<EncryptedPassword>".

    Note: Encrypted passwords are valid on the system where the encryption utility was run.

    To remove password encryption, enter the passwords in the configuration files normally and set the value of IsEncrypted="false".

  3. Create the configuration files for the silent configuration in one of the following ways:

    • Start the Closedconfiguration wizard to generate the configuration files with settings that you enter interactively
    • Manually copy the following template files to a location of your choice, and then add the missing values into the copycopycopies:

      <OMi_HOME>/opr/examples/silent-configuration/SilentConfiguration_Blank.xml

      <OMi_HOME>/opr/examples/silent-configuration/SilentConfiguration_Blank.xml

      <OMi_HOME>/opr/examples/silent-configuration/Oracle_DPS.xml

      <OMi_HOME>/opr/examples/silent-configuration/Oracle_GW.xml

      <OMi_HOME>/opr/examples/silent-configuration/SQL_Server_DPS.xml

      <OMi_HOME>/opr/examples/silent-configuration/SQL_Server_GW.xml

      <OMi_HOME>/opr/examples/silent-configuration/Postgres_SingleServer.xml

      <OMi_HOME>/opr/examples/silent-configuration/PostgresEmbedded_SingleServer.xml

      The template files contains comments to help you add appropriate values correctly.

      Caution: Leave the names of the PostgreSQL database schemas (the dbName keys) set to their default values.

  4. Configure OMi in silent mode:

    <OMi_HOME>\bin\silentConfigureBSM.bat <ConfigurationFilename>

    /opt/HP/BSM/bin/silentConfigureBSM.sh <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:

    <OMi_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 separately by specifying the corresponding parameter:

    • Post-installation only. To invoke OMi post-installation phase, run the following command:

      <OMi_HOME>\bin\silentConfigureBSM.bat <ConfigurationFilename> postinstall

      /opt/HP/BSM/bin/silentConfigureBSM.sh <ConfigurationFilename> postinstall

    • Configuration only. To reconfigure OMi after the initial configuration, run the following command:

      <OMi_HOME>\bin\silentConfigureBSM.bat <ConfigurationFilename> configserver

      /opt/HP/BSM/bin/silentConfigureBSM.sh <ConfigurationFilename> configserver

Repeat each step above for the secondary DPS and all gateway servers.

Restore certificates of the integrated products

If you backed up certificates of the BSMOMi-integrated products prior to starting the upgrade process, you must restore them to the appropriate OMi host system at this point. To do so, perform the following:

  • For integrated data providers, such as HPE Network Node Manager i, restore the certificates from the corresponding backup location to the following directory:

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

  • For integrated HPE 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 Installation Guide.

Start OMi

Caution: Before you start OMi on the primary data processing server, remove the jetty files created during the upgrade process as root user: /tmp/jetty-0.0.0.0-21212-conf-*

Start the OMi processes as root user:

/etc/init.d/hpbsmd start

The hpbsmd daemon script first switches to the non-root user and then starts the OMi processes.

Alternatively, log out, log in as the new user, and then run the following command to start the OMi processes as the new user:

/opt/HP/BSM/scripts/run_hpbsm start

To start OMi:

  • Windows Server 2008: Select Start > Programs > HPE Operations Manager i > Administration > Enable Operations Manager i.

  • Windows Server 2012: Press Ctrl + Esc and start typing Enable Operations Manager i. Then click Enable Operations Manager i in the search results.

To stop OMi:

  • Windows Server 2008: Select Start > Programs > HPE Operations Manager i > Administration > Disable Operations Manager i.

  • Windows Server 2012: Press Ctrl + Esc and start typing Disable Operations Manager i. Then click Disable Operations Manager i in the search results.

To start or stop OMi, run the following command:

/opt/HP/BSM/scripts/run_hpbsm (start | stop | restart)

To start, stop, or restart OMi using a daemon script, run the following command:

/etc/init.d/hpbsmd (start | stop | restart)

When enabling a distributed environment, first enable the data processing server and then enable the gateway server.

Note:  

If you used the configuration wizard to:

  • Add a new gateway server or modify the previously defined database types or connection parameters:

    Restart all OMi servers and data collectors after successfully completing the configuration wizard.

  • Upgrade from BSM to OMi:

    Restart the OMi data processing server after successfully completing the configuration wizard.

  • Modify any databases on a running OMi deployment:

    Be aware that My Workspace and Service Health no longer contain any pages and components, and OMi perspectives are removed. To restore My Workspace and Service Health pages and components and OMi perspectives, do the following:

    1. Navigate to the following directory:

      <GatewayServerRootDirectory>/conf/uimashup/import

      It contains two subdirectories: /loaded and /toload.

    2. Copy the contents of the /loaded directory into the /toload directory.

    3. Restart OMi.

Log in to OMi

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

To access the OMi login page and log in for the first time:

  1. Delete the web browser's temporary Internet files. This should be done with each browser that accesses OMi after the upgrade.

  2. 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 OMi certificate inventory:

      opr-cert-mgmt.bat ‑export "OMi Webserver CA Certificate" PEM "C:\ca_certificate.crt"

      opr-cert-mgmt.sh ‑export "OMi Webserver CA Certificate" PEM "/tmp/ca_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.

      • Firefox: Navigate to Options > Advanced > Certificates. Click View Certificates and then Import. In the Certificate Manager dialog box, select the Authorities tab and click Import.

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

  3. In the web browser's address bar, enter the following URL:

    https://<FullyQualifiedDomainName>/omi

    <FullyQualifiedDomainName> is the FQDN of the OMi server.

    <FullyQualifiedDomainName> is the FQDN of the OMi server. If there are multiple servers, or if OMi is deployed in a distributed architecture, specify the gateway server URL.

    <FullyQualifiedDomainName> is the FQDN of the OMi server. If there are multiple servers, or if OMi is deployed in a distributed architecture, specify the load balancer or gateway server URL.

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

  5. Recommended. Create additional administrative users to enable OMi administrators to access the system. For details on creating users in the OMi system, see the "Users, Groups, and Roles" chapter in the OMi Administration Guide.

Note:  

  • For login troubleshooting information, see "Troubleshooting and Limitations" in the OMi Administration Guide.
  • By default, single sign-on (SSO) login is disabled. HPE recommends this default if no integrations are required for your installation. For details on this as well as other login authentication strategies, see "Authentication Management" in the OMi Administration Guide.

When you have completed your session, HPE recommends that you log out of the web site to prevent unauthorized entry.

To log out from OMi:

  • Select Logout from the user menu ().

Transfer event data to OMi

To transfer event data to the OMi servers:

  1. Verify the trust relationship between BSMthe previous OMi environment and the new OMi environment, which should be established automatically by the upgrade wizard, as follows:

    • On a gateway server in the BSMprevious OMi environment, run the following command:

      %OvInstallDir%\bin\win64\bbcutil -ping https://<OMiGatewayServerFQDN>/com.hp.ov.opc.msgr

      /opt/OV/bin/bbcutil -ping https://<OMiGatewayServerFQDN>/com.hp.ov.opc.msgr

    If the command fails, manually establish the trust relationship as follows:

    • On a gateway server in the OMi10.10 environment, run the following command:

      <OMi_HOME>\opr\bin\BBCTrustServer.bat <BSMgatewayServerFQDN> -o

      /opt/HP/BSM/opr/bin/BBCTrustServer.sh <BSMgatewayServerFQDN> -o

  2. Locate the Default Server for Data Collectors URL on the BSM server from Admin > Platform > Setup and Maintenance > Infrastructure Settings > Foundations > Platform Administration > Default Virtual Gateway Server for Data Collectors URL and copy the URL to your clipboard or a temporary location.

  3. In the new OMi environment, create a new connected server that refers to the current production server:

    1. Go to Administration > Setup and Maintenance > Connected Servers.

    2. In the Connected Servers pane, click New and select Operations Manager i. The Create New Server Connection dialog box opens.

    3. In the General page, complete the following information:

      1. Enter a display name, a unique internal name, if you want to replace the automatically generated name, and (optionally) a description of the connection being specified.

      2. Click Next to open the Server Properties page.

    4. In the Server Properties page, enter the FQDN of the Default Virtual Gateway Server for Data Collectors URL (saved above) in the Fully Qualified DNS Name field.

    5. Click Finish.

  4. On the new OMi server, enable the processing of incoming events as follows:

    1. Go to Administration > Setup and Maintenance > Infrastructure Settings.

    2. In the upper part of the web page, select Operations Management from the Applications drop-down list.

    3. Locate the Operations Management – Staging Upgrade Settings settings group.

    4. Set Forward All to false.

    5. Set Forward All Target Server to <empty>.

    6. Set Staging Mode Enable to true.

    7. Locate the Operations Management – Event Pipeline Receiver Settings settings group and make sure Disable Receiving of Events is set to false.

  5. Synchronize the events and changes from the BSMprevious OMi environment:

    1. Allow the events and changes to synchronize. This process is complete when the event sync buffer is empty. To check if the buffer is empty, run the following command on a data processing server in the BSMprevious OMi environment:

      <BSM_HOME>\opr\bin\opr-event-sync.bat -monitor

      /opt/HP/BSM/opr/bin/opr-event-sync.sh -monitor

    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.

Optional. Review the log files and enable IPv6

Optional. Review the log files, enable IPv6, and change passwords

Complete the post-upgrade steps

Complete the post-upgrade steps

Optional. Configure additional OMi servers

Once you have a working OMi 10.10 environment, you can configure the secondary data processing server and additional gateway servers as desired.

Move event processing to OMi 10.10

When you are confident that you are ready to use your new OMi servers as your production environment, perform the following tasks:

  1. Move the processing of events from the BSM server to the OMi 10.10 server:

    1. In BSM, disable the receiving of events and changes as follows:

      1. Go to Admin > Platform > Setup and Maintenance> Infrastructure Settings

      2. In the Applications field, select Operations Management, and locate the Event Pipeline Receiver Settings table.

      3. Set Disable receiving of Events to true.

    2. In BSM, make sure incoming data connections are all closed by restarting the ovc processes. Run the following commands from the command line:

      ovc -kill

      ovc -start

    3. In BSM, synchronize the remaining events and changes to OMi 10.10:

      1. Now that new events will no longer be coming into BSM, enable the remaining events and changes to synchronize with OMi 10.10. This process is complete when the event sync buffer is empty. To check if the buffer is empty, run the following command on a data processing server in the BSM environment:

        <BSM_HOME>\opr\bin\opr-event-sync.bat -monitor

        /opt/HP/BSM/opr/bin/opr-event-sync.sh -monitor

      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.

    4. In BSM, disable further processing of incoming events as follows:

      1. Go to Admin > Platform > Setup and Maintenance > Infrastructure Settings.

      2. In the Applications field, select Operations Management and locate the Event Synchronization Settings table. Set Forward Events to true.

      3. In the Duplicate Events Suppression Settings table, set Enable Duplicate Events Suppression table to false.

      4. In the Event Synchronization Settings table, reset the value of Event Forwarding Expiration to the default or any desired value (the current value was temporarily set very high for the purposes of the upgrade).

      5. Go to Admin > Operations Management > Event Automation > Event Forwarding. Select and disable each active forwarding rule.

      6. Go to Admin > Operations Management > Event Automation > Time-Based Event Automation. Select and disable each active TBEA rule.

      7. Go to Admin > Operations Management > Event Automation > Automatic Run Book Execution. Select and disable each active OO rule.

      8. Go to Admin > Operations Management > Event Automation > Notifications. Select and disable each active notification rule.

      9. Go to Admin > Operations Management > Event Automation > Event Processing Customizations. Select and disable each active EPI step.

    5. If you were using multiple OMi environments reporting to one central OMi environment (manager of managers), you need to update the central OMi environment (the receiver) with the locations of the new servers as follows:

      On the data processing server, run the following command:

      <BSM_HOME>\bin\opr-switch-forwarding-info.bat --oldServerHost <FQDNofBSMgatewayServer> --newServerIp <FQDNofOMi10.10GatewayServer>

      /opt/HP/BSM/opr-switch-forwarding-info.sh --oldServerHost <FQDNofBSMgatewayServer> --newServerIp <FQDNofOMi10.10GatewayServer>

    6. On the OMi 10.10 server enable processing of incoming events as follows:

      1. Go to Administration > Setup and Maintenance > Infrastructure Settings.

      2. In the Applications field, select Operations Management and locate the Staging Upgrade Settings table. Set Staging Mode Enable to false.

    7. Restore the flow of events to the BSM servers to process the events in the data collector queues.

      1. On the OMi 10.10 server enable event reception as follows:

        Go to Administration > Setup and Maintenance > Infrastructure Settings.

        In the Applications field, select Operations Management and locate the Event Pipeline Receiver Settings table. Set Disable receiving of Events to false.

      2. On the BSM server enable event reception as follows:

        Go to Admin > Platform > Setup and Maintenance > Infrastructure Settings.

        In the Applications field, select Operations Management and locate the Event Pipeline Receiver Settings table. Set Disable receiving of Events to false.

Configure load balancing for gateway servers

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

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

    The first hostname is needed for accessing the OMi web site on the gateway server. It can be distributed to OMi 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 OMi.

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

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

    • Default Virtual Gateway Server for Application Users URL. Virtual hostname for the OMi web site. The gateway server you are working on must be able to resolve this virtual IP address. This means that nslookup for the virtual hostname for the application users should return 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 should return name and IP address when executed on any data collector server.
  3. Set the following parameters in the Infrastructure settings (Administration > Setup and Maintenance > Infrastructure Settings > Foundations > 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 sending 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, which HPE does not recommend, OMi works in Generic Mode. This means that you will only be able to log in to OMi by using the Virtual URL and not directly to the gateway.

      Note: If your load balancer and OMi 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 OMi Administration Guide.

    To determine the internal IP address of your load balancer:

    1. Log in to OMi through the load balancer.

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

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

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

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

  4. After changing the reverse proxy settings, restart the OMi 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 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, but 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, HPE recommends choosing stickiness by session.

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

    • Use the following keep-alive configuration:

      • Send string: GET /ext/mod_mdrv_wrap.dll?type=test

      • Receive string: Web Data Entry is up

      Note: If your OMi 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 port 80 or port 443).

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

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

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

    • Traffic on port 383 should be passed through on OSI model (network) layer 4 (not layer 7, no TLS offloading on the load balancer).

      With OSI model layer 7 balancing, 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 OMi servers (gateway and data processing server ) as well.
  8. Configure the load balancer for user access.

    • Use default settings, but 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, HPE recommends 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

Change the Windows service user account

The OMi service, which runs all OMi services and processes, is installed when you start the configuration wizard. By default, this service runs by using the Local System user account. However, you may need to assign it a different user account (for example, if you use NTLM authentication).

The user account you choose to run the service must have the following permissions:

  • Sufficient database permissions (as defined by the database administrator)

  • Sufficient network privileges

  • Administrative privileges on the local system

Note: When the OMi service is installed, it is installed as a service that is started manually. When you enable OMi for the first time, it becomes a service that is started automatically..

To change the OMi service user account:

  1. Disable OMi:

    • Windows Server 2008: Select Start > Programs > HPE Operations Manager i > Administration > Disable Operations Manager i.

    • Windows Server 2012: Press Ctrl + Esc and start typing Disable Operations Manager i. Then click Disable Operations Manager i in the search results.

  2. In the Windows Services window, double-click HP Operations Manager i. The HP Operations Manager i Properties (Local Computer) dialog box opens.

  3. Click the Log On tab.

  4. Select This account and browse to choose another user account from the list of valid user account on the system.

  5. Enter the selected user account’s Windows password and confirm this password.

  6. Click Apply to save your settings and OK to close the dialog box.

Note: Repeat the procedure after you reinstall or upgrade OMi.

Recommended. Connect data providers

For more information on the integrations, see the Operations Manager i (OMi) community pages of the HPE Live Network Content Marketplace web site.

For details on supported integration versions, select Operations Manager i from the product list in the following document:

Support Matrices for Operations Center products

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 OMi gateway servers. For details, see the documentation of each data provider. HPE recommends upgrading each data provider to the latest supported version.

For more information on the integrations, see the Operations Manager i (OMi) community pages of the HPE Live Network Content Marketplace web site.

For details on supported integration versions, select Operations Manager i from the product list in the following document:

Support Matrices for Operations Center products

Optional. Update management pack assignments

If you have deployed Management Templates and Aspects of the following management packs, update the assignments as described in the OMi Administration Guide or the correspondent management pack documentation, available from the OMi Management Pack Documentation Library.

  • OMi Management Pack for Microsoft SharePoint Server
  • OMi Management Pack for Microsoft SQL Server
  • OMi Management Pack for Oracle Database

Stop using the BSM servers

If you only used Operations Management in your BSM environment, you can stop using the BSM servers after you upgrade BSM to OMi. To continue to use APM-related applications (for example, BPM, RUM, SiteScope, or SLM), keep the BSM servers online and integrate them with OMi as described in the OMi Integrations Guide.

To properly stop using the BSM servers, proceed as follows:

  1. On the OMi server, exit staging mode:

    1. Go to Administration > Setup and Maintenance > Infrastructure Settings.

    2. In the upper part of the web page, click Foundations and then select Platform Administration from the Foundations drop-down list.

    3. Locate the Platform Administration – HP OMi Evaluation settings group.
    4. Set Enable evaluation (staging) mode to false.

    5. Set Enable evaluation (staging) mode for customer to false.

  2. Keep the BSM production servers online for a grace period.

    Even though no new events are sent to the production server, you must keep this server online. 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 OMi. If you do not consider these updates important, you can take the production server offline immediately. Otherwise, wait until all events still sent to the BSM production server are closed. HPE estimates that the grace period, in which most events are typically closed, lasts 1 to 2 weeks.

  3. Take the BSM production servers offline.

  4. Decommission the BSM servers.

Optional. Connect trouble ticket, automation, and reporting tools

For more information on the integrations, see the Operations Manager i (OMi) community pages of the HPE Live Network Content Marketplace web site.

For details on supported integration versions, select Operations Manager i from the product list in the following document:

Support Matrices for Operations Center products

Uninstall OMi

To completely uninstall OMi servers that are running on Microsoft Windows:

  1. Make sure the OMi host systems are connected to the Internet.

    During the uninstallation, OMi verifies certificates. If the OMi servers cannot access the Internet, the uninstallation might take up to three hours.

  2. On each OMi host system, perform the following:

    1. Uninstall OMi using the operating system tools or silently:

      • To uninstall OMi using the operating system tools:

        1. On the system from which you are uninstalling OMi, open the Windows Control Panel. Under Programs, click Uninstall a program.

        2. Right-click HP Operations Manager i and click Uninstall. The uninstallation wizard starts. Follow the wizard instructions when prompted.

          Note: Uninstallation might take more than 30 minutes.

        3. Optional. Clicking View installed updates displays all the updates installed over OMi. When OMi is removed, all updates are also removed.

      • To uninstall OMi silently:

        1. Disable OMi on the host system.

        2. Run the following command:

          <OMi_HOME>\installation\bin\uninstall.bat -i silent

        3. Check the following log file for errors, for example, the line INFO - Successfully Completed:

          C:\Users\<UserName>\AppData\Local\Temp\HPOMi_<Version>_HPOvInstaller.txt

    2. Restart the host system.

    3. If you are running OMi with Microsoft IIS, launch Internet Information Services (IIS) Manager and check the following:

      1. In the Connections pane, expand the directory tree as follows: <WebServerHostname> > Sites > Default Web Site.

      2. Check if any of the following applications still exist in the default web site:

        • bsm

        • ext

        • HPBSM

        • Jakarta

        • mam_images

        • MercuryAM

        • odb

        • omi

        • opr-console

        • Topaz

        • TopazDC

        • ucmdb-ui

        • uim

        For each existing application from the above list, check if its physical path property points to the OMi installation folder for the product-specific content (C:\HPBSM by default). If it does, remove the application from the default web site in IIS Manager.

      3. In the Connections pane, expand the directory tree and click the hostname of your web server.

      4. In the Features View pane, double-click ISAPI Filters. If the jakartaFilter entry is present in the filters list, select it. Depending on your future actions, proceed as follows:

        • Permanent OMi uninstallation. In the Actions pane, click Remove.

        • Relocation of OMi installation files on the same host system. Update the path for the filter as follows:

          I. In the Actions pane, click Edit.

          II. In the Edit ISAPI Filters dialog box, change the path of the executable so that jakartaFilter points to the correct OMi directory, and then click OK.

      5. Apply your changes and quit Internet Information Services (IIS) Manager.

      6. Restart the IIS services.

    4. Open the Windows Registry Editor.

      During installation, the value of the Windows Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ReservedPorts is updated to include the following port ranges required by OMi:

      1098-1099, 2506-2507, 8009-8009, 8080-8080, 4444-4444, 8083-8083, 8093-8093

      These ports ranges are not removed from the registry key during uninstall. You should remove the ports from the registry key manually after uninstalling OMi, provided they are no longer needed by any other application.

      Tip: HPE recommends that you back up Windows Registry before making any changes to it.

Uninstall OMi

To completely uninstall OMi servers that are running on Linux:

  1. On each OMi host system, perform the following:

    1. Disable OMi.

    2. Open a command shell as the root user.

    3. To change the current directory to the directory of the uninstallation program, run the following command:

      cd /opt/HP/BSM/installation/bin

    4. Uninstall OMi in the GUI mode or silently:

      • To uninstall OMi using the GUI mode, run the following command:

        ./uninstall.sh

        The OMi uninstallation wizard starts. Follow the on‑screen instructions. When the uninstallation wizard completes the operations, a success message is displayed. Click Finish.

      • To uninstall OMi silently, run the following command:

        ./uninstall.sh -i silent

    5. Check the following log file for errors, for example, the line INFO - Successfully Completed:

      /tmp/HPOMi_<Version>_HPOvInstaller.txt

      Previous installation files can be found in the following directory:

      /tmp/HPOvInstaller/HPOMi_<Version>

© Copyright 2015-2016 Hewlett Packard Enterprise Development LP