Installation Guide for Oracle Self-Service E-Billing > Configuring IBM WebSphere > Process of Configuring the IBM WebSphere Application Server for the Billing and Payment J2EE Application >

Configuring the Data Sources

You must configure three data source for the Billing and Payment application on IBM WebSphere.

This task is a step in Process of Configuring the IBM WebSphere Application Server for the Billing and Payment J2EE Application.

To configure the data sources

1. Select Resource, JDBC, and Data Source.
2. Select the following scope from the list:

   Node=Node_Name, Server=Server_Name

   where:

   • Node_Name is the Billing and Payment application server node.
   • Server_Name is the name of the Billing and Payment application server.
3. Click New, then click the Create a new J2C authentication alias link. You must create J2C authentication aliases to store the user name and password of the OLTP and OLAP databases.
4. Click New, and create a J2C authentication alias to store the user name and password of the OLTP database. In the Alias field enter OLTP, and enter OLTP User for the description.

   The user ID and password are the database schema user ID and password the alias uses to connect to the database.

5. Click Apply, then click Save to save change directly to the master configuration.
6. Repeat from Step 3 to create a J2C authentication alias for the OLAP database. In the Alias field enter OLAP, and enter OLAP User as the description.
7. Select Resource, JDBC, and Data Source.
8. Select the following scope from the list:

   Node=Node_Name, Server=Server_Name

   where:

   • Node_Name is the Billing and Payment application server node.
   • Server_Name is the name of the Billing and Payment application server.
9. Click New. You must create three data sources for the Billing and Payment application as shown in the following table. Specify the data source name (edxAdminDataSource), JNDI name (edx.databasePool), and J2C authentication alias (OLTP) for the first data source.

   Data Source Name	JNDI Name	J2C Alias	JDBC Provider
   edxAdminDataSource	edx.databasePool	OLTP	Oracle JDBC Driver (XA)
   edxXMADataSource	edx.xma.databasePool	OLTP	Oracle JDBC Driver (XA)
   reportDataSource	edx.report.databasePool	OLAP	Oracle JDBC Driver (XA)

10. Click Next, select the Select an existing JDBC provider option, and select the option from the list.
11. Click Next and specify the URL for the database in the form:

    jdbc:oracle:thin:@Host_Name:Port_Name:Database

    where:

    • Host_Name is the name of the Billing and Payment database server.
    • Port_Name is the name of the Billing and Payment database listener port.
    • Database is the name of the Billing and Payment database SID.

      For example:

    • For OLTP: jdbc:oracle:thin:@sdcbd80a036:1521:oltp10g
    • For OLAP: jdbc:oracle:thin:@sdcbd80a036:1521:olap10g
12. Select Oracle 10g data store helper as the data store helper class name. The data source helper must be consistent with the database that you connect to. For example, if the current database version you connect to is Oracle Database 11g, then choose Oracle 11g data store helper as the data store helper class name.
13. Click Next to view a summary of the data source you just created, then click Finish. Click Save to save the new data source directly to the master configuration.
14. To test the newly created data source, select the data source, then click Test connection.
15. Repeat from Step 9 to create the remaining data sources.