|
|
|
|
|
|
| | | |
Configuring and Managing Transactions
The following sections provides an overview of commonly performed administration tasks related to transactions. For general information on JTA configuration tasks, see Managing Transactions in the Administration Guide. For information on specific configuration attributes and procedures, see the JTA topic in the Administration Console Online Help.
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 Configuring WebLogic Servers and Clusters. The configuration process involves specifying values for attributes. These attributes define the transaction environment, including the following:
You should also be familiar with the administration of J2EE components that can participate in transactions, such as EJBs, JDBC, and JMS.
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.
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 the Server topic in the Administration Console Online Help. For information on using logging in troubleshooting and debugging, see Transaction Log in Troubleshooting Transactions.
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.
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 the Server topic in the Administration Console Online Help. For more information on using monitoring data in troubleshooting, see Transaction Monitoring, in Troubleshooting Transactions.
Adding a Transactional Resource Manager
A transactional resource manager provides access to a collection of information and processes. Transaction-aware JDBC drivers are common resource managers. When adding a JDBC driver, you must configure driver properties for proper operation with JTA. See Managing Transactions in the Administration Guide for JDBC configuration guidelines.
|
|
|
|
|
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|