You can configure the Operations Agent to retrieve alerts and anomalies from OBA and forward them to OBM as events. You can also directly open OBA by using drill-down links in OBM's Event Details. This enables you to get the benefit from using both the capabilities of OBA to identify events by using analytic tools and the advanced event management capabilities of OBM.

If configured, the OBA alerts and anomalies are logged into one predefined log file located on the OBA application server. When the Operations Agent is configured on the OBA application server as an OBM monitored node, it enables the Logfile Entry policy in OBM. The OBA alerts and anomalies are then forwarded to OBM to be managed as events and anomalies. You can filter the log file entries by a set of rules in the policy.

For more information about policy management in OBM, see the OBM Administer node.

The following diagram shows the details of this integration:

When you install OBA, the Operations Agent is installed, but not configured. Configure the agent using the name of the OBM server as follows:

1. Connect the agent to OBM:

   1. Log on to the OBA application server.

   2. Navigate to the following location:

      /opt/OV/bin/OpC/install/

   3. Run the following script to configure the Operations Agent on the OBA application server:

      ./oasetup.sh -configure -management_server <OBM_Gateway_Server/LB>

      For the <OBM_Gateway_Server/LB> enter either the FQDN of your OBM gateway server, or the load balancer.

2. In the OBM user interface, open the Certificate Requests manager and accept the new certificate request:

   Administration > Setup and Maintenance > Certificate Requests

   For more information about granting certificate requests, see the OBM Administer node.

3. Optional. Check HTTPS communication in both directions:

   bbcutil -ping https://<FQDN>

   If the connection is successful, the command returns status=eServiceOK.

To configure the connection between OBM and OBA, do the following:

1. Import the content pack to OBM. OBA provides content packs that contain the management templates and aspects area ready to be used by OBM.

   1. Copy the content pack, as required for your OBM versions, to your OBM system:

      /opt/HP/opsa/content-packs/omi_content_pack/omi_<omi_version>_content_pack.zip

   2. In OBM, navigate to Administration > Setup and Maintenance > Content Packs.

   3. Click Import Content Pack Definitions and Content...

   4. Click Browse and locate the content pack you copied over earlier.

   5. Select Import.

2. Assign and deploy management templates to the OBA application server so that they can listen to the log files that report on the OBA alerts and anomalies.

   1. In OBM, navigate to Administration > Monitoring > Management Templates & Aspects.

   2. In the Configuration Folders pane, select the OpsAOBA Alerts Config Folder folder.

   3. In the Management Templates & Aspects pane, select OpsA AspectOBA Aspect and click Assign and Deploy Item... .

   4. In the Assign and Deploy wizard, select the OBA application server, and click Finish.

   5. Optional. In the Configure Options page, clear the Enable Assignment(s) check box if you do not want to enable the assignment immediately. You can enable the assignment later by using the Assignments & Tuning manager.

   6. Click Finish. OBM creates a deployment job, which deploys the aspect to the node.

   7. To verify the deployment, run the following command on the OBA application server:

      /opt/OV/bin/ovpolicy -l

      The result shows the deployed policies.

   8. In OBA, create alerts and anomalies. For more information, see the OBA Online Help.

To collect data for OBM, follow these steps on the OBR Administration Console:

1. In Data Source Selection Wizard, select Operations Bridge Manager (OBM).

2. In Operations Bridge Manager (OBM), select the version of the application deployed in your environment.

   For additional deployment configurations using OBM and BSM, see:

   • OBM Topology Source with Integrated BSM

     While you can configure BSM and OBM as standalone topology and data sources, you can also setup BSM to synchronize topology data with the OBM system.

     In this configuration, the OBM system provides topology data and fact data for Operations Events and KPI. The BSM system provides fact data from RUM and BPM that are directly configured with it. For enabling topology sync between BSM and OBM, see the respective documentation.

     Use the NPS RTSM ETL (NetworkPerf_ETL_PerfiSPI_RTSM) Content Pack component, if NNMi is integrated to OBM RTSM. Otherwise, use the non NPS RTSM ETL (NetworkPerf_ETL_PerfiSPI_NonRTSM) Content Pack component.

   • OBM Topology and Fact Source after BSM Upgrade

     While you can configure BSM and OBM as standalone topology and data sources, you can also upgrade your BSM system to an OBM system.

     In this configuration, the existing topology synchronized between BSM system and OBR system is removed and the OBM system provides topology data for all nodes and fact data for Operations Events and KPI. The BSM system provides fact data from RUM, BPM, and SiteScope that are directly configured with BSM.

     In this scenario, if you are already using NPS RTSM ETL (NetworkPerf_ETL_PerfiSPI_RTSM) when OBR was connected to BSM 9.2x then ensure that NNMi is integrated to OBM RTSM after BSM is upgraded to OBM.

     In this configuration, after the BSMsystem is upgraded to OBM, all topology and fact data is collected from OBM. To perform the upgrade, follow these steps:

     Note Perform the following steps only if the CIIDs for the CI(s) are unchanged after OBM upgrade.

     For more information on OBM upgrade, see Operations Bridge Manager Installation and Upgrade Guide.

     1. Stop collection service manually from the OBM systems.

        Wait until all data is loaded into OBR tables

     2. Complete the BSM to OBM upgrade process.

     3. From the OBR system Administration Console > Content Pack Deployment page:

        1. Uninstall the older ETL component of BPM (SynTrans_ETL_BPM) and install the newer (SynTrans_ETL_BPM_OBM10) ETL component.
        2. Uninstall the older ETL component of RUM (RealUsrTrans_ETL_RUM) and install the newer (RealUsrTrans_ETL_RUM_OBM10) ETL component.
        3. If SiteScope is integrated with OBM then install the SiteScope Direct API (SysPerf_ETL_SiS_API) ETL.

     4. To modify the RTSM topology source for OBM, follow these steps:

        1. Log on to Postgres database from OBR system using the command line interface:

           psql -U pmdb_admin -p 21425 -d dwabc

        2. Enter the password given at the time of management database creation during post-install configuration.

        3. Run the following commands:

           update dwabc.dict_cmdb_ds set hostname='<omi10hostname>';

           commit;

           where <omi10hostname>, is the hostname of your OBM.

     5. Log in to Administration Console > Data Source Configuration > Topology Source, and click Configure to modify the user name, password, and port as relevant for OBM.

     6. Add Operations database connection of OBM in Administration Console > Data Source Configuration > BSM/APM/OBM page. For more information, see Configuring the Management and Profile Database Data Source topic.

     7. Enable HI/KPI Data Collection and optionally SiteScope.

     8. Change the collection service to manual and start the collection service.

     Ensure to configure the topology source to OBM in OBR soon after the upgrade and before starting the collection service. Otherwise OBM will continue to point and collect the data from BSM system even after upgrading to OBM. During this period, if a new CI is discovered in BSM and this new CI is collected by OBR, it will end up being a duplicate in OBR when the topology is changed to OBM. If you come across such situation, then use DLC to clean up the duplicates.

3. (Optional). You may select SiteScope for system performance, Operations Agent and VMware vCenter data source for the virtual environment

4. Click Next

Based on the data sources selected in OBR Administration Console, the content types will be listed in the Data Source Selection Wizard > Content Type Selection page.

Follow these steps to select the content type according to your data sources:

1. In Data Source Selection Wizard > Content Type Selection > Operations Bridge Manager (OBM), select the required Content Type.

2. (Optional).

   1. If you select SiteScope for system performance, then SiteScope Metric Channel section appears.
   2. You must select either Profile DB or Direct API as the metric channel for SiteScope.

In the Content Pack Deployment page, components for Direct API are selected automatically if the option is selected in the Configuration Wizard.

If SiteScope is used to monitor system or virtual environment performance in OBM, the metric channel for SiteScope is through Direct API.

The OBR Administration Console Data Source Selection Wizard > OBM Management Packs/OM SPIs Selection tab displays the selection options only when Enterprise application performance is selected in Content Type Selection tab.

Perform the following steps for each of the deployment scenario:

1. In Data Source Selection Wizard > OBM Management Packs/OM SPIs Selection, select Management Pack and/or Smart Plug-In(SPi).

You must make sure that necessary Management Pack and/or Smart Plug-In (SPi) policies are installed.

2. Click Next.

1. To configure RTSM topology source, follow these steps on the OBR Administration Console > Data Source Configuration > Topology Source page.
2. Click Create New. The Connection Parameter appears.

3. In the Connection Parameter, type the following details:

   Field	Description
   Host name	IP address or FQDN of the APM or OBM server. If your OBM installation is distributed, type the name of the gateway server in the field. In a distributed OBM deployment with multiple gateway servers and load balancer configured, type the virtual IP address of the load balancer in this field.
   Port	Port number to query the RTSM web service. The default port number is 80. Set the port to 443 when RTSM is HTTPS enabled. If the port number has been changed, contact your OBM administrator for more information.
   User name	Name of the RTSM web service user. The default user name is admin. You can use the user with only RTSMOpenApiUser role assigned to it.
   Password	Password of the RTSM web service user.
   Collection station	If you installed collectors on remote systems, you can choose either the local collector or a remote collector. To configure a remote collector to collect data from this RTSM source, select one of the available remote systems in the drop down list. To use the collector that was installed by default on the OBR system, select local.

4. Click OK.
5. Click Save to save the information.

6. Click Test Connection. A success message appears in the information message panel.

   You can configure additional RTSM data sources by repeating the same steps.

   If the Test Connection fails, check the {PMDB_HOME}/log/remotepoller.log for more information.

7.  
8. Click Next. The Content Type Selection page appears.

Configure Data Collection When HTTPS is Enabled for RTSM

In case of remote collector, follow the same configuration steps on the system where remote collector is installed.

If RTSM is HTTPS enabled, follow these steps:

1. Set the port to 443 when RTSM is HTTPS enabled during topology source configuration.

2. Export the OBM webserver CA certificate. You can use the opr-cert-mgmt command-line interface to get certificates.

   For example: ./opr-cert-mgmt.sh ‑export "OBM Webserver CA Certificate" JKS "test" "/tmp/test.jks"

   If FIPS is enabled, export the certificate in PKCS12 format, else export in PEM format.

   • For OBM with multiple Gateways, export the OBM Webserver CA Certificate PEM from the Gateways entry listed in Default Virtual Gateway Server for Data Collectors URL of the OBM user interface Administration > Setup and Maintenance > Infrastructure Settings > Platform Administration - Host Configuration.

   • For OBM configured with a load balancer which performs SSL-offloading, or SSL-forwarding, export the load balancer certificate by running the following command:

     openssl s_client -servername <OBMGateway or LoadBalancer FQDN> -connect <OBMGateway or LoadBalancer FQDN>:443 </dev/null | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' >certificate.pem

   For more information about the options that OBM provides to get the certificates, see OBM Documentation.

