B.2 Configure Resource Reference in WebLogic Application Server

This section describes how to configure Resource Reference in WebLogic Application server.

In the WebLogic server, you can create a Data Source in the following ways:

  • For a non-RAC Database instance, a Generic Data Source must be created.
  • For a RAC Database instance, a Gridlink Data Source must be created.
  • When Load Balancing/Fail over is required, a Multi Data Source must be created.

Create Data Source

The following steps apply to both config and atomic data source creation:
  1. Open the following URL in the browser window:

    http://<ipaddress>:<administrative console port>/console. (https, if SSL is enabled). The Welcome window is displayed.

  2. Log in with the Administrator Username and Password.

    Figure B-14 WLS Welcome screen

    This image shows the WebLogic Server Welcome screen.
  3. From the LHS menu (Domain Structure), click Services > Data Sources to display the Summary of JDBC Data Sources window.

    Figure B-15 Summary of JDBC Data Sources

    This image shows the Summary of JDBC Data Sources screen.
  4. Click New and select Generic Data Source to display the Create a New JDBC Data Source window.

    Figure B-16 Create a New JDBC Data Source

    This image shows the Create a New JDBC Data Source screen.
    You can also select GridLink Data Source or Multi Data Source while creating a Data Source. For more information, see the Create Data Source or Configure Multi-data Sources sections below.

    Figure B-17 JDBC Data Source Properties

    This image shows the JDBC Data Source Properties screen.
  5. Enter JDBC data source Name, JNDI Name, and select the Database Type from the drop-down list.
  6. Ensure the following:
    • The JNDI Name field must be in the format jdbc/informationdomain
    • The same steps must be followed to create a mandatory data source pointing to the configuration schema of infrastructure with jdbc/FICMASTER as JNDI name.
    • JNDI Name is the same as mentioned in the web.xml file of OFSAAI Application.
    • Required Database Type and Database Driver must be selected.

    Data sources must be created for atomic and atomiccnf schemas following the same steps.

  7. Click Next.

    Figure B-18 Transaction Options

    This image shows the Transaction Options screen.
  8. Select the Database Driver from the drop-down list. You must select the Database Driver depending on database setup, that is, with or without RAC. Click Next.

    Figure B-19 Database Name

    This image shows the Database Name screen.
  9. Select the Supports Global Transactions check box and the One-Phase Commit option.
  10. Click Next to display the Connection Properties window.

    Figure B-20 Database Details

    This image shows the Database Details screen.
  11. Enter the required details such as the Database Name, Host Name, Port, Oracle User Name, Password, and Confirm Password.
  12. Click Next to display the Test Database Connection window.

    Figure B-21 Select Targets

    This image shows the Select Targets screen.
  13. Verify the details and click Test Configuration and test the configuration settings. A confirmation message is displayed stating Connection test succeeded.
  14. Click Finish. The created Data Source is displayed in the list of Data Sources.

    Note:

    • User ID is the Oracle user ID that is created for the respective Information Domain.
    • User ID specified for a data source with FICMASTER as JNDI name must be the Oracle user ID created for the configuration schema.
  15. Select the new Data Source and click the Targets tab.

    Figure B-22 Data Source

    This image shows the Data Source screen.
  16. Select the AdminServer option and click Finish.

Create GridLink Data Source

If you have selected the option, New > GridLink Data Source while creating the Data Source, you can directly specify the JDBC URL as indicated.

Figure B-23 GridLink Data Source

This image shows the GridLink Data Source screen.
  1. Enter the Data Source Name and JNDI Name.
    Ensure that the JNDI Name field is specified in the format jdbc/infodomname and the XA Driver checkbox is not selected. Click Next.

    Figure B-24 JNDI Name

    This image shows the JNDI screen.
  2. Specify Complete JDBC URL, Database User Name, and Password.
  3. Click Finish. The created Data Source is displayed in the list of Data Sources.

Configure Multi-data Sources

A JDBC multi-data source is an abstraction around a group of data sources that provides load balancing and failover between data sources. As with data sources, multi-data sources are also bound to the JNDI tree. Applications can look up a multi-data source on the JNDI tree and then reserve a database connection from a data source. The multi-data source determines from which data source to provide the connection.

