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.
Name | Description |
---|---|
Name |
The name of this JDBC store. This name must be unique within the WebLogic Server instance or its cluster. MBean Attribute: 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: |
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: Changes take effect after you redeploy the module or restart the server. |
Prefix Name |
The prefix for the JDBC store's database table
( Each period symbol in the For specific guidelines about using JDBC store prefixes, refer
to the "Using the WebLogic Store" section of Designing and
Configuring WebLogic Server Environments" on
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: |
Create Table from DDL File |
Specifies the DDL (Data Definition Language) file to use for creating the JDBC store's backing table.
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.
MBean Attribute: Minimum value: Maximum value: 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.
MBean Attribute: Minimum value: Maximum value: 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.
MBean Attribute: Minimum value: Maximum value: Changes take effect after you redeploy the module or restart the server. |