3. Import the BSM/OBM root CA certificate into OBR server trust store. To import the CA certificates, follow these steps:

   1. On Windows

      keytool -import -trustcacerts -keystore <Path to store> -file "<filename with path>"

   2. On Linux

      keytool -import -trustcacerts -keystore <Path to store> -file "<filename with path>"

      where, <filename with path> is the location and file name of the OBM CA certificates.

      <Path to store> is the path to the trust store. You have to mention the same path in the collection service.

4. On the collector system chosen in above configuration, add the following fields in config.prp, located at %PMDB_HOME%\data (on Windows) $PMDB_HOME/data (on Linux):

   Field	Value
   ucmdb.protocol	https You must make sure to add ucmdb.protocol value in {PMDB_HOME}/data/config.prp file on the OBR server.
   shr.truststorepath	Full path to the keystore file. The path is in the format: C:\HPE-OBR\PMDB\keystore\SHR_CERT_HTTPS.jks Note: You may use the OBR keystore path OR you may create a new keystore.
   shr.truststorepassword	Password of the keystore
   shr.truststoretype	Type of the trust store - JKS or PKCS12

5. Follow these steps to add the entries in collection service scripts:

   1. On Windows

      1. Open the Services window, right-click the HPE_PMDB_Platform_Collection service, and then click Stop.

      2. Add -Djavax.net.ssl.trustStore=<Path to store> -Djavax.net.ssl.trustStorePassword=<password> to JVM_ARGS in %PMDB_HOME%\bin\CollectionServiceCreation.bat file.

         where, <Path to store> is the path to the trust store. Example: C:\OBR\PMDB\keystore\SHR_CERT_HTTPS.jks

         Important If OBR is upgraded from the 10.2x version to 10.3x version, with HTTPs configured RTSM, make sure to update the <Path to store> and <password> in the %PMDB_HOME%\bin\CollectionServiceCreation.bat file.

      3. Recreate the collection service, follow these steps:

         1. Open the command line console, run the following commands:

            CollectionServiceCreation.bat -remove <OV Install Directory> <Product Install Directory>

            CollectionServiceCreation.bat -install <OV Install Directory> <Product Install Directory>

            where, <OV Install Directory> is %OVInstallDir%

            <Product Install Directory> is %PMDB_HOME%\..

      4. Open the Services window, right-click the HPE_PMDB_Platform_Collection service, and then click Start.

   2. On Linux

      1. Go to /etc/init.d directory, and run the following command:

         On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Collection stop

         On RHEL 7.x/SLES 12.x/OEL: systemctl stop HPE_PMDB_Platform_Collection.service

      2. Add -Djavax.net.ssl.trustStore=<Path to store> -Djavax.net.ssl.trustStorePassword=<password> to JVM_ARGS in $PMDB_HOME/bin/hpbsm_pmdb_collector_start.sh files.

         where, <Path to store> is the path to the trust store.

         If OBR is upgraded from the 10.2x version to 10.3x version, with HTTPs configured RTSM, make sure to update the <Path to store> and <password> in the $PMDB_HOME/bin/hpbsm_pmdb_collector_start.sh file.

      3. Go to /etc/init.d directory, and run the following command:

         On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Collection start

         On RHEL 7.x/SLES 12.x/OEL: systemctl start HPE_PMDB_Platform_Collection.service

6. Stop and start the HPE_PMDB_Platform_Administration service as follows:

   On Windows:

   1. Open the Services window, right-click the HPE_PMDB_Platform_Administration service, and then click Stop.
   2. Wait for the service to stop.
   3. Open the Services window, right-click the HPE_PMDB_Platform_Administration service, and then click Start.

   On Linux:

   1. Go to the /etc/init.d directory, and run the following command:

      On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Administration stop

      On RHEL 7.x/SLES 12.x/OEL: systemctl stop HPE_PMDB_Platform_Administration.service

   2. Wait for the service to stop and then run the following command:

      On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Administration start

      On RHEL 7.x/SLES 12.x/OEL: systemctl start HPE_PMDB_Platform_Administration.service

For installing the required Content Packs, OBR provides the Content Pack Deployment page through the Administration Console. This web-based interface simplifies the process of installation by organizing the Content Packs based on the domain, the data source applications from where you want to collect data, and the specific Content Pack components you want to install to collect the data.

Before you begin installing Content Packs, make sure that:

1. OBR Post-installation is complete.
2. Data source selections are complete
3. In a distributed scenario, if OBR is installed on Windows, irrespective of BO installed on Windows or Linux or on the same system or different system, you must configure DSN on OBR system (installed on Windows) to connect to Vertica database. If OBR is installed on Linux then installer automatically handles the DSN configuration and connection to Vertica database. To configure DSN, see Configuring DSN on Windows for Vertica Database topic in OBR Documentation. To install Content Packs on Windows Operating System, make sure that UAC is disabled on the system.

Use the Content Pack Deployment page in the Administration Console to install the Content Pack components.

The Content Packs already selected in the Content Pack Deployment page may be mutually exclusive. For information on Content Packs that are mutually exclusive, see Listing of ETLs topic in OBR Documentation.

To install the Content Packs, follow these steps:

1. To log on to Administration Console, follow these steps:

   1. Launch the following URL:

      https://<OBR_Server_FQDN>:21412/OBRApp 

      where, <OBR_Server_FQDN> is the fully qualified domain name of the system where OBR is installed.

   2. Type administrator in the Login Name field and password in the Password field. Click Log In to continue. The Home page appears.

      If you use any other user account to access the Administration Console, make sure that the user account has administrator privileges.

2. On the left pane, click Content Pack Deployment. The Content Pack Deployment page appears.

   The Content Pack Deployment displays the Content Pack components that can be installed in the supported deployment scenario. You can modify the selection by clearing the selected content, the data source application, or the Content Pack components from the list.

   While you clear the components of the selected Content Pack that you do not want to install, make sure that you clear the dependent components of the Content Pack.

   The following table lists the content that is specific to each deployment scenario:

   List of Content Packs

   Content	OBM
   Default	ü
   Cross-Domain Operations Events	ü
   Health and Key Performance Indicators	ü
   IBM WebSphere Application Server	ü
   Microsoft Active Directory	ü
   Microsoft Exchange Server	ü
   Microsoft SQL Server	ü
   MSAppCore	ü
   Network Performance*	ü
   Network Component Health	ü
   Network Interface Health	ü
   Operations Events	ü
   Oracle	ü
   Oracle WebLogic Server	ü
   Real User Transaction Monitoring	ü
   Synthetic Transaction Monitoring	ü
   System Performance	ü
   Virtual Environment Performance	ü

   To generate reports on data from EVENT database, make the following selections:

   • CrossOprEvent_ETL_OBM

   • CrossOprEvent_ETL_OBM10x

   • CrossOprEvent_Domain_Reports

   • CrossOprEvent_ETL_OBM10x_Extended

   • CrossOprEvent_ETL_OBM_Extended

   • CrossOprEvent_Domain_Reports_Extended

   You must upgrade the CrossOprEvent_Domain_Reports_Extended core domain component to the latest version and then install the CrossOprEvent_ETL_OBM10x_Extended component. Also, make sure to uninstall the CrossOprEvent_ETL_OBM10_Extended component.

   To generate reports on data from OBM for HI and KPIs, make the following selections:

   • HIKPI_ETL_ServiceHealth (RTSM topology)
   • HIKPI_ETL_ServiceHealth_OBM10 (OBM topology)
   • HIKPI_Domain
   • HIKPI_Reports_ServiceHealth

   Install the following dependent content packs (and their components) along with this content pack for it to function:

   • Core

     • Core_Domain

   The dependent domain content pack get selected automatically, you have to select only the ETLs based on the topology source.

   The Content Pack components for RTSM and OBM topology source are mutually exclusive. Ensure that only one of them is selected.

3. Click Install / Upgrade to install the Content Packs.

   An Installation Started status appears in the Status column for Content Pack that is currently being installed. The Content Pack Deployment page automatically refreshes itself to display the updated status. Once the installation completes, an Installation Successful status appears. If the installation fails, an Installation Failed status appears.

   The HPE_PMDB_Platform_Orchestration and the Timer service will be stopped automatically during Content Pack(s) install/uninstall operation and will be started once operation is complete.

   During install/uninstall process, Content Pack Deployment page does not allow you to interrupt the process. Instead, you must wait till the current process is complete before you can perform any other operations on the Content Pack Deployment page.

After installing Health and Key Performance Indicators Content Pack, you must configure OBR to collect required data from various data collectors. The data collectors work internally within the OBR infrastructure to collect the data. Therefore, you cannot directly interface with these collectors. Instead, you can specify the data sources from where the collectors can collect the data through the Administration Console.

You can configure OBR to collect data from the following Business Service Management data repositories:

• Management database: The Management database stores system-wide and management-related meta data for the Business Service Management environment.

• Profile database: The Profile database stores raw and aggregated measurement data obtained from the Business Service Management data collectors. The Profile database also stores measurements collected through OBM, BPM, RUM, and Service Health.

Make sure to assign the same OBR collector to each instance of the Operations/Profile database and Management database connections.

To configure a new Management Database, follow these steps:

1. In the OBRAdministration Console, click Data Source Configuration > BSM/APM/OBM > Management Database.

   To discover Profile or Operations database in OBR system, you must copy the seed.properties and encryption.properties files from OBM server to OBR system. For more information, see Configure Multiple Profile Database topic.

2. Click Create New. The Connection Parameters dialog box appears.

3. Based on the topology source, select Data Source as OBM.

