In a custom installation the Operations Bridge Reporter Server, Vertica Server and SAP BusinessObjects Server are installed on different systems. The following prerequisites must be fulfilled on all systems.

Disk Space Requirements

• To download and merge the OBR media files, allocate minimum 40 GB in the <download location> directory on the system.

• To install OBR components, allocate minimum 40 GB in the /opt directory and minimum 5 GB in /tmp directory on the system.

  Note: For downloading, merging and installing OBR in /opt directory on the same system, allocate additional 40 GB in the /opt directory.

• To install Vertica server only, allocate minimum 2 GB in /opt. This does not include data and catalog files.

  Note: While installing Vertica, make sure that the used disk space should not reach 90% for data and catalog files.

Red Hat Enterprise Linux prerequisites

OBR should be installed on the system that has support for the following bash shell and it should be the default shell for SAP BusinessObjects user, PostgreSQL database user and Vertica user.

• RHEL 6.x - bash shell 4.1.2-40

• RHEL 7.x - bash shell 4.2.46-20 or above

• SUSE - bash shell 3.2-147.22 or above

• The installer by default creates OBR the SAP BusinessObjects user, PostgreSQL database user. The Vertica user will be created while the Vertica database is created. These users must be local to the system and can be created manually before installing OBR at the same location.

  Note: The postgres user created in LDAP is not supported.

• If you want to create new user/group for SAP BusinessObjects user, PostgreSQL and Vertica database user before installing OBR, run the following command on the command prompt:

  useradd -m -p <password> -U <user> -s /bin/bash

  where, <password> is the password for SAP BusinessObjects or Postgres database or Vertica database.

  <user> is the user name for SAP BusinessObjects or Postgres database or Vertica database.

Red Hat Enterprise Linux Libraries

Ensure that the following libraries are available on the respective OBR components installed servers:

For more information on the supported RHEL versions, see Operations Bridge ReporterSupport Matrix.

The list indicates the minimum required versions of required libraries for Red Hat Enterprise Linux. You may install a higher version of the library.

Vertica

For Vertica 8.0.1, Linux file system must be ext4. All other file system types are unsupported.

Linux Logical Volume Manager (LVM) is not supported on partitions that contain Vertica data and catalog files.

If Identity Manager is configured on the system and it uses the shell other than the operating system supported shell, Vertica is not supported on such system. The Vertica database creation fails on such systems.

Web Browser Requirements

Web browsers are only supported on Windows. Use a Windows system to access the OBR Administration Console, even when OBR is installed on Linux.

Port Availability

OBR uses a number of default ports for its different services. If you are using the firewall software, ensure that the firewall allows traffic through the required ports listed in the following table on the OBR system:

After the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for the OBR installation.

Task 1:Increase swap space

The swap space for the OBR server, SAP BusinessObjects server or OBR and SAP BusinessObjects on same system must be twice the physical memory space.

The swap space of minimum 2 GB is required for Vertica server only installation scenario.

To allocate sufficient swap space, perform the following steps:

1. Log on to the system as root user.

   Note: The root user must be the owner of the /opt and /var directories.

2. You must create a new swap file. Run the commands to create a swap file and set up swap space: 

   • dd if=/dev/zero of=<swapfile_full_path> bs=1M count=<swap_size_in_MB>
   • mkswap <swapfile_full_path>

   • swapon <swapfile_full_path>

     where, <swapfile_full_path> is the name of the new swap file (including full path to the file) and <swap_size_in_MB> is the space (in MB) that you want to allocate.

     For example, to allocate swap space by creating a new /extraswap file:

     dd if=/dev/zero of=/extraswap bs=1M count=16384

     mkswap /extraswap

     swapon /extraswap

3. For the change to remain in effect even after a system restart, add the following line in the /etc/fstab file:

   <swapfile_full_path>swap swap defaults 0 0

   where, <swapfile_full_path> is the name of the newly created swap file in step 2.

   For example:

   /extraswap swap swap defaults 0 0

Install using the Command Line Console

1. Go to the media root.

   Media root is the directory where the contents of the .tar file are extracted.

   Note: If you want to Install OBR as non-root user, refer to the Appendix section in this guide and then continue with the next installation steps.

2. At the command prompt, type the following command:

   ./HP-SHR_10.20_setup.bin -i console

3. Press Enter to start the installation.

   Note: At any point in time during installation, you can type back to go to the previous page and type quit to cancel the installation.

4. The Choose Locale section appears. Choose the locale in which you want to install OBR, and then press Enter. The installer prepares to install in console mode.

5. Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.

6. In the License Agreement section, press Enter and go through the License Terms.

   Note: Review the screen prompts carefully before pressing Enter each time. Pressing the Enter button continuously might take you through the next steps with the default selections.

   In I accept the terms of the License Agreement (Y/N): type Y to confirm the License Agreement.

   Note: At this point of installation if you want to perform the following action, refer to the Appendix section in this guide and then continue with the next installation steps.

   • Install OBR when /opt does not have enough space.

   The installer displays different installation options.

7. Type 2 to select Custom Operations Bridge Reporter Server and press Enter.

8. Type 1 to select Operations Bridge Reporter Server and press Enter.

   Note: Ensure that you type the relevant numerical identifier provided in the Operations Bridge Reporter installer for each of the OBR component that you want to install.

   To install multiple server components, include a comma between the numerical identifiers. For example, to install Operations Bridge Reporter Server and Vertica Server together, type 1,2 and press Enter.

9. Enter the FQDN of the host where you plan to install (or have already installed) SAP BusinessObjects.

   The installer performs necessary prerequisite checks and displays the result of the check in the console.

10. If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and then start the installation again. If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the OBR installation again.

11. If the prerequisite check is successful, press Enter. 

12. The installer shows preinstallation summary in the console. Press Enter to start the installation.

    Caution: Use the Modify option to install a new component on a system where another component is already installed, you must select both components in the Installer Wizard. In the command line console, enter the numerical identifier of both components. For example, 1,2. If you select only the new component and do not select the installed component, the installed component will be uninstalled and then the new component will be installed.

    On selecting the Modify option you will see a prompt "System restart may be required". Click Continue and the Installer Wizard appears.

If the installation fails, run the rollback utility as follows:

1. In the command line console, go to the rollback utility path located in the OBR media.

2. Run the following command:

   sh rollback-utility.sh

The postgres user is created on the system on successful OBR installation.

Install using the Command Line Console

1. Go to the media root.

   Media root is the directory where the contents of the .tar file are extracted.

   Note: If you want to Install OBR as non-root user, refer to the Appendix section in this guide and then continue with the next installation steps.

2. At the command prompt, type the following command:

   ./HP-SHR_10.20_setup.bin -i console

3. Press Enter to start the installation.

   Note: At any point in time during installation, you can type back to go to the previous page and type quit to cancel the installation.

4. The Choose Locale section appears. Choose the locale in which you want to install OBR, and then press Enter. The installer prepares to install in console mode.

5. Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.

6. In the License Agreement section, press Enter and go through the License Terms.

   Note: Review the screen prompts carefully before pressing Enter each time. Pressing the Enter button continuously might take you through the next steps with the default selections.

   In I accept the terms of the License Agreement (Y/N): type Y to confirm the License Agreement.

   Note: At this point of installation if you want to perform the following action, refer to the Appendix section in this guide and then continue with the next installation steps.

   • Install OBR when /opt does not have enough space.

   The installer displays different installation options.

7. Type 2 to select Custom Operations Bridge Reporter Server and press Enter.

8. Type 2 to select Vertica Server and press Enter.

   Note: Ensure that you type the relevant numerical identifier provided in the Operations Bridge Reporter installer for each of the OBR component that you want to install.

   To install multiple server components, include a comma between the numerical identifiers. For example, to install Operations Bridge Reporter Server and Vertica Server together, type 1,2 and press Enter.

   The installer performs necessary prerequisite checks and displays the result.

9. If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again. If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the OBR installation again.

10. After successful prerequisite check, press Enter. 

11. The installer shows preinstallation summary in the console. Press Enter to start the installation.

    Caution: Use the Modify option to install a new component on a system where another component is already installed, you must select both components in the Installer Wizard. If you use the command line console, enter the numerical identifier of both components. For example, 1,2. If you select only the new component and do not select the installed component, the installed component will be uninstalled and then the new component will be installed.

    On selecting the Modify option you will see a prompt "System restart may be required". Click Continue and the Installer Wizard appears.

12. Run the following command in the command line console:

    $PMDB_HOME/bin/CreateVerticaDatabase.sh <Vertica DBA User Name> <Vertica DBA Password> <Database File Location> <Catalog File Location> <Vertica Database User Name> <Vertica Database Password> <Database Name>

    where, <Vertica DBA User Name> is the Vertica database user name with DBA privilege to log on to Vertica database.

    <Vertica DBA Password> is the password for the Vertica database for the user with DBA privileges.

    <Database File Location> location for the Vertica database file.

    <Catalog File Location> location for the Vertica catalog file.

    <Vertica Database User Name> is the Vertica database user name.

    <Vertica Database Password> is the password for Vertica database user.

    <Database Name> is the name of Vertica database. This is an optional parameter. By default, the name of the Vertica database is PMDB.

    Note: Ensure that the user performing the command has the root privileges and database creation rights. The same <Vertica DBA User Name> and <Vertica DBA Password> should be given while configuring the Vertica database.

    The Vertica successfully installed message appears.

    The <vertica user> is created on the system on successful Vertica Server installation. You can enable the iptable on the Vertica Server and the required ports for Vertica should be open.

The log files is in the following location:

/opt/HP/BSM/PMDB/temp/VerticaDbCreation.log

If the installation fails, run the rollback utility as follows:

1. In the command line console, go to the rollback utility path located in the OBR media.

2. Run the following command:

   sh rollback-utility.sh

Vertica cluster configuration can be done after successful install of Vertica if scale-out for Vertica is planned in your IT environment. Vertica cluster configuration can be done only when Vertica is installed on a remote system. Vertica clustering depends on the way Vertica is installed.

In order to create Vertica cluster, complete all the prerequisites on the participating nodes and then create a cluster after Vertica installation as follows:

• Ensure that the system configuration of all the nodes of the cluster are identical.
• All the nodes share the same network.
• Ensure that the Date and Time are synchronized on all the nodes of the cluster.
• The private IP addresses allocated to nodes is used in Vertica clustering.

Install using the Command Line Console

1. Go to the media root.

   Media root is the directory where the contents of the .tar file are extracted.

   Note: If you want to Install OBR as non-root user, refer to the Appendix section in this guide and then continue with the next installation steps.

2. At the command prompt, type the following command:

   ./HP-SHR_10.20_setup.bin -i console

3. Press Enter to start the installation.

   Note: At any point in time during installation, you can type back to go to the previous page and type quit to cancel the installation.

4. The Choose Locale section appears. Choose the locale in which you want to install OBR, and then press Enter. The installer prepares to install in console mode.

5. Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.

6. In the License Agreement section, press Enter and go through the License Terms.

   Note: Review the screen prompts carefully before pressing Enter each time. Pressing the Enter button continuously might take you through the next steps with the default selections.

   In I accept the terms of the License Agreement (Y/N): type Y to confirm the License Agreement.

   Note: At this point of installation if you want to perform the following action, refer to the Appendix section in this guide and then continue with the next installation steps.

   • Install OBR when /opt does not have enough space.

   The installer displays different installation options.

7. Type 2 to select Custom Operations Bridge Reporter Server and press Enter.

8. Type 1, 2 to select Operations Bridge Reporter Server and Vertica Server and press Enter.

   Note: Ensure that you type the relevant numerical identifier provided in the Operations Bridge Reporter installer for each of the OBR component that you want to install.

   The installer performs necessary prerequisite checks and displays the result.

9. If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again. If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the OBR installation again.

10. After successful prerequisite check, press Enter. 

11. The installer shows preinstallation summary in the console. Press Enter to start the installation.

    Caution: Use the Modify option to install a new component on a system where another component is already installed, you must select both components in the Installer Wizard. If you use the command line console, enter the numerical identifier of both components. For example, 1,2. If you select only the new component and do not select the installed component, the installed component will be uninstalled and then the new component will be installed.

    On selecting the Modify option you will see a prompt "System restart may be required". Click Continue and the Installer Wizard appears.

If the installation fails, run the rollback utility as follows:

1. In the command line console, go to the rollback utility path located in the OBR media.

2. Run the following command:

   sh rollback-utility.sh

