HP Service Health Reporter

For the [Windows® and Linux] operating systems

Software Version: 9.40

Customized output from:

Interactive Installation Guide

Document Release Date: July 2016

Software Release Date: January 2015

HP logo

Legal Notices

Warranty

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.

Restricted Rights Legend

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 Notice

© Copyright 2015 - 2016 Hewlett-Packard Development Company, L.P.

Trademark Notices

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.

 
 
 
 

Interactive Installation Guide

Introduction

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.

Installation Overview

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.

Choose your Task

Install
Upgrade
Uninstall

Select the task you want to perform with HP Service Health Reporter.

Choose your Operating System

Windows 2008
Windows 2012
Linux

Select the operating system for HP Service Health Reporter.

Choose your Installation Preference

Custom
Typical

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.

Install Remote Collectors

Select to install remote collectors

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.

View or print

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.

Check your selections

The following steps are customized according to your selections.

 

If any selections are not correct, click Change.

Windows Prerequisites

This content is valid for Linux.

Linux Prerequisites

This content is valid for Linux.

Windows Install Typical

This content is valid for Windows.

Linux Install Typical

This content is valid for UNIX.

Windows Prerequisites

This content is valid for Linux.

Installation Prerequisites

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.

If SHR and SAP BusinessObjects are in separate directories, then there must be a free disk space of 10 GB on each to perform install.

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

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

Preinstallation Tasks and Checklist

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:

  1. 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.

  2. Type the following command to view the IP address of the system:

    ipconfig

  3. 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

    1. Click Start > Control Panel. The Control Panel window appears.
    2. In the Control Panel window, double-click User Accounts.
    3. In the User Accounts window, click User Accounts.
    4. In the User Accounts tasks window, click Turn User Account Control on or off.
    5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.
    6. Clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK.
    7. Click Restart Now to apply the change.
  • Windows Server 2008 R2 with Service Pack 1

    1. Click Start > Control Panel. The Control Panel window appears.
    2. In the Control Panel window, double-click User Accounts.
    3. In the User Accounts window, click User Accounts.
    4. In the User Accounts tasks window, click Change User Account Control Settings.
    5. In the User Accounts Control Settings window, move the slider to the bottom to select the Never notify option, and then click OK.
    6. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.
    7. Click Restart Now to apply the change.

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.

  1. Click Start > Run. The Run dialog box appears.
  2. In the Open box, type regedit. The Registry Editor window appears.
  3. On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Control, expand Session Manager, and click SubSystems.
  4. On the right pane, right-click Windows, and then click Modify. The Edit String dialog box appears.
  5. In the Value data box, change the value
    ObjectDirectory=\Windows SharedSection=1024,20480,768 to ObjectDirectory=\Windows SharedSection=1024,20480,1536.
  6. Restart the system after making the changes in the Registry Editor.

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:

  1. Click Start > Run to open the Run prompt.

  2. Type CMD and press Enter. The command prompt window appears.

  3. 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

  4. Download the .tar file parts into the temporary folder that you created in the previous step.

    For example: C:\temp\HPSHR_9.4-parts.

  5. 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

  6. 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

  • Log on to the system as administrator. You must be a member of the Local Administrators group.
  • You can also install SHR in a domain as a domain/local user with administrator rights.
  • Ensure that system time does not change during the course of the installation. Make sure the system does not automatically transition to the daylight saving time during installation.
  • Do not install SHR from a network share. Because of the large size of the installation files, installation of SHR over the network is not supported.

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.

Typical Installation: Install on a Single System

Install HP Service Health Reporter Server, Sybase IQ Server, and SAP BusinessObjects Server on a single system.

  1. Run the following file:

    HP-SHR_9.40_setup.exe

    The setup files are extracted.

  2. Select the language in which you want to install SHR, and click OK.

    The HP Service Health Reporter 9.40 Software Installer wizard appears.

  3. On the Introduction page, review the note and click Next.
  4. On the License Agreement page, review the license agreement.
  5. Select I accept..., and click Next to proceed with the installation.
  6. On the Product Customization page, select Typical HP Service Health Reporter Installation and click Next.
  7. 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.

  8. Enter the SAP BusinessObjects install drive. The default value is C.
  9. Note: Enter only the alphabet that denotes the drive. For example, enter C and not C:\ or C:.

  10. 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.

  11. The Pre-Installation Summary page appears. Review the summary, and click Install.
  12. 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:

  1. 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.

  2. 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.

Post-Installation Task for Sybase IQ

For SHR on a system with the Simplified Chinese or Japanese locale, follow these steps:

  1. 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.

  2. 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

Custom Installation: Install SHR in a Distributed Environment

The custom installation of SHR enables you to install different components of SHR on different systems. SHR comprises of the following fundamental components:

  • SHR server
  • Sybase server
  • SAP BusinessObjects server

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.

Installation Prerequisites

Make sure that all the prerequisites that are listed in this section are met on each system.

These prerequisites also apply to 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.

If SHR and SAP BusinessObjects are in separate directories, then there must be a free disk space of 10 GB on each to perform install.

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

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

Preinstallation Tasks and Checklist

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:

  1. 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.

  2. Type the following command to view the IP address of the system:

    ipconfig

  3. 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

    1. Click Start > Control Panel. The Control Panel window appears.
    2. In the Control Panel window, double-click User Accounts.
    3. In the User Accounts window, click User Accounts.
    4. In the User Accounts tasks window, click Turn User Account Control on or off.
    5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.
    6. Clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK.
    7. Click Restart Now to apply the change.
  • Windows Server 2008 R2 with Service Pack 1

    1. Click Start > Control Panel. The Control Panel window appears.
    2. In the Control Panel window, double-click User Accounts.
    3. In the User Accounts window, click User Accounts.
    4. In the User Accounts tasks window, click Change User Account Control Settings.
    5. In the User Accounts Control Settings window, move the slider to the bottom to select the Never notify option, and then click OK.
    6. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.
    7. Click Restart Now to apply the change.

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.

  1. Click Start > Run. The Run dialog box appears.
  2. In the Open box, type regedit. The Registry Editor window appears.
  3. On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Control, expand Session Manager, and click SubSystems.
  4. On the right pane, right-click Windows, and then click Modify. The Edit String dialog box appears.
  5. In the Value data box, change the value
    ObjectDirectory=\Windows SharedSection=1024,20480,768 to ObjectDirectory=\Windows SharedSection=1024,20480,1536.
  6. Restart the system after making the changes in the Registry Editor.

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:

  1. Click Start > Run to open the Run prompt.

  2. Type CMD and press Enter. The command prompt window appears.

  3. 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

  4. Download the .tar file parts into the temporary folder that you created in the previous step.

    For example: C:\temp\HPSHR_9.4-parts.

  5. 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

  6. 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

  • Ensure that system time does not change during the course of the installation. Make sure the system does not automatically transition to the daylight saving time during installation.
  • Do not install SHR from a network share. Because of the large size of the installation files, installation of SHR over the network is not supported.

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 SHR Server

  1. Run the following file:

    HP-SHR_9.40_setup.exe

    The setup files are extracted.

  2. Select the language in which you want to install SHR, and click OK.

    The HP Service Health Reporter 9.40 Software Installer wizard appears.

  3. On the Introduction page, review the note and click Next.
  4. On the License Agreement page, review the license agreement.
  5. Select I accept..., and click Next to proceed with the installation.
  6. On the Product Customization page, select Custom HP Service Health Reporter Installation and click Next.
  7. Select HP Service Health Reporter Server and click Next.
  8. Enter the fully qualified domain name of the host where you plan to install (or have already installed) SAP BusinessObjects.
  9. 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.

  10. 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.

  11. The Pre-Install Summary page appears. Review the summary, and click Install.
  12. After the installation is complete, click Done.
  13. 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:

  1. 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.

  2. 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.

Installing Sybase IQ Server

To install with the help of the installation wizard, follow these steps:

  1. Run the following file:

    HP-SHR_9.40_setup.exe

    The setup files are extracted.

  2. Select the language in which you want to install SHR, and click OK.

    The HP Service Health Reporter 9.40 Software Installer wizard appears.

  3. On the Introduction page, review the note and click Next.
  4. On the License Agreement page, review the license agreement.
  5. Select I accept..., and click Next to proceed with the installation.
  6. On the Product Customization page, select Custom HP Service Health Reporter Installation and click Next.
  7. Select Sybase IQ Server and click Next.
  8. 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.

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

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

  10. The Pre-Install Summary page appears. Review the summary, and click Install.
  11. After the installation is complete, click Done.
  12. 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:

  1. 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.

  2. 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.

Post-Installation Task for Sybase IQ

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

Installing SAP BusinessObjects

To install with the help of the installation wizard, follow these steps:

  1. Run the following file:

    HP-SHR_9.40_setup.exe

    The setup files are extracted.

  2. Select the language in which you want to install SHR, and click OK.

    The HP Service Health Reporter 9.40 Software Installer wizard appears.

  3. On the Introduction page, review the note and click Next.
  4. On the License Agreement page, review the license agreement.
  5. Select I accept..., and click Next to proceed with the installation.
  6. On the Product Customization page, select Custom HP Service Health Reporter Installation and click Next.
  7. Select SAP BusinessObjects Server and click Next.
  8. Enter the SAP BusinessObjects install drive. The default value is C.
  9. Note: Enter only the alphabet that denotes the drive. For example, enter C and not C:\ or C:.

  10. 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.

  11. 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.

  12. The Pre-Install Summary page appears. Review the summary, and click Install.
  13. After the installation is complete, click Done.
  14. 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:

  1. 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.

  2. 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.

Installing SAP BusinessObjects Language Packs

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:

  1. Log on to the system where you installed Service Health Reporter.
  2. 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.

  3. Make sure that the SHR media is available on the system.
  4. Go to the following directory:

    %PMDB_HOME%\temp\BO_Updates

  5. 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\"

  6. 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.

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

Custom Installation: Install SHR in a Distributed Environment

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:

  • SHR server
  • Sybase IQ server
  • SAP BusinessObjects server

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.

Installation Prerequisites

Make sure that all the prerequisites that are listed in this section are met on each system.

These prerequisites also apply to 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.

If SHR and SAP BusinessObjects are in separate directories, then there must be a free disk space of 10 GB on each to perform install.

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

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

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.

Preinstallation Tasks and Checklist

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:

  1. 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.

  2. Type the following command to view the IP address of the system:

    ipconfig

  3. 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

    1. Click Start > Control Panel. The Control Panel window appears.
    2. In the Control Panel window, double-click User Accounts.
    3. In the User Accounts window, click User Accounts.
    4. In the User Accounts tasks window, click Change User Account Control Settings.
    5. In the User Accounts Control Settings window, move the slider to the bottom to select the Never notify option, and then click OK.

    6. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.
    7. Click Restart Now to apply the change.

      Perform the following additional steps to disable it UAC via registry:

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

      2. In the Open box, type regedit. The Registry Editor window appears.
      3. In the registry go to the following path:

        HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > policies > system

      4. Set the value for EnableLUA to 0.
      5. You will get a notification to restart your system. The UAC will be disabled after restarting your system.

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:

  1. On the Windows 2012 system, download the Microsoft .NET Framework 3.5 from the Microsoft website http://www.microsoft.com.
  2. From the task-bar open the Server Manager Dashboard.
  3. Click Add roles and features. The Add Roles and Features wizard appears.
  4. Select Role based or feature based installation option and click Next. The Select destination server window appears.
  5. Click Select a server from the server pool and click on the required server from the list, and then click Next. The Select server role window appears.
  6. Click Next.The Select Features window appears.
  7. In the Features list expand .Net Framework 3.5 Features, and select it. The .Net Framework 3.5 (includes .Net 2.0 and 3.5) also gets selected automatically.
  8. Click Next. The Confirm Installation Selections window appears.
  9. Click Specify an alternate source path and type the path where you have downloaded Microsoft .Net Framework 3.5.
  10. Click Install to start the installation.
  11. After successful installation, click Close.

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.

  1. Click Start > Run. The Run dialog box appears.
  2. In the Open box, type regedit. The Registry Editor window appears.
  3. On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Control, expand Session Manager, and click SubSystems.
  4. On the right pane, right-click Windows, and then click Modify. The Edit String dialog box appears.
  5. In the Value data box, change the value
    ObjectDirectory=\Windows SharedSection=1024,20480,768 to ObjectDirectory=\Windows SharedSection=1024,20480,1536.
  6. Restart the system after making the changes in the Registry Editor.

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:

  1. Click Start > Run to open the Run prompt.

  2. Type CMD and press Enter. The command prompt window appears.

  3. 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

  4. Download the .tar file parts into the temporary folder that you created in the previous step.

    For example: C:\temp\HPSHR_9.4-parts.

  5. 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

  6. 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

  • Ensure that system time does not change during the course of the installation. Make sure the system does not automatically transition to the daylight saving time during installation.
  • Do not install SHR from a network share. Because of the large size of the installation files, installation of SHR over the network is not supported.

For remote Sybase IQ system on Linux operating system:

  • Users using the home directory with external applications are not supported (For Example: AD, NIS).
  • Always install SHR as root.

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

  • You can also install SHR in a domain as a domain/local user with administrator rights.
  • If you are installing SHR as a non-root user, the user and the home directory must be local to the system where installation is performed.
  • Ensure that system time does not change during the course of the installation. Make sure the system does not automatically transition to the daylight saving time during installation.
  • Do not install SHR from a network share. Because of the large size of the installation files, installation of SHR over the network is not supported.

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 SHR Server

  1. Run the following file:

    HP-SHR_9.40_setup.exe

    The setup files are extracted.

  2. Select the language in which you want to install SHR, and click OK.

    The HP Service Health Reporter 9.40 Software Installer wizard appears.

  3. On the Introduction page, review the note and click Next.
  4. On the License Agreement page, review the license agreement.
  5. Select I accept..., and click Next to proceed with the installation.
  6. On the Product Customization page, select Custom HP Service Health Reporter Installation and click Next.
  7. Select HP Service Health Reporter Server and click Next.
  8. Enter the fully qualified domain name of the host where you plan to install (or have already installed) SAP BusinessObjects.
  9. 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.

  10. 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.

  11. The Pre-Install Summary page appears. Review the summary, and click Install.
  12. After the installation is complete, click Done.
  13. 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:

  1. 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.

  2. 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.

Installation Sybase IQ

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.

  • To download and merge the SHR remote collector media files, allocate at least 15 GB in the /tmp directory on each system.
  • To install SHR remote collector, allocate at least 10 GB in the /opt directory on each system.
    • Do not start the installation directly from the mount point location.
    • Do not download and merge the TAR files directly from the mount point location.
  • If additional external storage space is required to be added, ensure that no other applications are installed in the /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.
  • compat-libstdc++-33-3.2.3-69.i686
  • compat-libstdc++-33-3.2.3-69.x86_64
  • libXext-1.1-3.i686
  • libXext-1.1-3.x86_64
  • libXext-devel-1.1-3.i686
  • libXext-devel-1.1-3.x86_64
  • libstdc++-4.4.4-13.x86_64
  • libstdc++-4.4.4-13.i686
  • libXtst-1.0.99.2-3.i686
  • libXtst-1.0.99.2-3.x86_64
  • libXau-1.0.5-1.i686
  • libXau-1.0.5-1.x86_64
  • libXdmcp-1.0.3-1.i686
  • libxcb-1.5-1.x86_64
  • libxcb-1.5-1.i686
  • libXrender-0.9.5-1.i686
  • libXrender-0.9.5-1.x86_64
  • glibc-2.12-1.7.x86_64
  • glibc-2.12-1.7.i686
  • libgcc-4.4.1-13.i686
  • libgcc-4.4.4-13.x86_64
  • libX11-1.3-2.i686
  • libX11-1.3-2.x86_64
  • libXi-1.3-3.x86_64
  • libXi-1.3-3.i686
  • alsa-lib-1.0.22-3.i686
  • alsa-lib-1.0.22-3.x86_64
  • nss-softokn-freebl-3.12.7-1.1.i686
  • ncurses-libs-5.7-3.20090208.i686
  • ncurses-libs-5.7-3.20090208.x86_64
  • redhat-lsb.i686
  • redhat-lsb.x86_64
  • tcsh-6.17-8.el6.x86_64
  • compat-libstdc++-33-3.2.3-61.x86_64
  • compat-libstdc++-33-3.2.3-61.i386
  • libXext-1.0.1-2.1.x86_64
  • libXext-1.0.1-2.1.i386
  • libXext-devel-1.0.1-2.1.x86_64
  • libXext-devel-1.0.1-2.1.i386
  • libstdc++-4.1.2-48.x86_64
  • libstdc++-4.1.2-48.i386
  • libXtst-1.0.1-3.1.x86_64
  • libXtst-1.0.1-3.1.i386
  • libXau-1.0.1-3.1.x86_64
  • libXau-1.0.1-3.1.i386
  • libXdmcp-1.0.1-2.1.i386
  • libXrender-0.9.1-3.1.x86_64
  • libXrender-0.9.1-3.1.i386
  • glibc-2.5-47.i686
  • glibc-2.5-47.x86_64
  • libgcc-4.1.2-48.i386
  • libgcc-4.1.2-48.x86_64
  • libX11-1.0.3-11.x86_64
  • libX11-1.0.3-11.i386
  • libXi-1.0.1-3.1.x86_64
  • libXi-1.0.1-3.1.i386
  • alsa-lib-1.0.17-1.x86_64
  • alsa-lib-1.0.17-1.i386
  • glibc-2.5-47.i686
  • glibc-2.5-47.x86_64
  • redhat-lsb.i686
  • redhat-lsb.x86_64
  • tcsh-6.17-8.el6.x86_64

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:

  1. Log on to the system as root.

    The root user must be the owner of the /opt and /var directories.
  2. 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

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

    <swapfile_full_path>swap swap defaults 0 0

    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

  4. Restart the system.

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

  1. Log on as root and run the following commands:

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

  1. Open the file /etc/sysctl.conf file.
  2. Set the values of the parameters as given below:

Note: If higher values are specified for these parameters already, do not make any modifications.

  • kernel.msgmnb = 65536
  • kernel.msgmax = 65536
  • kernel.shmmax = 68719476736
  • kernel.shmall = 4294967296
  • kernel.sem = 250 1024000 250 4096
  • vm.max_map_count = 1000000

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.

  1. To create a new directory for installing SHR, run the following command:

    mkdir <directory name>

    For example: mkdir /tmp/HPSHR_9.4-parts

  2. 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

  3. Download the .tar file parts into the newly created temporary directory.

  4. 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

  1. 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.

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

    ./HP-SHR_9.40_setup.bin -i console

  3. 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.

  4. Choose the locale in which you want to install SHR, and then press Enter. The installer shows the introductory information in the console.
  5. Press Enter.
  6. 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.

  7. Type 2 to select Custom HP Service Health Reporter Server, and then press Enter.
  8. 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.

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

    If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the SHR installation again.
  10. If the prerequisite check is successful, press Enter. The installer shows preinstallation summary in the console.

  11. 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.

  12. 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:

  1. 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.

  2. 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

Installing SAP BusinessObjects

To install with the help of the installation wizard, follow these steps:

  1. Run the following file:

    HP-SHR_9.40_setup.exe

    The setup files are extracted.

  2. Select the language in which you want to install SHR, and click OK.

    The HP Service Health Reporter 9.40 Software Installer wizard appears.

  3. On the Introduction page, review the note and click Next.
  4. On the License Agreement page, review the license agreement.
  5. Select I accept..., and click Next to proceed with the installation.
  6. On the Product Customization page, select Custom HP Service Health Reporter Installation and click Next.
  7. Select SAP BusinessObjects Server and click Next.
  8. Enter the SAP BusinessObjects install drive. The default value is C.

  9. 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.

  10. 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.

  11. The Pre-Install Summary page appears. Review the summary, and click Install.
  12. After the installation is complete, click Done.
  13. 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:

  1. 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.

  2. 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.

Installing SAP BusinessObjects Language Packs

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:

  1. Log on to the system where you installed Service Health Reporter.
  2. 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.

  3. Make sure that the SHR media is available on the system.
  4. Go to the following directory:

    %PMDB_HOME%\temp\BO_Updates

  5. 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\"

  6. 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.

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

