Step 3. Run the Suite Installer

To install the suite, follow these steps:

1. Launch the ITOM Platform from a supported web browser:

   https://<external_access_host>:5443

   <external_access_host> is the fully qualified domain name of the host which you specified as EXTERNAL_ACCESS_HOST in the install.properties file during the ITOM Platform installation. Usually, this is the master node's FQDN.

2. Log in to the ITOM Platform as the admin user. Use the password you specified after your initial login.

3. On the left side navigation, expand the SUITE menu and click Installation.
   Agree to the license agreement and, optionally, the privacy policy, and click Next.

4. Select Operations Bridge and the latest version of the suite, and click Next.

5. Select the edition of the suite (Express or Premium), and the capabilities of the Operations Bridge Suite that you want to install.

   When installing the Operations Bridge Suite Premium, you can select the following capabilities:

   • Operations Bridge Manager. Operations Bridge Manager (OMi) provides the ability to sense, analyze and adapt to manage IT services that support digital business. With advanced event correlation, log intelligence, predictive analytics and automation you can remediate issues across all your technologies to prioritize business targets.
   • Business Value Dashboard. Business Value Dashboard (BVD) brings your data to life. Use BVD to create custom, flexible dashboards that visualize information in an appealing way and that can be accessed anywhere, anytime, from any device. Incorporate your own graphics, add color to identify status, and receive real-time updates—so you always understand the value driven by your IT environment.
   • Performance Engine. The Performance Engine (PE) is an add-on component of Operations Bridge Manager (OMi) that provides streaming of custom metrics and system metrics in a large scale environment.
   • Operations Bridge Reporter. Operations Bridge Reporter (OBR) is a solution based on the Big Data technology HPE Vertica, and has been built to specifically address the challenges of reporting in dynamic IT environments. In addition to consolidating performance data and metrics from multiple domain-focused collectors, HPE Operations Bridge Reporter also collects and collates specific information on the relationships between the IT elements and the business services.

6. Select Use system default NFS share if you are using the master node as NFS server, and Use other NFS server if you are using your own NFS server. The exported share is the directory you created to store the suite data: /var/vols/itom/<opsbridge_directory>

   Click Next. The configuration wizard is displayed.

7. Configure the suite defaults. The Suite Defaults configuration defines general settings that all capabilities of the suite share.

   Configuration Type

   Select the configuration type of the suite.

   Custom configuration

   Default. Displays the complete configuration wizard. You can specify custom values for all capabilities.

   Express configuration

   Uses default values for some of the settings, to speed up the configuration process. When this option is chosen, the suite by default uses an internal PostgreSQL database, a TLS certificate automatically generated by the ITOM Platform, a 60-day evaluation license, and the same password for the administrator and the PostgreSQL database user.

   Login

   Define the default administrative user credentials for all capabilities.

   If you chose the express configuration, this will be the global password.
   If you chose the custom configuration, you can later specify individual user credentials for the different capabilities.

   Login

   The login name is admin.

   Password

   Specify a password for the administrator user. You can change this password again after the installation.

   Note The password must consist of eight characters or more, and contain at least one upper-case letter, one lower-case letter, one digit, and one special character.

   Database

   Configure the default database for the Operations Bridge Suite.

   If you chose the express configuration, this will be the database for all capabilities.
   If you chose the custom configuration, you can later specify individual databases for the different capabilities.

   Database type

   You can select one of the following database types: Internal PostgreSQL, External PostgreSQL.

   Host

   External database only. The name of the host machine on which the database is installed.

   Port Number

   External database only. The database listening port.

   Database user

   The name of a user with administrative permissions on the specified database.

   Password

   The password of the specified user.

   Connection

   Specify your load balancer information. The load balancer is used to access the different user interfaces of the Operations Bridge Suite capabilities.

   External Hostname

   The external hostname of the load balancer.

   In a single server environment, enter the FQDN you specified as EXTERNAL_ACCESS_HOST in the install.properties file. This hostname must be resolvable via the DNS server, not only via /etc/hosts.

   Port Number

   The port of the load balancer.

   Default: 443

   SSL Certificate File

   Click Use the certificate generated by the ITOM Platform to use the automatically generated certificate file.

   Click Upload certificate to browse your files and select the load balancer's server and CA root certificate files. The Operations Bridge Suite supports server certificates in P12 and PFX format, and CA certificates in PEM format.

