JBTA-AG-4/12/07

Legal Notices
The information contained in this documentation is subject to change without notice.
Arjuna Technologies Limited makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Arjuna Technologies Limited shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Java� and J2EE is a U.S. trademark of Sun Microsystems, Inc. Microsoft� and Windows NT� are registered trademarks of Microsoft Corporation. Oracle� is a registered U.S. trademark and Oracle9�, Oracle9 Server� Oracle9 Enterprise Edition� are trademarks of Oracle Corporation. Unix is used here as a generic term covering all versions of the UNIX� operating system. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.
Arjuna is a trademark of Hewlett-Packard Company.
Copyright
JBoss, Home of Professional Open Source Copyright 2006, JBoss Inc., and individual contributors as indicated by the @authors tag. All rights reserved.
See the copyright.txt in the distribution for a full listing of individual contributors. This copyrighted material is made available to anyone wishing to use, modify, copy, or redistribute it subject to the terms and conditions of the GNU General Public License, v. 2.0. This program is distributed in the hope that it will be useful, but WITHOUT A WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details. You should have received a copy of the GNU General Public License, v. 2.0 along with this distribution; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, * MA 02110-1301, USA.
Software Version
JBoss Transactions API 4.2.3
Restricted Rights
Legend
Use, duplication, or disclosure is subject to restrictions as set forth in contract subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause 52.227-FAR14.
� Copyright 2007 JBoss Inc.
About This Guide......................................... 5
What This Guide Contains.......................... 5
Audience................................................... 5
Prerequisites............................................... 5
Organization.............................................. 5
Documentation Conventions...................... 5
Additional Documentation......................... 6
Contacting Us............................................ 6
Administration of ArjunaTA....................... 7
Introduction............................................... 7
ObjectStore management........................... 7
ArjunaTA runtime information.................. 8
Failure recovery administration.................. 8
The Recovery Manager.............................. 8
Configuring the Recovery Manager........... 9
Periodic Recovery.................................... 12
Expired entry removal............................. 13
Errors and Exceptions.............................. 13
Selecting the JTA implementation............ 14
The Administration Guide contains information on how to administer JBoss Transactions API 4.2.3.
This guide is most relevant to engineers who are responsible for administration of JBoss Transactions API 4.2.3 installations.
In order to administer ArjunaTA it is first necessary to understand that it relies on ArjunaCore for a lot of the transaction functionality. As such, it is important to read the ArjunaCore Administration Guide before attempting to administer ArjunaTA.
This guide contains the following chapters:
� Chapter 1, Administration of ArjunaTA: describes how to administer ArjunaTA, mainly by selecting the variant of JTA implementation: pure local or remote (allowing distributed transactions).
The following conventions are used in this guide:
|
Description |
|
|
Italic |
In paragraph text, italic identifies the titles of documents that are being referenced. When used in conjunction with the Code text described below, italics identify a variable that should be replaced by the user with an actual value. |
|
Bold |
Emphasizes items of particular importance. |
|
Code |
Text that represents programming code. |
|
|