Installation Prerequisites

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.

  • To download and merge the SHR remote collector media files, allocate at least 15 GB in the /tmp directory on each system.
  • To install SHR remote collector, allocate at least 10 GB in the /opt directory on each system.
    • Do not start the installation directly from the mount point location.
    • Do not download and merge the TAR files directly from the mount point location.
  • If additional external storage space is required to be added, ensure that no other applications are installed in the /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.
  • compat-libstdc++-33-3.2.3-69.i686
  • compat-libstdc++-33-3.2.3-69.x86_64
  • libXext-1.1-3.i686
  • libXext-1.1-3.x86_64
  • libXext-devel-1.1-3.i686
  • libXext-devel-1.1-3.x86_64
  • libstdc++-4.4.4-13.x86_64
  • libstdc++-4.4.4-13.i686
  • libXtst-1.0.99.2-3.i686
  • libXtst-1.0.99.2-3.x86_64
  • libXau-1.0.5-1.i686
  • libXau-1.0.5-1.x86_64
  • libXdmcp-1.0.3-1.i686
  • libxcb-1.5-1.x86_64
  • libxcb-1.5-1.i686
  • libXrender-0.9.5-1.i686
  • libXrender-0.9.5-1.x86_64
  • glibc-2.12-1.7.x86_64
  • glibc-2.12-1.7.i686
  • libgcc-4.4.1-13.i686
  • libgcc-4.4.4-13.x86_64
  • libX11-1.3-2.i686
  • libX11-1.3-2.x86_64
  • libXi-1.3-3.x86_64
  • libXi-1.3-3.i686
  • alsa-lib-1.0.22-3.i686
  • alsa-lib-1.0.22-3.x86_64
  • nss-softokn-freebl-3.12.7-1.1.i686
  • ncurses-libs-5.7-3.20090208.i686
  • ncurses-libs-5.7-3.20090208.x86_64
  • redhat-lsb.i686
  • redhat-lsb.x86_64
  • tcsh-6.17-8.el6.x86_64
  • compat-libstdc++-33-3.2.3-61.x86_64
  • compat-libstdc++-33-3.2.3-61.i386
  • libXext-1.0.1-2.1.x86_64
  • libXext-1.0.1-2.1.i386
  • libXext-devel-1.0.1-2.1.x86_64
  • libXext-devel-1.0.1-2.1.i386
  • libstdc++-4.1.2-48.x86_64
  • libstdc++-4.1.2-48.i386
  • libXtst-1.0.1-3.1.x86_64
  • libXtst-1.0.1-3.1.i386
  • libXau-1.0.1-3.1.x86_64
  • libXau-1.0.1-3.1.i386
  • libXdmcp-1.0.1-2.1.i386
  • libXrender-0.9.1-3.1.x86_64
  • libXrender-0.9.1-3.1.i386
  • glibc-2.5-47.i686
  • glibc-2.5-47.x86_64
  • libgcc-4.1.2-48.i386
  • libgcc-4.1.2-48.x86_64
  • libX11-1.0.3-11.x86_64
  • libX11-1.0.3-11.i386
  • libXi-1.0.1-3.1.x86_64
  • libXi-1.0.1-3.1.i386
  • alsa-lib-1.0.17-1.x86_64
  • alsa-lib-1.0.17-1.i386
  • glibc-2.5-47.i686
  • glibc-2.5-47.x86_64
  • redhat-lsb.i686
  • redhat-lsb.x86_64
  • tcsh-6.17-8.el6.x86_64

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:

  1. Log on to the system as root.

    The root user must be the owner of the /opt and /var directories.
  2. 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

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

    <swapfile_full_path>swap swap defaults 0 0

    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

  4. Restart the system.

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.

Preinstallation Tasks and Checklist

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:

  1. 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:

  1. Open the file /etc/sysctl.conf file.
  2. Set the values of the parameters as given below:

Note: If higher values are specified for these parameters already, do not make any modifications.

  • kernel.msgmnb = 65536
  • kernel.msgmax = 65536
  • kernel.shmmax = 68719476736
  • kernel.shmall = 4294967296
  • kernel.sem = 250 1024000 250 4096
  • vm.max_map_count = 1000000

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:

  1. 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.

  2. Type the following command to view the IP address of the system:

    ifconfig

  3. 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.

  1. To create a new directory for installing SHR, run the following command:

    mkdir <directory name>

    For example: mkdir /tmp/HPSHR_9.4-parts

  2. 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

  3. Download the .tar file parts into the newly created temporary directory.

  4. 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

  • Users using the home directory with external applications are not supported (For Example: AD, NIS).
  • Always install SHR as root.

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

  • You can also install SHR in a domain as a domain/local user with administrator rights.
  • If you are installing SHR as a non-root user, the user and the home directory must be local to the system where installation is performed.
  • Ensure that system time does not change during the course of the installation. Make sure the system does not automatically transition to the daylight saving time during installation.
  • Do not install SHR from a network share. Because of the large size of the installation files, installation of SHR over the network is not supported.

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.

Typical Installation: Install on a Single System

Install HP Service Health Reporter Server, Sybase IQ Server, and SAP BusinessObjects Server on a single system.

Installing from the Command Line Console

  1. 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.

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

    ./HP-SHR_9.40_setup.bin -i console

  3. 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.

  4. Choose the locale in which you want to install SHR, and press Enter. The installer shows the introductory information in the console.
  5. Press Enter.
  6. 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.

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

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

    If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the SHR installation again.
  9. If the prerequisite check is successful, press Enter. The installer shows preinstallation summary in the console.

  10. Press Enter to start the installation.
  11. 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:

  1. 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.

  2. 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.

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

Custom Installation: Install SHR in a Distributed Environment

The custom installation of SHR enables you to install different components of SHR on different systems. SHR comprises of the following fundamental components:

  • SHR server
  • Sybase IQ server
  • SAP BusinessObjects server

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.

Installation Prerequisites

Ensure that all the prerequisites that are listed in this section are met on each system.

These prerequisites also apply to 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.

  • To download and merge the SHR remote collector media files, allocate at least 15 GB in the /tmp directory on each system.
  • To install SHR remote collector, allocate at least 10 GB in the /opt directory on each system.
    • Do not start the installation directly from the mount point location.
    • Do not download and merge the TAR files directly from the mount point location.
  • If additional external storage space is required to be added, ensure that no other applications are installed in the /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.
  • compat-libstdc++-33-3.2.3-69.i686
  • compat-libstdc++-33-3.2.3-69.x86_64
  • libXext-1.1-3.i686
  • libXext-1.1-3.x86_64
  • libXext-devel-1.1-3.i686
  • libXext-devel-1.1-3.x86_64
  • libstdc++-4.4.4-13.x86_64
  • libstdc++-4.4.4-13.i686
  • libXtst-1.0.99.2-3.i686
  • libXtst-1.0.99.2-3.x86_64
  • libXau-1.0.5-1.i686
  • libXau-1.0.5-1.x86_64
  • libXdmcp-1.0.3-1.i686
  • libxcb-1.5-1.x86_64
  • libxcb-1.5-1.i686
  • libXrender-0.9.5-1.i686
  • libXrender-0.9.5-1.x86_64
  • glibc-2.12-1.7.x86_64
  • glibc-2.12-1.7.i686
  • libgcc-4.4.1-13.i686
  • libgcc-4.4.4-13.x86_64
  • libX11-1.3-2.i686
  • libX11-1.3-2.x86_64
  • libXi-1.3-3.x86_64
  • libXi-1.3-3.i686
  • alsa-lib-1.0.22-3.i686
  • alsa-lib-1.0.22-3.x86_64
  • nss-softokn-freebl-3.12.7-1.1.i686
  • ncurses-libs-5.7-3.20090208.i686
  • ncurses-libs-5.7-3.20090208.x86_64
  • redhat-lsb.i686
  • redhat-lsb.x86_64
  • tcsh-6.17-8.el6.x86_64

  • compat-libstdc++-33-3.2.3-61.x86_64
  • compat-libstdc++-33-3.2.3-61.i386
  • libXext-1.0.1-2.1.x86_64
  • libXext-1.0.1-2.1.i386
  • libXext-devel-1.0.1-2.1.x86_64
  • libXext-devel-1.0.1-2.1.i386
  • libstdc++-4.1.2-48.x86_64
  • libstdc++-4.1.2-48.i386
  • libXtst-1.0.1-3.1.x86_64
  • libXtst-1.0.1-3.1.i386
  • libXau-1.0.1-3.1.x86_64
  • libXau-1.0.1-3.1.i386
  • libXdmcp-1.0.1-2.1.i386
  • libXrender-0.9.1-3.1.x86_64
  • libXrender-0.9.1-3.1.i386
  • glibc-2.5-47.i686
  • glibc-2.5-47.x86_64
  • libgcc-4.1.2-48.i386
  • libgcc-4.1.2-48.x86_64
  • libX11-1.0.3-11.x86_64
  • libX11-1.0.3-11.i386
  • libXi-1.0.1-3.1.x86_64
  • libXi-1.0.1-3.1.i386
  • alsa-lib-1.0.17-1.x86_64
  • alsa-lib-1.0.17-1.i386
  • glibc-2.5-47.i686
  • glibc-2.5-47.x86_64
  • redhat-lsb.i686
  • redhat-lsb.x86_64
  • tcsh-6.17-8.el6.x86_64

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:

  1. Log on to the system as root.

    The root user must be the owner of the /opt and /var directories.
  2. 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

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

    <swapfile_full_path>swap swap defaults 0 0

    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

  4. Restart the system.

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.

Preinstallation Tasks and Checklist

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:

  1. Log on as root and run the following commands:

    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:

  1. Open the file /etc/sysctl.conf file.
  2. Set the values of the parameters as given below:

Note: If higher values are specified for these parameters already, do not make any modifications.

  • kernel.msgmnb = 65536
  • kernel.msgmax = 65536
  • kernel.shmmax = 68719476736
  • kernel.shmall = 4294967296
  • kernel.sem = 250 1024000 250 4096
  • vm.max_map_count = 1000000

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:

  1. 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.

  2. Type the following command to view the IP address of the system:

    ifconfig

  3. 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.

  1. To create a new directory for installing SHR, run the following command:

    mkdir <directory name>

    For example: mkdir /tmp/HPSHR_9.4-parts

  2. 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

  3. Download the .tar file parts into the newly created temporary directory.

  4. 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

  • Users using the home directory with external applications are not supported (For Example: AD, NIS).
  • Always install SHR as root.

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

  • You can also install SHR in a domain as a domain/local user with administrator rights.
  • If you are installing SHR as a non-root user, the user and the home directory must be local to the system where installation is performed.
  • Ensure that system time does not change during the course of the installation. Make sure the system does not automatically transition to the daylight saving time during installation.
  • Do not install SHR from a network share. Because of the large size of the installation files, installation of SHR over the network is not supported.

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 SHR Server

Installing from the Command Line Console

  1. 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.

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

    ./HP-SHR_9.40_setup.bin -i console

  3. 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.

  4. Choose the locale in which you want to install SHR, and then press Enter. The installer shows the introductory information in the console.
  5. Press Enter.
  6. 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.

  7. The installer shows different installation options. Type 2 to select Custom HP Service Health Reporter Server, and then press Enter.
  8. 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.

  9. Type the FQDN of the system where you plan to install SAP BusinessObjects.
  10. 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.

    If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the SHR installation again.
  11. If the prerequisite check is successful, press Enter. The installer shows preinstallation summary in the console.

  12. 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.

  13. 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:

  1. 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.

  2. Run the following command:

    sh rollback-utility.sh

To perform the post-installation configuration tasks, see the HP Service Health Reporter Configuration Guide.

Installing Sybase IQ Server