The postgres user and <vertica user> are created on the system on successful OBR components installation.

Install using the Command Line Console

1. Go to the media root.

   Media root is the directory where the contents of the .tar file are extracted.

   Note: If you want to Install OBR as non-root user, refer to the Appendix section in this guide and then continue with the next installation steps.

2. At the command prompt, type the following command:

   ./HP-SHR_10.20_setup.bin -i console

3. Press Enter to start the installation.

   Note: At any point in time during installation, you can type back to go to the previous page and type quit to cancel the installation.

4. The Choose Locale section appears. Choose the locale in which you want to install OBR, and then press Enter. The installer prepares to install in console mode.

5. Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.

6. In the License Agreement section, press Enter and go through the License Terms.

   Note: Review the screen prompts carefully before pressing Enter each time. Pressing the Enter button continuously might take you through the next steps with the default selections.

   In I accept the terms of the License Agreement (Y/N): type Y to confirm the License Agreement.

   Note: At this point of installation if you want to perform the following action, refer to the Appendix section in this guide and then continue with the next installation steps.

   • Install OBR when /opt does not have enough space.

   The installer displays different installation options.

7. Type 2 to select Custom Operations Bridge Reporter Server and press Enter.

8. Type 3 to select SAP BusinessObjects Server and press Enter.

   Note: Ensure that you type the relevant numerical identifier provided in the Operations Bridge Reporter installer for each of the OBR component that you want to install.

   The installer performs necessary prerequisite checks and displays the result.

9. If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again. If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the OBR installation again.

10. After successful prerequisite check, press Enter. 

11. The installer shows preinstallation summary in the console. Press Enter to start the installation.

    Caution: Use the Modify option to install a new component on a system where another component is already installed, you must select both components in the Installer Wizard. If you use the command line console, enter the numerical identifier of both components. For example, 1,2. If you select only the new component and do not select the installed component, the installed component will be uninstalled and then the new component will be installed.

    On selecting the Modify option you will see a prompt "System restart may be required". Click Continue and the Installer Wizard appears.

The shrboadmin user is created on the system on successful SAP BusinessObjects Server installation.

Install using the Command Line Console

1. Go to the media root.

   Media root is the directory where the contents of the .tar file are extracted.

   Note: If you want to Install OBR as non-root user, refer to the Appendix section in this guide and then continue with the next installation steps.

2. At the command prompt, type the following command:

   ./HP-SHR_10.20_setup.bin -i console

3. Press Enter to start the installation.

   Note: At any point in time during installation, you can type back to go to the previous page and type quit to cancel the installation.

4. The Choose Locale section appears. Choose the locale in which you want to install OBR, and then press Enter. The installer prepares to install in console mode.

5. Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.

6. In the License Agreement section, press Enter and go through the License Terms.

   Note: Review the screen prompts carefully before pressing Enter each time. Pressing the Enter button continuously might take you through the next steps with the default selections.

   In I accept the terms of the License Agreement (Y/N): type Y to confirm the License Agreement.

   Note: At this point of installation if you want to perform the following action, refer to the Appendix section in this guide and then continue with the next installation steps.

   • Install OBR when /opt does not have enough space.

   The installer displays different installation options.

7. Type 2 to select Custom Operations Bridge Reporter Server and press Enter.

8. Type 1, 3 to select Operations Bridge Reporter Server and SAP BusinessObjects Server and press Enter.

   Note: Ensure that you type the relevant numerical identifier provided in the Operations Bridge Reporter installer for each of the OBR component that you want to install.

   The installer performs necessary prerequisite checks and displays the result.

9. If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again.If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the OBR installation again.

10. After successful prerequisite check, press Enter. 

11. The installer shows preinstallation summary in the console. Press Enter to start the installation.

    Caution: Use the Modify option to install a new component on a system where another component is already installed, you must select both components in the Installer Wizard. If you use the command line console, enter the numerical identifier of both components. For example, 1,2. If you select only the new component and do not select the installed component, the installed component will be uninstalled and then the new component will be installed.

    On selecting the Modify option you will see a prompt "System restart may be required". Click Continue and the Installer Wizard appears.

If the installation fails, run the rollback utility as follows:

1. In the command line console, go to the rollback utility path located in the OBR media.

2. Run the following command:

   sh rollback-utility.sh

The postgres user and shrboadmin user are created on the system on successful OBR components installation.

Install using the Command Line Console

1. Go to the media root.

   Media root is the directory where the contents of the .tar file are extracted.

   Note: If you want to Install OBR as non-root user, refer to the Appendix section in this guide and then continue with the next installation steps.

2. At the command prompt, type the following command:

   ./HP-SHR_10.20_setup.bin -i console

3. Press Enter to start the installation.

   Note: At any point in time during installation, you can type back to go to the previous page and type quit to cancel the installation.

4. The Choose Locale section appears. Choose the locale in which you want to install OBR, and then press Enter. The installer prepares to install in console mode.

5. Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.

6. In the License Agreement section, press Enter and go through the License Terms.

   Note: Review the screen prompts carefully before pressing Enter each time. Pressing the Enter button continuously might take you through the next steps with the default selections.

   In I accept the terms of the License Agreement (Y/N): type Y to confirm the License Agreement.

   Note: At this point of installation if you want to perform the following action, refer to the Appendix section in this guide and then continue with the next installation steps.

   • Install OBR when /opt does not have enough space.

   The installer displays different installation options.

7. Type 2 to select Custom Operations Bridge Reporter Server and press Enter.

8. Type 2, 3 to select Vertica Server and SAP BusinessObjects Server and press Enter.

   Note: Ensure that you type the relevant numerical identifier provided in the Operations Bridge Reporter installer for each of the OBR component that you want to install.

   The installer performs necessary prerequisite checks and displays the result.

9. If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again. If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the OBR installation again.

10. After successful prerequisite check, press Enter. 

11. The installer shows preinstallation summary in the console. Press Enter to start the installation.

    Caution: Use the Modify option to install a new component on a system where another component is already installed, you must select both components in the Installer Wizard. If you use the command line console, enter the numerical identifier of both components. For example, 1,2. If you select only the new component and do not select the installed component, the installed component will be uninstalled and then the new component will be installed.

    On selecting the Modify option you will see a prompt "System restart may be required". Click Continue and the Installer Wizard appears.

