Integration Guide for Oracle Billing Insight > Integrating Oracle Billing Insight With Oracle Utilities Customer Care And Billing > Process of Installing and Configuring Oracle Utilities CC&B Integration Components >

Configuring CC&B Provider

Follow these steps to configure CC&B Provider. You can install CC&B Provider on the Oracle Utilities CC&B 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 Billing Insight With Oracle Utilities Customer Care And Billing.

To configure CC&B Provider

1. Verify your environment configuration:
   • If you plan to extract and load billing data from Oracle Utilities CC&B 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 Utilities CC&B 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 CC&B 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 CC&B database for your implementation, and then save the file.

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

   where:

   • Host_Name.Example.com is the CC&B database host name.
   • Port_Num is the CC&B database listener port.
   • CCBDB is the CC&B database service name.

     CC&B Provider creates a new schema on the target database for pre-staging purposes, which stores simplified versions of Oracle Utilities CC&B tables. When you plan to output Oracle Utilities CC&B billing data to database tables (and specify the OUTPUT_TYPE property value as TABLE in the CCBProvider.properties file), the target database must be the Oracle Billing Insight database.

   2. If you are installing CC&B 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 CC&B 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 Utilities CC&B 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. Configure the following parameters in the CCBProvider.properties file for your organization. This file is located in the INTG_HOME/integration/ccb/db/provider directory. If you specify the OUTPUT_TYPE property as TABLE, then verify that the CC&B Provider ODI project is in the same working repository where the ETL project was imported.

   Parameter	Description
   OUTPUT_TYPE	The CC&B Provider output type for billing data (postpay) and master data: FILE. Outputs Oracle Utilities CC&B data to a text file. The file will be located at the directory specified in the PROV_BILLFILE_LOCATION property. TABLE. Inserts Oracle Utilities CC&B into Oracle Billing Insight staging tables. (Requires that the pre-staging schema be installed on the EBILL database.)
   PRESTG_WITH_BILLER	Indicates whether to install the pre-staging schema on the Oracle Utilities CC&B database: Y. Yes - Install with Oracle Utilities CC&B. (If this property is set to Y, make sure ODI is available on the Oracle Utilities CC&B database server, and the ODI repository and Agent have been created before installing CC&B Provider.) N. No - Do not install with Oracle Utilities CC&B. (Set to N if OUTPUT_TYPE is TABLE.)
   PROV_BILLFILE_LOCATION	The directory for storing generated billing files. This property is required only if OUTPUT_TYPE is set to FILE.
   PROV_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.
   BILLER_ID	The Oracle Utilities CC&B Billing System ID (assigned value).
   BILLER_DB_USER	The Oracle Utilities CC&B database user name.
   BILLER_DB_PASSWD	The Oracle Utilities CC&B database user password.
   BILLER_DB_TNS_NAME	The Oracle Utilities CC&B database TNS alias.
   BILLER_DB_SYS_PASSWD	The Oracle Utilities CC&B database SYS account password. This property is required if PRESTG_WITH_BILLER 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 CC&B Provider ODI XML files are located.
   BILLING_DATA_START_DT	The start date for extracting billing data (in MM/DD/YYYY format).

4. Set up the pre-staging area:
   1. Go to the INTG_HOME/integration/ccb/db/provider directory and run the ant script.
   2. On the Oracle Billing Insight CC&B 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 can not decrypt the password cipher text which was not encrypted previously by the current master repository cipher.

5. 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, CCBProvider, 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, CCBProvider, and DATA_LOAD. Right-click Notification Version 001 and select Regenerate.