4. Enter appropriate values in the fields of Connection Parameters dialog box:

   For Oracle Database:

   Field	Description
   OBM	Select the data source from the options
   Database in Oracle RAC	Enable this option to select the Database in Oracle RAC.
   Enable TLS	Enable JDBC connection over TLS. This option is displayed when Database type selected is ORACLE.
   Truststore Path	Full path to the truststore path. This option is displayed when Enable TLS is selected. It is recommended to have a common trust store file.
   Truststore Password	The password to access the truststore. This option is displayed when Enable TLS is selected.
   Host name	IP address or FQDN of the Management Database server. Not displayed when Database in Oracle RAC is selected.
   Port	Port number to query the Management Database server. Not displayed when Database in Oracle RAC is selected.
   Service name	Name of the service. This option appears only if Database in Oracle RAC is selected.
   ORA file name	The ORA file that contains connection information to the Oracle Real Application Cluster. This option appears only if Database in Oracle RAC is selected.
   Database type	The type of database engine that is used to create the Management Database - Oracle.
   Database instance	System Identifier (SID) of the Management Database instance. Not displayed when Database in Oracle RAC is selected. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   User name	Name of the Management Database user, which was specified in the BSM Configuration Wizard when setting up the Management Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Management Database user. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	If you installed collectors on remote systems, you can choose either the local collector or a remote collector. To configure a remote collector with this topology source, select one of the available remote systems in the drop down list. To use the collector that was installed by default on the OBR system, select local.

   For MS SQL Database:

   Field	Description
   OBM	Select the data source from the options
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Management Database server.
   Port	Port number to query the Management Database server.
   Database type	The type of database engine that is used to create the Management Database - MSSQL.
   Database instance	System Identifier (SID) of the Management Database instance. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   Windows Authentication	If you have selected MSSQL as the database type, you have the option to enable Windows authentication for MSSQL, that is, the user can use the same credentials to access SQL Server as that of the Windows system hosting the database. This option is not supported if OBR server is installed on Linux Operating System.
   Database name	Name of the database. This field appears only if MSSQL is selected as the database type.
   User name	Name of the Management Database user, which was specified in the BSM Configuration Wizard when setting up the Management Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Management Database user. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	If you installed collectors on remote systems, you can choose either the local collector or a remote collector. To configure a remote collector with this topology source, select one of the available remote systems in the drop down list. To use the collector that was installed by default on the OBR system, select local.

   For PostgreSQL Database:

   Field	Description
   OBM	Select the data source from the options
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Management Database server.
   Port	Port number to query the Management Database server.
   Database type	The type of database engine that is used to create the Management Database - PostgreSQL.
   Database name	Name of the database.
   User name	Name of the Management Database user, which was specified in the BSM Configuration Wizard when setting up the Management Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Management Database user. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system. If you installed collectors on remote systems, you can choose either the local collector or a remote collector. To configure a remote collector with this topology source, select one of the available remote systems in the drop down list. To use the collector that was installed by default on the OBR system, select local.

5. Click OK.

6. Click Test Connection to test the connection.

7. Click Discover Database to automatically discover corresponding Profile database(s).

   If management database and profile database are on the same system as the BSM system (local database), clicking Discover Database will automatically discover the corresponding Profile database. If the databases are on different systems (remote database), you have to manually configure the Profile database using the Profile Database tab. You have to manually provide configuration details with user name and password for each profile database.

   After you configure management database with Database in Oracle RAC option selected and the Test Connection is successful, clicking Discovery Database does not automatically discover the corresponding Profile database(s). You have to manually configure the profile database using the Profile Database tab. You have to manually provide configuration details with user name and password for each profile database.

8. Click Save to save the changes. A Saved Successfully message appears in the Information message pane.

To configure a new Profile database, follow these steps:

1. In the Administration Console, click Data Source Configuration > BSM/APM/OBM > Profile Database.

2. Click Create New. The Connection Parameters dialog box appears.

3. Type the following values in the Connection Parameters dialog box:

   For Oracle database:

   Field	Description
   Database in Oracle RAC	Enable this option to select the Database in Oracle RAC.
   Enable TLS	Enable JDBC connection over TLS.
   Truststore file	Full path to the truststore path. This option is displayed when Enable TLS is selected. It is recommended to have a common trust store file.
   Truststore Password	The password to access the truststore. This option is displayed when Enable TLS is selected.
   Host name	IP address or FQDN of the Profile Database server. Not displayed when Database in Oracle RAC is selected.
   Port	Port number to query the Profile Database server. Not displayed when Database in Oracle RAC is selected.
   Service name	Name of the service. This option appears only if Database in Oracle RAC is selected.
   ORA file name	The ORA file that contains connection information to the Oracle Real Application Cluster. This option appears only if Database in Oracle RAC is selected.
   Database type	The type of database engine that is used to create the Profile Database - Oracle.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Domains	Select the domains for which you want to enable data collection. You must select the domains from which you want to enable data collection. If you have skipped topology configuration during post-install configuration and installed the content packs, you must return here to select from among the following domains to enable data collection. Operations Manager OBM RUM BPM Service Health
   Database instance	System Identifier (SID) of the Profile Database instance. Not displayed when Database in Oracle RAC is selected. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   User name	Name of the Profile Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Profile Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

   For MS SQL Database:

   Field	Description
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Profile Database server.
   Port	Port number to query the Profile Database server.
   Database type	The type of database engine that is used to create the Profile Database - MSSQL.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Domains	Select the domains for which you want to enable data collection. You must select the domains from which you want to enable data collection. If you have skipped topology configuration during post-install configuration and installed the content packs, you must return here to select from among the following domains to enable data collection. Operations Manager OBM RUM BPM Service Health
   Database instance	System Identifier (SID) of the Profile Database instance. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   Windows Authentication	If you have selected MSSQL as the database type, you have the option to enable Windows authentication for MSSQL, that is, the user can use the same credentials to access SQL Server as that of the Windows system hosting the database. This option is not supported if OBR server is installed on Linux Operating System.
   Database name	Name of the database. This field appears only if MSSQL is selected as the database type.
   User name	Name of the Profile Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Profile Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

4. Click OK.

5. Click Test Connection to test the connection.
6. Click Save to save the changes made on this page. A Saved Successfully message appears in the Information message pane.

After you save the newly created Management database connection, OBR (local collector or remote collector) retrieves the Profile database information from the Management database data source and lists all the existing Profile database data sources under the Profile Database section of the page.

Data collection for the Profile database data source is enabled by default. In addition, the collection frequency is scheduled for every one hour.

In case of a Remote Collector, the collection station has to be selected from the Database type drop down box provided in the Profile Database section of the page.

Enable KPI Data Collection for Service Health CIs

KPIs are high-level indicators of a CI’s performance and availability. The KPI data pertaining to certain logical Service Health CIs, such as Business Service, Business Application, Business Process, and Host, are logged by default in the Profile database. OBR collects this data from the database for reporting.

However, the KPI data for other CI types are not automatically logged in the Profile database. To enable the logging of the KPI data for these CI types, you must configure the CIs in the BSM. For more information, see the Persistent Data and Historical Data section of the Business Service Management - Using Service Health guide. This document is available for the product, Application Performance Management (BAC), at the Software URL.

After installing OBM Event Content Packs, you must configure OBR to collect required data from various data collectors. The data collectors work internally within the OBR infrastructure to collect the data. Therefore, you cannot directly interface with these collectors. Instead, you can specify the data sources from where the collectors can collect the data through the Administration Console.

In OBM deployment scenario, SiteScope and Operations Agent monitors the physical and virtual nodes. When you configure data source in this scenario, choose Operations Agent and/or SiteScope as the data source.

If you install the OBM Content Pack, you must configure the OBM database connection for data collection. You can configure OBR to collect data from the following OBM data repositories:

• Events database: The events database stores data obtained from OBM (9.x versions) data source.

• Operations database: The operations database stores data obtained from OBM 10 (and later versions OBM) data source.

Before you create a new OBM data source connection, make sure that a data source connection for the Management database exists on the Management DB / Profile DB page, see Configuring the Management and Profile Database Data Source topic. This data connection is required to retrieve Assigned User/Group information for OBM, which is stored in the Management database.

If you have one or more OBM setups in your environment, you must configure the OBM data source that belongs to the BSM RTSM that was configured as the topology source.

To configure the OBM data source connections, follow these steps:

1. In the Administration Console, click Data Source Configuration > BSM/APM/OBM > Operations Database.

2. Click Create New to create a new OBM data source connection. The Connection Parameters dialog box appears.

3. Specify or type the following values in the Connection Parameters dialog box:

   For Oracle database:

   Field	Description
   Event Operations	Select your data source.
   Database in Oracle RAC	Enable this option to select the Database in Oracle RAC.
   Enable TLS	Enable JDBC connection over TLS. This option is displayed when Database type selected is ORACLE.
   Truststore file	Full path to the truststore path. This option is displayed when Enable TLS is selected.
   Truststore Password	The password to access the truststore. This option is displayed when Enable TLS is selected.
   Service name	Name of the service. This option appears only if Database in Oracle RAC is selected.
   ORA file name	The ORA file that contains connection information to the Oracle Real Application Cluster. This option appears only if Database in Oracle RAC is selected.
   Host name	IP address or FQDN of the Management Database server. Not displayed when Database in Oracle RAC is selected.
   Port	Port number to query the Management Database server. Not displayed when Database in Oracle RAC is selected.
   Database type	The type of database engine that is used to create the Management Database - Oracle.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Database instance	System Identifier (SID) of the Management Database instance. Not displayed when Database in Oracle RAC is selected. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   User name	Name of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

   For MS SQL database:

   Field	Description
   Event Operations	Select your data source.
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Management Database server.
   Port	Port number to query the Management Database server.
   Database type	The type of database engine that is used to create the Management Database - MSSQL.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Database instance	System Identifier (SID) of the Management Database instance. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   Windows Authentication	If you have selected MSSQL as the database type, you have the option to enable Windows authentication for MSSQL, that is, the user can use the same credentials to access SQL Server as that of the Windows system hosting the database. This option is not supported if OBR server is installed on Linux Operating System.
   Database name	Name of the database. This field appears only if MSSQL is selected as the database type.
   User name	Name of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

   For PostgreSQL database:

   Field	Description
   Event Operations	Select your data source.
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Management Database server.
   Port	Port number to query the Management Database server.
   Database type	The type of database engine that is used to create the Management Database . For Operations database - PostgreSQL.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Database name	Name of the database. This field appears only if MSSQL is selected as the database type.
   User name	Name of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

4. Click OK.

   You can create only one OBM data source connection. After the connection is created, the Create New button is disabled by default. Make sure that you type in the correct values.

5. Click Test Connection to test the connection.
6. Click Save to save the changes. A Saved Successfully message appears in the Information message panel.
7. To change the OBM data collection schedule for one or more hosts, in the Schedule Frequency column, specify a collection time between 1 and 24 hours in the Hrs box.
8. Click Save to save the changes. A Saved Successfully message appears in the Information message panel.

To collect data for OBM, follow these steps on the OBR Administration Console:

1. In Data Source Selection, select Operations Bridge Manager (OBM).

2. In Operations Bridge Manager (OBM), select the version of the application deployed in your environment.

   For additional deployment configurations using APM, see:

   • OBM Topology Source with Integrated APM

     In this configuration, the OBM system provides topology data and fact data for Operations Events and KPI. The APM system provides fact data from RUM, BPM, SiteScope and Service Health that are directly configured with it. For enabling topology sync between APM and OBM, see the respective documentation.

