Configuring disaster recovery for TrueSight Operations Management Report Engine with Oracle Data Guard

Before you begin

Ensure that TrueSight Infrastructure Management Server and Database is configured for disaster recovery with a host alias created. The host alias points to a primary server and to a recovery server, in case of disaster. For more information, see Disaster recovery deployment architecture (Oracle). For more information about the TrueSight Operations Management Report Engine, see BMC TrueSight Operations Management Reporting.

The example locations of primary (Amsterdam) and secondary (New York City) systems are derived from the configuration scenarios for a disaster recovery system for Oracle .

To set up the primary reporting environment

  1. At the primary location in the Netherlands, install SAP BusinessObjects on Computer A.
  2. At the primary location, install the Reporting Database on Computer B.
    Name the Reporting Database instance, for example, pnetRE.
  3. At the primary location, install the TrueSight Operations Management Report Engine on Computer C.
  4. To configure the cell on the primary computer for event and impact reporting, add the primary Report Engine entry in mcell.dir. For details, see Configuring cells for event reporting.
  5. Create a propagation policy for all events and propagate events to the primary Report Engine. For details, see Configuring cells for event reporting.
  6. Install and configure an Oracle client on the primary SAP BusinessObjects computer (Computer A).
  7. Import and export the BusinessObjects Universe to establish the connections on the SAP BusinessObjects computer.
    Verify that events from the cell are visible in reports.

To set up the recovery reporting environment

  1. At the recovery location in New York City, install SAP BusinessObjects on Computer X.
  2. At the recovery location, install an Oracle Database and create a dummy Reporting Database instance on Computer Y.
    You can create the dummy instance on a separate Oracle Database, or on the recovery Infrastructure Management Database.
    Name the dummy Reporting Database instance, for example, RE_temp.
  3. At the recovery location, install the TrueSight Operations Management Report Engine while connecting to the dummy database instance, on Computer Z.
  4. On the recovery Reporting Database, create a second database instance and name it, for example, pnetRENY.
  5. On the recovery cell, configure event and impact reporting, and create a propagation policy to the recovery Report Engine. For details, see Configuring cells for event reporting.

To configure Oracle Data Guard for disaster recovery of the TrueSight Operations Management Report Engine

When you create an Oracle Data Guard recovery database on Computer Y for the database on Computer B, use the following guidelines and recommendations:

  • Configure the recovery database as a separate database instance (pnetRENY) from the original dummy database instance (RE_temp); both database instances can reside on the same computer. The pnetRENY database instance is populated from the database on the primary system.
  • Follow procedures to set up Oracle Data Guard physical standby functionality in Oracle 11g, which includes many tasks on the primary and recovery databases.
  1. Open the recovery Reporting Database (pnetRENY) in read/write mode and then stop the Report Engine on the recovery location.
  2. On the recovery Report Engine, edit the following configuration files to point to the recovery database instance (pnetRENY, in this example), instead of the dummy instance (RE_temp). Change the database instance name. If the dummy database is created on a different Oracle Database installation, then change the database host name, too.

    File path and name

    Code

    Modification

    <installationDirectory>\ReportEngine
    \bin\reportsCLI\database_config.xml

    <url>jdbc:oracle:thin:@hostName:
    1521:newInstanceName</url>

    Change hostName and newInstanceName to the new instance on the recovery site.

    <installationDirectory>ReportEngine
    \tools\jboss\server\all\deploy\websdk-ds.xml

    <xa-datasource-property name="URL">
    jdbc:oracle:thin:@hostName:
    1521:newInstanceName
    </xa-datasource-property>

    Change hostName and newInstanceName to the new instance on the recovery site.

    _<installationDirectory>_ReportEngine
    \tools\jboss\server\all\deploy\websdk-ds.xml

    <xa-datasource-property name="URL">
    jdbc:oracle:thin:@hostName:
    1521:newInstanceName
    </xa-datasource-property>

    Change hostName and newInstanceName to the new instance on the recovery site.

    <installationDirectory>
    BMCProactiveNetInstalledConfiguration.xml

    <property>
    <name>SCHEMA_HOST</name>
    <value>hostName</value>
    </property>

    <property>
    <name>SCHEMA_INSTANCE
    </name>
    <value>newInstanceName</value>
    </property>

    Change hostName and newInstanceName properties to the new instance on the recovery site.

  3. If the user name on the dummy database instance and the recovery Reporting Database are different, then change the following files:

    File path and name

    Code

    Modification

    _<installationDirectory>_ReportEngine
    \tools\jboss\server\all\conf\login-config.xml

    <module-option name="userName">retest1</module-option>

    Change userName to the new user name.

    <installationDirectory>
    BMCProactiveNetInstalledConfiguration.xml

    <property>
    <name>schemaLogin</name>
    <value>reporting</value>
    </property>

    Change schemaLogin to the new user name.

  4. If the password on the dummy database instance and the recovery Reporting Database are different, run the following utility from the TrueSight Operations Management Report Engine computer:
    • (Windows) <installationDirectory>\ReportEngine\bin\reportsCLI\UpdateReportEngineDBPassword.cmd
    • (Solaris) <installationDirectory>/ReportEngine/bin/reportsCLI/UpdateReportEngineDBPassword.sh
  5. Install and configure an Oracle client on the recovery SAP BusinessObjects computer (Computer X) for recovery instance (pnetRENY).
    1. Import the TrueSight_DataMart.lcmbiar file. See  Manually importing the BMC TrueSight Operations Management universe and reports into supported SAP BusinessObjects  for more information.
    2. Create a connection on the recovery SAP BusinessObjects. See  Connecting SAP BusinessObjects Enterprise to the BMC TrueSight Operations Management Report Engine database  for more information.
    3. After you save the connection in the Design Tool, export the universe.
  6. At the primary location, stop the Report Engine service.
  7. At the recovery location, start the Report Engine, and ensure that the Report Engine comes up without any errors.
  8. Verify the following on the recovery Report Engine:
    • Event data from the primary Report Engine is available on the recovery Report Engine
    • Newly generated events reach the recovery Report Engine
    • Reports are generated by using SAP BusinessObjects
  9. After failover of Infrastructure Management from the primary location to the recovery location, switch Oracle Data Guard to the recovery database.

Note

A DNS alias is not created for SAP BusinessObjects. If failover occurs and the system moves to the recovery site, you need to access the URL for the recovery installation of SAP BusinessObjects. Data on recovery SAP BusinessObjects file system, such as custom reports, are lost.

Related topics

Disaster recovery deployment architecture (Oracle)

Was this page helpful? Yes No Submitting... Thank you

Comments