Customized output from:
Document Release Date: July 2016 Software Release Date: January 2015 |
|
The only warranties for HP 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. HP 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 HP 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 Development Company, L.P.
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.
Version: 9.40
Document Release Date: July 2016
HP Service Health Reporter (SHR) collects data from cross domain data sources, processes it, and generates reports. It uses components like the SAP Sybase IQ database for storing performance data, SAP BusinessObjects for generating reports, and PostgreSQL database for storing management data.
You can install all SHR components on a single system (typical installation). When reporting on a large number of nodes, to improve performance, you can distribute the different components (SHR server, SHR Data Collector, Sybase IQ, and SAP BusinessObjects) over different systems (custom installation).
You can perform install, uninstall and upgrade tasks using this guide. After installing the SHR bits, to configure the setup, see the HP Service Health Reporter Configuration Guide.
Select the task you want to perform with HP Service Health Reporter.
Select the operating system for HP Service Health Reporter.
Select "Custom" to distribute the installation of the server components over different systems.
Select "Typical" to install all the server components on the same system.
For Windows 2012 operating system the Sybase IQ must be installed on Linux. Windows 2012 does not support Sybase IQ which comes bundled with the SHR media.
All SHR components must be installed in the same operating system environment for Windows 2008 and Linux.
The SHR data collector is installed on the same system where SHR is installed. However, SHR also provides you option to install the collector on a separate server. You can have collectors installed on multiple systems depending on your need. You can install a collector on a remote system that runs on any of the operating systems supported by SHR.
You can view your customized document on the screen, or print it.
If you have a PDF print driver installed on your computer, click Print to create PDF documents that are customized according to your selections. PDF print drivers are available from several open source and third-party providers.
The following steps are customized according to your selections.
If any selections are not correct, click Change.
This content is valid for Linux.
This content is valid for Linux.
This content is valid for Windows.
This content is valid for UNIX.
This content is valid for Linux.
These prerequisites apply to the system where you want to install HP Service Health Reporter and also the remote systems where you want to install the SHR data collector.
Hardware Requirements
For a list of hardware requirements, see the HP Service Health Reporter Performance, Sizing, and Tuning Guide..
To install SHR, ensure that you have a free space of 20 GB in the installation directory.
Software Requirements
For the complete list of software requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Operating System Requirements
For the complete list of operating system requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Before you install SHR, you must update your operating system, apply all patches, establish network connectivity, and the anti-virus software.
Ensure that the virtual memory is twice the size of the RAM. For the steps to increase the virtual memory space, refer to the Windows operating system documentation.
Port Availability
SHR uses a number of default ports for different services. Ensure that the following ports are free before installing SHR components.
Service |
Port Number |
Protocol |
Inbound |
Outbound |
Description |
---|---|---|---|---|---|
HP PMDB Platform DB Logger |
21408 |
TCP |
Yes |
Yes |
The HP PMDB Platform DB Logger service persists logs in the database through this port. |
HP PMDB Platform Collection |
21409 |
TCP |
Yes |
Yes |
The JMX management port for the Collection service. The IM service monitors collection using this interface. |
HP PMDB Platform IM |
21410 |
TCP |
Yes |
No |
The JMX management port for the IM service. |
HP PMDB Platform Timer |
No port |
NA |
NA |
NA |
The Timer service for SHR. |
HP PMDB Platform Administrator |
21411 |
TCP |
Yes |
No |
The SHR web application server port, which hosts the Administration web application. The Report cross-launch functionality depends on this service. |
HP Software Communication Broker |
383 |
TCP |
Yes |
Yes |
SHR 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 SHR administration web server. |
HP PMDB Platform Collection | 21418 | HTTP | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 21419 | HTTPS | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 8080 | HTTP | No | Yes | The connection port to collect data from the SiteScope Data Acquisition API. |
HP PMDB Platform Sybase Service |
21424 |
TCP |
Yes |
Yes |
Port for the Sybase IQ server. |
Sybase IQ Agent 15.4 |
21423 |
TCP |
Yes |
No |
Port for the Sybase IQ Agent. |
HP-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 InfoView 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 (HOML01GEATON) |
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, SHR connects to RTSM. |
HPOM |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the HPOM database. SHR uses this port to connect to the HPOM database. |
HP Operations Agent |
383 |
TCP |
No |
Yes |
SHR 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. SHR uses this port to connect to the Profile database and the OMi database. |
Web Browser Requirements
To view the SHR Administration Console in Internet Explorer or Mozilla Firefox, you must enable the ActiveX and the JavaScript controls. Follow the Help menu of the web browser for assistance with enabling them.
For a list of supported Web Browsers, see "Web Browsers and Plug-ins" in the HP Service Health Reporter Support Matrix.
Installation User Account
After ensuring that the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for the SHR installation.
Task 1: Disable Anti-Virus
Anti-virus applications can hinder the installation of SHR. Temporarily disable any anti-virus software that might be running.
Re-enable the anti-virus software after the installation is complete.
Task 2: Configure Firewall
If you use firewall software, ensure that the firewall allows traffic through the required ports (see Installation Prerequisites > Port Availability ) on the SHR system.
Task 3: Verify the Fully Qualified Domain Name (FQDN) of the System
Before performing the SHR installation, you must verify that DNS lookup returns the accurate FQDN of the system. If the entry for the DNS lookup is different from the hostname of the system, you may experience difficulties in logging on to the SHR Administration Console. This can occur 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 hostname of the system:
hostname
Note down the hostname 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 system.
Ensure that the name displayed after running the nslookup
command matches the name displayed after running the HOSTNAME command. If the names do not match, you must change the hostname of the system.
Task 4: Disable User Account Control (UAC)
Perform this task only if the host system runs on the following operating systems:
Windows Server 2008 with Service Pack 2
Windows Server 2008 R2 with Service Pack 1
Task 5: Set a Static IPv6 Address on Windows Server 2008
When installing SHR on a Windows Server 2008 server where the communication protocol is IPv6, you must assign a static IPV6 address.
By default, the interface ID is randomly derived in Windows Server 2008, rather than being based on the Extended Unique Identifier (EUI)-64 address. You must disable the random interface IDs. For more information, see documentation of Microsoft available at http://www.microsoft.com
Task 6: 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.
When installing SHR on a Windows server, perform the following steps to increase the non-interactive desktop heap.
regedit
. The Registry Editor window appears.Task 7: Assemble the media
On the HP software download web site, the SHR installation media for Windows is distributed as a collection of the following three files:
HPSHR_940_Win64.part1
HPSHR_940_Win64.part2
HPSHR_940_Win64.part3
Before you start installing SHR, you must download all three files, and then combine them into a single .tar
file.
To create the SHR installation media, follow these steps:
Click Start > Run to open the Run prompt.
Type CMD
and press Enter. The command prompt window appears.
To create a new directory to install SHR, run the following command:
mkdir
drive:\directory name
For example: mkdir
C:\temp\HPSHR_9.4-parts
Download the .tar
file parts into the temporary folder that you created in the previous step.
For example: C:\temp\HPSHR_9.4-parts
.
To go to the location where you have copied the .tar
file parts, run the following command:
cd
<temp location>
For example: cd
C:\temp\HPSHR_9.4-parts
To merge the contents into a single .tar
file, run one of the following commands:
copy /b HPSHR_940_Win64.part? C:\temp\HPSHR_9.4-parts\HPSHR940.tar
or
type HPSHR_940_Win64.part? > C:\temp\HPSHR_9.4-parts\HPSHR940.tar
Note: You must type the command in a single line.
The SHR 9.40 media is now available as a single .tar
file in the following location:
C:\temp\HPSHR_9.4-parts\HPSHR940.tar
Unzip the .tar
file, you will find the HP-SHR_9.40_setup.exe
to move ahead with the installation.
Additional Considerations
Note: The SHR installer does not support forced reinstallation. In the event of a unsuccessful installation, you must manually remove all the files that were placed by the installer and start the installation process again.
Install HP Service Health Reporter Server, Sybase IQ Server, and SAP BusinessObjects Server on a single system.
Run the following file:
HP-SHR_9.40_setup.exe
The setup files are extracted.
Select the language in which you want to install SHR, and click OK.
The HP Service Health Reporter 9.40 Software Installer wizard appears.
Review the folders in which SHR would install. To change the installation folders, use the adjoining Browse buttons. Click Next.
Note: Do not enter spaces or special characters other than the - (hyphen) in the non-default folder name. The installation path must be less than 20 characters.
The installer performs checks for installation prerequisites and shows the result of the check on the Install Check page.
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.
After the installation is complete, click Done.
If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:
In the command line console, go to the rollback utility path.
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
<SHR INSTALL PATH>
For Example: rollback-utility.bat
C:\HP-SHR
To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
For SHR on a system with the Simplified Chinese or Japanese locale, follow these steps:
Run the following command to stop the Sybase IQ service:
dbstop -y -c uid=dba;pwd=sql;eng=<server engine name>;dbn=utility_db;links=tcpip{host=<host name>.<domain name>;port=21424}
In this instance, <server engine name>
refers to the name of the Sybase server engine, <host name>
refers to the name of the system hosting the SHR database and <domain name>
is the name of your domain according to your network configuration.
This command must be typed as a single line.
Manually delete the following files after installation:
%PMDB_HOME%\Sybase\IQ-15_4\Bin64\dblgzh_iq12.dll
%PMDB_HOME%\Sybase\IQ-15_4\Bin64\dblgja_iq12.dll
The custom installation of SHR enables you to install different components of SHR on different systems. SHR comprises of the following fundamental components:
You can choose to install each of these components on a separate, dedicated server, or you can install any one component on a dedicated server while the rest reside together on another server.
The following table illustrates different types of environments that you can create with the custom installation options.
Environment 1 | Environment 2 | Environment 3 |
---|---|---|
System1: SHR server System2: Sybase IQ server System3: SAP BusinessObjects server |
System1: SHR server System2: Sybase IQ server + SAP BusinessObjects server (not supported in Windows 2012)
|
System1: SHR server + SAP BusinessObjects server System2: Sybase IQ server |
If you have high performance load on a server, HP recommends that you install it on a separate system. For more information on performance considerations, see HP SHR Performance, Sizing, and Tuning Guide.
Make sure that all the prerequisites that are listed in this section are met on each system.
Hardware Requirements
For a list of hardware requirements, see the HP Service Health Reporter Performance, Sizing, and Tuning Guide..
To install SHR, ensure that you have a free space of 20 GB in the installation directory.
Software Requirements
For the complete list of software requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Operating System Requirements
For the complete list of operating system requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Before you install SHR, you must update your operating system, apply all patches, establish network connectivity, and disable the anti-virus software.
Ensure that the virtual memory is twice the size of the RAM. For the steps to increase the virtual memory space, refer to the Windows operating system documentation.
Port Availability
SHR uses a number of default ports for different services. Ensure that the following ports are free before installing SHR components.
Service |
Port Number |
Protocol |
Inbound |
Outbound |
Description |
---|---|---|---|---|---|
HP PMDB Platform DB Logger |
21408 |
TCP |
Yes |
Yes |
The HP PMDB Platform DB Logger service persists logs in the database through this port. |
HP PMDB Platform Collection |
21409 |
TCP |
Yes |
Yes |
The JMX management port for the Collection service. The IM service monitors collection using this interface. |
HP PMDB Platform IM |
21410 |
TCP |
Yes |
No |
The JMX management port for the IM service. |
HP PMDB Platform Timer |
No port |
NA |
NA |
NA |
The Timer service for SHR. |
HP PMDB Platform Administrator |
21411 |
TCP |
Yes |
No |
The SHR web application server port, which hosts the Administration web application. The Report cross-launch functionality depends on this service. |
HP Software Communication Broker |
383 |
TCP |
Yes |
Yes |
SHR 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 SHR administration web server. |
HP PMDB Platform Collection | 21418 | HTTP | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 21419 | HTTPS | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 8080 | HTTP | No | Yes | The connection port to collect data from the SiteScope Data Acquisition API. |
HP PMDB Platform Sybase Service |
21424 |
TCP |
Yes |
Yes |
Port for the Sybase IQ server. |
Sybase IQ Agent 15.4 |
21423 |
TCP |
Yes |
No |
Port for the Sybase IQ Agent. |
HP-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 InfoView 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 (HOML01GEATON) |
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, SHR connects to RTSM. |
HPOM |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the HPOM database. SHR uses this port to connect to the HPOM database. |
HP Operations Agent |
383 |
TCP |
No |
Yes |
SHR 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. SHR uses this port to connect to the Profile database and the OMi database. |
Web Browser Requirements
To view the SHR Administration Console in Internet Explorer or Mozilla Firefox, you must enable the ActiveX and the JavaScript controls. Follow the Help menu of the web browser for assistance with enabling them.
For a list of supported Web Browsers, see "Web Browsers and Plug-ins" in the HP Service Health Reporter Support Matrix.
Installation User Account
After ensuring that the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for the SHR installation.
Task 1: Disable Anti-Virus
Anti-virus applications can hinder the installation of SHR. Temporarily disable any anti-virus software that might be running.
Re-enable the anti-virus software after the installation is complete.
Task 2: Configure Firewall
If you use firewall software, ensure that the firewall allows traffic through the required ports (see Installation Prerequisites > Port Availability ) on the SHR system.
Task 3: Verify the Fully Qualified Domain Name (FQDN) of the System
Before performing the SHR installation, you must verify that DNS lookup returns the accurate FQDN of the system. If the entry for the DNS lookup is different from the hostname of the system, you may experience difficulties in logging on to the SHR Administration Console. This can occur 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 hostname of the system:
hostname
Note down the hostname 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 system.
Ensure that the name displayed after running the nslookup
command matches the name displayed after running the HOSTNAME command. If the names do not match, you must change the hostname of the system.
Task 4: Disable User Account Control (UAC)
Perform this task only if the host system runs on the following operating systems:
Windows Server 2008 with Service Pack 2
Windows Server 2008 R2 with Service Pack 1
Task 5: Set a Static IPv6 Address on Windows Server 2008
When installing SHR on a Windows Server 2008 server where the communication protocol is IPv6, you must assign a static IPV6 address.
By default, the interface ID is randomly derived in Windows Server 2008, rather than being based on the Extended Unique Identifier (EUI)-64 address. You must disable the random interface IDs. For more information, see documentation of Microsoft available at http://www.microsoft.com
Task 6: 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.
When installing SHR on a Windows server, perform the following steps to increase the non-interactive desktop heap.
regedit
. The Registry Editor window appears.Task 7: Assemble the media
On the HP software download web site, the SHR installation media for Windows is distributed as a collection of the following three files:
HPSHR_940_Win64.part1
HPSHR_940_Win64.part2
HPSHR_940_Win64.part3
Before you start installing SHR, you must download all three files, and then combine them into a single .tar
file.
To create the SHR installation media, follow these steps:
Click Start > Run to open the Run prompt.
Type CMD
and press Enter. The command prompt window appears.
To create a new directory to install SHR, run the following command:
mkdir
drive:\directory name
For example: mkdir
C:\temp\HPSHR_9.4-parts
Download the .tar
file parts into the temporary folder that you created in the previous step.
For example: C:\temp\HPSHR_9.4-parts
.
To go to the location where you have copied the .tar
file parts, run the following command:
cd
<temp location>
For example: cd
C:\temp\HPSHR_9.4-parts
To merge the contents into a single .tar
file, run one of the following commands:
copy /b HPSHR_940_Win64.part? C:\temp\HPSHR_9.4-parts\HPSHR940.tar
or
type HPSHR_940_Win64.part? > C:\temp\HPSHR_9.4-parts\HPSHR940.tar
Note: You must type the command in a single line.
The SHR 9.40 media is now available as a single .tar
file in the following location:
C:\temp\HPSHR_9.4-parts\HPSHR940.tar
Unzip the .tar
file, you will find the HP-SHR_9.40_setup.exe
to move ahead with the installation.
Additional Considerations
Note: The SHR installer does not support forced reinstallation. In the event of a unsuccessful installation, you must manually remove all the files that were placed by the installer and start the installation process again.
Run the following file:
HP-SHR_9.40_setup.exe
The setup files are extracted.
Select the language in which you want to install SHR, and click OK.
The HP Service Health Reporter 9.40 Software Installer wizard appears.
Review the folders in which SHR would install. To change the installation folders, use the adjoining Browse buttons. Click Next.
Note: Do not enter spaces or special characters other than the - (hyphen) in the non-default folder name. The installation path must be less than 20 characters.
The installer performs checks for installation prerequisites and shows the result of the check on the Install Check page.
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.
Optionally, if you plan to install another server (Sybase IQ Server or SAP BusinessObjects Server) on the same system later, restart it.
The installer wizard appears with Modify, Repair and Uninstall options. Select Modify option to install another component to the same system.
Caution: If you 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:
In the command line console, go to the rollback utility path.
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
<SHR INSTALL PATH>
For Example: rollback-utility.bat
C:\HP-SHR
To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
To install with the help of the installation wizard, follow these steps:
Run the following file:
HP-SHR_9.40_setup.exe
The setup files are extracted.
Select the language in which you want to install SHR, and click OK.
The HP Service Health Reporter 9.40 Software Installer wizard appears.
Review the folders in which SHR would install. To change the installation folders, use the adjoining Browse buttons. Click Next.
Note: Do not enter spaces or special characters other than the - (hyphen) in the non-default folder name. The installation path must be less than 20 characters.
The installer performs checks for installation prerequisites and shows the result of the check on the Install Check page.
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.
Optionally, if you plan to install another server (SHR Server or SAP BusinessObjects Server) on the same system later, restart it.
The installer wizard appears with Modify, Repair and Uninstall options. Select Modify option to install another component to the same system.
Caution: If you 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.
See Database Backup and Recovery chapter in the HP Service Health Reporter Configuration Guide if you want to move Sybase IQ to the server where SHR and SAP BusinessObjects is installed.
If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:
In the command line console, go to the rollback utility path.
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
<SHR INSTALL PATH>
For Example: rollback-utility.bat
C:\HP-SHR
To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
On a system with the Simplified Chinese or Japanese locale, manually delete the following files from the system where you installed Sybase IQ:
%PMDB_HOME%\Sybase\IQ-15_4\Bin64\dblgzh_iq12.dll
%PMDB_HOME%\Sybase\IQ-15_4\Bin64\dblgja_iq12.dll
To install with the help of the installation wizard, follow these steps:
Run the following file:
HP-SHR_9.40_setup.exe
The setup files are extracted.
Select the language in which you want to install SHR, and click OK.
The HP Service Health Reporter 9.40 Software Installer wizard appears.
C
.
Note: Enter only the alphabet that denotes the drive. For example, enter C and not C:\ or C:.
Review the folders in which SHR would install. To change the installation folders, use the adjoining Browse buttons. Click Next.
Note: Do not enter spaces or special characters other than the - (hyphen) in the non-default folder name. The installation path must be less than 20 characters.
The installer performs checks for installation prerequisites and shows the result of the check on the Install Check page.
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.
Optionally, if you plan to install another server (SHR Server or Sybase IQ Server) on the same system later, restart it.
The installer wizard appears with Modify, Repair and Uninstall options. Select Modify option to install another component to the same system.
Caution: If you 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.
See Database Backup and Recovery chapter in the HP Service Health Reporter Configuration Guide if you want to move SAP BusinessObjects to the server where SHR and Sybase IQ is installed.
If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:
In the command line console, go to the rollback utility path.
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
<SHR INSTALL PATH>
For Example: rollback-utility.bat
C:\HP-SHR
To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
SHR 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 SHR 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 SHR is successfully installed with the default language pack.
To check that the default language pack is installed successfully, launch the SAP BusinessObjects InfoView portal (http://<SHR_HostName>:8080/InfoViewApp), and then go to InfoView Page > Preferences > General > Product Locale. The Product Locale box lists the installed language packs.
In this instance, <SHR_HostName> is the fully qualified domain name of the SHR system.
Go to the following directory:
%PMDB_HOME%\temp\BO_Updates
For all the languages edit the .ini
files with the BO drive that you have entered during SHR installation.
Example: INSTALLDIR="C:\Program Files (x86)\Business Objects\
"
IF the BO drive is changed to E
drive from the default C
drive then edit as follows in all of the .ini
language files:
INSTALLDIR="E:\Program Files (x86)\Business Objects\
"
If you have created a CMS password, include the password in all of the language .ini
files.
For Example: CMSPASSWORD=""
By default the .ini
files will not have any password. You have to include the CMC password into the .ini
files if you have created.
CMSPASSWORD="abc123"
Note: After completing the installation of SAP BusinessObjects, you must remove the password that you have typed for CMSPASSWORD in the .ini
files.
Run the following command:
BO_LanguagepackInstall.bat<SHR_media_root><lang_pack_name>
In this instance:
<SHR_media_root> is the path to the root of the SHR media (that is, the directory where the SHR installer is available). Do not type the name of the installer and do not use a trailing \
character.
For example, if the SHR media is extracted into the E:\Installer directory, which means the SHR installer (HP-SHR_9.40_setup.exe
) exists in the E:\Installer directory, you must run the following command:
BO_LanguagepackInstall.bat E:\Installer<lang_pack_name>
<lang_pack_name> is the name of the SAP BusinessObjects language pack. The following table provides names of language packs for all supported locales:
Language |
Language Pack Name |
---|---|
German |
de |
English |
en |
Spanish |
es |
French |
fr |
Italian |
it |
Korean |
ko |
Dutch |
nl |
Portuguese |
pt |
Russian |
ru |
Chinese |
zh_CN |
Note: Since the language pack installation requires a significant amount of time, you must correctly choose the language pack of your interest while running the command.
You can install multiple language packs by providing multiple language pack names in the command (separated by spaces). Separate two language pack names only by a single space character. For example, to install both Spanish and Korean language packs, run the following command:
BO_LanguagepackInstall.bat<SHR_media_root> es ko
The custom installation of SHR on Windows 2012 operating system enables you to install different components of SHR on different systems. SHR comprises of the following fundamental components:
Windows 2012 does not support Sybase IQ that is bundled with the SHR media. Therefore, it is recommended that you install Sybase IQ on Linux operating system and other SHR components on Windows 2012.
You can choose to install each of these components on a separate, dedicated server, or you can install any one component on a dedicated server while the rest reside together on another server.
The following table illustrates different types of environments that you can create with the custom installation options.
Environment 1 | Environment 2 |
---|---|
System1: SHR server System2: Sybase IQ server System3: SAP BusinessObjects server |
System1: SHR server + SAP BusinessObjects server System2: Sybase IQ server |
If you have high performance load on a server, HP recommends that you install it on a separate system. For more information on performance considerations, see HP SHR Performance, Sizing, and Tuning Guide.
Make sure that all the prerequisites that are listed in this section are met on each system.
Hardware Requirements
For a list of hardware requirements, see the HP Service Health Reporter Performance, Sizing, and Tuning Guide..
To install SHR, ensure that you have a free space of 20 GB in the installation directory.
Software Requirements
For the complete list of software requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Operating System Requirements
For the complete list of operating system requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Before you install SHR, you must update your operating system, apply all patches, establish network connectivity, and disable the anti-virus software.
Ensure that the virtual memory is twice the size of the RAM. For the steps to increase the virtual memory space, refer to the Windows operating system documentation.
Port Availability
SHR uses a number of default ports for different services. Ensure that the following ports are free before installing SHR components.
Service |
Port Number |
Protocol |
Inbound |
Outbound |
Description |
---|---|---|---|---|---|
HP PMDB Platform DB Logger |
21408 |
TCP |
Yes |
Yes |
The HP PMDB Platform DB Logger service persists logs in the database through this port. |
HP PMDB Platform Collection |
21409 |
TCP |
Yes |
Yes |
The JMX management port for the Collection service. The IM service monitors collection using this interface. |
HP PMDB Platform IM |
21410 |
TCP |
Yes |
No |
The JMX management port for the IM service. |
HP PMDB Platform Timer |
No port |
NA |
NA |
NA |
The Timer service for SHR. |
HP PMDB Platform Administrator |
21411 |
TCP |
Yes |
No |
The SHR web application server port, which hosts the Administration web application. The Report cross-launch functionality depends on this service. |
HP Software Communication Broker |
383 |
TCP |
Yes |
Yes |
SHR 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 SHR administration web server. |
HP PMDB Platform Collection | 21418 | HTTP | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 21419 | HTTPS | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 8080 | HTTP | No | Yes | The connection port to collect data from the SiteScope Data Acquisition API. |
HP PMDB Platform Sybase Service |
21424 |
TCP |
Yes |
Yes |
Port for the Sybase IQ server. |
Sybase IQ Agent 15.4 |
21423 |
TCP |
Yes |
No |
Port for the Sybase IQ Agent. |
HP-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 InfoView 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 (HOML01GEATON) |
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, SHR connects to RTSM. |
HPOM |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the HPOM database. SHR uses this port to connect to the HPOM database. |
HP Operations Agent |
383 |
TCP |
No |
Yes |
SHR 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. SHR uses this port to connect to the Profile database and the OMi database. |
Installation User Account
Web Browser Requirements
To view the SHR Administration Console in Internet Explorer or Mozilla Firefox, you must enable the ActiveX and the JavaScript controls. Follow the Help menu of the web browser for assistance with enabling them.
For a list of supported Web Browsers, see "Web Browsers and Plug-ins" in the HP Service Health Reporter Support Matrix.
After ensuring that the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for the SHR installation.
Task 1: Disable Anti-Virus
Anti-virus applications can hinder the installation of SHR. Temporarily disable any anti-virus software that might be running.
Re-enable the anti-virus software after the installation is complete.
Task 2: Verify the Fully Qualified Domain Name (FQDN) of the System
Before performing the SHR installation, you must verify that DNS lookup returns the accurate FQDN of the system. If the entry for the DNS lookup is different from the host name of the system, you may experience difficulties in logging on to the SHR Administration Console. This can occur 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 hostname of the system:
hostname
Note down the hostname of the system.
For the remote Sybase IQ system on Linux type the following command to check the hostname of the system:
hostname -f
Note down the hostname 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 system.
Ensure that the name displayed after running the nslookup
command matches the name displayed after running the HOSTNAME command. If the names do not match, you must change the hostname of the system.
Task 3: Disable User Account Control (UAC)
Perform this task only if the host system runs on the following operating systems:
Windows Server 2012
In the User Accounts Control Settings window, move the slider to the bottom to select the Never notify option, and then click OK.
Click Restart Now to apply the change.
Perform the following additional steps to disable it UAC via registry:
Click Start > Run. The Run dialog box appears.
regedit
. The Registry Editor window appears.In the registry go to the following path:
HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > policies > system
0
.Task 5: Install Microsoft .NET Framework 3.5
The Management database component of SHR 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 6: Set a Static IPv6 Address on Windows Server 2012
When installing SHR on a Windows Server 2012 server where the communication protocol is IPv6, you must assign a static IPV6 address.
By default, the interface ID is randomly derived in Windows Server 2012, rather than being based on the Extended Unique Identifier (EUI)-64 address. You must disable the random interface IDs. For more information, see documentation of Microsoft available at http://www.microsoft.com
Task 7: 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.
When installing SHR on a Windows server, perform the following steps to increase the non-interactive desktop heap.
regedit
. The Registry Editor window appears.Task 8: Assemble the media
On the HP software download web site, the SHR installation media for Windows is distributed as a collection of the following three files:
HPSHR_940_Win64.part1
HPSHR_940_Win64.part2
HPSHR_940_Win64.part3
Before you start installing SHR, you must download all three files, and then combine them into a single .tar
file.
To create the SHR installation media, follow these steps:
Click Start > Run to open the Run prompt.
Type CMD
and press Enter. The command prompt window appears.
To create a new directory to install SHR, run the following command:
mkdir
drive:\directory name
For example: mkdir
C:\temp\HPSHR_9.4-parts
Download the .tar
file parts into the temporary folder that you created in the previous step.
For example: C:\temp\HPSHR_9.4-parts
.
To go to the location where you have copied the .tar
file parts, run the following command:
cd
<temp location>
For example: cd
C:\temp\HPSHR_9.4-parts
To merge the contents into a single .tar
file, run one of the following commands:
copy /b HPSHR_940_Win64.part? C:\temp\HPSHR_9.4-parts\HPSHR940.tar
or
type HPSHR_940_Win64.part? > C:\temp\HPSHR_9.4-parts\HPSHR940.tar
Note: You must type the command in a single line.
The SHR 9.40 media is now available as a single .tar
file in the following location:
C:\temp\HPSHR_9.4-parts\HPSHR940.tar
Unzip the .tar
file, you will find the HP-SHR_9.40_setup.exe
to move ahead with the installation.
Additional Considerations
For remote Sybase IQ system on Linux operating system:
Always install SHR as root.
Note: The root user must be the owner of the /opt
and /var
directories.
Note: The SHR installer does not support forced reinstallation. In the event of a unsuccessful installation, you must manually remove all the files that were placed by the installer and start the installation process again.
Run the following file:
HP-SHR_9.40_setup.exe
The setup files are extracted.
Select the language in which you want to install SHR, and click OK.
The HP Service Health Reporter 9.40 Software Installer wizard appears.
Review the folders in which SHR would install. To change the installation folders, use the adjoining Browse buttons. Click Next.
Note: Do not enter spaces or special characters other than the - (hyphen) in the non-default folder name. The installation path must be less than 20 characters.
The installer performs checks for installation prerequisites and shows the result of the check on the Install Check page.
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.
Optionally, if you plan to install another server (Sybase IQ server or SAP BusinessObjects server) on the same system later, restart it.
The installer wizard appears with Modify, Repair and Uninstall options. Select Modify option to install another component to the same system.
Caution: If you 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:
In the command line console, go to the rollback utility path.
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
<SHR INSTALL PATH>
For Example: rollback-utility.bat
C:\HP-SHR
To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
Prerequisites for remote Sybase IQ on Linux operating system
It is recommended that you install Sybase IQ on Linux operating system. Windows 2012 does not support Sybase IQ.
Disk Space Requirements
Ensure that you have required space as follows in /opt
and /tmp
directories:
To download and merge the SHR media files, allocate at least 30 GB in the /tmp
directory on each system.
To install SHR components, allocate at least 20 GB in the /opt
directory on each system.
/tmp
directory on each system./opt
directory on each system./opt
directory. Ensure that the following libraries are available on the SHR system and the SHR Remote Data Collector System.
Red Hat Enterprise Linux 6.x | Red Hat Enterprise Linux 5.5 | ||
---|---|---|---|
The list indicates the minimum required versions of required libraries. You can install a higher version of each library, if available. | |||
|
|
Note: Ensure that you have installed the tcsh-6.17-8.el6.x86_64
library.
Ensure that the swap space is twice the size of the RAM. To allocate sufficient swap space, perform the following steps:
Log on to the system as root.
/opt
and /var
directories.To set up the swap space by creating a new swap file, run the following commands :
dd if=/dev/zero of=
<swapfile_full_path>
bs=1M count=
<swap_size_in_MB>
mkswap <swapfile_full_path>
swapon <swapfile_full_path>
In this instance, <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 the previous step.
For example:
/extraswap swap swap defaults 0 0
Port Availability for Linux
SHR uses a number of default ports for its different services. Refer the "Port Availability" table earlier in this section for the list of default ports.
Preinstallation tasks:
Task 1: Configure Firewall
If you use firewall software, ensure that the firewall allows traffic through the required ports (see Installation Prerequisites > Port Availability ) on the SHR system.
For remote Sybase IQ on Linux operating system perform the following steps:
To disable the firewall, perform the following steps:
Task a: Configure Firewall
Log on as root and run the following commands:
/opt
and /var
directories.chkconfig iptables off
chkconfig ip6tables off
/etc/init.d/iptables stop
/etc/init.d/ip6tables stop
Task b: Prepare the Linux System
Task b.1: Disable SELinux
To disable SELinux, in the /etc/sysconfig/selinux
file, set the parameter SELINUX = disabled
.
Task b.2: Configure the Kernel Parameters (only if you use Red Hat Enterprise Linux 6.x)
To configure the Kernel parameters, follow these steps
/etc/sysctl.conf
file.Note: If higher values are specified for these parameters already, do not make any modifications.
Task b.3: Configure the Hostname
Log on to the SHR system, and configure the hostname in the /etc/hosts
file.
If you configure a hostname, it should be added after these two lines as they appear by default.
127.0.0.1 localhost.localdomain localhost
192.168.0.1 server1.example.com server1
The naming convention for the hostname is: <IP address> <FQDN of SHR host system> <Short name of SHR host system>
Task b.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 b.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
Restart the Linux system for all the changes to take effect.
Task 2: Assemble the media
On the HP software download web site, the SHR installation media for Linux is distributed as a collection of the following three files:
HPSHR_940_Lin64.part1
HPSHR_940_Lin64.part2
HPSHR_940_Lin64.part3
Before you start installing SHR, you must download all three files, and then combine them into a single .tar
file.
To create the SHR installation media, follow these steps:
Download the SHR media files into a temporary directory on the system where you want to install SHR components.
To create a new directory for installing SHR, run the following command:
mkdir <directory name>
For example: mkdir /tmp/HPSHR_9.4-parts
To go to the directory that you created in the previous step, run the following command:
cd
<temp location>
For example: cd
/tmp/HPSHR_9.4-parts
Download the .tar
file parts into the newly created temporary directory.
To merge the contents into a single .tar
file, run the following command:
cat HPSHR_940_Lin64.part? > /tmp/HPSHR_9.4-parts/HPSHR940.tar
The SHR 9.40 media is now available as a single .tar
file in the following location:
/tmp/HPSHR_9.4-parts/HPSHR940.tar
Unzip the .tar
file, you will find the HP-SHR_9.40_setup.bin
to move ahead with the installation.
Note: You must ensure that the unzipped .tar
folder has all the access rights (RWX) to the owner and to the other groups.
Installation
Installing from the Command Line Console
Go to the media root.
Media root is the directory where the contents of the SHR media (the .tar
file) are extracted.
Note: If you want to Install SHR 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_9.40_setup.bin -i console
Press Enter to start the installation. The Choose Locale section appears.
Tip: At any point during installation, type back
to go to the previous page and type quit
to cancel the installation.
Review the license agreement details. Type Y to accept the agreement, and then press Enter. The installer shows different installation options.
Note: At this point of installation if you want to perform any of the following actions, refer to the Appendix section in this guide and then continue with the next installation steps.
Install SHR when /opt
does not have enough space.
Configure SHR application users group privileges for non-root group (non-zero id).
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.
Type 2 to select Sybase IQ Server, and then press Enter.
To install multiple server components, include a comma between the numerical identifiers. For example, to install HP Service Health Reporter Server and Sybase IQ Server together, type 1,2 and press Enter.
The installer performs necessary prerequisite checks and shows the result of the check in the console.
If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again.
/tmp/SHR-Missing-Patches.txt
and install them. Start the SHR 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: If you use the Modify option to install a new component on a system where another component is already installed, you must select both the 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.
After successful installation, run the following command:
hostname -f
Check if the hostname is displayed.
If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:
In the command line console, go to the rollback utility path.
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
See Database Backup and Recovery chapter in the HP Service Health ReporterConfiguration Guide if you want to move Sybase IQ to the server where SHR and SAP BusinessObjects is installed.
To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
Post-Installation Task for Sybase IQ
On a system with the Simplified Chinese or Japanese locale, manually delete the following files after installation:
$PMDB_HOME/Sybase/IQ-15_4/res/dblgzh_iq12_eucgb.res
$PMDB_HOME/Sybase/IQ-15_4/res/dblgzh_iq12_cp936.res
$PMDB_HOME/Sybase/IQ-15_4/res/dblgja_iq12_eucjis.res
$PMDB_HOME/Sybase/IQ-15_4/res/dblgja_iq12_sjis.res
To install with the help of the installation wizard, follow these steps:
Run the following file:
HP-SHR_9.40_setup.exe
The setup files are extracted.
Select the language in which you want to install SHR, and click OK.
The HP Service Health Reporter 9.40 Software Installer wizard appears.
Enter the SAP BusinessObjects install drive. The default value is C
.
Review the folders in which SHR would install. To change the installation folders, use the adjoining Browse buttons. Click Next.
Note: Do not enter spaces or special characters other than the - (hyphen) in the non-default folder name. The installation path must be less than 20 characters.
The installer performs checks for installation prerequisites and shows the result of the check on the Install Check page.
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.
Optionally, if you plan to install another server (SHR Server or Sybase IQ Server) on the same system later, restart it.
The installer wizard appears with Modify, Repair and Uninstall options. Select Modify option to install another component to the same system.
Caution: If you 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.
See Database Backup and Recovery chapter in the HP Service Health Reporter Configuration Guide if you want to move SAP BusinessObjects to the server where SHR and Sybase IQ is installed.
If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:
In the command line console, go to the rollback utility path.
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
<SHR INSTALL PATH>
For Example: rollback-utility.bat
C:\HP-SHR
To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
SHR 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 SHR system to another supported language, you must separately install the SAP BusinessObjects language pack for that language.
To install additional SAP BusinessObjects language pack, follow these steps:
Make sure that SHR is successfully installed with the default language pack.
To check that the default language pack is installed successfully, launch the SAP BusinessObjects InfoView portal (http://<SHR_HostName>:8080/InfoViewApp), and then go to InfoView Page > Preferences > General > Product Locale. The Product Locale box lists the installed language packs.
In this instance, <SHR_HostName> is the fully qualified domain name of the SHR system.
Go to the following directory:
%PMDB_HOME%\temp\BO_Updates
For all the languages edit the .ini
files with the BO drive that you have entered during SHR installation.
Example: INSTALLDIR="C:\Program Files (x86)\Business Objects\
"
IF the BO drive is changed to E
drive from the default C
drive then edit as follows in all of the .ini
language files:
INSTALLDIR="E:\Program Files (x86)\Business Objects\
"
If you have created a CMS password, include the password in all of the language .ini
files.
For Example: CMSPASSWORD=""
By default the .ini
files will not have any password. You have to include the CMC password into the .ini
files if you have created.
CMSPASSWORD="abc123"
Note: After completing the installation of SAP BusinessObjects, you must remove the password that you have typed for CMSPASSWORD in the .ini
files.
Run the following command:
BO_LanguagepackInstall.bat <SHR_media_root><lang_pack_name>
In this instance:
<SHR_media_root> is the path to the root of the SHR media (that is, the directory where the SHR installer is available). Do not type the name of the installer and do not use a trailing \
character.
For example, if the SHR media is extracted into the E:\Installer directory, which means the SHR installer (HP-SHR_9.40_setup.exe
) exists in the E:\Installer directory, you must run the following command:
BO_LanguagepackInstall.bat E:\Installer<lang_pack_name>
<lang_pack_name> is the name of the SAP BusinessObjects language pack. The following table provides names of language packs for all supported locales:
Language |
Language Pack Name |
---|---|
German |
de |
English |
en |
Spanish |
es |
French |
fr |
Italian |
it |
Korean |
ko |
Dutch |
nl |
Portuguese |
pt |
Russian |
ru |
Chinese |
zh_CN |
Note: Since the language pack installation requires a significant amount of time, you must correctly choose the language pack of your interest while running the command.
You can install multiple language packs by providing multiple language pack names in the command (separated by spaces). Separate two language pack names only by a single space character. For example, to install both Spanish and Korean language packs, run the following command:
BO_LanguagepackInstall.bat<SHR_media_root> es ko
These prerequisites apply to the system where you want to install HP Service Health Reporter and also the remote systems where you want to install the SHR data collector.
Hardware Requirements
For a list of hardware requirements, see the HP Service Health Reporter Performance, Sizing, and Tuning Guide..
Disk Space Requirements
Ensure that you have required space as follows in /opt
and /tmp
directories:
To download and merge the SHR media files, allocate at least 30 GB in the /tmp
directory on each system.
To install SHR components, allocate at least 20 GB in the /opt
directory on each system.
/tmp
directory on each system./opt
directory on each system./opt
directory. Software Requirements
For the complete list of software requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Operating System Requirements
For the complete list of operating system requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Before you install SHR, you must update your operating system, apply all patches, establish network connectivity, and disable the anti-virus software.
Ensure that the following libraries are available on each system where you plan to install SHR components.
Red Hat Enterprise Linux 6.x | Red Hat Enterprise Linux 5.5 | ||
---|---|---|---|
The list indicates the minimum required versions of required libraries. You can install a higher version of each library, if available. | |||
|
|
Note: Ensure that you have installed the tcsh-6.17-8.el6.x86_64
library.
Ensure that the swap space is twice the size of the RAM. To allocate sufficient swap space, perform the following steps:
Log on to the system as root.
/opt
and /var
directories.To set up the swap space by creating a new swap file, run the following commands :
dd if=/dev/zero of=
<swapfile_full_path>
bs=1M count=
<swap_size_in_MB>
mkswap <swapfile_full_path>
swapon <swapfile_full_path>
In this instance, <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 the previous step.
For example:
/extraswap swap swap defaults 0 0
Port Availability
SHR uses a number of default ports for different services. Ensure that the following ports are free before installing SHR components.
Service |
Port Number |
Protocol |
Inbound |
Outbound |
Description |
---|---|---|---|---|---|
HP PMDB Platform DB Logger |
21408 |
TCP |
Yes |
Yes |
The HP PMDB Platform DB Logger service persists logs in the database through this port. |
HP PMDB Platform Collection |
21409 |
TCP |
Yes |
Yes |
The JMX management port for the Collection service. The IM service monitors collection using this interface. |
HP PMDB Platform IM |
21410 |
TCP |
Yes |
No |
The JMX management port for the IM service. |
HP PMDB Platform Timer |
No port |
NA |
NA |
NA |
The Timer service for SHR. |
HP PMDB Platform Administrator |
21411 |
TCP |
Yes |
No |
The SHR web application server port, which hosts the Administration web application. The Report cross-launch functionality depends on this service. |
HP Software Communication Broker |
383 |
TCP |
Yes |
Yes |
SHR 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 SHR administration web server. |
HP PMDB Platform Collection | 21418 | HTTP | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 21419 | HTTPS | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 8080 | HTTP | No | Yes | The connection port to collect data from the SiteScope Data Acquisition API. |
HP PMDB Platform Sybase Service |
21424 |
TCP |
Yes |
Yes |
Port for the Sybase IQ server. |
Sybase IQ Agent 15.4 |
21423 |
TCP |
Yes |
No |
Port for the Sybase IQ Agent. |
HP-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 InfoView 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 (HOML01GEATON) |
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, SHR connects to RTSM. |
HPOM |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the HPOM database. SHR uses this port to connect to the HPOM database. |
HP Operations Agent |
383 |
TCP |
No |
Yes |
SHR 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. SHR uses this port to connect to the Profile database and the OMi database. |
Web Browser Requirements
To view the SHR Administration Console in Internet Explorer or Mozilla Firefox, you must enable the ActiveX and the JavaScript controls. Follow the Help menu of the web browser for assistance with enabling them.
For a list of supported Web Browsers, see "Web Browsers and Plug-ins" in the HP Service Health Reporter Support Matrix.
After ensuring that the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for the SHR installation.
Task 1: Disable Anti-Virus
Anti-virus applications can hinder the installation of SHR. Temporarily disable any anti-virus software that might be running.
Re-enable the anti-virus software after the installation is complete.
Task 2: Configure Firewall
If you use firewall software, ensure that the firewall allows traffic through the required ports (see Installation Prerequisites > Port Availability ) on the SHR system.
To disable the firewall, perform the following steps:
Log on as root 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 3: Prepare the Linux System
On the Linux system, you must perform a set of additional steps.
Task 3.1: Disable SELinux
To disable SELinux, in the /etc/sysconfig/selinux
file, set the parameter SELINUX = disabled
.
Task 3.2: Configure the Kernel Parameters (only if you use Red Hat Enterprise Linux 6.x)
To configure the Kernel parameters, follow these steps:
/etc/sysctl.conf
file.Note: If higher values are specified for these parameters already, do not make any modifications.
Task 3.3: Configure the Hostname
Log on to the SHR system, and configure the hostname in the /etc/hosts
file.
If you configure a hostname, it should be added after these two lines as they appear by default.
127.0.0.1 localhost.localdomain localhost
192.168.0.1 server1.example.com server1
The naming convention for the hostname is: <IP address> <FQDN of SHR host system> <Short name of SHR host system>
Task 3.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 3.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
Restart the Linux system for all the changes to take effect.
Task 4: Verify the Fully Qualified Domain Name (FQDN) of the System
Before performing the SHR installation, you must verify that DNS lookup returns the accurate FQDN of the system. If the entry for the DNS lookup is different from the host name of the system, you may experience difficulties in logging on to the SHR Administration Console. This can occur 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 hostname of the system:
hostname -f
Note down the hostname 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 system.
Ensure that the name displayed after running the nslookup
command matches the name displayed after running the HOSTNAME command. If the names do not match, you must change the hostname of the system.
Task 5: Assemble the media
On the HP software download web site, the SHR installation media for Linux is distributed as a collection of the following three files:
HPSHR_940_Lin64.part1
HPSHR_940_Lin64.part2
HPSHR_940_Lin64.part3
Before you start installing SHR, you must download all three files, and then combine them into a single .tar
file.
To create the SHR installation media, follow these steps:
Download the SHR media files into a temporary directory on the system where you want to install SHR components.
To create a new directory for installing SHR, run the following command:
mkdir <directory name>
For example: mkdir /tmp/HPSHR_9.4-parts
To go to the directory that you created in the previous step, run the following command:
cd
<temp location>
For example: cd
/tmp/HPSHR_9.4-parts
Download the .tar
file parts into the newly created temporary directory.
To merge the contents into a single .tar
file, run the following command:
cat HPSHR_940_Lin64.part? > /tmp/HPSHR_9.4-parts/HPSHR940.tar
The SHR 9.40 media is now available as a single .tar
file in the following location:
/tmp/HPSHR_9.4-parts/HPSHR940.tar
Unzip the .tar
file, you will find the HP-SHR_9.40_setup.bin
to move ahead with the installation.
Note: You must ensure that the unzipped .tar
folder has all the access rights (RWX) to the owner and to the other groups.
Additional Considerations
Always install SHR as root.
Note: The root user must be the owner of the /opt
and /var
directories.
Note: The SHR installer does not support forced reinstallation. In the event of a unsuccessful installation, you must manually remove all the files that were placed by the installer and start the installation process again.
Install HP Service Health Reporter Server, Sybase IQ Server, and SAP BusinessObjects Server on a single system.
Installing from the Command Line Console
Go to the media root.
Media root is the directory where the contents of the SHR media (the .tar
file) are extracted.
Note: If you want to Install SHR 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_9.40_setup.bin -i console
Press Enter to start the installation. The Choose Locale section appears.
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.
The installer shows the license agreement details. Type Y to accept the agreement, and then press Enter. The installer shows different installation options.
Note: At this point of installation if you want to perform any of the following actions, refer to the Appendix section in this guide and then continue with the next installation steps.
Install SHR when /opt
does not have enough space.
Configure SHR application users group privileges for non-root group (non-zero id).
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.
Type 1 for Typical HP Service Health Reporter Installation to install SHR, Sybase IQ, and SAP BusinessObjects. Press Enter.
The installer performs necessary prerequisite checks and shows the result of the check in the console.
If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again.
/tmp/SHR-Missing-Patches.txt
and install them. Start the SHR installation again.If the prerequisite check is successful, press Enter. The installer shows preinstallation summary in the console.
After successful installation, run the following command:
hostname -f
Check if the hostname is displayed.
If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:
In the command line console, go to the rollback utility path.
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
Note: During SHR installation in Linux, SAP BusinessObjects client tools are also installed but not supported on Linux. If SHR is installed on a Linux server, you must install the SAP BusinessObjects client tools on a Windows operating system for developing or customizing application content. For more information, see Developing Content in Linux using CDE section of HP Service Health Reporter Content Development Guide.
To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
On a system with the Simplified Chinese or Japanese locale, manually delete the following files after installation:
$PMDB_HOME/Sybase/IQ-15_4/res/dblgzh_iq12_eucgb.res
$PMDB_HOME/Sybase/IQ-15_4/res/dblgzh_iq12_cp936.res
$PMDB_HOME/Sybase/IQ-15_4/res/dblgja_iq12_eucjis.res
$PMDB_HOME/Sybase/IQ-15_4/res/dblgja_iq12_sjis.res
The custom installation of SHR enables you to install different components of SHR on different systems. SHR comprises of the following fundamental components:
You can choose to install each of these components on a separate, dedicated server, or you can install any one component on a dedicated server while the rest reside together on another server.
The following table illustrates different types of environments that you can create with the custom installation options.
Environment 1 | Environment 2 | Environment 3 |
---|---|---|
System1: SHR server System2: Sybase IQ server System3: SAP BusinessObjects server |
System1: SHR server System2: Sybase IQ server + SAP BusinessObjects server |
System1: SHR server + SAP BusinessObjects server System2: Sybase IQ server |
If you have high performance load on a server, HP recommends that you install it on a separate system. For more information on performance considerations, see HP Service Health Reporter Performance, Sizing, and Tuning Guide.
Ensure that all the prerequisites that are listed in this section are met on each system.
Hardware Requirements
For a list of hardware requirements, see the HP Service Health Reporter Performance, Sizing, and Tuning Guide..
Disk Space Requirements
Ensure that you have required space as follows in /opt
and /tmp
directories:
To download and merge the SHR media files, allocate at least 30 GB in the /tmp
directory on each system.
To install SHR components, allocate at least 20 GB in the /opt
directory on each system.
/tmp
directory on each system./opt
directory on each system./opt
directory. Software Requirements
For the complete list of software requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Operating System Requirements
For the complete list of operating system requirements, see the Requirements section in the HP Service Health Reporter Support Matrix.
Before you install SHR, you must update your operating system, apply all patches, establish network connectivity, and disable the anti-virus software.
Ensure that the following libraries are available on each system where you plan to install SHR components.
Red Hat Enterprise Linux 6.x | Red Hat Enterprise Linux 5.5 | ||
---|---|---|---|
The list indicates the minimum required versions of required libraries. You can install a higher version of each library, if available. | |||
|
|
Note: Ensure that you have installed the tcsh-6.17-8.el6.x86_64
library.
Ensure that the swap space is twice the size of the RAM. To allocate sufficient swap space, perform the following steps:
Log on to the system as root.
/opt
and /var
directories.To set up the swap space by creating a new swap file, run the following commands :
dd if=/dev/zero of=
<swapfile_full_path>
bs=1M count=
<swap_size_in_MB>
mkswap <swapfile_full_path>
swapon <swapfile_full_path>
In this instance, <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 the previous step.
For example:
/extraswap swap swap defaults 0 0
Port Availability
SHR uses a number of default ports for different services. Ensure that the following ports are free before installing SHR components.
Service |
Port Number |
Protocol |
Inbound |
Outbound |
Description |
---|---|---|---|---|---|
HP PMDB Platform DB Logger |
21408 |
TCP |
Yes |
Yes |
The HP PMDB Platform DB Logger service persists logs in the database through this port. |
HP PMDB Platform Collection |
21409 |
TCP |
Yes |
Yes |
The JMX management port for the Collection service. The IM service monitors collection using this interface. |
HP PMDB Platform IM |
21410 |
TCP |
Yes |
No |
The JMX management port for the IM service. |
HP PMDB Platform Timer |
No port |
NA |
NA |
NA |
The Timer service for SHR. |
HP PMDB Platform Administrator |
21411 |
TCP |
Yes |
No |
The SHR web application server port, which hosts the Administration web application. The Report cross-launch functionality depends on this service. |
HP Software Communication Broker |
383 |
TCP |
Yes |
Yes |
SHR 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 SHR administration web server. |
HP PMDB Platform Collection | 21418 | HTTP | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 21419 | HTTPS | Yes | No | The connection port to the HTTP server for the SiteScope generic data integration. |
HP PMDB Platform Collection | 8080 | HTTP | No | Yes | The connection port to collect data from the SiteScope Data Acquisition API. |
HP PMDB Platform Sybase Service |
21424 |
TCP |
Yes |
Yes |
Port for the Sybase IQ server. |
Sybase IQ Agent 15.4 |
21423 |
TCP |
Yes |
No |
Port for the Sybase IQ Agent. |
HP-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 InfoView 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 (HOML01GEATON) |
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, SHR connects to RTSM. |
HPOM |
Any |
TCP |
No |
Yes |
This is the port that is configured in the Administration Console for the HPOM database. SHR uses this port to connect to the HPOM database. |
HP Operations Agent |
383 |
TCP |
No |
Yes |
SHR 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. SHR uses this port to connect to the Profile database and the OMi database. |
Web Browser Requirements
To view the SHR Administration Console in Internet Explorer or Mozilla Firefox, you must enable the ActiveX and the JavaScript controls. Follow the Help menu of the web browser for assistance with enabling them.
For a list of supported Web Browsers, see "Web Browsers and Plug-ins" in the HP Service Health Reporter Support Matrix.
After ensuring that the installation prerequisites are fulfilled, you must perform a series of tasks to prepare the server for SHR installation.
Task 1: Disable Anti-Virus
Anti-virus applications can hinder the installation of SHR. Temporarily disable any anti-virus software that might be running.
Re-enable the anti-virus software after the installation is complete.
Task 2: Configure Firewall
If you use firewall software, ensure that the firewall allows traffic through the required ports (see Installation Prerequisites > Port Availability ) on the SHR system.
To disable the firewall, perform the following steps:
Log on as root and run the following commands:
/opt
and /var
directories.chkconfig iptables off
chkconfig ip6tables off
/etc/init.d/iptables stop
/etc/init.d/ip6tables stop
Task 3: Prepare the Linux System
On the Linux system, you must perform a set of additional steps.
Task 3.1: Disable SELinux
To disable SELinux, in the /etc/sysconfig/selinux
file, set the parameter SELINUX = disabled
.
Task 3.2: Configure the Kernel Parameters (only if you use Red Hat Enterprise Linux 6.x)
To configure the Kernel parameters, follow these steps:
/etc/sysctl.conf
file.Note: If higher values are specified for these parameters already, do not make any modifications.
Task 3.3: Configure the Hostname
Log on to the SHR system, and configure the hostname in the /etc/hosts
file.
If you configure a hostname, it should be added after these two lines as they appear by default.
127.0.0.1 localhost.localdomain localhost
192.168.0.1 server1.example.com server1
The naming convention for the hostname is: <IP address> <FQDN of SHR host system> <Short name of SHR host system>
Task 3.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 3.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
Restart the Linux system for all the changes to take effect.
Task 4: Verify the Fully Qualified Domain Name (FQDN) of the System
Before performing the SHR installation, you must verify that DNS lookup returns the accurate FQDN of the system. If the entry for the DNS lookup is different from the host name of the system, you may experience difficulties in logging on to the SHR Administration Console. This can occur 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 console and type the following command to check the hostname of the system:
hostname -f
Note down the hostname 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 system.
Ensure that the name displayed after running the nslookup
command matches the name displayed after running the HOSTNAME command. If the names do not match, you must change the hostname of the system.
Task 5: Assemble the media
On the HP software download web site, the SHR installation media for Linux is distributed as a collection of the following three files:
HPSHR_940_Lin64.part1
HPSHR_940_Lin64.part2
HPSHR_940_Lin64.part3
Before you start installing SHR, you must download all three files, and then combine them into a single .tar
file.
To create the SHR installation media, follow these steps:
Download the SHR media files into a temporary directory on the system where you want to install SHR components.
To create a new directory for installing SHR, run the following command:
mkdir <directory name>
For example: mkdir /tmp/HPSHR_9.4-parts
To go to the directory that you created in the previous step, run the following command:
cd
<temp location>
For example: cd
/tmp/HPSHR_9.4-parts
Download the .tar
file parts into the newly created temporary directory.
To merge the contents into a single .tar
file, run the following command:
cat HPSHR_940_Lin64.part? > /tmp/HPSHR_9.4-parts/HPSHR940.tar
The SHR 9.40 media is now available as a single .tar
file in the following location:
/tmp/HPSHR_9.4-parts/HPSHR940.tar
Unzip the .tar
file, you will find the HP-SHR_9.40_setup.bin
to move ahead with the installation.
Note: You must ensure that the unzipped .tar
folder has all the access rights (RWX) to the owner and to the other groups.
Additional Considerations
Always install SHR as root.
Note: The root user must be the owner of the /opt
and /var
directories.
Note: The SHR installer does not support forced reinstallation. In the event of a unsuccessful installation, you must manually remove all the files that were placed by the installer and start the installation process again.
Installing from the Command Line Console
Go to the media root.
Media root is the directory where the contents of the SHR media (the .tar
file) are extracted.
Note: If you want to Install SHR 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_9.40_setup.bin -i console
Press Enter to start the installation. The Choose Locale section appears.
Tip: At any point during installation, type back
to go to the previous page and type quit
to cancel the installation.
Review the license agreement details. Type Y to accept the agreement, and then press Enter.
Note: At this point of installation if you want to perform any of the following actions, refer to the Appendix section in this guide and then continue with the next installation steps.
Install SHR when /opt
does not have enough space.
Configure SHR application users group privileges for non-root group (non-zero id).
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.
Type 1 to select HP Service Health Reporter Server, and then press Enter.
To install multiple server components, include a comma between the numerical identifiers. For example, to install HP Service Health Reporter Server and Sybase IQ Server together, type 1,2 and press Enter.
The installer performs necessary prerequisite checks and shows the result of the check in the console. If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met, and then start the installation again.
/tmp/SHR-Missing-Patches.txt
and install them. Start the SHR 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: If you use the Modify option to install a new component on a system where another component is already installed, you must select both the components in the installer wizard. If you use the command line console, enter the numerical identifier of both the 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.
After successful installation, run the following command:
hostname -f
Check if the hostname is displayed.
If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:
In the command line console, go to the rollback utility path.
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 perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
Installing from the Command Line Console
Go to the media root.
Note: If you want to Install SHR 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_9.40_setup.bin -i console
Press Enter to start the installation.
Tip: At any point during installation, type back
to go to the previous page and type quit
to cancel the installation.
Review the license agreement details. Type Y to accept the agreement and press Enter.
Note: At this point of installation if you want to perform any of the following actions, refer to the Appendix section in this guide and then continue with the next installation steps.
Install SHR when /opt
does not have enough space.
Configure SHR application users group privileges for non-root group (non-zero id).
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.
Type 2 to select Sybase IQ Server and press Enter.
To install multiple server components, include a comma between the numerical identifiers. For example, to install HP Service Health Reporter Server and Sybase IQ Server together, type 1,2 and press Enter.
The installer performs necessary prerequisite checks and shows the result of the check in the console.
If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again.
/tmp/SHR-Missing-Patches.txt
and install them. Start the SHR installation again.If the prerequisite check is successful, press Enter.
The installer shows preinstallation summary in the console. Press Enter to start the installation.
See Database Backup and Recovery chapter in the HP Service Health Reporter Configuration Guide if you want to move Sybase IQ to the server where SHR and SAP BusinessObjects is installed.
Caution: If you 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.
After successful installation, run the following command:
hostname -f
Check if the hostname is displayed.
If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:
In the command line console, go to the rollback utility path.
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 perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
On a system with the Simplified Chinese or Japanese locale, manually delete the following files after installation:
$PMDB_HOME/Sybase/IQ-15_4/res/dblgzh_iq12_eucgb.res
$PMDB_HOME/Sybase/IQ-15_4/res/dblgzh_iq12_cp936.res
$PMDB_HOME/Sybase/IQ-15_4/res/dblgja_iq12_eucjis.res
$PMDB_HOME/Sybase/IQ-15_4/res/dblgja_iq12_sjis.res
Installing from the Command Line Console
Go to the media root.
Note: If you want to Install SHR 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_9.40_setup.bin -i console
Press Enter to start the installation.
Tip: At any point during installation, type back
to go to the previous page and type quit
to cancel the installation.
Review the license agreement details. Type Y to accept the agreement and press Enter.
Note: At this point of installation if you want to perform any of the following actions, refer to the Appendix section in this guide and then continue with the next installation steps.
Install SHR when /opt
does not have enough space.
Configure SHR application users group privileges for non-root group (non-zero id).
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.
Type 3 to select SAP BusinessObjects Server and press Enter.
To install multiple server components, include a comma between the numerical identifiers. For example, to install HP Service Health Reporter Server and Sybase IQ Server together, type 1,2 and press Enter.
The installer performs necessary prerequisite checks and shows the result of the check in the console. If the prerequisite check fails or shows warning messages, ensure that all the prerequisites are met and start the installation again.
/tmp/SHR-Missing-Patches.txt
and install them. Start the SHR installation again.If the prerequisite check is successful, press Enter.
The installer shows preinstallation summary in the console. Press Enter to start the installation.
See Database Backup and Recovery chapter in the HP Service Health Reporter Configuration Guide if you want to move SAP BusinessObjects to the server where SHR and Sybase IQ is installed.
Caution: If you 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.
After successful installation, run the following command:
hostname -f
Check if the hostname is displayed.
If the installation fails, click Rollback and wait till the product gets rolled back. Run the rollback utility as follows:
In the command line console, go to the rollback utility path.
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
Note: During SHR installation in Linux, SAP BusinessObjects client tools are also installed but not supported on Linux. If SHR is installed on a Linux server, you must install the SAP BusinessObjects client tools on a Windows operating system for developing or customizing application content. For more information, see Developing Content in Linux using CDE section of HP Service Health Reporter Content Development Guide.
To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.
This is not a supported selection. Sybase IQ should be installed on Linux operating system or on Windows 2008 operating system as it is not supported in Windows 2012. Click Change and select the Custom option.
After you install the SHR software, verify if the product is working properly.
Perform the following to verify the success of installation:
Log on to the SHR system.
Click Start > Run. The Run dialog box appears.
Type services.msc
in the Open field, and then press ENTER. The Services window appears.
On the right pane, view the status of the SHR services.
To check the status of the SAP BusinessObjects services, you can use the SAP BusinessObjects Central Configuration Manager. Perform the following steps:
Go to Start and type Central Configuration Manager in Search. Double click on Central Configuration Manager and the window appears.
Log on to the Central Management Console.
From the drop down select Servers.
Note the status of the listed SAP BusinessObjects services. All services must be enabled and running.
Perform the following to verify the success of installation on Linux operating system:
Run the following command:
chkconfig --list
The command output lists the SHR services. Run the following commands for each of the services to ensure that they are running satisfactorily :
service HP_PMDB_Platform_Administrator status
service HP_PMDB_Platform_Collection status
service HP_PMDB_Platform_DB_Logger status
service HP_PMDB_Platform_IM status
service HP_PMDB_Platform_PostgreSQL status
service HP_PMDB_Platform_Sybase status
service HP_PMDB_Platform_IA status
service TrendTimer status
To check the status of the SAP BusinessObjects services, run the following commands at the command line console:
su - SHRBOADMIN
cd /opt/HP/BSM/BO/bobje
sh ccm.sh -display
The command output shows the status of SAP BusinessObjects services. All services must be enabled and running.
After you install the SHR software, verify if the product is working properly.
Perform the following to verify the success of installation:
Log on to the SHR system.
Click Start > Run. The Run dialog box appears.
Type services.msc
in the Open field, and then press ENTER. The Services window appears.
On the right pane, view the status of the SHR services.
To check the status of the SAP BusinessObjects services, you can use the SAP BusinessObjects Central Configuration Manager. Perform the following steps:
Click Start > Programs > BusinessObjects XI 3.1 > BusinessObjects Enterprise > Central Configuration Manager. The Central Configuration Manager window appears.
Log on to the Central Management Console.
From the drop down select Servers.
Note the status of the listed SAP BusinessObjects services. All services must be enabled and running.
Perform the following to verify the success of installation on Linux operating system:
Run the following command:
chkconfig --list
The command output lists the SHR services. Run the following commands for each of the services to ensure that they are running satisfactorily :
service HP_PMDB_Platform_Administrator status
service HP_PMDB_Platform_Collection status
service HP_PMDB_Platform_DB_Logger status
service HP_PMDB_Platform_IM status
service HP_PMDB_Platform_PostgreSQL status
service HP_PMDB_Platform_Sybase status
service HP_PMDB_Platform_IA status
service TrendTimer status
To check the status of the SAP BusinessObjects services, run the following commands at the command line console:
su - SHRBOADMIN
cd /opt/HP/BSM/BO/bobje
sh ccm.sh -display
The command output shows the status of SAP BusinessObjects services. All services must be enabled and running.
Note: If you have installed SHR on Red Hat Enterprise Linux 6.6, ensure that you perform Manual Restart of Tomcat Services in HP Service Health Reporter Configuration Guide after completing SHR configuration.
In the typical installation mode of SHR, the data collector is installed on the same system where SHR is installed. But, you can also install the data collector on a separate server. Also, you can install collectors on multiple systems as necessary.
In the typical installation mode of SHR, the data collector is installed on the same system where SHR is installed. But, you can also install the data collector on a separate server. Also, you can install collectors on multiple systems as necessary.
If you want to install SHR and install HP Operations agent on the same system, you must perform the following additional configuration steps:
Install HP Operations agent on the SHR Application system.
Log on to the SHR Application 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.
Follow these steps:
Run the following command on the SHR Application system:
ovc -restart
Run the following command on the SHR Application 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 SHR server:
ovcert -exporttrusted -file <filename1>
ovcert -importtrusted -file <filename1> -ovrg server
ovcert -exportcert -file <filename2> -pass <any password>
ovcert -importcert -file <filename2> -pass <password entered in earlier step> -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 SHR Application system:
ovc -status -level 8
The SHR 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 SHR system:
ovc -restart
If you want to install SHR and install HP Operations agent on the same system, you must perform the following additional configuration steps:
Install HP Operations agent on the SHR Application system.
Log on to the SHR Application 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.
Follow these steps:
Run the following command on the SHR Application system:
ovc -restart
Run the following command on the SHR Application 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 SHR server:
ovcert -exporttrusted -file <filename1>
ovcert -importtrusted -file <filename1> -ovrg server
ovcert -exportcert -file <filename2> -pass <any password>
ovcert -importcert -file <filename2> -pass <password entered in earlier step> -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 SHR Application system:
ovc -status -level 8
The SHR 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 SHR Application system:
ovc -restart
If you want to install SHR collector on a remote system and install HP Operations agent on the same system, perform the following additional configuration steps:
Install SHR collector on the remote system with HP Operations agent on the same system.
Log on to the SHR 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 displays a list of all certificates installed on the system.
Follow these steps:
Run the following command on the SHR 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 onto the SHR collector system.
Run the following command on the SHR 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 SHR collector system:
ovc -restart
If you want to install SHR collector on a remote system and install HP Operations agent on the same system, perform the following additional configuration steps:
Install SHR collector on the remote system with HP Operations agent on the same system.
Log on to the SHR 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.
Follow these steps:
Run the following command on the SHR 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 onto the SHR collector system.
Run the following command on the SHR 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 SHR collector system:
ovc -restart
You can upgrade to the latest version of SHR from the previous version only. You cannot upgrade any other older versions of SHR directly to the latest version.
You can upgrade to latest version of SHR on Windows 2008 operating system and then migrate to Windows 2012. For more information, see Migrating to Windows 2012 Environment section in HP Service Health Reporter Configuration Guide.
On the HP software download web site, the SHR installation media for Windows is distributed as a collection of the following three files:
HPSHR_940_Win64.part1
HPSHR_940_Win64.part2
HPSHR_940_Win64.part3
Before you start installing SHR, you must download all three files, and then combine them into a single .tar
file.
To create the SHR installation media, follow these steps:
Click Start > Run to open the Run prompt.
Type CMD
and press Enter. The command prompt window appears.
To create a new directory to install SHR, run the following command:
mkdir
drive:\directory name
For example: mkdir
C:\temp\HPSHR_9.4-parts
Download the .tar
file parts into the temporary folder that you created in the previous step.
For example: C:\temp\HPSHR_9.4-parts
.
To go to the location where you have copied the .tar
file parts, run the following command:
cd
<temp location>
For example: cd
C:\temp\HPSHR_9.4-parts
To merge the contents into a single .tar
file, run one of the following commands:
copy /b HPSHR_940_Win64.part? C:\temp\HPSHR_9.4-parts\HPSHR940.tar
or
type HPSHR_940_Win64.part? > C:\temp\HPSHR_9.4-parts\HPSHR940.tar
Note: You must type the command in a single line.
The SHR 9.40 media is now available as a single .tar
file in the following location:
C:\temp\HPSHR_9.4-parts\HPSHR940.tar
Unzip the .tar
file, you will find the HP-SHR_9.40_setup.exe
to move ahead with the installation.
To perform upgrade ensure that you have 5 GB disk space available in the directory where you have installed SHR.
Prerequisites for Upgrade
Before you proceed with the upgrade of SHR, complete the following tasks:
Take a backup of the complete SHR setup to prevent any data loss due to a unsuccessful upgrade.
For more information, see “Database Backup and Recovery” in the HP Service Health Reporter Configuration Guide.
Stop all SHR services using the following steps:
Stop the following services:
Open Windows Task Manager, go to the Processes tab:
Run the following command to verify whether all the required services and processes are stopped:
%PMDB_HOME%\DR\SHRServiceCheck.bat
Ensure all the installation prerequisites and preinstallation tasks listed in the Installation section of this document are met.
Note: SHR 9.40 does not support Windows 2003. If SHR is currently installed on Windows 2003, make sure to upgrade the operating system to Windows 2008 before upgrading to SHR 9.40.
Important Upgrade Considerations
Use the installer program provided with the SHR media to perform the upgrade. Note the following before performing the upgrade:
Typical Installation: If all components in the previous version of the SHR setup are installed on a single system, follow the instructions for Typical Installation, click Upgrade to complete the upgrade.
Custom Installation: If Sybase IQ is installed on a remote system in the previous version of the SHR setup, you must select the Custom Installation option in the SHR installer wizard and follow the custom installation instructions, click Upgradeto complete the upgrade. Install the SHR components as follows:
Note: Upgrade the remote Sybase IQ system (ensure that there is 5 GB disk space available) before upgrading the SHR system. Sybase IQ database must be up and running before performing the upgrade.
Upgrade SHR data collector:If the SHR data collector is installed on a remote system, upgrade it by performing the following:
\packages
folder.Copy the following file to the remote system where data collector is installed.
HP-SHR-09.40-RemoteCollector.zip
HP-SHR-09.40-RemoteCollector.tar.gz
HP-SHR-RemotePoller_9.40_setup
file.In the last step while performing the upgrade, clear the Force repair of already installed component packages check box and click Upgrade.
Upgrade steps
From the SHR media, run the following file:
HP-SHR_9.40_setup.exe
The set up files are extracted.
Select the language in which you want to install SHR, and click OK.
The HP Service Health Reporter 9.40 Software Installer wizard appears.
On the Introduction page, review the note and click Next.
Note: In High Availability environment, manually copy the %PMDB_HOME%\temp\postgreInstall.bat
file to the %temp%\..\HP-SHR
directory.
On the License Agreement page, review the license agreement. Select I accept..., and click Next to proceed with the installation.
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.
The Introduction (Upgrade) page opens. Review the summary, and click Next.
In Pre-Upgrade Summary page, click Upgrade.
Note: After performing the upgrade, launch the SHR Administration Console > Administration > Deployment Manager and upgrade the content packs to the latest version. For more information, see “Upgrading Content Packs” in the HP Service Health Reporter Configuration Guide.
The SysPerf_SiS_ETL Content Pack component is deprecated. Instead of SysPerf_SiS_ETL, use SysPerf_SiS_DB or SysPerf_SiS_API. For more information, see HP Service Health Reporter Online Help for Administrators.
If the upgrade fails, restore the backup of the previous version and then perform upgrade again.
Post-Upgrade Configurations
Perform the following tasks after upgrading SHR:
Task 1: To Synchronize the data on the configured collectors
If you have configured local or remote collectors with DB data sources, then from the SHR server, run the following command:
remotepollerutility –syncds –type DB –pollername local
If you have the remote collector configured, run the following command:
remotepollerutility –syncds –type DB –pollername remotecollectorname
Task 2: Reapplying Access Levels for the Universe Connection
When you upgrade a SHR Content Pack, the Universe connections are recreated. If you have specific user access levels enabled, you must re-assign the access after completing the upgrade. By default, the administrator will have complete access to the Universe connections. Therefore, if you have applied access restriction at each user or group level other than administrator user, you must grant same access restrictions again for the universe connection. For more information about enabling user access levels, see the SAP BusinessObjects documentation.
Task 3: Verify that SHR is Upgraded Successfully
Launch the following URL and make sure that you are able to log on to the Administration Console as administrator:
http://<SHR_Server_FQDN>:21411
Launch the following URL and make sure that you are able to log on to the InfoView Console as administrator:
http://<SHR_Server_FQDN>:8080
If you are able to successfully log on as administrator, SHR is upgraded successfully. If you see an authentication error, you must restore the backed-up databases on the system, and perform the upgrade procedure again. For more information, see the "Database Backup and Recovery" section in the HP Service Health Reporter Configuration Guide.
Note: Recreate Administrator and Collection Services
If you have installed SHR in a domain, recreate the following services as mentioned in "Configuring SHR Services when SHR is Installed in a Domain" section of the HP Service Health Reporter Configuration Guide.
To migrate to the latest version of SHR on Windows 2012 operating system, Sybase IQ must be installed on Linux. Windows 2012 does not support Sybase IQ which comes bundled with the SHR media. For more information, see HP Service Health Reporter Configuration Guide.
You can upgrade to the latest version of SHR from the previous version only. You cannot upgrade any other older versions of SHRdirectly to the latest version.
To perform upgrade ensure that you have 5 GB disk space available in the directory where you have installed SHR.
On the HP software download web site, the SHR installation media for Linux is distributed as a collection of the following three files:
HPSHR_940_Lin64.part1
HPSHR_940_Lin64.part2
HPSHR_940_Lin64.part3
Before you start installing SHR, you must download all three files, and then combine them into a single .tar
file.
To create the SHR installation media, follow these steps:
Download the SHR media files into a temporary directory on the system where you want to install SHR components.
To create a new directory for installing SHR, run the following command:
mkdir <directory name>
For example: mkdir /tmp/HPSHR_9.4-parts
To go to the directory that you created in the previous step, run the following command:
cd
<temp location>
For example: cd
/tmp/HPSHR_9.4-parts
Download the .tar
file parts into the newly created temporary directory.
To merge the contents into a single .tar
file, run the following command:
cat HPSHR_940_Lin64.part? > /tmp/HPSHR_9.4-parts/HPSHR940.tar
The SHR 9.40 media is now available as a single .tar
file in the following location:
/tmp/HPSHR_9.4-parts/HPSHR940.tar
Unzip the .tar
file, you will find the HP-SHR_9.40_setup.bin
to move ahead with the installation.
Note: You must ensure that the unzipped .tar
folder has all the access rights (RWX) to the owner and to the other groups.
Prerequisites for Upgrade
Before you proceed with the upgrade of SHR, complete the following tasks:
Take a backup of the complete SHR setup to prevent any data loss due to a unsuccessful upgrade.
For more information, see “Database Backup and Recovery” in the HP Service Health Reporter Configuration Guide.
Stop all SHR services using the following steps:
Run the following commands:
service HP_PMDB_Platform_Administrator stop
service HP_PMDB_Platform_Collection stop
service HP_PMDB_Platform_DB_Logger stop
service TrendTimer stop
service HP_PMDB_Platform_IM stop
service HP_PMDB_Platform_PostgreSQL stop
service HP_PMDB_Platform_Sybase stop
(In Custom Installation, stop this service before upgrading the Sybase IQ server)Perform the following steps to stop the SAP BusinessObjects services:
Run the following command to stop the webserver:
sh /opt/HP/BSM/BO/bobje/tomcatshutdown.sh
(In Custom Installation, stop this service before upgrading the SAP BusinessObjects server)
Run the following commands to stop the services.
ps -ef|grep iqsrv15
(In Custom Installation, stop this service before upgrading the Sybase IQ server)ps -ef | grep abcloadNrun
Note down the process ID (pid) displayed by the output of each command and run the following commands
kill -9 <pid_1>
kill -9 <pid_2>
In this instance, <pid_1> and <pid_2> are the process IDs that you noted down in the earlier step.
Ensure all the installation prerequisites and preinstallation tasks listed in the Installation section of this document are met.
Important Upgrade Considerations
Use the installer program provided with the SHR media to perform the upgrade. Note the following before performing the upgrade:
Typical Installation: If all components in the previous version of the SHR setup are installed on a single system, follow the typical installation instructions in this document to complete the upgrade.
Custom Installation: If Sybase IQ is installed on a remote system in the previous version of the SHR setup, you must select the Custom Installation option in the SHR installer wizard and follow the custom installation instructions in this document to complete the upgrade. Install the SHR components as follows:
Note: Upgrade the remote Sybase IQ system (ensure that there is 5 GB disk space available) before upgrading the SHR system. Sybase IQ database must be up and running before performing the upgrade.
Upgrade SHR data collector:If the SHR data collector is installed on a remote system, upgrade it by performing the following:
\packages
directory.Copy the following file to the remote system where data collector is installed.
HP-SHR-09.40-RemoteCollector.zip
HP-SHR-09.40-RemoteCollector.tar.gz
HP-SHR-RemotePoller_9.40_setup
file.Note: After performing the upgrade, launch the SHR Administration Console > Administration > Deployment Manager and upgrade the content packs to the latest version. For more information, see “Upgrading Content Packs” in the HP Service Health Reporter Configuration Guide.
The SysPerf_SiS_ETL Content Pack component is deprecated. Instead of SysPerf_SiS_ETL, use SysPerf_SiS_DB or SysPerf_SiS_API. For more information, see HP Service Health Reporter Online Help for Administrators.
If the upgrade fails, restore the backup of the previous version and then perform upgrade again.
Post-Upgrade Configurations
Perform the following tasks after upgrading SHR:
Task 1: To Synchronize the data on the configured collectors
If you have configured local or remote collectors with DB data sources, then from the SHR server, run the following command:
remotepollerutility –syncds –type DB –pollername local
If you have the remote collector configured, run the following command:
remotepollerutility –syncds –type DB –pollername remotecollectorname
Task 2: Reapplying Access Levels for the Universe Connection
When you upgrade a SHR Content Pack, the Universe connections are recreated. If you have specific user access levels enabled, you must re-assign the access after completing the upgrade. By default, the administrator will have complete access to the Universe connections. Therefore, if you have applied access restriction at each user or group level other than administrator user, you must grant same access restrictions again for the universe connection. For more information about enabling user access levels, see the SAP BusinessObjects documentation.
Task 3: Verify that SHR is Upgraded Successfully
Launch the following URL and make sure that you are able to log on to the Administration Console as administrator:
http://<SHR_Server_FQDN>:21411
Launch the following URL and make sure that you are able to log on to the InfoView Console as administrator:
http://<SHR_Server_FQDN>:8080
If you are able to successfully log on as administrator, SHR is upgraded successfully. If you see an authentication error, you must restore the backed-up databases on the system, and perform the upgrade procedure again. For more information, see the "Database Backup and Recovery" section in the HP Service Health Reporter Configuration Guide.
Note: Recreate Administrator and Collection Services
If you have installed SHR in a domain, recreate the following services as mentioned in "Configuring SHR Services when SHR is Installed in a Domain" section of the HP Service Health Reporter Configuration Guide.
The SHR 9.40 media presents the following add-on content that you can install anytime on the SHR server node:
Note: To install the add-on content in windows perform the following:
Go to the location where you have installed SHR.
For example: C:\HP-SHR\
Note: To install the rpm files for Linux, run the following command on the command line console:
rpm -ivh
<file name>
Content Pack | Files |
---|---|
To install the Content pack, install the packages in the given sequence. | |
SAP HANA |
|
SAP |
|
Hadoop |
|
Vertica |
|
The SHR 9.40 media presents the following add-on content that you can install anytime on the SHR server node:
Note: To install the add-on content in windows perform the following:
Go to the location where you have installed SHR.
For example: C:\HP-SHR\
Note: To install the rpm files for Linux, run the following command on the command line console:
rpm -ivh
<file name>
Content Pack | Files |
---|---|
To install the Content pack, install the packages in the given sequence. | |
SAP HANA |
|
SAP |
|
Hadoop |
|
Vertica |
|
The SHR 9.40 media presents the following add-on content that you can install anytime on the SHR server node:
Note: To install the add-on content in windows perform the following:
Go to the location where you have installed SHR.
For example: C:\HP-SHR\
Note: To install the rpm files for Linux, run the following command on the command line console:
rpm -ivh
<file name>
Content Pack | Files |
---|---|
To install the Content pack, install the packages in the given sequence. | |
SAP HANA |
|
SAP |
|
Hadoop |
|
Vertica |
|
If you are using SHR to create reports with BSM data, perform this task.
To import additional topology views delivered with SHR 9.40, follow these steps:
Note: If you have upgraded from an older version of SHR to the version 9.40, you must perform these steps before upgrading or installing any of the following Content Packs:
Collect the following BSM topology views available on the SHR system:
Content | View File Name | Location on the SHR System |
---|---|---|
Oracle | SHR_DBOracle_OM.zip |
For Windows: For Linux: |
Oracle WebLogic Server | J2EEApplication_OM.zip | For Windows:%PMDB_HOME%\Packages\ApplicationServer\ETL_AppSrvrWLS_WLSSPI.ap\source\cmdb_views
For Linux: |
IBM WebSphere Application Server | J2EEApplication_OM.zip | For Windows:%PMDB_HOME%\Packages\ApplicationServer\ETL_AppSrv
rWBS_WBSSPI.ap\source\cmdb_views
For Linux: |
Microsoft SQL Server | SHR_DBMSSQL_OM.zip | For Windows:
%PMDB_HOME%\Packages\DatabaseMSSQL\ETL_DBMSSQL_DBSPI.ap\source\cmdb_views
For Linux: |
Microsoft Exchange Server | SHR_Exchange_OM.zip | For Windows:%PMDB_HOME%\Packages\ExchangeServer\ETL_Exchange_Server2007.ap\source\cmdb_views
For Linux: |
Microsoft Active Directory | SHR_ActiveDirectory_OM.zip | For Windows:%PMDB_HOME%\Packages\ActiveDirectory\ETL_AD_ADSPI.ap\source\cmdb_views
For Linux: |
System Management | SM_BSM9_Views.zip | For Windows:%PMDB_HOME%\Packages\SystemManagement\ETL_SystemManagement_PA.ap\source\cmdb_views
For Linux: |
Task: Start the Sybase IQ Database
On the Linux system, run the following commands:
cd /etc/init.d
service HP_PMDB_Platform_Sybase status
If the command output shows that the HP_PMDB_Platform_Administrator service is stopped, run the following command:
service HP_PMDB_Platform_Sybase start
Task: Configure SHR for Profile and/or Operations Database Support
Caution: Perform this task only if you want to configure RTSM as the topology source for SHR.
You can skip this task and proceed to Task 1: Launching the Administration Console section in the HP Service Health Reporter Configuration Guide if you want to configure HPOM or VMware vCenter as the topology source.
SHR supports the configuration of and data collection from multiple Profile databases that are deployed in your HP BSM/OMi environment.
In case of OMi 10 (and later versions) perform this task for Operations Database support and then configure the database.
For information to configure the Operations Database, refer Configuring the HP OMi Data Source section in the HP Service Health Reporter Configuration Guide.
However, to ensure that SHR identifies and displays all the existing Profile databases in the Administration Console, follow these steps:
Log on to the HP BSM/OMi host system through remote access.
Note: If your HP BSM/OMi setup is distributed, you can access through the gateway server as well as the data processing server. HP recommends that you use the gateway server.
Browse to the {topaz_home}\Conf
folder.
Copy the following files from the {topaz_home}\Conf
folder of the HP BSM/OMi host system to the {PMDB_HOME}\config
folder on the SHR system:
encryption.properties
seed.properties
If you have configured multiple management databases (both BSM and OMi topology), create multiple folders at {PMDB_HOME}\config
(For example: {PMDB_HOME}\config\<Mgmt_DB_hostname>
) and copy the seed.properties
and encryption.properties
files into each folder.
Note: If you are configuring the Management/Profile database under Oracle RAC, you also need to copy the file bsm-tnsnames.ora
to the {PMDB_HOME}\config
folder on the SHR system.
If you are configuring the collection against a remote collector system then ensure to copy the tnsnames.ora
file to the {PMDB_HOME}\config
folder on that remote collector system acting as polling station.
After copying the files, you need to start the HP PMDB Platform Administrator service. Perform the following steps:
In the Open field, type services.msc
. The Services window appears.
On the right pane, right-click HP_PMDB_Platform_Administrator, and then click Restart.
Type the following command at the command prompt:
service HP_PMDB_Platform_Administrator restart
After installing SHR, you must perform configuration steps to configure SHR to use data sources. For more information, see HP Service Health Reporter Configuration Guide.
Caution: Take a backup of the SHR database so that you can restore it later. If you fail to take a data back up, you risk losing it permanently. For more information, see the "Database Backup and Recovery" section in the HP Service Health Reporter Configuration Guide.
Task: Start the Sybase IQ Database
On the Linux system, run the following commands:
cd /etc/init.d
service HP_PMDB_Platform_Sybase status
If the command output shows that the HP_PMDB_Platform_Administrator service is stopped, run the following command:
service HP_PMDB_Platform_Sybase start
Task: Configure SHR for Profile and/or Operations Database Support
Caution: Perform this task only if you want to configure RTSM as the topology source for SHR.
You can skip this task and proceed to Task 1: Launching the Administration Console section in the HP Service Health Reporter Configuration Guide if you want to configure HPOM or VMware vCenter as the topology source.
SHR supports the configuration of and data collection from multiple Profile databases that are deployed in your HP BSM/OMi environment.
In case of OMi 10 (and later versions) perform this task for Operations Database support and then configure the database.
For information to configure the Operations Database, refer Configuring the HP OMi Data Source section in the HP Service Health Reporter Configuration Guide.
However, to ensure that SHR identifies and displays all the existing Profile databases in the Administration Console, follow these steps:
Log on to the HP BSM/OMi host system through remote access.
Note: If your HP BSM/OMi setup is distributed, you can access through the gateway server as well as the data processing server. HP recommends that you use the gateway server.
Browse to the {topaz_home}\Conf
folder.
Copy the following files from the {topaz_home}\Conf
folder of the HP BSM/OMi host system to the {PMDB_HOME}\config
folder on the SHR system:
encryption.properties
seed.properties
If you have configured multiple management databases (both BSM and OMi topology), create multiple folders at {PMDB_HOME}\config
(For example: {PMDB_HOME}\config\<Mgmt_DB_hostname>
) and copy the seed.properties
and encryption.properties
files into each folder.
Note: If you are configuring the Management/Profile database under Oracle RAC, you also need to copy the file bsm-tnsnames.ora
to the {PMDB_HOME}\config
folder on the SHR system.
If you are configuring the collection against a remote collector system then ensure to copy the tnsnames.ora
file to the {PMDB_HOME}\config
folder on that remote collector system acting as polling station.
After copying the files, you need to start the HP PMDB Platform Administrator service. Perform the following steps:
In the Open field, type services.msc
. The Services window appears.
On the right pane, right-click HP_PMDB_Platform_Administrator, and then click Restart.
Type the following command at the command prompt:
service HP_PMDB_Platform_Administrator restart
After installing SHR, you must perform configuration steps to configure SHR to use data sources. For more information, see HP Service Health Reporter Configuration Guide.
Caution: Take a backup of the SHR database so that you can restore it later. If you fail to take a data back up, you risk losing it permanently. For more information, see the "Database Backup and Recovery" section in the HP Service Health Reporter Configuration Guide.
You can remove individual Content Packs without removing the entire application. You can remove the SHR application by using the HP Software Installer. This process removes all installed components including the Content Packs. But, before you uninstall, consider the following:
Creating a backup of Databases
Before you start uninstalling SHR, you must create a back up of the SHR databases.
SHR provides a backup script that you must edit to fit your requirements before you begin the backup process. This script is available in the %PMDB_HOME%\scripts\Sybase folder.
To edit the backup script:
In the last parameter within the .sql script, replace location_for_backup with the location where you want to save the backup files.
dsi_pmdb_backup 'FULL',NULL,'READWRITE_FILES_ONLY',NULL,NULL,NULL,NULL,NULL,'D','location_for_backup'
For a SHR installation with a remote database, the location_for_backup denotes a valid path on the Sybase IQ database server.
The script is run through the Execute_FullBackup_Script.bat file. This batch file is available in the %PMDB_HOME%\scripts\folder.
After the script runs, a database backup is created at the specified location.
Uninstalling Content Packs
Before you uninstall SHR, you must uninstall all content packs. If you have HP Service Health Optimizer (SHO) and SHR installed on the same system, you can retain the following content packs that are required for SHO and uninstall all other SHR content packs:
Common content pack components:
Components when RTSM is the topology source:
Components when HPOM is the topology source:
Caution: Avoid uninstalling individual Content Packs at 11 P.M. This is because during uninstallation, the PMDB Platform Timer service is stopped. However, for maintenance, SHR pauses the data processing streams at 9 P.M. and restarts the streams at 11 P.M. daily. To restart a stream, the PMDB Platform Timer service must be running. If the PMDB Platform Timer service is stopped, SHR cannot resume the paused data processing streams.
Alternatively, you can manually resume the job streams or wait for the next cycle, that is, next day 11 P.M. To resume the stream, you must run the following commands:
abcAdminUtil -resume -type loadBatch
abcAdminUtil -resume -type runStep
To remove the Content Packs using the Deployment Manager from Administration Console, perform the following steps:
Launch the following URL:
http://<SHR_Server_FQDN>:21411
Type administrator in the Login Name field and click Log In to continue. The Home page opens.
Note: Ensure that the user account you use to access the Administration Console has administrator privileges.
In the Remove column, click the icon for the Content Pack component that you want to remove. The Content Pack Components Removal Summary dialog box opens.
This dialog box displays the list of Content Pack components that will be removed by the Deployment Manager. This list includes the selected Content Pack component and other dependent components.
Click OK.
You have successfully uninstalled the Content Packs.
You can remove individual Content Packs without removing the entire application. You can remove the SHR application by using the HP Software Installer. This process removes all installed components including the Content Packs. But, before you uninstall, consider the following:
Creating a backup of Databases on Linux operating system
Before you start uninstalling SHR, you must create a back up of the SHR databases.
SHR provides a backup script that you must edit to fit your requirements before you begin the backup process. This script is available in the $PMDB_HOME\scripts\Sybase.
To edit the backup script:
In the last parameter within the .sql script, replace location_for_backup with the location where you want to save the backup files.
dsi_pmdb_backup 'FULL',NULL,'READWRITE_FILES_ONLY',NULL,NULL,NULL,NULL,NULL,'D','location_for_backup'
For a SHR installation with a remote database, the location_for_backup denotes a valid path on the Sybase IQ database server.
The script is run through the Execute_FullBackup_Script.sh file. This batch file is available in the $PMDB_HOME\scripts\ directory.
After the script runs, a database backup is created at the specified location.
Uninstalling Content Packs
Before you uninstall SHR, you must uninstall all content packs. If you have HP Service Health Optimizer (SHO) and SHR installed on the same system, you can retain the following content packs that are required for SHO and uninstall all other SHR content packs:
Common content pack components:
Components when RTSM is the topology source:
Components when HPOM is the topology source:
Caution: Avoid uninstalling individual Content Packs at 11 P.M. This is because during uninstallation, the PMDB Platform Timer service is stopped. However, for maintenance, SHR pauses the data processing streams at 9 P.M. and restarts the streams at 11 P.M. daily. To restart a stream, the PMDB Platform Timer service must be running. If the PMDB Platform Timer service is stopped, SHR cannot resume the paused data processing streams.
Alternatively, you can manually resume the job streams or wait for the next cycle, that is, next day 11 P.M. To resume the stream, you must run the following commands:
abcAdminUtil -resume -type loadBatch
abcAdminUtil -resume -type runStep
To remove the Content Packs using the Deployment Manager from Administration Console, perform the following steps:
Launch the following URL:
http://<SHR_Server_FQDN>:21411
Type administrator in the Login Name field and click Log In to continue. The Home page opens.
Note: Ensure that the user account you use to access the Administration Console has administrator privileges.
In the Remove column, click the icon for the Content Pack component that you want to remove. The Content Pack Components Removal Summary dialog box opens.
This dialog box displays the list of Content Pack components that will be removed by the Deployment Manager. This list includes the selected Content Pack component and other dependent components.
Click OK.
You have successfully uninstalled the Content Packs.
To remove the entire SHR application along with all the Content Packs, you can directly uninstall the application.
Perform the following steps to remove SHR:
Skip this step if Sybase IQ is installed on a remote system. Manually stop the Sybase IQ processes.
Open Windows Task Manager, go to the Processes tab, and then end the following processes:
iqsrv15.exe
dbisql.exe
Start the HP Software Installer:
Click Start > Programs > SHR > Uninstall.
Select the language that you prefer, and click OK.
The HP Software Installer opens.
HP Software Installer checks the system for any applications or services that might affect the uninstallation process such as anti-virus software. If HP Software Installer detects a problem, a warning or error is generated, and the Application requirements check warnings window opens.
Click Continue. The Application Maintenance page opens.
Under Maintenance Selection, select Uninstall and click Next. The Pre-Uninstall Summary page opens.
Note: SHR does not support the Repair option displayed in the HP 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 SHR on the same system.
You can search for the directory on the system that contains the SHR database files, and manually delete the directory. You can also delete the entire SHR installation directory.
Perform the following steps if you have installed the Sybase IQ server on a remote system:
Caution: Before performing the remote Sybase IQ uninstallation steps, you must first remove SHR from the host system. This ensures that the remote database schema is removed after the Sybase IQ uninstallation.
Manually stop the Sybase IQ processes.
Open Windows Task Manager, go to the Processes tab, and ensure that the following processes are killed:
iqsrv15.exe
dbisql.exe
%PMDB_HOME%\bin
folder.Run the following command:
%PMDB_HOME%\bin\SybaseServiceCreation.bat –remove
<INSTALLDIR>
In this instance, <INSTALLDIR> is the parent directory of the Sybase IQ installation directory. It is the same path that you chose for product installation in the install wizard.
For Example: %PMDB_HOME%\bin\SybaseServiceCreation.bat –remove
C:\HP-SHR\
The HP Software Installer opens.
HP Software Installer checks the system for any applications or services that might affect the uninstallation process such as anti-virus software. If HP Software Installer detects a problem, a warning or error is generated, and the Application requirements check warnings window opens.
Under Maintenance Selection, make sure that Uninstall is selected and then click Next. The Pre-Uninstall Summary page opens.
After the uninstallation is completed, the Delete dialog box appears.
You successfully uninstalled the Sybase IQ server from your remote system.
If your Service Health 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 Service Health Reporter installation before proceeding with a new installation:
Task 1: Stop all SHR services
services.msc
in the Open field, and then press ENTER. The Services window opens.Right-click the following services and select Stop to stop the service:
Caution: If you have Sybase IQ installed on a remote system, you must stop the Sybase IQ Agent 15.4 service on the remote system.
Task 2: Remove SAP BusinessObjects and PostgreSQL
Click Add or Remove Programs in the Control Panel window.
In the Add or Remove Programs dialog box, click the following items (one at a time), and then click Change/Remove to uninstall SAP BusinessObjects Enterprise:
SAP BusinessObjects Enterprise XI 3.1 SP7
Task 3: Remove Sybase IQ
Open Windows Task Manager, go to the Processes tab, and then end the following processes:
iqsrv15.exe
iqsrv15.exe
Once all the above tasks are performed, restart your system.
Task 4: Remove Windows Registry entries
Perform this task only if no other HP products are installed on your system.
regedit
and press ENTER. The Registry Editor window opens.Task 5: Remove the SHR components
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 HP OpenView.
Task 6: Remove specific environment variables
Delete the following variables:
Task 7: Remove the Service Health Reporter Folders
Delete all the folders.
Once all the above tasks are performed, restart your system.
To remove the collector application, follow these steps:
Start the HP 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 HP Software Installer opens.
On the HP Software Installer language selection page, select the required language and then click OK.
HP Software Installer checks the system for any applications or services that might hinder the uninstallation process such as anti-virus software. If HP Software Installer detects a hindrance, a warning or error is generated, and the Application requirements check warnings window opens.
Under Maintenance Selection, make sure that Uninstall is selected, and then click Next. The Pre-Uninstall Summary page opens.
Note: SHR does not support the Repair option displayed in the HP 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 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 HP Software products are installed on the system.
You can also delete the /opt/OV
directory if no other HP Software products are installed on the system.
After uninstalling the collector, you must clean up the SHR system to remove the traces of collection configuration data. To clean up the SHR system, follow these steps:
For each definition that is set up with the collector that you uninstalled, follow these steps:
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:
rollback-utility.bat
<SHR INSTALL PATH>
For Example: rollback-utility.bat C:\HP-SHR
Ensure that you do not include \
after C:\HP-SHR
.
Perform the following steps if you have installed the Sybase IQ server on a remote system:
Caution: Before performing the remote Sybase IQ uninstallation steps, you must first remove Service Health Reporter from the host system. This ensures that the remote database schema is removed after the Sybase IQ uninstallation.
Manually stop the Sybase IQ processes.
Run the following commands:
ps -ef|grep iqsrv15
ps -ef | grep dbisql
Run the following commands:
kill -9
<pid_1>
kill -9
<pid_2>
In this instance, <pid_1> and <pid_2> are the process IDs that you noted down in step b.
To uninstall SHR 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 uninstallation, some files may remain on the system. The residual files do not impact reinstallation of SHR on the same system.
Restart your system. You successfully uninstalled the Sybase IQ server from your remote system.
If your Service Health 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 Service Health Reporter installation before proceeding with a new installation:
Task 1: Stop all Service Health Reporter services
Type the following commands at the command line console:
cd /etc/init.d
service HP_PMDB_Platform_Administrator stop
service HP_PMDB_Platform_Collection stop
service HP_PMDB_Platform_DB_Logger stop
service HP_PMDB_Platform_IM stop
service HP_PMDB_Platform_PostgreSQL stop
service HP_PMDB_Platform_Sybase stop
service TrendTimer 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/BobjEnterprise120
find / -name "*BobjEnterprise*" -exec rm -f {} \;
rm -rf /tmp/.SQLAnywhere
rm -rf /root/.sqlanywhere12
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 Sybase IQ
To remove Sybase IQ, in the command line console run the following commands:
/opt/HP/BSM/Sybase/sybuninstall/IQSuite/uninstall -i silent
/opt/HP/BSM/Sybase/sybuninstall/IQClientSuite/uninstall -i silent
rm -rf /opt/HP/BSM/Sybase
chkconfig --del HP_PMDB_Platform_Sybase
rm -f /etc/init.d/HP_PMDB_Platform_Sybase
Task 4: Remove the Service Health Reporter 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
HPSHRWBLMPEtl
HPSHRADApp
HPSHRCDE
HPSHRADCore
HPSHREtlBpmOMi
HPSHREtlvmSiSAPI
HPSHRSM
HPPmdbLicAP
HPSHRWBSApp
HPPmdbTomcat
HPPmdbAdmin
HPSHROMi10Etl
HPSHREumCore
HPSHROM
HPSHRExchEtl13
HPSHRNwCore
HPSHRSmEtlPa
HPSHROraDBETL
HPSHRExchEtl10
HPSHRSmVVm
HPPmdbABC
HPOvSecCS
HPSHRCoreWBS
HPSHROMi10ExtEtl
HPSHRSmEtlVvmPa
HPPmdbCore
HPPmdbCollector
HPOvJPacc
HPSHRCoreAppS
HPPmdbSybIQPKG2
HPSHRCoreSHlth
HPSHRCoreOMi
HPOvSecCC
HPSHREumBpm
HPSHREtlSHlth10
HPSHREumEtlBpm
HPSHRExchEtl07
HPSHRWBSMPEtl
HPSHRSmEtlVHyPa
HPOvJbbc
HPOvJsec
HPSHRExchApp
HPSHROmEtl
HPSHROraDBApp
HPPmdbPostgreSQL
HPSHRCPHelp
HPPmdbBORebrand
HPPmdbBOTomcat
HPSHRMSSqlEtl
HPSHRSmCore
HPSHRCoreWLS
HPSHRWLSEtl
HPSHRSmEtlSisDB
HPSHRSmEtlVLprPa
HPSHREtlRumOMi
HPSHROMiExt
HPSHRSmV
HPSHROMiExtEtl
HPSHRMSSqlCore
HPOvJxpl
HPPmdbSybIQSP08
HPSHRSmEtlVVmVc
HPSHRCoreCP
HPSHREumRum
HPSHREumEtlRum
HPPmdbSybaseIQ
HPPmdbCommon
HPOvPerlA
HPPmdbPerl
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 Service Health Reporter Folders
To remove the SHR folders, run the command:
rm -rf /opt/HP/BSM
If no other HP 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 Service Health Reporter.
To uninstall SHR 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 uninstallation, some files may remain on the system. The residual files do not impact reinstallation of SHR on the same system.
You can search for the directory on the system that contains the SHR 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 HP Software products are installed on the system.
To remove the collector application, follow these steps:
Start the HP Software Installer.
Go to /opt/OV/Uninstall/HP-SHR-RemotePoller
and run the setup.bin
file.
Press Enter to start the installation.
Click Enter to continue.
HP Software Installer checks the system for any applications or services that might hinder the uninstallation process such as anti-virus software. If HP Software Installer detects a hindrance, a warning or error is generated, and the Application requirements check warnings window opens.
Under Maintenance Selection, ensure that Uninstall option is selected, and then click Enter. The Pre-Uninstall Summary appears.
Note: SHR does not support the Repair option displayed in the HP 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 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 HP Software products are installed on the system.
After uninstalling the collector, you must clean up the SHR system to remove the traces of collection configuration data. To clean up the SHR system, follow these steps:
For each definition that is set up with the collector that you uninstalled, follow these steps:
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
SHR is installed with a default SAP BusinessObjects database password. Perform this task to change the default SAP BusinessObjects database password.
After installing SHR, follow these steps to modify the default password of the database embedded with SAP BusinessObjects:
<BusinessObejcts installed drive>:\Program Files (x86)\Business Objects\SQLAnyWhere12\bin
dbisqlc
application.Type the credentials as follows:
User name = DBA.
Password = pmdb_admin.
Server name = BOE120SQLAW_<shrshorthostname>.
Database name = BOE120.
Run the following command in the sql window:
ALTER USER <shrshorthostname> IDENTIFIED BY <new password>;
ALTER USER DBA IDENTIFIED BY <new password>;
After updating the password, follow these steps:
To check if the password is modified, log in to the database using the new password.
SHR is installed with a default SAP BusinessObjects database password. Perform this task to change the default SAP BusinessObjects database password.
After installing SHR, follow these steps to modify the default password of the database embedded with SAP BusinessObjects:
Run the following command to switch to SHRBOADMIN user:
su - SHRBOADMIN
/opt/HP/BSM/BO/bobje/SQLAW/Bin/
.Run the following command:
source /opt/HP/BSM/BO/bobje/setup/env.sh
Run the following command:
./dbisqlc
The credentials window appears. Click Cancel.
Type the following details:
Run the following command in the sql window:
ALTER USER SHR IDENTIFIED BY <new password>;
ALTER USER DBA IDENTIFIED BY <new password>;
To modify the default password for BOE120_AUDIT, from Menu, click Command tab, and then click Connect....
Type the following details:
Run the following command in the sql window:
ALTER USER SHR IDENTIFIED BY <new password>;
ALTER USER DBA IDENTIFIED BY <new password>;
After updating the password, follow these steps:
For BOE120 perform the following:
/opt/HP/BSM/BO/bobje
.Run the following command:
./cmsdbsetup.sh
Run the following command:
./startservers
For BOE120_AUDIT perform the following:
/opt/HP/BSM/BO/bobje
.Run the following command:
./cmsdbsetup.sh
If you want to enable the Audit option Type yes in the command line.
You can type No if you do not want to enable Audit now and want to enable the Audit at a later point of time.
Run the following command:
./startservers
To check if the password is modified, log in to the database using the new password.
The new password must be updated in the BobjEnterprise120 script that contains the default password. Perform the following steps:
/etc/init.d
Go to the following line:
$SU - "$BOBJEUSERNAME" -c "$BOBJEDIR/sawstop.sh DATABASEUID=SHR DATABASEPWD=pmdb_admin"
pmdb_admin
.SHR is installed with a default SAP BusinessObjects database password. Perform this task to change the default SAP BusinessObjects database password.
After installing SHR, follow these steps to modify the default password of the database embedded with SAP BusinessObjects:
<BusinessObejcts installed drive>:\Program Files (x86)\Business Objects\SQLAnyWhere12\bin
dbisqlc
application.Type the credentials as follows:
User name = DBA.
Password = pmdb_admin.
Server name = BOE120SQLAW_<shrshorthostname>.
Database name = BOE120.
Run the following command in the sql window:
ALTER USER <shrshorthostname> IDENTIFIED BY <new password>;
ALTER USER DBA IDENTIFIED BY <new password>;
After updating the password, follow these steps:
To check if the password is modified, log in to the database using the new password.
SHR is installed with a default SAP BusinessObjects database password. Perform this task to change the default SAP BusinessObjects database password.
After installing SHR, follow these steps to modify the default password of the database embedded with SAP BusinessObjects:
Run the following command to switch to SHRBOADMIN user:
su - SHRBOADMIN
/opt/HP/BSM/BO/bobje/SQLAW/Bin/
.Run the following command:
source /opt/HP/BSM/BO/bobje/setup/env.sh
Run the following command:
./dbisqlc
The credentials window appears. Click Cancel.
Type the following details:
Run the following command in the sql window:
ALTER USER SHR IDENTIFIED BY <new password>;
ALTER USER DBA IDENTIFIED BY <new password>;
To modify the default password for BOE120_AUDIT, from Menu, click Command tab, and then click Connect....
Type the following details:
Run the following command in the sql window:
ALTER USER SHR IDENTIFIED BY <new password>;
ALTER USER DBA IDENTIFIED BY <new password>;
After updating the password, follow these steps:
For BOE120 perform the following:
/opt/HP/BSM/BO/bobje
.Run the following command:
./cmsdbsetup.sh
Run the following command:
./startservers
For BOE120_AUDIT perform the following:
/opt/HP/BSM/BO/bobje
.Run the following command:
./cmsdbsetup.sh
If you want to enable the Audit option Type yes in the command line.
You can type No if you do not want to enable Audit now and want to enable the Audit at a later point of time.
Run the following command:
./startservers
To check if the password is modified, log in to the database using the new password.
The new password must be updated in the BobjEnterprise120 script that contains the default password. Perform the following steps:
/etc/init.d
Go to the following line:
$SU - "$BOBJEUSERNAME" -c "$BOBJEDIR/sawstop.sh DATABASEUID=SHR DATABASEPWD=pmdb_admin"
pmdb_admin
.SHR is installed with a default SAP BusinessObjects database password. Perform this task to change the default SAP BusinessObjects database password.
After installing SHR, follow these steps to modify the default password of the database embedded with SAP BusinessObjects:
<BusinessObejcts installed drive>:\Program Files (x86)\Business Objects\SQLAnyWhere12\bin
dbisqlc
application.Type the credentials as follows:
User name = DBA.
Password = pmdb_admin.
Server name = BOE120SQLAW_<shrshorthostname>.
Database name = BOE120.
Run the following command in the sql window:
ALTER USER <shrshorthostname> IDENTIFIED BY <new password>;
ALTER USER DBA IDENTIFIED BY <new password>;
After updating the password, follow these steps:
To check if the password is modified, log in to the database using the new password.
SHR is installed with a default SAP BusinessObjects database password. Perform this task to change the default SAP BusinessObjects database password.
After installing SHR, follow these steps to modify the default password of the database embedded with SAP BusinessObjects:
Run the following command to switch to SHRBOADMIN user:
su - SHRBOADMIN
/opt/HP/BSM/BO/bobje/SQLAW/Bin/
.Run the following command:
source /opt/HP/BSM/BO/bobje/setup/env.sh
Run the following command:
./dbisqlc
The credentials window appears. Click Cancel.
Type the following details:
Run the following command in the sql window:
ALTER USER SHR IDENTIFIED BY <new password>;
ALTER USER DBA IDENTIFIED BY <new password>;
To modify the default password for BOE120_AUDIT, from Menu, click Command tab, and then click Connect....
Type the following details:
Run the following command in the sql window:
ALTER USER SHR IDENTIFIED BY <new password>;
ALTER USER DBA IDENTIFIED BY <new password>;
After updating the password, follow these steps:
For BOE120 perform the following:
/opt/HP/BSM/BO/bobje
.Run the following command:
./cmsdbsetup.sh
Run the following command:
./startservers
For BOE120_AUDIT perform the following:
/opt/HP/BSM/BO/bobje
.Run the following command:
./cmsdbsetup.sh
If you want to enable the Audit option Type yes in the command line.
You can type No if you do not want to enable Audit now and want to enable the Audit at a later point of time.
Run the following command:
./startservers
To check if the password is modified, log in to the database using the new password.
The new password must be updated in the BobjEnterprise120 script that contains the default password. Perform the following steps:
/etc/init.d
Go to the following line:
$SU - "$BOBJEUSERNAME" -c "$BOBJEDIR/sawstop.sh DATABASEUID=SHR DATABASEPWD=pmdb_admin"
pmdb_admin
.Appendix A
Install SHR when /opt
does not have enough space
Note: SHR 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 SHR by mounting free disk in /opt
as /opt/HP
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 SHR media (the .tar
file) are extracted.
At the command prompt, type the following command:
./HP-SHR_9.40_setup.bin -i console
Press Enter to start the installation. The Choose Locale section appears.
Tip: At any point during installation, type back
to go to the previous page and type quit
to cancel the installation.
Review the license agreement details. Type Y to accept the agreement, and then press Enter.
/tmp/HP-SHR
. Edit the script checkSpace.sh
and add exit 0
at the beginning of the script. Close the console.Appendix B
Install SHR as non-root user
Follow these steps to install as a non-root user:
useradd
to create a user.Update the sudoers
file and provide all permission to the newly created user using the following command:
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
Start the installation using the following command:
$ sudo ./HP-SHR_9.40_setup.bin -i console
Continue with the installation steps. For the installation steps, see the Installation section in this guide.
Appendix C
Configure SHR application users group privileges for non-root group (non-zero id).
Go to the media root.
Media root is the directory where the contents of the SHR media (the .tar
file) are extracted.
At the command prompt, type the following command:
./HP-SHR_9.40_setup.bin -i console
Press Enter to start the installation. The Choose Locale section appears.
Tip: At any point during installation, type back
to go to the previous page and type quit
to cancel the installation.
Review the license agreement details. Type Y to accept the agreement, and then press Enter.
Open a new command line console and go to the directory /tmp/HP-SHR
. Edit the script BOInstall.sh
and comment out the following lines.
if [ $(id -u) -eq 0 ]; then
usermod -g root SHRBOADMIN
else
echo "Only root may add a user to the system">>$BOInstallLog
exit 2
fi
Close this console.
This section is applicable only to Sybase IQ on Linux Operating System.
Appendix A
Install SHR when /opt
does not have enough space
Note: SHR 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 SHR by mounting free disk in /opt
as /opt/HP
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 SHR media (the .tar
file) are extracted.
At the command prompt, type the following command:
./HP-SHR_9.40_setup.bin -i console
Press Enter to start the installation. The Choose Locale section appears.
Tip: At any point during installation, type back
to go to the previous page and type quit
to cancel the installation.
Review the license agreement details. Type Y to accept the agreement, and then press Enter.
/tmp/HP-SHR
. Edit the script checkSpace.sh
and add exit 0
at the beginning of the script. Close the console.Appendix B
Install SHR as non-root user
Follow these steps to install as a non-root user:
useradd
to create a user.Update the sudoers
file and provide all permission to the newly created user using the following command:
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
Start the installation using the following command:
$ sudo ./HP-SHR_9.40_setup.bin -i console
Continue with the installation steps. For the installation steps, see the Installation section in this guide.
Appendix C
Configure SHR application users group privileges for non-root group (non-zero id).
Go to the media root.
Media root is the directory where the contents of the SHR media (the .tar
file) are extracted.
At the command prompt, type the following command:
./HP-SHR_9.40_setup.bin -i console
Press Enter to start the installation. The Choose Locale section appears.
Tip: At any point during installation, type back
to go to the previous page and type quit
to cancel the installation.
Review the license agreement details. Type Y to accept the agreement, and then press Enter.
Open a new command line console and go to the directory /tmp/HP-SHR
. Edit the script BOInstall.sh
and comment out the following lines.
if [ $(id -u) -eq 0 ]; then
usermod -g root SHRBOADMIN
else
echo "Only root may add a user to the system">>$BOInstallLog
exit 2
fi
Close this console.
Symptom: Installation Failure caused by SAP BusinessObjects Error
Description: While running the HP Software installer, the installation fails and the following error message is displayed:
SAP BusinessObjects is installed on the system. Please uninstall it before installing HP SH Reporter.
Resolution: If you have any component of SHR (such as SAP BusinessObjects or Sybase IQ) preinstalled or not cleanly uninstalled from a previous uninstall on your system, the SHR installation will fail because the installer tries to install the components that are bundled with the product.
To resolve this problem, you must clean up the existing components from the system and rerun the installer. For a virtual system, consider reimaging the VM, if feasible.
Symptom: Installation Failure caused by SAP BusinessObjects Error
Description: While running the HP Software installer, the installation fails and the following error message is displayed:
SAP BusinessObjects is installed on the system. Please uninstall it before installing HP SH Reporter.
Resolution: If you have any component of SHR (such as SAP BusinessObjects or Sybase IQ) preinstalled or not cleanly uninstalled from a previous uninstall on your system, the SHR installation will fail because the installer tries to install the components that are bundled with the product.
To resolve this problem, you must clean up the existing components from the system and rerun the installer. For a virtual system, consider reimaging the VM, if feasible.
Symptom: Installation failure due to missing libraries
Description: While installing SHR, if there any missing libraries the installation pre-check will fail.
Resolution: To resolve this problem, perform the following steps:
/tmp/SHR-Missing-Patches.txt
get the list of missing libraries.For more information, see the "Installation Prerequisites" section in this document.
Symptom: Installation failure due to missing libraries
Description: While installing SHR, if there any missing libraries the installation pre-check will fail.
Resolution: To resolve this problem, perform the following steps:
/tmp/SHR-Missing-Patches.txt
get the list of missing libraries.For more information, see the "Installation Prerequisites" section in this document.
Symptom: Unable to Bring up SHR Services after Successful Installation
Description: If SHR is installed on a virtual machine that is not restarted after the installation, the environment variables set by the installer will not be available to the user resulting in SHR services not coming up in spite of multiple retry.
Resolution: After installing SHR, ensure that you restart the virtual machine.
Symptom: Unable to Bring up SHR Services after Successful Installation
Description: If SHR is installed on a virtual machine that is not restarted after the installation, the environment variables set by the installer will not be available to the user resulting in SHR services not coming up in spite of multiple retry.
Resolution: After installing SHR, ensure that you restart the virtual machine.
Symptom: Remote Sybase IQ Database Creation Fails
In the HP Service Health Reporter Configuration Wizard, while trying to create the Sybase database file on a remote system, the post-install fails and the following error message is displayed:
<time stamp>,018 ERROR, com.hp.bto.bsmr.dao.helper.CreateSybaseIQDatabase.executeSQL, Could not connect to the database.
<time stamp>,049 ERROR, com.hp.bto.bsmr.dao.helper.CreateSybaseIQDatabase.executeSQL , Specified database not found
Resolution 1: This error occurs if the database file location specified in the HP Service Health Reporter Configuration Wizard includes one or more spaces in the file path. To resolve this problem, make sure that the specified database file location exists on the remote system. In addition, make sure that the path provided in the Post-Install wizard does not contain any spaces.
Resolution 2: This error can occur when adequate disk space is not available on the drive. The installer does not warn in case of a remote database. Increasing the disk space should resolve the issue.
Symptom: Sybase IQ Hangs
Description:SHR servers that have four or less CPUs, Sybase IQ hangs because of low iqgovern
parameter value that is computed automatically.
Resolution:
Windows: Add "-iqgovern 50
" parameter to the %PMDB_HOME%\config\pmdbConfig.cfg
file and restart the Sybase IQ database.
Linux: Add "-iqgovern 50
" parameter to the $PMDB_HOME/config/pmdbConfig.cfg
file and restart the Sybase IQ database.
Symptom: Sybase IQ Hangs
Description:SHR servers that have four or less CPUs, Sybase IQ hangs because of low iqgovern
parameter value that is computed automatically.
Resolution:
Windows: Add "-iqgovern 50
" parameter to the %PMDB_HOME%\config\pmdbConfig.cfg
file and restart the Sybase IQ database.
Linux: Add "-iqgovern 50
" parameter to the $PMDB_HOME/config/pmdbConfig.cfg
file and restart the Sybase IQ database.
Symptom: SHR Fails to Create the Sybase Schema
Description: If SHR fails to create the Sybase schema after you complete the post-installation configuration tasks, an error message appears in the database log files. The Sybase database log files—<hostname>.0001.srvlog
and <hostname>.0001.stderr—
are present in the /opt/HP/BSM/Sybase/IQ-16_0/logfiles
directory on Linux.
The following error message appears in the Sybase database log files:
“utility_db" (utility_db) stopped
Only the Sybase database log files show the error message; no error messages appear in the Administration console.
Resolution: Restart the Sybase service by running the following command:
service HP_PMDB_Platform_Sybase stop
service HP_PMDB_Platform_Sybase start
Symptom: SHR Fails to Create the Sybase Schema
Description: If SHR fails to create the Sybase schema after you complete the post-installation configuration tasks, an error message appears in the database log files. The Sybase database log files—<hostname>.0001.srvlog
and <hostname>.0001.stderr—
are present in the /opt/HP/BSM/Sybase/IQ-16_0/logfiles
directory on Linux.
The following error message appears in the Sybase database log files:
“utility_db" (utility_db) stopped
Only the Sybase database log files show the error message; no error messages appear in the Administration console.
Resolution: Restart the Sybase service by running the following command:
service HP_PMDB_Platform_Sybase stop
service HP_PMDB_Platform_Sybase start
Symptom: After Installation, User is Unable to Perform Post-Install Steps
Description: After installation, when user clicks Next, the subsequent page does not load despite enabling Java scripts to run.
Resolution: This occurs when the system date on which SHR is installed is much older than that of the ESX (in case of a VM). In such a scenario, the Tomcat server does not allow any requests from the client. Hence, it is always advisable to update the system date to current and install.
Perform the following steps:
Apply the permanent license.
When the system date is changed by more than three months, the license expires.
Symptom: After Installation, User is Unable to Perform Post-Install Steps
Description: After installation, when user clicks Next, the subsequent page does not load despite enabling Java scripts to run.
Resolution: This occurs when the system date on which SHR is installed is much older than that of the ESX (in case of a VM). In such a scenario, the Tomcat server does not allow any requests from the client. Hence, it is always advisable to update the system date to current and install.
Perform the following steps:
Apply the permanent license.
When the system date is changed by more than three months, the license expires.
Symptom: SHR Uninstall Fails
Description: Uninstalling SHR might not have completely uninstalled Sybase IQ Server.
Resolution: Uninstall Sybase IQ Server Suite 15.4 (64-bit) manually and restart your system.
Symptom: After Uninstalling SHR, Reinstall Fails
Description: After uninstalling SHR on a Windows system, when a reinstall is performed, the installer fails to launch and displays a Scripting Host not Found
error.
Resolution: This error is encountered when the Path environment variable in Windows is corrupted. Add the %systemroot%\System32
string to the Path environment variable by performing the following steps:
%systemroot%\System32
if missing.Symptom: After Uninstalling SHR, Reinstall Fails
Description: After uninstalling SHR on a Windows system, when a reinstall is performed, the installer fails to launch and displays a Scripting Host not Found
error.
Resolution: This error is encountered when the Path environment variable in Windows is corrupted. Add the %systemroot%\System32
string to the Path environment variable by performing the following steps:
%systemroot%\System32
if missing.Symptom: After interrupted installation, unable to continue reinstall with the installed components
Description: This issue may occur when you accidentally quit the SHR installation wizard and later continue to reinstall with the existing components.
Resolution: Perform the following steps to resolve this problem:
Symptom: After interrupted installation, unable to continue reinstall with the installed components
Description: This issue may occur when you accidentally quit the SHR installation wizard and later continue to reinstall with the existing components.
Resolution: Perform the following steps to resolve this problem:
Symptom: Data Collection Failure across all Configured Nodes
Description: Data collection in SHR fails with an Address already in use error logged in the topologycollector.log
file.
Resolution: This error occurs when the number of TCP/IP ports used exceeds the default value of 5000. To resolve this problem, you must make changes in the Windows Registry. Follow these steps:
In the Open box, type regedit
. The Registry Editor window appears.
On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.
On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:
MaxFreeTcbs = 65535 (decimal)
TcpTimedWaitDelay = 30 (decimal)
Restart the system after making changes in the Registry Editor.
Symptom: Data Collection Failure across all Configured Nodes
Description: Data collection in SHR fails with an Address already in use error logged in the topologycollector.log
file.
Resolution: This error occurs when the number of TCP/IP ports used exceeds the default value of 5000. To resolve this problem, you must make changes in the Windows Registry. Follow these steps:
In the Open box, type regedit
. The Registry Editor window appears.
On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.
On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:
MaxFreeTcbs = 65535 (decimal)
TcpTimedWaitDelay = 30 (decimal)
Restart the system after making changes in the Registry Editor.
Symptom: After uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector.
Description: If you uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector and error messages appear when you try to configure the collector in the Administration Console.
You can occasionally experience this issue even after installing the collector for the first time.
Resolution: To resolve this, manually import the certificate from the SHR system to the collector system by following these steps:
Log on to the collector system.
Run the following command:
ovcoreid
Note down the ID displayed in the console.
Log on to the SHR system.
Run the following command:
ovcm -issue -file <file> -name
<node name>-coreid
<core_ID>
In this instance, <core_ID> is the ID that you noted down in step 2.
The command prompts for a password. If you do not want to use a password, press Enter without typing anything.
In this instance, <file> is the name of the certificate file that you want to manually import to the collector system; you must specify the file name with complete path to the directory where you want to store the file. <node name> is the FQDN of the collector system.
Transfer the certificate file to the collector system.
Run the following command:
ovcert -importcert -file
<file>
Symptom: After uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector.
Description: If you uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector and error messages appear when you try to configure the collector in the Administration Console.
You can occasionally experience this issue even after installing the collector for the first time.
Resolution: To resolve this, manually import the certificate from the SHR system to the collector system by following these steps:
Log on to the collector system.
Run the following command:
ovcoreid
Note down the ID displayed in the console.
Log on to the SHR system.
Run the following command:
ovcm -issue -file <file> -name
<node name>-coreid
<core_ID>
In this instance, <core_ID> is the ID that you noted down in step 2.
The command prompts for a password. If you do not want to use a password, press Enter without typing anything.
In this instance, <file> is the name of the certificate file that you want to manually import to the collector system; you must specify the file name with complete path to the directory where you want to store the file. <node name> is the FQDN of the collector system.
Transfer the certificate file to the collector system.
Run the following command:
ovcert -importcert -file
<file>
Symptom: Installation fails for Management database package while installing as Domain user
Description:SHR installation fails with domain user during HPPmdbPostgreSQL package installation with the following error in the install log.
C:/HP-SHR/Postgres/data ... initdb: could not change permissions of directory "C:/HP-SHR/Postgres/data": Permission denied in %temp%\install-postgresql.log (or) %temp%\bitrock_installer.log
Resolution: Uninstall SHR and create a local user that is a member of the Local Administrators group with administrator rights and install SHR again.
Symptom: Installation fails for Management database package while installing as Domain user
Description:SHR installation fails with domain user during HPPmdbPostgreSQL package installation with the following error in the install log.
C:/HP-SHR/Postgres/data ... initdb: could not change permissions of directory "C:/HP-SHR/Postgres/data": Permission denied in %temp%\install-postgresql.log (or) %temp%\bitrock_installer.log
Resolution: Uninstall SHR and create a local user that is a member of the Local Administrators group with administrator rights and install SHR again.
Symptom: Installer fails to display that installation is complete.
Description: This issue may appear while performing SHR installation, upgrade or installing Remote Collectors. The installer progress bar shows that the installation is in process but the Done button is enabled. This is because the installer is not refreshed.
Resolution: Click Done to complete the process and check the install log files as follows to see if all the components are installed.
%temp%/../HP-SHR_9.40_HPOvInstaller.txt
/tmp/HP-SHR_9.40_HPOvInstaller.txt
Symptom: Installer fails to display that installation is complete.
Description: This issue may appear while performing SHR installation, upgrade or installing Remote Collectors. The installer progress bar shows that the installation is in process but the Done button is enabled. This is because the installer is not refreshed.
Resolution: Click Done to complete the process and check the install log files as follows to see if all the components are installed.
%temp%/../HP-SHR_9.40_HPOvInstaller.txt
/tmp/HP-SHR_9.40_HPOvInstaller.txt
Symptom: Installer fails to display that installation is complete.
Description: This issue may appear while performing SHR installation, upgrade or installing Remote Collectors. The installer progress bar shows that the installation is in process but the Done button is enabled. This is because the installer is not refreshed.
Resolution: Click Done to complete the process and check the install log files as follows to see if all the components are installed.
%temp%/../HP-SHR_9.40_HPOvInstaller.txt
/tmp/HP-SHR_9.40_HPOvInstaller.txt
Symptom: Sybase IQ database removal failed after uninstall.
Description: This issue occurs while performing uninstall of SHR. The Sybase IQ database is not removed properly, you will see a pop up as follows:
"Initialize action for HP Service Health Reporter 9.40 (Removing Sybase IQ schema) was not successful."
Resolution: You can move ahead with the uninstall and run the rollback utility. For the steps, see "Post Uninstalling SHR" section in this guide.
Symptom: Uninstall is not clean.
Description: This issue occurs while performing uninstall of SHR, you will see a pop up saying there is a failure as follows:
"Initialize action for package HPPmdbCollector 9.40.000 (HP PMDB Collector) (Performing Collection housekeeping) was not successful."
Resolution: You can ignore the pop up and move ahead with the uninstall and run the rollback utility. For the steps, see "Post Uninstalling SHR" section in this guide.
Symptom: Failure in upgrade command.
Description: This issue may occur after upgrade of SHR, you will see a message saying there is a failure in the upgrade command.
Resolution: From the command line console run the following script:
%Ovinstalldir%\nonOV\perl\a\bin\perl %PMDB_HOME%\upgrade\940\applyPatch.pl %PMDB_HOME%\..\ “%ovinstalldir%” %PMDB_HOME%\upgrade\940
/opt/OV/nonOV/perl/a/bin/perl /opt/HP/BSM/PMDB/upgrade/940/applyPatch.pl /opt/HP/BSM/ /opt/OV/ /opt/HP/BSM/PMDB/upgrade/940/
Symptom: Failure in service precheck while upgrade.
Description: While upgrade, if all the SHR services are not stopped this issue may occur.
Resolution: From the PMDB_HOME\temp
folder check the UpgradeServiceCheck.log
file to find the cause of failure.
Symptom: After upgrade, few links in the Administration Console may fail to work.
Description: After upgrade, the CMC and InfoView links may fail to work SHR Administration Console. This issue may occur if the SAP BusinessObjects services are not running.
Resolution: Perform the following steps to stop the SAP BusinessObjects services:
Start the Business Objects Webserver Service
Run the following command to start the webserver:
sh /opt/HP/BSM/BO/bobje/tomcatstartup.sh
Symptom: Installation with username having special character "&" requires system startup.
Description: While installing SHR with username having special character &
then the system requests for startup.
Resolution: Click Continue and proceed with your installation.
Symptom: Installation with username having special character "&" requires system startup.
Description: While installing SHR with username having special character &
then the system requests for startup.
Resolution: Click Continue and proceed with your installation.
Symptom: After Uninstall, reinstall hangs on RHEL 5.5.
Description: After uninstall, when you reinstall SHR on Linux RHEL 5.5, the system hangs while installing BusinessObjects.
Resolution: Ensure that you perform SHR installation on a new Linux RHEL 5.5 system.
Symptom: YUM check warning after SHR installation
Description: After installing SHR and meeting all the pre-requisites, the following message appears with a list of missing libraries:
Found 42 pre-existing rpmdb problem(s), 'yum check' output follows:
Resolution: If you get a list of missing libraries while performing the YUM check, you can ignore these libraries as they are not mandatory for SHR. This does not affect the functionality of SHR.
Symptom: Installation Failure caused by SAP BusinessObjects Error
Description: While running the HP Software installer, the installation fails and the following error message is displayed:
SAP BusinessObjects is installed on the system. Please uninstall it before installing HP SH Reporter.
Resolution: If you have any component of SHR (such as SAP BusinessObjects or Sybase IQ) preinstalled or not cleanly uninstalled from a previous uninstall on your system, the SHR installation will fail because the installer tries to install the components that are bundled with the product.
To resolve this problem, you must clean up the existing components from the system and rerun the installer. For a virtual system, consider reimaging the VM, if feasible.
Symptom: Installation Failure caused by SAP BusinessObjects Error
Description: While running the HP Software installer, the installation fails and the following error message is displayed:
SAP BusinessObjects is installed on the system. Please uninstall it before installing HP SH Reporter.
Resolution: If you have any component of SHR (such as SAP BusinessObjects or Sybase IQ) preinstalled or not cleanly uninstalled from a previous uninstall on your system, the SHR installation will fail because the installer tries to install the components that are bundled with the product.
To resolve this problem, you must clean up the existing components from the system and rerun the installer. For a virtual system, consider reimaging the VM, if feasible.
Symptom: Installation failure due to missing libraries
Description: While installing SHR, if there any missing libraries the installation pre-check will fail.
Resolution: To resolve this problem, perform the following steps:
/tmp/SHR-Missing-Patches.txt
get the list of missing libraries.For more information, see the "Installation Prerequisites" section in this document.
Symptom: Installation failure due to missing libraries
Description: While installing SHR, if there any missing libraries the installation pre-check will fail.
Resolution: To resolve this problem, perform the following steps:
/tmp/SHR-Missing-Patches.txt
get the list of missing libraries.For more information, see the "Installation Prerequisites" section in this document.
Symptom: Unable to Bring up SHR Services after Successful Installation
Description: If SHR is installed on a virtual machine that is not restarted after the installation, the environment variables set by the installer will not be available to the user resulting in SHR services not coming up in spite of multiple retry.
Resolution: After installing SHR, ensure that you restart the virtual machine.
Symptom: Unable to Bring up SHR Services after Successful Installation
Description: If SHR is installed on a virtual machine that is not restarted after the installation, the environment variables set by the installer will not be available to the user resulting in SHR services not coming up in spite of multiple retry.
Resolution: After installing SHR, ensure that you restart the virtual machine.
Symptom: Remote Sybase IQ Database Creation Fails
In the HP Service Health Reporter Configuration Wizard, while trying to create the Sybase database file on a remote system, the post-install fails and the following error message is displayed:
<time stamp>,018 ERROR, com.hp.bto.bsmr.dao.helper.CreateSybaseIQDatabase.executeSQL, Could not connect to the database.
<time stamp>,049 ERROR, com.hp.bto.bsmr.dao.helper.CreateSybaseIQDatabase.executeSQL , Specified database not found
Resolution 1: This error occurs if the database file location specified in the HP Service Health Reporter Configuration Wizard includes one or more spaces in the file path. To resolve this problem, make sure that the specified database file location exists on the remote system. In addition, make sure that the path provided in the Post-Install wizard does not contain any spaces.
Resolution 2: This error can occur when adequate disk space is not available on the drive. The installer does not warn in case of a remote database. Increasing the disk space should resolve the issue.
Symptom: Sybase IQ Hangs
Description:SHR servers that have four or less CPUs, Sybase IQ hangs because of low iqgovern
parameter value that is computed automatically.
Resolution:
Windows: Add "-iqgovern 50
" parameter to the %PMDB_HOME%\config\pmdbConfig.cfg
file and restart the Sybase IQ database.
Linux: Add "-iqgovern 50
" parameter to the $PMDB_HOME/config/pmdbConfig.cfg
file and restart the Sybase IQ database.
Symptom: Sybase IQ Hangs
Description:SHR servers that have four or less CPUs, Sybase IQ hangs because of low iqgovern
parameter value that is computed automatically.
Resolution:
Windows: Add "-iqgovern 50
" parameter to the %PMDB_HOME%\config\pmdbConfig.cfg
file and restart the Sybase IQ database.
Linux: Add "-iqgovern 50
" parameter to the $PMDB_HOME/config/pmdbConfig.cfg
file and restart the Sybase IQ database.
Symptom: SHR Fails to Create the Sybase Schema
Description: If SHR fails to create the Sybase schema after you complete the post-installation configuration tasks, an error message appears in the database log files. The Sybase database log files—<hostname>.0001.srvlog
and <hostname>.0001.stderr—
are present in the /opt/HP/BSM/Sybase/IQ-16_0/logfiles
directory on Linux.
The following error message appears in the Sybase database log files:
“utility_db" (utility_db) stopped
Only the Sybase database log files show the error message; no error messages appear in the Administration console.
Resolution: Restart the Sybase service by running the following command:
service HP_PMDB_Platform_Sybase stop
service HP_PMDB_Platform_Sybase start
Symptom: SHR Fails to Create the Sybase Schema
Description: If SHR fails to create the Sybase schema after you complete the post-installation configuration tasks, an error message appears in the database log files. The Sybase database log files—<hostname>.0001.srvlog
and <hostname>.0001.stderr—
are present in the /opt/HP/BSM/Sybase/IQ-16_0/logfiles
directory on Linux.
The following error message appears in the Sybase database log files:
“utility_db" (utility_db) stopped
Only the Sybase database log files show the error message; no error messages appear in the Administration console.
Resolution: Restart the Sybase service by running the following command:
service HP_PMDB_Platform_Sybase stop
service HP_PMDB_Platform_Sybase start
Symptom: After Installation, User is Unable to Perform Post-Install Steps
Description: After installation, when user clicks Next, the subsequent page does not load despite enabling Java scripts to run.
Resolution: This occurs when the system date on which SHR is installed is much older than that of the ESX (in case of a VM). In such a scenario, the Tomcat server does not allow any requests from the client. Hence, it is always advisable to update the system date to current and install.
Perform the following steps:
Apply the permanent license.
When the system date is changed by more than three months, the license expires.
Symptom: After Installation, User is Unable to Perform Post-Install Steps
Description: After installation, when user clicks Next, the subsequent page does not load despite enabling Java scripts to run.
Resolution: This occurs when the system date on which SHR is installed is much older than that of the ESX (in case of a VM). In such a scenario, the Tomcat server does not allow any requests from the client. Hence, it is always advisable to update the system date to current and install.
Perform the following steps:
Apply the permanent license.
When the system date is changed by more than three months, the license expires.
Symptom: SHR Uninstall Fails
Description: Uninstalling SHR might not have completely uninstalled Sybase IQ Server.
Resolution: Uninstall Sybase IQ Server Suite 15.4 (64-bit) manually and restart your system.
Symptom: After Uninstalling SHR, Reinstall Fails
Description: After uninstalling SHR on a Windows system, when a reinstall is performed, the installer fails to launch and displays a Scripting Host not Found
error.
Resolution: This error is encountered when the Path environment variable in Windows is corrupted. Add the %systemroot%\System32
string to the Path environment variable by performing the following steps:
%systemroot%\System32
if missing.Symptom: After Uninstalling SHR, Reinstall Fails
Description: After uninstalling SHR on a Windows system, when a reinstall is performed, the installer fails to launch and displays a Scripting Host not Found
error.
Resolution: This error is encountered when the Path environment variable in Windows is corrupted. Add the %systemroot%\System32
string to the Path environment variable by performing the following steps:
%systemroot%\System32
if missing.Symptom: After interrupted installation, unable to continue reinstall with the installed components
Description: This issue may occur when you accidentally quit the SHR installation wizard and later continue to reinstall with the existing components.
Resolution: Perform the following steps to resolve this problem:
Symptom: After interrupted installation, unable to continue reinstall with the installed components
Description: This issue may occur when you accidentally quit the SHR installation wizard and later continue to reinstall with the existing components.
Resolution: Perform the following steps to resolve this problem:
Symptom: Data Collection Failure across all Configured Nodes
Description: Data collection in SHR fails with an Address already in use error logged in the topologycollector.log
file.
Resolution: This error occurs when the number of TCP/IP ports used exceeds the default value of 5000. To resolve this problem, you must make changes in the Windows Registry. Follow these steps:
In the Open box, type regedit
. The Registry Editor window appears.
On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.
On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:
MaxFreeTcbs = 65535 (decimal)
TcpTimedWaitDelay = 30 (decimal)
Restart the system after making changes in the Registry Editor.
Symptom: Data Collection Failure across all Configured Nodes
Description: Data collection in SHR fails with an Address already in use error logged in the topologycollector.log
file.
Resolution: This error occurs when the number of TCP/IP ports used exceeds the default value of 5000. To resolve this problem, you must make changes in the Windows Registry. Follow these steps:
In the Open box, type regedit
. The Registry Editor window appears.
On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.
On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:
MaxFreeTcbs = 65535 (decimal)
TcpTimedWaitDelay = 30 (decimal)
Restart the system after making changes in the Registry Editor.
Symptom: After uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector.
Description: If you uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector and error messages appear when you try to configure the collector in the Administration Console.
You can occasionally experience this issue even after installing the collector for the first time.
Resolution: To resolve this, manually import the certificate from the SHR system to the collector system by following these steps:
Log on to the collector system.
Run the following command:
ovcoreid
Note down the ID displayed in the console.
Log on to the SHR system.
Run the following command:
ovcm -issue -file <file> -name
<node name>-coreid
<core_ID>
In this instance, <core_ID> is the ID that you noted down in step 2.
The command prompts for a password. If you do not want to use a password, press Enter without typing anything.
In this instance, <file> is the name of the certificate file that you want to manually import to the collector system; you must specify the file name with complete path to the directory where you want to store the file. <node name> is the FQDN of the collector system.
Transfer the certificate file to the collector system.
Run the following command:
ovcert -importcert -file
<file>
Symptom: After uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector.
Description: If you uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector and error messages appear when you try to configure the collector in the Administration Console.
You can occasionally experience this issue even after installing the collector for the first time.
Resolution: To resolve this, manually import the certificate from the SHR system to the collector system by following these steps:
Log on to the collector system.
Run the following command:
ovcoreid
Note down the ID displayed in the console.
Log on to the SHR system.
Run the following command:
ovcm -issue -file <file> -name
<node name>-coreid
<core_ID>
In this instance, <core_ID> is the ID that you noted down in step 2.
The command prompts for a password. If you do not want to use a password, press Enter without typing anything.
In this instance, <file> is the name of the certificate file that you want to manually import to the collector system; you must specify the file name with complete path to the directory where you want to store the file. <node name> is the FQDN of the collector system.
Transfer the certificate file to the collector system.
Run the following command:
ovcert -importcert -file
<file>
Symptom: Installation fails for Management database package while installing as Domain user
Description:SHR installation fails with domain user during HPPmdbPostgreSQL package installation with the following error in the install log.
C:/HP-SHR/Postgres/data ... initdb: could not change permissions of directory "C:/HP-SHR/Postgres/data": Permission denied in %temp%\install-postgresql.log (or) %temp%\bitrock_installer.log
Resolution: Uninstall SHR and create a local user that is a member of the Local Administrators group with administrator rights and install SHR again.
Symptom: Installation fails for Management database package while installing as Domain user
Description:SHR installation fails with domain user during HPPmdbPostgreSQL package installation with the following error in the install log.
C:/HP-SHR/Postgres/data ... initdb: could not change permissions of directory "C:/HP-SHR/Postgres/data": Permission denied in %temp%\install-postgresql.log (or) %temp%\bitrock_installer.log
Resolution: Uninstall SHR and create a local user that is a member of the Local Administrators group with administrator rights and install SHR again.
Symptom: Installer fails to display that installation is complete.
Description: This issue may appear while performing SHR installation, upgrade or installing Remote Collectors. The installer progress bar shows that the installation is in process but the Done button is enabled. This is because the installer is not refreshed.
Resolution: Click Done to complete the process and check the install log files as follows to see if all the components are installed.
%temp%/../HP-SHR_9.40_HPOvInstaller.txt
/tmp/HP-SHR_9.40_HPOvInstaller.txt
Symptom: Installer fails to display that installation is complete.
Description: This issue may appear while performing SHR installation, upgrade or installing Remote Collectors. The installer progress bar shows that the installation is in process but the Done button is enabled. This is because the installer is not refreshed.
Resolution: Click Done to complete the process and check the install log files as follows to see if all the components are installed.
%temp%/../HP-SHR_9.40_HPOvInstaller.txt
/tmp/HP-SHR_9.40_HPOvInstaller.txt
Symptom: Installer fails to display that installation is complete.
Description: This issue may appear while performing SHR installation, upgrade or installing Remote Collectors. The installer progress bar shows that the installation is in process but the Done button is enabled. This is because the installer is not refreshed.
Resolution: Click Done to complete the process and check the install log files as follows to see if all the components are installed.
%temp%/../HP-SHR_9.40_HPOvInstaller.txt
/tmp/HP-SHR_9.40_HPOvInstaller.txt
Symptom: Sybase IQ database removal failed after uninstall.
Description: This issue occurs while performing uninstall of SHR. The Sybase IQ database is not removed properly, you will see a pop up as follows:
"Initialize action for HP Service Health Reporter 9.40 (Removing Sybase IQ schema) was not successful."
Resolution: You can move ahead with the uninstall and run the rollback utility. For the steps, see "Post Uninstalling SHR" section in this guide.
Symptom: Uninstall is not clean.
Description: This issue occurs while performing uninstall of SHR, you will see a pop up saying there is a failure as follows:
"Initialize action for package HPPmdbCollector 9.40.000 (HP PMDB Collector) (Performing Collection housekeeping) was not successful."
Resolution: You can ignore the pop up and move ahead with the uninstall and run the rollback utility. For the steps, see "Post Uninstalling SHR" section in this guide.
Symptom: Failure in upgrade command.
Description: This issue may occur after upgrade of SHR, you will see a message saying there is a failure in the upgrade command.
Resolution: From the command line console run the following script:
%Ovinstalldir%\nonOV\perl\a\bin\perl %PMDB_HOME%\upgrade\940\applyPatch.pl %PMDB_HOME%\..\ “%ovinstalldir%” %PMDB_HOME%\upgrade\940
/opt/OV/nonOV/perl/a/bin/perl /opt/HP/BSM/PMDB/upgrade/940/applyPatch.pl /opt/HP/BSM/ /opt/OV/ /opt/HP/BSM/PMDB/upgrade/940/
Symptom: Failure in service precheck while upgrade.
Description: While upgrade, if all the SHR services are not stopped this issue may occur.
Resolution: From the PMDB_HOME\temp
folder check the UpgradeServiceCheck.log
file to find the cause of failure.
Symptom: After upgrade, few links in the Administration Console may fail to work.
Description: After upgrade, the CMC and InfoView links may fail to work SHR Administration Console. This issue may occur if the SAP BusinessObjects services are not running.
Resolution: Perform the following steps to stop the SAP BusinessObjects services:
Start the Business Objects Webserver Service
Run the following command to start the webserver:
sh /opt/HP/BSM/BO/bobje/tomcatstartup.sh
Symptom: Installation with username having special character "&" requires system startup.
Description: While installing SHR with username having special character &
then the system requests for startup.
Resolution: Click Continue and proceed with your installation.
Symptom: Installation with username having special character "&" requires system startup.
Description: While installing SHR with username having special character &
then the system requests for startup.
Resolution: Click Continue and proceed with your installation.
Symptom: After Uninstall, reinstall hangs on RHEL 5.5.
Description: After uninstall, when you reinstall SHR on Linux RHEL 5.5, the system hangs while installing BusinessObjects.
Resolution: Ensure that you perform SHR installation on a new Linux RHEL 5.5 system.
Symptom: YUM check warning after SHR installation
Description: After installing SHR and meeting all the pre-requisites, the following message appears with a list of missing libraries:
Found 42 pre-existing rpmdb problem(s), 'yum check' output follows:
Resolution: If you get a list of missing libraries while performing the YUM check, you can ignore these libraries as they are not mandatory for SHR. This does not affect the functionality of SHR.
Symptom: Installation Failure caused by SAP BusinessObjects Error
Description: While running the HP Software installer, the installation fails and the following error message is displayed:
SAP BusinessObjects is installed on the system. Please uninstall it before installing HP SH Reporter.
Resolution: If you have any component of SHR (such as SAP BusinessObjects or Sybase IQ) preinstalled or not cleanly uninstalled from a previous uninstall on your system, the SHR installation will fail because the installer tries to install the components that are bundled with the product.
To resolve this problem, you must clean up the existing components from the system and rerun the installer. For a virtual system, consider reimaging the VM, if feasible.
Symptom: Installation Failure caused by SAP BusinessObjects Error
Description: While running the HP Software installer, the installation fails and the following error message is displayed:
SAP BusinessObjects is installed on the system. Please uninstall it before installing HP SH Reporter.
Resolution: If you have any component of SHR (such as SAP BusinessObjects or Sybase IQ) preinstalled or not cleanly uninstalled from a previous uninstall on your system, the SHR installation will fail because the installer tries to install the components that are bundled with the product.
To resolve this problem, you must clean up the existing components from the system and rerun the installer. For a virtual system, consider reimaging the VM, if feasible.
Symptom: Installation failure due to missing libraries
Description: While installing SHR, if there any missing libraries the installation pre-check will fail.
Resolution: To resolve this problem, perform the following steps:
/tmp/SHR-Missing-Patches.txt
get the list of missing libraries.For more information, see the "Installation Prerequisites" section in this document.
Symptom: Installation failure due to missing libraries
Description: While installing SHR, if there any missing libraries the installation pre-check will fail.
Resolution: To resolve this problem, perform the following steps:
/tmp/SHR-Missing-Patches.txt
get the list of missing libraries.For more information, see the "Installation Prerequisites" section in this document.
Symptom: Unable to Bring up SHR Services after Successful Installation
Description: If SHR is installed on a virtual machine that is not restarted after the installation, the environment variables set by the installer will not be available to the user resulting in SHR services not coming up in spite of multiple retry.
Resolution: After installing SHR, ensure that you restart the virtual machine.
Symptom: Unable to Bring up SHR Services after Successful Installation
Description: If SHR is installed on a virtual machine that is not restarted after the installation, the environment variables set by the installer will not be available to the user resulting in SHR services not coming up in spite of multiple retry.
Resolution: After installing SHR, ensure that you restart the virtual machine.
Symptom: Remote Sybase IQ Database Creation Fails
In the HP Service Health Reporter Configuration Wizard, while trying to create the Sybase database file on a remote system, the post-install fails and the following error message is displayed:
<time stamp>,018 ERROR, com.hp.bto.bsmr.dao.helper.CreateSybaseIQDatabase.executeSQL, Could not connect to the database.
<time stamp>,049 ERROR, com.hp.bto.bsmr.dao.helper.CreateSybaseIQDatabase.executeSQL , Specified database not found
Resolution 1: This error occurs if the database file location specified in the HP Service Health Reporter Configuration Wizard includes one or more spaces in the file path. To resolve this problem, make sure that the specified database file location exists on the remote system. In addition, make sure that the path provided in the Post-Install wizard does not contain any spaces.
Resolution 2: This error can occur when adequate disk space is not available on the drive. The installer does not warn in case of a remote database. Increasing the disk space should resolve the issue.
Symptom: Sybase IQ Hangs
Description:SHR servers that have four or less CPUs, Sybase IQ hangs because of low iqgovern
parameter value that is computed automatically.
Resolution:
Windows: Add "-iqgovern 50
" parameter to the %PMDB_HOME%\config\pmdbConfig.cfg
file and restart the Sybase IQ database.
Linux: Add "-iqgovern 50
" parameter to the $PMDB_HOME/config/pmdbConfig.cfg
file and restart the Sybase IQ database.
Symptom: Sybase IQ Hangs
Description:SHR servers that have four or less CPUs, Sybase IQ hangs because of low iqgovern
parameter value that is computed automatically.
Resolution:
Windows: Add "-iqgovern 50
" parameter to the %PMDB_HOME%\config\pmdbConfig.cfg
file and restart the Sybase IQ database.
Linux: Add "-iqgovern 50
" parameter to the $PMDB_HOME/config/pmdbConfig.cfg
file and restart the Sybase IQ database.
Symptom: SHR Fails to Create the Sybase Schema
Description: If SHR fails to create the Sybase schema after you complete the post-installation configuration tasks, an error message appears in the database log files. The Sybase database log files—<hostname>.0001.srvlog
and <hostname>.0001.stderr—
are present in the /opt/HP/BSM/Sybase/IQ-16_0/logfiles
directory on Linux.
The following error message appears in the Sybase database log files:
“utility_db" (utility_db) stopped
Only the Sybase database log files show the error message; no error messages appear in the Administration console.
Resolution: Restart the Sybase service by running the following command:
service HP_PMDB_Platform_Sybase stop
service HP_PMDB_Platform_Sybase start
Symptom: SHR Fails to Create the Sybase Schema
Description: If SHR fails to create the Sybase schema after you complete the post-installation configuration tasks, an error message appears in the database log files. The Sybase database log files—<hostname>.0001.srvlog
and <hostname>.0001.stderr—
are present in the /opt/HP/BSM/Sybase/IQ-16_0/logfiles
directory on Linux.
The following error message appears in the Sybase database log files:
“utility_db" (utility_db) stopped
Only the Sybase database log files show the error message; no error messages appear in the Administration console.
Resolution: Restart the Sybase service by running the following command:
service HP_PMDB_Platform_Sybase stop
service HP_PMDB_Platform_Sybase start
Symptom: After Installation, User is Unable to Perform Post-Install Steps
Description: After installation, when user clicks Next, the subsequent page does not load despite enabling Java scripts to run.
Resolution: This occurs when the system date on which SHR is installed is much older than that of the ESX (in case of a VM). In such a scenario, the Tomcat server does not allow any requests from the client. Hence, it is always advisable to update the system date to current and install.
Perform the following steps:
Apply the permanent license.
When the system date is changed by more than three months, the license expires.
Symptom: After Installation, User is Unable to Perform Post-Install Steps
Description: After installation, when user clicks Next, the subsequent page does not load despite enabling Java scripts to run.
Resolution: This occurs when the system date on which SHR is installed is much older than that of the ESX (in case of a VM). In such a scenario, the Tomcat server does not allow any requests from the client. Hence, it is always advisable to update the system date to current and install.
Perform the following steps:
Apply the permanent license.
When the system date is changed by more than three months, the license expires.
Symptom: SHR Uninstall Fails
Description: Uninstalling SHR might not have completely uninstalled Sybase IQ Server.
Resolution: Uninstall Sybase IQ Server Suite 15.4 (64-bit) manually and restart your system.
Symptom: After Uninstalling SHR, Reinstall Fails
Description: After uninstalling SHR on a Windows system, when a reinstall is performed, the installer fails to launch and displays a Scripting Host not Found
error.
Resolution: This error is encountered when the Path environment variable in Windows is corrupted. Add the %systemroot%\System32
string to the Path environment variable by performing the following steps:
%systemroot%\System32
if missing.Symptom: After Uninstalling SHR, Reinstall Fails
Description: After uninstalling SHR on a Windows system, when a reinstall is performed, the installer fails to launch and displays a Scripting Host not Found
error.
Resolution: This error is encountered when the Path environment variable in Windows is corrupted. Add the %systemroot%\System32
string to the Path environment variable by performing the following steps:
%systemroot%\System32
if missing.Symptom: After interrupted installation, unable to continue reinstall with the installed components
Description: This issue may occur when you accidentally quit the SHR installation wizard and later continue to reinstall with the existing components.
Resolution: Perform the following steps to resolve this problem:
Symptom: After interrupted installation, unable to continue reinstall with the installed components
Description: This issue may occur when you accidentally quit the SHR installation wizard and later continue to reinstall with the existing components.
Resolution: Perform the following steps to resolve this problem:
Symptom: Data Collection Failure across all Configured Nodes
Description: Data collection in SHR fails with an Address already in use error logged in the topologycollector.log
file.
Resolution: This error occurs when the number of TCP/IP ports used exceeds the default value of 5000. To resolve this problem, you must make changes in the Windows Registry. Follow these steps:
In the Open box, type regedit
. The Registry Editor window appears.
On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.
On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:
MaxFreeTcbs = 65535 (decimal)
TcpTimedWaitDelay = 30 (decimal)
Restart the system after making changes in the Registry Editor.
Symptom: Data Collection Failure across all Configured Nodes
Description: Data collection in SHR fails with an Address already in use error logged in the topologycollector.log
file.
Resolution: This error occurs when the number of TCP/IP ports used exceeds the default value of 5000. To resolve this problem, you must make changes in the Windows Registry. Follow these steps:
In the Open box, type regedit
. The Registry Editor window appears.
On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.
On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:
MaxFreeTcbs = 65535 (decimal)
TcpTimedWaitDelay = 30 (decimal)
Restart the system after making changes in the Registry Editor.
Symptom: After uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector.
Description: If you uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector and error messages appear when you try to configure the collector in the Administration Console.
You can occasionally experience this issue even after installing the collector for the first time.
Resolution: To resolve this, manually import the certificate from the SHR system to the collector system by following these steps:
Log on to the collector system.
Run the following command:
ovcoreid
Note down the ID displayed in the console.
Log on to the SHR system.
Run the following command:
ovcm -issue -file <file> -name
<node name>-coreid
<core_ID>
In this instance, <core_ID> is the ID that you noted down in step 2.
The command prompts for a password. If you do not want to use a password, press Enter without typing anything.
In this instance, <file> is the name of the certificate file that you want to manually import to the collector system; you must specify the file name with complete path to the directory where you want to store the file. <node name> is the FQDN of the collector system.
Transfer the certificate file to the collector system.
Run the following command:
ovcert -importcert -file
<file>
Symptom: After uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector.
Description: If you uninstall a collector and reinstall it on a system, SHR fails to communicate with the collector and error messages appear when you try to configure the collector in the Administration Console.
You can occasionally experience this issue even after installing the collector for the first time.
Resolution: To resolve this, manually import the certificate from the SHR system to the collector system by following these steps:
Log on to the collector system.
Run the following command:
ovcoreid
Note down the ID displayed in the console.
Log on to the SHR system.
Run the following command:
ovcm -issue -file <file> -name
<node name>-coreid
<core_ID>
In this instance, <core_ID> is the ID that you noted down in step 2.
The command prompts for a password. If you do not want to use a password, press Enter without typing anything.
In this instance, <file> is the name of the certificate file that you want to manually import to the collector system; you must specify the file name with complete path to the directory where you want to store the file. <node name> is the FQDN of the collector system.
Transfer the certificate file to the collector system.
Run the following command:
ovcert -importcert -file
<file>
Symptom: Installation fails for Management database package while installing as Domain user
Description:SHR installation fails with domain user during HPPmdbPostgreSQL package installation with the following error in the install log.
C:/HP-SHR/Postgres/data ... initdb: could not change permissions of directory "C:/HP-SHR/Postgres/data": Permission denied in %temp%\install-postgresql.log (or) %temp%\bitrock_installer.log
Resolution: Uninstall SHR and create a local user that is a member of the Local Administrators group with administrator rights and install SHR again.
Symptom: Installation fails for Management database package while installing as Domain user
Description:SHR installation fails with domain user during HPPmdbPostgreSQL package installation with the following error in the install log.
C:/HP-SHR/Postgres/data ... initdb: could not change permissions of directory "C:/HP-SHR/Postgres/data": Permission denied in %temp%\install-postgresql.log (or) %temp%\bitrock_installer.log
Resolution: Uninstall SHR and create a local user that is a member of the Local Administrators group with administrator rights and install SHR again.
Symptom: Installer fails to display that installation is complete.
Description: This issue may appear while performing SHR installation, upgrade or installing Remote Collectors. The installer progress bar shows that the installation is in process but the Done button is enabled. This is because the installer is not refreshed.
Resolution: Click Done to complete the process and check the install log files as follows to see if all the components are installed.
%temp%/../HP-SHR_9.40_HPOvInstaller.txt
/tmp/HP-SHR_9.40_HPOvInstaller.txt
Symptom: Installer fails to display that installation is complete.
Description: This issue may appear while performing SHR installation, upgrade or installing Remote Collectors. The installer progress bar shows that the installation is in process but the Done button is enabled. This is because the installer is not refreshed.
Resolution: Click Done to complete the process and check the install log files as follows to see if all the components are installed.
%temp%/../HP-SHR_9.40_HPOvInstaller.txt
/tmp/HP-SHR_9.40_HPOvInstaller.txt
Symptom: Installer fails to display that installation is complete.
Description: This issue may appear while performing SHR installation, upgrade or installing Remote Collectors. The installer progress bar shows that the installation is in process but the Done button is enabled. This is because the installer is not refreshed.
Resolution: Click Done to complete the process and check the install log files as follows to see if all the components are installed.
%temp%/../HP-SHR_9.40_HPOvInstaller.txt
/tmp/HP-SHR_9.40_HPOvInstaller.txt
Symptom: Sybase IQ database removal failed after uninstall.
Description: This issue occurs while performing uninstall of SHR. The Sybase IQ database is not removed properly, you will see a pop up as follows:
"Initialize action for HP Service Health Reporter 9.40 (Removing Sybase IQ schema) was not successful."
Resolution: You can move ahead with the uninstall and run the rollback utility. For the steps, see "Post Uninstalling SHR" section in this guide.
Symptom: Uninstall is not clean.
Description: This issue occurs while performing uninstall of SHR, you will see a pop up saying there is a failure as follows:
"Initialize action for package HPPmdbCollector 9.40.000 (HP PMDB Collector) (Performing Collection housekeeping) was not successful."
Resolution: You can ignore the pop up and move ahead with the uninstall and run the rollback utility. For the steps, see "Post Uninstalling SHR" section in this guide.
Symptom: Failure in upgrade command.
Description: This issue may occur after upgrade of SHR, you will see a message saying there is a failure in the upgrade command.
Resolution: From the command line console run the following script:
%Ovinstalldir%\nonOV\perl\a\bin\perl %PMDB_HOME%\upgrade\940\applyPatch.pl %PMDB_HOME%\..\ “%ovinstalldir%” %PMDB_HOME%\upgrade\940
/opt/OV/nonOV/perl/a/bin/perl /opt/HP/BSM/PMDB/upgrade/940/applyPatch.pl /opt/HP/BSM/ /opt/OV/ /opt/HP/BSM/PMDB/upgrade/940/
Symptom: Failure in service precheck while upgrade.
Description: While upgrade, if all the SHR services are not stopped this issue may occur.
Resolution: From the PMDB_HOME\temp
folder check the UpgradeServiceCheck.log
file to find the cause of failure.
Symptom: After upgrade, few links in the Administration Console may fail to work.
Description: After upgrade, the CMC and InfoView links may fail to work SHR Administration Console. This issue may occur if the SAP BusinessObjects services are not running.
Resolution: Perform the following steps to stop the SAP BusinessObjects services:
Start the Business Objects Webserver Service
Run the following command to start the webserver:
sh /opt/HP/BSM/BO/bobje/tomcatstartup.sh
Symptom: Installation with username having special character "&" requires system startup.
Description: While installing SHR with username having special character &
then the system requests for startup.
Resolution: Click Continue and proceed with your installation.
Symptom: Installation with username having special character "&" requires system startup.
Description: While installing SHR with username having special character &
then the system requests for startup.
Resolution: Click Continue and proceed with your installation.
Symptom: After Uninstall, reinstall hangs on RHEL 5.5.
Description: After uninstall, when you reinstall SHR on Linux RHEL 5.5, the system hangs while installing BusinessObjects.
Resolution: Ensure that you perform SHR installation on a new Linux RHEL 5.5 system.
Symptom: YUM check warning after SHR installation
Description: After installing SHR and meeting all the pre-requisites, the following message appears with a list of missing libraries:
Found 42 pre-existing rpmdb problem(s), 'yum check' output follows:
Resolution: If you get a list of missing libraries while performing the YUM check, you can ignore these libraries as they are not mandatory for SHR. This does not affect the functionality of SHR.
© Copyright 2015 - 2016 Hewlett-Packard Development Company, L.P.