-->
edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Configure connectionConfigure connection factory transaction parameters
After you configure a connection factory, you can define a transaction time-out value, and also indicate whether an XA queue or XA topic connection factory is returned, which create sessions that are JTA user-transaction aware.
To configure transactions on a connection factory:
} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i
- If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
- In the Administration Console, navigate to the connection factory resource that you want to configure:
- Click the Configuration > Transactions tab.
- On the Transactions page:
- In Transaction Timeout, specify a timeout value, in seconds, for all transactions on transacted sessions created with this JMS connection factory. This setting has no effect on the transaction-timeout for JTA user transactions.
- In XA Connection Factory Enabled, select whether an XA queue or XA topic connection factory is returned, instead of a standard queue or topic connection factory. An XA factory is required for JMS applications to use JTA user-transactions, but is not required for transacted sessions.
Note: Selecting this option to enable JTA user-transactions with a JDBC store requires that the configured JDBC data source uses a non-XA JDBC driver. 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.
For more information about these fields, see Configuration Options.
- Save your changes:
- Save Changes to JMS Resources in System Modules
- Save changes to JMS resources in an application module
- To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).