Installing from the Command Line Console

  1. 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.

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

    ./HP-SHR_9.40_setup.bin -i console

  3. 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.

  4. The Choose Locale section appears. Choose the locale in which you want to install SHR, and then press Enter.
  5. The installer shows the introductory information in the console. Press Enter.
  6. 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.

  7. The installer shows different installation options. Type 2 to select Custom HP Service Health Reporter Server and press Enter.
  8. 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.

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

    If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the SHR installation again.
  10. If the prerequisite check is successful, press Enter

  11. 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.

  12. 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:

  1. 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.

  2. Run the following command:

    sh rollback-utility.sh

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

Installing SAP BusinessObjects Server

Installing from the Command Line Console

  1. 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.

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

    ./HP-SHR_9.40_setup.bin -i console

  3. 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.

  4. The Choose Locale section appears. Choose the locale in which you want to install SHR, and then press Enter.
  5. The installer shows the introductory information in the console. Press Enter.
  6. 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.

  7. The installer shows different installation options. Type 2 to select Custom HP Service Health Reporter Server and press Enter.
  8. 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.

  9. Enter the details of the Sybase IQ database that you plan to install or have already installed.
  10. 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.

    If the prerequisite check displays any missing libraries, check the list of missing libraries from the location /tmp/SHR-Missing-Patches.txt and install them. Start the SHR installation again.
  11. If the prerequisite check is successful, press Enter

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

    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.

  13. 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:

  1. 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.

  2. 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.

Installing HP Service Health Reporter (Unsupported)

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.

Validating SHR Installation

After you install the SHR software, verify if the product is working properly.

Perform the following to verify the success of installation:

  1. Log on to the SHR system.

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

  3. Type services.msc in the Open field, and then press ENTER. The Services window appears.

  4. 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:

  1. Go to Start and type Central Configuration Manager in Search. Double click on Central Configuration Manager and the window appears.

  2. Log on to the Central Management Console.

  3. From the drop down select Servers.

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

Perform the following to verify the success of installation on Linux operating system:

  1. Log on as root.
  2. 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:

    1. su - SHRBOADMIN
    2. cd /opt/HP/BSM/BO/bobje
    3. sh ccm.sh -display

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

Validating SHR Installation

After you install the SHR software, verify if the product is working properly.

Perform the following to verify the success of installation:

  1. Log on to the SHR system.

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

  3. Type services.msc in the Open field, and then press ENTER. The Services window appears.

  4. 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:

  1. Click Start > Programs > BusinessObjects XI 3.1 > BusinessObjects Enterprise > Central Configuration Manager. The Central Configuration Manager window appears.

  2. Log on to the Central Management Console.

  3. From the drop down select Servers.

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

Validating SHR Installation

Perform the following to verify the success of installation on Linux operating system:

  1. Log on as root.
  2. 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:

    1. su - SHRBOADMIN
    2. cd /opt/HP/BSM/BO/bobje
    3. 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.

Installing the SHR Data Collector on a Remote System (Optional)

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.

Installing the SHR Data Collector on a Remote System (Optional)

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.

Enabling SHR to Coexist with the HP Operations Agent (Optional)

If you want to install SHR and install HP Operations agent on the same system, you must perform the following additional configuration steps:

  1. Install HP Operations agent on the SHR Application system.

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

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

    ovcert -list

    The list of certificates installed on the system is displayed.

  4. Follow these steps:

  5. Run the following command on the SHR Application system:

    ovc -restart
  6. 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:

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

  8. 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
  9. Run the following command on the SHR system:

    ovc -restart

Enabling SHR to Coexist with the HP Operations Agent (Optional)

If you want to install SHR and install HP Operations agent on the same system, you must perform the following additional configuration steps:

  1. Install HP Operations agent on the SHR Application system.

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

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

    ovcert -list

    The list of certificates installed on the system is displayed.

  4. Follow these steps:

  5. Run the following command on the SHR Application system:

    ovc -restart
  6. 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:

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

  8. 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
  9. Run the following command on the SHR Application system:

    ovc -restart

Enabling SHR Collector on a Remote System to Coexist with the HP Operations Agent (Optional)

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:

  1. Install SHR collector on the remote system with HP Operations agent on the same system.

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

  3. 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.

  4. Follow these steps:

  5. The Flexible Management policy that was created for SHR Application system, can be used for SHR remote collector system.
  6. 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.

  7. Manually copy the exported certificate onto the SHR collector system.

  8. 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.

  9. Run the following command on the SHR collector system:

    ovc -restart

Enabling SHR Collector on a Remote System to Coexist with the HP Operations Agent (Optional)

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:

  1. Install SHR collector on the remote system with HP Operations agent on the same system.

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

  3. 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.

  4. Follow these steps:

  5. The Flexible Management policy that was created for SHR Application system, can be used for SHR remote collector system.
  6. 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.

  7. Manually copy the exported certificate onto the SHR collector system.

  8. 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.

  9. Run the following command on the SHR collector system:

    ovc -restart

Upgrading HP Service Health Reporter

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:

  1. Click Start > Run to open the Run prompt.

  2. Type CMD and press Enter. The command prompt window appears.

  3. 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

  4. Download the .tar file parts into the temporary folder that you created in the previous step.

    For example: C:\temp\HPSHR_9.4-parts.

  5. 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

  6. 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:

  1. 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.

  2. Ensure that the Management database password for postgres user is the default password. If the password is changed, make sure that you change it back to the default.
  3. Stop all SHR services using the following steps:

    1. Log on to the SHR system
    2. Open the Services window
    3. Stop the following services:

      • HP_PMDB_Platform_Administrator
      • HP_PMDB_Platform_Collection
      • HP_PMDB_Platform_DB_Logger
      • HP_PMDB_Platform_Timer
      • HP_PMDB_Platform_IM
      • HP_PMDB_Platform_PostgreSQL
      • HP_PMDB_Platform_Message_Broker
      • HP_PMDB_Platform_Sybase (In Custom Installation, stop this service before upgrading the Sybase IQ server)
      • Sybase IQ Agent 15.4 Service (In Custom Installation, stop this service before upgrading the Sybase IQ server)
      • Business Objects Webserver Service (In Custom Installation, stop this service before upgrading the SAP BusinessObjects server)
  4. Open Windows Task Manager, go to the Processes tab:

    • If the iqsrv15 process is running, select it and click End Process. (In Custom Installation, stop this service before upgrading the Sybase IQ server)
    • If the abcloadNrun processes are running, wait until they complete or, select and click End Process Tree.
  5. Run the following command to verify whether all the required services and processes are stopped:

    %PMDB_HOME%\DR\SHRServiceCheck.bat

  6. 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.

    • If SHR and SAP BusinessObjects are in same system, ensure that there is a 20 GB disk space available for upgrade.
    • If SHR and SAP BusinessObjects are in separate systems, then there must be a free disk space of 10 GB on each system to perform 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:

    • System 1: Sybase IQ.
    • System 2: SHR and SAP BusinessObjects.

    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:

    1. From the SHR installer media, browse to the \packages folder.
    2. Copy the following file to the remote system where data collector is installed.

      • For Windows: HP-SHR-09.40-RemoteCollector.zip
      • For Linux: HP-SHR-09.40-RemoteCollector.tar.gz
    3. Extract the contents and run the HP-SHR-RemotePoller_9.40_setup file.
    4. Follow instructions on the wizard to complete the upgrade.
  • In the last step while performing the upgrade, clear the Force repair of already installed component packages check box and click Upgrade.

Upgrade steps

  1. From the SHR media, run the following file:

    HP-SHR_9.40_setup.exe

    The set up files are extracted.

  2. Select the language in which you want to install SHR, and click OK.

    The HP Service Health Reporter 9.40 Software Installer wizard appears.

  3. 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.

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

  5. 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.

  6. The Introduction (Upgrade) page opens. Review the summary, and click Next.

  7. In Pre-Upgrade Summary page, click Upgrade.

  8. After the upgrade is complete, click Done.

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.

  • HP PMDB Platform Administrator Service
  • HP PMDB Platform Collection Service

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.

Upgrading HP Service Health Reporter

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.

  1. To create a new directory for installing SHR, run the following command:

    mkdir <directory name>

    For example: mkdir /tmp/HPSHR_9.4-parts

  2. 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

  3. Download the .tar file parts into the newly created temporary directory.

  4. 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:

  1. 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.

  2. Ensure that the Management database password for postgres user is the default password. If the password is changed, make sure that you change it back to the default
  3. Stop all SHR services using the following steps:

    1. Log on to the SHR system as root user.
    2. 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:

      • Log on to the system as root.
      • 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)

  4. 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.

  5. 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.

    • If SHR and SAP BusinessObjects are in same system, ensure that there is a 20 GB disk space available for upgrade.
    • If SHR and SAP BusinessObjects are in separate systems, then there must be a free disk space of 10 GB on each system to perform 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:

    • System 1: Sybase IQ.
    • System 2: SHR and SAP BusinessObjects.

    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:

    1. From the SHR installer media, browse to the \packages directory.
    2. Copy the following file to the remote system where data collector is installed.

      • For Windows: HP-SHR-09.40-RemoteCollector.zip
      • For Linux: HP-SHR-09.40-RemoteCollector.tar.gz
    3. Extract the contents and run the HP-SHR-RemotePoller_9.40_setup file.
    4. Follow instructions on the console to complete the 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.

  • HP PMDB Platform Administrator Service
  • HP PMDB Platform Collection Service

Install Add-on Content

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:

  1. Go to the location where you have installed SHR.

    For example: C:\HP-SHR\

  2. Open the addoncontent folder.
  3. Double-click on the required add-on content to install the files for Windows.

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
  • HPSHRHANACORE-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHANAApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHANAETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
SAP
  • HPSHRSAPApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

  • HPSHRSAPCore-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

  • HPSHRSAPETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

Hadoop
  • HPSHRHadoopCORE-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHadoopApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHadoopETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
Vertica
  • HPSHRVerticaCORE-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRVerticaApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRVerticaETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

Install Add-on Content

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:

  1. Go to the location where you have installed SHR.

    For example: C:\HP-SHR\

  2. Open the addoncontent folder.
  3. Double-click on the required add-on content to install the files for Windows.

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
  • HPSHRHANACORE-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHANAApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHANAETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
SAP
  • HPSHRSAPApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

  • HPSHRSAPCore-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

  • HPSHRSAPETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

Hadoop
  • HPSHRHadoopCORE-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHadoopApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHadoopETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
Vertica
  • HPSHRVerticaCORE-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRVerticaApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRVerticaETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

Install Add-on Content

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:

  1. Go to the location where you have installed SHR.

    For example: C:\HP-SHR\

  2. Open the addoncontent folder.
  3. Double-click on the required add-on content to install the files for Windows.

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
  • HPSHRHANACORE-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHANAApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHANAETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
SAP
  • HPSHRSAPApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

  • HPSHRSAPCore-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

  • HPSHRSAPETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

Hadoop
  • HPSHRHadoopCORE-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHadoopApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRHadoopETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
