Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

Before you begin

Ensure that BMC ProactiveNet 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 details, see BMC ProactiveNet Installation and Configuration Guide and Disaster recovery.

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

For more information about the BMC ProactiveNet Reporting Engine, see BMC ProactiveNet Performance Management Reporting.

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 Engine Database on Computer B.
    Name the Reporting Engine Database instance, for example, pnetRE.
  3. At the primary location, install the BMC ProactiveNet Reporting Engine on Computer C.
  4. To configure the BMC ProactiveNet Cell on the primary computer for event and impact reporting , add the primary Reporting Engine entry in mcell.dir. For details, see Configuring BMC ProactiveNet cells for event reporting.
  5. Create a propagation policy for all events and propagate events to the primary Reporting Engine. For details, see Configuring BMC ProactiveNet 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 Engine Database instance on Computer Y.
    You can create the dummy instance on a separate Oracle Database, or on the recovery BMC ProactiveNet Database.
    Name the dummy Reporting Engine Database instance, for example, RE_temp.
  3. At the recovery location, install the BMC ProactiveNet Reporting Engine while connecting to the dummy database instance, on Computer Z.
  4. On the recovery Reporting Engine Database, create a second database instance and name it, for example, pnetRENY.
  5. On the recovery BMC ProactiveNet Cell, configure event and impact reporting, and create a propagation policy to the recovery Reporting Engine. For details, see Configuring BMC ProactiveNet cells for event reporting.

To configure Oracle Data Guard for disaster recovery of the BMC ProactiveNet Reporting 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 BMC ProactiveNet Reporting Engine Database (pnetRENY) in read/write mode and then stop the Reporting Engine on the recovery location.
  2. On the recovery Reporting 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 Engine 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 Engine Database are different, run the following utility from the BMC ProactiveNet Reporting 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 bmcppm_90_boxi_31.biar by using BusinessObjects Import Wizard on the recovery SAP BusinessObjects computer.
    2. Create a connection by using BusinessObject Design Tool on the recovery SAP BusinessObjects computer.
      Establish the connection with the recovery instance (pnetRENY) and not the dummy instance.
    3. After you save the connection in the Design Tool, export the universe.
  6. At the primary location, stop the Reporting Engine service.
  7. At the recovery location, start the Reporting Engine, and ensure that the Reporting Engine server comes up without any errors.
  8. Verify the following on the recovery Reporting Engine:
    • Event data from the primary Reporting Engine is available on the recovery Reporting Engine
    • Newly generated events reach the recovery Reporting Engine
    • Reports are generated by using SAP BusinessObjects
  9. After failover of BMC ProactiveNet 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.

The following diagram illustrates BMC ProactiveNet with Oracle Data Guard: