Customized output from:
Document Release Date: November 2016
Software Release Date: June 2016 |
|
The only warranties for Hewlett-Packard Development Company, L.P. products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPE shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Confidential computer software. Valid license from HPE required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
© Copyright 2015 - 2016 Hewlett Packard Enterprise Development LP
Adobe® is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
HPE Operations Bridge Reporter (HPE OBR) collects data from cross domain data sources, processes it, and generates reports. It uses the following components:
How to use this guide?
Select the options provided in the following sections according to your task requirements. Refresh the selections page or press F5 to change your selections.
You can install all HPE OBR components (HPE Operations Bridge Reporter Server, SAP BusinessObjects Server, Vertica Server and Remote Collector) on a single system (Typical Installation). When reporting on a large number of nodes, to improve performance, you can distribute different components over different systems (Custom Installation).
Note: You cannot upgrade from the previous version to this version of HPE OBR.
Ensure that you have completed the pre-requisites before moving ahead with HPE OBR installation.
Pre-requisites to install HPE OBR
The following table lists the pre-installation requirements and the respective guides. You can download these guides at the HPE Software product manuals web site:
https://softwaresupport.hp.com/
Pre-requisite | Guide |
---|---|
Sizing Calculation | Refer OBR Licensing and Sizing Calculator from the link HPE Live Network. |
Hardware Requirements | HPE Operations Bridge Reporter Performance, Sizing and Tuning Guide |
Software Requirements | HPE Operations Bridge Reporter Support Matrix |
Operating System Requirements | HPE Operations Bridge Reporter Support Matrix |
Web Browser Requirements | HPE Operations Bridge Reporter Support Matrix |
Select the task you want to perform with HPE Operations Bridge Reporter.
Select "Custom" to distribute the installation of the HPE OBR components over different systems.
Select "Typical" to install all the HPE OBR components on the same system.
Select the operating system for the HPE OBR Server.
Vertica Server is supported only on Linux operating system
Select the operating system for the SAP BusinessObjects Server.
Vertica Server is supported only on Linux operating system
HPE OBR typical installation is supported only on Linux operating system because Vertica Server can be installed only on Linux.
Select your installation environment from the following options recommended by HPE.
Select your installation environment from the following options recommended by HPE.
Select your installation environment from the following options recommended by HPE.
Select your installation environment from the following options recommended by HPE.
Select the operating system for HPE Operations Bridge Reporter.
HPE OBR has a built-in collector. However, HPE OBR also provides you with an option to install the collector on a separate server. You can have collectors installed on multiple systems depending on your need. You can install Remote Collector that runs on any of the operating systems supported by HPE OBR.
Ensure that you have made all the required selections to view, or print your customized document.
You can view your customized document on the screen, or print it.
Version: 10.00
Document Release Date: November 2016
Software Release Date: June 2016
The following steps are customized according to your selections. Check that your selections are correct.
If any selections are not correct, click Change.
In a typical installation the HPE Operations Bridge Reporter Server, Vertica Server and SAP BusinessObjects Server are installed on a single system. The following prerequisites must be fulfilled before installing HPE OBR.
Note: These prerequisites are also applicable to the remote systems where you want to install the HPE OBR Collector.
Pre-requisites
Following are additional prerequisites for a successful HPE OBR install:
Disk Space Requirements
/tmp
directory on the system./opt
directory on the system./tmp
directory on the system./opt
directory on the system.Note: Do not start the installation directly from the mount point location. Also, do not download and merge the .tar
files directly from the mount point location.
Tip: HPE OBR uses /opt/HP, /opt/OV
and /opt/vertica
directories for installation. If the following statements are applicable for your /opt
directory:
/opt
directory, and/opt
filesystem.Follow the steps recommended by application(s) to move to different storage. Extend the /opt
filesystem, restore the application(s) back to /opt
.
Red Hat Enterprise Linux prerequisites
HPE OBR should be installed on the system that has support for bash shell (version -4.1.2-33
) and it should be the default shell for SAP BusinessObjects user, PostgreSQL database user and Vertica user.
On successful install of HPE OBR the SAP BusinessObjects user, PostgreSQL database user will be created by default. The Vertica user will be created while the Vertica database is created.
If you want to create new user/group for SAP BusinessObjects user, PostgreSQL and Vertica database user before installing HPE 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 HPE OBR system.
These libraries are also applicable to the remote systems where you want to install the HPE OBR Collector.
Red Hat Enterprise Linux 6.x |
---|
The list indicates the minimum required versions of required libraries for Red Hat Enterprise Linux 6.x. You may install a higher version of the library except for the mcelog library. |
Note: Run the following command to install the libraries only if the repository where the libraries are present is configured:
yum -y install compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 libXext.i686 libXext.x86_64 libXext-devel.i686 libXext-devel.x86_64 ncurses-libs.i686 ncurses-libs.x86_64 glibc.i686 glibc.x86_64 libstdc++.i686 libstdc++.x86_64 openssh.x86_64 sysstat.x86_64 gdb.x86_64 unixODBC.i686 unixODBC.x86_64 unixODBC-devel.i686 unixODBC-devel.x86_64 nss.i686 nss.x86_64 nss-softokn-freebl.i686 nss-softokn-freebl.x86_64 nspr.i686 nspr.x86_64 libpng.i686 libpng.x86_64 ncurses.x86_64 tcsh.x86_64 libaio.i686 libaio.x86_64 libXi.i686 libXi.x86_64 libXtst.i686 libXtst.x86_64 libXp.i686 libXp.x86_64 libXcursor.i686 libXcursor.x86_64 libgcc.i686 libgcc.x86_64 expat.i686 expat.x86_64 libX11.i686 libX11.x86_64 libXfixes.i686 libXfixes.x86_64 libXrender.i686 libXrender.x86_64 libXau.i686 libXau.x86_64 libxcb.i686 libxcb.x86_64 openmotif.i686 openmotif.x86_64 cifs-utils.x86_64 acl.x86_64 glibc-common.x86_64 environment-modules.x86_64
After completing the libraries installation, install the mcelog 101-0.x86_64
library.
Caution: Ensure to install only the 101-0.x86_64
version of mcelog
library. If you have installed any other version on mcelog
library uninstall it and install only this version.
You can upgrade to the latest mcelog
version after completing the OBR installation.
Vertica
EXT4 is the recommended file system for Vertica.
Linux Logical Volume Manager (LVM) is not supported on partitions that contain HP Vertica files.
Web Browser Requirements
Web browsers are only supported on Windows. Use a Windows system to access the HPE OBR Administration Console, even when HPE OBR is installed on Linux.
Port Availability
HPE OBR uses a number of default ports for its different services listed in the following table:
Service |
Port Number |
Protocol |
Inbound |
Outbound |
Description |
---|---|---|---|---|---|
HPE PMDB Platform DB Logger |
21408 |
TCP |
Yes |
Yes |
The HPE PMDB Platform DB Logger service consolidates FATAL errors in a single log file. |
HPE PMDB Platform Collection |
21409 |
TCP |
Yes |
Yes |
The JMX management port for the Collection service. The IM service monitors collection using this interface. |
HPE PMDB Platform IM |
21410 |
TCP |
Yes |
No |
The JMX management port for the IM service. |
HPE PMDB Platform Timer |
No port |
NA |
NA |
NA |
The Timer service for HPE OBR. |
HPE PMDB Platform Orchestration | 21424 | TCP | Yes | No |
The Orchestration service for HPE OBR. |
HPE PMDB Platform Administrator |
21411 |
TCP |
Yes |
No |
The HPE OBR web application server port, which hosts the Administration web application. The Report cross-launch functionality depends on this service. |
HP Vertica Service | 5433 | TCP | Yes | No | Port for the Vertica database. |
HP Vertica Service | 5434 | TCP | Port for the Vertica database. Intra-cluster communication | ||
HP Vertica Management Console | 5444 | TCP | MC-to-node and node-to-node (agent) communications port. | ||
HP Vertica Management Console | 5450 | TCP | Port used to connect to Management Console from a web browser and allows communication from nodes to the Management Console application/web server. | ||
Vertica Spread | 4803 | TCP | Yes | No |
Port for the Vertica Spread connections. Client connections. |
Vertica Spread | 4804 | TCP |
Daemon to Daemon connections. |
||
Vertica Spread | 6543 | UDP |
Port for the Vertica Spread connections. Monitor to Daemon connection. |
||
HPE Software Communication Broker |
383 |
TCP |
Yes |
Yes |
HPE OBR uses this port to communicate with collectors installed on remote servers. |
Administration Console web server |
21416 |
TCP |
Yes |
Yes |
The JMX management port for the HPE OBR administration web server. |
HPE PMDB Platform Collection | 21418 | HTTP | Yes | No | The connection port to HTTP server for the SiteScope generic data integration. |
HPE PMDB Platform Collection | 21419 | HTTPS | Yes | No | The connection port to HTTPS server for the SiteScope generic data integration. |
HPE PMDB Platform Collection | 8080 | HTTP | No | Yes | The connection port to collect data from the SiteScope Data Acquisition API. |
HPE PMDB Platform Collection | 9998 | TCP | Yes | No | The connection port to collect data from the Network Automation (NA) and Server Automation (SA). |
HPE-SHR-Postgre - PostgreSQL Server 9.0 |
21425 |
TCP |
Yes |
Yes |
Port for the PostgreSQL service. |
Apache Tomcat |
8080 |
TCP |
Yes |
No |
This is the SAP BusinessObjects Application Service port. The SAP BusinessObjects Central Management Console and the SAP BusinessObjects BI launch pad web applications are hosted on this port. |
SAP BOBJ Central Management Server |
6400 |
TCP |
Yes |
Yes |
This is the port for the SAP BusinessObjects Central Management Server, which is mainly used for SAP BusinessObjects authentication purposes. |
Server Intelligence Agent (OBR) |
6410 |
TCP |
Yes |
Yes |
Port for the SAP BusinessObjects Server Intelligence Agent, which manages all SAP BusinessObjects-related tasks. |
BOE120SQLAW |
2638 |
TCP |
Yes |
Yes |
Port for the SAP BusinessObjects repository database. |
RTSM |
21212 |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the RTSM data source. Using this port, HPE OBR connects to RTSM. |
HPOM |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the HPOM database. HPE OBR uses this port to connect to the HPOM database. |
HP Operations Agent |
383 |
TCP |
No |
Yes |
HPE OBR uses this port to connect to the HP Operations agent. |
HP BSM Profile database |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the Profile database. |
Preinstallation Tasks
Note: Make sure to check whether HP/BSM
directory or other HP products directories exists before installing HPE OBR. If HP/BSM
is present and contains no files and directories, delete it and move ahead with HPE OBR installation.
After the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for the HPE OBR installation.
Task 1:Increase swap space
To allocate sufficient swap space, perform the following steps:
Log on to the system as root
user.
Note: The root
user must be the owner of the /opt
and /var
directories.
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
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
In this instance, <swapfile_full_path>
is the name of the newly created swap file (in step 2).
For example:
/extraswap swap swap defaults 0 0
Task 2: Disable Anti-Virus
Anti-virus applications can hinder the installation of HPE OBR. Temporarily disable any anti-virus software that is running. Once the installation is complete, enable the anti-virus software.
Task 3: Configure Firewall
If you are using the firewall software, ensure that the firewall allows traffic through the required ports on the HPE OBR system. For more information on port availability, see the section Prerequisites > Port Availability.
To disable the firewall, perform the following steps:
Log on as root
user and run the following commands:
Note: The root
user must be the owner of the /opt
and /var
directories.
chkconfig iptables off
chkconfig ip6tables off
/etc/init.d/iptables stop
/etc/init.d/ip6tables stop
Task 4: Prepare the Linux Server
You must perform the following tasks to prepare the Linux server for installation.
Task 4.1: Disable SELinux
To disable SELinux, in the /etc/sysconfig/selinux
file, set the parameter SELINUX = disabled
.
Task 4.2: Configure the Kernel Parameters (only if you use Red Hat Enterprise Linux 6.x)
To configure the Kernel parameters, follow these steps:
Open the file /etc/sysctl.conf
file and set the values of the parameters as given below:
Note: If these parameters have higher values specified already, do not make any changes.
Note: After the successful Vertica database creation, additional parameter of vm.max_map_count
with different value based on the hardware configuration will be added. Delete the entry that has the minimum value.
Task 4.3: Configure the Host name
Log on to the HPE OBR system, and configure the hostname in the /etc/hosts
file.
If you configure a hostname, it should be added after the following two lines as they appear by default.
127.0.0.1 localhost.localdomain localhost
::1 server1.example.com server1
The naming convention for the hostname is: <IP address> <FQDN of HPE OBR host system> <Short name of HPE OBR host system>
Task 4.4: Configure the limits.conf
file
Open the /etc/security/limits.conf
file and increase the number of open files by setting the following values:
*
soft nofile 65535
*
hard nofile 65535
Task 4.5: Configure the 90-nproc.conf
file (only if you use Red Hat Enterprise Linux 6.x)
Open the /etc/security/limits.d/90-nproc.conf
file and comment out the following line by adding a # character in the beginning:
#*soft nproc 1024
The reason to add # character is to increase the number of user processes for SAP BusinessObjects and Vertica database in setenv.sh
file.
Restart the system for the changes to take effect.
Task 5: Verify the Fully Qualified Domain Name (FQDN) of the system
Before installing HPE OBR, verify that DNS lookup returns the accurate FQDN of the host system. If the entry for the DNS lookup is different from the host name of the system, the log on to the HPE OBR Administration Console will fail. This is because during the SAP BusinessObjects installation, the host name of the system is used for creating the servers/services and registering them.
To verify the FQDN of the host system, perform the following steps:
Open the command line interface and type the following command to check the host name of the system:
hostname -f
Note down the host name of the system.
Type the following command to view the IP address of the system:
ifconfig
Type the following command to verify the FQDN of the displayed IP address:
nslookup
<IP_address>
where, <IP address
> is the IP address of the host system.
Ensure that the name returned by the lookup
command is same as the hostname
command. If the names do not match, you must change the hostname of the system.
Task 6: Linux Operating System configuration for Vertica
Perform the following tasks on the Vertica server:
Task 6.1: Disk Readahead
The following commands must be run with root privileges:
Note: You must ensure to apply the following command based on the disk sda, sdb, sdc, sdd
and the location of blockdev program.
The following command assumes the blockdev program is in /sbin
:
/sbin/blockdev --setra 2048 /dev/sda
echo '/sbin/blockdev --setra 2048 /dev/sda' >> /etc/rc.local
The blockdev program operates on whole devices, and not individual partitions.
Task 6.2: Transparent hugepages
The transparent hugepages must be disabled
or set to madvise
.
To verify if transparent hugepages is enabled, run the following command:
cat /sys/kernel/mm/redhat_transparent_hugepage/enabled
The output in brackets is the current setting as follows:
[always] madvise never
To disable transparent hugepages perform any one of the following steps:
Edit the boot loader (for example /etc/grub.conf
), add the following at the end of the kernel line:
transparent_hugepage=never
Edit /etc/rc.local
and add the following script:
echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled
Note: For systems that do not support /etc/rc.local, use the equivalent startup script.
Task 6.3: I/O scheduling set to deadline or noop
Viewing the contents of this file shows you all of the possible settings for the scheduler, with the currently-selected scheduler surrounded by square brackets:
Run the following command to view the scheduler settings:
cat /sys/block/sda/queue/scheduler
The output in brackets is the current setting as follows:
noop deadline [cfq]
To change the scheduler, type the name of the scheduler as root user.
The following example assumes to set the sda
drive to use the deadline scheduler, run the following command as root:
echo deadline > /sys/block/sda/queue/scheduler
cat /sys/block/sda/queue/scheduler
noop [deadline] cfq
Task 7: Assemble the media
The HPE Operations Bridge Reporter (HPE OBR) software is available in three TAR image part files.
HPEOBR_1000_Lin64.part1
HPEOBR_1000_Lin64.part2
HPEOBR_1000_Lin64.part3
Before you start installing HPE OBR, you must download .tar
file into a single location and perform a merge of the contents.
Note: You must not download the .tar
file under /opt
directory.
Step1: Download the TAR Image Part Files and Check for File Integrity
Step 2: Merge the TAR Image Part Files
Download the TAR Image parts into a temporary folder on the system where you intend to install HPE OBR.
For example: /tmp/HPEOBR_1000-parts
.
To change directory to the location where you copied the contents of the image part files, run the following command:
cd <temp location>
For example: cd /tmp/HPEOBR_1000-parts
Note: Ensure that you have adequate space in the directory.
To merge the contents into a single TAR Image file, run following command:
cat HPEOBR_1000_Lin64.part1 HPEOBR_1000_Lin64.part2 HPEOBR_1000_Lin64.part3 > /tmp/HPEOBR_1000-parts/HPEOBR_1000_Lin64.tar
Note: You must type the command in a single line.
Step 3: Verify the Reassembly of the Build Segments
Compare and verify if the md5 checksum of merged file matches with the corresponding md5 checksum value as listed in “Distribution Contents and MD5 Checksum Values”.
Distribution Contents and MD5 Checksum Values:
The HPE OBR media is now available as a single .tar
file in the following location:
File Name | Size | MD5 Checksum |
---|---|---|
HPEOBR_1000_Lin64.part1 | 4294967296 | 77c5c7c321f86d01d65652a3d4134d54 |
HPEOBR_1000_Lin64.part2 | 4294967296 | ac3bc2431b47a61f0e56056f0cd99571 |
HPEOBR_1000_Lin64.part3 | 1293877248 | e22b651e4f985785c0bdaca3eae10b73 |
HPEOBR_1000_Lin64.tar (Merged file) | 9883811840 | 7d2c4c002ffeee1bc94778243e6ed506 |
The HPE OBR media is now available as a single TAR file in the following location:
/tmp/HPEOBR_1000-parts
/HPEOBR_1000.tar
Note: You must ensure that the parent directory of the unzipped .tar
folder has all the access rights (777) to the owner and to the other groups as a requirement for SAP BusinessObjects.
For example, if you have unzipped the TAR file in /installer/OBR
, the installer
folder should have 777 permissions.
Unzip the .tar
file, you will find the HP-SHR_10.00_setup.bin
to move ahead with the installation.
Task 8: Run the HPE OBR Installation Pre-Check Tool
The HPE OBR Installation Pre-check tool verifies the necessary pre-requisites before installing HPE OBR.
Follow these steps to run the Pre-Check tool:
On the system which you plan to install HPE OBR, download the latestHPE OBR Installation Pre-check tool from the link:
https://hpln.hpe.com/contentoffering/hpe-obr-installation-pre-check-tool
Unzip the .zip
file.
OBR10_InstallPrecheck_README.pdf
to run the Pre-check tool.Additional Considerations
Log on to the system as root
user.
Note: The root
user must be the owner of the /opt
and /var
directories.
Note: The HPE OBR installer does not support forced reinstall. In the event of an unsuccessful installation, you must manually remove all the files that were placed by the installer and perform installation again.
Additional Information
After successful OBR install:
The HPE OBR installer by default creates the postgres
and shrboadmin
users as mentioned in the following table:
User | Group | Home Directory |
---|---|---|
postgres |
postgres
|
/opt/HP/BSM/Postgres
|
shrboadmin
|
shrboadmin
|
/home/shrboadmin
|
<Vertica user>
|
<Vertica group>
|
/home/
|
These users must be local to the system and can be created manually before installing HPE OBR at the same location.
In the PMDB_HOME/bin/setenv.sh
file, the ulimit
value changes automatically for the root
user, <vertica user>
and postgres
user as shown in the following table. This value applies on next log on to the system.
Parameter | ulimit value | Recommended by |
---|---|---|
Number of file descriptors | 65535 | Vertica |
Number of user process | 127510 | SAP BusinessObjects |
Install HPE OBR using the Command Line Console
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.
At the command prompt, type the following command:
./HP-SHR_10.00_setup.bin -i console
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.
Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.
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.
Type 1 for Typical HPE Operations Bridge Reporter Installation to install HPE OBR, Vertica and SAP BusinessObjects on the same system. Press Enter.
The installer performs Install Requirements Checks and displays the result.
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 HPE OBR installation again.
After successful prerequisite check, press Enter.
If the installation fails, run the rollback utility as follows:
Run the following command:
sh rollback-utility.sh
The postgres
user, shrboadmin
user and <vertica user>
are created on the system on successful OBR installation.
Apply the HPE OBR 10.01 patch. For steps, see HPE Operations Bridge Reporter Release Notes.
Install using the Command Line Console
HPE 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 HPE 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:
Make sure that HPE 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://<HPE 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, <HPE OBR_HostName
> is the fully qualified domain name of the HPE OBR system.
Go to the installation directory:
/opt/HP/BSM/BOE4
./modifyOrRemoveProducts.sh
to start the language pack installer. The Application Maintenance page appears.Select Modify and press Enter.
A list of SAP BusinessObjects language pack is displayed as shown in the following image:
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.
Click Next again. The Existing CMS Deployment Information page appears.
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.
In a custom installation the HPE Operations Bridge Reporter Server, Vertica Server and SAP BusinessObjects Server are installed on different systems. The following prerequisites must be fulfilled on all systems.
Note: These prerequisites are also applicable to the remote systems where you want to install the HPE OBR Remote Collector.
Prerequisites
Following are additional prerequisites for a successful HPE OBR install:
Disk Space Requirements
/tmp
directory on each system./opt
directory on each system./tmp
directory on each system./opt
directory on each system.Note: Do not start the installation directly from the mount point location. Also, do not download and merge the .tar
files directly from the mount point location.
Tip: HPE OBR uses /opt/HP, /opt/OV
and /opt/vertica
directories for installation. If the following statements are applicable for your /opt
directory:
/opt
directory, and/opt
filesystem.Follow the steps recommended by application(s) to move to different storage. Extend the /opt
filesystem, restore the application(s) back to /opt
.
Red Hat Enterprise Linux prerequisites
HPE OBR should be installed on the system that has support for bash shell (version -4.1.2-33
) and it should be the default shell for SAP BusinessObjects user, PostgreSQL database user and Vertica user.
On successful install of HPE OBR the SAP BusinessObjects user, PostgreSQL database user will be created by default. The Vertica user will be created while the Vertica database is created.
If you want to create new user/group for SAP BusinessObjects user, PostgreSQL and Vertica database user before installing HPE 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 HPE OBR system.
These libraries are also applicable to the remote systems where you want to install the HPE OBR Collector.
Red Hat Enterprise Linux 6.x |
---|
The list indicates the minimum required versions of required libraries for Red Hat Enterprise Linux 6.x. You may install a higher version of the library except for the mcelog library. |
Note: Run the following command to install the libraries only if the repository where the libraries are present is configured:
yum -y install compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 libXext.i686 libXext.x86_64 libXext-devel.i686 libXext-devel.x86_64 ncurses-libs.i686 ncurses-libs.x86_64 glibc.i686 glibc.x86_64 libstdc++.i686 libstdc++.x86_64 openssh.x86_64 sysstat.x86_64 gdb.x86_64 unixODBC.i686 unixODBC.x86_64 unixODBC-devel.i686 unixODBC-devel.x86_64 nss.i686 nss.x86_64 nss-softokn-freebl.i686 nss-softokn-freebl.x86_64 nspr.i686 nspr.x86_64 libpng.i686 libpng.x86_64 ncurses.x86_64 tcsh.x86_64 libaio.i686 libaio.x86_64 libXi.i686 libXi.x86_64 libXtst.i686 libXtst.x86_64 libXp.i686 libXp.x86_64 libXcursor.i686 libXcursor.x86_64 libgcc.i686 libgcc.x86_64 expat.i686 expat.x86_64 libX11.i686 libX11.x86_64 libXfixes.i686 libXfixes.x86_64 libXrender.i686 libXrender.x86_64 libXau.i686 libXau.x86_64 libxcb.i686 libxcb.x86_64 openmotif.i686 openmotif.x86_64 cifs-utils.x86_64 acl.x86_64 glibc-common.x86_64 environment-modules.x86_64
After completing the libraries installation, install the mcelog 101-0.x86_64
library.
Caution: Ensure to install only the 101-0.x86_64
version of mcelog
library. If you have installed any other version on mcelog library uninstall it and install only this version.
You can upgrade to the latest mcelog
version after completing the OBR installation.
Vertica
EXT4 is the recommended file system for Vertica.
Linux Logical Volume Manager (LVM) is not supported on partitions that contain HP Vertica files.
Web Browser Requirements
Web browsers are only supported on Windows. Use a Windows system to access the HPE OBR Administration Console, even when HPE OBR is installed on Linux.
Port Availability
HPE OBR uses a number of default ports for its different services listed in the following table:
Service |
Port Number |
Protocol |
Inbound |
Outbound |
Description |
---|---|---|---|---|---|
HPE PMDB Platform DB Logger |
21408 |
TCP |
Yes |
Yes |
The HPE PMDB Platform DB Logger service consolidates FATAL errors in a single log file. |
HPE PMDB Platform Collection |
21409 |
TCP |
Yes |
Yes |
The JMX management port for the Collection service. The IM service monitors collection using this interface. |
HPE PMDB Platform IM |
21410 |
TCP |
Yes |
No |
The JMX management port for the IM service. |
HPE PMDB Platform Timer |
No port |
NA |
NA |
NA |
The Timer service for HPE OBR. |
HPE PMDB Platform Orchestration | 21424 | TCP | Yes | No |
The Orchestration service for HPE OBR. |
HPE PMDB Platform Administrator |
21411 |
TCP |
Yes |
No |
The HPE OBR web application server port, which hosts the Administration web application. The Report cross-launch functionality depends on this service. |
HP Vertica Service | 5433 | TCP | Yes | No | Port for the Vertica database. |
HP Vertica Service | 5434 | TCP | Port for the Vertica database. Intra-cluster communication | ||
HP Vertica Management Console | 5444 | TCP | MC-to-node and node-to-node (agent) communications port. | ||
HP Vertica Management Console | 5450 | TCP | Port used to connect to Management Console from a web browser and allows communication from nodes to the Management Console application/web server. | ||
Vertica Spread | 4803 | TCP | Yes | No |
Port for the Vertica Spread connections. Client connections. |
Vertica Spread | 4804 | TCP |
Daemon to Daemon connections. |
||
Vertica Spread | 6543 | UDP |
Port for the Vertica Spread connections. Monitor to Daemon connection. |
||
HPE Software Communication Broker |
383 |
TCP |
Yes |
Yes |
HPE OBR uses this port to communicate with collectors installed on remote servers. |
Administration Console web server |
21416 |
TCP |
Yes |
Yes |
The JMX management port for the HPE OBR administration web server. |
HPE PMDB Platform Collection | 21418 | HTTP | Yes | No | The connection port to HTTP server for the SiteScope generic data integration. |
HPE PMDB Platform Collection | 21419 | HTTPS | Yes | No | The connection port to HTTPS server for the SiteScope generic data integration. |
HPE PMDB Platform Collection | 8080 | HTTP | No | Yes | The connection port to collect data from the SiteScope Data Acquisition API. |
HPE PMDB Platform Collection | 9998 | TCP | Yes | No | The connection port to collect data from the Network Automation (NA) and Server Automation (SA). |
HPE-SHR-Postgre - PostgreSQL Server 9.0 |
21425 |
TCP |
Yes |
Yes |
Port for the PostgreSQL service. |
Apache Tomcat |
8080 |
TCP |
Yes |
No |
This is the SAP BusinessObjects Application Service port. The SAP BusinessObjects Central Management Console and the SAP BusinessObjects BI launch pad web applications are hosted on this port. |
SAP BOBJ Central Management Server |
6400 |
TCP |
Yes |
Yes |
This is the port for the SAP BusinessObjects Central Management Server, which is mainly used for SAP BusinessObjects authentication purposes. |
Server Intelligence Agent (OBR) |
6410 |
TCP |
Yes |
Yes |
Port for the SAP BusinessObjects Server Intelligence Agent, which manages all SAP BusinessObjects-related tasks. |
BOE120SQLAW |
2638 |
TCP |
Yes |
Yes |
Port for the SAP BusinessObjects repository database. |
RTSM |
21212 |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the RTSM data source. Using this port, HPE OBR connects to RTSM. |
HPOM |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the HPOM database. HPE OBR uses this port to connect to the HPOM database. |
HP Operations Agent |
383 |
TCP |
No |
Yes |
HPE OBR uses this port to connect to the HP Operations agent. |
HP BSM Profile database |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the Profile database. |
Preinstallation Tasks
Note: Make sure to check whether HP/BSM
directory or other HP products directories exists before installing HPE OBR. If HP/BSM
is present and contains no files and directories, delete it and move ahead with HPE OBR installation.
After the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for the HPE OBR installation.
Task 1:Increase swap space
To allocate sufficient swap space, perform the following steps:
Log on to the system as root
user.
Note: The root
user must be the owner of the /opt
and /var
directories.
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
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
Task 2: Disable Anti-Virus
Anti-virus applications can hinder the installation of HPE OBR. Temporarily disable any anti-virus software that is running.
Once the installation is complete, enable the anti-virus software.
Task 3: Configure Firewall
If you are using the firewall software, ensure that the firewall allows traffic through the required ports on the HPE OBR system. For more information on port availability, see the section Prerequisites > Port Availability.
To disable the firewall, perform the following steps:
Log on as root
user and run the following commands:
Note: The root
user must be the owner of the /opt
and /var
directories.
chkconfig iptables off
chkconfig ip6tables off
/etc/init.d/iptables stop
/etc/init.d/ip6tables stop
Task 4: Prepare the Linux Server
You must perform the following tasks to prepare the Linux server for installation.
Task 4.1: Disable SELinux
To disable SELinux, in the /etc/sysconfig/selinux
file, set the parameter SELINUX = disabled
.
Task 4.2: Configure the Kernel Parameters (only if you use Red Hat Enterprise Linux 6.x)
To configure the Kernel parameters, follow these steps:
Open the file /etc/sysctl.conf
file and set the values of the parameters as given below:
Note: If these parameters have higher values specified already, do not make any changes.
Note: After the successful Vertica database creation, additional parameter of vm.max_map_count
with different value based on the hardware configuration will be added. Delete the entry that has the minimum value.
Task 4.3: Configure the Host name
Log on to the HPE OBR system, and configure the hostname in the /etc/hosts
file.
If you configure a hostname, it should be added after the following two lines as they appear by default.
127.0.0.1 localhost.localdomain localhost
::1 server1.example.com server1
The naming convention for the hostname is: <IP address> <FQDN of HPE OBR host system> <Short name of HPE OBR host system>
Task 4.4: Configure the limits.conf
file
Open the /etc/security/limits.conf
file and increase the number of open files by setting the following values:
*
soft nofile 65535
*
hard nofile 65535
Task 4.5: Configure the 90-nproc.conf
file (only if you use Red Hat Enterprise Linux 6.x)
Open the /etc/security/limits.d/90-nproc.conf
file and comment out the following line by adding a # character in the beginning:
#*soft nproc 1024
The reason to add # character is to increase the number of user processes for SAP BusinessObjects and Vertica database in setenv.sh
file.
Restart the Linux system for the changes to take effect.
Task 5: Verify the Fully Qualified Domain Name (FQDN) of the system
Before installing HPE OBR, verify that DNS lookup returns the accurate FQDN of the host system. If the entry for the DNS lookup is different from the host name of the system, the log in to the HPE OBR Administration Console will fail. This is because during the SAP BusinessObjects installation, the host name of the system is used for creating the servers/services and registering them.
To verify the FQDN of the host system, follow these steps:
Open the command line interface and type the following command to check the host name of the system:
hostname -f
Type the following command to view the IP address of the system:
ifconfig
Type the following command to verify the FQDN of the displayed IP address:
nslookup
<IP_address>
where, <IP address
> is the IP address of the host system.
Ensure that the name returned by the lookup
command is same as the hostname
command. If the names do not match, you must change the hostname of the system.
Task 6: Linux Operating System configuration for Vertica
Perform the following tasks on the Vertica server:
Task 6.1: Disk Readahead
The following commands must be run with root privileges:
Note: You must ensure to apply the following command based on the disk sda, sdb, sdc, sdd
and the location of blockdev program.
The following command assumes the blockdev program is in /sbin
:
/sbin/blockdev --setra 2048 /dev/sda
echo '/sbin/blockdev --setra 2048 /dev/sda' >> /etc/rc.local
The blockdev program operates on whole devices, and not individual partitions.
Task 6.2: Transparent hugepages
The transparent hugepages must be disabled
or set to madvise
.
To verify if transparent hugepages is enabled, run the following command:
cat /sys/kernel/mm/redhat_transparent_hugepage/enabled
The output in brackets is the current setting as follows:
[always] madvise never
To disable transparent hugepages perform any one of the following steps:
Edit the boot loader (for example /etc/grub.conf
), add the following at the end of the kernel line:
transparent_hugepage=never
Edit /etc/rc.local
and add the following script:
echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled
Note: For systems that do not support /etc/rc.local, use the equivalent startup script.
Task 6.3: I/O scheduling set to deadline or noop
Viewing the contents of this file shows you all of the possible settings for the scheduler, with the currently-selected scheduler surrounded by square brackets:
Run the following command to view the scheduler settings:
cat /sys/block/sda/queue/scheduler
The output in brackets is the current setting as follows:
noop deadline [cfq]
To change the scheduler, type the name of the scheduler as root user.
The following example assumes to set the sda
drive to use the deadline scheduler, run the following command as root:
echo deadline > /sys/block/sda/queue/scheduler
cat /sys/block/sda/queue/scheduler
noop [deadline] cfq
Task 7: Assemble the media
The HPE Operations Bridge Reporter (HPE OBR) software is available in three TAR image part files.
HPEOBR_1000_Lin64.part1
HPEOBR_1000_Lin64.part2
HPEOBR_1000_Lin64.part3
Before you start installing HPE OBR, you must download .tar
file into a single location and perform a merge of the contents.
Note: You must not download the .tar
file under /opt
directory.
Step1: Download the TAR Image Part Files and Check for File Integrity
Step 2: Merge the TAR Image Part Files
Download the TAR Image parts into a temporary folder on the system where you intend to install HPE OBR.
For example: /tmp/HPEOBR_1000-parts
.
To change directory to the location where you copied the contents of the image part files, run the following command:
cd <temp location>
For example: cd /tmp/HPEOBR_1000-parts
Note: Ensure that you have adequate space in the directory.
To merge the contents into a single TAR Image file, run following command:
cat HPEOBR_1000_Lin64.part1 HPEOBR_1000_Lin64.part2 HPEOBR_1000_Lin64.part3 > /tmp/HPEOBR_1000-parts/HPEOBR_1000_Lin64.tar
Note: You must type the command in a single line.
Step 3: Verify the Reassembly of the Build Segments
Compare and verify if the md5 checksum of merged file matches with the corresponding md5 checksum value as listed in “Distribution Contents and MD5 Checksum Values”.
Distribution Contents and MD5 Checksum Values:
The HPE OBR media is now available as a single .tar
file in the following location:
File Name | Size | MD5 Checksum |
---|---|---|
HPEOBR_1000_Lin64.part1 | 4294967296 | 77c5c7c321f86d01d65652a3d4134d54 |
HPEOBR_1000_Lin64.part2 | 4294967296 | ac3bc2431b47a61f0e56056f0cd99571 |
HPEOBR_1000_Lin64.part3 | 1293877248 | e22b651e4f985785c0bdaca3eae10b73 |
HPEOBR_1000_Lin64.tar (Merged file) | 9883811840 | 7d2c4c002ffeee1bc94778243e6ed506 |
The HPE OBR media is now available as a single TAR file in the following location:
/tmp/HPEOBR_1000-parts
/HPEOBR_1000.tar
Note: You must ensure that the parent directory of the unzipped .tar
folder has all the access rights (777) to the owner and to the other groups as a requirement for SAP BusinessObjects.
For example, if you have unzipped the TAR file in /installer/OBR
, the installer
folder should have 777 permissions.
Unzip the .tar
file, you will find the HP-SHR_10.00_setup.bin
to move ahead with the installation.
Task 8: Run the HPE OBR Installation Pre-Check Tool
The HPE OBR Installation Pre-check tool verifies the necessary pre-requisites before installing HPE OBR.
Follow these steps to run the Pre-Check tool:
On the system which you plan to install HPE OBR, download the HPE OBR Installation Pre-check tool from the link:
https://hpln.hpe.com/contentoffering/hpe-obr-installation-pre-check-tool
Unzip the .zip
file.
OBR10_InstallPrecheck_README.pdf
to run the Pre-check tool.Additional Considerations
Log on to the system as root
user.
Note: The root
user must be the owner of the /opt
and /var
directories.
Note: The HPE OBR installer does not support forced reinstall. In the event of an unsuccessful installation, you must manually remove all the files that were placed by the installer and perform installation again.
Additional Information
After successful OBR install:
The HPE OBR installer by default creates the postgres
and shrboadmin
users as mentioned in the following table:
User | Group | Home Directory |
---|---|---|
postgres |
postgres
|
/opt/HP/BSM/Postgres
|
shrboadmin
|
shrboadmin
|
/home/shrboadmin
|
<Vertica user>
|
<Vertica group>
|
/home/
|
These users must be local to the system and can be created manually before installing HPE OBR at the same location.
In the PMDB_HOME/bin/setenv.sh
file, the ulimit
value changes automatically for the root
user, <vertica user>
and postgres
user as shown in the following table. This value applies on next log on to the system.
Parameter | ulimit value | Recommended by |
---|---|---|
Number of file descriptors | 65535 | Vertica |
Number of user process | 127510 | SAP BusinessObjects |
Install using the Command Line Console
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.
At the command prompt, type the following command:
./HP-SHR_10.00_setup.bin -i console
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.
Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.
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.
Type 1 to select HPE Operations Bridge Reporter Server and press Enter.
Note: Ensure that you type the relevant numerical identifier provided in the HPE Operations Bridge Reporter installer for each of the HPE OBR component that you want to install.
To install multiple server components, include a comma between the numerical identifiers. For example, to install HPE Operations Bridge Reporter Server and Vertica Server together, type 1,2 and press Enter.
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.
/tmp/SHR-Missing-Patches.txt
and install them. Start the HPE OBR installation again.If the prerequisite check is successful, press Enter.
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:
Run the following command:
sh rollback-utility.sh
The postgres
user is created on the system on successful OBR installation.
Apply the HPE OBR 10.01 patch. For steps, see HPE Operations Bridge Reporter Release Notes.
Install using the Command Line Console
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.
At the command prompt, type the following command:
./HP-SHR_10.00_setup.bin -i console
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.
Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.
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.
Type 2 to select Vertica Server and press Enter.
Note: Ensure that you type the relevant numerical identifier provided in the HPE Operations Bridge Reporter installer for each of the HPE OBR component that you want to install.
To install multiple server components, include a comma between the numerical identifiers. For example, to install HPE Operations Bridge Reporter Server and Vertica Server together, type 1,2 and press Enter.
The installer performs necessary prerequisite checks and displays the result.
/tmp/SHR-Missing-Patches.txt
and install them. Start the HPE OBR installation again.After successful prerequisite check, press Enter.
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.
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:
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:
For steps on scale out and High Availability setup, see the following chapters of HPE Operations Bridge Reporter High Availability Guide:
Setting up Vertica Cluster
Note: If you have completed running the CreateVerticaDatabase.sh
then skip the Step 1 in this chapter and proceed with next steps.
Configuring Vertica Cluster
Install using the Command Line Console
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.
At the command prompt, type the following command:
./HP-SHR_10.00_setup.bin -i console
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.
Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.
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.
Type 1, 2 to select HPE Operations Bridge Reporter Server and Vertica Server and press Enter.
Note: Ensure that you type the relevant numerical identifier provided in the HPE Operations Bridge Reporter installer for each of the HPE OBR component that you want to install.
The installer performs necessary prerequisite checks and displays the result.
/tmp/SHR-Missing-Patches.txt
and install them. Start the HPE OBR installation again.After successful prerequisite check, press Enter.
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:
Run the following command:
sh rollback-utility.sh
The postgres
user and <vertica user>
are created on the system on successful OBR components installation.
Apply the HPE OBR 10.01 patch. For steps, see HPE Operations Bridge Reporter Release Notes.
Install using the Command Line Console
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.
At the command prompt, type the following command:
./HP-SHR_10.00_setup.bin -i console
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.
Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.
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.
Type 3 to select SAP BusinessObjects Server and press Enter.
Note: Ensure that you type the relevant numerical identifier provided in the HPE Operations Bridge Reporter installer for each of the HPE OBR component that you want to install.
The installer performs necessary prerequisite checks and displays the result.
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 HPE OBR installation again.
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.
Apply the HPE OBR 10.01 patch. For steps, see HPE Operations Bridge Reporter Release Notes.
Install using the Command Line Console
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.
At the command prompt, type the following command:
./HP-SHR_10.00_setup.bin -i console
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.
Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.
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.
Type 1, 3 to select HPE Operations Bridge Reporter Server and SAP BusinessObjects Server and press Enter.
Note: Ensure that you type the relevant numerical identifier provided in the HPE Operations Bridge Reporter installer for each of the HPE OBR component that you want to install.
The installer performs necessary prerequisite checks and displays the result.
/tmp/SHR-Missing-Patches.txt
and install them. Start the HPE OBR installation again.After successful prerequisite check, press Enter.
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:
Run the following command:
sh rollback-utility.sh
The postgres
user and shrboadmin
user are created on the system on successful OBR components installation.
Apply the HPE OBR 10.01 patch. For steps, see HPE Operations Bridge Reporter Release Notes.
Install using the Command Line Console
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.
At the command prompt, type the following command:
./HP-SHR_10.00_setup.bin -i console
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.
Press Enter again. The installer displays the Introduction in the console. Press Enter to continue.
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.
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 HPE Operations Bridge Reporter installer for each of the HPE OBR component that you want to install.
The installer performs necessary prerequisite checks and displays the result.
/tmp/SHR-Missing-Patches.txt
and install them. Start the HPE OBR installation again.After successful prerequisite check, press Enter.
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.
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:
Run the following command:
sh rollback-utility.sh
Install using the Command Line Console
HPE 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 HPE 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:
Make sure that HPE 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://<HPE 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, <HPE OBR_HostName
> is the fully qualified domain name of the OBR system.
Go to the installation directory:
/opt/HP/BSM/BOE4
./modifyOrRemoveProducts.sh
to start the language pack installer. The Application Maintenance page appears.Select Modify and press Enter.
A list of SAP BusinessObjects language pack is displayed as shown in the following image:
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.
Click Next again. The Existing CMS Deployment Information page appears.
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.
In a Custom installation the HPE Operations Bridge Reporter Server, Vertica Server and SAP BusinessObjects Server are installed on different systems. The following prerequisites must be fulfilled on all systems.
Note: These prerequisites are also applicable to the systems where you want to install the HPE OBR Remote Collector.
Prerequisites
Following are additional prerequisites for a successful HPE OBR install:
Web Browser Requirements
Web browsers are only supported on Windows. Use a Windows system to access the HPE OBR Administration Console, even when HPE OBR is installed on Linux.
Port Availability
HPE OBR uses a number of default ports for its different services listed in the following table:
Service |
Port Number |
Protocol |
Inbound |
Outbound |
Description |
---|---|---|---|---|---|
HPE PMDB Platform DB Logger |
21408 |
TCP |
Yes |
Yes |
The HPE PMDB Platform DB Logger service consolidates FATAL errors in a single log file. |
HPE PMDB Platform Collection |
21409 |
TCP |
Yes |
Yes |
The JMX management port for the Collection service. The IM service monitors collection using this interface. |
HPE PMDB Platform IM |
21410 |
TCP |
Yes |
No |
The JMX management port for the IM service. |
HPE PMDB Platform Timer |
No port |
NA |
NA |
NA |
The Timer service for HPE OBR. |
HPE PMDB Platform Orchestration | 21424 | TCP | Yes | No |
The Orchestration service for HPE OBR. |
HPE PMDB Platform Administrator |
21411 |
TCP |
Yes |
No |
The HPE OBR web application server port, which hosts the Administration web application. The Report cross-launch functionality depends on this service. |
HP Vertica Service | 5433 | TCP | Yes | No | Port for the Vertica database. |
HP Vertica Service | 5434 | TCP | Port for the Vertica database. Intra-cluster communication | ||
HP Vertica Management Console | 5444 | TCP | MC-to-node and node-to-node (agent) communications port. | ||
HP Vertica Management Console | 5450 | TCP | Port used to connect to Management Console from a web browser and allows communication from nodes to the Management Console application/web server. | ||
Vertica Spread | 4803 | TCP | Yes | No |
Port for the Vertica Spread connections. Client connections. |
Vertica Spread | 4804 | TCP |
Daemon to Daemon connections. |
||
Vertica Spread | 6543 | UDP |
Port for the Vertica Spread connections. Monitor to Daemon connection. |
||
HPE Software Communication Broker |
383 |
TCP |
Yes |
Yes |
HPE OBR uses this port to communicate with collectors installed on remote servers. |
Administration Console web server |
21416 |
TCP |
Yes |
Yes |
The JMX management port for the HPE OBR administration web server. |
HPE PMDB Platform Collection | 21418 | HTTP | Yes | No | The connection port to HTTP server for the SiteScope generic data integration. |
HPE PMDB Platform Collection | 21419 | HTTPS | Yes | No | The connection port to HTTPS server for the SiteScope generic data integration. |
HPE PMDB Platform Collection | 8080 | HTTP | No | Yes | The connection port to collect data from the SiteScope Data Acquisition API. |
HPE PMDB Platform Collection | 9998 | TCP | Yes | No | The connection port to collect data from the Network Automation (NA) and Server Automation (SA). |
HPE-SHR-Postgre - PostgreSQL Server 9.0 |
21425 |
TCP |
Yes |
Yes |
Port for the PostgreSQL service. |
Apache Tomcat |
8080 |
TCP |
Yes |
No |
This is the SAP BusinessObjects Application Service port. The SAP BusinessObjects Central Management Console and the SAP BusinessObjects BI launch pad web applications are hosted on this port. |
SAP BOBJ Central Management Server |
6400 |
TCP |
Yes |
Yes |
This is the port for the SAP BusinessObjects Central Management Server, which is mainly used for SAP BusinessObjects authentication purposes. |
Server Intelligence Agent (OBR) |
6410 |
TCP |
Yes |
Yes |
Port for the SAP BusinessObjects Server Intelligence Agent, which manages all SAP BusinessObjects-related tasks. |
BOE120SQLAW |
2638 |
TCP |
Yes |
Yes |
Port for the SAP BusinessObjects repository database. |
RTSM |
21212 |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the RTSM data source. Using this port, HPE OBR connects to RTSM. |
HPOM |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the HPOM database. HPE OBR uses this port to connect to the HPOM database. |
HP Operations Agent |
383 |
TCP |
No |
Yes |
HPE OBR uses this port to connect to the HP Operations agent. |
HP BSM Profile database |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the Profile database. |
Preinstallation Tasks
After the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for the HPE 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.
Task 2: Disable Anti-Virus
Anti-virus applications can hinder the installation of HPE OBR. Temporarily disable any anti-virus software that is running.
Once the installation is complete, enable the anti-virus software.
Task 3: Configure Firewall
If you are using the firewall software, ensure that the firewall allows traffic through the required ports on the HPE OBR system. For more information on port availability, see the section Prerequisites > Port Availability.
Task 4: Verify the Fully Qualified Domain Name (FQDN) of the system
Before installing HPE OBR, verify that DNS lookup returns the accurate FQDN of the host system. If the entry for the DNS lookup is different from the host name of the system, the log in to the HPE OBR Administration Console will fail. This is because during the SAP BusinessObjects installation, the host name of the system is used for creating the servers/services and registering them.
To verify the FQDN of the host system, follow these steps:
Type the following command in the command line interface to check the host name of the system:
hostname
Note down the host name of the system.
Type the following command to view the IP address of the system:
ipconfig
Type the following command to verify the FQDN of the displayed IP address:
nslookup
<IP_address>
where, <IP address
> is the IP address of the host system.
Ensure that the name returned by the lookup
command is same as the hostname
command. If the names do not match, you must change the hostname of the system.
Task 5: Disable User Account Control (UAC)
Perform the following steps on Windows Server 2012 system to disable UAC:
Click Start > Run. The Run dialog box appears.
In the Open box, type regedit
. The Registry Editor window appears.
On the left pane, expand HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > policies
Double-click on System. The list appears on the right pane.
Double-click the EnableLUA and type 0
in Value data. You must ensure that EnableLUA Value data is always 0
.
You will get a notification to restart your system. The UAC will be disabled after you restart the system.
Task 6: Install Microsoft .NET Framework 3.5
The Management database component of HPE OBR requires Microsoft .Net Framework 3.5 on Windows 2012 server.
Perform the following steps to install Microsoft .NET Framework 3.5 on Windows 2012 server:
Task 7: Set a Static IPv6 Address on Windows Server 2012 (Applicable only for communication protocol is IPv6)
Perform this task if your communication protocol is IPv6.
Before installing HPE OBR on a Windows Server 2012 server with the communication protocol IPv6, you must assign a static IPv6 address.
By default, the interface ID is randomly derived in Windows Server 2012. It is not based on the Extended Unique Identifier (EUI)-64 address. You must disable the random interface IDs. For more information to set static IPv6, see Microsoft documentation or contact your Windows Administrator.
Task 8: Increase the Non-interactive Desktop Heap
In a single user session, every desktop object is associated with a desktop heap memory. The desktop heap stores certain user interface objects such as windows, menus, and hooks.
Desktop heap exhaustion can prevent certain processes from starting or cause processes to fail. To avoid desktop heap usage issues, you must change the default value of the heap memory in the Registry Editor.
Before you install HPE OBR on Windows Server 2012, follow these steps to increase the non-interactive desktop heap:
regedit
in the Open box. The Registry Editor window appears.You must make sure to restart the system after completing all of the above tasks and then move ahead with the next tasks.
Task 9: Assemble the media
The HPE Operations Bridge Reporter (HPE OBR) software is available in three TAR image part files.
HPEOBR_1000_Win64.part1
HPEOBR_1000_Win64.part2
HPEOBR_1000_Win64.part3
Before you start installing HPE OBR, you must download all 3 TAR file parts into a single temporary location and perform a merge of the contents.
Step1: Download the TAR Image Part Files and Check for File Integrity
Evaluate the md5 checksum of the downloaded image part File then compare and verify if it matches with the corresponding md5 checksum value as listed in “Distribution Contents and MD5 Checksum Values”.
Step 2: Merge the TAR Image Part Files
Download the TAR Image parts into a temporary folder on the system where you intend to install HPE OBR.
For example, C:\temp\HPEOBR_1000-parts
.
To change directory to the location where you copied the contents of the image part files, run the following command:
cd <temp location>
For example, cd C:\temp\HPEOBR_1000-parts
Note: Ensure that you have adequate space in the directory.
To merge the contents into a single TAR Image file, run following command:
copy /b HPEOBR_1000_Win64.part1 HPEOBR_1000_Win64.part2 HPEOBR_1000_Win64.part3 C:\temp\HPEOBR_1000-parts\HPEOBR_1000_Win64.tar
or
type HPEOBR_1000_Win64.part1 HPEOBR_1000_Win64.part2 HPEOBR_1000_Win64.part3 >> C:\temp\HPEOBR_1000-parts\HPEOBR_1000_Win64.tar
Note: You must type the command in a single line.
Step 3: Verify the Reassembly of the Build Segments
Compare and verify if the md5 checksum
of merged file matches with the corresponding md5 checksum value as listed in “Distribution Contents and MD5 Checksum Values”.
Distribution Contents and MD5 Checksum Values:
The distribution of HPE OBR software contains the following set of files:
File Name | Size | MD5 Checksum |
---|---|---|
HPEOBR_1000_Win64.part1 | 4294967296 | b18b3b869603781b8596d068bc80f241 |
HPEOBR_1000_Win64.part2 | 4294967296 | a106eb0802ff63305fcbba3a3d326714 |
HPEOBR_1000_Win64.part3 | 871067648 | 487558b98f624ce503e0a72fa0b0c4a0 |
HPEOBR_1000_Win64.tar (Merged file) | 9461002240 | 249290c3d9acb91b15ef16ef883f15dd |
The HPE OBR media is now available as a single TAR file in the following location:
C:\temp\HPEOBR_1000-parts\HPEOBR_1000.tar
Unzip the .tar
file, you will find the HP-SHR_10.00_setup.exe
to move ahead with the installation.
Task 10: Run the HPE OBR Installation Pre-Check Tool
The HPE OBR Installation Pre-check tool verifies the necessary pre-requisites before installing HPE OBR.
Follow these steps to run the Pre-Check tool:
On the system which you plan to install HPE OBR, download the HPE OBR Installation Pre-check tool from the link:
https://hpln.hpe.com/contentoffering/hpe-obr-installation-pre-check-tool
Unzip the .zip
file.
OBR10_InstallPrecheck_README.pdf
to run the Pre-check tool.Additional Considerations
Note: The HPE OBR installer does not support forced reinstallation. In the event of an unsuccessful installation, manually remove all the files that were placed by the installer and perform installation again.
Installation User Account
Run the following file:
HP-SHR_10.00_setup.exe
The setup files are extracted.
Select the language to install HPE OBR, and click OK.
The HPE Operations Bridge Reporter 10.0 Software Installer wizard appears.
On the Introduction page, review the note and click Next.
Select HPE Operations Bridge Reporter Server and click Next.
Enter the FQDN of the host where you plan to install (or have already installed) SAP BusinessObjects.
Review the folders in which OBR will be installed. To change the installation folders, use the Browse buttons. Click Next.
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.
Note: You must ensure to configure DSN on HPE 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 HPE Operations Bridge Reporter Configuration Guide.
If you plan to install another HPE 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:
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.
Apply the HPE OBR 10.01 patch. For steps, see HPE Operations Bridge Reporter Release Notes.
To install SAP BusinessObjects using the installation wizard, follow these steps:
Run the following file:
HP-SHR_10.00_setup.exe
The setup files are extracted.
Select the language to install HPE OBR, and click OK.
The HPE Operations Bridge Reporter 10.0 Software Installer wizard appears.
Select SAP BusinessObjects Server and click Next.
Review the folders in which HPE OBR will be installed. To change the installation folders, use the Browse buttons. Click Next.
Enter the SAP BusinessObjects install drive. The default value is C
.
Note: Enter only the alphabet that denotes the drive. For example, enter C and not C:\ or C:.
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.
If you plan to install another HPE 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:
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.
Apply the HPE OBR 10.01 patch. For steps, see HPE Operations Bridge Reporter Release Notes.
To install HPE Operations Bridge Reporter Server and SAP BusinessObjects Server on a single Windows system using the installation wizard, follow these steps:
Run the following file:
HP-SHR_10.00_setup.exe
The setup files are extracted.
Select the language to install HPE OBR, and click OK.
The HPE Operations Bridge Reporter 10.0 Software Installer wizard appears.
Select HPE Operations Bridge Reporter Server and SAP BusinessObjects Server and click Next.
Review the folders in which HPE OBR will be installed. To change the installation folders, use the Browse buttons. Click Next.
Enter the SAP BusinessObjects install drive. The default value is C
.
Note: Enter only the alphabet that denotes the drive. For example, enter C and not C:\ or C:.
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.
Note: You must ensure to configure DSN on HPE 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 HPE Operations Bridge Reporter Configuration Guide.
If you plan to install another HPE 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:
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.
Apply the HPE OBR 10.01 patch. For steps, see HPE Operations Bridge Reporter Release Notes.
HPE 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 HPE 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:
Make sure that HPE 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://<HPE 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, <HPE OBR _HostName
> is the fully qualified domain name of the OBR system.
Go to the following directory:
<HPE OBR media root>\packages\BO\DATA_UNITS\BusinessObjectsServer_win
where <HPE OBR media root>
is the location where the OBR installer is available.
setup.exe
to start the language pack installer. The installer wizard appears.Select Modify and click Next.
Note: Modify will be selected by default.
The wizard displays a list of SAP BusinessObjects language pack as follows:
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.
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.
Perform the following steps to verify the success of installation:
Tip: If you have any other java installations on the HPE OBR installed system, make sure the JAVA_HOME
directory points to java installed as part of HPE OBR installation.
Validating services
Perform the following to verify the success of installation on Linux operating system:
Run the following command:
chkconfig --list
The command output lists the all the services of HPE OBR.
HPE_PMDB_Platform_Administrator
HPE_PMDB_Platform_Collection
HPE_PMDB_Platform_DB_Logger
HPE_PMDB_Platform_IA
HPE_PMDB_Platform_IM
HPE_PMDB_Platform_NRT_ETL
HPE_PMDB_Platform_PostgreSQL
HPE_PMDB_Platform_Orchestration
Run the following commands in the command line console to ensure if the services are running satisfactorily:
service HPE_PMDB_Platform_Administrator status
service HPE_PMDB_Platform_PostgreSQL status
SAP BusinessObjects services
To check the status of the SAP BusinessObjects services, run the following commands at the command line console:
su - shrboadmin
cd /opt/HP/BSM/BOE4/sap_bobj
./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.
Tip: If you have any other java installations on the HPE OBR installed system, make sure the JAVA_HOME
directory points to java installed as part of HPE OBR installation.
Generating a Certificate Authority Signed Certificate
In HPE OBR, HTTPs communication is enabled by default for Administrator console and SAP BusinessObjects. HPE OBR uses the self-signed certificate. However, it is highly recommended to use the Certificate Authority (CA) certificate.
Note: The certificate shipped by HPE OBR out-of-box is valid for only three months from the date of installation. Ensure to perform the following steps before you begin the post-install configuration.
To get a CA signed certificate and configure HPE OBR to use this certificate, perform these steps:
Open the command prompt and take a backup of the existing keystore file from the following location:
On Linux: $PMDB_HOME/keystore/SHR_CERT_HTTPS.jks
.
Move the SHR_CERT_HTTPS.jks
file from {PMDB_HOME}/keystore
to another location.
Generate a private key from your system using the keytool command.
Run the following command:
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
Enter the requested information.
Note: When prompted for first and last name, enter the FQDN (fully-qualified domain name) of your system.
Run the following command exactly as shown to create a Certificate Signing Request (CSR) file:
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
Send the CSR (CERTREQFILE
) to your CA signing authority. They should provide you with one of the following:
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.
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.
Copy the files containing these certificates to the HPE OBR server on the following location:
On Linux: $PMDB_HOME/keystore
Run the following command to import the server certificate and the CA certificate into the HPE OBR SHR_CERT_HTTPS.jks
file:
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
Run the following commands to import the CA certificate into the HPE OBR SHR_TRUSTSTORE file:
On Linux: $PMDB_HOME/../JRE64/bin/keytool -import -alias myca -keystore $PMDB_HOME/keystore/SHR_TRUSTSTORE -file myca.crt
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:
/opt/HP/BSM/PMDB/adminServer/conf/server.xml
keystorePass
value in the server.xml
file with the <password>
.For SAP BusinessObjects
/opt/HP/BSM/PMDB/BOWebServer/conf/server.xml
keystorePass
value in the server.xml
file with the <password>
.Restart the HPE OBR services by running the below commands:
On Linux
service HP_PMDB_Platform_Administrator stop
service SAPBOBJEnterpriseXI40 stop
service HP_PMDB_Platform_Administrator start
service SAPBOBJEnterpriseXI40 start
Test the HTTPS access to the HPE OBR Administration console and SAP BusinessObjects Launch pad using the following syntax:
https://<HPE OBR hostname>:21412/BSMRApp
https://<hostname>:8443/BOE/BI
After you complete the installation and Generating a Certificate Authority Signed Certificate, you must configure HPE OBR so that it can collect data from the sources. For information to configure HPE OBR, see HPE Operations Bridge Reporter Configuration Guide.
For information to schedule the back up, see Database Backup and Recovery section in the HPE Operations Bridge Reporter Configuration Guide.
Generating a Certificate Authority Signed Certificate
In HPE OBR, HTTPs communication is enabled by default for Administrator console and SAP BusinessObjects. HPE OBR uses the self-signed certificate. However, it is highly recommended to use the Certificate Authority (CA) certificate.
Note: The certificate shipped by HPE OBR out-of-box is valid for only three months from the date of installation. Ensure to perform the following steps before you begin the post-install configuration.
To get a CA signed certificate and configure HPE OBR to use this certificate, perform these steps:
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.
Generate a private key from your system using the keytool command.
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
Enter the requested information.
Note: When prompted for first and last name, enter the FQDN (fully-qualified domain name) of your system.
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
Send the CSR (CERTREQFILE
) to your CA signing authority. They should provide you with one of the following:
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.
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.
Copy the files containing these certificates to the HPE OBR server on the following location:
On Windows: %PMDB_HOME%\keystore
On Linux: $PMDB_HOME/keystore
Run the following command to import the server certificate and the CA certificate into the HPE 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
Run the following commands to import the CA certificate into the HPE 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
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:
{PMDB_HOME}/adminServer/conf/server.xml
keystorePass
value in the server.xml
file with the <password>
.For SAP BusinessObjects
{PMDB_HOME}/BOWebServer/conf/server.xml
keystorePass
value in the server.xml
file with the <password>
.Restart the HPE OBR services by running the below commands:
On Windows:
services.msc
.In the services window, right-click and select Stop for the following services:
Wait for a while for the services to stop.
Right-click and select Start for the following services:
On Linux
service HP_PMDB_Platform_Administrator stop
service SAPBOBJEnterpriseXI40 stop
service HP_PMDB_Platform_Administrator start
service SAPBOBJEnterpriseXI40 start
Test the HTTPS access to the HPE OBR Administration console and SAP BusinessObjects Launch pad using the following syntax:
https://<HPE OBR hostname>:21412/BSMRApp
https://<hostname>:8443/BOE/BI
After you complete the installation and Generating a Certificate Authority Signed Certificate, you must configure HPE OBR so that it can collect data from the sources. For more information to configure HPE OBR, see HPE Operations Bridge Reporter Configuration Guide.
For information to schedule the back up, see Database Backup and Recovery section in the HPE Operations Bridge Reporter Configuration Guide.
During HPE OBR Server installation, the collector also gets installed on the same server. You can install the collector on a separate server that does not have any other HPE OBR components installed. Also, you can install Remote Collectors on multiple systems as necessary.
If you want to install HPE OBR and HPE Operations Agent on the same system, you must perform the following additional configuration steps:
Install HPE Operations Agent on an HPE OBR system.
Log on to the HPE OBR system as administrator for Windows or root for Linux.
In the command line console, run the following command:
ovcert -list
The list of certificates installed on the system is displayed.
From the command line console, note down the contents of the Certificates and Trusted Certificates field under the Keystore Content section.
Example:
On the HPE 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.
On the HPE 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.
Use the oainstall.vbs -configure
or oainstall.sh -configure
command to configure the agent to work with the HPOM management server or the OMi management server. For more information, see the HPE Operations Agent and HPE Operations Smart Plug-ins for Infrastructure Installation Guide.
If you get the following error:
"Failed to start (some) OVO agent processes. See OVO log file and event log."
ovc -kill
command in the command line console. ovc
command.ovcd.exe
, right-click it and select End Process.You can proceed to configure the agent to work with HPOM management server or the OMi management server.
In the HPOM or OMi console, accept the certificate request of the HPE OBR node.
Follow these steps:
Run the following command on the HPE 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.
Run the following command on the HPE 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.
On the HPE OBR system, run the following command:
ovcert -trust
<Management_Server>
-ovrg server
In this instance, <Management_Server>
is the FQDN of the HPOM system or OMi system.
Run the following command on the HPE OBR system:
ovc -restart
Run the following command on the HPE OBR system:
ovcert -list -ovrg server
The trust certificates are displayed. If trust certificates are absent, perform the following steps:
Run the following commands on the HPE 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.
Run the following command on the HPE OBR system:
ovc -status -level 8
The HPE OBR Policy call backs (shrcb)
parameter must be listed.
If not listed, run the following command:
ovcreg -add $PMDB_HOME/config/shr.xml
Run the following command on the HPE OBR system:
ovc -restart
If the restart of HPE OBR system is not successful or if the system hangs, run the following commands:
ovc -kill
ovc -start
If you want to install HPE OBR and HPE Operations agent on the same system, you must perform the following additional configuration steps:
Install HPE Operations Agent on an HPE OBR system.
Log on to the HPE OBR system as administrator for Windows or root for Linux.
In the command line console, run the following command:
ovcert -list
The list of certificates installed on the system is displayed.
From the command line console, note down the contents of the Certificates and Trusted Certificates field under the Keystore Content section.
Example:
On the HPE 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.
On the HPE 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.
Use the oainstall.vbs -configure
or oainstall.sh -configure
command to configure the agent to work with the HPOM management server or the OMi management server. For more information, see the HPE Operations Agent and HPE Operations Smart Plug-ins for Infrastructure Installation Guide.
If you get the following error:
"Failed to start (some) OVO agent processes. See OVO log file and event log."
ovc -kill
command in the command line console. ovc
command.ovcd.exe
, right-click it and select End Process.You can proceed to configure the agent to work with HPOM management server or the OMi management server.
In the HPOM or OMi console, accept the certificate request of the HPE OBR node.
Follow these steps:
Run the following command on the HPE 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.
Run the following command on the HPE 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.
On the HPE OBR system, run the following command:
ovcert -trust
<Management_Server>
-ovrg server
In this instance, <Management_Server>
is the FQDN of the HPOM system or OMi server.
Run the following command on the HPE OBR system:
ovc -restart
Run the following command on the HPE OBR system:
ovcert -list -ovrg server
The trust certificates are displayed. If trust certificates are absent, perform the following steps:
Run the following commands on the HPE 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.
Run the following command on the HPE 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
Run the following command on the HPE OBR system:
ovc -restart
If the restart of HPE OBR system is not successful or if the system hangs, run the following commands:
ovc -kill
ovc -start
If you want to install an HPE OBR Remote Collector on a system with HPE Operations Agent, perform the following additional configuration steps:
Install HPE OBR Remote Collector on a separate system with HPE Operations Agent.
Log on to the Remote Collector system as administrator for Windows or root for Linux.
In the command line console, run the following command:
ovcert -list
In the command line console, the command shows a list of all certificates installed on the system.
From the command line console, note down the contents of the Certificates and Trusted Certificates field under the Keystore Content section.
Example:
On the Remote Collector 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.
On the Remote Collector 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.
Run the following command on the Remote Collector system:
perl %PMDB_HOME%\bin\scripts\configurePoller.pl
<HPOM or OMi_Server>
In the HPOM or OMi console, accept the certificate request of the HPE OBR node.
Follow these steps:
Run the following command on the HPE 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.
Manually copy the exported certificate to the Remote Collector system.
Run the following command on the Remote Collector 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.
Run the following command on the Remote Collector system:
ovc -restart
HPE 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 HPE OBR and they have to be installed individually.
You can install add-on content from the Content Catalog tab in the link HP Live Network - Operations Bridge Reporter.
HPE 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 HPE OBR and they have to be installed individually.
You can install add-on content from the Content Catalog tab in the link HP Live Network - Operations Bridge Reporter.
Appendix A
Install OBR when /opt
does not have enough space
Note: HPE OBR installation requires 20 GB
disk space in /opt
and it will exit if there is not enough space.
If /opt
does not have recommended space, you can install OBR by mounting free disk in /opt
as /opt/HP
, /opt/OV
and then follow these steps:
Note: You must ensure that the free disk has to be mounted in /opt
as /opt/HP
and not as a link.
Go to the media root.
Media root is the directory where the contents of the HPE OBR media (the .tar
file) are extracted.
At the command prompt, type the following command:
./HP-SHR_10.00_setup.bin -i console
Continue with the HPE OBR installation steps as provided in this guide.
Appendix B
Install OBR as non-root user
Follow these steps to install as a non-root user:
useradd
to create a user.If shr
is the non-root user name and shrgroup
is group name that non root user belongs to update the sudoers
file as follows:
sudo visudo
Add the below lines:
# shr is the user invoking installer
shr ALL=(ALL) ALL
# shrgroup for the user shr
%shrgroup ALL=(ALL) ALL
# shrgroup for the user shr
%shrgroup ALL=(ALL) NOPASSWD: ALL
As shr
user update the /etc/security/limits.conf
with the following values:
Note: The spaces in the following values are tab separated.
shr - nofile 65535
shr - nproc 127510
Start the installation using the following command:
$ sudo ./HP-SHR_10.00_setup.bin -i console
Continue with the installation steps. For the installation steps, see the Installation section in this guide.
Additional Information
After successful installation as a non-root user, following changes are seen:
PMDB_HOME/bin/setenv.sh
file, username
is the non-root user name. The username
for ulimit
is the non-root username instead of root user.PMDB_HOME
folder is owned by non-root user. PMDB_HOME
and /var/opt/OV
for other users is RX
. config.prp
file has additional entry nonrootuser=<nonrootuser name>
.The ulimit
value changes automatically for the non-root user in PMDB_HOME/bin/setenv.sh
file as shown in the following table. This value applies on next log on to the system.
Parameter | ulimit value | Recommended by |
---|---|---|
Number of file descriptors | 65535 | Vertica |
Number of user process | 127510 | SAP BusinessObjects |
Perform the following steps to remove HPE OBR:
To remove the entire HPE OBR application along with all the Content Packs, you can directly uninstall the application.
Start the HPE Software Installer:
Click Start > Apps > HP Software > Uninstall.
Select the language that you prefer, and click OK. The HPE Software Installer wizard gets initialized. The Application Maintenance page appears.
HPE Software Installer checks the system for any applications or services that might affect the uninstallation process such as anti-virus software. If HPE Software Installer detects a problem, a warning or error is generated, and an Application requirements check warnings window opens. Click Continue.
Under Maintenance Selection, select Uninstall and click Next. The Pre-Uninstall Summary page appears.
Note: HPE OBR does not support the Repair option displayed in the HPE Software Installer; it is disabled by default. You can use the Modify option in the Custom Installation scenario.
After uninstallation, some files may remain on the system. The residual files do not impact reinstallation of HPE OBR on the same system.
You can search for the directory on the system that contains the HPE OBR database files, and manually delete the directory. You can also delete the entire HPE OBR installation directory.
You must also remove SAP BusinessObjects and SQL Anywhere 12 Deployment manually. Follow these steps:
Click the following items (one at a time), and then click Uninstall to uninstall:
SQL Anywhere 12 Deployment
If your HPE Operations Bridge Reporter installation fails because of unexpected circumstances such as power outage or hardware failure, you can perform the following steps to manually clean up the existing HPE Operations Bridge Reporter installation before proceeding with a new installation:
Task 1: Stop all OBR services
services.msc
in the Open field, and then press ENTER. The Services window appears.Right-click the following services and select Stop to stop the service:
HPE_PMDB_Platform_Orchestration
Task 2: Remove SAP BusinessObjects and PostgreSQL
Click the following items (one at a time), and then click Uninstall to uninstall:
SQL Anywhere 12 Deployment
Task 3: Remove Windows Registry entries
Perform this task only if no other HPE products are installed on your system.
regedit
and press ENTER. The Registry Editor window opens.Press Ctrl + F and search for the following registries:
HPPmdb
HPSHR
Business Objects
Task 4: Remove the HPE OBR components
cmd
and press ENTER. The Command Prompt window appears.At the command prompt, type the following command to uninstall a component:
msiexec /x <product code value>
In this instance, <product code value>
is the value that is listed in the right pane of the Registry Editor window for a particular components.
For example, to uninstall the HPPmdbMsgBus component, type:
msiexec /x {F44672D8-C8A9-45F6-A215-C9CF138E6ED1}
Perform this step for all the components listed under BSM and HPE OpenView.
Task 5: Remove specific environment variables
Task 6: Remove the HPE Operations Bridge Reporter Folders
Once all the above tasks are performed, restart your system.
To uninstall HPE OBR from the command line console, perform the following steps:
At the new command prompt type the command
/opt/OV/Uninstall/HP-SHR/setup.bin -i console
A screen appears with pre-installation summary, press ENTER to continue.
Note: The installer automatically checks and uninstalls the application packages.
After uninstall, some files may remain on the system. The residual files do not impact reinstallation of HPE OBR on the same system.
You can search for the directory on the system that contains the HPE OBR database files, and then manually delete the directory.
Additionally, you can delete the following directories:
/opt/HP/BSM
You can also delete the /opt/OV
directory if no other HPE Software products are installed on the system.
If your HPE Operations Bridge Reporter installation fails because of unexpected circumstances such as power outage or hardware failure, you can perform the following steps to manually clean up the existing HPE Operations Bridge Reporter installation before proceeding with a new installation:
Task 1: Stop all HPE OBR services
Type the following commands at the command line console:
cd /etc/init.d
service HPE_PMDB_Platform_Orchestration stop
service HPE_PMDB_Platform_Administrator stop
service HPE_PMDB_Platform_Collection stop
service HPE_PMDB_Platform_DB_Logger stop
service HPE_PMDB_Platform_IM stop
service HPE_PMDB_Platform_IA stop
service HPE_PMDB_Platform_PostgreSQL stop
service HP_PMDB_Platform_NRT_ETL stop
service BobjEnterprise120stop
Go to the following directory:
/opt/HP/BSM/BO/bobje
Run the following command:
./sawstop.sh
When prompted for password, specify pmdb_admin
.
Task 2: Remove SAP BusinessObjects and PostgreSQL
To remove SAP BusinessObjects, in the command line console run the following commands:
ps -U SHRBOADMIN | awk '{print $1}' | xargs -i kill {}
rm -rf /opt/HP/BSM/BO
rm -f /etc/init.d/SAPBOBJEnterpriseXI40
find / -name "*SAPBOBJEnterprise*" -exec rm -f {} \;
rm -rf /tmp/.SQLAnywhere
rm -rf /root/.sqlanywhere12
#ps -ef | sed -n '/BO/{/grep/!p;}' | awk '{print$2}' | xargs -i kill {}
userdel -rf SHRBOADMIN
To remove PostgreSQL, in the command line console run the following commands:
service HP_PMDB_Platform_PostgreSQL restart
/opt/HP/BSM/Postgres/uninstall-postgresql --mode unattended
userdel postgres
chkconfig --del HP_PMDB_Platform_PostgreSQL
rm -f /etc/init.d/HP_PMDB_Platform_PostgreSQL
rm -rf /opt/HP/BSM/Postgres/
Task 3: Remove Vertica
To remove Vertica, in the command line console run the following commands:
rpm -e vertica-7.0.2-1.x86_64
rm -rf /opt/vertica/
If you have installed Vertica on a remote system, uninstall the Vertica Client from the OBR or SAP BusinessObjects server. Run the following command:
rpm -e vertica-client-7.0.2-1.x86_64
Task 4: Remove the HPE OBR components
To remove Red Hat Package Manager (RPM) packages, follow these steps:
shrPkgList
under the /tmp
directory.With a text editor, add the following lines to the shrPkgList
file:
Note: Do not change the sequence while adding these lines to the shrPkgList
file.
HPSHRNwPerf
HPSHRSmEtlVvmSiS
HPSHRNwENps92
HPSHRSmEtlVSolPa
HPSHRADApp
HPSHRCDE
HPPmdbVertica
HPSHRADCore
HPSHREtlvmSiSAPI
HPSHRSM
HPPmdbLicAP
HPSHRWBSApp
HPPmdbTomcat
HPPmdbAdmin
HPSHROMi10Etl
HPSHREumCore
HPSHROM
HPSHRNwCore
HPSHRSmEtlPa
HPSHROraDBETL
HPSHRExchEtl10
HPSHRSmVVm
HPPmdbABC
HPOvSecCS
HPSHRCoreWBS
HPSHRSmEtlVvmPa
HPPmdbCore
HPPmdbCollector
HPOvJPacc
HPSHRCoreAppS
HPSHRCoreSHlth
HPSHRCoreOMi
HPOvSecCC
HPSHREumBpm
HPSHREtlSHlth10
HPSHREumEtlBpm
HPSHRExchEtl07
HPSHRSmEtlVHyPa
HPOvJbbc
HPOvJsec
HPSHRExchApp
HPSHROmEtl
HPSHROraDBApp
HPPmdbPostgreSQL
HPSHRCPHelp
HPPmdbBORebrand
HPPmdbBOTomcat
HPPmdbCommon
HPOvPerlA
HPPmdbPerl
HPSHRMSSqlEtl
HPSHRSmCore
HPSHRCoreWLS
HPSHRWLSEtl
HPSHRSmEtlSisDB
HPSHRSmEtlVLprPa
HPSHROMiExt
HPSHRSmV
HPSHROMiExtEtl
HPSHRMSSqlCore
HPOvJxpl
HPSHRSmEtlVVmVc
HPSHRCoreCP
HPSHREumRum
HPSHREumEtlRum
HPSHRMSSqlApp
HPSHRWLSApp
HPSHRSmCoreVVM
HPSHROMiEtl
HPSHRMSAppCore
HPSHRSmCoreV
HPSHRExchCore
HPSHROraDBCore
HPSHRSHlthA
HPSHRSmEtlSis
HPSHRSmEtlSisAPI
HPSHRADEtl
HPOvConf
HPOvDepl
HPSHRNwENpsN92
HPOvCtrl
HPOvBbc
HPOvSecCo
HPOvXpl
HPSHREtlSHlthBSM
HPSHRWBSEtl
Run the following command:
for i in `cat /tmp/shrPkgList`; do echo Uninstalling: $i | tee -a /tmp/shrPkgRemove; rpm -e $i 2>&1 | tee -a /tmp/shrPkgRemove; done
Note: The command output shows the following error message in the command line console:
basename: invalid option -- 'e'
Try `basename --help' for more information.
Ignore the error.
Task 5: Remove specific environment variables
To remove specific environment variables, run the command:
service HP_PMDB_Platform_PostgreSQL restart
rm -f /etc/profile.d/setenv.sh
Task 6: Remove the HPE Operations Bridge Reporter Folders
To remove the HPE OBR folders, run the command:
rm -rf /opt/HP/BSM
If no other HPE Software products are installed on the system, delete the /opt/OV
directory by running the following command:
rm -rf /opt/OV
Task 5: Restart the System
Restart the system to free up the ports that were used by HPE Operations Bridge Reporter.
You can uninstall Vertica manually or from the installer. Perform the following steps for Vertica on a remote Linux operating system:
Caution: Before performing the remote Vertica uninstallation steps, you must first remove HPE Operations Bridge Reporter from the host system. This ensures that the remote database schema is removed after the Vertica uninstallation.
Uninstall from the Installer:
Start the HPE Software Installer.
At the new command prompt type the command
/opt/OV/Uninstall/HP-SHR/setup.bin -i console
A screen appears with pre-installation summary, press ENTER to continue.
Note: The installer automatically checks and uninstalls the application packages.
After uninstall, some files may remain on the system. The residual files do not impact reinstallation of HPE OBR on the same system.
You can search for the directory on the system that contains the HPE OBR database files, and then manually delete the directory.
Uninstall manually:
Run the following commands:
su <VerticaDBUsername> -c "/opt/vertica/bin/adminTools -t stop_db -d <VerticaDatabase Name> -p <VerticaDBPassword> -F"
where, <VerticaDBUsername>
is the Vertica database user name.
<VerticaDatabase Name>
is the name of the Vertica database.
<VerticaDBPassword>
is the password for the Vertica database.
su <VerticaDBUsername> -c "/opt/vertica/bin/adminTools -t drop_db -d <VerticaDatabase Name>"
rpm -e vertica-7.1.2-0.x86_64
rm -rf /opt/vertica
rm –f /tmp/4803
After uninstallation, some files may remain on the system. The Rollback utility present within the installer tar files is used to remove such files.
Perform the following steps after uninstall to remove the remaining files:
In the command line console, type the path of Rollback utility location.
You will find the Rollback utility file in the location from where the installation setup files were extracted for installation.
Run the following command:
rollback-utility.bat <HPE OBR INSTALL PATH>
For Example: rollback-utility.bat C:\HPE-OBR
Ensure that you do not include \
after C:\HPE-OBR
.
After uninstallation, some files may remain on the system. The Rollback utility present within the tar files is used to remove such files.
Perform the following steps after uninstall to remove the remaining files:
In the command line console, type the path of Rollback utility location.
You will find the Rollback utility file in the location from where the installation setup files were extracted for installation.
Run the following command:
sh rollback-utility.sh
To remove the Remote Collector application, follow these steps:
Start the HPE Software Installer.
Go to %ovinstalldir%\Uninstall\HP-SHR-RemotePoller
and run the setup.exe
file.
Select the language that you prefer, and click OK.
The HPE Software Installer appears.
On the HPE Software Installer language selection page, select the required language and then click OK.
HPE Software Installer checks the system for any applications or services that might hinder the uninstallation process such as anti-virus software. If HPE Software Installer detects a hindrance, a warning or error is generated, and an Application requirements check warnings window opens.
Under Maintenance Selection, make sure that Uninstall is selected, and then click Next. The Pre-Uninstall Summary page appears.
Note: OBR does not support the Repair option displayed in the HPE Software Installer; it is disabled by default. You can use the Modify option in the Custom Installation scenario.
After uninstallation, some files may remain on the system. The residual files do not impact reinstallation of the Remote Collector on the same system.
The sub-folders located at <install dir> \HP BTO Software\ <sub-folders>
and VC Redistributable must not be deleted as they may be used by other applications.
You can delete the following directories after uninstallation:
The complete collector installation directory if no other HPE Software products are installed on the system.
You can also delete the /opt/OV
directory if no other HPE Software products are installed on the system.
After uninstalling the Remote Collector, you must clean up the HPE OBR system to remove the traces of collection configuration data. To clean up the HPE OBR system, follow these steps:
For each definition that is set up with the Remote Collector that you uninstalled, follow these steps:
To remove the Remote Collector application, follow these steps:
Start the HPE Software Installer.
Go to the following location and run the file:
/opt/OV/Uninstall/HP-SHR-RemotePoller/setup.bin -i console
Note: OBR does not support the Repair option displayed in the HPE Software Installer; it is disabled by default. You can use the Modify option in the Custom Installation scenario.
After uninstallation, some files may remain on the system. The residual files do not impact reinstallation of the Remote Collector on the same system.
The sub-folders located at <install dir> \HP BTO Software\ <sub-folders>
must not be deleted as they may be used by other applications.
You can delete the following directories after uninstallation:
/opt/HP/BSM
You can also delete the /opt/OV
directory if no other HPE Software products are installed on the system.
After uninstalling the Remote Collector, you must clean up the HPE OBR system to remove the traces of collection configuration data. To clean up the HPE OBR system, follow these steps:
For each definition that is set up with the Remote Collector that you uninstalled, follow these steps:
© Copyright 2015 - 2016 Hewlett Packard Enterprise Development LP