3. (Optional). You may select SiteScope for system performance, Operations Agent and VMware vCenter data source for the virtual environment

4. Click Next

Based on the data sources selected in OBR Administration Console, the content types will be listed in the Data Source Selection Wizard > Content Type Selection page.

Follow these steps to select the content type according to your data sources:

1. In Data Source Selection Wizard > Content Type Selection > Operations Bridge Manager (OBM), select the required Content Type.

2. (Optional).

   1. If you select SiteScope for system performance, then SiteScope Metric Channel section appears.
   2. You must select either Profile DB or Direct API as the metric channel for SiteScope.

In the Content Pack Deployment page, components for Direct API are selected automatically if the option is selected in the Configuration Wizard.

If SiteScope is used to monitor system or virtual environment performance in OBM, the metric channel for SiteScope is through Direct API.

The OBR Administration Console Data Source Selection Wizard > OBM Management Packs/OM SPIs Selection tab displays the selection options only when Enterprise application performance is selected in Content Type Selection tab.

Perform the following steps for each of the deployment scenario:

1. In Data Source Selection Wizard > OBM Management Packs/OM SPIs Selection, select Management Pack and/or Smart Plug-In(SPi).

You must make sure that necessary Management Pack and/or Smart Plug-In (SPi) policies are installed.

2. Click Next.

1. To configure RTSM topology source, follow these steps on the OBR Administration Console > Data Source Configuration > Topology Source page.
2. Click Create New. The Connection Parameter appears.

3. In the Connection Parameter, type the following details:

   Field	Description
   Host name	IP address or FQDN of the APM or OBM server. If your APM installation is distributed, type the name of the gateway server in the field. In a distributed APM deployment with multiple gateway servers and load balancer configured, type the virtual IP address of the load balancer in this field.
   Port	Port number to query the RTSM web service. The default port number is 80. Set the port to 443 when RTSM is HTTPS enabled. If the port number has been changed, contact your APM administrator for more information.
   User name	Name of the RTSM web service user. The default user name is admin. You can use the user with only RTSMOpenApiUser role assigned to it.
   Password	Password of the RTSM web service user.
   Collection station	If you installed collectors on remote systems, you can choose either the local collector or a remote collector. To configure a remote collector to collect data from this RTSM source, select one of the available remote systems in the drop down list. To use the collector that was installed by default on the OBR system, select local.

4. Click OK.
5. Click Save to save the information.

6. Click Test Connection. A success message appears in the information message panel.

   You can configure additional RTSM data sources by repeating the same steps.

   If the Test Connection fails, check the {PMDB_HOME}/log/remotepoller.log for more information.

7. Click Next. The Content Type Selection page appears.

Configure Data Collection When HTTPS is Enabled for RTSM

In case of remote collector, follow the same configuration steps on the system where remote collector is installed.

If RTSM is HTTPS enabled, follow these steps:

1. Set the port to 443 when RTSM is HTTPS enabled during topology source configuration.

2. Export the OBM webserver CA certificate. You can use the opr-cert-mgmt command-line interface to get certificates.

   For example: ./opr-cert-mgmt.sh ‑export "OBM Webserver CA Certificate" JKS "test" "/tmp/test.jks"

   If FIPS is enabled, export the certificate in PKCS12 format, else export in PEM format.

   • For OBM with multiple Gateways, export the OBM Webserver CA Certificate PEM from the Gateways entry listed in Default Virtual Gateway Server for Data Collectors URL of the OBM user interface Administration > Setup and Maintenance > Infrastructure Settings > Platform Administration - Host Configuration.

   • For OBM configured with a load balancer which performs SSL-offloading, or SSL-forwarding, export the load balancer certificate by running the following command:

     openssl s_client -servername <OBMGateway or LoadBalancer FQDN> -connect <OBMGateway or LoadBalancer FQDN>:443 </dev/null | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' >certificate.pem

   For more information about the options that OBM provides to get the certificates, see OBM Documentation.

3. Import the BSM/OBM root CA certificate into OBR server trust store. To import the CA certificates, follow these steps:

   1. On Windows

      keytool -import -trustcacerts -keystore <Path to store> -file "<filename with path>"

   2. On Linux

      keytool -import -trustcacerts -keystore <Path to store> -file "<filename with path>"

      where, <filename with path> is the location and file name of the OBM CA certificates.

      <Path to store> is the path to the trust store. You have to mention the same path in the collection service.

4. On the collector system chosen in above configuration, add the following fields in config.prp, located at %PMDB_HOME%\data (on Windows) $PMDB_HOME/data (on Linux):

   Field	Value
   ucmdb.protocol	https You must make sure to add ucmdb.protocol value in {PMDB_HOME}/data/config.prp file on the OBR server.
   shr.truststorepath	Full path to the keystore file. The path is in the format: C:\HPE-OBR\PMDB\keystore\SHR_CERT_HTTPS.jks Note: You may use the OBR keystore path OR you may create a new keystore.
   shr.truststorepassword	Password of the keystore
   shr.truststoretype	Type of the trust store - JKS or PKCS12

5. Follow these steps to add the entries in collection service scripts:

   1. On Windows

      1. Open the Services window, right-click the HPE_PMDB_Platform_Collection service, and then click Stop.

      2. Add -Djavax.net.ssl.trustStore=<Path to store> -Djavax.net.ssl.trustStorePassword=<password> to JVM_ARGS in %PMDB_HOME%\bin\CollectionServiceCreation.bat file.

         where, <Path to store> is the path to the trust store. Example: C:\OBR\PMDB\keystore\SHR_CERT_HTTPS.jks

         Important If OBR is upgraded from the 10.2x version to 10.3x version, with HTTPs configured RTSM, make sure to update the <Path to store> and <password> in the %PMDB_HOME%\bin\CollectionServiceCreation.bat file.

      3. Recreate the collection service, follow these steps:

         1. Open the command line console, run the following commands:

            CollectionServiceCreation.bat -remove <OV Install Directory> <Product Install Directory>

            CollectionServiceCreation.bat -install <OV Install Directory> <Product Install Directory>

            where, <OV Install Directory> is %OVInstallDir%

            <Product Install Directory> is %PMDB_HOME%\..

      4. Open the Services window, right-click the HPE_PMDB_Platform_Collection service, and then click Start.

   2. On Linux

      1. Go to /etc/init.d directory, and run the following command:

         On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Collection stop

         On RHEL 7.x/SLES 12.x/OEL: systemctl stop HPE_PMDB_Platform_Collection.service

      2. Add -Djavax.net.ssl.trustStore=<Path to store> -Djavax.net.ssl.trustStorePassword=<password> to JVM_ARGS in $PMDB_HOME/bin/hpbsm_pmdb_collector_start.sh files.

         where, <Path to store> is the path to the trust store.

         If OBR is upgraded from the 10.2x version to 10.3x version, with HTTPs configured RTSM, make sure to update the <Path to store> and <password> in the $PMDB_HOME/bin/hpbsm_pmdb_collector_start.sh file.

      3. Go to /etc/init.d directory, and run the following command:

         On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Collection start

         On RHEL 7.x/SLES 12.x/OEL: systemctl start HPE_PMDB_Platform_Collection.service

6. Stop and start the HPE_PMDB_Platform_Administration service as follows:

   On Windows:

   1. Open the Services window, right-click the HPE_PMDB_Platform_Administration service, and then click Stop.
   2. Wait for the service to stop.
   3. Open the Services window, right-click the HPE_PMDB_Platform_Administration service, and then click Start.

   On Linux:

   1. Go to the /etc/init.d directory, and run the following command:

      On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Administration stop

      On RHEL 7.x/SLES 12.x/OEL: systemctl stop HPE_PMDB_Platform_Administration.service

   2. Wait for the service to stop and then run the following command:

      On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Administration start

      On RHEL 7.x/SLES 12.x/OEL: systemctl start HPE_PMDB_Platform_Administration.service

For installing the required Content Packs, OBR provides the Content Pack Deployment page through the Administration Console. This web-based interface simplifies the process of installation by organizing the Content Packs based on the domain, the data source applications from where you want to collect data, and the specific Content Pack components you want to install to collect the data.

Before you begin installing Content Packs, make sure that:

1. Post-installation is complete
2. Data source selections are complete
3. In a distributed scenario, if OBR is installed on Windows, irrespective of BO installed on Windows or Linux or on the same system or different system, you must configure DSN on OBR system (installed on Windows) to connect to Vertica database. If OBR is installed on Linux then installer automatically handles the DSN configuration and connection to Vertica database. To configure DSN, see Configuring DSN on Windows for Vertica Database topic in OBR Documentation. To install Content Packs on Windows Operating System, make sure that UAC is disabled on the system.

Use the Content Pack Deployment page in the Administration Console to install the Content Pack components.

The Content Packs already selected in the Content Pack Deployment page may be mutually exclusive. For information on Content Packs that are mutually exclusive, see Listing of ETLs topic in OBR Documentation.

To install the Content Packs, follow these steps:

1. To log on to Administration Console, follow these steps:

   1. Launch the following URL:

      https://<OBR_Server_FQDN>:21412/OBRApp 

      where, <OBR_Server_FQDN> is the fully qualified domain name of the system where OBR is installed.

   2. Type administrator in the Login Name field and password in the Password field. Click Log In to continue. The Home page appears.

      If you use any other user account to access the Administration Console, make sure that the user account has administrator privileges.

2. On the left pane, click Content Pack Deployment. The Content Pack Deployment page appears.

   The Content Pack Deployment displays the Content Pack components that can be installed in the supported deployment scenario. You can modify the selection by clearing the selected content, the data source application, or the Content Pack components from the list.

   While you clear the components of the selected Content Pack that you do not want to install, make sure that you clear the dependent components of the Content Pack.

   The following table lists the content that is specific to each deployment scenario:

   List of Content Packs

   Content	OBM
   Default	ü
   Cross-Domain Operations Events	ü
   Health and Key Performance Indicators	ü
   IBM WebSphere Application Server	ü
   Microsoft Active Directory	ü
   Microsoft Exchange Server	ü
   Microsoft SQL Server	ü
   MSAppCore	ü
   Network Performance*	ü
   Network Component Health	ü
   Network Interface Health	ü
   Operations Events	ü
   Oracle	ü
   Oracle WebLogic Server	ü
   Real User Transaction Monitoring	ü
   Synthetic Transaction Monitoring	ü
   System Performance	ü
   Virtual Environment Performance	ü

   To generate reports on data from EVENT database, make the following selections:

   • CrossOprEvent_ETL_OBM

   • CrossOprEvent_ETL_OBM10x

   • CrossOprEvent_Domain_Reports

   • CrossOprEvent_ETL_OBM10x_Extended

   • CrossOprEvent_ETL_OBM_Extended

   • CrossOprEvent_Domain_Reports_Extended

   You must upgrade the CrossOprEvent_Domain_Reports_Extended core domain component to the latest version and then install the CrossOprEvent_ETL_OBM10x_Extended component. Also, make sure to uninstall the CrossOprEvent_ETL_OBM10_Extended component.

   To generate reports on data from OBM for HI and KPIs, make the following selections:

   • HIKPI_ETL_ServiceHealth (RTSM topology)
   • HIKPI_ETL_ServiceHealth_OBM10 (OBM topology)
   • HIKPI_Domain
   • HIKPI_Reports_ServiceHealth

   Install the following dependent content packs (and their components) along with this content pack for it to function:

   • Core

     • Core_Domain

   The dependent domain content pack get selected automatically, you have to select only the ETLs based on the topology source.

   The Content Pack components for RTSM and OBM topology source are mutually exclusive. Ensure that only one of them is selected.

