Bookshelf Home | Contents | Index | PDF     

Integration Guide for Oracle Billing Insight > Integrating Oracle Billing Insight With Oracle BRM >

Installing and Configuring BRM Provider

Follow these steps to install and configure BRM Provider, used to load billing data from Oracle BRM to Oracle Billing Insight.

This task is a step in Process of Setting Up and Integrating Oracle BRM With Oracle Billing Insight.

To install and configure BRM Provider

  1. Verify that the ETL environment is installed and configured. For details see Installation Guide for Oracle Billing Insight.
  2. Configure the TNS alias:
    1. On the Oracle Billing Insight database server, open the tnsnames.ora file, configure a TNS alias connecting to the BRM database for your implementation, and then save the file.

    PINDB =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = Host_Name.Example.com)(PORT = Port_Num))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = PINDB)
    )
    )

    where:

    • Host_Name.Example.com is the BRM database host name.
    • Port_Num is the BRM database listener port.
    • PINDB is the BRM database service name.

      BRM Provider creates a new schema on the Oracle Billing Insight database for pre-staging purposes, which stores simplified versions of Oracle BRM tables.

    1. Do one of the following:
      • If you are installing BRM Provider directly on the Oracle Billing Insight database server, make sure that your tnsnames.ora file contains following alias connecting your Oracle Billing Insight database service.
      • If you are installing BRM Provider remotely (not from Oracle Billing Insight database server), make sure that you have Oracle Client installed on your remote computer, and configure two TNS aliases on your Oracle Client; one must connect to the Oracle BRM database and the other must connect to the Oracle Billing Insight database. For example:

    EBILL =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = Host_Name.Example.com)(PORT = Port_Num))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = EBILL)
    )
    )

    where:

    • Host_Name.Example.com is the EBILL database host name.
    • Port_Num is the EBILL database listen port.
    • EBILL is the EBILL database service name.
  3. Complete this step if your Oracle BRM implementation does not meet the following requirements:
    • The IFW_IMPACT_CAT data in the pipeline schema is loaded into the CONFIG_IMPACT_CATEGORIES_T table in the Oracle BRM schema.
    • The IFW_RUM data in the pipeline schema is loaded into the CONFIG_CANDIDATE_RUMS_T table in the Oracle BRM schema.
    1. (Skip this step if your pipeline tables and Oracle BRM tables reside in the same database schema in your deployment.) Go to the EDX_HOME/integration/db/provider/brm/Scripts directory. Connect to the pipeline schema and run the following script to grant the table access privileges to the Oracle BRM schema:

    sqlplus pipeline_schema_name/pipeline_schema_password@DB_TNS_alias @ifw_grant_priv.sql

    where:

    • pipeline_schema_name is the pipeline schema name.
    • pipeline_schema_password is the pipeline schema password
    • DB_TNS_alias is the Oracle BRM database TNS alias.

      When prompted for the Oracle BRM database user, specify a value for pin_1, where pin_1 is the Oracle BRM schema name.

    1. Connect to the Oracle BRM schema and run the following script:

    sqlplus BRM_schema_name/BRM_schema_password@DB_TNS_alias@prerequisites.sql

    where:

    • BRM_schema_name is the Oracle BRM schema name.
    • BRM_schema_password is the Oracle BRM schema password.
    • DB_TNS_alias is the Oracle BRM database TNS alias.

      The script prompts you for the Oracle BRM pipeline schema owner name.

      When prompted, enter a value for the pipeline database user, specify a value for pre_1, where, pre_1 is the pipeline schema name.

      This step verifies that all data required by the integration solution is located in the Oracle BRM schema. Oracle BRM Provider extracts data from the Oracle BRM schema only.

  4. Configure the parameters in the BRMProvider.properties file, shown here, for your organization. (Verify that the BRM Provider Oracle Data Integrator (ODI) project is in the same working repository where the ETL project was imported.) This file is located in the EDX_HOME/integration/db/provider directory.

    /*
    * Name: BRMProvider.properties
    *
    * $Header: $
    * Copyright (c) 1996, 2015 Oracle. All rights reserved.
    */
    ###############################################
    ### Parameters of Pre-staging area ###
    ###############################################
    --EBILL db host name
    EBILL_DB_HOST=
    --EBILL db listen port
    EBILL_DB_PORT=1521
    --EBILL db service name
    EBILL_DB_SERVICE=
    --Pre-staging user name
    PRESTG_USER=
    --Pre-staging password
    PRESTG_PASSWD=
    --EBILL TNS (Transparent Network Substrate) NAME
    EBILL_TNS_NAME=
    --EBILL SYS PASSWORD
    SYS_PASSWD=
    --EBILL olap user name
    OLAP_USER=
    --EBILL oltp user name
    OLTP_USER=
    ###############################################
    ### Parameters of BRM DB or BRM staging DB ###
    ###############################################
    --BRM Billing System ID(assigned value)
    --Should be the same as the value in adapter configuration file.
    BRM_BILLER_ID=BRM
    --BRM pin user name
    BRM_USER=
    --BRM pin user password
    BRM_PASSWD=
    --BRM PINDB TNS alias
    PINDB_TNS_NAME=
    ###############################################
    ### Parameters of pre-staging tablespaces ###
    ###############################################
    --data tablespace file location
    L_DB_PRESTG_DATA_FILE_LOC=/export/home/oracle/oradata
    --index tablespace file location
    L_DB_PRESTG_INDX_FILE_LOC=/export/home/oracle/oradata
    ###############################################
    ### Parameters for importing ODI objects ###
    ###############################################
    -- ODI home directory
    ODI_HOME_DIR=/export/home/oracle/Middleware/ODI1213
    -- ODI user name
    ODI_USER=SUPERVISOR
    -- ODI password
    ODI_PASSWD=
    -- Master repository db host
    MASTERREP_HOST=
    -- Master repository db port
    MASTERREP_PORT=1521
    -- Master repository db service name
    MASTERREP_SERVICE=
    -- Master repository schema owner name
    MASTERREP_USER=EBILL_ODI_REPO
    -- Master repository schema password
    MASTERREP_PASSWD=
    -- Bin directory where the standalong agent is located
    AGENT_BIN_DIR=/export/home/oracle/Middleware/ODI_Alone/user_projects/domains/ODI_domain/bin
    -- Agent name
    AGENT_NAME=OracleDIAgent1
    -- location where the Billing Insight XML files are located
    XMLFILES_DIR=/Oracle/BillingInsight/integration/db/provider/odi
    -- Work repository name
    WORKREP_NAME=WORKREP
    -- Billing data will be extracted since this start date (in MM/DD/YYYY format)
    BILLING_DATA_START_DT=01/01/2015

  5. Set up the pre-staging area:
    1. Go to the EDX_HOME/integration/db/provider directory and run the ant script.
    2. On the Oracle Billing Insight BRM Provider Install Menu, run Options 1, 2, and 3 individually or select Option 4 (Run steps 1-3) to install.
  6. Specify the required parameters in the ODI studio to enable load notification email to be sent when loading completes:
    1. Log into the ODI studio, expand Global Objects and then Global Variables, and set the following global variables values for notification:
      Global Variable
      Description

      08_Email_ToAddress

      The email address to receive processing notifications from ODI.

      09_Email_FromAddress

      The email address to appear in the From field on email notifications generated by ODI.

      10_Email_CCAddress

      The email address to copy on any notifications sent by ODI.

      11_Email_SMTPPort

      The number of the authenticated SMTP listener port to use for sending email notifications from ODI. The default is 465.

      12_Email_SMTPServer

      The name of the SMTP server to use for sending email notifications from ODI.
    2. Expand Projects, BRMProvider, DATA_LOAD, and Packages, and then double-click Notification package. On the bottom right panel, set the Password for Authentication parameter.
    3. Regenerate the Notification Version 001 scenario. Expand Load Plans and Scenarios, BRMProvider, and DATA_LOAD. Right-click Notification Version 001 and select Regenerate.
  7. If you want BRM AQAdapter to automatically start the postpay data extraction and load into Oracle Billing Insight using the ODI Webservice when Oracle BRM finishes a bill run, then follow these steps to modify the pin_bill_day script, adding the bill_run_event.sh script into the existing logic to publish a billRun event into the Advanced Queue:
    1. To use encryption, make OpenSSL available on your Oracle BRM server.

      The enq_bill_run_event.sh script uses OpenSSL to perform encryption.

    2. Set ORACLE_HOME and PIN_HOME for the enq_bill_run_event.sh script.
    3. Upload the enq_bill_run_event.sh and enq_bill_run_event.txt files located in the EDX_HOME/integration/aqadaptor/brm/ directory to the $PIN_HOME/bin directory, and add execution privilege to the enq_bill_run_event.sh script.
    4. Open the enq_bill_run_event.txt file and set the Oracle BRM schema password as pin_db_password in the following statement:

    sm_pw pin_db_password

    1. Run the enq_bill_run_event.sh script once to encrypt the password. This generates the enq_bill_run_event.enc file which contains the encrypted password. (The enq_bill_run_event.txt file is deleted after the script runs.)
    2. Open the pin_bill_day file and add the last two lines as shown below after the execution of pin_bill_accts:

    #
    # IMPORTANT: Must finish before next step.
    #
    #-------------------------------------------------------------------
    pin_bill_accts -pay_type 10007 $1 $2 $3
    err=$?
    if [ $err != 0 ]; then
    exit $err;
    fi
    pin_bill_accts -discount $1 $2 $3
    err=$?
    if [ $err != 0 ]; then
    exit $err;
    fi
    pin_bill_accts -sponsorship $1 $2 $3
    err=$?
    if [ $err != 0 ]; then
    exit $err;
    fi
    pin_bill_accts $1 $2 $3
    err=$?
    if [ $err != 0 ]; then
    exit $err;
    fi
    wait
    echo "Publish billRun event"
    enq_bill_run_event.sh > /dev/null

  8. Comment out the pin_collect feature in the pin_bill_day script to enable customers to make payments using Oracle Billing Insight and suppress the automatic payment feature in Oracle BRM. Comment all of the pin_collect lines for automated credit card collection in the script as shown here:

    #-------------------------------------------------------------------
    # Credit Card Collection (pin_collect -pay_type 10003 -vendor fusa)
    #
    # Collect the balance due from credit card accounts.
    #
    #-------------------------------------------------------------------
    #pin_collect -inactive -pay_type 10003 -vendor fusa
    #pin_collect -active -pay_type 10003 -vendor fusa&
    #pin_collect -close -pay_type 10003 -vendor fusa&
    #-------------------------------------------------------------------
    # Wait for credit card collection to finish up.
    #-------------------------------------------------------------------
    #wait
    #-------------------------------------------------------------------
    # Direct Debit Collection (pin_collect -pay_type 10005 -vendor fusa)
    #
    # Collect the balance due from direct debit accounts.
    #
    #-------------------------------------------------------------------
    #pin_collect -inactive -pay_type 10005 -vendor fusa
    #pin_collect -active -pay_type 10005 -vendor fusa&
    #pin_collect -close -pay_type 10005 -vendor fusa&
    #-------------------------------------------------------------------
    # Wait for direct debit collection to finish up.
    #-------------------------------------------------------------------
    #wait
    #-------------------------------------------------------------------
    # SEPA Direct Debit Collection (pin_collect -pay_type 10018)
    #
    # Collect the balance due from sepa accounts.
    #
    #-------------------------------------------------------------------
    #pin_collect -inactive -pay_type 10018&
    #pin_collect -active -pay_type 10018&
    #pin_collect -close -pay_type 10018&
    #-------------------------------------------------------------------
    # Wait for sepa direct debit collection to finish up.
    #-------------------------------------------------------------------
    #wait

    
Integration Guide for Oracle Billing Insight Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices.