Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# JDBC Store: Configuration

Configuration Options Related Tasks Related Topics

Use this page to configure a JDBC-accessible store for storing subsystem data, such as persistent JMS messages or Store-and-Forward messages.

#### Configuration Options

Name | Description
--- | ---
Name | The name of this JDBC store. This name must be unique within the WebLogic Server instance or its cluster. MBean Attribute: `JDBCStoreMBean.Name` Changes take effect after you redeploy the module or restart the server.
Target | The list of all WebLogic Server instances that have been defined in the current domain and are therefore candidates for hosting this JDBC store. MBean Attribute: `PersistentStoreMBean.Targets`
Data Source | The JDBC data source used by this JDBC store to access its backing table. You cannot configure a JDBC store to use a JDBC data source that is configured to support global transactions. The JDBC store 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. MBean Attribute: `JDBCStoreMBean.DataSource` Changes take effect after you redeploy the module or restart the server.
Prefix Name | The prefix for the JDBC store's database table (`WLStore`), in the following format: `[[[catalog.]schema.]prefix]`. Each period symbol in the `[[catalog.]schema.]prefix` format is significant, where schema generally corresponds to username in many databases. When no prefix is specified, the JDBC store table name is simply `WLStore` and the database implicitly determines the schema according to the JDBC connection's user. As a best practice, you should always configure a prefix for the JDBC `WLStore` table name. For specific guidelines about using JDBC store prefixes, refer to the "Using the WebLogic Store" section of Designing and Configuring WebLogic Server Environments" on `../../config_wls/store.html#JDBCStorePrefixes` Changes take effect after you redeploy the module or restart the server.
Logical Name | The name used by subsystems to refer to different stores on different servers using the same name. For example, an EJB that uses the timer service may refer to its store using the logical name, and this name may be valid on multiple servers in the same cluster, even if each server has a store with a different physical name. Multiple stores in the same domain or the same cluster may share the same logical name. However, a given logical name may not be assigned to more than one store on the same server. MBean Attribute: `PersistentStoreMBean.LogicalName`
Create Table from DDL File | Specifies the DDL (Data Definition Language) file to use for creating the JDBC store's backing table. This field is ignored when the JDBC store's backing table, `WLStore`, already exists. If a DDL file is not specified and the JDBC store detects that a backing table doesn't already exist, the JDBC store automatically creates the table by executing a preconfigured DDL file that is specific to the database vendor. These preconfigured files are located in the `weblogic.jar` file in the `weblogic/store/io/jdbc/ddl` directory. If a DDL file is specified and the JDBC store detects that a backing table doesn't already exist, then the JDBC store searches for the DDL file in the file path first, and then if the file is not found, it searches for it in the CLASSPATH. Once found, the SQL within the DDL file is executed to create the JDBC store's database table. If the DDL file is not found and the backing table doesn't already exist, the JDBC store will fail to boot. Changes take effect after you redeploy the module or restart the server.
Deletes Per Batch Maximum | The maximum number of table rows that are deleted per database call. When possible, a JDBC store uses JDBC 3.0 batching to batch concurrent client requests. Both the maximum batch size for concurrent inserts and for concurrent writes are configurable. To disable JDBC 3.0 batching, set the maximum batch size to 1. The maximum batch size has no effect on the maximum number of concurrent client requests. MBean Attribute: `JDBCStoreMBean.DeletesPerBatchMaximum` Minimum value: `1` Maximum value: `100` Changes take effect after you redeploy the module or restart the server.
Inserts Per Batch Maximum | The maximum number of table rows that are inserted per database call. When possible, a JDBC store uses JDBC 3.0 batching to batch concurrent client requests. Both the maximum batch size for concurrent inserts and for concurrent writes are configurable. To disable JDBC 3.0 batching, set the maximum batch size to 1. The maximum batch size has no effect on the maximum number of concurrent client requests. MBean Attribute: `JDBCStoreMBean.InsertsPerBatchMaximum` Minimum value: `1` Maximum value: `100` Changes take effect after you redeploy the module or restart the server.
Deletes Per Statement Maximum | The maximum number of table rows that are deleted per database call. Applies only when a JDBC store does not use JDBC 3.0 batching to batch concurrent client requests. The maximum deletes per statement has no effect on the maximum number of concurrent client requests. For some databases, the JDBC store may choose a lower value than the one configured. MBean Attribute: `JDBCStoreMBean.DeletesPerStatementMaximum` Minimum value: `1` Maximum value: `100` Changes take effect after you redeploy the module or restart the server.

Related Tasks

- Create JDBC stores
- Create JDBC data sources

Related Topics

- Using the WebLogic Persistent Store
- Configuring and Managing WebLogic JDBC