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 use an XA JDBC driver or configured to support global transactions. 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". MBean Attribute: GenericJDBCStoreMBean.PrefixName 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\store\io\jdbc\ddl directory of the MIDDLEWARE_HOME\modules\com.bea.core.store.jdbc_x.x.x.x.jar file. 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. MBean Attribute: GenericJDBCStoreMBean.CreateTableDDLFile 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.
Worker Count	The number of JDBC store worker threads to process the workerload. A value of 1 indicates a single thread is used (the default). A value greater than 1 indicates that multiple threads are used. For Oracle databases, Oracle recommends users rebuild the primary key index into a reverse index for the JDBC Store table when the worker count is greater than 1. For non-Oracle databases, refer to the database provider's documentation for help with indexing. MBean Attribute: JDBCStoreMBean.WorkerCount Minimum value: 1 Maximum value: 1000 Changes take effect after you redeploy the module or restart the server.
Worker Preferred Batch Size	Specifies the batch size when the Worker Count attribute is configured to a value greater than 1. Used to configure the workload the JDBC store incrementally puts on each worker thread. The workload consists of IO requests which are grouped and pushed to each JDBC worker thread for processing. If the IO request is very large (for example 1M), then tune this attribute to a smaller value. MBean Attribute: JDBCStoreMBean.WorkerPreferredBatchSize Minimum value: 1 Maximum value: 2147483647 Changes take effect after you redeploy the module or restart the server.
Three Step Threshold	Specifies the threshold, in bytes, when the JDBC store uses 3 steps (insert, select, populate) instead of 1 step (insert) to populate an Oracle Blob data type. Applies only to Oracle databases where a Blob data type is used instead of the default Long Raw data type for record data. The default value is 200000. MBean Attribute: JDBCStoreMBean.ThreeStepThreshold Minimum value: 4000 Maximum value: 2147483647 Changes take effect after you redeploy the module or restart the server.

Related Tasks

• Create JDBC stores
• Create JDBC generic data sources

Related Topics

• Using the WebLogic Persistent Store
• Configuring JDBC Data Sources