12. Run the following command in the command line console:

    $PMDB_HOME/bin/CreateVerticaDatabase.sh <Vertica DBA User Name> <Vertica DBA Password> <Database File Location> <Catalog File Location> <Vertica Database User Name> <Vertica Database Password> <Database Name>

    where, <Vertica DBA User Name> is the Vertica database user name with DBA privilege to log on to Vertica database.

    <Vertica DBA Password> is the password for the Vertica database for the user with DBA privileges.

    <Database File Location> location for the Vertica database file.

    <Catalog File Location> location for the Vertica catalog file.

    <Vertica Database User Name> is the Vertica database user name.

    <Vertica Database Password> is the password for Vertica database user.

    <Database Name> is the name of Vertica database. This is an optional parameter. By default, the name of the Vertica database is PMDB.

    Note: Ensure that the user performing the command has the root privileges and database creation rights. The same <Vertica DBA User Name> and <Vertica DBA Password> should be given while configuring the Vertica database.

    The Vertica successfully installed message appears.

    The <vertica user> and shrboadmin user are created on the system on successful OBR components installation.

The log files is in the following location:

/opt/HP/BSM/PMDB/temp/VerticaDbCreation.log

If the installation fails, run the rollback utility as follows:

1. In the command line console, go to the rollback utility path located in the OBR media.

2. Run the following command:

   sh rollback-utility.sh

Install using the Command Line Console

OBR is available in ten different languages. You can select the language of your choice at the time of installation. The installer installs the SAP BusinessObjects language pack for the selected language. However, in the future, if you change the locale of the OBR system to another supported language, you must separately install the SAP BusinessObjects language pack for that language.

To install an additional SAP BusinessObjects language pack, follow these steps:

1. Log on to the system where you installed SAP BusinessObjects as shrboadmin.

2. Make sure that OBR is successfully installed with the default language pack.

   To check that the default language pack is installed successfully, launch the SAP BusinessObjects BI Launchpad portal (http://<OBR_HostName>:8080/BOE\BI), and then go to BI Launchpad Page > Preferences > General > Product Locale. The Product Locale box lists the installed language packs.

   In this instance, <OBR_HostName> is the fully qualified domain name of the OBR system.

3. Make sure that OBR media is available on the system.

4. Go to the installation directory:

   /opt/HP/BSM/BOE4

5. Run the script ./modifyOrRemoveProducts.sh to start the language pack installer. The Application Maintenance page appears.

6. Select Modify and press Enter.

7. A list of SAP BusinessObjects language pack is displayed as shown in the following image:

   

8. Select the desired language pack(s), and press Enter.

   Note: Since the language pack installation requires a significant amount of time, you must correctly choose the language pack of your interest.

   The Select Features page appears.

9. Click Next again. The Expand Installation page appears.

10. Click Next again. The Existing CMS Deployment Information page appears.

    

11. Type the Password and press Enter. The Start Installation page appears.

    Note: In the Connection Information for Existing CMS section the default values for CMS Name and the CMS Port will be displayed.

    

12. Press Enter to complete the SAP BusinessObjects language pack installation.

In a Custom installation the Operations Bridge Reporter Server, Vertica Server and SAP BusinessObjects Server are installed on different systems. The following prerequisites must be fulfilled on all systems.

Following are additional prerequisites for a successful OBR install:

Web Browser Requirements

Web browsers are only supported on Windows. Use a Windows system to access the OBR Administration Console, even when OBR is installed on Linux.

Port Availability

OBR uses a number of default ports for its different services. If you are using the firewall software, ensure that the firewall allows traffic through the required ports listed in the following table on the OBR system:

Installation User Account

• Always install OBR as a local administrator user that is part of the administrators group.
• If the user with which you are going to install OBR is a domain user, make sure the user has all the administrator rights and is also part of the local administrators group on the system where OBR will be installed.

After the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for the OBR installation.

Task 1: Increase Virtual Memory

Ensure that the virtual memory is twice the size of RAM. To increase the size of virtual memory, see Windows operating system documents.

1. Run the following file:

   HP-SHR_10.20_setup.exe

   The setup files are extracted.

2. Select the language to install OBR, and click OK.

   The Operations Bridge Reporter 10.20 Software Installer wizard appears.

3. On the Introduction page, review the note and click Next.

   

4. On the License Agreement page, review the license agreement.
5. Select I accept..., and click Next to proceed with the installation.

6. Select Operations Bridge Reporter Server and click Next.

   

7. Enter the FQDN of the host where you plan to install (or have already installed) SAP BusinessObjects. Click Next.

   

8. Review the folders in which OBR will be installed. To change the installation folders, use the Browse buttons. Click Next.

   

9. On the Product Requirements page, if the checks are successful, click Next.

   If the prerequisite check fails or shows warning messages, make sure that all the prerequisites are met and start the installation again.

10. The Pre-Install Summary page appears. Review the summary, and click Install.
11. After the installation is complete, click Done.

Note: You must ensure to configure DSN on OBR Server to connect to Vertica database before installing the Content packs. For steps, see Configuring DSN on Windows for Vertica Database Connection chapter in Operations Bridge Reporter Configuration Guide.

If you plan to install another OBR component on the same system, restart the system and then perform installation.

Caution: Use the Modify option to install a new component on a system where another component is already installed, you must select both components in the Installer Wizard. If you select only the new component and do not select the installed component, the installed component will be uninstalled and then the new component will be installed.

On selecting the Modify option you will see a prompt "System restart may be required". Click Continue and the Installer Wizard appears.

If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:

1. In the command line console, go to the rollback utility path located in the OBR media.

2. Run the following command:

   rollback-utility.bat <OBR INSTALL PATH>

   For example: rollback-utility.bat C:\HPE-OBR

The postgres user is created on the system on successful OBR installation.

To install SAP BusinessObjects using the installation wizard, follow these steps:

1. Run the following file:

   HP-SHR_10.20_setup.exe

   The setup files are extracted.

2. Select the language to install OBR, and click OK.

   The Operations Bridge Reporter 10.20 Software Installer wizard appears.

3. On the Introduction page, review the note and click Next.
4. On the License Agreement page, review the license agreement.
5. Select I accept..., and click Next to proceed with the installation.

6. Select SAP BusinessObjects Server and click Next.

   

7. Review the folders in which OBR will be installed. To change the installation folders, use the Browse buttons. Click Next.

   

8. Enter the SAP BusinessObjects install drive. The default value is C. Click Next.

   

Note: Enter only the alphabet that denotes the drive. For example, enter C and not C:\ or C:.

9. On the Product Requirements page, if the checks are successful, click Next.

   If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again.

10. The Pre-Install Summary page appears. Review the summary, and click Install.
11. After the installation is complete, click Done.

If you plan to install another OBR component on the same system, restart the system and then perform installation.

Caution: Use the Modify option to install a new component on a system where another component is already installed, you must select both components in the Installer Wizard. If you select only the new component and do not select the installed component, the installed component will be uninstalled and then the new component will be installed.

On selecting the Modify option you will see a prompt "System restart may be required". Click Continue and the Installer Wizard appears.

If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:

1. In the command line console, go to the rollback utility path located in the OBR media.

2. Run the following command:

   rollback-utility.bat <OBR INSTALL PATH>

   For example: rollback-utility.bat C:\HPE-OBR

The shrboadmin user is created on the system on successful SAP BusinessObjects Server installation.

To install Operations Bridge Reporter Server and SAP BusinessObjects Server on a single Windows system using the installation wizard, follow these steps:

1. Run the following file:

   HP-SHR_10.20_setup.exe

   The setup files are extracted.

2. Select the language to install OBR, and click OK.

   The Operations Bridge Reporter 10.20 Software Installer wizard appears.

3. On the Introduction page, review the note and click Next.
4. On the License Agreement page, review the license agreement.
5. Select I accept..., and click Next to proceed with the installation.

6. Select Operations Bridge Reporter Server and SAP BusinessObjects Server and click Next.

   

7. Review the folders in which OBR will be installed. To change the installation folders, use the Browse buttons. Click Next.

   

8. Enter the SAP BusinessObjects install drive. The default value is C. Click Next.

   

Note: Enter only the alphabet that denotes the drive. For example, enter C and not C:\ or C:.

9. On the Product Requirements page, if the checks are successful, click Next.

   If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again.

10. The Pre-Install Summary page appears. Review the summary, and click Install.
11. After the installation is complete, click Done.

Note: You must ensure to configure DSN on OBR Server to connect to Vertica database before installing the Content packs. For steps, see Configuring DSN on Windows for Vertica Database Connection chapter in Operations Bridge Reporter Configuration Guide.

If you plan to install another OBR component on the same system, restart the system and then perform installation.

Caution: Use the Modify option to install a new component on a system where another component is already installed, you must select both components in the Installer Wizard. If you select only the new component and do not select the installed component, the installed component will be uninstalled and then the new component will be installed.

On selecting the Modify option you will see a prompt "System restart may be required". Click Continue and the Installer Wizard appears.

If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:

1. In the command line console, go to the rollback utility path located in the OBR media.

2. Run the following command:

   rollback-utility.bat <OBR INSTALL PATH>

   For example: rollback-utility.bat C:\HPE-OBR

The postgres user and shrboadmin user are created on the system on successful OBR components installation.

OBR is available in ten different languages. You can select the language of your choice at the time of installation. The installer installs the SAP BusinessObjects language pack for the selected language. However, in the future, if you change the locale of the OBR system to another supported language, you must separately install the SAP BusinessObjects language pack for that language.

To install an additional SAP BusinessObjects language pack, follow these steps:

1. Log on to the system where you installed Operations Bridge Reporter.

2. Make sure that OBR is successfully installed with the default language pack.

   To check that the default language pack is installed successfully, launch the SAP BusinessObjects BI Launchpad portal (http://<OBR_HostName>:8080/BOE\BI), and then go to BI Launchpad Page > Preferences > General > Product Locale. The Product Locale box lists the installed language packs.

   In this instance, <OBR _HostName> is the fully qualified domain name of the OBR system.

3. Make sure that OBR media is available on the system.

4. Go to the following directory:

   <OBR media root>\packages\BO\DATA_UNITS\BusinessObjectsServer_win

   where <OBR media root> is the location where the OBR installer is available.

5. Double-click setup.exe to start the language pack installer. The installer wizard appears.

6. Select Modify and click Next.

   Note: Modify will be selected by default.

   

7. The wizard displays a list of SAP BusinessObjects language pack.

8. Select the desired language pack(s), and click Next.

   Note: Since the language pack installation requires a significant amount of time, you must correctly choose the language pack of your interest.

   The Select Features page appears.

9. Click Next again. The Expand Installation page appears.
10. Click Next again. The SAP BusinessObjects BI platform 4.1 SP5 setup page appears.

11. In the CMS Administrator Logon Information section type the password and click Next. The Start Installation page appears.

    Note: In the Connection Information for Existing CMS section the default values for CMS Name and the CMS Port will be displayed.

12. Click Next to complete the SAP BusinessObjects language pack installation.

Perform the following steps to verify the success of installation:

For Linux

Validating services

1. Log on as root.

2. Run the following command:

   On RHEL 6.x: chkconfig --list

   On RHEL 7.x: systemctl list-unit-files

   The command output lists the all the services of OBR.

   RHEL 6.x	RHEL 7.x
   On OBR server
   HPE_PMDB_Platform_Administrator HPE_PMDB_Platform_Collection HPE_PMDB_Platform_DB_Logger HPE_PMDB_Platform_IA HPE_PMDB_Platform_IM HPE_PMDB_Platform_JobManager HPE_PMDB_Platform_NRT_ETL HPE_PMDB_Platform_Orchestration HPE_PMDB_Platform_PostgreSQL HPE_PMDB_Platform_TaskManager TrendTimer	HPE_PMDB_Platform_Administrator.service HPE_PMDB_Platform_Collection.service HPE_PMDB_Platform_DB_Logger.service HPE_PMDB_Platform_IA.service HPE_PMDB_Platform_IM.service HPE_PMDB_Platform_JobManager.service HPE_PMDB_Platform_NRT_ETL.service HPE_PMDB_Platform_Orchestration.service HPE_PMDB_Platform_PostgreSQL.service HPE_PMDB_Platform_TaskManager.service TrendTimer.service
   On SAP BusinessObjects server
   SAPBOBJEnterpriseXI40	SAPBOBJEnterpriseXI40
   On Vertica server
   HPE_PMDB_Platform_Vertica	HPE_PMDB_Platform_Vertica.service
   On Remote Collector
   HPE_PMDB_Platform_Collection	HPE_PMDB_Platform_Collection.service
   On Data Processor
   HPE_PMDB_Platform_TaskManager	HPE_PMDB_Platform_TaskManager.service

   Note: HPE_PMDB_Platform_Vertica This service is available on the system where Vertica is installed and appears only after Vertica database is created.

3. Run the following commands in the command line console to ensure if the services are running satisfactorily:

   On RHEL 6.x/SLES 11

   • service HPE_PMDB_Platform_Administrator status

   • service HPE_PMDB_Platform_PostgreSQL status

   On RHEL 7.x

   • systemctl status HPE_PMDB_Platform_Administrator.service

   • systemctl status HPE_PMDB_Platform_PostgreSQL.service

SAP BusinessObjects services

To check the status of the SAP BusinessObjects services, run the following commands at the command line console:

1. su - shrboadmin

2. cd /opt/HP/BSM/BOE4/sap_bobj

3. ./ccm.sh -cms <servername where BO installed>:6400 -username Administrator -password 1ShrAdmin -authentication secEnterprise -display

   The command output shows the status of SAP BusinessObjects services. All services must be enabled and running.

For Windows

Validating services

1. Log on to the OBR system.

2. Click Start > Run. The Run dialog box appears.

3. Type services.msc in the Open field, and then press ENTER. The Services window appears with the list of following services:

   On OBR server

   HPE_PMDB_Platform_Administrator HPE_PMDB_Platform_Collection HPE_PMDB_Platform_DB_Logger HPE_PMDB_Platform_IA HPE_PMDB_Platform_IM HPE_PMDB_Platform_JobManager HPE_PMDB_Platform_NRT_ETL HPE_PMDB_Platform_Orchestration HPE_PMDB_Platform_PostgreSQL HPE_PMDB_Platform_TaskManager HPE_PMDB_Platform_Timer

   On SAP BusinessObjects server

   Business Objects Webserver

   On Vertica server

   HPE_PMDB_Platform_Vertica

   On Remote Collector

   HPE_PMDB_Platform_Collection

   On Data Processor

   HPE_PMDB_Platform_TaskManager

   The Vertica service HPE_PMDB_Platform_Vertica will be available in the Linux system where it is installed.

4. On the right pane, view the status of the OBR services.

   

SAP BusinessObjects services

To check the status of the SAP BusinessObjects services, you can use the SAP BusinessObjects Central Configuration Manager. Perform the following steps:

1. Click Start and type Central Management Console in Search. The Central Management Console window appears.

2. Log on to the Central Management Console.

3. From the drop down select Servers.

   

4. Note the status of the listed SAP BusinessObjects services. All services must be enabled and running.

   

Validating files

Verify the following parameters in the respective files display the values as mentioned in the table:

*The <value> differs for each of the installation scenario, see the Operations Bridge Reporter Performance, Sizing and Tuning Guide for more information.

In flink-conf.yaml file, ensure that the following parameters are not duplicated:

taskmanager.network.numberOfBuffers

task.cancellation-interval

If duplicates are found, remove the last occurrence of these parameters.

Generating a Certificate Authority Signed Certificate

In OBR, HTTPs communication is enabled by default for Administrator console and SAP BusinessObjects. OBR uses the self-signed certificate. However, it is highly recommended to use the Certificate Authority (CA) certificate.

To get a CA signed certificate and configure OBR to use this certificate, perform these steps:

1. Open the command prompt and take a backup of the existing keystore file from the following location:

   On Windows: %PMDB_HOME%\keystore\SHR_CERT_HTTPS.jks.

   On Linux: $PMDB_HOME/keystore/SHR_CERT_HTTPS.jks.

   Move the SHR_CERT_HTTPS.jks file from {PMDB_HOME}/keystore to another location.

2. Generate a private key from your system using the keytool command.

   1. Run the following command:

      On Windows: %PMDB_HOME%\..\JRE64\bin\keytool -genkeypair -keyalg <algorithm> -keysize <keysize value> -keystore %PMDB_HOME%\keystore\SHR_CERT_HTTPS.jks -storepass <password> -alias SHR

      where, <password> is the password that a user can provide while running the preceding keytool command.

      <algorithm> is the key algorithm.

      <keysize value> is the value for the keysize.

      For example: %PMDB_HOME%\..\JRE64\bin\keytool -genkeypair -keyalg RSA -keysize 1024 -keystore %PMDB_HOME%\keystore\SHR_CERT_HTTPS.jks -storepass shradmin -alias SHR

      On Linux: $PMDB_HOME/../JRE64/bin/keytool -genkeypair -keyalg <algorithm> -keysize <keysize value> -keystore /opt/HP/BSM/PMDB/keystore/SHR_CERT_HTTPS.jks -storepass <password> -alias SHR

      where, <password> is the password that a user can provide while running the preceding keytool command.

      <algorithm> is the key algorithm.

      <keysize value> is the value for the keysize.

      For example: $PMDB_HOME/../JRE64/bin/keytool -genkeypair -keyalg RSA -keysize 1024 -keystore /opt/HP/BSM/PMDB/keystore/SHR_CERT_HTTPS.jks -storepass shradmin -alias SHR

   2. Enter the requested information.

   Note: When prompted for first and last name, enter the FQDN (fully-qualified domain name) of your system.

3. Run the following command exactly as shown to create a Certificate Signing Request (CSR) file:

   On Windows: %PMDB_HOME%\..\JRE64\bin\keytool -keystore SHR_CERT_HTTPS.jks -certreq -storepass <password> -alias SHR -file CERTREQFILE

   where, <password> is the password that a user can provide while running the preceding keytool command.

   For example: %PMDB_HOME%\..\JRE64\bin\keytool -keystore SHR_CERT_HTTPS.jks -certreq -storepass shradmin -alias SHR -file CERTREQFILE

   On Linux: $PMDB_HOME/../JRE64/bin/keytool -keystore SHR_CERT_HTTPS.jks -certreq -storepass <password> -alias SHR -file CERTREQFILE

   where, <password> is the password that a user can provide while running the preceding keytool command.

   For example: $PMDB_HOME/../JRE64/bin/keytool -keystore SHR_CERT_HTTPS.jks -certreq -storepass shradmin -alias SHR -file CERTREQFILE

4. Send the CSR (CERTREQFILE) to your CA signing authority. They should provide you with one of the following:

   1. A signed certificate, referred to as myserver.crt. The myserver.crt file contains both the server certificate (the top certificate contained in the file) and one or more CA (Certified Authority) certificates (the last certificates contained in the file). Copy the CA certificates into a new file, the myca.crt file. Use the myserver.crt file when importing the server certificate into the SHR_CERT_HTTPS.jks file and the myca.crt file when importing the CA certificate into the SHR_TRUSTSTORE file.

   2. Two files, referred to myserver.crt and CA.crt in this procedure. Add the CA.crt file content to the end of the myserver.crt file. Use the myserver.crt file when importing the server certificate into the SHR_CERT_HTTPS.jks file and the myca.crt file when importing the CA certificate into the SHR_TRUSTSTORE file.

5. Copy the files containing these certificates to the OBR server on the following location:

   On Windows: %PMDB_HOME%\keystore

   On Linux: $PMDB_HOME/keystore

6. Run the following command to import the server certificate and the CA certificate into the OBR SHR_CERT_HTTPS.jks file:

   On Windows: %PMDB_HOME%\..\JRE64\bin\keytool -importcert -trustcacerts -alias SHR -keystore %PMDB_HOME%\keystore\SHR_CERT_HTTPS.jks -storepass <password> -file mycert.crt

   where, <password> is the password that a user can provide while running the preceding keytool command.

   For example: %PMDB_HOME%\..\JRE64\bin\keytool -importcert -trustcacerts -alias SHR -keystore %PMDB_HOME%\keystore\SHR_CERT_HTTPS.jks -storepass shradmin -file mycert.crt

   On Linux: $PMDB_HOME/../JRE64/bin/keytool -importcert -trustcacerts -alias SHR -keystore $PMDB_HOME/keystore/SHR_CERT_HTTPS.jks -storepass <password> -file mycert.crt

   where, <password> is the password that a user can provide while running the preceding keytool command.

   For example: $PMDB_HOME/../JRE64/bin/keytool -importcert -trustcacerts -alias SHR -keystore $PMDB_HOME/keystore/SHR_CERT_HTTPS.jks -storepass shradmin -file mycert.crt

7. Run the following commands to import the CA certificate into the OBR SHR_TRUSTSTORE file:

   On Windows: %PMDB_HOME%\..\JRE64\bin\keytool -import -alias myca -keystore %PMDB_HOME%\keystore\SHR_TRUSTSTORE -file myca.crt

   On Linux: $PMDB_HOME/../JRE64/bin/keytool -import -alias myca -keystore $PMDB_HOME/keystore/SHR_TRUSTSTORE -file myca.crt

8. The <password> provided to the keytool command must be updated in the server.xml file for Administration Console and SAP BusinessObjects. Perform these steps to updated the <password>:

   For Administration Console:

   1. Go to the path {PMDB_HOME}/adminServer/conf/server.xml
   2. Edit the keystorePass value in the server.xml file with the <password>.

   For SAP BusinessObjects:

   1. Go to the path {PMDB_HOME}/BOWebServer/conf/server.xml
   2. Edit the keystorePass value in the server.xml file with the <password>.

9. Restart the OBR services by running the below commands:

   On Windows:

   1. From the run window, type services.msc.

   2. In the services window, right-click and select Stop for the following services:

      • HPE_PMDB_Platform_Administrator
      • SAPBOBJEnterpriseXI40

      Wait for a while for the services to stop.

   3. Right-click and select Start for the following services:

      • HPE_PMDB_Platform_Administrator
      • SAPBOBJEnterpriseXI40

   On Linux

   RHEL 6.x/SUSE Linux Enterprise Server 11:

   • service HPE_PMDB_Platform_Administrator stop
   • service SAPBOBJEnterpriseXI40 stop
   • service HPE_PMDB_Platform_Administrator start
   • service SAPBOBJEnterpriseXI40 start

   RHEL 7.x:

   • systemctl stop HPE_PMDB_Platform_Administrator.service
   • systemctl stop SAPBOBJEnterpriseXI40.service
   • systemctl start service HPE_PMDB_Platform_Administrator.service
   • systemctl start SAPBOBJEnterpriseXI40.service

10. Test the HTTPS access to the OBR Administration console and SAP BusinessObjects Launch pad using the following syntax:

    https://<OBR_Server_FQDN>:21412/OBRApp

    https://OBR_Server_FQDN>:8443/BI

After you complete the installation and Generating a Certificate Authority Signed Certificate, you must configure OBR so that it can collect data from the sources. For more information to configure OBR, see Operations Bridge Reporter Configuration Guide.

For information to schedule the back up, see Database Backup and Recovery section in the Operations Bridge Reporter Configuration Guide.

If you want to install OBR and Operations Agent on the same system, you must perform the following additional configuration steps:

1. Install Operations Agent on an OBR system.

2. Log on to the OBR system as administrator for Windows or root for Linux.

3. In the command line console, run the following command:

   ovcert -list

   The list of certificates installed on the system is displayed.

4. From the command line console, note down the contents of the Certificates and Trusted Certificates field under the Keystore Content section.

   Example:

   

5. On the OBR system, run the following command:

   ovcert -remove <certificate_content>

   In this instance, <certificate_content> is the complete string of characters that appears under the Certificates Keystore Content section.

   Caution: Do not remove the content under Keystore Content<OVRG: server> section.

6. On the OBR system, run the following command:

   ovcert -remove<trusted_certificate_content>

   In this instance, <trusted_certificate_content> is the complete string of characters that appears under the Trusted Certificates Keystore Content section.

   Caution: Do not remove the content under Keystore Content<OVRG: server> section.

7. Go to the Operations Agent bits download location or OVINSTALLDIR\bin\win64\OpC\install directory and run the following command:

   cscript oainstall.vbs -c -a -s <mgmt_srv_name> -cs <cert_srv_name> (Windows)

   oainstall.sh -c -a -s <mgmt_srv_name> -cs <cert_srv_name> (Linux)

   to configure the agent to work with the OM management server or the OMi management server.

   If you get the following error:

   "Failed to start (some) OVO agent processes. See OVO log file and event log."

   1. Run the ovc -kill command in the command line console.
   2. Check if all the services are stopped by running the ovc command.
   3. If the services are not stopped then stop the services manually by performing the following steps:
   1. In the OBR system go to Windows > Task Manager.
   2. Select the Processes tab, locate ovcd.exe, right-click it and select End Process.

   You can proceed to configure the agent to work with OM management server or the OMi management server.

8. Add and monitor the node . Request for certificate and apply them.

   For more information, see the Operations Agent and Operations Smart Plug-ins for Infrastructure Installation Guide.

9. Follow these steps:

   If you are using OM for Windows:

   1. Create a new policy under Policy Management > Policies grouped by type> Agent policies > Flexible Management.
   2.  Copy the following contents to the policy:

   3. #

      # Template for message forwarding to another management server

      #

      TIMETEMPLATES

      # None

      #

      # Responsible Manager Configurations

      #

      RESPMGRCONFIGS

      # Responsible target Manager: target

      # Responsible source Manager: source

      RESPMGRCONFIG

       DESCRIPTION "Responsible managers"

       SECONDARYMANAGERS

       SECONDARYMANAGER

       NODE IP 0.0.0.0 "OM_SERVER"

       DESCRIPTION "Management Server OM_SERVER"

       SECONDARYMANAGER

       NODE IP 0.0.0.0 "SHR_SERVER"

       DESCRIPTION "Backup Server for OM_SERVER"

       ACTIONALLOWMANAGERS

       ACTIONALLOWMANAGER

       NODE IP 0.0.0.0 "OM_SERVER"

       DESCRIPTION "Management Server OM_SERVER"

       ACTIONALLOWMANAGER

       NODE IP 0.0.0.0 "SHR_SERVER"

       DESCRIPTION "Backup Server for OM_SERVER"

       MSGTARGETRULES

   4. Replace OM_SERVER with the FQDN of the OM management server and SHR_SERVER with the FQDN of the OBR system.

   5. Click Check Syntax and make sure that the content is valid.

   6. Deploy the policy to the OBR system.
   If you are using BSM/OMi for Windows/Linux:

   1. Create a new policy under Administration > Monitoring > Policy Templates > Policy Management > Templates grouped by type > Configuration > Flexible Management.
   2. Copy the following contents to the policy:

      #

      # Template for message forwarding to another management server

      #

      TIMETEMPLATES

      # None

      #

      # Responsible Manager Configurations for a backup server

      #

      RESPMGRCONFIGS

      RESPMGRCONFIG

      DESCRIPTION "Responsible managers"

      SECONDARYMANAGERS

      SECONDARYMANAGER

      NODE IP 0.0.0.0 "fqdn_OMi_Server" ID "OvCoreId_OMi_Server"

      DESCRIPTION "Management Server OMi"

      SECONDARYMANAGER

      NODE IP 0.0.0.0 "fqdn_OBR_Server" ID "OvCoreId_OBR_Server"

      DESCRIPTION "Management Server OBR"

      ACTIONALLOWMANAGERS

      ACTIONALLOWMANAGER

      NODE IP 0.0.0.0 "fqdn_OMi_Server" ID "OvCoreId_OMi_Server"

      DESCRIPTION "Management Server OMi"

      ACTIONALLOWMANAGER

      NODE IP 0.0.0.0 "fqdn_OBR_Server" ID "OvCoreId_OBR_Server"

      DESCRIPTION "Management Server OBR"

      ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

      In this instance,

      fqdn_OMi_Server is the FQDN of the OMi server,

      fqdn_OBR_Server is the FQDN of the OBR server,

      OvCoreId_OMi_Server is the Core Id of the OMi server, and

      OvCoreId_OBR_Server is the Core Id of the OBR server.

   3. Replace fqdn_OMi_Server with the FQDN of the OMi management server and fqdn_OBR_Server with the FQDN of the OBR system.

      Also, replace OvCoreId_OMi_Server with the Core Id of the OMi management server and OvCoreId_OBR_Server with the Core Id of the OBR system.

      Note: Run the following command in OMi server to get the OvCoreId: 

      ovcoreid –ovrg server

   4. Save and Close the policy.

   5. Deploy the policy to the OBR system.
   If you are using OM for Linux:

   1. Log on to the management server as root.
   2. Run the following command:

   cp /etc/opt/OV/share/conf/OpC/mgmt_sv/tmpl_respmgrs/backup-server/etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/allnode

   3. Edit the /etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/allnodes/backup-server file to replace M1 with the FQDN of the OM management server and M2 with the FQDN of the OBR system.
   4. Run the following command:

   opcragt –dist<OBR Nodename>

10. Run the following command on the OBR system:

    ovcert -exporttrusted -file<filename>-ovrg server

    In the instance, <filename> is the name with which you want to save the certificate. You must specify the complete path to the certificate file.

11. Run the following command on the OBR system:

    ovcert -importtrusted -file<filename>

    In the instance, <filename> is the name of the file that you copied in the previous step. You must specify the complete path to the certificate file.

12. On the OBR system, run the following command:

    ovcert -trust<Management_Server>-ovrg server

    In this instance, <Management_Server> is the FQDN of the OM system or OMi system.

13. Run the following command on the OBR system:

    ovc -restart

14. Run the following command on the OBR system:

    ovcert -list -ovrg server

    The trust certificates are displayed. If trust certificates are absent, perform the following steps:

15. Run the following commands on the OBR server:

    ovcert -exporttrusted -file <filename1>

    ovcert -importtrusted -file <filename1> -ovrg server

    ovc -restart

    ovdeploy -env PMDB_HOME -ovrg server

    The value of the PMDB_HOME environment variable must display.

16. Run the following command on the OBR system:

    ovc -status -level 8

    The OBR Policy call backs (shrcb) parameter must be listed.

    If not listed, run the following command:

    ovcreg -add $PMDB_HOME/config/shr.xml

17. Run the following command on the OBR system:

    ovc -restart

    If the restart of OBR system is not successful or if the system hangs, run the following commands:

    ovc -kill

    ovc -start

Run the following command to verify certificate and policy deployment:

ovdeploy -env PMDB_HOME -ovrg server

If the value of the PMDB_HOME environment variable is displayed, then certificate and policy deployment is successful.

OBR consists of out-of-the-box content packs that comes bundled and are installed by default. However, there are a few content packs that are not bundled with OBR and they have to be installed individually.

You can install add-on content from the Content Catalog tab in the link ITOM Marketplace - Operations Bridge Reporter.