Step 1. Meet the system requirements

Suite database requirements

When configuring the Operations Bridge Suite, you can choose between an internal PostgreSQL database or an external PostgreSQL database. .

• InternalPostgreSQL. There are no specific requirements for the internal PostgreSQL database.
• External PostgreSQL. A database for use by the Operations Bridge Suite must already be configured. The name of the database must not be postgres. In addition, the user that accesses the database must have permissions to create tables.
  For a list of supported PostgreSQL database versions, see the support matrix for the Operations Bridge Suite.

OMi database requirements

• Internal PostgreSQL. With an internal PostgreSQL database, the database instance is installed and configured in a separate container, and database files are stored on the NFS server.

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

BVD database requirements

When configuring BVD, you can choose between an external PostgreSQL database and an internal PostgreSQL database.

There are no specific requirements for the internal PostgreSQL database. The database instance is installed and configured in a separate container, and database files are stored on the NFS server.

The requirements for the external PostgreSQL database are as follows:

• Hardware. For PostgreSQL hardware requirements, see the PostgreSQL documentation available at:

  http://www.postgresql.org/docs/manuals/

• PostgreSQL version. For a list of supported PostgreSQL database versions, see the support matrix at:

  Support Matrices for Operations Center products

  Download and extract the support matrix files, open the document SUMA.htm and select Operations Manager i Business Value Dashboard from the product list.

• Installation. For details on the PostgreSQL software installation, see the installation guide in the documentation for your specific PostgreSQL version.

  Caution Make sure you configure the pg_hba.conf file on the PostgreSQL server to accept remote connections. Otherwise, the connection to the PostgreSQL database cannot be established.

• Configuration. A database for use by BVD must already be configured. The name of the database must not be postgres, and the database must use password for the authentication, not MD5. In addition, the user that accesses the database must have permissions to create tables.

• Data migration. If you were using BVD 10.12, specify the external PostgreSQL of your 10.12 deployment during the configuration to migrate your 10.12 data to the BVD container deployment. The migrated data includes your dashboards, instances, API key, dashboard customizations, CSS customizations, and data integrations.

  Before you specify the details of your 10.12 database in the Suite Installer, perform the following steps:

  1. Stop BVD 10.12. BVD must no longer be active on the database.

  2. Use a database tool, for example PgAdmin, to open the BVD database.

     1. Edit the table bvdLdapServerConfigurations.
     2. Remove the single line that the table contains. This is the LDAP server configuration for 10.12, which is no longer required.
        Do not drop the table.

To also migrate your LDAP user permissions and assignments, specify the LDAP server you used for BVD 10.12 during the LDAP configuration. If the same LDAP server is configured, BVD will apply the already configured permissions and role assignments.
For more information about the LDAP configuration, see the Operations Bridge Suite Administration Guide.

PE database requirements

Performance Engine requires an external Vertica database. If your Operations Bridge Suite container deployment includes Performance Engine and Operations Bridge Reporter, the Vertica instance is shared between OBR and PE.

HPE Vertica does not support VMware Vmotion and Logical Volume Manager (LVM) on any system where database files are stored. HPE recommends VMware ESX 5.5 Hypervisor to virtualize the HPE Vertica Analytics Platform, with VMware Tools installed on each virtual machine.

OBR database requirements

Operations Bridge Reporter requires an external dedicated Vertica database. Vertica is not deployed in a container, but the resources are required for an installation of Vertica on a standalone virtual machine. Use the classic OBR installer and select Vertica database to install Vertica on a virtual machine. If your Operations Bridge Suite container deployment includes the Performance Engine (PE) capability, the Vertica instance can be shared between OBR and PE.

HPE Vertica does not support VMware Vmotion and Logical Volume Manager (LVM) on any system where database files are stored. HPE recommends VMware ESX 5.5 Hypervisor to virtualize the HPE Vertica Analytics Platform, with VMware Tools installed on each virtual machine.

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

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