HP HP BSM Connector

For the Linux and Windows® operating systems

Software Version: 9.21

Customized output from:

Installation and Upgrade Guide

HP logo

Document Release Date: February 2013

Software Release Date: February 2013

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 2012-2013 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

AMD and the AMD Arrow symbol are trademarks of Advanced Micro Devices, Inc.

Google™ and Google Maps™ are trademarks of Google Inc.

Intel®, Itanium®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.

iPod is a trademark of Apple Computer, Inc.

Java is a registered trademark of Oracle and/or its affiliates.

Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

 
 
 
 

Installation and Upgrade Guide

About this manual

Welcome to the HP BSM Connector 9.21 Installation and Upgrade Guide. This guide enables you to specify the type of installation or upgrade that you want to perform, and then view or print a customized guide which includes only the requirements and tasks that apply to you.

Note: This manual may have been updated with important corrections or additional information after it was packaged with the installation media. Before you start the installation or upgrade, download the latest version of this guide from the HP Software Product Manuals web site: http://h20230.www2.hp.com/selfsolve/manuals

Start by choosing an installation type

Install HP BSM Connector 9.21
Upgrade from HP BSM Integration Adapter
Update HP BSM Connector 9.20 to 9.21
Uninstall HP BSM Connector 9.21
Silent installation without upgrade instructions

Choose the installation procedure that you want to perform from the options on the left.

An interactive installation presents a series of screens on which you make selections, enter information, and step through the installation process.

A silent installation is a script-driven installation process and does not require you to interact with the installation program screens.

Choose the operating system

Windows
Linux

BSM Connector is available for Windows and Linux operating systems.

Choose the operating system of the computer on which you are installing BSM Connector.

Specify advanced installation options

HP BSM environment with load balancer or reverse proxy
HP BSM Connector on an HPOM managed node

If the BSM environment uses a load balancer or reverse proxy and the load balancer or reverse proxy is configured for HTTPS communication only, you must manually configure BSM Connector for HTTPS communication.

You can install BSM Connector on HPOM managed nodes that have HP Operations Agent version 11.02 or lower installed. (After the installation, you can upgrade the agent to a higher version.) During the BSM Connector configuration, the primary management server of the agent changes from the HPOM management server to the BSM server. The configuration also generates the agent-based flexible management policy BSM Connector FlexMgmt Policy. Certain limitations exist.

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. Check that your selections are correct.

 

If any selections are not correct, click Change.

Introduction to BSM Connector

BSM Connector captures and forwards data from third-party systems to BSM.

The data transfer is controlled by policies that you define in BSM Connector. Policies capture the data sources and, if certain conditions apply, forward the collected data in the form of events or metrics to BSM. The policies can optionally also map the data to topology and create configuration items (CIs) and CI relationships in BSM. This enables BSM to associate the events and metrics it receives with CIs.

BSM Connector supports predefined integrations with these third-party systems:

  • Microsoft System Center Operations Manager (SCOM)
  • IBM Tivoli Enterprise Console (TEC)
  • Nagios

BSM Connector also supports predefined integrations with these HP products:

  • HP Network Node Manager i (NNMi)
  • HP ArcSight ESM
  • HP ArcSight Logger

Additional integrations can be obtained through HP Live Network; see the HP Live Network site: https://hpln.hp.com/group/bsm-integrations.

You can also develop custom integrations in BSM Connector.

For complete information about the features, capabilities and usage of BSM Connector, see the BSM Connector online help after you install BSM Connector. To access the help, click Help in the toolbar of the BSM Connector user interface.

Plan and prepare the deployment environment

This section describes requirements of the BSM Connector deployment environment.This information can help you understand where to install BSM Connector.

Check compatibility with BSM and related components

BSM Connector 9.21 requires the following:

  • BSM 9.2x

  • Operations Agent 11.02

    BSM Connector includes HP Operations Agent version 11.02. When BSM Connector is installed, HP Operations Agent is also installed unless an installation of HP Operations Agent version 11.02 already exists on the computer. In that case the existing HP Operations Agent 11.02 is used with BSM Connector, and no new version is installed.

    If an older installation of HP Operations Agent (version 8.53, 8.60, 11.00, or 11.01) exists on the computer, the BSM Connector installation program will upgrade it to 11.02.

    If a newer installation of HP Operations Agent (version 11.03 or higher) exists on the computer, BSM Connector 9.21 cannot be installed. You must first uninstall the newer version of HP Operations Agent, then install BSM Connector 9.21, and then upgrade the agent to the newer version that you want to use.

