Oracle Telecommunications Billing Integrator Implementation Guide Release 12.1 Part Number E13596-04

Contents

Previous

Next

Configuring Oracle Applications InterConnect

This appendix provides information on configuring Oracle Applications InterConnect (OAI).

This appendix covers the following topics:

• Oracle Applications InterConnect Overview
• Setting Up OAI Hub
• Setting up OAI Adapter for Advanced Queues
• Dropping the Hub Schema
• Importing OAI Maps to the Repository

Oracle Applications InterConnect Overview

Oracle Applications InterConnect (OAI 9.0.4) is the middleware for TBI. The components of OAI applicable to TBI are: OAI Hub and OAI Adapter for Advanced Queues (AQ).

The OAI Hub contains all the mapping and transformation data required for integration in its repository. The repository is maintained in an Oracle database on the hub machine. The OAI adapter is attached to an application participating in the integration and is responsible for transfer of data from and to the respective application and the OAI hub. Each adapter performs the necessary data transformation based on the OAI repository metadata.

Configuring OAI as the middleware for TBI involves:

1. Setting Up OAI Hub

2. Setting up OAI Adapter for Advanced Queues

3. Dropping the Hub Schema

4. Importing OAI maps to the Repository

Setting Up OAI Hub

Use this procedure to set up the OAI hub.

1. Choose the hub machine.

2. Install Oracle 9iR2 database version 9.2.0.2.1 or higher on the hub machine. Use Oracle Database Configuration Assistant to create an empty database instance to serve as the hub repository. Set the following parameters:

   • HOST: SID: PORT information for the new database instance.

   • Passwords for system and users for the new database instance.

   • TNS name entry for the new database instance.

3. Install Oracle Applications InterConnect Hub version 9.0.4.0.1 on the hub machine. The OAI Hub must be installed in a separate Oracle Home. Provide the following details:

   • Hub DB Parameters: Provide the Host/Port/SID information.

   • Schema Names: Default name for the OAI hub repository schema is ‘oaihub904'.

4. Provide the following schema details:

   • Schema: Oaihub904, owf_mgr

   • Schema User Name: oaihub904, Owf_mgr

   • Password: <hub_user_password>, <workflow_user_password>

5. To create database objects in the hub schema, change folder to OAI_HOME/oai/9.0.4/repository.

6. Run the following command: hubschema - create system/<system_user_pwd> <hub_user_pwd> <HubDB_TNS_Name>

7. Run the following script to start the repository service:

   <OAI_HOME>/oai/9.0.4/repository/start
   

8. To stop the repository service, use the following command:

   <OAI_HOME>/oai/9.0.4/repository/stop
   

Setting up OAI Adapter for Advanced Queues

The Advanced Queuing Adapter (AQ Adapter) allows an instance of E-Business Suite to send or receive information to and from the OAI Hub. The AQ adapter connects to the E-Business Suite database and OAI Hub. It reads and writes into the advanced queues in the E-Business database.

Use this procedure to install and setup the OAI Adapter for Advanced Queues.

1. Install Oracle Application Server InterConnect AQ Adapter v.9.0.4. Provide the following details:

   • Hub DB parameters (Host/ Port/ SID): Connection information to the hub database.

   • Password: Password of the hub schema user.

   • App Name: Used to identify an application participating in the integration. Every instance of an AQ adapter is associated with a particular application. Example: ORA_APPS.

   • Application Spoke DB (Host/ Port/ SID): Connection information to the application database on which the advanced queues are configured. This information usually pertains to an applications database instance. For example: (myserver.domain.com:<port number>:mySID).

   • Spoke Application Database User and Password: User name and password to connect to the Application Spoke DB.

   • Consumer: WF_JMS_OUT

2. After installation, ensure that the aq_bridge_owner parameter in the adapter.ini file is set to the schema name in the Spoke DB (Example: “APPLSYS”).

3. Optionally, to configure the adapter after installation, customize the parameters in the adapter.ini file. Locate the adapter.ini file in <OAI_HOME>/oai/9.0.4/adapters/<ADAPTER_NAME> folder on the host. OAI_HOME is the Oracle home of OAI and ADAPTER_NAME is the application name given to the adapter. Edit the following parameters in adapter.ini file:

   • application: The application name given to the adapter.

   • aq_bridge_host: The host name of the Application Spoke DB.

   • aq_bridge_port: The DB port of the Application Spoke DB.

   • aq_bridge_instance: The SID of the Application Spoke DB.

   • aq_bridge_username: The username to connect to the Spoke DB.

   • encrypted_aq_bridge_password: The encrypted password of the aq_bridge_username. To encrypt a password, use the OAI_HOME/oai/9.0.4/bin/encrypt utility from the console. This utility generates cipher text and prints it on the console, which can be copied to the adapter.ini file.

   • aq_bridge_owner: The name of the schema to which the AQs in the spoke database belongs. This value should be set to a valid schema name before the adapter is started.

4. Optionally, you can configure the following parameters to improve the performance of the adapter:

   • agent_pipeline_to_hub = false

   • agent_pipeline_from_hub = false

   • agent_log_level = 0

5. Copy the DTDs from APPL_TOP at the following location: $XNB_TOP/xml/oag72, and place them in the home folder of the adapter on the host file system, i.e. <OAI_HOME>/oai/9.0.4/adapters/<ADAPTER_NAME>. The AQ Adapter requires the DTDs of the XML messages that it reads and writes into the AQs.

6. To start an adapter service, run the following script from the console:

   <OAI_HOME>/oai/9.0.4/adapters/<ADAPTER_NAME>/start
   

7. To stop an adapter service, run the following script from the console:

   <OAI_HOME>/oai/9.0.4/adapters/<ADAPTER_NAME>/stop
   

Note: The following file contains the log of adapter activities:

<OAI_HOME>/oai/9.0.4/adapters/<ADAPTER_NAME>/logs/<latest_timestamp>/oailog.txt

Dropping the Hub Schema

To drop the hub schema, you must stop the adapters and the repository service. The steps are:

1. Run the following script from the console to stop the adapters:

   <OAI_HOME>/oai/9.0.4/adapters/<ADAPTER_NAME>/stop
   

2. Run the following script from the console to stop the repository service:

   <OAI_HOME>/oai/9.0.4/repository/stop
   

3. Run the following script at the command prompt:

   <OAI_HOME>/oai/9.0.4/repository/hubschema –drop system/<system_user_pwd> <hub_user_pwd> <HubDB_TNS_Name>
   

Importing OAI Maps to the Repository

Seeded integration maps are provided as database export files. This metadata must be imported into an existing OAI 9.0.4 hub repository. Before importing the OAI maps to the repository, you must drop the existing Hub Schema.

Use this procedure to import an OAI map.

1. Run the following script at the command prompt:

   <OAI_HOME>/oai/9.0.4/repository/oaiimport <IntegrationMap_file> <hub_user_name> system/<system_user_pwd> <hub_user_pwd> <HubDB_TNS_Name>
   

   Note: The values are:

   • hub_user_name: Hub schema owner user name. Default is oaihub904.

   • IntegrationMap_file: The path to the database export file containing the map.

   • HubDB_TNS_Name: The TNS entry for the database.

2. If the repository service stops, run the following script to start the repository service:

   <OAI_HOME>/oai/9.0.4/repository/start
   

3. If the adapter service stops, run the following script from the console to start the adapter service:

   <OAI_HOME>/oai/9.0.4/adapters/<ADAPTER_NAME>/start
   

Copyright © 2005, 2010, Oracle and/or its affiliates. All rights reserved.