Skip Headers
Oracle® Communications Data Model Adapters and Analytics User's Guide
Release 11.3.2

E37699-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

1 About BRM Adapter for Oracle Communications Data Model

This chapter describes the Oracle Communications Billing and Revenue Management Adapter for Oracle Communications Data Model (BRM Adapter).

This chapter includes the following sections:

For more information on Oracle Communications Data Model, see Oracle Communications Data Model Implementation and Operations Guide.

What is the BRM Adapter for Oracle Communications Data Model?

The BRM Adapter loads data from an Oracle Communications Billing and Revenue Management source system into Oracle Communications Data Model. You can load data in both an initial and an incremental manner. The data from Oracle Communications Billing and Revenue Management populates the Oracle Communications Data Model derived and aggregate tables, reports, and mining models.

The BRM Adapter is an option for Oracle Communications Data Model.

Overview of BRM Adapter for Oracle Communications Data Model

BRM Adapter for Oracle Communications Data Model uses the Extract Load and Transform (EL-T) principle. The adapter supports both Oracle GoldenGate and Oracle Data Integrator (ODI). Oracle GoldenGate is used when you want to provide real-time feed to the staging area, and ODI is used for batch loading (to the staging area) and for transformation in the staging to the Oracle Communications Data Model foundation layer. The BRM Adapter for Oracle Communications Data Model enables the staging layer to perform operational data store for near real-time reporting.

Oracle GoldenGate is an option, if you do not require or do not want true real-time feeds, then can you can use the standard bulk load with ODI-only (default). Using ODI Knowledge Module (KM) for Oracle GoldenGate enables a single User Interface (UI) to be used to configure Oracle GoldenGate and ODI on its own.

Figure 1-1 shows the BRM Adapter for Oracle Communications Data Model architecture.

Figure 1-1 BRM Adapter Architecture

Description of Figure 1-1 follows
Description of "Figure 1-1 BRM Adapter Architecture"

Components of BRM Adapter for Oracle Communications Data Model

The BRM Adapter for Oracle Communications Data Model uses the following components:

BRM Adapter for Oracle Communications Data Model Database Schemas

The BRM Adapter for Oracle Communications Data Model uses the following Database schemas:

  • Source schemas the source system is Oracle Communications Billing and Revenue Management and database schemas is BRM_SRC (PIN).

    See "BRM Source and Oracle Communications Data Model Target Tables" for details on the specific source objects.

  • Staging layer schema. The BRM Adapter for Oracle Communications Data Model uses a staging area when loading data from the BRM system to the foundation layer objects of an Oracle Communications Data Model warehouse. The staging layer contains changed data and historical data storage and provides the source schema to load Oracle Communications Data Model tables.

    The BRM Adapter for Oracle Communications Data Model defines the staging layer with a database schema: BRM_STG. For more information on the BRM_STG schema, see "BRM Adapter for Oracle Communications Data Model Staging Schema Objects".

  • Target schema. The target of the BRM Adapter for Oracle Communications Data Model is an Oracle Communications Data Model warehouse. The specific target objects are the foundation layer objects of the Oracle Communications Data Model. These objects are defined in the ocdm_sys schema (Oracle Communications Data Model). For more information on the ocdm_sys schema, see Oracle Communications Data Model Reference.

    The installation of the BRM Adapter for Oracle Communications Data Model defines additional procedures in the ocdm_sys schema. These procedures are outlined in "BRM Adapter for Oracle Communications Data Model OCDM_SYS Objects".

Schema Definitions Added for the BRM Adapter for Oracle Communications Data Model

Installing and configuring the BRM Adapter for Oracle Communications Data Model as described in Oracle Communications Data Model Installation Guide adds the following definitions:

BRM Adapter for Oracle Communications Data Model Staging Schema Objects

After the installation of BRM Adapter for Oracle Communications Data Model, a staging schema is created, (BRM_STG).

The staging schema contains the tables, views, functions, and procedures as shown in "BRM Adapter Staging Schema Objects (BRM_STG)".

BRM Adapter for Oracle Communications Data Model OCDM_SYS Objects

Installing and configuring the BRM Adapter for Oracle Communications Data Model adds the following procedure definitions to the ocdm_sys schema delivered with Oracle Communications Data Model creates procedures in ocdm_sys schema to populate the integrated BRM data.

Procedures

  • DISB_CONS

  • ENAB_CONS

  • INSERT_REF

  • SCD2_UPDATE

Oracle Data Integrator