Obtain lightweight single sign-on (LW-SSO) information before you install

BSM Connector deployments can use lightweight single sign-on (LW-SSO) for the user authentication strategy, which allows the BSM Connector users to be managed in the same way as the BSM users and groups. LW-SSO is the recommended strategy for BSM.

The installation program prompts for the following LW-SSO information. You should obtain the information before installing BSM Connector if possible, however you can also specify it after installation.

Check the system requirements

You can install the HP BSM Connector 9.21 Service Pack on a computer that has HP BSM Connector 9.20 installed.

You can install the HP BSM Connector on a computer that meets the following system requirements:

Category Requirements
Processor

800 MHz or higher

Dual-core processor minimum, quad-core processor is recommended

Operating system
  • Windows Server 2003 R2 SP2 Standard Edition (32 bit)

  • Windows Server 2003 R2 SP2 Standard Edition (64 bit)

  • Windows Server 2003 R2 SP2 Enterprise Edition (32 bit)

  • Windows Server 2003 R2 SP2 Enterprise Edition (64 bit)

  • Windows Server 2008 SP2 Standard Edition (32 bit)

  • Windows Server 2008 SP2 Standard Edition (64 bit)

  • Windows Server 2008 SP2 Enterprise Edition (32 bit)

  • Windows Server 2008 SP2 Enterprise Edition (64 bit)

  • Windows Server 2008 R2 SP1 Standard Edition (64 bit)

  • Windows Server 2008 R2 SP1 Enterprise Edition (64 bit)

  • Red Hat Enterprise Linux AS 5.3 and later minor versions (64 bit)

  • Red Hat Enterprise Linux ES 5.3 and later minor versions (64 bit)

Memory

4 GB minimum, 8 GB or more is recommended

Free hard disk space

2 GB minimum, 10 GB or more is recommended

Installation media drive

If installing from DVD, a DVD-ROM drive or alternative method to read the BSM Connector installation media

BSM Connector user interface requirements
  • Internet Explorer 7.0, 8.0, 9.0

  • Firefox 10.0 ESR

  • Adobe Flash Player 10.1 or higher

  • If LW-SSO is used, browsers must be configured to accept cookies

Read the release notes

HP recommends that you read the BSM Connector and HP Operations Agent release notes before you start the installation or upgrade. The latest versions of the BSM Connector and HP Operations Agent release notes are available from the HP Software Product Manuals page at HP Software Support Online:

http://h20230.www2.hp.com/selfsolve/manuals

Uninstall BSM Integration Adapter

To prepare the upgrade of a BSM Integration Adapter, you uninstall BSM Integration Adapter:

  1. Log on to the host on which BSM Integration Adapter is installed.

  2. Open a command prompt or shell and type:

    ovc -stop IA WEB

  3. Uninstall BSM Integration Adapter 9.12 Service Pack as follows:

    1. From the Control Panel, choose Add or Remove Programs.

    2. Right-click HP BSM Integration Adapter 9.1 Integ. Adapt.<platform>09.12.061 and choose Uninstall.

    Run: rpm -e HPBsm912IA01

  4. Uninstall BSM Integration Adapter 9.10 as follows:

    1. From the Control Panel, choose Add or Remove Programs.

    2. Right-click HP BSM Integration Adapter and choose Uninstall.

    Alternatively, start the HP BSM Integration Adapter installer (you may have to load it from the product DVD) and choose the Remove/Uninstallation option.

    Start the Integration Adapter installer in GUI or console mode (you may have to load it from the product DVD), and choose the Remove/Uninstallation option.

After the BSM Integration Adapter is uninstalled, the state of the system is as follows:

  • All active policies are deactivated.

  • Policy files are still available in the policy store and will be reused by BSM Connector.

  • The users.properties and lwsso-config.xml configuration files remain on the system and can be reused by BSM Connector.

  • HP Operations Agent (including certificates) has been removed (unless the agent was installed separately before the BSM Integration Adapter).

  • OvXPL configuration values are still available.

  • HP Operations Agent remains; it was not removed by the BSM Integration Adapter uninstallation.

  • All active BSM Integration Adapter policies were deactivated; HPOM managed policies remain active.

  • BSM Integration Adapter policy files are still available in the policy store and will be reused by BSM Connector.

  • The users.properties and lwsso-config.xml configuration files remain on the system and can be reused by BSM Connector.

  • HP Operations Agent is still connected to a management server.

