Skip navigation.
Downloads | Product Documentation | Support

Programming WebLogic JTA

# Configuring and Managing Transactions

This section provides an overview of commonly performed administration tasks related to transactions. For general information on JTA configuration tasks, see JTA in the Administration Console Online Help.

This section discusses the following topics:

- Configuring Transactions
- Monitoring Transactions

# Configuring Transactions

The Administration Console provides the interface used to configure features of WebLogic Server, including WebLogic JTA. To invoke the Administration Console, refer to the procedures described in Starting and Using the Administration Console in the Administration Guide. The configuration process involves specifying values for attributes. These attributes define the transaction environment, including the following:

- Transaction timeouts and limits
- Transaction manager behavior

You should also be familiar with the administration of J2EE components that can participate in transactions, such as EJBs, JDBC, and JMS.

# Monitoring Transactions

You can monitor transactions on a server using the logging, statistics, and monitoring facilities. Use the Administration Console to configure these features and to display the resulting output.

## Logging

The transaction log consists of multiple files. Each file is named using a prefix indicating the location in the file system, as defined by the `TransactionLogFilePrefix` attribute, the server name, a unique numeric suffix, and a file extension. The `TransactionLogFilePrefix` attribute is set for each server in a domain. The overall amount of space consumed by the transaction log is limited only by the file system's available disk space. For more information on setting server logging attributes, see Server —> Logging —> JTA in the Administration Console Online Help. Also see Monitoring Transactions in the Administration Console Online Help.

Note: The transaction log buffer is limited to 250 KB. If your application includes very large transactions that require transaction log writes that exceed this value, WebLogic Server will throw an exception. In that case, you must reconfigure your application to work around the buffer size.

WebLogic Server keeps statistics on transactions organized by server, resource, and transaction name. For more information on viewing statistics, see the JTA topic in the Administration Console Online Help. For information on using statistics in troubleshooting and debugging, see Transaction Statistics in Troubleshooting Transactions.

## Monitoring

You can monitor transactions in progress using the Administration Console. You can display information for transactions by name, transactions by resource, or all active transactions. For more information on monitoring transactions, see Server —> Logging —> JTA in the Administration Console Online Help. For more information on using monitoring data in troubleshooting, see Monitoring Transactions in the Administration Console Online Help.