Prerequisites

The hardware, network configuration, database, and installing user requirements are listed in this guide. For a list of supported platforms, web browsers, database management systems, visualization tools as well as coexistence and virtualization information, see the support matrix:

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.

Hardware Requirements

  • Processor. 2 CPU cores minimum, 4 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 2 (or 4) physical CPU cores.

  • Disk space. 10 GB

    BVD installs to the following default directories:

    Directory Reference in Documentation Windows (default) Linux (default)
    Application folder <BVD_Install_Dir> C:\Program Files\Hewlett Packard Enterprise\BVD\ /opt/HP/BVD
    Data folder <BVD_Data_Dir> C:\ProgramData\Hewlett Packard Enterprise\BVD\ /var/opt/HP/BVD
    Shared content installation folder   C:\Program Files\HP\HP BTO Software\ /opt/OV
    Shared content data folder   C:\ProgramData\HP\HP BTO Software\ /var/opt/OV

    The default Linux directories cannot be changed during the installation.

  • Memory (RAM). 2 GB (absolute minimum)

For information about the hardware requirements in large computing environments, see Sizing and Performance Recommendations.

Network Configuration Requirements

  • IP Address. If the system on which you are running BVD supports IPv6, then, by default, only IPv6 addresses will be allowed to access BVD.

    If you want BVD to only be accessible via IPv4 instead, manually disable IPv6 on your system. On Windows, access the Network and Sharing Center, click Change adapter settings and disable Internet Protocol Version 6 (TCP/IPv6) in the properties for the corresponding connection.

Database Requirements

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

There are no specific requirements for the embedded PostgreSQL database other than making sure that you meet the hardware requirements listed in Hardware Requirements. BVD installs and configures the embedded PostgreSQL database instance for you on the BVD 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 when configuring BVD.

  • Configuration. A database for use by BVD 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 details on connecting BVD to the database, see Configuration.

User Account Requirements

  • Windows. You need administrative privileges on the host system on which you are installing and configuring BVD.

  • Linux. You must use the root user account to install and configure BVD.

Linux Requirements

In a non-root environment, SELinux must be disabled on your system:

  1. Edit the configuration file: /etc/selinux/config

  2. Disable SELinux: SELINUX=disabled

  3. Save the file.

Sizing and Performance Recommendations

If BVD is deployed in large computing environments, refer to the following recommendations to estimate the requirements and improve the performance of your BVD system.

  • Required number of CPUs. The following recommendations are based on the assumption that the default settings for the Web Server Processes and Receiver Processes are used.

    On a system with an internal PostgreSQL database and a fast disk (for example SSD), the average load handled by BVD is 100 msg/sec per CPU core.
    For an external PostgreSQL database, the write rate of the database can be a limiting factor.

    In order to estimate the msg/sec (messages per second) for your BVD environment, calculate the following:

    CPU calculation

    Example:

    The number of channels equals the number of dashboards multiplied by the number of widgets per dashboard. The messages per minute equals the number of channels multiplied by the updates per minute (per widget). The messages per second equals the messages per minute divided by 60.

    Number of dashboards Number of widgets per dashboard Number of channels Updates per minute Messages per minute Messages per second
    100 10 1000 1 update/min 1000 msg/min 16 msg/sec
    1000 10 10000 1 update/min 10000 msg/min 160 msg/sec
    1000 10 10000 5 updates/min 50000 msg/min 833 msg/sec
    1000 20 20000 1 update/min 20000 msg/min 333 msg/sec
  • Required disk space.

    On top of the 10 GB minimum requirement, additional disk space is required for large environments.
    In order to estimate the additional disk space requirements for your BVD environment, calculate the following:

    disk space calculation

    Example:

    The example is based on the following assumptions: your BVD environment consists of 100 dashboards, each containing 10 widgets. 500 messages per widget are kept in the cache and the average data sample size is 500 bytes.

    If you configure the Aging by Maximum Age instead of Maximum Number, you need to calculate the average incoming message rate multiplied by the time span for aging.
    For example, if the configured Maximum Age is 1 day and the average incoming message rate is 1 message per minute per widget, then roughly 1440 messages are stored per widget.

  • Required RAM.

    HPE recommends 8 GB RAM for configurations up to 8 CPUs, and 12 GB RAM for larger environments up to 16 CPUs.

Send us feedback