edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Create JDBC stores

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create JDBC stores


A JDBC store is a JDBC-accessible database for storing subsystem data, such as persistent JMS messages and durable subscriber information.

  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 left panel of the console, expand Services and select Persistent Stores.
  3. On the Summary of Persistent Stores page, click New > Create JDBC Store.

    Note: Once you create a JDBC store, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  4. On the Create a new JDBC Store page, update the following:
    1. Name -- Enter a name for the JDBC Store.
    2. Target -- Select a server instance or migratable target on which to deploy the JDBC store.

      Note: In a clustered environment, a recommended best practice is to target a JDBC store to the same migratable target as the migratable JMS service, so that a member server will not be a single point of failure. A JDBC store can also be automatically migrated from an unhealthy server instance to a healthy server instance, with the help of the server health monitoring services. See Configure migratable targets for JMS-related services.

    3. Data Source -- Select a configured JDBC data source or multi-data source used to access the JDBC store. If you need to configure a JDBC data source for the store, click the Configure a Data Source button.

      Note: You cannot configure a JDBC store to use a JDBC data source that is configured to support global transactions. Instead, it must use a JDBC data source that uses a non-XA JDBC driver. You also cannot enable Logging Last Resource or Emulate Two-Phase Commit in the data source. This limitation does not remove the XA capabilities of layered subsystems that use JDBC stores. For example, WebLogic JMS is fully XA-capable regardless of whether it uses a file store or any JDBC store.

      Note: When a JDBC store is targeted to a migratable target, you must select a data source that is accessible to all candidate servers in the migratable target.

    4. Prefix Name -- Specify a prefix name to prepend to the table name in this JDBC store for use with multiple instances.
    5. Click Finish.

    For more information about these fields, refer to Configuration Options.

  5. On the Summary of Persistent Stores page, select the JDBC store created in steps 2-3.
  6. On the JDBC Store > Configuration tab, update any additional Advanced parameters as required:
    1. Logical Name -- Optional name that can be used by subsystems that need a way to refer to different JDBC stores on different servers in a cluster, but need to refer to them using the same logical name.
    2. Create Table from DDL File -- Used with supported DDL (Data Definition Language) files to create the JDBC store's backing table (WLStore) if one does not already exist.
    3. Deletes Per Batch Maximum, Inserts Per Batch Maximum, and Deletes Per Statement Maximum -- Used to tune JDBC batching performance and should only be used under the directive of Oracle customer support.

    For more information about these fields, refer to Configuration Options.

  7. Click Save.
  8. 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).

After you finish

You do not need to restart the Administration Server after creating and initially configuring a JDBC store. However, if you modify an existing JDBC store, you must restart the Administration Server.


Back to Top