Optional. Install HP Operations Agent manually

BSM Connector installations include the HP Operations Agent. By default the agent installation uses the following folders on Windows operating systems:

  • Windows Server 2003:

    • Application files: C:\Program Files\HP\HP BTO Software\

    • Data files: C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\

  • Windows Server 2008:

    • Application files: C:\Program Files\HP\HP BTO Software\

    • Data files: C:\ProgramData\HP\HP BTO Software\

If you want to use different folders for the agent, you must install the agent manually, before you install BSM Connector.

To install the agent manually:

  1. Log on to the computer on which you will install BSM Connector.

  2. Insert the BSM Connector installation DVD into the computer, and then in a command prompt, navigate to the one of the following folders on the DVD:

    • On a 32-bit operating system:

      \Windows32_Setup\packages\operations_agent\

    • On a 64-bit operating system:

      \Windows64_Setup\packages\operations_agent\

  3. Type the following command to start the agent installation script:

    cscript oainstall.vbs -i -a -includeupdates -install_dir <install_dir> -data_dir <data_dir>

    Replace <install_dir> with the path of the folder for the agent application files.

    Replace <data_dir> with the path of the folder for agent data and configuration files.

    For more information about the agent installation script, type cscript oainstall.vbs.

The BSM Connector installation automatically detects the location of the agent.

Note: If you manually install the agent before you install BSM Connector, and later uninstall BSM Connector, the agent is not automatically uninstalled. In this situation, you can manually uninstall the agent.

Start the installation of BSM Connector 9.20

To start the BSM Connector 9.20 installation program in interactive mode, insert the installation DVD into the computer, and then in Windows Explorer double-click one of the following files:

  • On a 32-bit operating system:

    Windows32_Setup\BSMConnector_<version>_setup.exe

  • On a 64-bit operating system:

    Windows64_Setup\BSMConnector_<version>_setup.exe

The installation program begins.

To start the BSM Connector 9.20 installation program in interactive mode:

  1. Log on as root to the computer on which you want to install BSM Connector. Open a desktop session or export the display.

  2. Insert the installation DVD into the computer, and then mount it.

  3. Open a shell prompt and change to the following directory:

    /<DVD mount point>/Linux_Setup/

  4. Type the following command

    ./BSMConnector_<version>_setup.bin

    The installation program begins.

Choose a language

Choose the language used by the installation program. Click OK.

Read the introduction

Review the information on the Introduction panel. Click Next.

Review the license agreement

Review the license agreement. To continue, select I accept the terms of the License Agreement, and then click Next.

Check the installation folder

Specify the folder for the installation files; accept the default location, or click Browse to choose the desired parent folder. Click Next.

By default, this folder location is C:\BSMConnector\. You can specify a different parent folder for this folder, but the last subfolder name in the path must be BSMConnector. The path must not contain spaces.

The Product Customization screen is skipped, because on Linux you cannot change the installation directories. The directories are always as follows:

  • BSM Connector installation: /opt/HP/BSMConnector/

  • HP Operations Agent installation: /opt/OV/

  • HP Operations Agent data: /var/opt/OV/

Review the installation check results

Review the information on the Install Checks panel. This panel indicates whether there is enough space on the target host. If an error message appears, cancel the installation and increase the available disk space. Otherwise, click Next.

Review the pre-installation summary

Review the Pre-Install Summary panel, which lists the components being installed. All of the components are required. Click Install.

Install the software

The Installing panel is displayed which includes a progress bar showing the progress of this phase of the installation. It can take up to several minutes for the installation program to complete this phase.

Note: If you click Cancel during the installation, the installation begins to roll back. The roll back removes BSM Connector files, but does not remove HP Operations Agent files.

If you want to uninstall the HP Operations Agent, you have to uninstall the agent manually, after the BSM Connector roll back is complete.

Read the configuration wizard introduction

The Post-Install panel appears with the Please Wait message. After a few seconds, the HP BSM Connector Configuration Wizard is launched in a separate window. Click Next.

Configure deployment settings

Review the Settings panel.

  • Ports settings. Specify the ports at which the BSM Connector user interface is to run. Default: 30001 for the HTTP port, 30000 for the HTTPS port.

    Note: Record the port settings and host name of the BSM Connector. This information is needed to configure the integration of BSM Connector to BSM from the BSM user interface.

  • BSM Connector service settings. Specify the service name used by BSM Connector. Default: HP BSM Connector

    Also specify the user credentials to be used to manage the BSM Connector service. Select Use local system account to specify the Windows predefined LocalSystem account. This account has extensive privileges on the local computer, and has access to most system objects. When BSM Connector is running under the LocalSystem account, it attempts to connect to remote servers using the credentials of the remote servers as configured in BSM Connector.

    For more information about the LocalSystem account, see your Windows system documentation.

    Select Use this account: to enter a different user name and password that is used to run the BSM Connector service. These user credentials must already exist on the system and the user must have domain administration privileges and be granted Log On as a Service rights. This gives BSM Connector access privileges to access server data within the domain. Enter an account and password (and confirm the password) that can access the remote servers.

    To grant a user logon service access:

    1. In Windows Control Panel, double-click Administrative Tools.

    2. Double-click Local Security Policy, and select Local Policies > User Rights Assignment > Log On as a Service.

    3. Click Add User or Group, and specify the user you want to grant logon service access to, and click OK.

    4. Click OK to save the updated policy.

    Default: BSM Connector is installed to run as a LocalSystem account.

  • Start service. Starts the BSM Connector service automatically, once the installation program completes. Otherwise, you can start the BSM Connector service manually. See Perform optional post-installation steps. Default: Selected

  • Click Next.

Configure credentials

Specify the administrator user on the Credentials panel.

You must specify credentials for the BSM Connector administrator. You can optionally also specify Single Sign-On settings:

  • BSM Connector administration user settings. Specifies a local user account to become the BSM Connector administrator. This user can access the local BSM Connector instance only by logging on with these credentials, and cannot gain access to other BSM applications.
    Default user name: admin
    Default password: empty field (you must supply a password)

    Note: When you upgrade a BSM Integration Adapter, the configuration wizard sets the default User name and Password, using the values from the existing configuration. You can change the values if you want to use different credentials.

    Note: It is currently not possible to change the user name and password after you complete this configuration wizard.

    Note: You need this username and password when you configure the integration of BSM Connector to BSM from the BSM user interface.

  • Single Sign On settings. Specifies the lightweight single sign-on (LW-SSO) strategy, which is the default single sign-on authentication strategy for BSM. LW-SSO does not require an external computer for authentication. LW-SSO enables a user to log into BSM once and gain access to all BSM applications in the same domain without being prompted to log in again. If you configure BSM Connector to use LW-SSO, BSM users can launch the BSM Connector user interface without having to provide additional credentials. For more information about LW-SSO, see the BSM Platform Administration guide.

    To enable Single Sign On (SSO), check the Enable Single Sign On checkbox and specify the following:

    Domain name. Type the domain of the associated BSM gateway server. For more information about obtaining the domain name, see Obtain lightweight single sign-on (LW-SSO) information before you install . If you do not specify the domain name here, a default name is provided and you can modify it later. See Perform optional post-installation steps.

    Domain name. Type the domain of the associated BSM gateway server. For more information about obtaining the domain name, see Obtain lightweight single sign-on (LW-SSO) information before you install . If you do not specify the domain name here, a default name is provided and you can modify it later. See Installation and Upgrade Guide.

    Token key. Type the token key generated in the BSM Users and Permissions manager.

    Note: Single-sign on can only work if the token key that you type here is exactly the same as the token key on the BSM server. For more information about obtaining the token key, see Obtain lightweight single sign-on (LW-SSO) information before you install .

    Accessible BSM Groups/Roles. Type or accept the BSM users and roles that will have access to BSM Connector. Separate individual groups and roles with commas (for example, BSMC_ADMINS,SUPERUSER). Default: BSMC_ADMINS group and the SUPERUSER role. Enter DISABLED to indicate that group-based authentication is not used. For information about users and roles, see Obtain lightweight single sign-on (LW-SSO) information before you install

    Tip: You can also enter group and role names that contain spaces; for example: BSMC ADMINS.

    Note: When you upgrade a BSM Integration Adapter that has LW-SSO already configured, the configuration wizard sets the default Domain name, Token key, and Accessible BSM Groups/Roles using the values from the existing configuration.

  • Click Next.

Review the configuration summary

Review the Summary panel. Click Next.

Complete the configuration

Review the Done panel. Click the URL to access the BSM Connector user interface, or note it for future access. Click Finish.

Review the Done panel.

Open a separate shell prompt, and then start the BSM Connector processes by typing the following command:

/opt/HP/BSMConnector/start

You can then return to the Done panel and click the URL to access the BSM Connector user interface, or note it for future access. Click Finish