3. Click Install / Upgrade to install the Content Packs.

   An Installation Started status appears in the Status column for Content Pack that is currently being installed. The Content Pack Deployment page automatically refreshes itself to display the updated status. Once the installation completes, an Installation Successful status appears. If the installation fails, an Installation Failed status appears.

   The HPE_PMDB_Platform_Orchestration and the Timer service will be stopped automatically during Content Pack(s) install/uninstall operation and will be started once operation is complete.

   During install/uninstall process, Content Pack Deployment page does not allow you to interrupt the process. Instead, you must wait till the current process is complete before you can perform any other operations on the Content Pack Deployment page.

After installing Health and Key Performance Indicators Content Pack, you must configure OBR to collect required data from various data collectors. The data collectors work internally within the OBR infrastructure to collect the data. Therefore, you cannot directly interface with these collectors. Instead, you can specify the data sources from where the collectors can collect the data through the Administration Console.

You can configure OBR to collect data from the following Business Service Management data repositories:

• Management database: The Management database stores system-wide and management-related meta data for the Business Service Management environment.

• Profile database: The Profile database stores raw and aggregated measurement data obtained from the Business Service Management data collectors. The Profile database also stores measurements collected through OBM, BPM, RUM, and Service Health.

Make sure to assign the same OBR collector to each instance of the Operations/Profile database and Management database connections.

To configure a new Management Database, follow these steps:

1. In the OBRAdministration Console, click Data Source Configuration > BSM/APM/OBM > Management Database.

   To discover Profile or Operations database in OBR system, you must copy the seed.properties and encryption.properties files from APM/OBM server to OBR system. For more information, see Configure Multiple Profile Database topic.

2. Click Create New. The Connection Parameters dialog box appears.

3. Based on the topology source, select Data Source as BSM/APM or OBM.

4. Enter appropriate values in the fields of Connection Parameters dialog box:

   For Oracle Database:

   Field	Description
   BSM/APM OBM	Select the data source from the options
   Database in Oracle RAC	Enable this option to select the Database in Oracle RAC.
   Enable TLS	Enable JDBC connection over TLS. This option is displayed when Database type selected is ORACLE.
   Truststore Path	Full path to the truststore path. This option is displayed when Enable TLS is selected. It is recommended to have a common trust store file.
   Truststore Password	The password to access the truststore. This option is displayed when Enable TLS is selected.
   Host name	IP address or FQDN of the Management Database server. Not displayed when Database in Oracle RAC is selected.
   Port	Port number to query the Management Database server. Not displayed when Database in Oracle RAC is selected.
   Service name	Name of the service. This option appears only if Database in Oracle RAC is selected.
   ORA file name	The ORA file that contains connection information to the Oracle Real Application Cluster. This option appears only if Database in Oracle RAC is selected.
   Database type	The type of database engine that is used to create the Management Database - Oracle.
   Database instance	System Identifier (SID) of the Management Database instance. Not displayed when Database in Oracle RAC is selected. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   User name	Name of the Management Database user, which was specified in the BSM Configuration Wizard when setting up the Management Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Management Database user. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	If you installed collectors on remote systems, you can choose either the local collector or a remote collector. To configure a remote collector with this topology source, select one of the available remote systems in the drop down list. To use the collector that was installed by default on the OBR system, select local.

   For MS SQL Database:

   Field	Description
   BSM/APM OBM	Select the data source from the options
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Management Database server.
   Port	Port number to query the Management Database server.
   Database type	The type of database engine that is used to create the Management Database - MSSQL.
   Database instance	System Identifier (SID) of the Management Database instance. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   Windows Authentication	If you have selected MSSQL as the database type, you have the option to enable Windows authentication for MSSQL, that is, the user can use the same credentials to access SQL Server as that of the Windows system hosting the database. This option is not supported if OBR server is installed on Linux Operating System.
   Database name	Name of the database. This field appears only if MSSQL is selected as the database type.
   User name	Name of the Management Database user, which was specified in the BSM Configuration Wizard when setting up the Management Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Management Database user. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	If you installed collectors on remote systems, you can choose either the local collector or a remote collector. To configure a remote collector with this topology source, select one of the available remote systems in the drop down list. To use the collector that was installed by default on the OBR system, select local.

   For PostgreSQL Database:

   Field	Description
   BSM/APM OBM	Select the data source from the options
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Management Database server.
   Port	Port number to query the Management Database server.
   Database type	The type of database engine that is used to create the Management Database - PostgreSQL.
   Database name	Name of the database.
   User name	Name of the Management Database user, which was specified in the BSM Configuration Wizard when setting up the Management Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Management Database user. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system. If you installed collectors on remote systems, you can choose either the local collector or a remote collector. To configure a remote collector with this topology source, select one of the available remote systems in the drop down list. To use the collector that was installed by default on the OBR system, select local.

5. Click OK.

6. Click Test Connection to test the connection.

7. Click Discover Database to automatically discover corresponding Profile database(s).

   If management database and profile database are on the same system as the BSM system (local database), clicking Discover Database will automatically discover the corresponding Profile database. If the databases are on different systems (remote database), you have to manually configure the Profile database using the Profile Database tab. You have to manually provide configuration details with user name and password for each profile database.

   After you configure management database with Database in Oracle RAC option selected and the Test Connection is successful, clicking Discovery Database does not automatically discover the corresponding Profile database(s). You have to manually configure the profile database using the Profile Database tab. You have to manually provide configuration details with user name and password for each profile database.

8. Click Save to save the changes. A Saved Successfully message appears in the Information message pane.

To configure a new Profile database, follow these steps:

1. In the Administration Console, click Data Source Configuration > BSM/APM/OBM > Profile Database.

2. Click Create New. The Connection Parameters dialog box appears.

3. Type the following values in the Connection Parameters dialog box:

   For Oracle database:

   Field	Description
   Database in Oracle RAC	Enable this option to select the Database in Oracle RAC.
   Enable TLS	Enable JDBC connection over TLS.
   Truststore file	Full path to the truststore path. This option is displayed when Enable TLS is selected. It is recommended to have a common trust store file.
   Truststore Password	The password to access the truststore. This option is displayed when Enable TLS is selected.
   Host name	IP address or FQDN of the Profile Database server. Not displayed when Database in Oracle RAC is selected.
   Port	Port number to query the Profile Database server. Not displayed when Database in Oracle RAC is selected.
   Service name	Name of the service. This option appears only if Database in Oracle RAC is selected.
   ORA file name	The ORA file that contains connection information to the Oracle Real Application Cluster. This option appears only if Database in Oracle RAC is selected.
   Database type	The type of database engine that is used to create the Profile Database - Oracle.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Domains	Select the domains for which you want to enable data collection. You must select the domains from which you want to enable data collection. If you have skipped topology configuration during post-install configuration and installed the content packs, you must return here to select from among the following domains to enable data collection. Operations Manager OBM RUM BPM Service Health
   Database instance	System Identifier (SID) of the Profile Database instance. Not displayed when Database in Oracle RAC is selected. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   User name	Name of the Profile Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Profile Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

   For MS SQL Database:

   Field	Description
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Profile Database server.
   Port	Port number to query the Profile Database server.
   Database type	The type of database engine that is used to create the Profile Database - MSSQL.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Domains	Select the domains for which you want to enable data collection. You must select the domains from which you want to enable data collection. If you have skipped topology configuration during post-install configuration and installed the content packs, you must return here to select from among the following domains to enable data collection. Operations Manager OBM RUM BPM Service Health
   Database instance	System Identifier (SID) of the Profile Database instance. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   Windows Authentication	If you have selected MSSQL as the database type, you have the option to enable Windows authentication for MSSQL, that is, the user can use the same credentials to access SQL Server as that of the Windows system hosting the database. This option is not supported if OBR server is installed on Linux Operating System.
   Database name	Name of the database. This field appears only if MSSQL is selected as the database type.
   User name	Name of the Profile Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the Profile Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

4. Click OK.

5. Click Test Connection to test the connection.
6. Click Save to save the changes made on this page. A Saved Successfully message appears in the Information message pane.

After you save the newly created Management database connection, OBR (local collector or remote collector) retrieves the Profile database information from the Management database data source and lists all the existing Profile database data sources under the Profile Database section of the page.

Data collection for the Profile database data source is enabled by default. In addition, the collection frequency is scheduled for every one hour.

In case of a Remote Collector, the collection station has to be selected from the Database type drop down box provided in the Profile Database section of the page.

Enable KPI Data Collection for Service Health CIs

KPIs are high-level indicators of a CI’s performance and availability. The KPI data pertaining to certain logical Service Health CIs, such as Business Service, Business Application, Business Process, and Host, are logged by default in the Profile database. OBR collects this data from the database for reporting.

However, the KPI data for other CI types are not automatically logged in the Profile database. To enable the logging of the KPI data for these CI types, you must configure the CIs in the BSM. For more information, see the Persistent Data and Historical Data section of the Business Service Management - Using Service Health guide. This document is available for the product, Application Performance Management (BAC), at the Software URL.

After installing OBM Event Content Packs, you must configure OBR to collect required data from various data collectors. The data collectors work internally within the OBR infrastructure to collect the data. Therefore, you cannot directly interface with these collectors. Instead, you can specify the data sources from where the collectors can collect the data through the Administration Console.

In OBM deployment scenario, SiteScope and Operations Agent monitors the physical and virtual nodes. When you configure data source in this scenario, choose Operations Agent and/or SiteScope as the data source.

If you install the OBM Content Pack, you must configure the OBM database connection for data collection. You can configure OBR to collect data from the following OBM data repositories:

