HP BSM Connector Release Notes...KnownProblems...

HP BSMConnectorFor the Linux and Windows® operating systems

Software Version: 9.20

Release Notes

Document Release Date: August 2012

Software Release Date: August 2012

Legal NoticesWarranty

The only warranties for HP products and services are set forth in the express warranty statementsaccompanying such products and services. Nothing herein should be construed as constituting anadditional warranty. HP shall not be liable for technical or editorial errors or omissions containedherein.

The information contained herein is subject to change without notice.

Restricted Rights LegendConfidential computer software. Valid license from HP required for possession, use or copying.Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer SoftwareDocumentation, and Technical Data for Commercial Items are licensed to the U.S. Governmentunder vendor's standard commercial license.

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

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

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

Google™ andGoogleMaps™ are trademarks of Google Inc.

Intel®, Itanium®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. andother 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, andWindows Vista® are U.S. registeredtrademarks of Microsoft Corporation.

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

UNIX® is a registered trademark of TheOpenGroup.

AcknowledgementsThis product includes software developed by the Apache Software Foundation(http://www.apache.org/).

This product includes software developed by the JDOM Project (http://www.jdom.org/).

HP BSMConnector (9.20)Page 2 of 30

Release Notes

http://www.apache.org/

http://www.jdom.org/

This product includes software developed by theMX4J project (http://mx4j.sourceforge.net).


Release Notes

Documentation UpdatesThe title page of this document contains the following identifying information:

l Software Version number, which indicates the software version.

l Document Release Date, which changes each time the document is updated.

l Software Release Date, which indicates the release date of this version of the software.

To check for recent updates or to verify that you are using themost recent edition of a document, goto:

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

This site requires that you register for an HP Passport and sign in. To register for an HP PassportID, go to:

http://h20229.www2.hp.com/passport-registration.html

Or click theNew users - please register link on the HP Passport login page.

You will also receive updated or new editions if you subscribe to the appropriate product supportservice. Contact your HP sales representative for details.

Note: This document was last updated: Wednesday, August 22, 2012


Release Notes

SupportVisit the HP Software Support Online web site at:

http://www.hp.com/go/hpsoftwaresupport

This web site provides contact information and details about the products, services, and supportthat HP Software offers.

HP Software online support provides customer self-solve capabilities. It provides a fast andefficient way to access interactive technical support tools needed tomanage your business. As avalued support customer, you can benefit by using the support web site to:

l Search for knowledge documents of interest

l Submit and track support cases and enhancement requests

l Download software patches

l Manage support contracts

l Look up HP support contacts

l Review information about available services

l Enter into discussions with other software customers

l Research and register for software training

Most of the support areas require that you register as an HP Passport user and sign in. Many alsorequire a support contract. To register for an HP Passport ID, go to:

http://h20229.www2.hp.com/passport-registration.html

To findmore information about access levels, go to:

http://h20230.www2.hp.com/new_access_levels.jsp


Release Notes

ContentsRelease Notes 1

Contents 6

HP BSM Connector Release Notes 7

What's New in This Release? 8

Supported Environments 9

HP Software Products Integration 9

Installation Requirements 10

Known Problems 11

Installation and Upgrade Problems 11

User Interface Problems 13

General Issues 15

Documentation Updates 17

Configuring BSM Connector to Use SSL 18

How to Prepare BSM Connector for Using SSL 20

How to Configure BSM Connector to SendMetrics and Topology to a BSM ServerOver a Secure Channel 21

How to Configure BSM Connector to Connect to a BSM Server That Requires a ClientCertificate 23

How to Configure the Topology Discovery Agent in BSM ConnectorWhen the BSMServer Requires a Client Certificate 27

Localization and Globalization 30


HP BSM Connector Release NotesThis document is an overview of HP BSMConnector (BSM Connector). It contains importantinformation that is not included in books or Help. You can find information about the following in thisdocument:

l "What's New in This Release?" on the next page

l "Supported Environments" on page 9

l "HP Software Products Integration" on page 9

l "Installation Requirements" on page 10

l "Known Problems" on page 11

l "Documentation Updates" on page 17

l "Localization andGlobalization" on page 30


What's New in This Release?BSMConnector combines the technology used by HP BSM Integration Adapter with that ofHP SiteScope Technology IntegrationMonitors to create a unified solution for integration of third-party managers, applications, and enterprisemanagement systems. BSM Connector 9.20 providesthe following capabilities:

l Discover topology from the product BSM Connector connects to (based on log files, databasetables, Web services, or custom data sources using topology scripts); discovered topologypopulates RTSM

l Get events (from log files, database tables, Web services, XML files, SNMP traps, OpenMessage Interfacemessages, or scheduled tasks)

l Get metrics (from log files, database tables, orWeb services); metrics are stored in the BSMProfile Database

l Define policies usingWeb-based UI

l Synchronize events

l Manage BSMConnector from BSM

l Backward compatibility with previous integrations based on BSM Integration Adapter(SiteScope Technology IntegrationMonitors remain available for existing integrations in BSM9.20 since there is nomigration tool from SiteScope Technology IntegrationMonitors to BSMConnector yet; for new integrations, BSM Connector should be used)

l Supports BSM's open integration strategy, providing out-of-the-box connectors to HP and third-party products. This enables expanding connectivity of BSM and related products (OperationsManager i, Service Health Analyzer). Customers can access connectors via HP Live Network(HPLN); NNMi Connector, BSM Connector for Nagios, BSM Connector for Microsoft SCOM,and BSMConnector for IBM Tivoli are already available. HP certified partners will also be able tobuild their own connectors and post them onHPLN. See the HP Live Network sitehttps://hpln.hp.com/group/bsm-integrations.


Release NotesHP BSMConnector Release Notes

https://hpln.hp.com/group/bsm-integrations

https://hpln.hp.com/group/bsm-integrations

Supported EnvironmentsThe BSMConnector server runs in these operating system environments:

l Microsoft Windows Server:

n Windows Server 2003 R2 SP2 Standard Edition (32 bit)


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


n Windows Server 2008 SP2 Standard Edition (32 bit)

n Windows Server 2008 SP2 Standard Edition (64 bit)

n Windows Server 2008 SP2 Enterprise Edition (32 bit)

n Windows Server 2008 SP2 Enterprise Edition (64 bit)



l RedHat Enterprise Linux

n RedHat Enterprise Linux AS 5.3 and later minor versions (64 bit)

n RedHat Enterprise Linux ES 5.3 and later minor versions (64 bit)

HP Software Products IntegrationBSMConnector integrates with these HP Software products:

l HP Business ServiceManagement 9.20

l HP ArcSight ESM

l HP ArcSight Logger

l HP Network NodeManager i


Release NotesHP BSMConnector Release Notes

Installation RequirementsYou can find requirements and steps to install BSM Connector in the interactiveBSMConnectorInstallation and UpgradeGuide on the product installationmedia at this location:

/Documentation/HP_BSM_Connector_Installation_and_Upgrade_Guide.htm

Note: BSMConnector is supported with Internet Explorer 7.0, 8.0, 9.0 and Firefox 10.0 ESR.Use a supported browser to open theBSMConnector Installation and UpgradeGuide.


Known ProblemsThe reference number for each known problem is the Change Request (QCCR) number. For moreinformation about open known problems, visit HP Software Support Online, or contact your HPSupport representative directly.

Installation and Upgrade ProblemsThis section describes installation and upgrade problems.

QCCR1A146938During the initialization of the installation wizard, an unnecessary message boxopens

Description:During the initialization of the installation wizard amessage box opens, whichcontains the followingmessage:

"A factory provided installation configuration file was found in the directory with the installationexecutable. Do you want to use the values in this file for the current installation?"

Workaround:When this message box opens, click No.

QCCR1A131604 HP BSM Connector Configuration Wizard stops responding

Description: During the BSMConnector installation, theHP BSM Connector ConfigurationWizardmay stop responding when it reaches the Introduction page.

Workaround: Restart the configuration wizard.

Windows:

1. Close the unresponsiveHP BSM Connector Configuration Wizard.

2. Navigate to %Temp%\HPOvInstaller\BSMConnector_<version>.

3. Copy one of the ovinstallparams_<time_stamp>.ini files to %Temp%.

4. Rename %Temp%\ovinstallparams_<time_stamp>.ini to%Temp%\ovinstallparams.ini.

5. Open a command prompt and run %Temp%\BSMConnector\postinstall_launch_bsmc_config.bat %cd%.

The configuration wizard opens. Complete the wizard pages and finish the BSMConnectorinstallation.


http://www.hp.com/managementsoftware/support




Linux:

1. Close the unresponsiveHP BSM Connector Configuration Wizard.

2. Navigate to /tmp/HPOvInstaller/BSMConnector_<version>.

3. Copy one of the ovinstallparams_<time_stamp>.ini files to /tmp.

4. Rename /tmp/ovinstallparams_<time_stamp>.ini to/tmp/ovinstallparams.ini.

5. Open a command prompt and run /tmp/BSMConnector/postinstall_launch_bsmc_config.sh.

The configuration wizard opens. Complete the wizard pages and finish the BSMConnectorinstallation.

QCCR1A146587 The BSMConnector service starts automatically after installation although theStart BSM Connector service after install checkbox is cleared

Description: The BSM Connector service starts automatically onWindows computers althoughtheStart BSM Connector service after install checkbox in theHP BSM ConnectorConfiguration Wizard is not selected.

Workaround: Manually stop theHP BSM Connector service inAdministrative Tools >Services.

QCCR1A146732When the BSM server uses SSL, problems occur when configuring BSMConnector integrations in the BSM user interface

Description:When the BSM server uses SSL, a certificate request is not correctly triggered whenconfiguring BSM Connector integrations in the BSM user interface.

Workaround:On the computer that runs the BSMConnector, activate the HP Operations Agentmanually using one of the following commands:

l OnWindows:

cscript %ovinstalldir%\bin\win64\OpC\install\opcactivate.vbs -srv<BSM gateway server>

l On Linux:

/opt/OV/bin/OpC/install/opcactivate -srv <BSM gateway server>


Release NotesKnown Problems

User Interface ProblemsThis section describes user interface problems.

QCCR1A146403 Log file policies only: Datamay be lost if the policy timeout is higher than thefrequency

Description:BSMConnector may not send all events, metrics, and topology to BSM, if thetimeout in log file policies is higher than the frequency.

Workaround: Complete the following steps:

1. In log file policies, navigate to theSource page.

2. Make sure the value configured in the Frequency field is higher than the value configured in theTimeout field.

3. Save the policy and activate it.

QCCR1A146117Metrics integration policies only: an unexpected error occurs when copying a rulewith an empty description

Description:When copying ametrics rule with no description text in a database, log file, orWebservice listener policy, an unknown error dialog box is displayed.

Workaround:Click OK to close the error dialog box and continue editing the copied rule. You canignore the error.

QCCR1A145569Connecting to a remote HP-UX server using SSH is not possible

Description:Connecting to a remote HP-UX server using the SSH protocol may not be possible.

Workaround: In cases where SSH connections to a remote HP-UX server do not work, use adifferent protocol such as telnet.

QCCR1A145535Some policy variables are not correct.

Description: TheOpenMessage Interface Policy Editor and SNMP Trap Policy Editor both providethe ability to use the policy variable <$MSG_TYPE>. This policy variable never contains a value forthese types of policies, and should not appear in the list of available policy variables.

In addition, the SNMP Trap Policy Editor provides the ability to use the policy variable <$s>. Thispolicy variable should contain the event severity, but always contains the value Unknown.

Workaround: None.

QCCR1A141981Policy state changes with ovpolicy are not reflected in the BSMConnector list ofpolicies

Description:When changing the policy state from enabled to disabled using the ovpolicycommand line tool, the policy activation state in the BSMConnector user interface remainsactivated.



Workaround:Do not use ovpolicy to activate or deactivate a policy. Always use the BSMConnectorActivate andDeactivate toolbar buttons or the context menu. Youmay use ovpolicyonly for troubleshooting purposes, for example to investigate whether a policy is enabled or disabled(ovpolicy -list).

QCCR1A138852Connecting to a remote UNIX server using rlogin is not possible

Description:With some network configurations, connecting to a third party remote server using therlogin protocol may not be possible.

Workaround: In cases where rlogin connections to a third party remote server do not work, use adifferent protocol such as SSH or telnet.

QCCR1A137653Client test tools for the web service listener aremissing on Linux

Description:Client test tools for checking connectivity to the web service listener aremissing fromthe following folder on Linux:

/opt/HP/BSMConnector/conf/ems/webservice/test_client

Workaround:None.

QCCR1A147195 The BSM Connector user interface does not open on Korean, Japanese, andSimplified Chinese systems

Description: The BSM Connector user interface does not open when the Internet Explorerlanguage preferences include Korean (ko-KR), Japanese (ja-JP), and Simplified Chinese (zh-CN).

Workaround:Contact HP Support to receive a hotfix for the problem. In themeantime, removeKorean, Japanese, and Simplified Chinese from your Internet Explorer language preferences.



General IssuesThis section describes general problems in BSM Connector.

QCCR1A146085BSMConnector does not send all events and the JVM crashes

Description: Database, log file, andWeb service listener policies are not capable of sending 110events per second as described in the BSM Connector online help and User Guide. Events may belost and the Java Virtual Machine (JVM)may crash.

Workaround: Complete the following steps:

1. Increase themaximum size of the internal event file:

a. Open the following file in a text editor:

<BSM Connector root directory>/groups/master.config

b. Find the entry change _eventRollingMaxFileSizeInKB and increase the defaultvalue of 100000KB, for example to 1000000KB.

2. Increase the heap size of the JVM:

Windows:

a. Stop the BSMConnector service in theAdministrative Tools > Services.

b. Edit the BSM Connector's service key in the registry. Use regedit to open the RegistryEditor.

c. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/<BSM Connector servicename>/serviceParam. The default service name is HP BSM Connector.

d. Modify the serviceParam default and change -Xmx512m to one of the following:

2GB: -Xmx2048m

4GB: -Xmx4096m

e. Start the BSM Connector service in theAdministrative Tools > Services.

Linux:

a. Stop BSMConnector, type:

/opt/HP/BSMConnector/stop

b. Navigate to <BSM Connector root directory>/bin and edit the start-servicescript.

c. In the script, change -Xmx512m to one of the following:

2GB: -Xmx2048m

4GB: -Xmx4096m

d. Start the BSM Connector service, type:

/opt/HP/BSMConnector/start



QCCR1A135761 Linux only: After rebooting the BSM Connector system, the BSM Connectorprocess does not start automatically

Description: On Linux systems, the BSM Connector process does not start automatically after areboot.

Workaround: Manually start the BSM Connector process:

/opt/HP/BSMConnector/start.



Documentation UpdatesThe first page of this document identifies the:

l Version number for the software.

l Software release date.

To check for recent updates or to verify that you are using themost recent edition, visit the HPSoftware Product Manuals web site.

To retrieve a document, select the:

1. Product name.

2. Version list.

3. Operating System.

4. Preferred Language.

5. Document title.

6. Click Open orDownload.

Youmust have Adobe® Reader installed to view files in PDF format (*.pdf). To download AdobeReader, go to the Adobe web site.

Note: This document was last updated: Wednesday, August 22, 2012






http://www.adobe.com/

Configuring BSM Connector to Use SSLBSMConnector uses SSL to encrypt communication with the user interface. Because the self-signed certificate that the BSMConnector uses by default is not from a trusted certificate authority,you normally see certificate errors in theWeb browser when you connect to BSM Connector.

To secure the connection and prevent the certificate errors, you can obtain a server certificate froma trusted certificate authority and then import the certificate.

BSM Connector can also be configured to connect to a BSM server that requires SSLwith orwithout a client certificate. If the BSM server requires SSL, BSM Connector sends metrics andtopology data in securemode. Event data is always sent securely.

The diagram "Secure Communication Overview " on the next page illustrates the securecommunication channels between the browser-based BSMConnector user interface, the BSMConnector server, and BSM. The numbers in the diagram correspond to the sections that explainthe configuration required to communicate securely:

(1) "How to Prepare BSM Connector for Using SSL" on page 20

(2) "How to Configure BSM Connector to SendMetrics and Topology to a BSM Server Over aSecure Channel" on page 21

(3) "How to Configure BSM Connector to Connect to a BSM Server That Requires a ClientCertificate" on page 23

(4) "How to Configure the Topology Discovery Agent in BSM ConnectorWhen the BSM ServerRequires a Client Certificate" on page 27


Release NotesDocumentation Updates

Secure Communication Overview

KeytoolBSMConnector is shipped withKeytool. Keytool is a key and certificate management utility. Itenables users to administer their own public/private key pairs and associated certificates forauthentication using digital signatures. It also enables users to cache the public keys of otherpersons and organizations they communicate with. This is installed in <BSM Connector rootdirectory>\java\bin.

You can find out more about keytool at the OracleWeb site:

http://docs.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html



http://docs.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html

How to Prepare BSM Connector for Using SSLBSMConnector is shipped with a default self-signed certificate. You should replace the self-signedcertificate with a certificate issued by your Certificate Authority (CA) as described below.

1. Obtain a server certificate from your CA issued to the BSMConnector server. Typically thiscertificate 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 rootdirectory>\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 cannot obtain server certificate from aCA in PKCS12 format, manually generate a servercertificate using a Java Keystore (JKS) and have it signed by your CA. See the section "Creating aKeystore" in the BSM Hardening Guide.



How to Configure BSM Connector to Send Metricsand Topology to a BSM Server Over a SecureChannel

This task describes the steps involved in enabling secure communication between BSMConnectorand BSMwhen the BSM server requires SSL. If the BSM server requires SSL, BSM Connectorsends metrics and topology data in securemode. Event data is always sent securely.

1. On the BSMConnector server, establish trust by importing the Certificate Authority (CA) rootcertificate of the authority that issued the BSM server certificates for the external accesspoints (load balancer, reverse proxy, BSMWeb server). Run the following command from the<BSM Connector root directory>\java\bin directory:

keytool -import -trustcacerts -alias <your alias> -keystore..\lib\security\cacerts -file <root CA certificate file>

2. In BSM, select Admin > Integrations > BSM Connector Integrations, and click theNewBSM Connector button to add the BSMConnector instance. In the New BSMConnectorpage, make sure the following settings are configured:

n Main Settings: InHTTP port number specify theHTTPS port number of the BSMConnector. HTTP port number andHTTPS port numbermust both contain the samevalue here. By default, BSM Connector uses the HTTPS port number 30000, but it can beconfigured to use a different port number instead.

n BSM Gateway Server Settings:Check that theGateway server name/IP addresscontains the correct server name and port (if not the default port 443). Enter the name of theexternal access point, if the BSM environment includes a load balancer, reverse proxy, orBSMWeb server.

Note:When you configure BSM Connector in the New BSMConnector page inAdmin> Integrations > BSM Connector Integrations, add the fully qualified domain nameof the BSM external access point in theGateway server name/IP address field. Youmust use the same name as in the BSM server certificate.

n Profile Settings:Select theWeb Server Use SSL checkbox. Youmust also select theUse SSL check box if BSM Connector is configured to use SSL.

3. If the gateway servers are configured to use the Apache HTTP Server: In BSM, select Admin> Platform > Setup and Maintenance > Infrastructure Settings, click Foundations andthen select Platform Administration.

Make sure all alphabetic characters in the following settings are lower-case:

n Default Virtual Gateway Server for Application Users URL

n Default Virtual Gateway Server for Data Collectors URL

Note: The BSM server certificate must also have been created using a lower-case hostname.



4. On the computer that runs the BSMConnector, activate the HP Operations Agent manuallyusing one of the following commands:

n OnWindows:

cscript %ovinstalldir%\bin\win64\OpC\install\opcactivate.vbs -srv<BSM gateway server>

n On Linux:

/opt/OV/bin/OpC/install/opcactivate -srv <BSM gateway server>



How to Configure BSM Connector to Connect to aBSM Server That Requires a Client Certificate

This task describes the steps involved in enabling secure communication between BSMConnectorand BSMwhen the BSM server requires a client certificate.

1. If you obtained the client certificate in Java keystore (JKS) format, copy it to the <BSMConnector root directory>\templates.certificates folder, and then continue with "Check thekeystore contents" on page 25.

Note:

n Make sure that the private key password is at least six characters long, and that theprivate key and keystore passwords are the same.

n In addition, make sure that the above keystore contains the CA certificate that issuedit.

Otherwise, perform the following steps (if you did not obtain the client certificate in JKSformat). See also the section "Creating a Keystore" in the BSM Hardening Guide.

a. Create a keystore under <BSM Connector root directory>\templates.certificates byrunning the following command from the <BSM Connector root directory>\java\bindirectory:

keytool -genkeypair -keyalg RSA -alias bsmc -keystore <BSMConnector root directory>\templates.certificates\.ks -storepass<your_keystore_password>

For example:

keytool -genkeypair -keyalg RSA -alias bsmc -keystoreC:\BSMConnector\templates.certificates\.ks -storepass changeitWhat is your first and last name?[Unknown]: domain.nameWhat is the name of your organizational unit?[Unknown]: deptWhat is the name of your organization?[Unknown]: XYZ LtdWhat is the name of your City or Locality?[Unknown]: New YorkWhat is the name of your State or Province?[Unknown]: USAWhat is the two-letter country code for this unit?[Unknown]: USIs CN=domain.name, OU=dept, O=XYZ Ltd, L=New York, ST=USA, C=UScorrect?[no]: yesEnter key password for <BSM Connector>Press Enter to use the same password as the keystore password.



b. Create a certificate request for this keystore by running the following command from the<BSM Connector root directory>\java\bin directory:

keytool -certreq -alias bsmc -file c:\bsmc.csr -keystore <BSMConnector root directory>\templates.certificates\.ks -storepass<your_keystore_password>

For example:

keytool -certreq -alias bsmc -file c:\bsmc.csr -keystoreC:\BSMConnector\templates.certificates\.ks -storepass changeit

c. Have your certificate authority sign the certificate request. Copy/paste the contents of the.csr file into your Certificate Authority Web form.

d. Download the signed client certificate in BASE-64 format to <BSM Connector rootdirectory>\templates.certificates\clientcert.cer.

e. Download the certificate authority certificate in BASE-64 format to c:\.

f. Import the certificate authority certificate into the JKS keystore by running the followingcommand:

keytool -import -alias ca -file c:\ca.cer -keystore <BSMConnector root directory>\templates.certificates\.ks -storepass<your_keystore_password>

For example:

keytool -import -alias ca -file c:\ca.cer -keystoreC:\BSMConnector\templates.certificates\.ks -storepass changeitOwner: CN=dept-CA, DC=domain.nameIssuer: CN=dept-CA, DC=domain.nameSerial number: 2c2721eb293d60b4424fe82e37794d2cValid from: Tue Jun 17 11:49:31 IDT 2008 until: Mon Jun 1711:57:06 IDT 2013Certificate fingerprints:MD5: 14:59:8F:47:00:E8:10:93:23:1C:C6:22:6F:A6:6C:5BSHA1:17:2F:4E:76:83:5F:03:BB:A4:B9:96:D4:80:E3:08:94:8C:D5:4A:D5Trust this certificate? [no]: yesCertificate was added to keystore

g. Import the client certificate into the keystore by running the following command:

keytool -import -alias bsmc -file <BSM Connector rootdirectory>\templates.certificates\certnew.cer -keystore <BSMConnector root directory>\templates.certificates\.ks -storepass<your_keystore_password>

For example:

keytool -import -alias bsmc -filec:\BSMConnector\templates.certificates\certnew.cer -keystoreC:\BSMConnector\templates.certificates\.ks -storepass changeit



The certificate reply is installed in the keystore <BSM Connector rootdirectory>\java\bin directory.

2. Check the keystore contents

Run the following command from the <BSM Connector root directory>\java\bin directory,and enter the keystore password:

keytool -list -keystore <BSM Connector rootdirectory>\templates.certificates\.ks

For example:

keytool -list -keystore C:\BSMConnector\templates.certificates\.ksEnter keystore password: changeit

Keystore type: jksKeystore provider: SUN

Your keystore contains 2 entries

ca, Mar 8, 2012, trustedCertEntry,Certificate fingerprint (MD5):14:59:8F:47:00:E8:10:93:23:1C:C6:22:6F:A6:6C:5Bbsmc, Mar 8, 2012, keyEntry,Certificate fingerprint (MD5):C7:70:8B:3C:2D:A9:48:EB:24:8A:46:77:B0:A3:42:E1

C:\BSMConnector\java\bin>

3. To use this keystore for client certificate, add the following lines to the <BSM Connector rootdirectory>\groups\master.config file:

_urlClientCert=<keystoreName>_urlClientCertPassword=<keystorePassword>

For example:

_urlClientCert=.ks_urlClientCertPassword=changeit

4. Save the changes to the file.

5. Restart the BSM Connector server:

Windows: Restart theHP BSM Connector service in theAdministrative Tools > Services.

Linux: Restart the BSM Connector main process, type /opt/HP/BSMConnector/stopfollowed by /opt/HP/BSMConnector/start.

6. In BSM, select Admin > Integrations > BSM Connector Integrations, and click theNewBSM Connector button to add the BSMConnector instance.

TroubleshootingIf the connection between BSMConnector and BSM fails, check the following log files for errors:



l BSMConnector machine:

<BSM Connector root directory>\log\bac_integration.log

l BSM Gateway Server:

<HPBSM root directory>\log/topaz_all.ejb.log

Check for the following error:

javax.net.ssl.SSLHandshakeException:sun.security.validator.ValidatorException: PKIX path buildingfailed: sun.security.provider.certpath.SunCertPathBuilderException:unable to find valid certification path to requested target

Possible solutions: The error indicates one of the following:

n The CA root certificate was not imported into the BSM JVM.

n The BSM server was not restarted after the import. (A server restart is always required after acertificate import. This is a known limitation.)



How to Configure the Topology Discovery Agentin BSM Connector When the BSM Server Requiresa Client Certificate

After configuring BSM Connector to connect to the BSMGateway Server using a client certificate(see "How to Configure BSM Connector to Connect to a BSM Server That Requires a ClientCertificate" on page 23), you need to perform the following steps for discovery to report topology tothe BSM server.

1. Import the Certificate Authority (CA) certificate (or BSM server certificate) into the discoverytrust store (<BSM Connector rootdirectory>\WEBINF\classes\security\MAMTrustStoreExp.jks) with password (the defaultpassword for the discovery trust store is logomania, which encrypted, is: [22,-8,116,-119,-107,64,49,93,-69,57,-13,-123,-32,-114,-88,-61]):

keytool -import -alias <your_CA> -keystore <BSM Connector rootdirectory>\WEB-INF\classes\security\MAMTrustStoreExp.jks -storepass<your_keystore_password>

For example:

keytool -import -alias AMQA_CA -file c:\ca.cer -keystoreC:\BSMConnector\WEB-INF\classes\security\MAMTrustStoreExp.jks -storepass logomania

Note: The private key passwordmust be at least six characters, and the password for theprivate key and password for the keystoremust be the same.

2. Check the contents of trustStore using the following command:

keytool -list -keystore <BSM Connector root directory>\WEB-INF\classes\security\MAMTrustStoreExp.jks -storepass <your_keystore_password>Keystore type: <Keystore_type>Keystore provider: <Keystore_provider>Your keystore contains 2 entriesmam, Nov 4, 2004, trustedCertEntry,Certificate fingerprint (MD5):<Certificate_fingerprint>amqa_ca, Dec 30, 2010, trustedCertEntry,Certificate fingerprint(MD5):<Certificate_fingerprint>

For example:

keytool -list -keystore C:\BSMConnector\WEB-INF\classes\security\MAMTrustStoreExp.jks -storepass logomaniaKeystore type: JKSKeystore provider: SUNYour keystore contains 2 entriesmam, Nov 4, 2004, trustedCertEntry,Certificate fingerprint (MD5):



C6:78:0F:58:32:04:DF:87:5C:8C:60:BC:58:75:6E:F7amqa_ca, Dec 30, 2010, trustedCertEntry,Certificate fingerprint (MD5):5D:47:4B:52:14:66:9A:6A:0A:90:8F:6D:7A:94:76:AB

3. Copy the BSMConnector client keyStore (.ks) from <BSM Connector rootdirectory>\templates.certificates to <BSM Connector root directory>\WEB-INF\classes\security\.

4. In the ssl.properties file, update the javax.net.ssl.keyStore property to the keyStore name.For example, javax.net.ssl.keyStore=.ks.

5. Change the BSMConnector client keyStore password tomatch the Discovery password forkeystore (default is logomania).

keytool -storepasswd -new <Discovery_keystore_password>-keystore <BSM Connector root directory>\WEB-INF\classes\security\.ks-storepass <your_keystore_password>

For example:

keytool -storepasswd -new logomania -keystore C:\BSMConnector\WEB-INF\classes\security\.ks -storepass changeit

6. Change private key password tomatch Discovery password for keyStore:

keytool -keypasswd -alias bsmc -keypass <your_keystore_password>-new <Discovery_keystore_password> -keystore <BSM Connector rootdirectory>\WEB-INF\classes\security\.ks -storepass <your_keystore_password>

For example:

keytool -keypasswd -alias bsmc -keypass changeit -new logomania -keystoreC:\BSMConnector\WEB-INF\classes\security\.ks -storepass logomania

7. Verify keystore using new password:

keytool -list -v -keystore <BSM Connector root directory>\WEB-INF\classes\security\.ks -storepass <your_keystore_password>

For example:

keytool -list -v -keystore C:\BSMConnector\WEB-INF\classes\security\.ks-storepass logomania

8. Restart the BSM Connector server:

Windows: Restart theHP BSM Connector service in theAdministrative Tools > Services.

Linux: Restart the BSM Connector main process, type /opt/HP/BSMConnector/stopfollowed by /opt/HP/BSMConnector/start.

9. In BSM, select Admin > Integrations > BSM Connector Integrations, and click theNewBSM Connector button to add the BSMConnector instance. In theProfile Settings pane,



make sure to select theWeb Server Use SSL checkbox.

10. Check the topology appears inBSM > Admin > RTSM Administration > IT UniverseManager > System Monitors view.

Troubleshootingl Check the bac-integration.log located in <BSM Connector root directory>\logs\bac_

integration\ for the following errors:

2010-12-30 11:03:06,399 [TopologyReporterSender](TopologyReporterSender.java:364)ERROR - failed to run main topology agent.topologyCommand=TopologyCommand{commandType=RUN_SCRIPT, …java.lang.IllegalArgumentException: cannot find script withname=create_monitor.py at com.mercury.sitescope.integrations.bac.topology.dependencies.DependenciesCrawler.findDependencies(DependenciesCrawler.java:60)at com.mercury.sitescope.integrations.bac.topology.dependencies.ScriptDependenciesFinder.find(ScriptDependenciesFinder.java:80)at com.mercury.sitescope.integrations.bac.topology.TopologyReporterSender.getDependencies(TopologyReporterSender.java:552)at com.mercury.sitescope.integrations.bac.topology.TopologyReporterSender.send(TopologyReporterSender.java:347)at com.mercury.sitescope.integrations.bac.topology.TopologyReporterSender.run(TopologyReporterSender.java:304)at java.lang.Thread.run(Thread.java:619)

Verify that the certificate and keyStore passwords are identical.



Localization and GlobalizationLocalization is the process by which software applications are adapted to suit a specific localmarket or locale. Globalization is the process of designing products or services for the globalmarketplace so that they can be sold anywhere in the world with only minor revision.

HP supplies BSM Connector localized software in these languages:

l English

l French

l German

l Japanese

l Korean

l Simplified Chinese


Date post:	05-Sep-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

HP BSM Connector Release Notes...KnownProblems...

Documents