Close the installation wizard

Focus returns to the Installation Complete panel of the Installation program. Click Done.

Install the BSM Connector Service Pack 9.21

  1. Download the BSM Connector 9.21 Service Pack from http://support.openview.hp.com/selfsolve/patches.

  2. Extract the files from the zip file.

  3. Execute the extracted installer. It is not necessary to stop the BSM Connector serviceprocesses.

    The installation program begins and presents the installation wizard. Use the wizard to install the 9.21 Service Pack. The installation is complete when the Installation Complete page appears.

Start the BSM Connector service

The HP BSM Connector service is not started automatically after the installation. To start the service manually:

  1. Start the Windows Task Manager.

  2. Click the Services tab.

  3. Right-click the BSM Connector service and choose Start Service.

    The default BSM Connector service name is HP BSM Connector.

Configure the bsmc init script

BSM Connector provides an init script that must be integrated into the boot process so that the BSM Connector process starts automatically after a system reboot:

  1. Copy the init script bsmc to /etc/init.d:

    cp /opt/HP/BSMConnector/bin/bsmc /etc/init.d/bsmc.tmp

  2. Convert the script from DOS to UNIX format, for example:

    dos2unix /etc/init.d/bsmc.tmp /etc/init.d/bsmc

  3. Add execution rights to the script:

    chmod +x /etc/init.d/bsmc

  4. Register the script:

    chkconfig --add bsmc

  5. Usage:

    service bsmc <start|stop|restart|status>

Start BSM Connector

BSM Connector is not started automatically after the installation. To start BSM Connector manually, type:

/opt/HP/BSMConnector/start

Run the installation program in silent mode

A silent mode installation runs the installation program in the background without requiring you to navigate through the installation program dialogs. All required input comes from configuration parameters and assigned values that you specify in a response file in text format.

Tip: To run silent installations for different configurations, create multiple response files.

To install in silent mode, complete the following steps:

  1. Copy one of the following folders from the BSM Connector 9.20 installation DVD to the computer that you want to install the software on:

    • On a 32-bit operating system:

      \Windows32_Setup\

    • On a 64-bit operating system:

      \Windows64_Setup\

  2. Copy the following folder from the BSM Connector 9.20 installation DVD to the computer that you want to install the software on:

    \Linux_Setup\

  3. In your copy of the folder, open the ovinstallparams.ini file and modify it with the options you want specified during the silent installation. Be careful when editing the file so that the format is retained.

    The BSM Connector installation path (prodInstallDir=<Installation_path>) must not contain spaces or non-Latin characters in its name, and must end with a folder named BSMConnector (the folder name is case sensitive).

    The BSM Connector installation path (prodInstallDir=<Installation_path>) is set by default to /opt/HP/BSMConnector and cannot be changed.

  4. Run the BSM Connector 9.20 installer from the command line with the -i silent flag. For example:

    BSMConnector_<version>_setup.exe -i silent

    BSMConnector_<version>_setup.bin -i silent

  5. Download the BSM Connector 9.21 Service Pack from http://support.openview.hp.com/selfsolve/patches and extract the files from the zip file.

  6. Run the BSM Connector 9.21 Service Pack installer from the command line with the -i silent flag. For example:

    BSMConnector_<version>_setup.exe -i silent

    BSMConnector_<version>_setup.bin -i silent

  7. View the status of the installation by viewing the following log file:

    %temp%\..\HPOvInstaller\BSMConnector_<Version>\BSMConnector_<Version>_<TimeStamp>_HPOvInstallerLog.txt

    /tmp/HPOvInstaller/BSMConnector_<Version>/BSMConnector_<Version>_<TimeStamp>_HPOvInstallerLog.txt

    For example: BSMConnector_09.20.110_2012.02.19_09_36_HPOvInstallerLog.txt

  8. The HP BSM Connector service is not started automatically by the installation program. To start the service manually:

    1. Start the Windows Task Manager.

    2. Click the Services tab.

    3. Right-click the BSM Connector service and choose Start Service.

      The default BSM Connector service name is HP BSM Connector.

  9. BSM Connector provides an init script that must be integrated into the boot process so that the BSM Connector process starts automatically after a system reboot:

    1. Copy the init script bsmc to /etc/init.d:

      cp /opt/HP/BSMConnector/bin/bsmc /etc/init.d

    2. Add execution rights to the script:

      chmod +x /etc/init.d/bsmc

    3. Register the script:

      chkconfig --add bsmc

    Usage:

    service bsmc <start|stop|restart|status>

  10. BSM Connector is not started automatically by the installation program. To start BSM Connector manually, type one of the following commands:

    service bsmc start

    /opt/HP/BSMConnector/start