• Events database: The events database stores data obtained from OBM (9.x versions) data source.

• Operations database: The operations database stores data obtained from OBM 10 (and later versions OBM) data source.

Before you create a new OBM data source connection, make sure that a data source connection for the Management database exists on the Management DB / Profile DB page, see Configuring the Management and Profile Database Data Source topic. This data connection is required to retrieve Assigned User/Group information for OBM, which is stored in the Management database.

If you have one or more OBM setups in your environment, you must configure the OBM data source that belongs to the BSM RTSM that was configured as the topology source.

To configure the OBM data source connections, follow these steps:

1. In the Administration Console, click Data Source Configuration > BSM/APM/OBM > Operations Database.

2. Click Create New to create a new OBM data source connection. The Connection Parameters dialog box appears.

3. Specify or type the following values in the Connection Parameters dialog box:

   For Oracle database:

   Field	Description
   Event Operations	Select your data source.
   Database in Oracle RAC	Enable this option to select the Database in Oracle RAC.
   Enable TLS	Enable JDBC connection over TLS. This option is displayed when Database type selected is ORACLE.
   Truststore file	Full path to the truststore path. This option is displayed when Enable TLS is selected.
   Truststore Password	The password to access the truststore. This option is displayed when Enable TLS is selected.
   Service name	Name of the service. This option appears only if Database in Oracle RAC is selected.
   ORA file name	The ORA file that contains connection information to the Oracle Real Application Cluster. This option appears only if Database in Oracle RAC is selected.
   Host name	IP address or FQDN of the Management Database server. Not displayed when Database in Oracle RAC is selected.
   Port	Port number to query the Management Database server. Not displayed when Database in Oracle RAC is selected.
   Database type	The type of database engine that is used to create the Management Database - Oracle.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Database instance	System Identifier (SID) of the Management Database instance. Not displayed when Database in Oracle RAC is selected. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   User name	Name of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

   For MS SQL database:

   Field	Description
   Event Operations	Select your data source.
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Management Database server.
   Port	Port number to query the Management Database server.
   Database type	The type of database engine that is used to create the Management Database - MSSQL.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Database instance	System Identifier (SID) of the Management Database instance. For information about the database host name, port number, and SID, contact your Business Service Management administrator.
   Windows Authentication	If you have selected MSSQL as the database type, you have the option to enable Windows authentication for MSSQL, that is, the user can use the same credentials to access SQL Server as that of the Windows system hosting the database. This option is not supported if OBR server is installed on Linux Operating System.
   Database name	Name of the database. This field appears only if MSSQL is selected as the database type.
   User name	Name of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

   For PostgreSQL database:

   Field	Description
   Event Operations	Select your data source.
   Database in Oracle RAC	Clear this option.
   Host name	IP address or FQDN of the Management Database server.
   Port	Port number to query the Management Database server.
   Database type	The type of database engine that is used to create the Management Database . For Operations database - PostgreSQL.
   Management Database	Links Profile Database to the Management Database. If you collect data from only SiteScope, no Management Database needs to be selected.
   Database name	Name of the database. This field appears only if MSSQL is selected as the database type.
   User name	Name of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Password	Password of the OBM Database user, which was specified in the BSM Configuration Wizard when setting up the Profile Database. If the Windows Authentication option is selected, this field is disabled.
   Collection Station	This option is used for a collector installed on a remote system.

4. Click OK.

   You can create only one OBM data source connection. After the connection is created, the Create New button is disabled by default. Make sure that you type in the correct values.

5. Click Test Connection to test the connection.
6. Click Save to save the changes. A Saved Successfully message appears in the Information message panel.
7. To change the OBM data collection schedule for one or more hosts, in the Schedule Frequency column, specify a collection time between 1 and 24 hours in the Hrs box.
8. Click Save to save the changes. A Saved Successfully message appears in the Information message panel.

To collect data for OBM, follow these steps on the OBR Administration Console:

1. In Data Source Selection, select Operations Bridge Manager (OBM).

2. In Operations Bridge Manager (OBM), select the version of the application deployed in your environment.

3. (Optional). You may select SiteScope for system performance, Operations Agent and VMware vCenter data source for the virtual environment

4. Click Next

Based on the data sources selected in OBR Administration Console, the content types will be listed in the Data Source Selection Wizard > Content Type Selection page.

Follow these steps to select the content type according to your data sources:

1. In Data Source Selection Wizard > Content Type Selection > Operations Bridge Manager (OBM), select the required Content Type.

2. (Optional).

   1. If you select SiteScope for system performance, then SiteScope Metric Channel section appears.
   2. You must select either Profile DB or Direct API as the metric channel for SiteScope.

In the Content Pack Deployment page, components for Direct API are selected automatically if the option is selected in the Configuration Wizard.

If SiteScope is used to monitor system or virtual environment performance in OBM, the metric channel for SiteScope is through Direct API.

The OBR Administration Console Data Source Selection Wizard > OBM Management Packs/OM SPIs Selection tab displays the selection options only when Enterprise application performance is selected in Content Type Selection tab.

Perform the following steps for each of the deployment scenario:

1. In Data Source Selection Wizard > OBM Management Packs/OM SPIs Selection, select Management Pack and/or Smart Plug-In(SPi).

You must make sure that necessary Management Pack and/or Smart Plug-In (SPi) policies are installed.

2. Click Next.

1. To configure RTSM topology source, follow these steps on the OBR Administration Console > Data Source Configuration > Topology Source page.
2. Click Create New. The Connection Parameter appears.

3. In the Connection Parameter, type the following details:

   Field	Description
   Host name	IP address or FQDN of the APM or OBM server. If your OBM installation is distributed, type the name of the gateway server in the field. In a distributed OBM deployment with multiple gateway servers and load balancer configured, type the virtual IP address of the load balancer in this field.
   Port	Port number to query the RTSM web service. The default port number is 80. Set the port to 443 when RTSM is HTTPS enabled. If the port number has been changed, contact your OBM administrator for more information.
   User name	Name of the RTSM web service user. The default user name is admin. You can use the user with only RTSMOpenApiUser role assigned to it.
   Password	Password of the RTSM web service user.
   Collection station	If you installed collectors on remote systems, you can choose either the local collector or a remote collector. To configure a remote collector to collect data from this RTSM source, select one of the available remote systems in the drop down list. To use the collector that was installed by default on the OBR system, select local.

4. Click OK.
5. Click Save to save the information.

6. Click Test Connection. A success message appears in the information message panel.

   You can configure additional RTSM data sources by repeating the same steps.

   If the Test Connection fails, check the {PMDB_HOME}/log/remotepoller.log for more information.

7. Click Next. The Content Type Selection page appears.

Configure Data Collection When HTTPS is Enabled for RTSM

In case of remote collector, follow the same configuration steps on the system where remote collector is installed.

If RTSM is HTTPS enabled, follow these steps:

1. Set the port to 443 when RTSM is HTTPS enabled during topology source configuration.

2. Export the OBM root CA certificate. You can use the opr-cert-mgmt command-line interface to get certificates.

   For example: ./opr-cert-mgmt.sh ‑export "OBM Webserver CA Certificate" JKS "test" "/tmp/test.jks"

   For more information about the options that OBM provides to get the certificates, see OBM Documentation.

   If FIPS is enabled, export the certificate in PKCS12 format, else export in PEM format.

3. Import the BSM/OBM root CA certificate into OBR server trust store. To import the CA certificates, follow these steps:

   1. On Windows

      keytool -import -trustcacerts -keystore <Path to store> -file "<filename with path>"

   2. On Linux

      keytool -import -trustcacerts -keystore <Path to store> -file "<filename with path>"

      where, <filename with path> is the location and file name of the OBM CA certificates.

      <Path to store> is the path to the trust store. You have to mention the same path in the collection service.

4. On the collector system chosen in above configuration, add the following fields in config.prp, located at %PMDB_HOME%\data (on Windows) $PMDB_HOME/data (on Linux):

   Field	Value
   ucmdb.protocol	https You must make sure to add ucmdb.protocol value in {PMDB_HOME}/data/config.prp file on the OBR server.
   shr.truststorepath	Full path to the keystore file. The path is in the format: C:\HPE-OBR\PMDB\keystore\SHR_CERT_HTTPS.jks Note: You may use the OBR keystore path OR you may create a new keystore.
   shr.truststorepassword	Password of the keystore
   shr.truststoretype	Type of the trust store - JKS or PKCS12

5. Follow these steps to add the entries in collection service scripts:

   1. On Windows

      1. Open the Services window, right-click the HPE_PMDB_Platform_Collection service, and then click Stop.

      2. Add -Djavax.net.ssl.trustStore=<Path to store> -Djavax.net.ssl.trustStorePassword=<password> to JVM_ARGS in %PMDB_HOME%\bin\CollectionServiceCreation.bat file.

         where, <Path to store> is the path to the trust store. Example: C:\OBR\PMDB\keystore\SHR_CERT_HTTPS.jks

         Important If OBR is upgraded from the 10.2x version to 10.3x version, with HTTPs configured RTSM, make sure to update the <Path to store> and <password> in the %PMDB_HOME%\bin\CollectionServiceCreation.bat file.

      3. Recreate the collection service, follow these steps:

         1. Open the command line console, run the following commands:

            CollectionServiceCreation.bat -remove <OV Install Directory> <Product Install Directory>

            CollectionServiceCreation.bat -install <OV Install Directory> <Product Install Directory>

            where, <OV Install Directory> is %OVInstallDir%

            <Product Install Directory> is %PMDB_HOME%\..

      4. Open the Services window, right-click the HPE_PMDB_Platform_Collection service, and then click Start.

   2. On Linux

      1. Go to /etc/init.d directory, and run the following command:

         On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Collection stop

         On RHEL 7.x/SLES 12.x/OEL: systemctl stop HPE_PMDB_Platform_Collection.service

      2. Add -Djavax.net.ssl.trustStore=<Path to store> -Djavax.net.ssl.trustStorePassword=<password> to JVM_ARGS in $PMDB_HOME/bin/hpbsm_pmdb_collector_start.sh files.

         where, <Path to store> is the path to the trust store.

         If OBR is upgraded from the 10.2x version to 10.3x version, with HTTPs configured RTSM, make sure to update the <Path to store> and <password> in the $PMDB_HOME/bin/hpbsm_pmdb_collector_start.sh file.

      3. Go to /etc/init.d directory, and run the following command:

         On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Collection start

         On RHEL 7.x/SLES 12.x/OEL: systemctl start HPE_PMDB_Platform_Collection.service