When the database used is Oracle RAC (Real Application Clusters), which allows Oracle Database to run across a set of clustered servers, then a group of data sources can be created for instances running on a set of clustered servers and a JDBC multi-data source can be created so that applications can look up a multi-data source on the JNDI tree to reserve database connection. If a clustered server fails, Oracle continues running on the remaining servers.
To configure multi-data sources, follow these steps:
  1. Open the WebLogic Admin Console in the browser window: http://<ipaddress>:<administrative console port>/console. (https if SSL is enabled). The Login window is displayed.
  2. Log in with the user ID with administrative privileges.
  3. In the LHS menu (Domain Structure), select Services > JDBC > Multi Data Sources to display the Summary of JDBC Multi Data Sources window.

    Figure B-25 Multi Data Sources

    This image shows the Multi Data Sources screen.
  4. Click New to display the New JDBC Multi Data Source window.

    Figure B-26 Configure Multi Data Source

    This image shows the Configure Multi Data Source screen.

    Note:

    Ensure that the Data Sources which must be added to the new JDBC Multi Data Source are created.
  5. Enter the JDBC Source Name, JNDI name, and select the Algorithm Type from the drop-down list. Click Next.

    Note:

    • The JNDI Name must be specified in the format jdbc/infodomname.
    • The JNDI Name of the Data Sources that is added to the new JDBC Multi data source must be different from the JNDI name specified during Multi Data Source.
    • The same steps must be followed to create a mandatory data source pointing to the "configuration schema" of infrastructure with jdbc/FICMASTER as JNDI name for Data Source.
    • The JNDI Name provided in the multi-data source must be the same name that is mentioned in the web.xml file of OFSAAI Application.
    • You can select the Algorithm Type as Load-Balancing.

    Figure B-27 JDBC Details

    This image shows the JDBC Details screen.
  6. Select the AdminServer check box and click Next.

    Figure B-28 Select Data Source Type

    This image shows the Select Data Source Type screen.
  7. Select the type of data source to add to the new JDBC Multi Data Source. Click Next.

    Figure B-29 Add Data Sources

    This image shows the Add Data Sources screen.
  8. Map the required Data Source from the Available Data Sources. Click Finish. The New JDBC Multi Data Source is created with added data sources.

Configure Advanced Settings for Data Source

To configure the advanced setting for the data source, follow these steps:
  1. Click the new Data Source from the Summary of JDBC Data Sources window to display the Settings for <Data Source Name> window.
  2. Select the Connection Pooling tab given under Configuration.
  3. Navigate to the Advanced option at the bottom of the window, and check the Test Connection of Reserve checkbox (enables WebLogic Server to test a connection before giving it to a client).

    To verify if the data source is valid, select Data Source Name.

    For example: FICMASTER.

  4. Select the server and click Test Data Source. A message is displayed indicating that the test was successful.

    After the Data Source is created successfully, the following messages are displayed: All changes are activated. No restart is necessary.

    Settings updated successfully. If not, follow these same steps to recreate the data source.

Configure JDBC Connection Pooling

To define the JDBC connection pooling, ensure that you have created the JDBC Provider and Data Source to access the data from the database.
  1. Click the newly created Data Source $DATA_SOURCE$ and navigate to the path: Home>Summary of Services: JDBC>Summary of JDBC Data Sources>JDBC Data Source-<INFODDOM_NAME>.
  2. Set the following values:
    • Initial Capacity: 10
    • Maximum Capacity: 100
    • Capacity Increment: 1
    • Statement Cache Type: LRU
    • Statement Cache Size: 10
  3. Click Save.

Create Work Manager

A Work Manager is used to re-trigger failed messages.

To create a Work Manager, follow these steps:

  • The Name field must have the value wm/WorkManager-TFLT
  • The Type field must have the value Work Manager
  • The Targets field must have the value AdminServer
  • The Scope field must have the value Global
  • The Stuck Thread Action field must have the value Ignore stuck threads. Click Save.

    Figure B-30 Work Manager Screen 1

    This image shows the Work Manager Screen 1.

    Figure B-31 Work Manager Screen 2

    This image shows the Work Manager Screen 2.