8. Optional. Configure Operations Bridge Manager (OMi).

   Login

   Define the administrative user credentials for OMi. You can later change the password in your account settings.

   Use suite default administrative user account

   Select to use the administrative user account credentials that you specified during the suite configuration.

   Custom credentials

   Select to specify custom credentials for OMi.

   The OMi administrator user name is admin, the password can be changed in the OMi user interface at a later time.

   The JMX password is used by the OMi administrator for all JMX consoles (user name: admin) and for the RTSM JMX console (user name: sysadmin).

   Database

   Configure a database to store all OMi related information. You can choose to use the database specified for the Operations Bridge Suite, use an OMi specific internal database, create a new database, or you can connect to an already existing database.

   Use suite default database settings

   Select to use the database that you specified during the suite configuration. You can specify the names of the Management, RTSM, and Event schemas.

   Custom database settings for Operations Bridge Manager

   Select to create a new database for this OMi instance or connect to an existing database.
   
   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 databases manually, see the OMi Database Guide.

   If you decide to use an internal PostgreSQL database instance, OMi installs and configures the instance for you.

   Database Type

   Select the appropriate database type: Internal PostgreSQL, or External PostgreSQL.

   Host

   The name of the host machine on which the database is installed. Alternatively, you can also specify the IP address of the host machine.

   Port Number

   The database listening port.

   Default: 5432 (Postgres)

   Login

   The name of a user with administrative permissions on the specified database.

   Password

   The password of the specified user.

   Use TLS

   Optional. Click Use TLS to encrypt the communication with the database.

   The server must be running with TLS communication enabled and it must provide a certificate for use by OMi.

   Management Schema

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

   Event Schema

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

   RTSM Schema

   For storage of RTSM data. The RTSM (Run-time Service Model) is OMi's embedded CMDB, that acts as the central repository for configuration information that is collected and updated from the various OMi data collection processes.

   Server Deployment

   Define the size of your OMi deployment. The number of monitored nodes determines the amount of memory on your system.

   Number of monitored nodes

   Select the appropriate number of monitored nodes that send events to OMi: up to 2000, up to 5000, or more than 5000.

   This includes all nodes that are present as CIs and that send events to OMi (for example, nodes connected to Operations Manager, nodes directly connected to OMi, and target connectors).

   Management Packs

   Select the HPE OMi Management Packs to install in your OMi environment.
   You can choose not to install dependent management packs. However, if you do so, the functional scope of the selected management packs might reduce.

   Management packs provide add-on content on top of 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, run opr-mp-installer. For details about how to run OMi command-line tools from within the container, see Access Command Line Interfaces.

   opr-mp-installer by default installs management packs from the <OMi_HOME>/opr/mgmtpacks directory inside the OMi container. In this directory, you can find all management packs that can be selected during the suite installation.

   Once installed, management packs cannot be removed.

   Note To update a management pack to a later version than the one included with OMi, download its installation package from the HPE Marketplace website and install the management pack manually. You can also install additional management packs that are not bundled with OMi.

   To install the downloaded management pack, put the management pack zip file into a location that is accessible to the OMi container, then specify this location when executing the opr-mp-installer script using the -i <input_path> option.

   For example, a suitable location would be a mgmtpacks directory in the /omi/var/opt/OV/shared/server/conf/ subfolder on the NFS share. You could then execute the opr-mp-installer tool as follows:
   opr-mp-installer -install <mp_name> -i /var/opt/OV/shared/server/conf/mgmtpacks

9. Optional. Configure Business Value Dashboard (BVD).

   Login

   Define the administrative user credentials for BVD. One built-in super-admin user is defined for every installation of BVD. You can later change the password in your account settings.

   Use suite default administrative user account

   Select to use the administrative user account credentials that you specified during the suite configuration.

   Custom credentials

   Select to specify custom credentials for BVD.

   Name

   Login name of the built-in BVD super-admin.

   The built-in super-admin is not listed among the users in user management. If you have logged in as the super-admin, you can change the user's information, including password and contact information, in the My Account page in the Personal User Settings menu.

   Default: admin

   Password

   Password of the built-in super-admin.

   BVD enforces a strong password policy. The password must be at least eight characters long, and meet at least two of the following requirements: one upper-case letter, one digit, and one special character. Special characters should be ASCII characters only.

   Database

   Configure a database to store all BVD related information. You can choose to use the database specified for the Operations Bridge Suite, create a new, embedded database, or you can connect to an already existing database.

   Use suite default database

   Select to use the database that you specified during the suite configuration. If you chose an external database, enter a database name.

   Custom database for BVD related data

   Select to specify an existing, already configured database for BVD.

   To migrate data from a previous BVD 10.12 installation, make sure you performed the migration steps described in the BVD database requirements. Then you can proceed with specifying the external PostgreSQL database that you used for your 10.12 deployment.

   Note Before connecting to an external PostgreSQL database, make sure the database is installed as required by BVD.

   Database type

   Choose the type of database to be used.

   External PostgreSQL: for use with an external PostgreSQL database.

   Internal PostgreSQL: for use with the embedded PostgreSQL database.

   Host

   The name of the host machine on which PostgreSQL is installed.

   Default: localhost

   Port

   The PostgreSQL listening port.

   Default: 5432

   Database

   The name of the PostgreSQL database.

   Login

   The name of a user with administrative permissions on the PostgreSQL database.

   Default: dbadmin

   Password

   The password of the BVD administrative user to access the PostgreSQL database.

   Security

   Configure security settings for BVD.

   Allow to embed BVD in iframes

   Determines if BVD can be embedded into other web pages as a iframe. If checked, the browser allows framing from other domains.
   Be aware that this might enable an attacker to perform cross-site scripting attacks against BVD.

   Aging

   Configure the controller process that scans the database configuration.
   By default, up to 500 data records per data channel are stored in the database. You can modify the default and adjust additional data aging settings.

   Scanning Interval

   Time interval (in minutes) at which the aging process scans the database to identify and automatically delete data records.

   The value must be an integer greater than 0.

   Default: 30 minutes

   Data Records

   Purge old data records based on their age. The Maximum Age is the time period (in days) during which data records are kept in the database. Records older than the configured time period are automatically deleted by the aging process.

   The value must be an integer greater than 0.

   Default: 10 days

   Data Channel Statistics

   Time period (in days) during which a data channel is available in the list of data channels in the widget properties. If a data channel does not receive any data during the configured time period and the data channel is not associated with a widget, it is deleted from the data store. If the data channel is associated with a widget, the channel is not deleted even if the data last received for the channel is older than the configured time period.

   The value must be an integer greater than 0.

   Default: 1 day