Vertica
  • HPSHRVerticaCORE-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRVerticaApp-9.30.000-Win5.2_64.msiLinux2.6_64.rpm
  • HPSHRVerticaETL-9.30.000-Win5.2_64.msiLinux2.6_64.rpm

Post-Upgrade Task: Import Additional BSM Topology Views

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:

  • Oracle
  • Oracle WebLogic Server
  • IBM WebSphere Application Server
  • Microsoft SQL Server
  • Microsoft Exchange Server
  • Microsoft Active Directory
  • System Management
  1. 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:%PMDB_HOME%\Packages\DatabaseOracle\ETL_DBOracle_DBSPI.ap\source\cmdb_views

    For Linux:$PMDB_HOME/Packages/DatabaseOracle/ETL_DBOracle_DBSPI.ap/source/cmdb_views

    Oracle WebLogic Server J2EEApplication_OM.zip For Windows:%PMDB_HOME%\Packages\ApplicationServer\ETL_AppSrvrWLS_WLSSPI.ap\source\cmdb_views

     

    For Linux:$PMDB_HOME/Packages/ApplicationServer/ETL_AppSrvrWLS_WLSSPI.ap/source/cmdb_views

    IBM WebSphere Application Server J2EEApplication_OM.zip For Windows:%PMDB_HOME%\Packages\ApplicationServer\ETL_AppSrv rWBS_WBSSPI.ap\source\cmdb_views

     

    For Linux:$PMDB_HOME/packages/ApplicationServer/ETL_AppSrvrWBS_WBSSPI.ap/source/cmdb_views

    Microsoft SQL Server SHR_DBMSSQL_OM.zip For Windows: %PMDB_HOME%\Packages\DatabaseMSSQL\ETL_DBMSSQL_DBSPI.ap\source\cmdb_views

     

    For Linux: $PMDB_HOME/Packages/DatabaseMSSQL/ETL_DBMSSQL_DBSPI.ap/source/cmdb_views

    Microsoft Exchange Server SHR_Exchange_OM.zip For Windows:%PMDB_HOME%\Packages\ExchangeServer\ETL_Exchange_Server2007.ap\source\cmdb_views

     

    For Linux:$PMDB_HOME/Packages/ExchangeServer/ETL_Exchange_Server2007.ap/source/cmdb_views

    Microsoft Active Directory SHR_ActiveDirectory_OM.zip For Windows:%PMDB_HOME%\Packages\ActiveDirectory\ETL_AD_ADSPI.ap\source\cmdb_views

     

    For Linux:$PMDB_HOME/Packages/DatabaseOracle/ActiveDirectory/ETL_AD_ADSPI.ap/source/cmdb_views

    System Management SM_BSM9_Views.zip For Windows:%PMDB_HOME%\Packages\SystemManagement\ETL_SystemManagement_PA.ap\source\cmdb_views

     

    For Linux:$PMDB_HOME/Packages/SystemManagement/ETL_SystemManagement_PA.ap/source/cmdb_views

  2. Move all the view files to the BSM system.
  3. Launch the BSM console in a web browser.
  4. Log on as administrator, and then click Administration > RTSM Administration.
  5. Click Administration > Package Manager.
  6. Click Deploy Packages to Server (from local disk).
  7. Click the Add icon. The Deploy Package to Server (from local disk) dialog box opens.
  8. Browse to the location of the Content Pack zip files, select the required files, and then click Open.

Next Steps

Task: Start the Sybase IQ Database

On the Linux system, run the following commands:

  1. cd /etc/init.d
  2. 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:

  1. 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.

  2. Browse to the {topaz_home}\Conf folder.

  3. 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:

  1. On the SHR system, click Start > Run. The Run dialog box appears.
  2. In the Open field, type services.msc. The Services window appears.

  3. On the right pane, right-click HP_PMDB_Platform_Administrator, and then click Restart.

  4. Close the Services window.

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.

Next Steps

Task: Start the Sybase IQ Database

On the Linux system, run the following commands:

  1. cd /etc/init.d
  2. 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:

  1. 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.

  2. Browse to the {topaz_home}\Conf folder.

  3. 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:

  1. On the SHR system, click Start > Run. The Run dialog box appears.
  2. In the Open field, type services.msc. The Services window appears.

  3. On the right pane, right-click HP_PMDB_Platform_Administrator, and then click Restart.

  4. Close the Services window.

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.

Preconditions to Uninstalling HP Service Health Reporter

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:

  1. Browse to the %PMDB_HOME%\scripts\Sybase folder.
  2. Open IQ_backup_full.sql with the Notepad application.
  3. 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:

  • Core_Domain
  • VirtualEnvPerf_Domain
  • VirtualEnvPerf_Domain_VMWare
  • SysPerf_Domain
  • vCenter Collector Content Pack

Components when RTSM is the topology source:

  • SysPerf_ETL_PerformanceAgent (optional, only for standalone hosts)
  • VirtualEnvPerf_ETL_HyperV_PerformanceAgent (optional, only for HyperV hosts)

Components when HPOM is the topology source:

  • SysPerf_ETL_PerformanceAgent (optional, only for standalone hosts)
  • VirtualEnvPerf_ETL_HyperV_PerformanceAgent (optional, only for HyperV hosts)

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:

  1. Launch the following URL:

    http://<SHR_Server_FQDN>:21411

  2. 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.

  3. On the left pane, click Administration and then click Deployment Manager. The Deployment Manager page opens.
  4. 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.

  5. Click OK.

    You have successfully uninstalled the Content Packs.

Preconditions to Uninstalling HP Service Health Reporter

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:

  1. Browse to the $PMDB_HOME\scripts\Sybase directory.
  2. Open IQ_backup_full.sql with the Notepad application.
  3. 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:

  • Core_Domain
  • VirtualEnvPerf_Domain
  • VirtualEnvPerf_Domain_VMWare
  • SysPerf_Domain
  • vCenter Collector Content Pack

Components when RTSM is the topology source:

  • SysPerf_ETL_PerformanceAgent (optional, only for standalone hosts)
  • VirtualEnvPerf_ETL_HyperV_PerformanceAgent (optional, only for HyperV hosts)

Components when HPOM is the topology source:

  • SysPerf_ETL_PerformanceAgent (optional, only for standalone hosts)
  • VirtualEnvPerf_ETL_HyperV_PerformanceAgent (optional, only for HyperV hosts)

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:

  1. Launch the following URL:

    http://<SHR_Server_FQDN>:21411

  2. 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.

  3. On the left pane, click Administration and then click Deployment Manager. The Deployment Manager page opens.
  4. 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.

  5. Click OK.

    You have successfully uninstalled the Content Packs.

Uninstalling HP Service Health Reporter

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:

  1. Skip this step if Sybase IQ is installed on a remote system. Manually stop the Sybase IQ processes.

    1. From the Services window, stop the HP PMDB Platform Sybase service.
    2. Open Windows Task Manager, go to the Processes tab, and then end the following processes:

      •  iqsrv15.exe
      • dbisql.exe 
  2. 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.

  3. Click Continue. The Application Maintenance page opens.

  4. 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.

  5. Click Uninstall. The Uninstalling page opens.
  6. After the uninstallation is completed, the Delete dialog box opens.
  7. Click Yes to delete the SHR directory. The Uninstall Complete page opens.
  8. Click Done to complete the uninstallation.
  9. Click Yes in the System Restart message box to restart your system.
  10. Browse to the SHR directory and check that the SHR database directories have been deleted. If the folders exist, delete them manually.

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.

Uninstalling Remote Sybase IQ

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.

  1. Log on to the remote Sybase IQ system.
  2. Manually stop the Sybase IQ processes.

    1. From the Services window, stop the HP PMDB Platform Sybase service.
    2. Open Windows Task Manager, go to the Processes tab, and ensure that the following processes are killed:

      • iqsrv15.exe
      • dbisql.exe
  3. From the Services window, start the HP PMDB Platform Sybase service.
  4. Follow these steps:
    • Click Start > Programs > Administrative Tools > Services. The Services window opens.
    • Right-click Sybase IQ Agent 15.4 and then click Stop.
    • Right-click the Sybase IQ service that you created and then click Stop.
    • Open the command prompt.
    • Go to the %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\

  5. Start the HP Software Installer.
    1. Click Start > Settings > Control Panel.
    2. Click Add or Remove Programs in the Control Panel window.
    3. In the Add or Remove Programs dialog box, click Service Health Reporter SybaseIQ, and then click Change/Remove.

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.

  1. Click Continue. The Application Maintenance page opens.
  2. Under Maintenance Selection, make sure that Uninstall is selected and then click Next. The Pre-Uninstall Summary page opens.

  3. Click Uninstall. The Uninstalling page opens.

After the uninstallation is completed, the Delete dialog box appears.

  1. Click Yes to delete the Service Health Reporter directory. The Uninstall Complete page opens.
  2. Click Done to complete the uninstallation.
  3. Browse to Sybase IQ directory and check if the HP-SHR folder has been deleted. If the folder exists, manually delete it.
  4. Click Yes in the System Restart message box to restart your system.

You successfully uninstalled the Sybase IQ server from your remote system.

Uninstalling SHR Manually

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

  1. Log on to the host system as administrator.
  2. Click Start > Run.The Run dialog box opens.
  3. Type services.msc in the Open field, and then press ENTER. The Services window opens.
  4. Right-click the following services and select Stop to stop the service:

    • HP PMDB Platform Administrator
    • HP PMDB Platform IM
    • HP PMDB Platform DB Logger
    • HP PMDB Platform Collection
    • HP PMDB Platform Timer
    • HP_PMDB_Platform_PostgreSQL - PostgreSQL Server 9.0
    • HP PMDB Platform Sybase
    • Sybase IQ Agent 15.4

    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.

  5. Close the Services window.

Task 2: Remove SAP BusinessObjects and PostgreSQL

  1. On the Windows desktop, click Start > Settings > Control Panel.
  2. Click Add or Remove Programs in the Control Panel window.

  3. 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

  4. Follow the instructions in the uninstallation wizard to complete the uninstallation.
  5. In the Add or Remove Programs dialog box, click PostgreSQL 9.0, and then click Change/Remove.
  6. Follow the instructions in the uninstallation wizard to complete the uninstallation.

Task 3: Remove Sybase IQ

  1. From the Services window, stop the HP PMDB Platform Sybase service.
  2. Open Windows Task Manager, go to the Processes tab, and then end the following processes:

    iqsrv15.exe

    iqsrv15.exe

  3. On the Windows desktop, click Start > Settings >Control Panel.
  4. Click Add or Remove Programs in the Control Panel window.
  5. Click Sybase IQ Server Suite 15.4 ESD 4 (64-bit) in the Add or Remove Programs window, and then click Change/Remove to remove the Sybase IQ application.
  6. In the Sybase IQ uninstallation wizard, click Next on the Welcome page.
  7. Ensure that the features that you want to remove are listed on the Pre-Uninstallation Summary page, and then click Next.
  8. Click Next and then click Uninstall.
  9. On the Delete User Files page, select the Delete All of These Files check box, and click Next.
  10. Click Done to complete the uninstallation process.
  11. Select the Yes, restart my computer option and then click Finish to restart your system.

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.

  1. On the Windows desktop, click Start > Run.
  2. In the Run dialog box, type regedit and press ENTER. The Registry Editor window opens.
  3. Expand HKEY_LOCAL_MACHINE, expand Software, and then expand Hewlett-Packard.
  4. Click a folder and note the package name and the product code.

