Customized output from:
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
© Copyright 2005-2012 Hewlett-Packard Development Company, L.P.
Adobe™ is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
This product includes an interface of the 'zlib' general purpose compression library, which is Copyright © 1995-2002 Jean-loup Gailly and Mark Adler.
Visit 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 support that HP Software offers.
HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to:
Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to:
http://h20229.www2.hp.com/passport-registration.html
To find more information about access levels, go to:
http://h20230.www2.hp.com/new_access_levels.jsp
The purpose of this guide is to provide the procedures required to upgrade BSM 9.1x from a previous version of BAC or BSM.
Before performing this procedure, we recommend that you download the latest version of this guide from the HP Software Product Manuals website: http://h20230.www2.hp.com/selfserve/manuals.
Using a staging environment to upgrade BSM refers to installing the new software on different machines and database schemas (referred to as the staging environment) to allow the original BAC or BSM servers to continue functioning while the upgrade is in process. The original machines are referred to as the production environment. This minimizes downtime and allows you to ensure that the new servers are functioning as desired before disconnecting the original servers.
When upgrading using a staging environment, the BSM software is installed on the staging servers and then the wizard activates the Staging Data Replicator (SDR). This listens to the samples (data) coming in to the original server and passes them to the staging server. The SDR replicates only data samples and not configuration changes made within the databases. Therefore, any configuration changes made to the production server from the start of the SDR will not be transferred to the staging environment. For more information, see the BSM 9.1x Upgrade Guide.
Upgrading directly refers to installing the new version on the same servers and database schemas as the original version. This can only be performed after uninstalling the original version and therefore results in greater downtime.
If your source and target environments are not using the same operating system, you must upgrade using the staging method. This requires an additional set of servers. For details, see the BSM 9.1x Upgrade Guide.
Using a staging environment to upgrade BSM refers to installing the new software on different machines and database schemas (referred to as the staging environment) to allow the original BAC or BSM servers to continue functioning while the upgrade is in process. The original machines are referred to as the production environment. This minimizes downtime and allows you to ensure that the new servers are functioning as desired before disconnecting the original servers.
When upgrading using a staging environment, the BSM software is installed on the staging servers and then the wizard activates the Staging Data Replicator (SDR). This listens to the samples (data) coming in to the original server and passes them to the staging server. The SDR replicates only data samples and not configuration changes made within the databases. Therefore, any configuration changes made to the production server from the start of the SDR will not be transferred to the staging environment. For more information, see the BSM 9.1x Upgrade Guide.
Upgrading directly refers to installing the new version on the same servers and database schemas as the original version. This can only be performed after uninstalling the original version and therefore results in greater downtime.
The following steps are customized according to your selections. Check that your selections are correct.
If any selections are not correct, click Change.
For information about how to download and install the latest BSM 9.1x service pack on top of a BSM 9.10 environment, see the BSM Deployment Guide.
Create a complete deployment plan including the required software, hardware, and components. Refer to the following sections of the Deployment and Upgrade Guides to guide you through the process of planning a deployment:
Deployment Planning
Understanding the Platform and Components
High Availability for HP Business Service Management
Deployment Configurations
System Requirements
Additionally, for a high level overview of the entire deployment process, see the Getting Started with BSM Guide
Staging Data Replicator. The Staging Data Replicator (SDR) listens to the samples (data) coming in to the original server and passes them to the staging server. If you need to run the Staging Data Replicator on an external server, you will need an additional server to run the SDR during staging mode. For more information, see the BSM 9.1x Upgrade Guide.
Integrations. There are a number of integrations with other products that can affect the upgrade procedure.
Product |
Details |
---|---|
OO |
If you were using OO with BAC 8.x, you must upgrade to OO 7.51 or higher. For more information, see the support matrix. |
SM |
If you had integration between Service Manager and BAC 8.x via HP Universal CMDB, follow the instructions in the HP Universal CMDB upgrade procedures. For details, see Upgrading HP Universal CMDB Integration - Splitting Procedure in the BSM 9.1x Upgrade Guide. |
CLIP |
For information about upgrading an integration with HP CLIP 1.5, contact HP software support. |
HP Universal CMDB |
For information about upgrading HP Universal CMDB and products that integrate with it, see HP Universal CMDB Upgrade Information in the BSM 9.1x Upgrade Guide. |
NNMi |
You can continue to use BSM 9.1x without upgrading your integration with NNMi. If you choose to upgrade to NNMi 9.x, there are optional upgrades to this integration. For more information, see NNMi Upgrade Information in the BSM 9.1x Upgrade Guide. |
Documentation. The following documents are referenced in the upgrade procedures and may be needed during the upgrade process. They are all included in the BSM documentation library.
Database Guide
Platform Administration
Solutions and Integrations
Business Process Monitor Administration
Real User Monitor Administration
Using System Availability Management
Hardening Guide
Order licenses with a sales representative based on your deployment plan. Register your copy of HP Business Service Management to gain access to technical support and information on all HP products. You will also be eligible for updates and upgrades. You can register your copy of HP Business Service Management on the HP Software Support site. http://www.hp.com/go/hpsoftwaresupport
Set up your BSM servers and your BSM database server. Verify that your database has the following settings:
Oracle: The Oracle Partitioning option must be enabled.
SQL: The Compatibility Level database setting must be higher than 90 (SQL Server 2005 and higher). If you are upgrading with a staging environment, the collation must be identical in both the production and staging environments.
For information about setting up your database server, see the HP Business Service Management Database Guide.
Review relevant information describing changes from BSM 8.x to 9.1x. Depending on your BSM configuration, review the relevant upgrade sections in the Upgrade Information section of the BSM 9.1x Upgrade Guide.
If you are not using BAC 7.55 or higher, upgrade to BAC 7.55. Upgrade your BAC 7.5x environment to BAC 8.x in staging mode by following the instructions in the Upgrade section of the BAC 8.0 Deployment Guide. This guide is included in the BAC 8.0 DVD. In the upgrade wizard, skip the SDR and Data Import/Export steps, but make sure that you reach the end of the wizard. Also, do not move the new servers to production mode or perform any post-installation tasks specified in the 8.x documentation. Maintain the original 7.5x servers in production mode.
Upgrade your BAC 7.5 environment to BAC 8.x directly by following the instructions in the Upgrade section of the BAC 8.0 Deployment Guide. This guide is included in the BAC 8.0 DVD.
We recommend installing the latest service pack on the BAC 8.0x servers. You must install at least service pack 8.06 before continuing with the upgrade. For details, see the Service Pack release notes.
Run the pre-upgrade tool to view a customized list of items that may need attention before starting the upgrade. For details, see the BSM 8.07 Pre-Upgrade Tool Guide pdf. This guide can be found in the BSM 8.07 installation package or in the HP Software Product Manuals website http://h20230.www2.hp.com/selfsolve/manuals.
If you have an external HP Universal CMDB, upgrade it to version 8.06 or later so that it will be compatible with your version of BAC.
You must have DDM Content Pack 8 before continuing with the upgrade. If you are working with an external HP Universal CMDB, this should be done on the external HP Universal CMDB server. If not, this is done on the BSM server. Download the content pack, along with instructions about how to install it from https://hpln.hp.com/group/content-packs-ddm.
Make sure that the version of HPOM that you plan to use with BSM 9.1x is supported. For more information about supported versions, see the BSM 9.1x Release Notes.
HP strongly recommends that you upgrade the HP Operations Smart Plug-ins (SPIs) to SPI DVD release 2010 or later to take full advantage of the improvements that come with the latest versions. For more information about upgrading SPIs, see the documentation provided with the SPIs. For more information about supported versions, see the support matrix at:
http://support.openview.hp.com/selfsolve/document/KM323488
This site requires that you register for an HP Passport and sign in.
The upgrade does not migrate the following indicators (and their customizations) to version 9.1x. The 9.1x content packs replace these indicators with new indicators of the same name. The new indicators are not compatible and do not work with SPI versions earlier than SPI DVD release 2010:
Indicator |
9.1x Content Pack |
---|---|
Ping Availability |
Infrastructure Content Pack and some dependent Content Packs |
Server Load |
Lync Server Content Pack |
EJB Timeout Rate |
JEE Application Server Content Pack |
JMS Server Utilization |
JEE Application Server Content Pack |
Transaction Timeout Errors |
JEE Application Server Content Pack |
Transaction Capacity Utilization |
JEE Application Server Content Pack |
Transaction System Errors |
JEE Application Server Content Pack |
Make a note of each modification to the OMi 8.10 content packs in the following situations:
Alternatively, if you have applied many modifications, consider creating a new content pack that contains all of your OMi 8.10 modifications. For more information about creating content packs, see the Platform Administration PDF.
This task describes how to back up the OMi configuration files. The configuration files include the content packs, topology synchronization data, and custom icons.
Note: Events, Event Browser filters, the configuration for Event Assignments, and Graph Templates, and Graph Assignments are not migrated as part of the product migration.
If you want to use the same filters in the migrated installation, you must make a note of the original filters and recreate them within the Operator and Administrator areas for each user associated with the filter.
To back up the content packs and the topology synchronization rules:
From the BAC 8.x Data Processing Server host system, make a copy of all the files in the following directory and subdirectories:
%TOPAZ_HOME%\conf\opr\
Staging Only. Copy the files to a safe location on the BSM 9.1x Data Processing Server host system.
Note: The files are copied for backup purposes only. They are not automatically migrated to the new installation. If you have modified any out-of the-box content packs, you must manually migrate your changes after the upgrade. Also, if you have modified any out-of the-box topology synchronization packages, you must manually recreate your changes after the upgrade.
To back up the custom icons, complete the following steps:
From an BAC 8.x Gateway Server host system, make a copy of all the files in the following directory and subdirectories:
%TOPAZ_HOME%\opr\resources\images\hivalues\
Save these files to a safe location.
Staging Only. Copy the files to a safe location on the BSM 9.1xGateway Server host system.
To be able to recreate the configuration for Event Assignments:
Make a note of each Event Assignment rule and each associated filter.
Recreate these filters and Event Assignment rules in the migrated installation.
To be able to recreate the filters used in the Event Browser, and Closed Event Browser:
Make a note of each user and the filter configurations associated with that user.
Recreate these filters in the migrated installation.
To be able to recreate Graph Templates and Graph Assignments:
Make a note of each Graph Template and Graph Assignment that has been created. (After migrating from BAC 8.x to 9.1x, when you install content packs 9.1x on BSM 9.1x, new graph templates for all content packs are available in the Content Manager.)
Recreate your Graph Templates and Graph Assignments in the migrated installation.
Microsoft Active Directory and Microsoft SQL Server Content Packs only: Delete all CIs whose name is not the fully qualified domain name.
To delete CIs with short hostnames:
Identify and delete all Active Directory Forest CIs whose Name
field is not filled with the fully qualified domain name (FQDN).
For example, if two CIs with the names forest1
(FQDN: forest1.com
) and forest2.com
(FQDN: forest2.com
) exist, delete the forest1
CI.
Delete all Active Directory Domain CIs (recursive) and Active Directory Sites that belong to the deleted Active Directory Forest CI.
In this example, all domains and site CIs for forest1
must be deleted.
Identify and delete all SQL Server CIs whose name field is not filled with the FQDN.
HP Operations Smart Plug-in for Virtual Infrastructure only: Because the Host Name
attribute of host CIs created by the SPI for Virtual Infrastructure is empty, the CIs are not migrated successfully. To correct the problem, create an enrichment rule that copies the value of the Name
attribute to Host Name
.
To update empty Host Name attributes:
In the BAC 8.x Enrichment Manager, create a new, active enrichment rule based on a new TQL:
Select Admin > Universal CMDB > Modeling > Enrichment Manager.
To create a new enrichment rule, right-click anywhere in the Enrichment Rules pane and click New.
In the enrichment rule wizard, specify a name and description for the rule. Select Rule is active. As base TQL type, select Base the Enrichment on a new TQL. Close the wizard by clicking Finish.
Drag the CI type Host
to the editing pane.
Right-click Host
in the editing pane and select Node Properties.
Add a new attribute condition by clicking the button with the green plus sign. If necessary, select the new condition, then select Host Name - (string)
from the Attribute name: drop-down list.
Select Is null
from the Operator: drop-down list. (The Value field remains empty.) Click OK.
Optional: Calculate the TQL query results.
In the upper-left corner of the editing pane, click TQL Mode and select Enrichment Mode.
Right-click Host
in the editing pane and select Update Node.
In the Node Definition dialog, select the Host Name
attribute in the Name column, then click the By Attribute button. The string Host
appears in the drop-down list next to the By Attribute button.
To specify the attribute to be taken, select the Name
attribute in the drop-down list to the right of the Host attribute. Click OK.
Navigate to Scheduler, select:
Admin > Universal CMDB > Settings > Scheduler
Add a new job by clicking the button with the green plus sign. The Job Definition dialog opens where you specify a name and a definition.
To add an action to the job, click the button with the green plus sign under Actions. The Action Definition dialog opens. Select Run an Enrichment rule and click Next. Select the enrichment rule that you created in earlier and click Finish.
In the Job Definition dialog, under Scheduler, select Once and specify the current time. Click OK to save the job definition and close the dialog.
Wait for the enrichment to finish. Check that the enrichment query created earlier no longer matches any hosts.
For more information about enrichment rules and scheduling, see the Model Management section in the BAC online help.
Export the OMi 8.10 configuration data in the following situations:
If you are retaining the SPIs that you have been using with OMi 8.10, use the ContentManager command line interface tool to export a snapshot that contains the complete OMi configuration data to a BSM package file.
If you upgraded the SPIs to SPI DVD release 2010 and created a custom content pack for your OMi 8.10 content modifications, export that content pack only.
To export the OMi configuration data, complete the following steps:
From a BAC 8.x Gateway Server, in a command prompt window, go to the following directory:
%TOPAZ_HOME%\opr\bin\
If you are retaining the HPOM Plug-ins (SPIs) that you have been using with your OMi 8.10 installation, export all 8.10 content packs. Enter the following command:
ContentManager -snapshot -username <administrator account> -password <administrator password> -o <snapshot file name>.xml
Where the administrator account must have read and write access to the Content Manager.
If you collected your modifications to OMi 8.10 content in a custom content pack, export that custom content pack. Enter the following command:
ContentManager -username <administrator account> -password <administrator password> -e <custom content pack name> -o <custom file name>.xml
Where the administrator account must have read and write access to the Content Manager.
Save the exported data output file to a temporary location, for example:
Windows: %TEMP%\migration
Linux: /tmp/migration
If you are following the Staging Mode and the BSM 9.1x Gateway Server host system is already installed and available, copy the exported data output file to a temporary location on the BSM 9.1x Gateway Server host system.
The exported data must be converted to the syntax and model required by the BSM 9.1x version. This procedure will be described below.
For more details about uninstalling OMi, see the HP Operations Manager i Installation and Deployment Guide version 8.10.
Note: Complete this task only if you are upgrading from BAC 8.x using the direct mode.
To delete the installed OMi components from all the BSM server systems, follow these steps:
On all Data Processing and Gateway Servers, stop the BSM platform, if it is running:
Start > Programs (or All Programs) > HP Business Availability Center > Administration > Disable Business Availability Center
In a command prompt window, disable OMi by executing the following command on all the BSM platform systems:
%TOPAZ_HOME%\bin\opr-configuration.bat -disable
Click Start > Control Panel > Add or Remove Programs
Select HP Operations Manager i and click Change/Remove to start the HP Software Installer.
Select Uninstall and click Next.
In the Pre-Uninstall Summary, click Uninstall.
Click OK when the note about uninstalling the BSM platform appears.
The Installer selects and uninstalls the OMi software components. Each software component and its uninstallation progress are displayed on your screen during the uninstallation operation.
After the uninstallation process is complete, the Uninstall Complete window opens showing you a summary of the uninstallation process.
In the Uninstall Complete window, click Done to close the uninstallation program.
Note: From the View log file link, you can access the uninstallation log file that opens in a web browser. For details on the removed packages, click the Details tab.
If you are installing BSM on Windows 2008 server, disable User Access Control.
Ensure that all necessary Session Identification configurations do not have empty session ID values. Those with empty session ID values are not upgraded.
Check-in all BPM scripts to the Script Repository. The upgrade process does not preserve the checked-out status of scripts.
If you have custom integration adapters or if you modified out-of-the-box adapters, you will need to manually migrate these to BSM 9.10. For details, see "Migrating Modified UCMDB Integration (Federation) Adapters" in the BSM 9.1x Upgrade Guide.
If you created custom Java rules, custom rule .jar files, or custom Groovy rule files in pre-9.0 versions of BAC, contact HP Support for instructions on modifying and packaging them for BSM 9.x before upgrading. For details, see "Custom Rules" in the BSM 9.1x Upgrade Guide.
If you made changes to any files in the <HP BSM root directory>\WebServer\conf directory, back up the changed files and, after the upgrade, reapply the changes to the new files (do not copy the old files on top of the new ones).
Make sure your content packs are compatible with your version of HP Universal CMDB. Incompatibilities can cause problems during the upgrade. For example, installing Content Pack 9 with HP Universal CMDB 8.x could result in problems during the upgrade procedure.
All BSM machines in the staging environment must be set to the same time zone as the source environment. Incompatible time zone settings can lead to inaccuracies in reporting historical data.
Run the installation and post-installation wizards. If you have a distributed deployment, run the wizards on the Data Processing Server first. The wizards will direct when to begin running the wizards on the Gateway Server.
Note: Important: If you are upgrading from 7.5 using the staging/staging method, at the end of the post-installation wizard specify that you are upgrading from 8.x, not 7.5.
For details about installing on a Windows platform, see Installing BSM Servers on a Windows Platform in the BSM 9.10 Upgrade Guide.
For details about installing on a Linux platform, see Installing BSM Servers on a Linux Platform in the BSM 9.10 Upgrade Guide.
Disable any firewalls that exist between BSM Gateway and Data Processing Server servers. By default, Windows Server 2003 SP1 and later versions include such a firewall. It must be manually disabled.
If you have more than one BSM Data Processing server, you need to establish trust to enable communication between the servers.
For each additional Data Processing Server, complete the following configuration appropriate for your environment:
If you have a central certificate authority, make sure that the CA root certificate was already imported into the OV certificate repository on all BSM Data Processing Servers using the following command:
ovcert - importtrusted -file c:\ca_root.pem
ovcert - importtrusted -file c:\ca_root.pem -ovrg server
From the primary Data Processing Server, export the trusted certificates using the following command:
ovcert -exporttrusted -file <file with certificate>
Copy the exported trusted certificates to the new Data Processing Server and install the certificates on new Data Processing Server using the following commands:
ovcert -importtrusted -file <file with certificate>
ovcert -importtrusted -file <file with certificate> -ovrg server
On new Data Processing Servers, export certificates using the command:
ovcert -exporttrusted -file < file with certificate>
Copy this file to all your existing Data Processing Servers and import using the following commands:
ovcert -importtrusted -file <file with certificate>
ovcert -importtrusted -file <file with certificate> -ovrg server
If you have an integration with HPOM (Windows or Unix) follow the procedure "How to Establish a Trust Relationship between BSM and External Servers" in Solutions and Integrations for every Data Processing server.
Update trusted certificates using the ovcert -updatetrusted command on following servers:
All Gateway servers
All HP Diagnostics servers
All SiteScope servers
All Integration Adapter servers
Operations Management and other HP BTO Software applications use certificates that enable to clients and servers to identify themselves and communicate securely with each other. The data processing server can issue the required certificates to other servers in your environment, acting as a certificate authority.
If you have a one-machine deployment, the installation configures the certificates that you need. You do not need to configure gateway server certificates.
However, if you have a distributed deployment, after you install your BSM servers, you must make sure that every gateway server requests certificates from the data processing server. You must then make sure that the data processing server grants each certificate request.
Note: If BSM is required to issue certificates, for example, for an Integration Adapter, then the Gateway Servers must be configured to forward all incoming requests to the Data Processing Server. The Data Processing Server must be configured in the Operations Management Infrastructure Settings: Applications > Operations Management > Certificate Server Settings > Certificate Server IP Address.
To request certificates for gateway servers:
On each gateway server, open a command prompt, and then type the appropriate command depending on your operating system:
Windows: cd %TOPAZ_HOME%/bin
Linux: cd /opt/HP/BSM/bin
Start the following command:
setup-secure-communication
The command prompts you for the DNS name of the data processing server. Type this name, and then press Enter.
To grant certificate requests:
On the data processing server, open a command prompt, and then type the appropriate command depending on your operating system:
Windows: cd %TOPAZ_HOME%\bin
Linux: cd /opt/HP/BSM/bin
Start the following command:
setup-secure-communication
The command checks for pending certificate requests. For each pending certificate request, the command shows details of the request. For example:
INFO: Secure communication request from: gateway1.example.com
Press g to grant each request in turn. After you grant a certificate request, the command sends certificates to the gateway server, and then verifies that secure communication is possible.
If you have more than one Data Processing server, repeat the above procedures for each Data Processing server.
If you are planning to use Operations Manager i, perform the following steps:
Go to Admin > RTSM Administration > Modeling > CI Type Manager.
From the CI Types list select System Type Manager.
Select product_name_enum and click Edit.
Type lync_server and click Add.
Click OK.
You can see the installation log file by clicking the View log file link at the bottom of the installer window.
In a Windows environment, this log file, along with additional log files for separate installation packages, is located in the %temp%\..\HPOvInstaller\HPBsm_9.10 directory.
In a Linux environment, the logs files are located in the /tmp/HPOvInstaller/HPBsm_9.10 directory.
The installer log file name is in the following format:
HPBsm_<VERSION>_<DATE>_ HPOvInstallerLog.html or HPBsm_<VERSION>_<DATE>_ HPOvInstallerLog.txt (for example, HPBsm_9.10_2010.10.21_13_34_HPOvInstallerLog.html
).
Individual installation package log file names are in the following format:
Package_<PACKAGE_TYPE>_HPBSM_<PACKAGE_NAME>_install.log (for example, Package_msi_HPBSM_BPIPkg_install.log
).
For connection and communication between the BSM and HPOM systems, you must establish a trust relationship between the systems.
Note: The following steps use the ovcert, ovconfchg, and bbcutil command line tools. The tools are located in:
To establish a trust relationship between BSM and HPOM systems, do the following:
Ensure that certificates have been set up on the Gateway and Processing Servers. For details, see "Post-Installation Tasks" in the the HP Business Service Management Deployment Guide PDF.
On all BSM Processing Servers, execute the following command:
ovcert -exporttrusted -file BSM _DPS<#>.cer
On the HPOM management server, execute the following command:
ovcert -exporttrusted -file other.cer
Copy other.cer from the HPOM management server to all BSM Processing Servers.
Copy BSM_DPS<#>.cer from the BSM Processing Server to the HPOM management server and all other BSM Processing Servers.
On all BSM Processing Servers, execute the following commands:
ovcert -importtrusted -file other.cer
and:
ovcert -importtrusted -file other.cer -ovrg server
On the HPOM management server and on all BSM Processing Servers, execute the following commands:
ovcert -importtrusted -file BSM _DPS<#>.cer
and:
ovcert -importtrusted -file BSM _DPS<#>.cer -ovrg server
If you have a multi-machine deployment, execute the following command on all Gateway Servers:
setupSecureCommunication <BSM BSM Data Processing server>
If you are not sure whether the agent was installed first, use the command ovconfchg -edit to check the hp.XplConfig.ovconfchg file. If sec.cm.client.certificate_server is set to the HPOM management server, then the agent was not installed first.
If the agent was installed on the system before the BSM server was installed, execute the following command on all Gateway servers:
ovcert -updatetrusted
Configure the load balancers and reverse proxies according to the instructions in the the HP Business Service Management Deployment Guide PDF depending on your certificate authority and setup. Make sure that the new Data Processing Server certificates are trusted if no central certificate authority is used.
After establishing a trust relationship between the BSM and HPOM systems, check the connection between the two systems.
To check the connection between BSM and HPOM:
From the HPOM management server, verify that communication to the BSM installation is possible (the return value should be eServiceOk
) by executing the following command on the HPOM server:
bbcutil -ping https://<BSM load_balancer, proxy server, or single_gateway_server>
Example of the command result:
https://<BSM servername>: status=eServiceOK
coreID=7c66bf42-d06b-752e-0e93-e82d1644cef8 bbcV=06.10.105
appN=ovbbccb appV=06.10.105 conn=1 time=1094 ms
From all BSM Processing Server hosts, verify that communication with the HPOM management server host is possible (the return value should be eServiceOk
) by executing the following command:
bbcutil -ping https://<HPOM_management_server_hostname>
Example of the command result:
htt
ps://<HPOM servername>: status=eServiceOK
coreID=0c43c032-5c94-7535-064a-f7654a86f2d3 bbcV=06.10.070
appN=ovbbccb appV=06.10.070 conn=7 time=140 ms
On the HPOM management server, add any new BSM Gateway Servers, load balancers, or reverse proxies to the list of target servers for discovery data.
Restart the discovery server processes on the HPOM management server:
HPOM for Windows:
net stop "OvAutoDiscovery Server"
net start "OvAutoDiscovery Server"
HPOM for UNIX or Linux:
ovc -stop opcsvcdisc
ovc -start opcsvcdisc
To allow event forwarding between HPOM and yoru two versions of BSM, you must modify the message forwarding policy on each HPOM management server with the node name of the load balancers, if configured, or one Gateway Server for each BSM-Operations Management installation, as appropriate for your high availability arrangement. This allows each HPOM management server to send messages to both the original OMi 8.10 and the new BSM 9.1x environments during the upgrade process.
During the migration, HPOM continues to attempt sending events to the OMi environment. If the OMi servers cannot be reached, HPOM starts to buffer the events until the servers are online again. This task describes how to adjust the maximum length of the delivery timeout and the maximum size of the buffer file in HPOMs. Depending on the length of the forwarding outage and the number of events, you need to increase the timeout and the buffer size so that HPOM does not discard any unsent events.
To configure HPOM for Windows event buffering, complete the following steps:
In the console tree, right-click Operations Manager, and then click ConfigureServer.... The Server Configuration dialog box appears.
Click Namespaces, and then click Server-based Flexible Management.
Change the value of Forwarding delivery timeout (in seconds) (default 1 hour). For example, to set the timeout to 2 days, type 172800.
Change the value of Forwarding queue size maximum (in megabytes) (default 50 MB). For example, to set the buffer size to 3 GB, type 3072.
Optional: Change the value of Forwarding queue size warning threshold (in megabytes) (default 40 MB). For example, to set the warning threshold to 2.5 GB, type 2560.
Click OK to save the new values and close the dialog.
To configure HPOM for UNIX or Linux event buffering, complete the following steps:
Adjust the timeout. For example, to set the timeout to 2 days, type:
ovconfchg -ovrg server -ns opc.opcforwm -set \
REQUEST_TIMEOUT 172800
Optional: In HPOM for UNIX or Linux, the buffer size is by default set to 0 (unlimited). To change the buffer size, type
ovconfchg -ovrg server -ns opc.opcforwm -set \
MAX_FILE_BUFFER_SIZE <bytes>
Optional: Check the current values of the HTTPS-based forwarding parameters, type:
ovconfget -ovrg server opc.opcforwm
The command displays only the non-default values.
This task describes how to convert the content packs that you exported from your OMi 8.10 installation in the step Exporting the OMi Configuration Data to the syntax and model required by the BSM 9.1x version.
The ContentMigration
migration tool is located in:
Windows: %TOPAZ_HOME%\opr\bin\ContentMigration.bat
Linux: /opt/HP/BSM/opr/bin/ContentMigration.sh
The ContentMigration
migration tool accepts the following options:
ContentMigration <inputFileName> <outputFileName>
[-A Availability_KPI_UUID] [-P Performance_KPI_UUID]
For more information about the parameters that the ContentMigration command, see the following list:
<inputFileName>
Name of the input file. This must be an OMi Content Pack in XML file format from OMi 8.10.
<outputFileName>
Name of the output file, to which the BSM 9.1x formatted content pack XML file is written.
[-A <Availability_KPI_UUID>]
Optional: Specify an alternative availabilty KPI as the standard availability KPI assignment. For details, see Alternative KPIs.
[-P <Performance_KPI_UUID>]
Optional: Specify an alternative performance KPI as the standard availability KPI assignment. For details, see Alternative KPIs.
Note: By default the OMi 8.10 KPI assignments to Availability
and Performance
are replaced by assignments to System Availability
and System Performance
respectively. To assign alternative KPIs as the standard availability KPI assignment, see Alternative KPIs in the BSM 9.1x Upgrade Guide.
To convert an OMi 8.10 content pack to the model and syntax required by BSM 9.1x:
Copy the exported data output file of the content packs that you exported from your OMi 8.10 installation in the step Exporting the OMi Configuration Data. Store the output file in a temporary location on the BSM 9.1x Gateway Server host system that is upgraded first, for example:
Windows: %TEMP%\migration
Linux: /tmp/migration
On the BSM 9.1x Gateway Server host system, convert the exported content packs:
To convert the exported snapshot of all OMi 8.10 content packs, enter the following command:
Windows: %TOPAZ_HOME%\opr\bin\ContentMigration <snapshot file name> <output file name>
Linux: /opt/HP/BSM/opr/bin/ContentMigration <snapshot file name> <output file name>
To convert the exported custom content pack that contains your OMi 8.10 modifications, enter the following command:
Windows: %TOPAZ_HOME%\opr\bin\ContentMigration <custom file name> <output file name>
Linux: /opt/HP/BSM/opr/bin/ContentMigration <custom file name> <output file name>
Substitute the appropriate file names and specify alternative KPIs, if necessary. See also Alternative KPIs.
Copy the converted OMi 8.10 content pack snapshot to the following location on the BSM 9.1x Gateway Server host system:
Windows: %TOPAZ_HOME%\conf\opr\content\migration
Linux: /opt/HP/BSM/conf/opr/content/migration
The upgrade wizard automatically uploads all converted content packs that reside in that location.
Note: Do not copy the converted OMi 8.10 custom content pack to that location because you must manually upload that content pack after the migration. For more information, see "Recreate your OMi 8.10 Modifications in 9.1x" in the BSM Upgrade Guide.
Optional: Delete the original, unconverted OMi 8.10 content packs from the following temporary directory on the BSM 9.1x Data Processing Server host system:
Windows: %TEMP%\migration
Linux: /tmp/migration
You can assign alternative KPIs to the default ones. To do this you need to know what KPIs are available and what their stableId attributes are in the SH-DefaultKPIs.xml file.
To assign alternative KPIs, complete the following steps:
Open the following file:
Windows: %TOPAZ_HOME%\conf\opr\content\en_US\SH-DefaultKPIs.xml
Linux: /opt/HP/BSM/conf/opr/content/en_US/SH-DefaultKPIs.xml
Select an alternative KPI by its stabeId attribute.
KPIs are contained in XML elements named <Dimension>. Select a KPI where the application attribute is equal to dashboard (application="dashboard").
Run the ContentMigration migration tool and specify the stableId attribute of the selected KPI for the -A or -P parameters.
ContentMigration <exported_OMi_8.10_content_pack>.xml <converted_BSM_9.1x_content_pack>.xml
-A <stableId_of_alternative_Availability_KPI>
-P <stableId_of_alternative_Performance_KPI>
If you have saved copies of OMi 8.10 icons for health indicators, copy the saved OMi 8.10 files to the BSM 9.1x installation.
Because some of the icons have changed in 9.1x, from a BSM 9.1x Gateway Server host system, make a backup copy of all the files in the following directory and subdirectories:
Windows: %TOPAZ_HOME%\AppServer\webapps\site.war\images\gui\severities
Linux: /opt/HP/BSM/AppServer/webapps/site.war/images/gui/severities
Copy the custom icon files that you saved from your OMi 8.10 installation in the step Backing Up OMi Configuration Files to the following location on the BSM 9.1x Gateway Server host system:
Windows: %TOPAZ_HOME%\AppServer\webapps\site.war\images\gui\severities
Linux: /opt/HP/BSM/AppServer/webapps/site.war/images/gui/severities
Secure environments only: To re-enable the trust relationship between the Java Runtime Environment (JRE) and the LDAP server, you must import the LDAP trusted certificate to the JRE truststore. For details, see the HP Business Service Management Hardening Guide PDF.
Prerequisites
Before installing a BSM service pack, it is recommended that you back up all BSM databases.
Before installing a BSM service pack, make sure that BSM has been fully stopped on all machines and that there are no open connections (for example, from Windows Explorer) from any machines to the BSM root directory or any of its subdirectories.
Download and install the service pack from the SSO site
Go to the SSO site:
Select Application Performance Management (BAC) > 9.13 (or the most recent service pack) and click Search to locate the installation files.
Save the package locally and launch the relevant setup file to install the Service Pack.
Run the installation files on all BSM servers (Gateway and Data Processing).
Run the post-installation wizard. This wizard follows the service pack installation automatically.
Reapply manual changes
If you have made changes in the HP BSM root directory to files that are updated during patch installation, for example while performing hardening procedures on your system, you must reapply those changes after patch installation on all relevant BSM machines. You can access your modified files from the backup folder located at: <HP BSM root directory>\installation\<PATCH_NAME>\backup\<PATH_TO_FILE>.
Enable BSM
Enable BSM on all servers.
Clear the repository type cache
The service pack contains a fix for an issue with context menus on the dashboard. If you are upgrading to BSM 9.13, you must activate the fix by clearing the repository type cache as follows:
In a web browser, open http://<gateway server>:8080/jmx-console.
Under Topaz, click service=repositories_manager.
Start cleanRepositoryTypeDBAndCache() with sCustId=0 and repositoryType=contextMenu.
Alter the ALL_EVENTS table
The service pack contains a fix for an issue with events that have an automatic action exceeding 255 characters in length. If you are upgrading to BSM 9.13, you (or your database administrator) must manually alter the ALL_EVENTS table in the BSM event schema database. You must increase the size of the AA_CALL column from 255 to 4000 characters.
Use one of the following SQL expressions:
For Microsoft SQL Server:
alter table ALL_EVENTS alter column AA_CALL nvarchar(4000)
For Oracle:
alter table ALL_EVENTS modify (AA_CALL varchar2(4000 CHAR));
Delete temporary internet files
Delete the browser's temporary Internet files on each browser that accesses BSM.
For more details, see Upgrade Wizard Overview in the BSM 9.1x Upgrade Guide.
Disable BSM servers. Disable all BSM servers before running the upgrade wizard
Multiple servers. If you have more than one Data Processing or Gateway Server, run the upgrade wizards on one of each type of server only. For each additional Data Processing and Gateway Server, run the the Setup and Database Configuration Utility. For more details, see Setup and Database Configuration Utility Overview in the BSM 9.1x Upgrade Guide.
Disable IDM-SSO. In the upgrade wizard, after the data from the management database has been transferred to the new system, disable IDM-SSO on the new environment. To do so, log into the JMX console (http://<Gateway Server name>:8080/jmx-console) and search for the SSO service (service=SSO). Locate the setSingleSignOnMode operation and in the ParamValue box, type Lightweight. Click Invoke.
Staging mode begins at the end of the upgrade wizard. During staging mode, the staging servers should be verified and configured as desired before moving them to production mode.
Remove the entry for the obsoleted OMi 8.10 installation from all HPOM message forwarding policies. For details on modifying an HPOM message forwarding policy, see the appropriate section below:
To enable communication between HPOM and OMi 8.10, the BAC 8.x servers were set up as managed nodes in HPOM (but no HP Operations Agent software installed). After the migration, the managed nodes that represent the BAC 8.x servers are no longer needed in HPOM and you can delete them. (The BSM 9.1x servers do not need to be added to HPOM to enable communication.)
Do not delete the BAC 8.x managed nodes if the HP Operations Agent software is installed and HPOM monitors the BAC 8.x servers for the purpose of system and performance management:
For direct upgrades, you must update the nodes’ core IDs in HPOM because the systems have received new certificates. For details, see Updating the Core IDs
If you are performing a staging upgrade and you want to monitor the new BSM 9.1x systems with HPOM, add the 9.1x systems as new managed nodes to HPOM and install the HP Operations Agent software to these nodes. For details, see the HPOM documentation.
Do not delete the BAC 8.x managed nodes if the HP Operations Agent software is installed and HPOM monitors the BAC 8.x servers for the purpose of system and performance management:
For direct upgrades, if this is the case, you must update the nodes' core IDs in HPOM because the systems have received new certificates. For details, select the appropriate drop-down:
If you are performing a staging upgrade and you want to monitor the new BSM 9.1x systems with HPOM, add the 9.1x systems as new managed nodes to HPOM and install the HP Operations Agent software to these nodes. For details, see the HPOM documentation.
Check whether the message forwarding policy for sending messages from HPOM to OMi is correctly configured as follows:
Make sure the BSM platform is running.
Make sure at least one open message interface policy is deployed on your HPOM system. For instructions and details, see the HPOM documentation.
On the HPOM system, open a command or a shell prompt.
Create a new message by executing the following command:
On the HPOM for Windows system:
opcmsg a=App o=Obj msg_text="Hello"
On the HPOM for UNIX and HPOM for Linux system:
/opt/OV/bin/OpC/opcmsg a=App o=Obj msg_text="Hello"
If you have correctly configured the server-based flexible management, the message arrives at the HPOM management server and is forwarded to OMi. You can view the events with the Operations Management Event Browser.
Note: If the message is sent multiple times, no new message is generated by HPOM. These messages are regarded as duplicates and only the message duplicate count is increased.
To verify the synchronization of HP OMi events with HPOM messages, complete the following steps:
Make sure the BSM platform is running.
Log on to the BSM platform management console.
Click Applications > Operations Management.
In the Event Browser, select an event that has been synchronized in HPOM and OMi earlier.
In the Event Details pane, click the Edit button of the General tab.
From the Severity drop-down list, choose another severity (for example, major) and click Save to change it to the selected severity.
In HPOM, verify the severity of this event and make sure it has been set to the new severity value.
If you have modified the out-of-the-box topology synchronization packages, you must manually recreate your changes in the 9.1x topology synchronization packages.
If you have created and saved your own custom topology synchronization packages in OMi 8.10, copy the saved custom packages to the BSM 9.1x installation. If these custom synchronization packages use out-of-the-box CI types, make sure that your synchronization packages still produce the desired results in BSM 9.1x, complete the following steps.
For more information about topology synchronization, see the HP Operations Manager i Extensibility Guide.
To validate topology synchronization, complete the following steps:
Copy the custom topology synchronization rules that you saved from your OMi 8.10 installation in the step Backing Up OMi Configuration Files to the following location on the BSM 9.1x Data Processing Server host system:
Windows: %TOPAZ_HOME%\conf\opr\topology-sync\sync-packages
Linux: /opt/HP/BSM/conf/opr/topology-sync/sync-packages
On the BSM 9.1x Data Processing Server host system, run basic topology synchronization. Open a command prompt or shell and type:
Windows: %TOPAZ_HOME%\bin\opr-startTopologySync.bat
Linux: /opt/HP/BSM/bin/opr-startTopologySync.sh
If out-of-the-box CI types have changed in BSM 9.1x, the synchronization process ends with errors. Check the synchronization log file:
Windows: %TOPAZ_HOME%\log\opr-topologysync
Linux: /opt/HP/BSM/log/opr-topologysync
Enable the data dump option and verify the CI attributes:
Navigate to the HPOM Topology Synchronization settings in the Infrastructure Settings Manager:
Infrastructure Settings > Applications > Operations Management > Operations Management - HPOM Topology Synchronization Settings > Dump data
Change the value of Dump data to true.
Run the Topology Sync tool with the following command:
Windows: <HPBSM root directory>/bin/opr-startTopologySync.bat
Linux: <HPBSM root directory>/bin/opr-startTopologySync.sh
Check if the file in the following directory contains all expected attributes for the CIs of your synchronization package:
Windows: %TOPAZ_HOME%\opr\tmp\datadump\postenrichment
Linux: /opt/HP/BSM/opr/tmp/datadump/postenrichment
Use the BSM 9.1x CI Type Manager to find changed CI types, adapt your mapping rules, and run topology synchronization again.
Repeat this process until all mapping errors have been resolved.
For more information about topology synchronization, see the HP Operations Manager i Extensibility Guide.
If you upgraded the SPIs to SPI DVD release 2010 before the migration, you must manually recreate the modifications that you applied to the OMi 8.10 content in your 9.1x installation.
Alternatively, if you exported and converted a custom content pack, upload the custom content pack in create
mode after the migration.
To recreate upload the custom content pack in create mode, complete the following steps:
Change to the temporary location on the BSM 9.1x Gateway Server host system, where the converted custom content pack resides, for example:
Windows: %TEMP%\migration
Linux: /tmp/migration
Upload the custom content pack in create
mode, enter the following command:
<HPBSM Install Directory>/opr/bin/ContentManager -username admin -password admin -i <converted custom content pack>
Where the administrator account must have read and write access to the Content Manager.
Verify the uploaded content pack in the Content Packs Manager.
If you did not upgrade the SPIs to the SPI DVD 2010 release before the migration, but rather decide to switch to the new SPIs after the migration, you must reimport the 9.1x content with overwrite mode. However, the overwrite mode will overwrite all of your modifications. You must then manually recreate your OMi 8.10 modifications in the 9.1x content.
To reimport 9.1x content, complete the following steps:
Upgrade the HP Operations SPIs to SPI DVD release 2010 as described in the documentation provided with the SPIs.
Reimport the 9.1x content in overwrite mode, enter the following command:
<HPBSM Install Directory>/opr/bin/ContentManager -username admin -password admin -a -forceReload -f
Manually recreate your OMi 8.10 modifications in the 9.1x content.
For BPM profiles upgraded to applications, manually reconfigure the correct time zones. A configuration file was used to map time zone offsets (used by the old model) and time zone IDs (used by the new model). The first time zone ID that matched the time zone offset was used.
When you are confident that you are ready to use your staging servers as your production environment, perform the following tasks:
Transfer the data collectors to the new servers by setting the Load Balancer(s) to communicate with the new servers. If you are not using Load Balancers, you must configure each data collector individually to communicate with the new servers.
End the SDR and unsubscribe it from the source server. For details, see Staging Data Replicator in the BSM 9.1x Upgrade Guide.
In the new BSM server(s), log in and select Admin > Platform > Infrastructure Settings > Foundations > Platform Administration. In the HP BSM Evaluation table, modify Enable Evaluation Mode and Enable Evaluation Mode for Customer to false.
We recommend backing up the database schemas as close as possible to the 8.0x uninstall as possible to minimize the risk of data loss.
Manually copy the LDAP database from the original BAC Gateway Server. The upgrade wizard will instruct you when and how to restore the LDAP database.
Open the Nanny Manager management console on the production Gateway Server that is running the LDAP by using the url http://localhost:11021.
Invoke the stopService method with ldap as the serviceName parameter value.
Verify that the slapd process is not running. Wait until the process is stopped before proceeding.
Back up the bdb folder from the <Gateway Server installation directory>\openldap directory in the original BAC Gateway Server. Note the folder structure as you will need to eventually restore this folder using the same structure.
Back up the following folders and files from the BAC 8.0x server(s). The upgrade wizard will tell you when to restore them.
<BAC Data Processing Server installation directory>\CMDB\adapters\adapters
<BAC Data Processing Server installation directory>\CMDB\general
All custom rules jar files from the <BAC Data Processing Server installation directory>\BLE\rules folder
If you used User Reports to create excel reports, back them up as well. The reports are stored in the <Gateway Server>\HPBSM\AppServer\webapps\site.war\openapi\excels\ directory in folders for each customer ID.
Disable and uninstall the BAC 8.0x server(s). For details, see Uninstalling HP Business Service Management Servers in the BSM 9.1x Upgrade Guide.
Run the installation and post-installation wizards. If you have a distributed deployment, run the wizards on the Data Processing Server first. The wizards will direct when to begin running the wizards on the Gateway Server.
Note: Important: If you are upgrading from 7.5 using the staging/staging method, at the end of the post-installation wizard specify that you are upgrading from 8.x, not 7.5.
For details about installing on a Windows platform, see Installing BSM Servers on a Windows Platform in the BSM 9.10 Upgrade Guide.
For details about installing on a Linux platform, see Installing BSM Servers on a Linux Platform in the BSM 9.10 Upgrade Guide.
For connection and communication between the BSM and HPOM systems, you must establish a trust relationship between the systems.
Note: The following steps use the ovcert, ovconfchg, and bbcutil command line tools. The tools are located in:
To establish a trust relationship between BSM and HPOM systems, do the following:
Ensure that certificates have been set up on the Gateway and Processing Servers. For details, see "Post-Installation Tasks" in the the HP Business Service Management Deployment Guide PDF.
On all BSM Processing Servers, execute the following command:
ovcert -exporttrusted -file BSM _DPS<#>.cer
On the HPOM management server, execute the following command:
ovcert -exporttrusted -file other.cer
Copy other.cer from the HPOM management server to all BSM Processing Servers.
Copy BSM_DPS<#>.cer from the BSM Processing Server to the HPOM management server and all other BSM Processing Servers.
On all BSM Processing Servers, execute the following commands:
ovcert -importtrusted -file other.cer
and:
ovcert -importtrusted -file other.cer -ovrg server
On the HPOM management server and on all BSM Processing Servers, execute the following commands:
ovcert -importtrusted -file BSM _DPS<#>.cer
and:
ovcert -importtrusted -file BSM _DPS<#>.cer -ovrg server
If you have a multi-machine deployment, execute the following command on all Gateway Servers:
setupSecureCommunication <BSM BSM Data Processing server>
If you are not sure whether the agent was installed first, use the command ovconfchg -edit to check the hp.XplConfig.ovconfchg file. If sec.cm.client.certificate_server is set to the HPOM management server, then the agent was not installed first.
If the agent was installed on the system before the BSM server was installed, execute the following command on all Gateway servers:
ovcert -updatetrusted
Configure the load balancers and reverse proxies according to the instructions in the the HP Business Service Management Deployment Guide PDF depending on your certificate authority and setup. Make sure that the new Data Processing Server certificates are trusted if no central certificate authority is used.
After establishing a trust relationship between the BSM and HPOM systems, check the connection between the two systems.
To check the connection between BSM and HPOM:
From the HPOM management server, verify that communication to the BSM installation is possible (the return value should be eServiceOk
) by executing the following command on the HPOM server:
bbcutil -ping https://<BSM load_balancer, proxy server, or single_gateway_server>
Example of the command result:
https://<BSM servername>: status=eServiceOK
coreID=7c66bf42-d06b-752e-0e93-e82d1644cef8 bbcV=06.10.105
appN=ovbbccb appV=06.10.105 conn=1 time=1094 ms
From all BSM Processing Server hosts, verify that communication with the HPOM management server host is possible (the return value should be eServiceOk
) by executing the following command:
bbcutil -ping https://<HPOM_management_server_hostname>
Example of the command result:
htt
ps://<HPOM servername>: status=eServiceOK
coreID=0c43c032-5c94-7535-064a-f7654a86f2d3 bbcV=06.10.070
appN=ovbbccb appV=06.10.070 conn=7 time=140 ms
On the HPOM management server, add any new BSM Gateway Servers, load balancers, or reverse proxies to the list of target servers for discovery data.
Restart the discovery server processes on the HPOM management server:
HPOM for Windows:
net stop "OvAutoDiscovery Server"
net start "OvAutoDiscovery Server"
HPOM for UNIX or Linux:
ovc -stop opcsvcdisc
ovc -start opcsvcdisc
To allow event forwarding between HPOM and yoru two versions of BSM, you must modify the message forwarding policy on each HPOM management server with the node name of the load balancers, if configured, or one Gateway Server for each BSM-Operations Management installation, as appropriate for your high availability arrangement. This allows each HPOM management server to send messages to both the original OMi 8.10 and the new BSM 9.1x environments during the upgrade process.
During the migration, HPOM continues to attempt sending events to the OMi environment. If the OMi servers cannot be reached, HPOM starts to buffer the events until the servers are online again. This task describes how to adjust the maximum length of the delivery timeout and the maximum size of the buffer file in HPOMs. Depending on the length of the forwarding outage and the number of events, you need to increase the timeout and the buffer size so that HPOM does not discard any unsent events.
To configure HPOM for Windows event buffering, complete the following steps:
In the console tree, right-click Operations Manager, and then click ConfigureServer.... The Server Configuration dialog box appears.
Click Namespaces, and then click Server-based Flexible Management.
Change the value of Forwarding delivery timeout (in seconds) (default 1 hour). For example, to set the timeout to 2 days, type 172800.
Change the value of Forwarding queue size maximum (in megabytes) (default 50 MB). For example, to set the buffer size to 3 GB, type 3072.
Optional: Change the value of Forwarding queue size warning threshold (in megabytes) (default 40 MB). For example, to set the warning threshold to 2.5 GB, type 2560.
Click OK to save the new values and close the dialog.
To configure HPOM for UNIX or Linux event buffering, complete the following steps:
Adjust the timeout. For example, to set the timeout to 2 days, type:
ovconfchg -ovrg server -ns opc.opcforwm -set \
REQUEST_TIMEOUT 172800
Optional: In HPOM for UNIX or Linux, the buffer size is by default set to 0 (unlimited). To change the buffer size, type
ovconfchg -ovrg server -ns opc.opcforwm -set \
MAX_FILE_BUFFER_SIZE <bytes>
Optional: Check the current values of the HTTPS-based forwarding parameters, type:
ovconfget -ovrg server opc.opcforwm
The command displays only the non-default values.
This task describes how to convert the content packs that you exported from your OMi 8.10 installation in the step Exporting the OMi Configuration Data to the syntax and model required by the BSM 9.1x version.
The ContentMigration
migration tool is located in:
Windows: %TOPAZ_HOME%\opr\bin\ContentMigration.bat
Linux: /opt/HP/BSM/opr/bin/ContentMigration.sh
The ContentMigration
migration tool accepts the following options:
ContentMigration <inputFileName> <outputFileName>
[-A Availability_KPI_UUID] [-P Performance_KPI_UUID]
For more information about the parameters that the ContentMigration command, see the following list:
<inputFileName>
Name of the input file. This must be an OMi Content Pack in XML file format from OMi 8.10.
<outputFileName>
Name of the output file, to which the BSM 9.1x formatted content pack XML file is written.
[-A <Availability_KPI_UUID>]
Optional: Specify an alternative availabilty KPI as the standard availability KPI assignment. For details, see Alternative KPIs.
[-P <Performance_KPI_UUID>]
Optional: Specify an alternative performance KPI as the standard availability KPI assignment. For details, see Alternative KPIs.
Note: By default the OMi 8.10 KPI assignments to Availability
and Performance
are replaced by assignments to System Availability
and System Performance
respectively. To assign alternative KPIs as the standard availability KPI assignment, see Alternative KPIs in the BSM 9.1x Upgrade Guide.
To convert an OMi 8.10 content pack to the model and syntax required by BSM 9.1x:
Copy the exported data output file of the content packs that you exported from your OMi 8.10 installation in the step Exporting the OMi Configuration Data. Store the output file in a temporary location on the BSM 9.1x Gateway Server host system that is upgraded first, for example:
Windows: %TEMP%\migration
Linux: /tmp/migration
On the BSM 9.1x Gateway Server host system, convert the exported content packs:
To convert the exported snapshot of all OMi 8.10 content packs, enter the following command:
Windows: %TOPAZ_HOME%\opr\bin\ContentMigration <snapshot file name> <output file name>
Linux: /opt/HP/BSM/opr/bin/ContentMigration <snapshot file name> <output file name>
To convert the exported custom content pack that contains your OMi 8.10 modifications, enter the following command:
Windows: %TOPAZ_HOME%\opr\bin\ContentMigration <custom file name> <output file name>
Linux: /opt/HP/BSM/opr/bin/ContentMigration <custom file name> <output file name>
Substitute the appropriate file names and specify alternative KPIs, if necessary. See also Alternative KPIs.
Copy the converted OMi 8.10 content pack snapshot to the following location on the BSM 9.1x Gateway Server host system:
Windows: %TOPAZ_HOME%\conf\opr\content\migration
Linux: /opt/HP/BSM/conf/opr/content/migration
The upgrade wizard automatically uploads all converted content packs that reside in that location.
Note: Do not copy the converted OMi 8.10 custom content pack to that location because you must manually upload that content pack after the migration. For more information, see "Recreate your OMi 8.10 Modifications in 9.1x" in the BSM Upgrade Guide.
Optional: Delete the original, unconverted OMi 8.10 content packs from the following temporary directory on the BSM 9.1x Data Processing Server host system:
Windows: %TEMP%\migration
Linux: /tmp/migration
You can assign alternative KPIs to the default ones. To do this you need to know what KPIs are available and what their stableId attributes are in the SH-DefaultKPIs.xml file.
To assign alternative KPIs, complete the following steps:
Open the following file:
Windows: %TOPAZ_HOME%\conf\opr\content\en_US\SH-DefaultKPIs.xml
Linux: /opt/HP/BSM/conf/opr/content/en_US/SH-DefaultKPIs.xml
Select an alternative KPI by its stabeId attribute.
KPIs are contained in XML elements named <Dimension>. Select a KPI where the application attribute is equal to dashboard (application="dashboard").
Run the ContentMigration migration tool and specify the stableId attribute of the selected KPI for the -A or -P parameters.
ContentMigration <exported_OMi_8.10_content_pack>.xml <converted_BSM_9.1x_content_pack>.xml
-A <stableId_of_alternative_Availability_KPI>
-P <stableId_of_alternative_Performance_KPI>
If you have saved copies of OMi 8.10 icons for health indicators, copy the saved OMi 8.10 files to the BSM 9.1x installation.
Because some of the icons have changed in 9.1x, from a BSM 9.1x Gateway Server host system, make a backup copy of all the files in the following directory and subdirectories:
Windows: %TOPAZ_HOME%\AppServer\webapps\site.war\images\gui\severities
Linux: /opt/HP/BSM/AppServer/webapps/site.war/images/gui/severities
Copy the custom icon files that you saved from your OMi 8.10 installation in the step Backing Up OMi Configuration Files to the following location on the BSM 9.1x Gateway Server host system:
Windows: %TOPAZ_HOME%\AppServer\webapps\site.war\images\gui\severities
Linux: /opt/HP/BSM/AppServer/webapps/site.war/images/gui/severities
Secure environments only: To re-enable the trust relationship between the Java Runtime Environment (JRE) and the LDAP server, you must import the LDAP trusted certificate to the JRE truststore. For details, see the HP Business Service Management Hardening Guide PDF.
Prerequisites
Before installing a BSM service pack, it is recommended that you back up all BSM databases.
Before installing a BSM service pack, make sure that BSM has been fully stopped on all machines and that there are no open connections (for example, from Windows Explorer) from any machines to the BSM root directory or any of its subdirectories.
Download and install the service pack from the SSO site
Go to the SSO site:
Select Application Performance Management (BAC) > 9.13 (or the most recent service pack) and click Search to locate the installation files.
Save the package locally and launch the relevant setup file to install the Service Pack.
Run the installation files on all BSM servers (Gateway and Data Processing).
Run the post-installation wizard. This wizard follows the service pack installation automatically.
Reapply manual changes
If you have made changes in the HP BSM root directory to files that are updated during patch installation, for example while performing hardening procedures on your system, you must reapply those changes after patch installation on all relevant BSM machines. You can access your modified files from the backup folder located at: <HP BSM root directory>\installation\<PATCH_NAME>\backup\<PATH_TO_FILE>.
Enable BSM
Enable BSM on all servers.
Clear the repository type cache
The service pack contains a fix for an issue with context menus on the dashboard. If you are upgrading to BSM 9.13, you must activate the fix by clearing the repository type cache as follows:
In a web browser, open http://<gateway server>:8080/jmx-console.
Under Topaz, click service=repositories_manager.
Start cleanRepositoryTypeDBAndCache() with sCustId=0 and repositoryType=contextMenu.
Alter the ALL_EVENTS table
The service pack contains a fix for an issue with events that have an automatic action exceeding 255 characters in length. If you are upgrading to BSM 9.13, you (or your database administrator) must manually alter the ALL_EVENTS table in the BSM event schema database. You must increase the size of the AA_CALL column from 255 to 4000 characters.
Use one of the following SQL expressions:
For Microsoft SQL Server:
alter table ALL_EVENTS alter column AA_CALL nvarchar(4000)
For Oracle:
alter table ALL_EVENTS modify (AA_CALL varchar2(4000 CHAR));
Delete temporary internet files
Delete the browser's temporary Internet files on each browser that accesses BSM.
For more details, see Upgrade Wizard Overview in the BSM 9.1x Upgrade Guide.
Disable BSM servers. Disable all BSM servers before running the upgrade wizard
Multiple servers. If you have more than one Data Processing or Gateway Server, run the upgrade wizards on one of each type of server only. For each additional Data Processing and Gateway Server, run the the Setup and Database Configuration Utility. For more details, see Setup and Database Configuration Utility Overview in the BSM 9.1x Upgrade Guide.
Disable IDM-SSO. In the upgrade wizard, after the data from the management database has been transferred to the new system, disable IDM-SSO on the new environment. To do so, log into the JMX console (http://<Gateway Server name>:8080/jmx-console) and search for the SSO service (service=SSO). Locate the setSingleSignOnMode operation and in the ParamValue box, type Lightweight. Click Invoke.
Disable any firewalls that exist between BSM Gateway and Data Processing Server servers. By default, Windows Server 2003 SP1 and later versions include such a firewall. It must be manually disabled.
If you have more than one BSM Data Processing server, you need to establish trust to enable communication between the servers.
For each additional Data Processing Server, complete the following configuration appropriate for your environment:
If you have a central certificate authority, make sure that the CA root certificate was already imported into the OV certificate repository on all BSM Data Processing Servers using the following command:
ovcert - importtrusted -file c:\ca_root.pem
ovcert - importtrusted -file c:\ca_root.pem -ovrg server
From the primary Data Processing Server, export the trusted certificates using the following command:
ovcert -exporttrusted -file <file with certificate>
Copy the exported trusted certificates to the new Data Processing Server and install the certificates on new Data Processing Server using the following commands:
ovcert -importtrusted -file <file with certificate>
ovcert -importtrusted -file <file with certificate> -ovrg server
On new Data Processing Servers, export certificates using the command:
ovcert -exporttrusted -file < file with certificate>
Copy this file to all your existing Data Processing Servers and import using the following commands:
ovcert -importtrusted -file <file with certificate>
ovcert -importtrusted -file <file with certificate> -ovrg server
If you have an integration with HPOM (Windows or Unix) follow the procedure "How to Establish a Trust Relationship between BSM and External Servers" in Solutions and Integrations for every Data Processing server.
Update trusted certificates using the ovcert -updatetrusted command on following servers:
All Gateway servers
All HP Diagnostics servers
All SiteScope servers
All Integration Adapter servers
Operations Management and other HP BTO Software applications use certificates that enable to clients and servers to identify themselves and communicate securely with each other. The data processing server can issue the required certificates to other servers in your environment, acting as a certificate authority.
If you have a one-machine deployment, the installation configures the certificates that you need. You do not need to configure gateway server certificates.
However, if you have a distributed deployment, after you install your BSM servers, you must make sure that every gateway server requests certificates from the data processing server. You must then make sure that the data processing server grants each certificate request.
Note: If BSM is required to issue certificates, for example, for an Integration Adapter, then the Gateway Servers must be configured to forward all incoming requests to the Data Processing Server. The Data Processing Server must be configured in the Operations Management Infrastructure Settings: Applications > Operations Management > Certificate Server Settings > Certificate Server IP Address.
To request certificates for gateway servers:
On each gateway server, open a command prompt, and then type the appropriate command depending on your operating system:
Windows: cd %TOPAZ_HOME%/bin
Linux: cd /opt/HP/BSM/bin
Start the following command:
setup-secure-communication
The command prompts you for the DNS name of the data processing server. Type this name, and then press Enter.
To grant certificate requests:
On the data processing server, open a command prompt, and then type the appropriate command depending on your operating system:
Windows: cd %TOPAZ_HOME%\bin
Linux: cd /opt/HP/BSM/bin
Start the following command:
setup-secure-communication
The command checks for pending certificate requests. For each pending certificate request, the command shows details of the request. For example:
INFO: Secure communication request from: gateway1.example.com
Press g to grant each request in turn. After you grant a certificate request, the command sends certificates to the gateway server, and then verifies that secure communication is possible.
If you have more than one Data Processing server, repeat the above procedures for each Data Processing server.
If you are planning to use Operations Manager i, perform the following steps:
Go to Admin > RTSM Administration > Modeling > CI Type Manager.
From the CI Types list select System Type Manager.
Select product_name_enum and click Edit.
Type lync_server and click Add.
Click OK.
You can see the installation log file by clicking the View log file link at the bottom of the installer window.
In a Windows environment, this log file, along with additional log files for separate installation packages, is located in the %temp%\..\HPOvInstaller\HPBsm_9.10 directory.
In a Linux environment, the logs files are located in the /tmp/HPOvInstaller/HPBsm_9.10 directory.
The installer log file name is in the following format:
HPBsm_<VERSION>_<DATE>_ HPOvInstallerLog.html or HPBsm_<VERSION>_<DATE>_ HPOvInstallerLog.txt (for example, HPBsm_9.10_2010.10.21_13_34_HPOvInstallerLog.html
).
Individual installation package log file names are in the following format:
Package_<PACKAGE_TYPE>_HPBSM_<PACKAGE_NAME>_install.log (for example, Package_msi_HPBSM_BPIPkg_install.log
).
Remove the entry for the obsoleted OMi 8.10 installation from all HPOM message forwarding policies. For details on modifying an HPOM message forwarding policy, see the appropriate section below:
To enable communication between HPOM and OMi 8.10, the BAC 8.x servers were set up as managed nodes in HPOM (but no HP Operations Agent software installed). After the migration, the managed nodes that represent the BAC 8.x servers are no longer needed in HPOM and you can delete them. (The BSM 9.1x servers do not need to be added to HPOM to enable communication.)
Do not delete the BAC 8.x managed nodes if the HP Operations Agent software is installed and HPOM monitors the BAC 8.x servers for the purpose of system and performance management:
For direct upgrades, you must update the nodes’ core IDs in HPOM because the systems have received new certificates. For details, see Updating the Core IDs
If you are performing a staging upgrade and you want to monitor the new BSM 9.1x systems with HPOM, add the 9.1x systems as new managed nodes to HPOM and install the HP Operations Agent software to these nodes. For details, see the HPOM documentation.
Do not delete the BAC 8.x managed nodes if the HP Operations Agent software is installed and HPOM monitors the BAC 8.x servers for the purpose of system and performance management:
For direct upgrades, if this is the case, you must update the nodes' core IDs in HPOM because the systems have received new certificates. For details, select the appropriate drop-down:
If you are performing a staging upgrade and you want to monitor the new BSM 9.1x systems with HPOM, add the 9.1x systems as new managed nodes to HPOM and install the HP Operations Agent software to these nodes. For details, see the HPOM documentation.
Check whether the message forwarding policy for sending messages from HPOM to OMi is correctly configured as follows:
Make sure the BSM platform is running.
Make sure at least one open message interface policy is deployed on your HPOM system. For instructions and details, see the HPOM documentation.
On the HPOM system, open a command or a shell prompt.
Create a new message by executing the following command:
On the HPOM for Windows system:
opcmsg a=App o=Obj msg_text="Hello"
On the HPOM for UNIX and HPOM for Linux system:
/opt/OV/bin/OpC/opcmsg a=App o=Obj msg_text="Hello"
If you have correctly configured the server-based flexible management, the message arrives at the HPOM management server and is forwarded to OMi. You can view the events with the Operations Management Event Browser.
Note: If the message is sent multiple times, no new message is generated by HPOM. These messages are regarded as duplicates and only the message duplicate count is increased.
To verify the synchronization of HP OMi events with HPOM messages, complete the following steps:
Make sure the BSM platform is running.
Log on to the BSM platform management console.
Click Applications > Operations Management.
In the Event Browser, select an event that has been synchronized in HPOM and OMi earlier.
In the Event Details pane, click the Edit button of the General tab.
From the Severity drop-down list, choose another severity (for example, major) and click Save to change it to the selected severity.
In HPOM, verify the severity of this event and make sure it has been set to the new severity value.
If you have modified the out-of-the-box topology synchronization packages, you must manually recreate your changes in the 9.1x topology synchronization packages.
If you have created and saved your own custom topology synchronization packages in OMi 8.10, copy the saved custom packages to the BSM 9.1x installation. If these custom synchronization packages use out-of-the-box CI types, make sure that your synchronization packages still produce the desired results in BSM 9.1x, complete the following steps.
For more information about topology synchronization, see the HP Operations Manager i Extensibility Guide.
To validate topology synchronization, complete the following steps:
Copy the custom topology synchronization rules that you saved from your OMi 8.10 installation in the step Backing Up OMi Configuration Files to the following location on the BSM 9.1x Data Processing Server host system:
Windows: %TOPAZ_HOME%\conf\opr\topology-sync\sync-packages
Linux: /opt/HP/BSM/conf/opr/topology-sync/sync-packages
On the BSM 9.1x Data Processing Server host system, run basic topology synchronization. Open a command prompt or shell and type:
Windows: %TOPAZ_HOME%\bin\opr-startTopologySync.bat
Linux: /opt/HP/BSM/bin/opr-startTopologySync.sh
If out-of-the-box CI types have changed in BSM 9.1x, the synchronization process ends with errors. Check the synchronization log file:
Windows: %TOPAZ_HOME%\log\opr-topologysync
Linux: /opt/HP/BSM/log/opr-topologysync
Enable the data dump option and verify the CI attributes:
Navigate to the HPOM Topology Synchronization settings in the Infrastructure Settings Manager:
Infrastructure Settings > Applications > Operations Management > Operations Management - HPOM Topology Synchronization Settings > Dump data
Change the value of Dump data to true.
Run the Topology Sync tool with the following command:
Windows: <HPBSM root directory>/bin/opr-startTopologySync.bat
Linux: <HPBSM root directory>/bin/opr-startTopologySync.sh
Check if the file in the following directory contains all expected attributes for the CIs of your synchronization package:
Windows: %TOPAZ_HOME%\opr\tmp\datadump\postenrichment
Linux: /opt/HP/BSM/opr/tmp/datadump/postenrichment
Use the BSM 9.1x CI Type Manager to find changed CI types, adapt your mapping rules, and run topology synchronization again.
Repeat this process until all mapping errors have been resolved.
For more information about topology synchronization, see the HP Operations Manager i Extensibility Guide.
If you upgraded the SPIs to SPI DVD release 2010 before the migration, you must manually recreate the modifications that you applied to the OMi 8.10 content in your 9.1x installation.
Alternatively, if you exported and converted a custom content pack, upload the custom content pack in create
mode after the migration.
To recreate upload the custom content pack in create mode, complete the following steps:
Change to the temporary location on the BSM 9.1x Gateway Server host system, where the converted custom content pack resides, for example:
Windows: %TEMP%\migration
Linux: /tmp/migration
Upload the custom content pack in create
mode, enter the following command:
<HPBSM Install Directory>/opr/bin/ContentManager -username admin -password admin -i <converted custom content pack>
Where the administrator account must have read and write access to the Content Manager.
Verify the uploaded content pack in the Content Packs Manager.
If you did not upgrade the SPIs to the SPI DVD 2010 release before the migration, but rather decide to switch to the new SPIs after the migration, you must reimport the 9.1x content with overwrite mode. However, the overwrite mode will overwrite all of your modifications. You must then manually recreate your OMi 8.10 modifications in the 9.1x content.
To reimport 9.1x content, complete the following steps:
Upgrade the HP Operations SPIs to SPI DVD release 2010 as described in the documentation provided with the SPIs.
Reimport the 9.1x content in overwrite mode, enter the following command:
<HPBSM Install Directory>/opr/bin/ContentManager -username admin -password admin -a -forceReload -f
Manually recreate your OMi 8.10 modifications in the 9.1x content.
For BPM profiles upgraded to applications, manually reconfigure the correct time zones. A configuration file was used to map time zone offsets (used by the old model) and time zone IDs (used by the new model). The first time zone ID that matched the time zone offset was used.
If you manually configured different users to run BSM services, these settings must be configured again. For details, see "Changing BSM Service Users" in the BSM 9.1x Upgrade Guidepdf.
If your original environment was secured with SSL, you need to re-establish the trust to the certificate authority that issued server certificates for the BSM virtual servers. Additionally, you may need to repeat other hardening procedure. We recommend performing the hardening procedures again. For details, see the HP Business Service Management Hardening Guide PDF.
We recommend that you update all components associated with BSM.
Disable the BSM server(s) by selecting Start > Programs > HP Business Service Management > Administration > Disable Business Service Management.
If you are using an Oracle database, make sure that the parameter RECYCLEBIN is set to Off, as specified in the HP Business Service Management Database Guide PDF.
We recommend backing up the database schema as close as possible to the uninstall to minimize the risk of data loss.
Note: If you have added any custom SiteScope monitors in SAM Admin > Metrics and Indicators, you must manually backup the following file and restore it to the same location after BSM 9.1 is installed (before configuring the management database schema) HPBSM\webapps\site.war\WEB-INF\sam\hi-mapping-monitors.xml.
In order to preserve your certificate authority configuration, you must back up the data before BSM 9.0x is uninstalled and restore it after the upgrade. This procedure is only required if you are using one or more of the following components:
HP Diagnostics
SiteScope
Integration Adapter
HPOM
OMi
NNMi
To save the certificate authority configurations, run the following commands on the Data Processing Server. Note that these are lists of commands that must be run one line at a time:
For Windows:
ovcm -exportcacert -file %TEMP%\migration\oldca.p12
ovcert -exporttrusted -file %TEMP%\migration\oldtrust.pem
ovcert -exportcert -file %TEMP%\migration\oldcert.p12
ovcoreid > %TEMP%\migration\oldcoreid
For Linux:
ovcm -exportcacert -file /tmp/migration/oldca.p12
ovcert -exporttrusted -file /tmp/migration/oldtrust.pem
ovcert -exportcert -file /tmp/migration/oldcert.p12
ovcoreid > /tmp/migration/oldcoreid
If you have customized the OMi integration with HP Service Manager or any topology synchronization data, back up your customized files before starting the upgrade to BSM 9.1x. Back up the following directories:
%TOPAZ_HOME%\conf\opr\integration
%TOPAZ_HOME%\conf\opr\topology-sync
In BSM 9.0x, it is possible to modify health indicators (HIs) that child configuration item types (CITs) acquire from their parent CITs. Modifications include, for example, changing the display name or description. When you modify an inherited HI its UUID changes but the name remains the same. Subsequent uploads of content packs in overwrite
mode then lead to errors like the following:
Indicator with id: <uuid>. Cause: Indicator already exists with the same name for this CI type hierarchy. Indicator name: <indicator>.
To prevent upload problems, perform the following steps:
Before the upgrade, merge the changes applied to inherited indicators with the original indicator defined for the parent CIT.
Go to Admin > Service Health > Repositories. Select the child CIT and the health indicator that you have modified. Check you changes and then apply them to the HI of the parent CIT.
Delete the modified HI.
Alternatively, before the upgrade, make a note of your HI modifications, and then delete the modified HIs. After the upgrade, create new HIs for the child CITs, based on your notes.
You must delete the TV Content Pack and the TVDiag Shared Content Pack definitions (if their IDs start with a specific string) before beginning to upgrade to BSM 9.10. Otherwise the upload fails with the following error in opr-admin.log:
A Content Pack Definition with the name [TV_Content_Pack] and a different ID already exists.
To delete TV content pack definitions, complete the following steps:
Open the Content Packs Manager:
Admin > Platform > Content Packs
In the Content Packs Definitions pane, select TV Content Pack
and edit it. If the ID starts with 6f0
, delete the content pack definition.
In the Content Packs Definitions pane, select TVDiag Shared Content Pack
and edit it. If the ID starts with 045
, delete the content pack definition.
The upgrade may fail if more than one downtime category with the same name exists. You must therefore delete all duplicate downtime categories before beginning the upgrade to BSM 9.10.
To delete duplicate Downtime Categories, complete the following steps:
Navigate to the Downtime Behavior manager:
Admin > Operations Management > Tune Operations Management > Downtime Behavior
Refresh the list of categories.
If there is more than one entry per category, delete the duplicate categories. Access the Event Schema database using a database administration tool (for example, Microsoft SQL Server Management Studio).
Open the table DOWNTIME_CONFIG
.
Make sure there is only one line per DT_CATEGORY_ID
.
Delete all other rows with that ID or change the ID to another existing Downtime Category.
The 9.0x Content Pack for Blackberry Enterprise Server generates unique IDs for configuration item type to graph family assignments. Because the IDs are different in each BSM installation, the upload of the new 9.1x Blackberry content pack fails. To avoid upload problems after the upgrade, delete the graph family assignments before the upgrade. The upload of the 9.1x Blackberry content pack recreates the correct assignments.
To delete graph family assignments, complete the following steps:
Navigate to the Performance Graphs manager:
Admin > Operations Management > Design Operations Content > Performance Graphs
In the CI Types pane, select ConfigurationItem > Infrastructure Element > Running Software > Application Server > BB Component.
In the Performance Graphs pane, click the Delete Item toolbar button to remove the performance graphs configuration from the selected CI type.
To avoid lengthy database upgrades, it is recommended that you archive your open and closed OMi events before starting the upgrade wizard. You should not keep more than 100,000 events in the database. To archive OMi events, use the archive tool opr-archive-events. For details about opr-archive-events, see the Operations Management online help.
Uninstall BSM 9.0x on all BSM servers. For task details, see the BSM 9.1x Upgrade Guide.
Run the installation and post-installation wizards. If you have a distributed deployment, run the wizards on the Data Processing Server first. The wizards will direct when to begin running the wizards on the Gateway Server.
Note: Important: If you are upgrading from 7.5 using the staging/staging method, at the end of the post-installation wizard specify that you are upgrading from 8.x, not 7.5.
For details about installing on a Windows platform, see Installing BSM Servers on a Windows Platform in the BSM 9.10 Upgrade Guide.
For details about installing on a Linux platform, see Installing BSM Servers on a Linux Platform in the BSM 9.10 Upgrade Guide.
To restore the certificate authority configuration that you backed up earlier, follow the appropriate procedure depending on your operating system:
Disable any firewalls that exist between BSM Gateway and Data Processing Server servers. By default, Windows Server 2003 SP1 and later versions include such a firewall. It must be manually disabled.
If you have more than one BSM Data Processing server, you need to establish trust to enable communication between the servers.
For each additional Data Processing Server, complete the following configuration appropriate for your environment:
If you have a central certificate authority, make sure that the CA root certificate was already imported into the OV certificate repository on all BSM Data Processing Servers using the following command:
ovcert - importtrusted -file c:\ca_root.pem
ovcert - importtrusted -file c:\ca_root.pem -ovrg server
From the primary Data Processing Server, export the trusted certificates using the following command:
ovcert -exporttrusted -file <file with certificate>
Copy the exported trusted certificates to the new Data Processing Server and install the certificates on new Data Processing Server using the following commands:
ovcert -importtrusted -file <file with certificate>
ovcert -importtrusted -file <file with certificate> -ovrg server
On new Data Processing Servers, export certificates using the command:
ovcert -exporttrusted -file < file with certificate>
Copy this file to all your existing Data Processing Servers and import using the following commands:
ovcert -importtrusted -file <file with certificate>
ovcert -importtrusted -file <file with certificate> -ovrg server
If you have an integration with HPOM (Windows or Unix) follow the procedure "How to Establish a Trust Relationship between BSM and External Servers" in Solutions and Integrations for every Data Processing server.
Update trusted certificates using the ovcert -updatetrusted command on following servers:
All Gateway servers
All HP Diagnostics servers
All SiteScope servers
All Integration Adapter servers
Operations Management and other HP BTO Software applications use certificates that enable to clients and servers to identify themselves and communicate securely with each other. The data processing server can issue the required certificates to other servers in your environment, acting as a certificate authority.
If you have a one-machine deployment, the installation configures the certificates that you need. You do not need to configure gateway server certificates.
However, if you have a distributed deployment, after you install your BSM servers, you must make sure that every gateway server requests certificates from the data processing server. You must then make sure that the data processing server grants each certificate request.
Note: If BSM is required to issue certificates, for example, for an Integration Adapter, then the Gateway Servers must be configured to forward all incoming requests to the Data Processing Server. The Data Processing Server must be configured in the Operations Management Infrastructure Settings: Applications > Operations Management > Certificate Server Settings > Certificate Server IP Address.
To request certificates for gateway servers:
On each gateway server, open a command prompt, and then type the appropriate command depending on your operating system:
Windows: cd %TOPAZ_HOME%/bin
Linux: cd /opt/HP/BSM/bin
Start the following command:
setup-secure-communication
The command prompts you for the DNS name of the data processing server. Type this name, and then press Enter.
To grant certificate requests:
On the data processing server, open a command prompt, and then type the appropriate command depending on your operating system:
Windows: cd %TOPAZ_HOME%\bin
Linux: cd /opt/HP/BSM/bin
Start the following command:
setup-secure-communication
The command checks for pending certificate requests. For each pending certificate request, the command shows details of the request. For example:
INFO: Secure communication request from: gateway1.example.com
Press g to grant each request in turn. After you grant a certificate request, the command sends certificates to the gateway server, and then verifies that secure communication is possible.
If you have more than one Data Processing server, repeat the above procedures for each Data Processing server.
If you are planning to use Operations Manager i, perform the following steps:
Go to Admin > RTSM Administration > Modeling > CI Type Manager.
From the CI Types list select System Type Manager.
Select product_name_enum and click Edit.
Type lync_server and click Add.
Click OK.
You can see the installation log file by clicking the View log file link at the bottom of the installer window.
In a Windows environment, this log file, along with additional log files for separate installation packages, is located in the %temp%\..\HPOvInstaller\HPBsm_9.10 directory.
In a Linux environment, the logs files are located in the /tmp/HPOvInstaller/HPBsm_9.10 directory.
The installer log file name is in the following format:
HPBsm_<VERSION>_<DATE>_ HPOvInstallerLog.html or HPBsm_<VERSION>_<DATE>_ HPOvInstallerLog.txt (for example, HPBsm_9.10_2010.10.21_13_34_HPOvInstallerLog.html
).
Individual installation package log file names are in the following format:
Package_<PACKAGE_TYPE>_HPBSM_<PACKAGE_NAME>_install.log (for example, Package_msi_HPBSM_BPIPkg_install.log
).
Prerequisites
Before installing a BSM service pack, it is recommended that you back up all BSM databases.
Before installing a BSM service pack, make sure that BSM has been fully stopped on all machines and that there are no open connections (for example, from Windows Explorer) from any machines to the BSM root directory or any of its subdirectories.
Download and install the service pack from the SSO site
Go to the SSO site:
Select Application Performance Management (BAC) > 9.13 (or the most recent service pack) and click Search to locate the installation files.
Save the package locally and launch the relevant setup file to install the Service Pack.
Run the installation files on all BSM servers (Gateway and Data Processing).
Run the post-installation wizard. This wizard follows the service pack installation automatically.
Reapply manual changes
If you have made changes in the HP BSM root directory to files that are updated during patch installation, for example while performing hardening procedures on your system, you must reapply those changes after patch installation on all relevant BSM machines. You can access your modified files from the backup folder located at: <HP BSM root directory>\installation\<PATCH_NAME>\backup\<PATH_TO_FILE>.
Enable BSM
Enable BSM on all servers.
Clear the repository type cache
The service pack contains a fix for an issue with context menus on the dashboard. If you are upgrading to BSM 9.13, you must activate the fix by clearing the repository type cache as follows:
In a web browser, open http://<gateway server>:8080/jmx-console.
Under Topaz, click service=repositories_manager.
Start cleanRepositoryTypeDBAndCache() with sCustId=0 and repositoryType=contextMenu.
Alter the ALL_EVENTS table
The service pack contains a fix for an issue with events that have an automatic action exceeding 255 characters in length. If you are upgrading to BSM 9.13, you (or your database administrator) must manually alter the ALL_EVENTS table in the BSM event schema database. You must increase the size of the AA_CALL column from 255 to 4000 characters.
Use one of the following SQL expressions:
For Microsoft SQL Server:
alter table ALL_EVENTS alter column AA_CALL nvarchar(4000)
For Oracle:
alter table ALL_EVENTS modify (AA_CALL varchar2(4000 CHAR));
Delete temporary internet files
Delete the browser's temporary Internet files on each browser that accesses BSM.
For more details, see Upgrade Wizard Overview in the BSM 9.1x Upgrade Guide.
Disable BSM servers. Disable all BSM servers before running the upgrade wizard
Multiple servers. If you have more than one Data Processing or Gateway Server, run the upgrade wizards on one of each type of server only. For each additional Data Processing and Gateway Server, run the the Setup and Database Configuration Utility. For more details, see Setup and Database Configuration Utility Overview in the BSM 9.1x Upgrade Guide.
Disable IDM-SSO. In the upgrade wizard, after the data from the management database has been transferred to the new system, disable IDM-SSO on the new environment. To do so, log into the JMX console (http://<Gateway Server name>:8080/jmx-console) and search for the SSO service (service=SSO). Locate the setSingleSignOnMode operation and in the ParamValue box, type Lightweight. Click Invoke.
For details, see the BSM 9.1x Upgrade Guide.
If you had a hardened environment in BSM 9.0x, you need to perform the hardening procedure again after the BSM 9.1x upgrade. For details, see the HP Business Service Management Hardening Guide PDF.
After starting BSM, wait for the content pack upload to finish. Check the file <HPBSM Install Directory>/log/EJBContainer/opr-admin.log for the following entry:
"2011-05-06 10:21:19,431 [BackgroundThreadManager Thread (BG#1)] INFO ContentPackImportService.invoke(?) - OOTB Content Packs import finished in 283.542 seconds."
The OMi integration and topology synchonization files have changed with BSM 9.1x. It is therefore recommended that you merge your saved OMi customizations with the BSM 9.1x configuration files rather than replacing them.
On the BSM 9.1x Data Processing Server host system, make a backup copy of all the files in the following directory and subdirectories:
Windows: %TOPAZ_HOME%\conf\opr
Linux: /opt/HP/BSM/conf/opr
Merge the OMi integration and topology synchronization files that you saved from your BSM 9.0x installation in the step "Backing Up OMi Configuration Files" on page 222 with the BSM 9.1x configuration files.
The OMi integration and topology synchronization files reside in the following location on the BSM 9.1x Data Processing Server host system
Windows:
%TOPAZ_HOME%\conf\opr\integration
%TOPAZ_HOME%\conf\opr\topology-sync
Linux:
/opt/HP/BSM/conf/opr/integration
/opt/HP/BSM/conf/opr/topology-sync
Secure environments only: To re-enable the trust relationship between the Java Runtime Environment (JRE) and the LDAP server, you must import the LDAP trusted certificate to the JRE truststore. For details, see the HP Business Service Management Hardening Guide PDF.
Content is uploaded automatically on the first BSM startup using the create
mode. The create
mode ignores modified objects in the 9.1x content packs and uploads new and unchanged objects only. The HP-modified objects are described in the following file:
%TOPAZ_HOME%\conf\opr\content\migration\bdm_changes.xml
/opt/HP/BSM/conf/opr/content/migration/bdm_changes.xml
Note: New HI Values are not new objects, but a modification of the Health Indicator, which is a modification of the objects in your content pack.
If you have also modified the same objects, you can either redo your modifications manually after the migration has finished, or upload the upgrade content packs manually using the overwrite
mode. See Importing Modified Upgrade Content Packs below for details.
The upgrade content pack packages are located in the following directory:
<HPBSM Install Directory>/conf/opr/content/upgrade/<locale>
The available upgrade content pack packages are:
MM-INF_upgrade.xml — Content Pack for Infrastructure SPI
MM-JEE_upgrade.xml — Content Pack for J2EE SPI
MM-MSS_upgrade.xml — Content Pack for MS SQL SPI
MM-Ora_upgrade.xml — Content Pack for Oracle SPI
When you installed BSM 9.x, content that was imported using out-of-the-box content packs was categorized in the Service Health and SLM repositories as Custom or Predefined (Custom), rather than as Predefined.
After you install BSM 9.12, run the Repository Data Transfer tool to automatically re-label this out-of-the-box content in the repositories as Predefined, using the following steps:
Access the JMX console on the Gateway Server via http://<Gateway Server name>:8080/jmx-console, and enter the user name and password.
Click service=content-manager in the Topaz section.
Locate the invokeRepositoryTool() operation.
Click Invoke.
Note: If you have customized any repository items, they are not affected by this procedure.
Wait for the BSM services to be started again and then upload the content packs again. Execute the following command on the Gateway server:
<HPBSM Install Directory>/opr/bin/ContentManager -username admin -password admin -a -forceReload
If you have alerts configured with an Event Template, the ETI display label needs to be manually upgraded. To upgrade the display label, execute the following JMX command from the BSM 9.1x Data Processing Server:
BAC.Alerts.Upgrade service=change Eti name to ID update()