[jboss-svn-commits] JBL Code SVN: r36905 - in labs/jbosstm/trunk: ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US and 3 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Wed Apr 13 10:12:16 EDT 2011
Author: tomjenkinson
Date: 2011-04-13 10:12:15 -0400 (Wed, 13 Apr 2011)
New Revision: 36905
Added:
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/JBossJTS_Administration_Guide.ent
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/JBossJTS_Administration_Guide.xml
labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Web_Service_Component.xml
labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Web_Service_Transaction_Management.xml
Removed:
labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Additional_JAR_Requirements.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ArjunaCore_Runtime_Information.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ArjunaJTS_Installation_And_Administration_Guide.ent
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ArjunaJTS_Installation_And_Administration_Guide.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Errors_And_Exceptions.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Logging.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ObjectStore_Management.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Operating_System_Services.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Preparing_Your_System.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Setting_Properties.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Web_Service_Component.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Web_Service_Transaction_Management.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/publican-maven.cfg
Modified:
labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US/Book_Info.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Author_Group.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Book_Info.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Failure_Recovery_Administration.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Introduction.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Preface.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Revision_History.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Starting_And_Stopping_Transaction_Manager.xml
labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/publican.cfg
labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Book_Info.xml
labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Transactions_XTS_Administration_And_Development_Guide.xml
Log:
JBTM-820 separated the administration and installation guides
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US/Book_Info.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US/Book_Info.xml 2011-04-13 13:53:29 UTC (rev 36904)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US/Book_Info.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -7,7 +7,7 @@
<title>ArjunaJTS Development Guide</title>
<subtitle>Developing distributed transactional applications with JBoss Transactions</subtitle>
<productname>ArjunaJTS</productname>
- <productnumber>4.14.0</productnumber>
+ <productnumber>4.15.0</productnumber>
<edition>0</edition>
<pubsnumber>0</pubsnumber>
<!--
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Additional_JAR_Requirements.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Additional_JAR_Requirements.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Additional_JAR_Requirements.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,13 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation__And_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title>Additional JAR Requirements</title>
- <para>
- To use all of the facilities available within ArjunaJTS, you need to add all of the JAR files contained in the
- <filename>lib/</filename> directory of the distribution to the <varname>CLASSPATH</varname>.
- </para>
-</chapter>
-
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ArjunaCore_Runtime_Information.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/ArjunaCore_Runtime_Information.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ArjunaCore_Runtime_Information.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,17 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title>ArjunaJTS Runtime Information</title>
- <para>
- Compile-time configuration information is available via class
- <classname>com.arjuna.common.util.ConfigurationInfo</classname>. Runtime configuration is embodied in the various
- <!-- Should this be <classname><replaceable>name</replaceable>EnvironmentBean</classname> classes?
- --><name>EnvironmentBean classes, see the configuration section of the user guide. These beans have
- corresponding <!--<interfacename>MBean</interfacename>? -->MBean interfaces and may be linked to JMX for remote
- inspection of the configuration if desired.
- </para>
-</chapter>
-
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ArjunaJTS_Installation_And_Administration_Guide.ent
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/ArjunaJTS_Installation_And_Administration_Guide.ent 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ArjunaJTS_Installation_And_Administration_Guide.ent 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,4 +0,0 @@
-<!ENTITY PRODUCT "ArjunaJTS">
-<!ENTITY BOOKID "ArjunaJTS_Installation_And_Administration_Administration_Guide">
-<!ENTITY YEAR "2010">
-<!ENTITY HOLDER "JBoss.org">
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ArjunaJTS_Installation_And_Administration_Guide.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/ArjunaJTS_Installation_And_Administration_Guide.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ArjunaJTS_Installation_And_Administration_Guide.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,38 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <part>
- <title>Installation</title>
- <xi:include href="Preparing_Your_System.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Operating_System_Services.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Logging.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Web_Service_Component.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="ObjectStore_Management.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Additional_JAR_Requirements.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Setting_Properties.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </part>
- <part>
- <title>Administration</title>
- <!-- <xi:include href="Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
- <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Starting_And_Stopping_Transaction_Manager.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ObjectStore_Management.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="OTS_Java_EE_Transaction_Service_Management.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Web_Service_Transaction_Management.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ArjunaCore_Runtime_Information.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Failure_Recovery_Administration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ORB_Specific_Configurations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Initializing_JBossTS_Applications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Errors_And_Exceptions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
-
- </part>
- <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <index />
-</book>
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Author_Group.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Author_Group.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Author_Group.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "JBossJTS_Administration_Guide.ent">
%BOOK_ENTITIES;
]>
<authorgroup>
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Book_Info.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Book_Info.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Book_Info.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,13 +1,13 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "JBossJTS_Administration_Guide.ent">
%BOOK_ENTITIES;
]>
-<bookinfo id="book-ArjunaJTS_Installation_And_Administration_Guide">
- <title>ArjunaJTS Installation And Administration Guide</title>
- <subtitle>Installation and Administration of the ArjunaJTS toolkit, used as part of the ArjunaCore Transaction Service</subtitle>
- <productname>ArjunaJTS</productname>
- <productnumber>4.14.0</productnumber>
+<bookinfo id="book-JBossJTS_Administration_Guide">
+ <title>JBossJTS Administration Guide</title>
+ <subtitle>Administration of the JBossJTS toolkit, used as part of the ArjunaCore Transaction Service</subtitle>
+ <productname>JBossJTS</productname>
+ <productnumber>4.15.0</productnumber>
<edition>1</edition>
<pubsnumber>1</pubsnumber>
<!--
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Errors_And_Exceptions.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Errors_And_Exceptions.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Errors_And_Exceptions.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,51 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title></title>
-
- <para>
- This section covers the types and causes of errors and exceptions which may be thrown or reported during a transactional
- application.
- </para>
- <variablelist>
- <title>Errors and Exceptions</title>
- <varlistentry>
- <term><literal>NO_MEMORY</literal></term>
- <listitem>
- <para>
- The application has run out of memory, and has thrown an <systemitem>OutOfMemoryError</systemitem>
- exception. <application>ArjunaJTS</application> has attempted to do some cleanup, by running the garbage
- collector, before re-throwing the exception. This is probably a transient problem and retrying the invocation
- should succeed.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><literal>com.arjuna.ats.arjuna.exceptions.FatalError</literal></term>
- <listitem>
- <para>
- An error has occurred, and the error is of such severity that that the transaction system must shut
- down. Prior to this error being thrown the transaction service ensures that all running transactions have
- rolled back. If an application catches this error, it should tidy up and exit. If further work is attempted,
- application consistency may be violated.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><literal>com.arjuna.ats.arjuna.exceptions.ObjectStoreError</literal></term>
- <listitem>
- <para>
- An error occurred while the transaction service attempted to use the object store. Further forward progress is
- not possible.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- Object store warnings about access problems on states may occur during the normal execution of crash recovery. This
- is the result of multiple concurrent attempts to perform recovery on the same transaction. It can be safely ignored.
- </para>
-</chapter>
\ No newline at end of file
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Failure_Recovery_Administration.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Failure_Recovery_Administration.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Failure_Recovery_Administration.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,13 +1,13 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "JBossJTS_Administration_Guide.ent">
%BOOK_ENTITIES;
]>
<chapter>
<title>Failure Recovery Administration</title>
<para>
- The failure recovery subsystem of ArjunaJTS will ensure that results of a transaction are applied consistently to
+ The failure recovery subsystem of JBossJTS will ensure that results of a transaction are applied consistently to
all resources affected by the transaction, even if any of the application processes or the machine hosting them
crash or lose network connectivity. In the case of machine (system) crash or network failure, the recovery will not
take place until the system or network are restored, but the original application does not need to be
@@ -32,8 +32,8 @@
<title>The Recovery Manager</title>
<para>
- The failure recovery subsystem of ArjunaJTS requires that the stand-alone Recovery Manager process be running for
- each <systemitem>ObjectStore</systemitem> (typically one for each node on the network that is running ArjunaJTS
+ The failure recovery subsystem of JBossJTS requires that the stand-alone Recovery Manager process be running for
+ each <systemitem>ObjectStore</systemitem> (typically one for each node on the network that is running JBossJTS
applications). The <filename>RecoveryManager</filename> file is located in the arjunaJTS JAR file within the
package <package>com.arjuna.ats.arjuna.recovery.RecoveryManager</package>. To start the Recovery Manager issue the
following command:
@@ -143,7 +143,7 @@
</para>
<note>
<para>
- In previous versions of <application>ArjunaJTS</application>, there was no contact mechanism, and the back-off
+ In previous versions of <application>JBossJTS</application>, there was no contact mechanism, and the back-off
period needed to be long enough to avoid catching transactions in flight at all. From 3.0, there is no such
risk.
</para>
@@ -151,7 +151,7 @@
<para>
Two recovery modules, implementations of the
<interfacename>com.arjuna.ats.arjuna.recovery.RecoveryModule</interfacename> interface, are supplied with
- <application>ArjunaJTS</application>. These modules support various aspects of transaction recovery, including
+ <application>JBossJTS</application>. These modules support various aspects of transaction recovery, including
JDBC recovery. It is possible for advanced users to create their own recovery modules and register them with the
Recovery Manager. The recovery modules are registered with the RecoveryManager using
<methodname>RecoveryEnvironmentBean.recoveryModuleClassNames</methodname>. These will be invoked on each pass of the
@@ -189,12 +189,12 @@
<listitem>
<para>
One TransactionStatusManager item is created by every application process that uses
- <application>ArjunaJTS</application>. It contains the information that allows the RecoveryManager to
+ <application>JBossJTS</application>. It contains the information that allows the RecoveryManager to
determine if the process that initiated the transaction is still alive, and its status. The expiry time for
these items is set by the property
<property>com.arjuna.ats.arjuna.recovery.transactionStatusManagerExpiryTime</property>, expressed in
hours. The default is 12, and 0 (zero) means never to expire.The expiry time should be greater than the
- lifetime of any single processes using <application>ArjunaJTS</application>.
+ lifetime of any single processes using <application>JBossJTS</application>.
</para>
</listitem>
</varlistentry>
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Introduction.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Introduction.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Introduction.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "JBossJTS_Administration_Guide.ent">
%BOOK_ENTITIES;
]>
<chapter>
@@ -17,15 +17,15 @@
</para>
<para>
Apart from ensuring that the run-time system is executing normally, there is little continuous administration needed
- for the ArjunaJTS software. Refer to <xref linkend="important_points_for_administrators" /> for some specific
+ for the JBossJTS software. Refer to <xref linkend="important_points_for_administrators" /> for some specific
concerns.
</para>
<itemizedlist id="important_points_for_administrators">
<title>Important Points for Administrators</title>
<listitem>
<para>
- The present implementation of the ArjunaJTS system provides no security or protection for data. The objects
- stored in the ArjunaJTS object store are (typically) owned by the user who ran the application that created
+ The present implementation of the JBossJTS system provides no security or protection for data. The objects
+ stored in the JBossJTS object store are (typically) owned by the user who ran the application that created
them. The Object Store and Object Manager facilities make no attempt to enforce even the limited form of
protection that Unix/Windows provides. There is no checking of user or group IDs on access to objects for either
reading or writing.
@@ -47,7 +47,7 @@
There is presently no support for version control of objects or database reconfiguration in the event of class
structure changes. This is a complex research area that we have not addressed. At present, if you change the
definition of a class of persistent objects, you are entirely responsible for ensuring that existing instances
- of the object in the Object Store are converted to the new representation. The ArjunaJTS software can neither
+ of the object in the Object Store are converted to the new representation. The JBossJTS software can neither
detect nor correct references to old object state by new operation versions or vice versa.
</para>
</listitem>
Added: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/JBossJTS_Administration_Guide.ent
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/JBossJTS_Administration_Guide.ent (rev 0)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/JBossJTS_Administration_Guide.ent 2011-04-13 14:12:15 UTC (rev 36905)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBossJTS">
+<!ENTITY BOOKID "JBossJTS_Administration_Guide">
+<!ENTITY YEAR "2010">
+<!ENTITY HOLDER "JBoss.org">
Added: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/JBossJTS_Administration_Guide.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/JBossJTS_Administration_Guide.xml (rev 0)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/JBossJTS_Administration_Guide.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -0,0 +1,17 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "JBossJTS_Administration_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<book>
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Starting_And_Stopping_Transaction_Manager.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="OTS_Java_EE_Transaction_Service_Management.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Failure_Recovery_Administration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ORB_Specific_Configurations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Initializing_JBossTS_Applications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <index />
+</book>
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Logging.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Logging.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Logging.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,34 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title>Logging</title>
- <para>
- The recovery manager and the transaction server services produce log files which are located in the <filename>services/logs/</filename> directory. Two log files are created per service.
- </para>
- <variablelist>
- <varlistentry>
- <term><filename><replaceable>service-name</replaceable>-service.log</filename></term>
- <listitem>
- <para>
- Contains information regarding whether the service is stopped, started, restarted, or in another state.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><filename><replaceable>service-name</replaceable>.log</filename></term>
- <listitem>
- <para>
- Contains information logged from the actual service.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- To configure what information is logged in these files, edit the appropriate LOG4J configuration files located in
- <filename>services/config/</filename>.
- </para>
-</chapter>
-
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ObjectStore_Management.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/ObjectStore_Management.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/ObjectStore_Management.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,73 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title>ObjectStore Management</title>
- <para><!-- This is duplicate content from the Installation Guide --> Within the transaction service installation, the
- object store is updated regularly whenever transactions are created, or when <application>Transactional Objects for
- Java</application> is used. In a failure-free environment, the only object states which should reside within the
- object store are those representing objects created with the <application>Transactional Objects for Java</application>
- API.
- </para>
- <para>
- However, if failures occur, transaction logs may remain in the object store until crash recovery facilities have
- resolved the transactions they represent. As such it is very important that the contents of the object store are not
- deleted without due care and attention, as this will make it impossible to resolve in doubt transactions. In
- addition, if multiple users share the same object store it is important that they realize this and do not simply
- delete the contents of the object store assuming it is an exclusive resource.
- </para>
-
- <section>
- <title>Specifying the ORB to use</title>
- <para>
- JDK releases from 1.2.2 onwards include a minimum ORB implementation from Sun. If you use such a JDK in conjunction
- with another ORB, you must inform the JVM which ORB to use. Specify the
- <varname>org.omg.CORBA.ORBClass</varname> and <varname>org.omg.CORBA.ORBSingletonClass</varname> properties. In
- earlier versions of the Transaction Manager, you needed to specify these properties explicitly, either on the command line of in the properties file. However, the ORB Portability classes ensure that these properties are
- automatically set when required. If needed, you can still specify the values explitly. This may be necessary if
- you are not using the ORB initialization methods.
- </para>
-
- </section>
-
- <section>
- <title>The interface repository</title>
- <para>
- The transaction manager ships with two <systemitem>idl</systemitem> files, which are required to build and run
- applications. These files are <filename>CosTransactions.idl</filename> and <filename>ArjunaOTS.idl</filename>. You
- can register them with your interface repository before running any applications. Refer to the manual for your ORB
- for instructions on how to register the interfaces.
- </para>
- </section>
-
- <section>
- <title>Installing into a non-default location</title>
- <procedure>
- <title>Installing into a non-default location</title>
- <step>
- <para>
- Specify the location of the OTS server configuration file, using the
- <varname>OrbPortabilityEnvironmentBean.initialReferencesRoot</varname> property variable. See the Orb
- Portability manual for further details.
- </para>
- </step>
- <step>
- <para>
- Specify the location of the object store, using the
- <varname>ObjectStoreEnvironmentBean.objectStoreDir</varname> property variable.
- </para>
- </step>
- <step>
- <para>
- Update your <varname>CLASSPATH</varname> to reflect the location of the various JBossTS jars in
- <filename><replaceable>JBTS_ROOT</replaceable>/lib</filename> and
- <filename><replaceable>JBTS_ROOT</replaceable>/lib/ext</filename>.
- </para>
- </step>
- </procedure>
- </section>
-
-</chapter>
-
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Operating_System_Services.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Operating_System_Services.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Operating_System_Services.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,160 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title>Operating System Services</title>
-
- <important>
- <para>
- Before running any of the scripts, you must edit the <filename>recoveryservice.conf</filename> and
- <filename>transactionservice.conf</filename> files and replace <replaceable>PUT_JACORB_HOME_HERE</replaceable>
- with the location of your JacORB installation.
- </para>
- </important>
-
- <section>
- <title>Microsoft Windows Server</title>
- <para>
- Four scripts, located in the <filename>Services\bin\windows</filename> folder, install and uninstall the recovery
- manager and transaction server services.
- </para>
- <variablelist>
- <title>Installation Scripts for Microsoft Windows</title>
- <varlistentry>
- <term>Recovery Manager Service</term>
- <listitem><para><filename>InstallRecoveryManagerService-NT.bat</filename></para></listitem>
- </varlistentry>
- <varlistentry>
- <term>Transaction Server</term>
- <listitem><para><filename>InstallTransactionServiceService-NT.bat</filename></para></listitem>
- </varlistentry>
- </variablelist>
- <variablelist>
- <title>Uninstallation Scripts for Microsoft Windows</title>
- <varlistentry>
- <term>Recovery Manager Service</term>
- <listitem><para><filename>UninstallRecoveryManagerService-NT.bat</filename></para></listitem>
- </varlistentry>
- <varlistentry>
- <term>Transaction Server</term>
- <listitem><para><filename>UninstallTransactionServerService-NT.bat</filename></para></listitem>
- </varlistentry>
- </variablelist>
- <note>
- <para>
- Each of the scripts requires administrative privileges.
- </para>
- </note>
- <para>
- After running any of the scripts, a status message indicates success or failure.
- </para>
-
- </section>
-
- <section>
- <title>Linux / UNIX</title>
-
- <procedure>
- <title>Installing Services in Linux / UNIX</title>
- <step>
- <title>Log into the system with <systemitem>root</systemitem> privileges.</title>
- <para>
- The installer needs these privileges to create files in <filename>/etc</filename>.
- </para>
- </step>
- <step>
- <title>Change to <filename><replaceable>JBOSS_HOME</replaceable>/services/installer</filename> directory.</title>
- <para>
- <filename><replaceable>JBOSS_HOME</replaceable></filename> refers to the directory where you extracted ArjunaJTS.
- </para>
- </step>
- <step>
- <title>Set the <varname>JAVA_HOME</varname> variable, if necessary.</title>
- <para>
- Set the <varname>JAVA_HOME</varname> variable to the <firstterm>base directory</firstterm> of the JVM the service
- will use. The base directory is the directory above <filename>bin/java</filename>.
- </para>
- <substeps>
- <step>
- <para>Bash: <command>export JAVA_HOME="/opt/java"</command></para>
- </step>
- <step>
- <para>CSH: <command>setenv JAVA_HOME="/opt/java"</command></para>
- </step>
- </substeps>
- </step>
- <step>
- <title>Run the installer script.</title>
- <para>
- <command>./install_service.sh</command>
- </para>
- </step>
- <step>
- <title>The start-up and shut-down scripts are installed.</title>
- <para>Information similar to the output below is displayed.</para>
- <screen>
- Adding $JAVA_HOME (/opt/java) to $PATH in /opt/arjuna/ats-3.2/services/bin/solaris/recoverymanagerservice.sh Adding
- $JAVA_HOME (/opt/java) to $PATH in /opt/arjuna/ats-3.2/services/bin/solaris/transactionserverservice.sh Installing
- shutdown scripts into /etc/rcS.d: K01recoverymanagerservice K00transactionserverservice Installing shutdown scripts
- into /etc/rc0.d: K01recoverymanagerservice K00transactionserverservice Installing shutdown scripts into /etc/rc1.d:
- K01recoverymanagerservice K00transactionserverservice Installing shutdown scripts into /etc/rc2.d:
- K01recoverymanagerservice K00transactionserverservice Installing startup scripts into /etc/rc3.d:
- S98recoverymanagerservice S99transactionserverservice
- </screen>
- <para>
- The start-up and shut-down scripts are installed for each run-level. Depending on your specific operating
- system, you may need to explicitly enable the services for automatic start-up.
- </para>
- </step>
- </procedure>
-
- <procedure>
- <title>Uninstalling Services in Linux / UNIX</title>
- <step>
- <title>Log into the system with <systemitem>root</systemitem> privileges.</title>
- <para>
- The installer needs these privileges to delete files in <filename>/etc</filename>.
- </para>
- </step>
- <step>
- <title>Change to <filename><replaceable>JBOSS_HOME</replaceable>/services/installer</filename> directory.</title>
- <para>
- <filename><replaceable>JBOSS_HOME</replaceable></filename> refers to the directory where you extracted ArjunaJTS.
- </para>
- </step>
-
- <step>
- <title>Run the installation script with the <option>-u</option> option.</title>
- <para>
- <command>./install_services.sh -u</command>
- </para>
- </step>
- <step>
- <title>The start-up and shut-down scripts are removed.</title>
- <para>
- Messages like the ones below indicate that the start-up and shut-down scripts have been removed successfully.
- </para>
- <screen>
- Removing startup scripts from /etc/rc3.d:
- S98recoverymanagerservice
- S99transactionserverservice
- Removing shutdown scripts from /etc/rcS.d:
- K01recoverymanagerservice
- K00transactionserverservice
- Removing shutdown scripts from /etc/rc0.d:
- K01recoverymanagerservice
- K00transactionserverservice
- Removing shutdown scripts from /etc/rc1.d:
- K01recoverymanagerservice
- K00transactionserverservice
- Removing shutdown scripts from /etc/rc2.d:
- K01recoverymanagerservice
- K00transactionserverservice
- </screen>
- </step>
- </procedure>
- </section>
-</chapter>
-
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Preface.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Preface.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Preface.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "JBossJTS_Administration_Guide.ent">
%BOOK_ENTITIES;
]>
<preface id="pref-ArjunaCore_Administration_Guide-Preface">
@@ -9,7 +9,7 @@
<section>
<title>Prerequisities</title>
<para>
- ArjunaJTS is the implementation of the JTS API provided for use with JBoss Transaction Manager. For more details
+ JBossJTS is the implementation of the JTS API provided for use with JBoss Transaction Manager. For more details
about the Transaction Manager, refer to the ArjunaCore Installation and Administration Guide, which is also
available from the JBoss Transactions website, <ulink url="http://www.jboss.org/jbosstm" />.
</para>
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Preparing_Your_System.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Preparing_Your_System.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Preparing_Your_System.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,57 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title>Preparing Your System</title>
- <procedure>
- <title>Pre-Installation Steps</title>
- <para>
- Before installing the ArjunaJTS software, we recommend the following administrative steps be taken, assuming a default configuration for ArjunaJTS.
- </para>
- <step>
- <title>Optional but recommended: Create a user and group to run JBossTS.</title>
- <para>
- It is recommended that you create a user and group <literal>arjuna</literal>, using the preferred method for
- your operating system. This user runs the OTS transaction manager, ensuring proper ownership of all the
- transaction logs and the object store, and preventing accidental deletion of these objects by any other users.
- </para>
- </step>
- <step>
- <title>Install the distribution into the required location.</title>
- <para>
- Typically, the distribution is extracted from a <filename>.ZIP</filename> file.
- </para>
- </step>
- <step>
- <title>Specify the Location for the Object Store</title>
- <para>
- ArjunaJTS requires a minimum object store for storing the outcome of transactions in the event of system crashes. The location of this should be specified in the properties file using the <property>ObjectStoreEnvironmentBean.objectStoreDir</property> key or by using environment
- variable:
- </para>
- <screen><command>java –DObjectStoreEnvironmentBean.objectStoreDir =C:\temp foo.</command></screen>
- </step>
- <step>
- <title>Optional: Specify the sub-directory within the Object Store root.</title>
- <para>
- By default, all object states will be stored within the <filename>defaultStore/</filename> sub-directory of the
- object store root. For instance, if the object store root is
- <filename>/usr/local/Arjuna/TransactionService/ObjectStore</filename>, the subdirectory
- <filename>/usr/local/Arjuna/TransactionService/ObjectStore/defaultStore/</filename> is used.
- </para>
- <para>
- To change this subdirectory, set the <property>ObjectStoreEnvironmentBean.localOSRoot</property> or
- <property>com.arjuna.ats.arjuna.objectstore.localOSRoot</property> property variable accordingly.
- </para>
- </step>
- <step>
- <title>Optional: Change the JTA implementation to use JTS instead of JTA.</title>
- <para>
- If you plan to use the JBossTS transactional JDBC driver, or JTA with the JTS, you must change the JTA
- implementation to use the JTS. You should consult the ArjunaJTS Development Guide or the JTA manuals for
- details.
- </para>
- </step>
- </procedure>
-</chapter>
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Revision_History.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Revision_History.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Revision_History.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "JBossJTS_Administration_Guide.ent">
%BOOK_ENTITIES;
]>
<appendix>
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Setting_Properties.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Setting_Properties.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Setting_Properties.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,51 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title>Setting Properties</title>
- <para>
- ArjunaJTS has been designed to be highly configurable at runtime through
- the use of various property attributes. <!--, which will be described in
- subsequent sections.-->Although these attributes can be provided at runtime
- on the command line, it may be more convenient to specify them through a
- single properties file or via <methodname>setter</methodname> methods on the
- beans. At runtime, ArjunaJTS looks for the file
- <filename>jbossts-properties.xml</filename>, in a specific search order.
- </para>
- <orderedlist>
- <listitem><para>A location specified by a system property<!--Which one? -->, allowing the normal search path to be overridden.</para></listitem>
- <listitem><para>The directory from which the application was executed.</para></listitem>
- <listitem><para>The home directory of the user that launched ArjunaJTS.</para></listitem>
- <listitem><para><varname>java.home</varname></para></listitem><!-- Is that like $JAVA_HOME? -->
- <listitem><para>The <varname>CLASSPATH</varname>, which normally includes the installation's
- <filename>etc/</filename> directory.</para></listitem>
- <listitem><para>A default set of properties embedded in the <filename>JAR</filename> file.</para></listitem>
- </orderedlist>
- <para>
- Where properties are defined in both the system properties by using the <parameter>-D</parameter> switch, and in the
- properties file, the value from the system property takes precedence. This facilitates overriding individual
- properties easily on the command line.
- </para>
- <para>
- The properties file uses <filename>java.uil.Properties</filename> XML format, for example:
- </para>
- <programlisting>
- <![CDATA[
-<entry key="CoordinatorEnvironmentBean.asyncCommit">NO</entry>
-<entyr key="ObjectStoreEnvironmentBean.objectStoreDir">/var/ObjectStore</entry>
- ]]>
- </programlisting>
- <para>
- You can override the name of the properties file at runtime by specifying a new file using the
- <varname>com.arjuna.ats.arjuna.common.propertiesFile</varname> attribute variable.
- </para>
- <note>
- <para>
- Unlike earlier releases, there is no longer one properties file name per module. This properties file name key is
- now global for all JBoss Transaction Service components in the JVM.
- </para>
- </note>
-</chapter>
-
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Starting_And_Stopping_Transaction_Manager.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Starting_And_Stopping_Transaction_Manager.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Starting_And_Stopping_Transaction_Manager.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaJTS_Installation_And_Administration_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "JBossJTS_Administration_Guide.ent">
%BOOK_ENTITIES;
]>
<chapter>
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Web_Service_Component.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Web_Service_Component.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Web_Service_Component.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,19 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title>Web Service Component</title>
- <para>
- To configure the demo application of the Web Services transactions component and standalone coordinator, edit the
- appropriate <filename>build.xml</filename> file before running <command>ant</command>. Consult the trail map
- accompanying these components for details.
- </para>
- <para>
- When running within JBoss Application Server, it is recommended to use the <literal>all</literal> server
- profile. Specify the profile with the <parameter>-c</parameter> switch: <command>run.sh -c all</command> in Linux,
- or <command>run.bat -c all</command> in Microsoft Windows.
- </para>
-</chapter>
-
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Web_Service_Transaction_Management.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/en-US/Web_Service_Transaction_Management.xml 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/en-US/Web_Service_Transaction_Management.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,219 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Administration_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter>
- <title>Web Service Transaction Service (XTS) Management</title>
- <para>
- The basic building blocks of a transactional Web Services application include the application itself, the Web
- services that the application consumes, the Transaction Manager, and the transaction participants which support
- those Web services. Although it is likely that different developers will be responsible for each piece, the concepts
- are presented here so that you can see the whole picture. Often, developers produce services, or applications that
- consume services, and system administrators run the transaction-management infrastructure.
- </para>
-
- <section>
- <title>Transaction manager overview</title>
- <para>
- The transaction manager is a Web service which coordinates JBossTS transactions. It is the only software component
- in JBossTS that is designed to be run directly as a network service, rather than to support end-user code. The
- transaction manager runs as a JAXM request/response Web service.
- </para>
- <note>
- <para>
- When starting up an application server instance that has JBossTS transaction manager deployed within it, you may
- see various “error” messages in the console or log. For example 16:53:38,850 ERROR [STDERR] Message Listener
- Service: started, message listener jndi name activationcoordinator". These are for information purposes only and
- are not actual errors.
- </para>
- </note>
- </section>
-
-
- <section>
- <title>Configuring the transaction manager</title>
- <para>
- You can configure the Transaction Manager and related infrastructure by using three properties files:
- <filename>wscf.xml</filename>, <filename>wst.xml</filename>, and <filename>wstx.xml</filename>. Each file is
- located in the <filename>conf/</filename> directory. Both the demo application and the stand-alone module rely on
- them for configuration.
- </para>
- <para>
- For the most part the default values in these files are suitable. However, the
- <varname>ObjectStoreEnvironmentBean.objectStoreDir</varname> property, which determines the location of the
- persistent store used to record transaction state, should be modified to suit your environment. The default value
- is <literal>C:/temp/ObjectStore</literal>. For production environments this directory should reside on
- fault-tolerant media such as a RAID array.
- </para>
- <para>
- When an application uses a standalone coordinator, you must enable and modify two additional
- properties in <filename>wstx.xml</filename>. These properties are
- <varname>com.arjuna.mw.wst.coordinatorURL</varname> and <varname>com.arjuna.mw.wst.terminatorURL</varname>. They specify the
- URLs needed by client application to contact the standalone coordinator, and need to specify the correct hostname
- and port for the stand-alone server.
- </para>
- <para>
- JBossTS is extremely modular. To allow flexible deployment of individual components, the same property values
- sometimes need to appear in more than one configuration file. Except in special circumstances, maintain consistent
- values for properties that are defined in more than one file.
- </para>
-
- </section>
-
- <section>
- <title>Deploying the transaction manager</title>
- <para>
- The JBossTS XTS component consists of a number of <filename>.jar</filename> files containing the application’s
- class files, plus Web service (<filename>.war</filename>) files which expose the necessary services. These
- components are typically included in an application's Enterprise Archive (<filename>.ear</filename>) file during
- application development, as this simplifies deployment of the transaction infrastructure. For production, you can
- install the Transaction Manager as an application in its own right, allowing for centralized configuration and
- management at the server level, independent of specific applications. The demonstration application shipped with
- JBossTS provides a sample deployment descriptor illustrating how the Transaction Manager components can be
- included in an application.
- </para>
- <para>
- JBossTS 4.x uses fixed endpoints for its underlying protocol communication. Therefore, problems may arise if you
- deploy multiple applications using JBossTS to the same server concurrently. If you need to deploy several
- transactional applications in the same server, you must deploy the Transaction Manger as a separate application,
- rather than embedding it within the development of individual applications.
- </para>
- <para>
- The <filename>coordinator/</filename> directory in the JBossTS installation can assist in the configuration and
- deployment of a stand-alone transaction manager.
- </para>
- <procedure>
- <title>Using the <filename>coordinator/</filename> diretory to configure and deploy a stand-alone transaction manager</title>
- <step>
- <para>
- Install JBossTS 4.14.
- </para>
- </step>
- <step>
- <para>
- Use a separate application server installation for the coordinator. This installation can be on a separate
- machine. To set this up on JBoss Application Server, see <ulink
- url="http://www.yorku.ca/dkha/jboss/docs/MultipleInstances.htm" /> for more information.
- </para>
- </step>
- <step>
- <para>
- Install Ant 1.4 or later.
- </para>
- <warning>
- <para>
- A separate application server installation must be used, separate from the one that clients and services are
- deployed into, to prevent conflicts between the various JBossTS components.
- </para>
- </warning>
- </step>
- <step>
- <para>
- Edit the <filename>build.xml</filename> included in the <filename>coordinator/</filename> directory, to point
- to the application server installation where the transaction coordinator will be deployed and the location of
- the JBossTS installation. The files <filename>ws-c_jaxm_web-app.xml</filename> and
- <filename>ws-t_jaxm_web-app.xml</filename> in the <filename>dd/</filename> subdirectory of
- <filename>coordinator/</filename> are the deployment descriptors for the WS-C and WS-T
- <filename>war</filename> files. These files contain templated URLs. During the build phase, ant will
- substitute the hostname and port values you specify in the <filename>build.xml</filename> into these files.
- </para>
- </step>
- <step>
- <para>
- Run ant, with one of targets <systemitem>deploy-weblogic</systemitem>, <systemitem>deploy-jboss</systemitem>,
- or <systemitem>deploy-webmethods</systemitem>, to create and deploy a new coordinator into the correct
- application server installation.
- </para>
- </step>
- <step>
- <para>
- Finally, point your client at the required coordinator. To do this, generate the demo
- application. specifying the port and hostname of the coordinator.
- </para>
- </step>
- </procedure>
- </section>
-
- <section>
- <title>Deployment descriptors</title>
- <para>
- In general, changing the contents of the various deployment descriptors used by JBossTS is not necessary. However,
- if you do need to modify them they are all included in the coordinator module.
- </para>
- <para>
- Not all JBossTS components have ready access to the information in the deployment descriptors. Therefore, if you
- modify the JNDI names used by any of the WS-C or WS-T deployment descriptors, you may need to inform other JBossTS
- components at runtime, by setting an appropriate property in the <filename>wstx.xml</filename> configuration
- file.
- </para>
- <important>
- <para>
- You need to prefix each property in this table with the string <literal>com.arjuna.mw.wst.</literal>. The
- prefix has been removed for formatting reasons, and has been replaced by <literal>...</literal>.
- </para>
- </important>
- <table>
- <title>Deployment descriptor values and properties</title>
- <tgroup cols="2">
- <thead>
- <row>
- <entry>JNDI Name</entry>
- <entry>Property</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Activationrequester</entry>
- <entry>...at.activationrequester</entry>
- </row>
- <row>
- <entry>Activationcoordinator</entry>
- <entry>...at.activationcoordinator</entry>
- </row>
- <row>
- <entry>Completionparticipant</entry>
- <entry>...at.completionparticipant</entry>
- </row>
- <row>
- <entry>Registrationrequester</entry>
- <entry>...at.registrationrequester</entry>
- </row>
- <row>
- <entry>durable2pcdispatcher</entry>
- <entry>...at.durable2pcdispatcher</entry>
- </row>
- <row>
- <entry>durable2pcparticipant</entry>
- <entry>...at.durable2pcparticipant</entry>
- </row>
- <row>
- <entry>volatile2pcdispatcher</entry>
- <entry>...at.volatile2pcdispatcher</entry>
- </row>
- <row>
- <entry>volatile2pcparticipant</entry>
- <entry>...at.volatile2pcparticipant</entry>
- </row>
- <row>
- <entry>businessagreementwithparticipantcompletiondispatcher</entry>
- <entry>...ba.businessagreementwpcdispatcher</entry>
- </row>
- <row>
- <entry>businessagreementwithparticipantcompletionparticipant</entry>
- <entry>...ba.businessagreementwpcparticipant</entry>
- </row>
- <row>
- <entry>businessagreementwithcoordinatorcompletiondispatcher</entry>
- <entry>...ba.businessagreementwccdispatcher</entry>
- </row>
- <row>
- <entry>Businessagreementwithcoordinatorcompletionparticipant</entry>
- <entry>...ba.businessagreementwccparticipant</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </section>
-</chapter>
-
Deleted: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/publican-maven.cfg
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/publican-maven.cfg 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/publican-maven.cfg 2011-04-13 14:12:15 UTC (rev 36905)
@@ -1,8 +0,0 @@
-# Config::Simple 4.59
-# Fri Sep 24 12:42:32 2010
-
-xml_lang: en-US
-type: Book
-brand: jboss-community
-tmp_dir: target/publican/ArjunaJTS_Installation_And_Administration_Guide
-
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/publican.cfg
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Installation_And_Administration_Guide/publican.cfg 2011-04-13 13:08:25 UTC (rev 36902)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/administration_guide/publican.cfg 2011-04-13 14:12:15 UTC (rev 36905)
@@ -4,4 +4,4 @@
xml_lang: en-US
type: Book
brand: jboss-community
-tmp_dir: ../../build/ArjunaJTS_Installation_And_Administration_Guide
+tmp_dir: target/publican
Modified: labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Book_Info.xml
===================================================================
--- labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Book_Info.xml 2011-04-13 13:53:29 UTC (rev 36904)
+++ labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Book_Info.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -7,7 +7,7 @@
<title>Transactions XTS Administration And Development Guide</title>
<subtitle>Using the XTS Module of &PRODUCT; to provide Web Services Transactions</subtitle>
<productname>JBoss Transactions</productname>
- <productnumber>4.14.0</productnumber>
+ <productnumber>4.15.0</productnumber>
<edition>0</edition>
<pubsnumber>0</pubsnumber>
<abstract>
Modified: labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Transactions_XTS_Administration_And_Development_Guide.xml
===================================================================
--- labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Transactions_XTS_Administration_And_Development_Guide.xml 2011-04-13 13:53:29 UTC (rev 36904)
+++ labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Transactions_XTS_Administration_And_Development_Guide.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -16,6 +16,8 @@
<xi:include href="XTS_API.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Stand_Alone_Coordination.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Participant_Crash_Recovery.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Web_Service_Component.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Web_Service_Transaction_Management.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<index />
Added: labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Web_Service_Component.xml
===================================================================
--- labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Web_Service_Component.xml (rev 0)
+++ labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Web_Service_Component.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -0,0 +1,19 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Administration_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<chapter>
+ <title>Web Service Component</title>
+ <para>
+ To configure the demo application of the Web Services transactions component and standalone coordinator, edit the
+ appropriate <filename>build.xml</filename> file before running <command>ant</command>. Consult the trail map
+ accompanying these components for details.
+ </para>
+ <para>
+ When running within JBoss Application Server, it is recommended to use the <literal>all</literal> server
+ profile. Specify the profile with the <parameter>-c</parameter> switch: <command>run.sh -c all</command> in Linux,
+ or <command>run.bat -c all</command> in Microsoft Windows.
+ </para>
+</chapter>
+
Added: labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Web_Service_Transaction_Management.xml
===================================================================
--- labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Web_Service_Transaction_Management.xml (rev 0)
+++ labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Administration_And_Development_Guide/en-US/Web_Service_Transaction_Management.xml 2011-04-13 14:12:15 UTC (rev 36905)
@@ -0,0 +1,219 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Administration_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<chapter>
+ <title>Web Service Transaction Service (XTS) Management</title>
+ <para>
+ The basic building blocks of a transactional Web Services application include the application itself, the Web
+ services that the application consumes, the Transaction Manager, and the transaction participants which support
+ those Web services. Although it is likely that different developers will be responsible for each piece, the concepts
+ are presented here so that you can see the whole picture. Often, developers produce services, or applications that
+ consume services, and system administrators run the transaction-management infrastructure.
+ </para>
+
+ <section>
+ <title>Transaction manager overview</title>
+ <para>
+ The transaction manager is a Web service which coordinates JBossTS transactions. It is the only software component
+ in JBossTS that is designed to be run directly as a network service, rather than to support end-user code. The
+ transaction manager runs as a JAXM request/response Web service.
+ </para>
+ <note>
+ <para>
+ When starting up an application server instance that has JBossTS transaction manager deployed within it, you may
+ see various “error” messages in the console or log. For example 16:53:38,850 ERROR [STDERR] Message Listener
+ Service: started, message listener jndi name activationcoordinator". These are for information purposes only and
+ are not actual errors.
+ </para>
+ </note>
+ </section>
+
+
+ <section>
+ <title>Configuring the transaction manager</title>
+ <para>
+ You can configure the Transaction Manager and related infrastructure by using three properties files:
+ <filename>wscf.xml</filename>, <filename>wst.xml</filename>, and <filename>wstx.xml</filename>. Each file is
+ located in the <filename>conf/</filename> directory. Both the demo application and the stand-alone module rely on
+ them for configuration.
+ </para>
+ <para>
+ For the most part the default values in these files are suitable. However, the
+ <varname>ObjectStoreEnvironmentBean.objectStoreDir</varname> property, which determines the location of the
+ persistent store used to record transaction state, should be modified to suit your environment. The default value
+ is <literal>C:/temp/ObjectStore</literal>. For production environments this directory should reside on
+ fault-tolerant media such as a RAID array.
+ </para>
+ <para>
+ When an application uses a standalone coordinator, you must enable and modify two additional
+ properties in <filename>wstx.xml</filename>. These properties are
+ <varname>com.arjuna.mw.wst.coordinatorURL</varname> and <varname>com.arjuna.mw.wst.terminatorURL</varname>. They specify the
+ URLs needed by client application to contact the standalone coordinator, and need to specify the correct hostname
+ and port for the stand-alone server.
+ </para>
+ <para>
+ JBossTS is extremely modular. To allow flexible deployment of individual components, the same property values
+ sometimes need to appear in more than one configuration file. Except in special circumstances, maintain consistent
+ values for properties that are defined in more than one file.
+ </para>
+
+ </section>
+
+ <section>
+ <title>Deploying the transaction manager</title>
+ <para>
+ The JBossTS XTS component consists of a number of <filename>.jar</filename> files containing the application’s
+ class files, plus Web service (<filename>.war</filename>) files which expose the necessary services. These
+ components are typically included in an application's Enterprise Archive (<filename>.ear</filename>) file during
+ application development, as this simplifies deployment of the transaction infrastructure. For production, you can
+ install the Transaction Manager as an application in its own right, allowing for centralized configuration and
+ management at the server level, independent of specific applications. The demonstration application shipped with
+ JBossTS provides a sample deployment descriptor illustrating how the Transaction Manager components can be
+ included in an application.
+ </para>
+ <para>
+ JBossTS 4.x uses fixed endpoints for its underlying protocol communication. Therefore, problems may arise if you
+ deploy multiple applications using JBossTS to the same server concurrently. If you need to deploy several
+ transactional applications in the same server, you must deploy the Transaction Manger as a separate application,
+ rather than embedding it within the development of individual applications.
+ </para>
+ <para>
+ The <filename>coordinator/</filename> directory in the JBossTS installation can assist in the configuration and
+ deployment of a stand-alone transaction manager.
+ </para>
+ <procedure>
+ <title>Using the <filename>coordinator/</filename> diretory to configure and deploy a stand-alone transaction manager</title>
+ <step>
+ <para>
+ Install JBossTS 4.15.
+ </para>
+ </step>
+ <step>
+ <para>
+ Use a separate application server installation for the coordinator. This installation can be on a separate
+ machine. To set this up on JBoss Application Server, see <ulink
+ url="http://www.yorku.ca/dkha/jboss/docs/MultipleInstances.htm" /> for more information.
+ </para>
+ </step>
+ <step>
+ <para>
+ Install Ant 1.4 or later.
+ </para>
+ <warning>
+ <para>
+ A separate application server installation must be used, separate from the one that clients and services are
+ deployed into, to prevent conflicts between the various JBossTS components.
+ </para>
+ </warning>
+ </step>
+ <step>
+ <para>
+ Edit the <filename>build.xml</filename> included in the <filename>coordinator/</filename> directory, to point
+ to the application server installation where the transaction coordinator will be deployed and the location of
+ the JBossTS installation. The files <filename>ws-c_jaxm_web-app.xml</filename> and
+ <filename>ws-t_jaxm_web-app.xml</filename> in the <filename>dd/</filename> subdirectory of
+ <filename>coordinator/</filename> are the deployment descriptors for the WS-C and WS-T
+ <filename>war</filename> files. These files contain templated URLs. During the build phase, ant will
+ substitute the hostname and port values you specify in the <filename>build.xml</filename> into these files.
+ </para>
+ </step>
+ <step>
+ <para>
+ Run ant, with one of targets <systemitem>deploy-weblogic</systemitem>, <systemitem>deploy-jboss</systemitem>,
+ or <systemitem>deploy-webmethods</systemitem>, to create and deploy a new coordinator into the correct
+ application server installation.
+ </para>
+ </step>
+ <step>
+ <para>
+ Finally, point your client at the required coordinator. To do this, generate the demo
+ application. specifying the port and hostname of the coordinator.
+ </para>
+ </step>
+ </procedure>
+ </section>
+
+ <section>
+ <title>Deployment descriptors</title>
+ <para>
+ In general, changing the contents of the various deployment descriptors used by JBossTS is not necessary. However,
+ if you do need to modify them they are all included in the coordinator module.
+ </para>
+ <para>
+ Not all JBossTS components have ready access to the information in the deployment descriptors. Therefore, if you
+ modify the JNDI names used by any of the WS-C or WS-T deployment descriptors, you may need to inform other JBossTS
+ components at runtime, by setting an appropriate property in the <filename>wstx.xml</filename> configuration
+ file.
+ </para>
+ <important>
+ <para>
+ You need to prefix each property in this table with the string <literal>com.arjuna.mw.wst.</literal>. The
+ prefix has been removed for formatting reasons, and has been replaced by <literal>...</literal>.
+ </para>
+ </important>
+ <table>
+ <title>Deployment descriptor values and properties</title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>JNDI Name</entry>
+ <entry>Property</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Activationrequester</entry>
+ <entry>...at.activationrequester</entry>
+ </row>
+ <row>
+ <entry>Activationcoordinator</entry>
+ <entry>...at.activationcoordinator</entry>
+ </row>
+ <row>
+ <entry>Completionparticipant</entry>
+ <entry>...at.completionparticipant</entry>
+ </row>
+ <row>
+ <entry>Registrationrequester</entry>
+ <entry>...at.registrationrequester</entry>
+ </row>
+ <row>
+ <entry>durable2pcdispatcher</entry>
+ <entry>...at.durable2pcdispatcher</entry>
+ </row>
+ <row>
+ <entry>durable2pcparticipant</entry>
+ <entry>...at.durable2pcparticipant</entry>
+ </row>
+ <row>
+ <entry>volatile2pcdispatcher</entry>
+ <entry>...at.volatile2pcdispatcher</entry>
+ </row>
+ <row>
+ <entry>volatile2pcparticipant</entry>
+ <entry>...at.volatile2pcparticipant</entry>
+ </row>
+ <row>
+ <entry>businessagreementwithparticipantcompletiondispatcher</entry>
+ <entry>...ba.businessagreementwpcdispatcher</entry>
+ </row>
+ <row>
+ <entry>businessagreementwithparticipantcompletionparticipant</entry>
+ <entry>...ba.businessagreementwpcparticipant</entry>
+ </row>
+ <row>
+ <entry>businessagreementwithcoordinatorcompletiondispatcher</entry>
+ <entry>...ba.businessagreementwccdispatcher</entry>
+ </row>
+ <row>
+ <entry>Businessagreementwithcoordinatorcompletionparticipant</entry>
+ <entry>...ba.businessagreementwccparticipant</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+</chapter>
+
More information about the jboss-svn-commits
mailing list