10. Optional. Configure the Performance Engine.

    Login

    Password

    Password for the Performance Engine. The password must be at least sixteen characters long, and contain at least one lower-case letter, one upper-case letter, one digit, and one special character.

    Vertica Database

    Optional. Configure Vertica Database

    Select to configure a Vertica database for storing and retrieving historical performance data. When installing the Performance Engine without this option, the embedded data store of the Performance Engine allows you to retrieve data only for a limited time period. By additionally configuring a Vertica database, you can access data that has been collected for a longer time period.

    For information about how to install Vertica, see the OBR Interactive Installation Guide.

    Vertica hostname

    The hostname of your Vertica database (if your Vertica instance is not shared).

    Port

    The Vertica listening port. Default: 5433 (if your Vertica instance is not shared)

    Database name

    The name of the Vertica database.

    Database user name

    The name of a user with administrative permissions on the Vertica database.

    Database password

    The password of the administrative user to access the Vertica database.

11. Optional. Configure Operations Bridge Reporter.

    Login

    Define the administrative user credentials for Operations Bridge Reporter. You can later change the password in your account settings. For more information, see the Operations Bridge Reporter Administration Guide.

    Use suite default administrative user account

    Select to use the administrative user account credentials that you specified during the suite configuration.

    Custom credentials

    Select to specify custom credentials for OBR.

    Time Zone Selection

    Select the time zone in which you want the Operations Bridge Reporter to operate. The time zone that you select applies to the OBR system and reports. However, the run-time information for processes like collection and work flow streams is always based on local time zone irrespective of this selection.

    GMT

    Select to use the Greenwich Mean Time (GMT).

    Local

    Select to use the time zone of your local system.

    Vertica Database

    Configure a Vertica database to store performance data.

    For information about how to install Vertica, see the OBR Interactive Installation Guide.

    Vertica hostname

    The hostname of your Vertica database (if your Vertica instance is not shared).

    Port

    The Vertica listening port. Default: 5433 (if your Vertica instance is not shared)

    Database name

    The name of the Vertica database.

    Database user name

    The name of a user with administrative permissions on the Vertica database.

    Database password

    The password of the administrative user to access the Vertica database.

    Management Database

    OBR comes with a management database that stores the OBR configuration and run-time data. Create a new user account for the management database administrator to access this database.

    The management database refers to the Online Transaction Processing (OLTP) store used by HPE OBR to store its run-time data such as data process job stream status, runtime information for individual steps, and data source information.

    Database Admin (DBA)

    The password of the database administrator. The login name is postgres.

    Database User

    The password of the management database user. The login name is pmdb_admin.

    Reporting Platform

    OBR uses SAP BusinessObjects for report generation. The Operations Bridge Reporter includes the SAP BusinessObjects BI launch pad portal that enables you to view the generated reports.

    Business Objects hostname

    The hostname of the system that hosts the BusinessObjects BI platform.

    Note After the OBR container is deployed, you must configure OBR to collect data from the data sources. For more information on configuring OBR, see the Operations Bridge Reporter Configuration Guide.

12. On the Configuration Complete page, click Next to start the installation.

    Caution Do not refresh the page during the installation; otherwise, you will quit the installation and log out of the ITOM Platform.

    Wait until the installation is complete.