6. Stop and start the HPE_PMDB_Platform_Administration service as follows:

   On Windows:

   1. Open the Services window, right-click the HPE_PMDB_Platform_Administration service, and then click Stop.
   2. Wait for the service to stop.
   3. Open the Services window, right-click the HPE_PMDB_Platform_Administration service, and then click Start.

   On Linux:

   1. Go to the /etc/init.d directory, and run the following command:

      On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Administration stop

      On RHEL 7.x/SLES 12.x/OEL: systemctl stop HPE_PMDB_Platform_Administration.service

   2. Wait for the service to stop and then run the following command:

      On RHEL 6.x/SLES 11.x: service HPE_PMDB_Platform_Administration start

      On RHEL 7.x/SLES 12.x/OEL: systemctl start HPE_PMDB_Platform_Administration.service

For installing the required Content Packs, OBR provides the Content Pack Deployment page through the Administration Console. This web-based interface simplifies the process of installation by organizing the Content Packs based on the domain, the data source applications from where you want to collect data, and the specific Content Pack components you want to install to collect the data.

Before you begin installing Content Packs, make sure that:

1. Post-installation is complete
2. Data source selections are complete
3. In a distributed scenario, if OBR is installed on Windows, irrespective of BO installed on Windows or Linux or on the same system or different system, you must configure DSN on OBR system (installed on Windows) to connect to Vertica database. If OBR is installed on Linux then installer automatically handles the DSN configuration and connection to Vertica database. To configure DSN, see Configuring DSN on Windows for Vertica Database topic in OBR Documentation. To install Content Packs on Windows Operating System, make sure that UAC is disabled on the system.

Use the Content Pack Deployment page in the Administration Console to install the Content Pack components.

The Content Packs already selected in the Content Pack Deployment page may be mutually exclusive. For information on Content Packs that are mutually exclusive, see Listing of ETLs topic in OBR Documentation.

To install the Content Packs, follow these steps:

1. To log on to Administration Console, follow these steps:

   1. Launch the following URL:

      https://<OBR_Server_FQDN>:21412/OBRApp 

      where, <OBR_Server_FQDN> is the fully qualified domain name of the system where OBR is installed.

   2. Type administrator in the Login Name field and password in the Password field. Click Log In to continue. The Home page appears.

      If you use any other user account to access the Administration Console, make sure that the user account has administrator privileges.

2. On the left pane, click Content Pack Deployment. The Content Pack Deployment page appears.

   The Content Pack Deployment displays the Content Pack components that can be installed in the supported deployment scenario. You can modify the selection by clearing the selected content, the data source application, or the Content Pack components from the list.

   While you clear the components of the selected Content Pack that you do not want to install, make sure that you clear the dependent components of the Content Pack.

   The following table lists the content that is specific to each deployment scenario:

   List of Content Packs

   Content	OBM
   Default	ü
   Cross-Domain Operations Events	ü
   Health and Key Performance Indicators	ü
   IBM WebSphere Application Server	ü
   Microsoft Active Directory	ü
   Microsoft Exchange Server	ü
   Microsoft SQL Server	ü
   MSAppCore	ü
   Network Performance*	ü
   Network Component Health	ü
   Network Interface Health	ü
   Operations Events	ü
   Oracle	ü
   Oracle WebLogic Server	ü
   Real User Transaction Monitoring	ü
   Synthetic Transaction Monitoring	ü
   System Performance	ü
   Virtual Environment Performance	ü

   Make the following selections to generate the reports:

   IBM WebSphere

   • IBMWebSphere_ETL_WebSphereMP - Use IBMWebSphere_ETL_WebSphereMP to gather data from OBM Management Pack for WebSphere.
   • IBMWebSphere_Domain
   • IBMWebSphere_Reports

   Install the following dependent Content Packs (and their components) along with this Content Pack for it to function:

   • Core
     • Core_Domain
     • Core_Domain_AppServer
   • Operations Manager
     • OprEvent_Domain_Reports
   • System Performance
     • SysPerf_Domain

   Microsoft Active Directory

   • MicrosoftActiveDirectory_ETL_ADSPI

   • MicrosoftActiveDirectory_Domain

   • MicrosoftActiveDirectory_Reports

   Install the following dependent Content Packs (and their components) along with this Content Pack for it to function:

   • Core

   • Core_Domain

   • MSAppCore

   Microsoft Exchange

   For Microsoft Exchange 2010

   • Operations Smart Plug-in for Microsoft Exchange 2010, OBM Management Pack for Microsoft Exchange Server
     • MicrosoftExchange_ETL_ExchangeSPI2010
     • MicrosoftExchange_Domain
     • MicrosoftExchange_Reports
     • For Microsoft Exchange 2013
   • Operations Smart Plug-in for Microsoft Exchange 2013, OBM Management Pack for Microsoft Exchange Server
     • MicrosoftExchange_ETL_ExchangeSPI2013
     • MicrosoftExchange_Domain
     • MicrosoftExchange_Reports

   Install the following dependent Content Packs (and their components) along with this Content Pack for it to function:

   • Core
   • Core_Domain
   • MSAppCore
   • System Performance
   • SysPerf_Domain
   • SysPerf_Reports

   Microsoft SQL Server

   • MicrosoftSQLServer_ETL_ADSPI

   • MicrosoftSQLServer_Domain

   • MicrosoftSQLServer_Reports

   Install the following dependent Content Packs (and their components) along with this Content Pack for it to function:

   • Core

   • Core_Domain

   • MSAppCore

   Oracle

   • Oracle_ETL_DBSPI
   • Oracle_Domain
   • Oracle_Reports

   Install the following dependent Content Packs (and their components) along with this Content Pack for it to function:

   • Core
     • Core_Domain
   • Operations Manager
     • OprEvent_Domain_Reports
   • System Performance
     • SysPerf_Domain

   Oracle Weblogic

   • OracleWebLogic_ETL_WebLogicMP - Use OracleWebLogic_ETL_WebLogic_MP to gather data from OBM Management Pack for WebLogic.
   • OracleWebLogic_Domain
   • OracleWebLogic_Reports

   Install the following dependent Content Packs (and their components) along with this Content Pack for it to function:

   • Core
     • Core_Domain

     • Core_Domain_AppServer

   • Operations Manager
     • OprEvent_Domain_Reports
   • System Performance
     • SysPerf_Domain

   The dependent domain content pack get selected automatically, you have to select only the ETLs based on the topology source.

   For more information about the applicable OBM Management Packs, see OBR Documentation.

3. Click Install / Upgrade to install the Content Packs.

   An Installation Started status appears in the Status column for Content Pack that is currently being installed. The Content Pack Deployment page automatically refreshes itself to display the updated status. Once the installation completes, an Installation Successful status appears. If the installation fails, an Installation Failed status appears.

   The HPE_PMDB_Platform_Orchestration and the Timer service will be stopped automatically during Content Pack(s) install/uninstall operation and will be started once operation is complete.

   During install/uninstall process, Content Pack Deployment page does not allow you to interrupt the process. Instead, you must wait till the current process is complete before you can perform any other operations on the Content Pack Deployment page.

After installing Content Packs, you must configure OBR to collect required data from various data collectors. The data collectors work internally within the OBR infrastructure to collect the data. Therefore, you cannot directly interface with these collectors. Instead, you can specify the data sources from where the collectors can collect the data through the Administration Console.

In the RTSM deployment scenario, you do not have to create new Operations Agent data source connections. Because, by default, all the nodes on which Operations Agent is installed are automatically discovered when the topology information is collected. These data sources or nodes are listed in the Operations Agent Data Source page of the Administration Console.

To configure the OBM data source connections, follow these steps:

1. In the Administration Console, click Data Source Configuration > Operations Agent.

2. To view detailed information about the Operations Agent data sources, click the Domain name or the number in the Host collection status summary table. The Hosts : <selected host name> table appears.

3. To change the data collection schedule for one or more hosts, specify a polling time between 1 and 24 hours in the Hrs box in the Collection frequency column.

4. Click Save to save the changes. A Saved Successfully message appears in the Information message panel.

Follow these steps to enable global ID onOBM system:

1. On your OBM system, change the Global ID Generator settings from the JMX Console using the following link:

   http://localhost:21212/jmx-console/

   To access the JMX Console on Linux using the CLI, see OBM Documentation.

2. Click UCMDB:service=Multiple CMDB Instances Services.

   The UCMDB:service=Multiple CMDB Instances Services page appears.

   Figure 1.1 UCMDB:service=Multiple CMDB Instances Services page

   

3. Click setAsGlobalIdGenerator.

   Figure 1.1 (a) SetAsGlobalIdGenerator

   

4. Type 1 as the value for customerID and dbTimeout .

   Figure 1.1 (b) SetAsGlobalIdGenerator

   

5. Click Invoke.

   Figure 1.1 (c) SetAsGlobalIdGenerator

   

   OBM is set as the Global ID Generator.

Create a user account in OBM with permissions to create and view pages in OBM Dashboard . The same OBM user name needs to be created as a user in OBR with permissions to view OBR reports.

In this document, an existing OBM user account admin is used as an example user.

OBR uses SAP BusinessObjects for user management. To create a user in OBR, perform the following steps:

If you are using LDAP user, do not perform the steps 1 to 6, continue from step 7. For more information on LDAP user configurations, see Configure LDAP Authentication for OBR topic in OBR Documentation.

1. Log on to SAP BusinessObjects Central Management Console (CMC) using the following link as an administrator:

   http://<System_FQDN>:8443/BOE/CMC

   where <System_FQDN> is the fully qualified domain name of the system where SAP BusinessObjects is installed.

   Figure 3.1: Log on screen of SAP BusinessObjects Central Management Console

   

2. Select Users and Groups from the drop-down box.

   Figure 3.2: CMC Users and Groups screen

   

3. Select User List and click Create New User icon as shown in figure 1.3.

   Figure 3.3: Creating a new user

   

4. Enter the user details in the New User window as shown in figure 1.4 (a).

   The SAP BusinessObjects username must be the same as the Account Name in OBM.

   1. Check Password never expires under Enterprise Password Settings.

   2. Click Create & Close.

   Figure 3.4(a): Create New User Screen

   

   The newly created user appears in the User List as shown in the following figure:

   

5. To add the OBM user to Administrator group, perform the following steps:

   1. Select the user you created and click the Add member to user group icon as shown below.

      Figure 3.5(a): Add a member

      

   2. Right-click the username and click Join Group.

      Figure 3.5(b): Join Group

      

      A pop-up window Join Group: <username> appears as shown in figure 2.5 (b).

   3. To move Administrators from Available Groups to Destination Group(s), select Administrators, click >, then click OK as shown in figure 2.5 (b).

      Figure 3.5(c): Join Group

      

6. To verify User and Group configuration, perform the following steps:

   1. Double-click admin, the user you created from the list of users.

   2. Select Member Of and check if Administrators is listed on the right side as shown in figure 2.6.

      Figure 3.6: Member of a group

      

7. To ensure proper functioning of the Drill Up/Drill Down functionality in reports while accessing them from the OBM Dashboard console, you must set the user preferences as follows:

   1. Log on to SAP BusinessObjects BI Launch pad with the user credentials created in CMC from the following link:

      https://<Host_Name>:8443/BOE/BI

      where <Host_Name> is the name of the server on which SAP BusinessObjects is installed.

      While logging on to the SAP BusinessObjects BI Launch pad for the first time, make sure to change the password.

   2. Click Preferences in the upper right corner as shown in figure 1.7 (a).

      Figure 3.7(a): Preferences

      

   3. In the General tab, ensure that the default preferences are selected.

      Figure 3.7(b): Preferences

      

   4. Click the Web Intelligence tab, and select the Synchronize drill on report blocks check-box.

      Figure 3.7(c): Preferences

      

Using Lightweight Single Sign-on (LW-SSO), you can enable a OBM Dashboard user to access OBR reports with the same user credentials.

As SAP BusinessObjects is a third-party application, Single Sign-on (SSO) cannot be directly achieved with OBM using LW-SSO. 

• For OBM Dashboard , SSO is setup first between the OBM and OBM using LW-SSO as explained in Configure OBR/OBM LW-SSO Authentication steps.
• Then, SSO is setup between the OBM and SAP BusinessObjects using SAP BusinessObjects Trusted Authentication as explained in Configure SAP BusinessObjects Trusted Authentication steps.

Before setting up LW-SSO, ensure that OBR is in Local Intranet zone on all clients accessing OBM and OBR. To do this, open Internet Explorer and go to Internet Options > Security. Click Local Intranet > Sites >Advanced and add OBR to the zone.

To configure LW-SSO, perform the following steps:

1. Copy the LW-SSO token from OBM:

   1. Log on to the OBM system as Administrator.

   2. Navigate to Administration > Users > Authentication Management.

   3. Copy the Token Creation Key (InitString) and note it down in a text file and click Configure.

      The SSO Configuration Wizard appears.

      

   4. Click Single Sign-On.

      Figure 3.2

      

   5. Under Trusted Hosts/Domains, add the OBM and OBM domain names.

      If OBR and OBM are hosted on the same domain, it is enough to add the domain name once to the Trusted Hosts/Domains list.

   6. Uncheck the Enable SAML2 authentication schema check-box.
   7. Click Next, and then click Finish.
   8. Restart the OBM services for the authentication changes to take effect.

2. To configure LW-SSO in OBR, perform the following steps:

   1. Log on to OBR Administration Console from the following link:

      http://<OBR_Server_FQDN>:21411/OBRApp/

      where, <OBR_Server_FQDN> is the name of the server on which OBR is installed.

   2. Go to Additional Configurations > Security in the left pane.

   3. Click Security and the LW-SSO tab appears.

   4. Copy the values from the Token Creation Key (InitString) field in OBM (This is the InitString you have copied from OBM to a text file.) and paste them into the Init String field.
   5. Check the Enabled option.
   6. In the Domain field, enter the OBR domain.
   7. In the Expiration Period field, enter the recommended value of 60 minutes for LW-SSO configuration.

   8. In the Protected Domains field, add the OBM domain name. Type the multiple protected domain names with comma separated without space.

      1. Even if OBRand OBM are hosted in the same domain, add the domain name to the Protected Domain field.
      2. Ensure <PMDB_HOME>\PMDB\data\config.prp, bo.cms is set to fully qualified doman name of the OBM system.

      3. In OBM integration with OBR, if OBM is https enabled, add/edit the following parameters to the config.prp file:

         • admin.ssl=true
         • bo.ssl=true

         Restart the HPE_PMDB_Platform_Administrator service.

   9. Click Save to save the configuration.

      Figure 3.3

      

      The following confirmation message appears:

      LW-SSO Configuration saved successfully. Please restart the HPE_PMDB_Platform_Administrator' service for these changes to take effect

   10. Restart the HPE_PMDB_Platform_Administrator service from the Windows services list.

1. On OBR system, go to the following location:

   On Windows: %PMDB_HOME%\adminServer\webapps\OBRApp\WEB-INF\classes

   On Linux: cd $PMDB_HOME/adminServer/webapps/OBRApp/WEB-INF/classes

2. Open lwssofmconf.xml and add the following entries after </protectedDomains>:

   Figure 5: Add OBR and OBM FQDNs

   

3. Save the changes to the file.
4. Restart the HPE_PMDB_Platform_Administrator service.

To setup SSO between the OBR Administration Console and SAP BusinessObjects, perform the following steps:

1. On the OBR Administration Console, go to Additional Configurations > Security > BO Trusted Authentication.

   Figure 6.1

   

2. Check the Enabled option.

3. Enter a string of your choice in the Shared Secret box.

   SAP BusinessObjects Trusted Authentication works based on a shared secret mechanism between the OBR Administration Console and SAP BusinessObjects. The string you copied from OBR is the shared secret.  This string is the same shared secret across OBM Administration Console and SAP BusinessObjects.

   To verify if the same shared secret is also configured in SAP BusinessObjects, log on to SAP BusinessObjects CMC.

4. Click Save to save the configuration.

5. Restart the HPE_PMDB_Platform_Administrator service from the Windows services list, to apply the changes made in Configure OBM10 (OBM)/ LW-SSO Authentication and Configure SAP BusinessObjects Trusted Authentication steps.

   On a Linux host, log on as a root user and run the following command:

   service HPE_PMDB_Platform_Administrator stop/start

Disable ClickjackFilterSameOrigin on SAP BusinessObjects system

1. On your SAP BusinessObjects system, go to the following directory:

   On Linux: $PMDB_HOME/BOWebServer/webapps/BOE/WEB-INF

   On Windows: %PMDB_HOME%\BOWebServer\webapps\BOE\WEB-INF

2. Open the web.xml file.

3. Go to ClickjackFilterSameOrigin filter:

   

4. Comment the element as shown here:

   

5. Restart the BusinessObjects service.

   On Linux: SAPBOBJEnterpriseXI40

   On Windows: Business Objects Webserver

6. Wait for five minutes.

Generate the component XML file using the ComponentGenerator command on the OBR host and load it to the OBM host through a combination of manual copying and using the JMX Console.

Generate the report component XML file

Perform the following steps to generate the report component XML file:

1. Log on to the OBR system.
2. Open a command line window (for Windows) or a shell prompt (for Linux) .

3. Run the following commands to see the ComponentGenerator syntax:

   For Windows: %PMDB_HOME%\bin\ComponentGenerator

   For Linux: $PMDB_HOME/bin/ComponentGenerator

   Figure 8.1: (Windows)

   

4. Run the following command to generate the XML file:

   For Windows: %PMDB_HOME%\bin\ ComponentGenerator –c <categoryName> -d <documentId > -n <componentName> -l <outputDir> -f <optional Parameter>

   For Linux:$PMDB_HOME/bin/ ComponentGenerator.sh –c <categoryName> -d <documentId > -n <componentName> -l <outputDir> -f <optional Parameter>

• Category Name = This is the Category to be created in Component Gallery in OBM Dashboard
• Document Id = This is the report’s unique document ID – see the How to find the Document ID for a Report topic in OBR Documentation for more information.
• File Location = This is the directory where the component XML file will be created
• Component Name =  The Component name to be created for the report in OBM Dashboard (note the use of quotes here)

• Optional Parameter = Use non zero value if the report does not accept view or CIID as parameter.

  The above command generates <Component Category><componentName>.uim.xml file in on the Desktop.

  Example

  The following is an example command for System Management Inventory:

  %PMDB_HOME%\bin\ComponentGenerator -c OBR -d AfHfjvp01_pHrwWbfzGNaTY -l C:\Users\Administrator\Desktop -n "SM System Inventory"

  The command displays the following result:

  Figure 8.2: SM System Inventory

  

Perform the following steps to load the report component to OBM Dashboard :

1. From OBR system, copy the report component file *.uim.xml file from OBR.

2. On the OBM system, paste the component XML file at %TOPAZ_HOME%\conf\uimashup\import\toload\Components.

   If OBM is deployed in a distributed environment, the XML file resides in the Gateway Server.

3. Load the XML (*.uim.xml) file using the JMX Console.

   1. On the OBM system, log on to the OBM JMX Console using the following link:

      http://localhost:29000/mbean?objectname=Foundations%3Aservice%3DUIMDataLoader

   2. Enter the credentials if prompted for the username and password.

   3. Click service=UIMDataLoader link as shown in figure 4.4 (a) and navigate to JMX MBean View screen as per figure 4.4 (b)

      Figure 9.1(a): JMX MBean View

      

   4. Go to the method named boolean loadComponentsGallery ()

      Figure 9.1(b): Load Components Gallery

      

   5. Enter 1 as input value in the text field and select true.

   6. Click Invoke to load the *.uim.xml file.

      Figure 9.1(c): Load Components Gallery

      

   The component is visible on OBM system in the following location:

   C:\HPBSM\conf\uimashup\import\toload\Components

   After successful upload, the component is visible in the following location:

   C:\HPBSM\conf\uimashup\import\loaded\Components

4. To verify the availability of the component in OBM Dashboard console:

   1. Log on to the OBM user interface.

   2. Click Workspaces > My Workspace > Component Gallery.

      Figure 9.2: Components Gallery

      

      The component must be available within the category.

5. To verify the wiring, Click Wiring as shown in Figure 4.9.

   By default, all reports are wired on CIChange and ViewChange event. If the report does not support any events, clear the check-box to disable the wiring.

   Figure 9.3: Edit Component

   

You must create a OBM Dashboard page and add the OBM report as a component in the page.

To create a OBM Dashboard page, perform the following steps:

1. On the OBM user interface, click New page.

   Figure 10.1

   

2. Split the page as per the requirement.

   Figure 10.2

   

3. Click Components and drag-drop the components, such as View Explorer, to trigger the events.

4. Drag and drop the required OBR components.

   The OBM report can be viewed in the OBM Dashboard page.

5. Save the page to view it from the OBM Dashboard user interface.

If you get a certificate error as shown in the following image, import the certificate from your browser, and re-launch the browser.

In Internet Explorer, if your browser does not provide a save option for the import certificate settings, import the certificate every time you close or re-launch your browser.