Decide How You Want to Implement Report Manager

The information in this section is used to determine which Report Manager implementation is appropriate for your organization before doing any installations.

Oracle Communications Report Manager is an optional application within Oracle Communications Session Delivery Manager that is used to centrally manage the following database functions, display functions, and applications:
  • Use Oracle Business Intelligence Publisher (Oracle BI Publisher) application to render reports.
  • Report Manager uses Oracle BI Publisher to render reports based on metrics collected from Historical Data Recording (HDR). HDR is a group of management features used to configure a managed device in order to collect statistics about system operation and function. The Report Manager collects raw data in CSV files from designated devices to aggregate it into time granularities (raw, hourly, daily, monthly, yearly), and make this data available for running reports.

Note:

With the introduction of Oracle Communications Session Delivery Manager, Release 7.5, both the Oracle Communications Session Delivery Manager and Oracle database software, must be installed together on the same server if you are using Report Manager. The Oracle Communications Session Delivery Manager Data Warehouse (OSCDMDW) database software that is used to store collected data from devices that are managed by Oracle Communications Session Delivery Manager.
You can do a simple or Oracle BI Publisher cluster installation for Report Manager:
  • Simple installation—A local standalone installation, local cluster installation, or a remote standalone installation. See the Simple Implementation of Report Manager section for more information.
  • Oracle BI Publisher Cluster Installation and scale-out installation—A remote cluster installation, in which multiple instances of Oracle BI Publisher and Oracle Communications Session Delivery Manager are installed on separate servers. See the Oracle BI Publisher Cluster Implementation of Report Manager section for more information.

    Note:

    You can select this installation option (Enterprise Install) later when you are installing Oracle BI Publisher and creating an Oracle BI Publisher cluster. See the Create a BI Publisher Cluster section in this document for more information.

    Note:

    In a remote cluster installation (Enterprise Install), the Oracle BI Publisher is not on the same server as the Oracle Communications Session Delivery Manager. Ensure that the Oracle database application is installed on one of the servers on which Oracle BI Publisher is installed and on both servers on which Oracle Communications Session Delivery Manager is installed.

Simple Implementation of Report Manager

A simple implementation of Report Manager can include the following types of installations:
  • Local standalone installation—A single local server that has Oracle Communications Session Delivery Manager, Oracle BI Publisher, and their respective databases that work together to generate reports.

    Figure 1-1 Local standalone installation of Report Manager

    Refer to the preceding text for a description of this figure.
  • Local cluster installation—A cluster of local servers that generate reports and provide high availability in case one system experiences a sudden failure. On each local server that is part of the same cluster, Oracle BI Publisher and Oracle Communications Session Delivery Manager are installed with their respective databases. Once installed, the Oracle BI Publisher application is local to the Oracle Communications Session Delivery Manager application.

    Note:

    In a local cluster, the databases synchronize every night. The database content of all non-master cluster nodes is synchronized with the master cluster node. All identifying information for one host, such as a username, password, and database prefix, should be identical to the identifying information of another host in the same cluster.

    Figure 1-2 Local cluster installation of Report Manager

    Refer to the preceding text for a description of this figure.
  • Remote standalone installation—A single remote server that has Oracle Communications Session Delivery Manager, Oracle BI Publisher, and their respective databases.

    Note:

    If you select this type of installation, install Oracle Communications Session Delivery Manager on its server first on Server 1, and next install the Oracle BI Publisher software on Server 2.

    Figure 1-3 Remote standalone installation of Report Manager

    Refer to the preceding text for a description of this figure.
The distinct databases in the illustration above function in the following ways for Oracle Communications Session Delivery Manager, Oracle BI Publisher, and Oracle Communications Report Manager:
  • The Berkeley (SDM) XML database is embedded into the Oracle Communications Session Delivery Manager infrastructure, and provides database storage for Oracle Communications Session Delivery Manager user name and user group variables. It is initiated by the database service.
  • The AcmeBIPublisher database is maintained and used by the Oracle database to hold the schemas and configuration required by the Oracle BI Publisher application.
  • The Oracle Communications Session Delivery Manager Data Warehouse (ocsdmdw) database is maintained by Oracle Communications Session Delivery Manager and it is used to store data that is collected from devices for which collection is enabled is OCSDM.

Oracle BI Publisher Installation for Report Manager

An Oracle BI Publisher installation for Report Manager remote cluster installation, in which multiple instances of Oracle BI Publisher and Oracle Communications Session Delivery Manager are installed on separate servers.

Figure 1-4 Remote cluster installation of Report Manager

Refer to the preceding text for a description of this figure.

The OCSDMDW database on the replica node is synchronized with the master node every night. When the user signs into Oracle BI Publisher from Oracle Communications Session Delivery Manager, the log in is attempted on the Oracle BI Publisher nodes (Server 2 and Server 3) in a round-robin fashion.

If this describes the architecture of your system, first install Oracle Communications Session Delivery Manager on Server 1 and Server 4. Then use this guide to install Oracle BI Publisher on all the Oracle BI Publisher server nodes (That is, Server 2 and Server 3 as shown in the example above).

Note:

You must set up the shared repository according to the security policies of your company.