Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create LLR-enabled JDBC data sources

Before you begin

Make sure that the JDBC drivers that you want to use to create database connections are installed on all servers on which you want to deploy the data source. Some JDBC drivers are installed with WebLogic Server, including WebLogic-branded Data Direct JDBC drivers for DB2, Informix, MS SQL Server, and Sybase. For more information about working with JDBC drivers, see Using JDBC Drivers with WebLogic Server.

You can configure a JDBC data source to use the Logging Last Resource (LLR) transaction optimization, which enables one non-XA resource to participate in a global transaction with improved performance and with the same ACID guarantee as XA. For more information about the Logging Last Resource transaction option, see Understanding the Logging Last Resource Transaction Option.

To create an LLR-enabled JDBC data source:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the Domain Structure tree, expand Services, then select Data Sources.
  3. On the Summary of Data Sources page, click New.
  4. On the JDBC Data Source Properties page, enter or select the following information:

    Name - Enter a name for this JDBC data source. This name is used in the configuration file (config.xml) and throughout the Administration Console whenever referring to this data source.

    JNDI Name - Enter the JNDI path to where this JDBC data source will be bound. Applications look up the data source on the JNDI tree by this name when reserving a connection.

    Database Type - Select the DBMS of the database that you want to connect to. If your DBMS is not listed, select Other.

    Database Driver - Select the non-XA JDBC driver you want to use to connect to the database. The list includes common JDBC drivers for the selected DBMS.

    Note: You must install JDBC drivers before you can use them to create database connections. Some JDBC drivers are installed with WebLogic Server, but many are not installed.

    Click Next to continue.

  5. On the Transactions Options page, select global transaction options:

    Supports Global Transactions - Select this check box (the default) to enable global transaction support in this data source.

    Logging Last Resource - Select this option to enable a non-XA JDBC connection to participate in global transactions using the Logging Last Resource (LLR) transaction optimization.

    For more information about transaction options, see JDBC Data Source Transaction Options

    Click Next to continue.

  6. On the Connection Properties page, enter values for the following properties:

    Database Name - Enter the name of the database that you want to connect to. Exact database name requirements vary by JDBC driver and by DBMS.

    Host Name - Enter the DNS name or IP address of the server that hosts the database.

    Port - Enter the port on which the database server listens for connections requests.

    Database User Name - Enter the database user account name that you want to use for each connection in the data source.

    Password/Confirm Password - Enter the password for the database user account.

    Click Next to continue.

  7. On the Test Database Connection page, review the connection parameters and click Test Configuration.

    WebLogic attempts to create a connection from the Administration Server to the database. Results from the connection test are displayed at the top of the page. If the test is unsuccessful, you should correct any configuration errors and retry the test.

    If the JDBC driver you selected is not installed on the Administration Server, you should click Next to skip this step.

    Click Next to continue.

  8. On the Select Targets page, select the servers or clusters on which you want to deploy the data source.
  9. Click Finish to save the JDBC data source configuration and deploy the data source to the targets that you selected.
  10. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

Back to Top