A JDBC store is a JDBC-accessible database for storing subsystem data, such as persistent JMS messages and durable subscriber information.
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.
For more information about these fields, refer to Configuration Options.
Note: A JDBC store must use a JDBC data source that uses a non-XA JDBC driver and has Supports Global Transactions disabled. 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: Be sure to select a data source that is accessible to all candidate servers.
Note: When selecting a dynamic cluster, the store must be targeted to the same dynamic cluster as the JMS server. When selecting a migratable target, the store must share the same migratable target as the migratable JMS server or SAF agent.
For more information about these fields, refer to Configuration Options.
For more information about these fields, refer to Configuration Options.
After you finish
You do not need to restart the restart the Administration Server after creating and initially configuring a file store. However, if you modify an existing file store, you must restart the Administration Server.