Installation Guide for Oracle Self-Service E-Billing > Configuring IBM WebSphere > Process of Configuring the IBM WebSphere Application Server for the Command Center Application >

Configuring the Data Sources


You must configure six data sources for the Command Center application on IBM WebSphere.

This task is a step in Process of Configuring the IBM WebSphere Application Server for the Command Center 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 Command Center application server node.
    • Server_Name is the name of the Command Center 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, then click the Create a J2C authentication alias to store the user name and password of the OLTP database. In the Alias field enter OLTP, enter oltp for the user ID and password, 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. Click Apply, then click Save to save changes directly to the master configuration.

  5. Repeat from Step 3 to create a J2C authentication alias for the OLAP database. In the Alias field enter OLAP, enter olap for the user ID and password, and enter OLAP User as the description.
  6. Select Resource, JDBC, and Data Source.
  7. Select the following scope from the list:

    Node=Node_Name, Server=Server_Name

    where:

    • Node_Name is the Command Center application server node.
    • Server_Name is the name of the Command Center application server.
  8. Click New. You must create six data sources for the Command Center 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

    edxLoggerDataSource

    edx.logger.databasePool

    OLTP

    Oracle JDBC Driver

    edxMessagingDataSource

    edx.messaging.databasePool

    OLTP

    Oracle JDBC Driver (XA)

    edxXMADataSource

    edx.xma.databasePool

    OLTP

    Oracle JDBC Driver (XA)

    edxUserDataSource

    edx.user.databasePool

    OLTP

    Oracle JDBC Driver

    reportDataSource

    edx.report.databasePool

    OLAP

    Oracle JDBC Driver (XA)

  9. Click Next, select the Select an existing JDBC provider option, and then select the appropriate option from the list.
  10. 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 Command Center application server.
    • Port_Name is the name of the Command Center application server port.
    • Database is the name of the Command Center database SID.

      For example:

    • For OLTP: jdbc:oracle:thin:@sdcbd80a036:1521:oltp10g
    • For OLAP: jdbc:oracle:thin:@sdcbd80a036:1521:olap10g
  11. 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.
  12. Click Next to view a summary of the data source you just created, click Finish, and then click Save.
  13. To test the newly created data source, select the data source, then click Test connection.
  14. Repeat from Step 8 to create the remaining data sources.
Installation Guide for Oracle Self-Service E-Billing Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.