To uninstall in silent mode, run one of the following uninstall commands:

  • Uninstall the BSM Connector 9.21 Service Pack only:

    <BSM Connector installation folder>\installation\BSMConnector0921\bin\uninstall.bat -i silent

  • Uninstall BSM Connector 9.21 and 9.20:

    <BSM Connector installation folder>\installation\bin\uninstall.bat -i silent

  • Uninstall the BSM Connector 9.21 Service Pack only:

    /opt/OV/Uninstall/BSMConnector0921/setup.bin -i silent

  • Uninstall BSM Connector 9.21 and 9.20:

    /opt/HP/BSMConnector/installation/bin/uninstall.sh -i silent

Configure HP Operations Agent manually

You must configure HP Operations Agent manually if the BSM environment uses a load balancer or reverse proxy:

Configure certificates and flexible management on HPOM managed nodes

When you install BSM Connector on an HPOM managed node, you need certificates from the BSM server, and an agent-based flexible management policy. The agent-based flexible management policy enables HP Operations Agent to forward the collected data as follows:

  • The BSM server receives all events generated by BSM Connector policies that have the Type attribute set to BSMC_Message.

    The HPOM management server receives all events that do not have the Type attribute set to BSMC_Message.

    BSM Connector sets the event type attribute automatically to BSMC_Message. You can delete the value in a policy but BSM Connector inserts it again when you save the policy. The type attribute is available in the Advanced attributes tab of the policy editors.

  • The BSM server receives all metrics data.

  • The BSM server receives all topology data (both HP Operations Agent and DFM-discovered data).

To configure certificates and flexible management:

  1. Make sure the HPOM management server is connected to the BSM server. (For more information, see the topic "How to Create a Connection to an HPOM Server" in the BSM online help.)

  2. Remove the existing agent certificate on the BSM Connector computer as follows:

    1. Open a command prompt on the BSM Connector computer, and then type the following command:

      ovcert -list

      Open a shell prompt on the BSM Connector computer, and then type the following command:

      /opt/OV/bin/ovcert -list

      The command outputs a list of certificate IDs. For example:

      +---------------------------------------------------------+
      | Keystore Content                                        |
      +---------------------------------------------------------+
      | Certificates:                                           |
      |     2c3214a2-6964-755d-1520-b8b3f84d86e6 (*)            |
      +---------------------------------------------------------+
      | Trusted Certificates:                                   |
      |     CA_bc180332-d338-7557-0384-a10be68caa36             |
      +---------------------------------------------------------+
    2. Copy the first certificate ID, and use it in the following command:

      ovcert -remove <certificate ID>

      /opt/OV/bin/ovcert -remove <certificate ID>

      For example:

      ovcert -remove 2c3214a2-6964-755d-1520-b8b3f84d86e6

      /opt/OV/bin/ovcert -remove 2c3214a2-6964-755d-1520-b8b3f84d86e6

  3. Configure HP Operations Agent and generate a flexible management policy. Type the following command:

    %OvDataDir%\installation\HPOprIA\bsmc-conf.bat -s <bsm_hostname> -f -flexmgmt -omc_srv <om_hostname>

    /var/opt/OV/installation/HPOprIA/bsmc-conf.sh -s <bsm_hostname > -f -flexmgmt -omc_srv <om_hostname>

    Replace <bsm_hostname> with the fully qualified domain name (FQDN) of the BSM gateway server or load balancer (depending on your BSM deployment).

    Replace <om_hostname> with the FQDN of the HPOM management server.

  4. Log on to the BSM server as a user with administrative privileges, and grant the pending certificate request:

    1. Navigate to Admin > Operations Management > Setup > Certificate Requests.

    2. On the Certificate Requests tab, select the certificate request and then click the Grant itembutton.

    If the certificate request does not appear in the list, send another request using the following command on the BSM Connector computer:

    ovcert -certreq

    /opt/OV/bin/ovcert -certreq

  5. On the BSM Connector computer, update the trusted certificates store. Type the following commands:

    1. ovcert -updatetrusted

      /opt/ov/bin/ovcert -updatetrusted

      You should see the following message:

      INFO: Trusted certificate update was successful.

    2. ovc -restart

      /opt/OV/bin/ovc -restart

      The command should run for several seconds and then finish without displaying any error messages.

