Show Table of Contents
18.5. JDBC Object Store Support
18.5.1. JDBC Store for Transactions
JBoss Transactions can now be configured to use a JDBC database as its store. This eliminates the need for an expensive replicated storage solution on the application server machine, as file-based ObjectStore requires replicated storage for failover and recovery.
This is enabled in the Transactions Subsystem by setting the following two attributes using the CLI tool.
- Set
use-jdbc-storetotrue./subsystem=transactions:write-attribute(name=use-jdbc-store, value=true)
- Set
jdbc-store-datasourceto the JNDI name for the data source to use./subsystem=transactions:write-attribute(name=jdbc-store-datasource, value=java:jboss/datasources/TransDS)
The complete set of attributes is provided below.
Table 18.5. Transactions JDBC Store Properties
| Property | Description |
|---|---|
use-jdbc-store
|
Set this to "true" to enable the JDBC store for transactions.
|
jdbc-store-datasource
|
The JNDI name of the JDBC datasource used for storage.
|
jdbc-action-store-drop-table
|
Drop and recreate the action store tables at launch. Optional, defaults to "false".
|
jdbc-action-store-table-prefix
|
The prefix for the action store table names. Optional.
|
jdbc-communication-store-drop-table
|
Drop and recreate the communication store tables at launch. Optional, defaults to "false".
|
jdbc-communication-store-table-prefix
|
The prefix for the communication store table names. Optional.
|
jdbc-state-store-drop-table
|
Drop and recreate the state store tables at launch. Optional, defaults to "false".
|
jdbc-state-store-table-prefix
|
The prefix for the state store table names. Optional.
|
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.