Task 5: Remove the SHR components

  1. To uninstall the components, on the Windows desktop, click Start > Run.
  2. In the Run dialog box, type cmd and press ENTER. The Command Prompt window opens.
  3. 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

  1. In the Control Panel window, double-click System. The System Properties dialog box opens.
  2. Click the Advanced tab, and then click the Environment Variables button. The Environment Variables dialog box opens.
  3. Delete the following variables:

    • IQPORT
    • SYBASE
    • SYBROOT

Task 7: Remove the Service Health Reporter Folders

  1. Browse to the Service Health Reporter install directory.
  2. Delete all the folders.

    Once all the above tasks are performed, restart your system.

Uninstalling a Collector Installed on a Remote System

To remove the collector application, follow these steps:

  1. 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.

  2. 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.

  3. Click Continue. The Application Maintenance page opens.
  4. 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.

  5. Click Uninstall. The Uninstalling page opens.
  6. After the uninstallation is completed, the Delete dialog box appears.
  7. Click Yes to delete the Remote Collector directory. The Uninstall Complete page opens.
  8. Click Done to complete the uninstallation.

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:

  1. Log on to the Administration Console.
  2. Go to the Topology Source > Service Definition tab.
  3. For each definition that is set up with the collector that you uninstalled, follow these steps:

    1. Click Configure.
    2. If the Collection Station property is set to the uninstalled collector, make necessary changes. (You can set the property to Local if no collectors are currently installed on remote systems.)
    3. Click Save.
    4. Click OK.
  4. Go to the Collection Configuration tab.
  5. For each data source, delete the connections that were configured with the collector that you uninstalled.
  6. Go to the Administration tab, and then go to the Collection Configuration page.
  7. Delete the uninstalled collector.

Post Uninstalling SHR

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:

  1. 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.

  2. 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.

Uninstalling Remote Sybase IQ

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.

  1. Log on to the remote Sybase IQ system.
  2. Manually stop the Sybase IQ processes.

    1. Run the following commands:

      • ps -ef|grep iqsrv15
      • ps -ef | grep dbisql
    2. Note down the process IDs displayed by the output of each command.
    3. 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.

  3. To uninstall SHR from the command line console, perform the following steps:

    1. Log on to the local system.
    2. At the new command prompt type the command

      /opt/OV/Uninstall/HP-SHR/setup.bin -i console
    3. Press 1 to continue uninstallation.
    4. A screen appears with pre-installation summary, press ENTER to continue.

      Note: The installer automatically checks and uninstalls the application packages.

    5. Follow the prompts to complete uninstallation.

    After uninstallation, some files may remain on the system. The residual files do not impact reinstallation of SHR on the same system.

  4. Browse to Sybase IQ directory and check if the HP-SHR folder has been deleted. If the folder exists, manually delete it.
  5. Restart your system. You successfully uninstalled the Sybase IQ server from your remote system.

Uninstalling SHR Manually

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

  1. 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
  2. Go to the following directory:

    /opt/HP/BSM/BO/bobje
  3. 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:

  1. Create a empty file and save the file as shrPkgList under the /tmp directory.
  2. With a text editor, add the following lines to the shrPkgList file:

    Note: Do not change the sequence while adding these lines to the shrPkgListfile.

    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
  3. 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.

Uninstalling SHR in the Console Mode

To uninstall SHR from the command line console, perform the following steps:

  1. Log on to the local system.
  2. At the new command prompt type the command

    /opt/OV/Uninstall/HP-SHR/setup.bin -i console
  3. Press 1 to continue uninstallation.
  4. A screen appears with pre-installation summary, press ENTER to continue.

    Note: The installer automatically checks and uninstalls the application packages.

  5. Follow the prompts to complete uninstallation.

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:

  • On Linux: /opt/HP/BSM
  • On Windows: The complete SHR installation directory.

You can also delete the /opt/OV directory if no other HP Software products are installed on the system.

Uninstalling a Collector Installed on a Remote System

To remove the collector application, follow these steps:

  1. 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.

  2. 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.

  3. 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.

  4. Click Enter to continue the uninstall, the Delete section appears.
  5. Follow the console instruction to delete the Remote Collector directory. The Uninstall Complete page appears.

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:

  1. Log on to the Administration Console.
  2. Go to the Topology Source > Service Definition tab.
  3. For each definition that is set up with the collector that you uninstalled, follow these steps:

    1. Click Configure.
    2. If the Collection Station property is set to the uninstalled collector, make necessary changes. (You can set the property to Local if no collectors are currently installed on remote systems.)
    3. Click Save.
    4. Click OK.
  4. Go to the Collection Configuration tab.
  5. For each data source, delete the connections that were configured with the collector that you uninstalled.
  6. Go to the Administration tab, and then go to the Collection Configuration page.
  7. Delete the uninstalled collector.

Post Uninstalling SHR

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:

  1. 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.

  2. Run the following command:

    sh rollback-utility.sh

Change the Default SAP BusinessObjects Database 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:

  1. Go to <BusinessObejcts installed drive>:\Program Files (x86)\Business Objects\SQLAnyWhere12\bin
  2. Open the dbisqlc application.
  3. Type the credentials as follows:

    User name = DBA.

    Password = pmdb_admin.

    Server name = BOE120SQLAW_<shrshorthostname>.

    Database name = BOE120.

  4. Run the following command in the sql window:

    ALTER USER <shrshorthostname> IDENTIFIED BY <new password>;

    ALTER USER DBA IDENTIFIED BY <new password>;

  5. Repeat the same steps for database BOE120_AUDIT.

After updating the password, follow these steps:

  1. Go to CCM from Start > All Programs > BusinessObjects XI 3.1 > BusinessObjects Enterprise > Central Configuration Manager
  2. Stop the Server Intelligence Agent (SIA); right-click and select Properties.
  3. Go to the Configuration tab, you may see a error pop up click OK to proceed, and then click Specify of BOE120.
  4. Click on the Update Data Source Settings .
  5. Click OK.
  6. Select SQL Anywhere (ODBC) and click OK.
  7. The Select Datasource window appears. Select Machine Data Source tab.
  8. Double-click DSN BOE120 and provide the password that was changed and click OK.
  9. Repeat from step 3 to 8 for BOE120_AUDIT database by selecting the BOE120_AUDIT.
  10. Start the SIA.

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:

  1. Log in to the system as root.
  2. Run the following command to switch to SHRBOADMIN user:

    su - SHRBOADMIN

  3. Go to /opt/HP/BSM/BO/bobje/SQLAW/Bin/.
  4. Run the following command:

    source /opt/HP/BSM/BO/bobje/setup/env.sh

  5. Run the following command:

    ./dbisqlc

    The credentials window appears. Click Cancel.

  6. Select Command tab, and then click Connect.... The Connect credentials window appears.
  7. Type the following details:

    1. USER ID = DBA.
    2. Password = pmdb_admin.
    3. Database Name = <shrshorthostname>BOE120.
    4. Server = <shrshorthostname>BOE120_SHR.
  8. Run the following command in the sql window:

    ALTER USER SHR IDENTIFIED BY <new password>;

    ALTER USER DBA IDENTIFIED BY <new password>;

  9. To modify the default password for BOE120_AUDIT, from Menu, click Command tab, and then click Connect....

  10. Type the following details:

    1. USER ID = DBA.
    2. Password = pmdb_admin.
    3. Database Name = <shrshorthostname>BOE120_AUDIT.
    4. Server = <shrshorthostname>BOE120_SHR.
  11. 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:

  1. Go to /opt/HP/BSM/BO/bobje.
  2. Run the following command:

    ./cmsdbsetup.sh

  3. Provide the SIA name as PRD_SHR and click on Enter.
  4. The prompt shows stop SIA. Type yes, and then click on Enter.
  5. The prompt asks you to update. Type update, and then click on Enter.
  6. Type yes and click Enter.
  7. Select SQL Anywhere or Type 2, and then click on Enter.
  8. Type DSN as<shrshorthostname>BOE120, and then click on Enter.
  9. Type user as SHR, and then click on Enter.
  10. Type the new password, which you changed recently, and then click on Enter.
  11. Run the following command:

    ./startservers

For BOE120_AUDIT perform the following:

  1. Go to /opt/HP/BSM/BO/bobje.
  2. Run the following command:

    ./cmsdbsetup.sh

  3. Provide the SIA name as PRD_SHR and click on Enter.
  4. The prompt shows stop SIA. Type yes, and then click on Enter.
  5. Select selectaudit option, and then click Enter.
  6. 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.

  7. Select SQL Anywhere or Type 2, and then click on Enter.
  8. Type the DSN as <shrshorthostname>BOE120_AUDIT.
  9. Type user as SHR, and then click on Enter.
  10. Type the new password, which you changed recently, and then click on Enter.
  11. 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:

  1. Go to the location /etc/init.d
  2. Open the script BobjEnterprise120.
  3. Go to the following line:

    $SU - "$BOBJEUSERNAME" -c "$BOBJEDIR/sawstop.sh DATABASEUID=SHR DATABASEPWD=pmdb_admin"

  4. Type the new password in place of pmdb_admin.

Change the Default SAP BusinessObjects Database 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:

  1. Go to <BusinessObejcts installed drive>:\Program Files (x86)\Business Objects\SQLAnyWhere12\bin
  2. Open the dbisqlc application.
  3. Type the credentials as follows:

    User name = DBA.

    Password = pmdb_admin.

    Server name = BOE120SQLAW_<shrshorthostname>.

    Database name = BOE120.

  4. Run the following command in the sql window:

    ALTER USER <shrshorthostname> IDENTIFIED BY <new password>;

    ALTER USER DBA IDENTIFIED BY <new password>;

  5. Repeat the same steps for database BOE120_AUDIT.