Upgrade flexible management configuration

The upgrade procedure depends on whether the BSM system to which the BSM Integration Adapter is reporting has also been upgraded to 9.2x.

Perform optional post-installation steps

This section contains some tasks that may be necessary after BSM Connector is installed.

Perform post-upgrade configuration

Perform the following procedures to complete the BSM Integration Adapter policy upgrade to BSM Connector and prepare them for use.

Uninstall BSM Connector on Windows

To uninstall the BSM Connector 9.21 Service Pack from a Windows computer:

  1. Start the uninstallation from the Control Panel in Windows:

    • Windows 2008

      Open Programs and Features, and then click View installed updates. Right-click HP BSMConnector 09.21.<version>, and select Uninstall.

    • Windows 2003

      Open Add or Remove Programs, and then select Show updates. Double-click HP BSMConnector 09.21.<version>.

  2. The Choose Locale screen displays. Choose the language and click OK.

  3. The BSM Connector Application Maintenance screen displays. Choose Uninstall, and click Next.

  4. The Pre-Uninstall Summary screen displays. Click Uninstall.

  5. The Uninstalling and then the Post-Uninstall screens display. Click Next.

  6. The Uninstall Complete screen displays. Click Done.

To uninstall BSM Connector 9.21 and 9.20 from a Windows computer:

  1. Make sure the BSM Connector is not in use. To check which BSM Connectors are being used:

    1. In the BSM user interface, choose Admin > Integrations > BSM Connector Integrations.

    2. In the Summary view, scan the Name column for all active BSM Connectors in the current deployment environment.

    3. If the BSM Connector that you want to delete appears in the list, remove it before continuing.

  2. From your desktop, choose All Programs > HP BSM Connector > Uninstall HP BSM Connector.

  3. The Choose Locale screen displays. Choose the language and click OK.

  4. The BSM Connector Application Maintenance screen displays. Choose Uninstall, and click Next.

  5. The Pre-Uninstall Summary screen displays. Click Uninstall.

  6. The Uninstalling and then the Post-Uninstall screens display. Click Next.

  7. The Uninstall Complete screen displays. Click Done.

The uninstallation procedure also uninstalls the HP Operations Agent, unless the agent was installed separately before BSM Connector. In this case, you can uninstall the agent manually.

Uninstall BSM Connector on Linux

To uninstall the BSM Connector 9.21 Service Pack from a Linux computer:

  1. Type one of the following commands:

    /opt/OV/Uninstall/BSMConnector0921/setup.bin

    Or:

    /opt/HP/BSMConnector/installation/BSMConnector0921/bin/uninstall.sh

  2. Respond to the prompts as required.

To uninstall BSM Connector 9.21 and 9.20 from a Linux computer:

  1. Make sure the BSM Connector is not in use. To check which BSM Connectors are being used:

    1. In the BSM user interface, choose Admin > Integrations > BSM Connector Integrations.

    2. In the Summary view, scan the Name column for all active BSM Connectors in the current deployment environment.

    3. If the BSM Connector that you want to delete appears in the list, remove it before continuing.

  2. Type the command /opt/HP/BSMConnector/installation/bin/uninstall.sh and respond to the prompts.

The uninstallation procedure also uninstalls the HP Operations Agent, unless the agent was installed separately before BSM Connector. In this case, you can uninstall the agent manually.

Integrate BSM Connector with BSM

Each BSM Connector instance must be configured to integrate with a BSM Gateway Server:

