Integration Guide for Oracle Billing Insight > Integrating Oracle Billing Insight With Oracle BRM > Installing Oracle BRM Integration Components Using InstallAnywhere >

Configuring BRM Provider

Follow these steps to configure BRM Provider. BRM Provider can be installed on the Oracle BRM server or a target server, which can be the Oracle Billing Insight database server or another database server.

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

To configure BRM Provider

1. Verify your environment configuration:
   • If you plan to extract and load billing data from Oracle BRM directly to the Oracle Billing Insight database tables, then verify that the ETL environment is installed and configured. For details see Installation Guide for Oracle Billing Insight.
   • If you plan to extract billing data from Oracle BRM to a billing text file (for an On Demand implementation of Oracle Billing Insight), verify that Oracle Data Integrator (ODI) is installed, and the ODI repository and ODI agent are ready on the target database server where you plan to install the BRM Provider pre-staging schema.
2. Configure the TNS alias:
   1. On the target database server where you plan to install the pre-staging schema, 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 target database for pre-staging purposes, which stores simplified versions of Oracle BRM tables. When you plan to output Oracle BRM billing data to database tables (and specify the OUTPUT_TYPE property value as TABLE in the BRMProvider.properties file), the target database must be the Oracle Billing Insight database.

   2. If you are installing BRM Provider directly on the target database server, then make sure that your tnsnames.ora file contains the following alias connecting your target database service.

      If you are installing BRM Provider remotely (not from the target database server), then 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 target database.

      For example:

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

   where:

   • Host_Name.Example.com is the target database host name.
   • Port_Num is the target database listen port.
   • TARGET_SERVICE is the target 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 INTG_HOME/integration/brm/db/provider/brm/Scripts directory, where INTG_HOME is the directory where you installed Oracle Billing Insight integration components. 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 schema owner name, enter a value for BRM_schema_owner_name.

   2. 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 schema owner name, such as for pre_1.

     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. This file is located in the INTG_HOME/integration/brm/db/provider directory. If you specify OUTPUT_TYPE as TABLE, verify that the BRM Provider ODI project is in the same working repository where the ETL project was imported.

   Property Name	Description
   OUTPUT_TYPE	The BRM Provider output type for billing data (postpay, prepay, and unbilled) and master data: FILE. Outputs Oracle BRM data to a text file. The file will be located at the directory specified in the BRMPROV_BILLFILE_LOCATION property. TABLE. Inserts Oracle BRM into Oracle Billing Insight staging tables. (Requires that the pre-staging schema be installed on the EBILL database.)
   PRESTG_WITH_BRM	Indicates whether to install the pre-staging schema on the Oracle BRM staging database: Y. Yes - Install with Oracle BRM. (If this property is set to Y, make sure ODI is available on the Oracle BRM database server, and the ODI repository and Agent have been created before installing BRM Provider.) N. No - Do not install with Oracle BRM. (Set to N if OUTPUT_TYPE is TABLE.)
   BRMPROV_BILLFILE_LOCATION	The directory for storing generated billing files. This property is required only if OUTPUT_TYPE is set to FILE.
   BRMPROV_TMPFILE_LOCATION	The directory for storing temporary files. This property is required only if OUTPUT_TYPE is set to FILE.
   PRESTG_HOST	The pre-staging database host name.
   PRESTG_PORT	The pre-staging database port.
   PRESTG_SERVICE	The pre-staging database service.
   PRESTG_TNS_NAME	The pre-staging TNS (Transparent Network Substrate) name. This property must be the EBILL TNS name if OUTPUT_TYPE is set to TABLE.
   PRESTG_USER	The pre-staging user name.
   PRESTG_PASSWD	The pre-staging password.
   PRESTG_SYS_PASSWD	The pre-staging SYS PASSWORD. This property must be the EBILL database sys password if OUTPUT_TYPE is set to TABLE.
   OLAP_USER	The EBILL OLAP user name. This property is required only if OUTPUT_TYPE is set to TABLE.
   BRM_BILLER_ID	The Oracle BRM Billing System ID (assigned value). The value must be the same as the value in BRM AQAdapter configuration file adaptor.properites.
   BRM_USER	The Oracle BRM pin user name.
   BRM_PASSWD	The Oracle BRM pin user password.
   PINDB_TNS_NAME	The Oracle BRM PINDB TNS alias.
   PINDB_SYS_PASSWD	The Oracle BRM PINDB SYS PASSWORD. This property is required if PRESTG_WITH_BRM is set to Y.
   L_DB_PRESTG_DATA_FILE_LOC	The data tablespace file location.
   L_DB_PRESTG_INDX_FILE_LOC	The index tablespace file location.
   ODI_HOME_DIR	The ODI home directory, or ODI client home directory if installed remotely.
   ODI_USER	The ODI user name (SUPERVISOR).
   ODI_PASSWD	The ODI password.
   MASTERREP_HOST	The master repository database host.
   MASTERREP_PORT	The master repository database port.
   MASTERREP_SERVICE	The master repository database service name.
   MASTERREP_USER	The master repository schema owner name.
   MASTERREP_PASSWD	The master repository schema password.
   WORKREP_NAME	The work repository name.
   AGENT_BIN_DIR	The bin directory where the standalone agent is located.
   AGENT_HOST	The agent host. Specify the hostname instead of the localhost. The agent must be run on the database server where the pre-staging schema is installed.
   AGENT_HOST_PORT	The agent port (the default is 20910).
   AGENT_PROTOCOL	The agent protocol (the default is http).
   AGENT_NAME	The physical agent name (the default is OracleDIAgent1).
   LOG_AGENT_NAME	The logical agent name (the default ODIAgent).
   XMLFILES_DIR	The directory where the BRM Provider ODI XML files are located.
   BILLING_DATA_START_DT	The start date for extracting billing data (in MM/DD/YYYY format).

5. Set up the pre-staging area:
   1. Go to the INTG_HOME/integration/brm/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.

      If you receive the following error when running Option 3, Configuring working repository, you can ignore it:

   com.sunopsis.core.SecurityAccessException: javax.crypto.IllegalBlockSizeException: Input length must be multiple of 16 when decrypting with padded cipher

   ODI cannot decrypt the password cipher text which was not encrypted previously by the current master repository cipher.

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 Web service when Oracle BRM finishes a bill run, then follow these steps to modify the pin_bill_day script, adding the eng_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 INTG_HOME/integration/brm/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

   5. 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.)
   6. 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