After updating the password, follow these steps:

  1. Go to CCM from Start > All Programs > BusinessObjects XI 3.1 > BusinessObjects Enterprise > Central Configuration Manager
  2. Stop the Server Intelligence Agent (SIA); right-click and select Properties.
  3. Go to the Configuration tab, you may see a error pop up click OK to proceed, and then click Specify of BOE120.
  4. Click on the Update Data Source Settings .
  5. Click OK.
  6. Select SQL Anywhere (ODBC) and click OK.
  7. The Select Datasource window appears. Select Machine Data Source tab.
  8. Double-click DSN BOE120 and provide the password that was changed and click OK.
  9. Repeat from step 3 to 8 for BOE120_AUDIT database by selecting the BOE120_AUDIT.
  10. Start the SIA.

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:

  1. Log in to the system as root.
  2. Run the following command to switch to SHRBOADMIN user:

    su - SHRBOADMIN

  3. Go to /opt/HP/BSM/BO/bobje/SQLAW/Bin/.
  4. Run the following command:

    source /opt/HP/BSM/BO/bobje/setup/env.sh

  5. Run the following command:

    ./dbisqlc

    The credentials window appears. Click Cancel.

  6. Select Command tab, and then click Connect.... The Connect credentials window appears.
  7. Type the following details:

    1. USER ID = DBA.
    2. Password = pmdb_admin.
    3. Database Name = <shrshorthostname>BOE120.
    4. Server = <shrshorthostname>BOE120_SHR.
  8. Run the following command in the sql window:

    ALTER USER SHR IDENTIFIED BY <new password>;

    ALTER USER DBA IDENTIFIED BY <new password>;

  9. To modify the default password for BOE120_AUDIT, from Menu, click Command tab, and then click Connect....

  10. Type the following details:

    1. USER ID = DBA.
    2. Password = pmdb_admin.
    3. Database Name = <shrshorthostname>BOE120_AUDIT.
    4. Server = <shrshorthostname>BOE120_SHR.
  11. 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:

  1. Go to /opt/HP/BSM/BO/bobje.
  2. Run the following command:

    ./cmsdbsetup.sh

  3. Provide the SIA name as PRD_SHR and click on Enter.
  4. The prompt shows stop SIA. Type yes, and then click on Enter.
  5. The prompt asks you to update. Type update, and then click on Enter.
  6. Type yes and click Enter.
  7. Select SQL Anywhere or Type 2, and then click on Enter.
  8. Type DSN as<shrshorthostname>BOE120, and then click on Enter.
  9. Type user as SHR, and then click on Enter.
  10. Type the new password, which you changed recently, and then click on Enter.
  11. Run the following command:

    ./startservers

For BOE120_AUDIT perform the following:

  1. Go to /opt/HP/BSM/BO/bobje.
  2. Run the following command:

    ./cmsdbsetup.sh

  3. Provide the SIA name as PRD_SHR and click on Enter.
  4. The prompt shows stop SIA. Type yes, and then click on Enter.
  5. Select selectaudit option, and then click Enter.
  6. 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.

  7. Select SQL Anywhere or Type 2, and then click on Enter.
  8. Type the DSN as <shrshorthostname>BOE120_AUDIT.
  9. Type user as SHR, and then click on Enter.
  10. Type the new password, which you changed recently, and then click on Enter.
  11. 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:

  1. Go to the location /etc/init.d
  2. Open the script BobjEnterprise120.
  3. Go to the following line:

    $SU - "$BOBJEUSERNAME" -c "$BOBJEDIR/sawstop.sh DATABASEUID=SHR DATABASEPWD=pmdb_admin"

  4. Type the new password in place of pmdb_admin.

Change the Default SAP BusinessObjects Database 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:

  1. Go to <BusinessObejcts installed drive>:\Program Files (x86)\Business Objects\SQLAnyWhere12\bin
  2. Open the dbisqlc application.
  3. Type the credentials as follows:

    User name = DBA.

    Password = pmdb_admin.

    Server name = BOE120SQLAW_<shrshorthostname>.

    Database name = BOE120.

  4. Run the following command in the sql window:

    ALTER USER <shrshorthostname> IDENTIFIED BY <new password>;

    ALTER USER DBA IDENTIFIED BY <new password>;

  5. Repeat the same steps for database BOE120_AUDIT.

After updating the password, follow these steps:

  1. Go to CCM from Start > All Programs > BusinessObjects XI 3.1 > BusinessObjects Enterprise > Central Configuration Manager
  2. Stop the Server Intelligence Agent (SIA); right-click and select Properties.
  3. Go to the Configuration tab, you may see a error pop up click OK to proceed, and then click Specify of BOE120.
  4. Click on the Update Data Source Settings .
  5. Click OK.
  6. Select SQL Anywhere (ODBC) and click OK.
  7. The Select Datasource window appears. Select Machine Data Source tab.
  8. Double-click DSN BOE120 and provide the password that was changed and click OK.
  9. Repeat from step 3 to 8 for BOE120_AUDIT database by selecting the BOE120_AUDIT.
  10. Start the SIA.

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:

  1. Log in to the system as root.
  2. Run the following command to switch to SHRBOADMIN user:

    su - SHRBOADMIN

  3. Go to /opt/HP/BSM/BO/bobje/SQLAW/Bin/.
  4. Run the following command:

    source /opt/HP/BSM/BO/bobje/setup/env.sh

  5. Run the following command:

    ./dbisqlc

    The credentials window appears. Click Cancel.

  6. Select Command tab, and then click Connect.... The Connect credentials window appears.
  7. Type the following details:

    1. USER ID = DBA.
    2. Password = pmdb_admin.
    3. Database Name = <shrshorthostname>BOE120.
    4. Server = <shrshorthostname>BOE120_SHR.
  8. Run the following command in the sql window:

    ALTER USER SHR IDENTIFIED BY <new password>;

    ALTER USER DBA IDENTIFIED BY <new password>;

  9. To modify the default password for BOE120_AUDIT, from Menu, click Command tab, and then click Connect....

  10. Type the following details:

    1. USER ID = DBA.
    2. Password = pmdb_admin.
    3. Database Name = <shrshorthostname>BOE120_AUDIT.
    4. Server = <shrshorthostname>BOE120_SHR.
  11. 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:

  1. Go to /opt/HP/BSM/BO/bobje.
  2. Run the following command:

    ./cmsdbsetup.sh

  3. Provide the SIA name as PRD_SHR and click on Enter.
  4. The prompt shows stop SIA. Type yes, and then click on Enter.
  5. The prompt asks you to update. Type update, and then click on Enter.
  6. Type yes and click Enter.
  7. Select SQL Anywhere or Type 2, and then click on Enter.
  8. Type DSN as<shrshorthostname>BOE120, and then click on Enter.
  9. Type user as SHR, and then click on Enter.
  10. Type the new password, which you changed recently, and then click on Enter.
  11. Run the following command:

    ./startservers

For BOE120_AUDIT perform the following:

  1. Go to /opt/HP/BSM/BO/bobje.
  2. Run the following command:

    ./cmsdbsetup.sh

  3. Provide the SIA name as PRD_SHR and click on Enter.
  4. The prompt shows stop SIA. Type yes, and then click on Enter.
  5. Select selectaudit option, and then click Enter.
  6. 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.

  7. Select SQL Anywhere or Type 2, and then click on Enter.
  8. Type the DSN as <shrshorthostname>BOE120_AUDIT.
  9. Type user as SHR, and then click on Enter.
  10. Type the new password, which you changed recently, and then click on Enter.
  11. 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:

  1. Go to the location /etc/init.d
  2. Open the script BobjEnterprise120.
  3. Go to the following line:

    $SU - "$BOBJEUSERNAME" -c "$BOBJEDIR/sawstop.sh DATABASEUID=SHR DATABASEPWD=pmdb_admin"

  4. Type the new password in place of pmdb_admin.

Appendix

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.

  1. Go to the media root.

    Media root is the directory where the contents of the SHR media (the .tar file) are extracted.

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

    ./HP-SHR_9.40_setup.bin -i console

  3. 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.

  4. Choose the locale in which you want to install SHR, and then press Enter. The installer shows the introductory information in the console.
  5. Press Enter.
  6. Review the license agreement details. Type Y to accept the agreement, and then press Enter.

  7. Open a new command line console and go to the directory /tmp/HP-SHR. Edit the script checkSpace.sh and add exit 0 at the beginning of the script. Close the console.
  8. Go to the console where the installer is initiated and continue with the installation steps. For the installation steps, see the Installation section in this guide.

Appendix B

Install SHR as non-root user

Follow these steps to install as a non-root user:

  1. Log on as root user.
  2. Run the command useradd to create a user.
  3. Update the sudoers file and provide all permission to the newly created user using the following command:

    sudo visudo

    Add the below lines:

    1. # shr is the user invoking installer
    2. shr ALL=(ALL) ALL
    3. # shrgroup for the user shr
    4. %shrgroup ALL=(ALL) ALL
    5. # shrgroup for the user shr
    6. %shrgroup ALL=(ALL) NOPASSWD: ALL
  4. Log on as newly created user in another command line console.
  5. 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).

  1. Go to the media root.

    Media root is the directory where the contents of the SHR media (the .tar file) are extracted.

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

    ./HP-SHR_9.40_setup.bin -i console

  3. 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.

  4. Choose the locale in which you want to install SHR, and then press Enter. The installer shows the introductory information in the console.
  5. Press Enter.
  6. Review the license agreement details. Type Y to accept the agreement, and then press Enter.

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

    • Line 44: if [ $(id -u) -eq 0 ]; then
    • Line 48: usermod -g root SHRBOADMIN
    • Line 98-102:
      • else
      • echo "Only root may add a user to the system">>$BOInstallLog

      • exit 2
      • fi

    Close this console.

  8. Go to the console where the installer is initiated and continue with the installation steps. For the installation steps, see the Installation section in this guide.

Appendix

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.

  1. Go to the media root.

    Media root is the directory where the contents of the SHR media (the .tar file) are extracted.

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

    ./HP-SHR_9.40_setup.bin -i console

  3. 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.

  4. Choose the locale in which you want to install SHR, and then press Enter. The installer shows the introductory information in the console.
  5. Press Enter.
  6. Review the license agreement details. Type Y to accept the agreement, and then press Enter.

  7. Open a new command line console and go to the directory /tmp/HP-SHR. Edit the script checkSpace.sh and add exit 0 at the beginning of the script. Close the console.
  8. Go to the console where the installer is initiated and continue with the installation steps. For the installation steps, see the Installation section in this guide.

Appendix B

Install SHR as non-root user

Follow these steps to install as a non-root user:

  1. Log on as root user.
  2. Run the command useradd to create a user.
  3. Update the sudoers file and provide all permission to the newly created user using the following command:

    sudo visudo

    Add the below lines:

    1. # shr is the user invoking installer
    2. shr ALL=(ALL) ALL
    3. # shrgroup for the user shr
    4. %shrgroup ALL=(ALL) ALL
    5. # shrgroup for the user shr
    6. %shrgroup ALL=(ALL) NOPASSWD: ALL
  4. Log on as newly created user in another command line console.
  5. 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).

  1. Go to the media root.

    Media root is the directory where the contents of the SHR media (the .tar file) are extracted.

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

    ./HP-SHR_9.40_setup.bin -i console

  3. 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.

  4. Choose the locale in which you want to install SHR, and then press Enter. The installer shows the introductory information in the console.
  5. Press Enter.
  6. Review the license agreement details. Type Y to accept the agreement, and then press Enter.

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

    • Line 44: if [ $(id -u) -eq 0 ]; then
    • Line 48: usermod -g root SHRBOADMIN
    • Line 98-102:
      • else
      • echo "Only root may add a user to the system">>$BOInstallLog

      • exit 2
      • fi

    Close this console.

  8. Go to the console where the installer is initiated and continue with the installation steps. For the installation steps, see the Installation section in this guide.

Troubleshooting

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:

  1. From the file /tmp/SHR-Missing-Patches.txt get the list of missing libraries.
  2. Install the missing libraries.
  3. Re-initiate SHRinstallation.

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:

  1. From the file /tmp/SHR-Missing-Patches.txt get the list of missing libraries.
  2. Install the missing libraries.
  3. Re-initiate SHRinstallation.

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:

  1. Change system date to current.
  2. Apply the permanent license.

    When the system date is changed by more than three months, the license expires.

  3. Restart Admin service, Tomcat server, and SAP BusinessObjects servers.
  4. Log on and perform the post configuration again.

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:

  1. Change system date to current.
  2. Apply the permanent license.

    When the system date is changed by more than three months, the license expires.

  3. Restart Admin service, Tomcat server, and SAP BusinessObjects servers.
  4. Log on and perform the post configuration again.

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:

  1. Right-click My Computer, and then click Properties.
  2. Click the Advanced tab.
  3. Click Environment Variables.
  4. In the System Variable group, select Path.
  5. Click Edit and add the string %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:

  1. Right-click My Computer, and then click Properties.
  2. Click the Advanced tab.
  3. Click Environment Variables.
  4. In the System Variable group, select Path.
  5. Click Edit and add the string %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:

  1. Start the installation wizard and review the Pre-Install Summary.
  2. Select the Force repair of already installed component packages and click Install.
  3. If the reinstall fails then, click Rollback in the pop-up message. The installed components will be removed.
  4. Now perform a new installation.

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:

  1. Start the installation wizard and review the Pre-Install Summary.
  2. Select the Force repair of already installed component packages and click Install.
  3. If the reinstall fails then, click Rollback in the pop-up message. The installed components will be removed.
  4. Now perform a new installation.

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:

  1. Click Start > Run. The Run dialog box appears.
  2. In the Open box, type regedit. The Registry Editor window appears.

  3. On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.

  4. On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:

    • MaxUserPort = 65535 (decimal)
    • MaxFreeTcbs = 65535 (decimal)

    • MaxHashTableSize = 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:

  1. Click Start > Run. The Run dialog box appears.
  2. In the Open box, type regedit. The Registry Editor window appears.

  3. On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.

  4. On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:

    • MaxUserPort = 65535 (decimal)
    • MaxFreeTcbs = 65535 (decimal)

    • MaxHashTableSize = 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:

  1. Log on to the collector system.

  2. Run the following command:

    ovcoreid

    Note down the ID displayed in the console.

  3. Log on to the SHR system.

  4. 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.

  5. Transfer the certificate file to the collector system.

  6. Log on to the collector system.
  7. 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:

  1. Log on to the collector system.

  2. Run the following command:

    ovcoreid

    Note down the ID displayed in the console.

  3. Log on to the SHR system.

  4. 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.

  5. Transfer the certificate file to the collector system.

  6. Log on to the collector system.
  7. 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.

  • Windows: %temp%/../HP-SHR_9.40_HPOvInstaller.txt
  • Linux: /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.

  • Windows: %temp%/../HP-SHR_9.40_HPOvInstaller.txt
  • Linux: /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.

  • Windows: %temp%/../HP-SHR_9.40_HPOvInstaller.txt
  • Linux: /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:

  1. Log on to the SHR system
  2. Open the Services window
  3. Start the Business Objects Webserver Service

  1. Log on to the system as root.
  2. 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.

Troubleshooting

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:

  1. From the file /tmp/SHR-Missing-Patches.txt get the list of missing libraries.
  2. Install the missing libraries.
  3. Re-initiate SHRinstallation.

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:

  1. From the file /tmp/SHR-Missing-Patches.txt get the list of missing libraries.
  2. Install the missing libraries.
  3. Re-initiate SHRinstallation.

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:

  1. Change system date to current.
  2. Apply the permanent license.

    When the system date is changed by more than three months, the license expires.

  3. Restart Admin service, Tomcat server, and SAP BusinessObjects servers.
  4. Log on and perform the post configuration again.

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:

  1. Change system date to current.
  2. Apply the permanent license.

    When the system date is changed by more than three months, the license expires.

  3. Restart Admin service, Tomcat server, and SAP BusinessObjects servers.
  4. Log on and perform the post configuration again.

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:

  1. Right-click My Computer, and then click Properties.
  2. Click the Advanced tab.
  3. Click Environment Variables.
  4. In the System Variable group, select Path.
  5. Click Edit and add the string %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:

  1. Right-click My Computer, and then click Properties.
  2. Click the Advanced tab.
  3. Click Environment Variables.
  4. In the System Variable group, select Path.
  5. Click Edit and add the string %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:

  1. Start the installation wizard and review the Pre-Install Summary.
  2. Select the Force repair of already installed component packages and click Install.
  3. If the reinstall fails then, click Rollback in the pop-up message. The installed components will be removed.
  4. Now perform a new installation.

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:

  1. Start the installation wizard and review the Pre-Install Summary.
  2. Select the Force repair of already installed component packages and click Install.
  3. If the reinstall fails then, click Rollback in the pop-up message. The installed components will be removed.
  4. Now perform a new installation.

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:

  1. Click Start > Run. The Run dialog box appears.
  2. In the Open box, type regedit. The Registry Editor window appears.

  3. On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.

  4. On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:

    • MaxUserPort = 65535 (decimal)
    • MaxFreeTcbs = 65535 (decimal)

    • MaxHashTableSize = 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:

  1. Click Start > Run. The Run dialog box appears.
  2. In the Open box, type regedit. The Registry Editor window appears.

  3. On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.

  4. On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:

    • MaxUserPort = 65535 (decimal)
    • MaxFreeTcbs = 65535 (decimal)

    • MaxHashTableSize = 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:

  1. Log on to the collector system.

  2. Run the following command:

    ovcoreid

    Note down the ID displayed in the console.

  3. Log on to the SHR system.

  4. 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.

  5. Transfer the certificate file to the collector system.

  6. Log on to the collector system.
  7. 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:

  1. Log on to the collector system.

  2. Run the following command:

    ovcoreid

    Note down the ID displayed in the console.

  3. Log on to the SHR system.

  4. 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.

  5. Transfer the certificate file to the collector system.

  6. Log on to the collector system.
  7. 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.

  • Windows: %temp%/../HP-SHR_9.40_HPOvInstaller.txt
  • Linux: /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.

  • Windows: %temp%/../HP-SHR_9.40_HPOvInstaller.txt
  • Linux: /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.

  • Windows: %temp%/../HP-SHR_9.40_HPOvInstaller.txt
  • Linux: /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:

  1. Log on to the SHR system
  2. Open the Services window
  3. Start the Business Objects Webserver Service

  1. Log on to the system as root.
  2. 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.

Troubleshooting

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:

  1. From the file /tmp/SHR-Missing-Patches.txt get the list of missing libraries.
  2. Install the missing libraries.
  3. Re-initiate SHRinstallation.

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:

  1. From the file /tmp/SHR-Missing-Patches.txt get the list of missing libraries.
  2. Install the missing libraries.
  3. Re-initiate SHRinstallation.

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:

  1. Change system date to current.
  2. Apply the permanent license.

    When the system date is changed by more than three months, the license expires.

  3. Restart Admin service, Tomcat server, and SAP BusinessObjects servers.
  4. Log on and perform the post configuration again.

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:

  1. Change system date to current.
  2. Apply the permanent license.

    When the system date is changed by more than three months, the license expires.

  3. Restart Admin service, Tomcat server, and SAP BusinessObjects servers.
  4. Log on and perform the post configuration again.

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:

  1. Right-click My Computer, and then click Properties.
  2. Click the Advanced tab.
  3. Click Environment Variables.
  4. In the System Variable group, select Path.
  5. Click Edit and add the string %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:

  1. Right-click My Computer, and then click Properties.
  2. Click the Advanced tab.
  3. Click Environment Variables.
  4. In the System Variable group, select Path.
  5. Click Edit and add the string %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:

  1. Start the installation wizard and review the Pre-Install Summary.
  2. Select the Force repair of already installed component packages and click Install.
  3. If the reinstall fails then, click Rollback in the pop-up message. The installed components will be removed.
  4. Now perform a new installation.

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:

  1. Start the installation wizard and review the Pre-Install Summary.
  2. Select the Force repair of already installed component packages and click Install.
  3. If the reinstall fails then, click Rollback in the pop-up message. The installed components will be removed.
  4. Now perform a new installation.

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:

  1. Click Start > Run. The Run dialog box appears.
  2. In the Open box, type regedit. The Registry Editor window appears.

  3. On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.

  4. On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:

    • MaxUserPort = 65535 (decimal)
    • MaxFreeTcbs = 65535 (decimal)

    • MaxHashTableSize = 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:

  1. Click Start > Run. The Run dialog box appears.
  2. In the Open box, type regedit. The Registry Editor window appears.

  3. On the left pane, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet, expand Services, expand Tcpip, and then click Parameters.

  4. On the right pane, right-click anywhere, point to New, and then click DWORD Value to add a new entry. Add the following entries:

    • MaxUserPort = 65535 (decimal)
    • MaxFreeTcbs = 65535 (decimal)

    • MaxHashTableSize = 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:

  1. Log on to the collector system.

  2. Run the following command:

    ovcoreid

    Note down the ID displayed in the console.

  3. Log on to the SHR system.

  4. 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.

  5. Transfer the certificate file to the collector system.

  6. Log on to the collector system.
  7. 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:

  1. Log on to the collector system.

  2. Run the following command:

    ovcoreid

    Note down the ID displayed in the console.

  3. Log on to the SHR system.

  4. 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.

  5. Transfer the certificate file to the collector system.

  6. Log on to the collector system.
  7. 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.

  • Windows: %temp%/../HP-SHR_9.40_HPOvInstaller.txt
  • Linux: /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.

  • Windows: %temp%/../HP-SHR_9.40_HPOvInstaller.txt
  • Linux: /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.

  • Windows: %temp%/../HP-SHR_9.40_HPOvInstaller.txt
  • Linux: /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:

  1. Log on to the SHR system
  2. Open the Services window
  3. Start the Business Objects Webserver Service

  1. Log on to the system as root.
  2. 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.