For full details about how to configure a BSM Connector integration server, see the BSM online help or the BSM Application Administration Guide.

  1. On the BSM Connector server, close any running instances of the command ovconfchg -edit.

  2. In BSM, check that a profile database exists, access:

    Admin > Platform > Setup and Maintenance > Manage Profile Databases

    The profile database stores metrics data and is required, even if no metrics data will be sent from the BSM Connector.

    If a profile database does not yet exist, create one as described in "Database Administration" in the BSM Platform Administration Guide.

  3. In BSM, open the New BSM Connector page, select:

    Admin > Integrations > BSM Connector Integrations

    In the left pane, click New BSM Connector. The New BSM Connector page displays.

    The information you need to enter depends on the type of integration data you want to collect with this BSM Connector:

    • Main Settings. Complete the mandatory Display name and Host name fields. Accept or change the default HTTP and HTTPS port numbers.

    • Event Drilldown Settings. These settings apply to event data only and are optional.

      Event drilldown enables BSM users to launch the user interface of the third-party system in the context of an event collected through BSM Connector. Event synchronization sends event lifecycle changes back to the event source. For example, if a BSM operator closes an event originating from NNMi, a notification can be automatically sent to NNMi.

    • BSM Gateway Server Settings. These settings are mandatory and are completed automatically. Accept or change the defaults as required.

      The required information includes the name of the BSM Gateway Server to which the BSM Connector sends the collected data. The name of the user to log into the BSM Gateway Server from the BSM Connector is also required because BSM Connector subsequently uses this user name to authenticate internal calls to BSM.

    • Policy Management Settings. These settings are optional. Accept or change the defaults as required.

      The Configure policy management settings establish secure communication between BSM Connector and the BSM Gateway Server based on certificates. The Configure policy management check box sends a certificate request to BSM, which must then be granted in BSM. Secure communication is required for policy activation in BSM Connector and for event forwarding from BSM Connector to BSM.

    • Policy Management Settings.

      Caution: Make sure to clear the Configure policy management checkbox.

    • Profile Settings. These settings are mandatory and are completed automatically. Accept or change the defaults as required.

      The settings define a profile database for a BSM Connector in BSM. The profile database stores metrics data and is required, even if no metrics data will be sent from the BSM Connector. If a profile does not yet exist in BSM, create one as described in "Database Administration" in the BSM Platform Administration Guide.

    • Topology Settings. These settings are mandatory for topology data only. Accept or change the defaults as required.

      The settings define how often the topology data is synchronized between BSM and BSM Connector, from which routing domain the topology data is collected, and to which port on the BSM Gateway Server BSM Connector sends the collected data.

  4. Click Submit to save the new BSM Connector integration.

  5. Grant the pending certificate request:

    1. Navigate to Admin > Operations Management > Setup > Certificate Requests.

      It may take a few minutes for the certificate request to appear.

    2. On the Certificate Requests tab, select the certificate request and then click the Grant itembutton.

Setting up a BSM Connector integration on this page automatically creates a BSM Connector connected server in Operations Management.

Replace the self-signed certificate

BSM Connector is shipped with a self-signed certificate. You must replace the certificate with a certificate issued by your Certificate Authority (CA):

  1. Obtain a server certificate from your CA issued to the BSM Connector server. Typically this certificate is issued in PKCS12 format with a password-protected private key.

  2. Change the Tomcat configuration to use the PKCS12 certificate instead of the default self-signed Java certificate. Locate the following lines in the <BSM Connector root directory>/Tomcat/conf/server.xml configuration file:

       keystore="../groups/serverKeystore" keystoreType="JKS"
    keystorePass="changeit"/>

    Change them to:

       keystore="path to server certificate in PKCS12 format"  
       keystoreType="PKCS12" 
    keystorePass="password for the private key"

    Restart Tomcat.

If you cannot obtain a server certificate from a CA in PKCS12 format, manually generate a server certificate using a Java Keystore (JKS) and have it signed by your CA. See the section "Creating a Keystore" in the BSM Hardening Guide.

If the invalid self-signed certificate is not replaced, accessing the BSM Connector user interface produces a "web page not found" error in the browser, and the Tomcat log file <BSM Connector root directory>/logs/tomcat.log contains the following lines:

LifecycleException:  service.getName(): "Catalina";  
Protocol handler start failed: java.io.IOException: 
Keystore was tampered with, or password was incorrect

Access the BSM Connector user interface

From a supported web browser, enter one of the following URLs:

https://<host_name>:<port>/bsmconnector
https://<host_name>:<port>/bsmc

Replace <host_name> with the current host name and <port> with the port specified during installation (by default, 30000 for HTTPS). If you try to access the user interface using HTTP (by default port 30001), BSM Connector will automatically redirect you to the HTTPS port.

For information about using BSM Connector, see the online help accessible from the user interface.

Where to go next

Once BSM Connector is installed and configured, you can start using it to import or develop policies that collect data.

If BSM Connector is installed on an HPOM managed node, remember to activate the flexible management policy BSM Connector FlexMgmt Policy in the BSM user interface.

Note: The flexible management policy BSM Connector FlexMgmt Policy cannot be edited in BSM Connector . If you no longer need the policy, deactivate it and delete it.

See the BSM Connector online help or the Using BSM Connector Guide for more information.

© Copyright 2012-2013 Hewlett-Packard Development Company, L.P.