The BRM Adapter for Oracle Communications Data Model uses ETL created by Oracle Data Integrator (ODI) as the ETL for performing an initial load of the foundation layer objects of the Oracle Communications Data Model (that is, the base, reference, and lookup tables). You can also use ODI ETL to perform a scheduled refresh of the staging database.

For more information on the use of ODI with the BRM Adapter for Oracle Communications Data Model, see the following topics:

Oracle GoldenGate Replication

After you have performed an initial load of the foundation layer objects of the Oracle Communications Data Model using ODI, you can use Oracle GoldenGate to perform real-time feed of BRM source data to the staging database.

For more information on the use of Oracle GoldenGate with the BRM Adapter for Oracle Communications Data Model, see the following topics:

BRM Adapter for Oracle Communications Data Model Execution Flows

The BRM Adapter for Oracle Communications Data Model uses a different execution flow depending on whether you are using the adapter with Oracle GoldenGate:

Execution Flow Using BRM Adapter: ODI Pull Version (without Oracle GoldenGate)

You can use the BRM Adapter for Oracle Communications Data Model with Oracle Data Integrator (ODI) alone. This method of using the BRM Adapter for Oracle Communications Data Model is the ODI-pull version.

Figure 1-2 illustrates the BRM Adapter for Oracle Communications Data Model execution flow when using the adapter only with ODI (ODI-pull version).

Figure 1-2 Execution Flow When Using the Adapter without Oracle GoldenGate

Description of Figure 1-2 follows
Description of "Figure 1-2 Execution Flow When Using the Adapter without Oracle GoldenGate"

The ODI-pull version gives you the option to load data at regular periods. When using the ODI-pull approach, the execution flow is as follows (as shown in Figure 1-2):

  1. (Steps 1 and 3) The BRM Adapter, using ODI, loads the data from the source database into stage database.

  2. (Steps 2 and 5) Using pre and post procedures, the BRM Adapter loads data into several stage database tables; for example, lastday (xxx_ld), delta (_delta), and history tables.

  3. (Step 4 in the diagram) The BRM Adapter loads the delta tables in the staging area using normal table 'MINUS' last day table.

  4. (Step 6 in diagram) The BRM Adapter loads the data from the delta tables into foundation layer of the Oracle Communications Data Model warehouse.

Execution Flow Using BRM Adapter: with Oracle GoldenGate and ODI

When you use the BRM Adapter for Oracle Communications Data Model with Oracle GoldenGate to refresh the foundation layer of the Oracle Communications Data Model warehouse, this method allows the foundation layer data to be synchronized with the BRM source data.

Figure 1-3 illustrates the BRM Adapter for Oracle Communications Data Model execution flow when using the BRM Adapter with Oracle GoldenGate.

Figure 1-3 Execution Flow When Using the BRM Adapter with Oracle GoldenGate

Description of Figure 1-3 follows
Description of "Figure 1-3 Execution Flow When Using the BRM Adapter with Oracle GoldenGate"

When using Oracle GoldenGate with the BRM Adapter for Oracle Communications Data Model, the execution flow is as follows (as shown in Figure 1-3):

  1. Assuming that all Oracle GoldenGate processes for the BRM Adapter for Oracle Communications Data Model are running, whenever new data is placed in the source database, Oracle GoldenGate extracts the new incoming data and uses it to populate the staging tables.

  2. Steps 2 and 3 in Figure 1-3 (Staging area): in this part of the execution process you can hold all the changed data including the current and the historical data. The procedure STG_OCDM_OGG_CDC_LOAD_SCENERIO_PKG handles this process; this runs after the normal tables are updated by the Oracle GoldenGate extract process.

    Note:

    Only the data in the delta history tables remains forever and is always synchronized with source data. Once the data in the delta staging tables is loaded into the foundation layer of the Oracle Communications Data Model warehouse, the delta tables are truncated.
  3. The final step Step 4 in Figure 1-3 is to load data from the Delta tables to the foundation layer of Oracle Communications Data Model; to do this use the ODI package STG_OCDM_OGG_CDC_LOAD_SCENARIO_PKG which depends on STG_OCDM_OGG_CDC_LOAD_PKG.

After the initial installation, if you are planning to use Oracle GoldenGate for incremental loads, you should first use the ODI-pull procedures described in "Execution Flow Using BRM Adapter: ODI Pull Version (without Oracle GoldenGate)" to load data from the source system to the staging system and from the staging system to Oracle Communications Data Model. After the initial load, you can then setup the incremental load to keep the Oracle Communications Data Model data synchronized with the Oracle Communications Billing and Revenue Management source system, as described in "Refreshing the Foundation Layer with Real-Time Data".