[jboss-svn-commits] JBL Code SVN: r19032 - in labs/jbosstm/trunk: ArjunaJTS and 1 other directory.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Mon Mar 17 07:26:31 EDT 2008
Author: jhalliday
Date: 2008-03-17 07:26:31 -0400 (Mon, 17 Mar 2008)
New Revision: 19032
Modified:
labs/jbosstm/trunk/ArjunaJTA/INSTALL
labs/jbosstm/trunk/ArjunaJTS/INSTALL
Log:
Updated READMEs for 4.3.GA. JBTM-344.
Modified: labs/jbosstm/trunk/ArjunaJTA/INSTALL
===================================================================
--- labs/jbosstm/trunk/ArjunaJTA/INSTALL 2008-03-17 06:54:34 UTC (rev 19031)
+++ labs/jbosstm/trunk/ArjunaJTA/INSTALL 2008-03-17 11:26:31 UTC (rev 19032)
@@ -1,41 +1,40 @@
Installing JBossJTA into JBoss 4.0.3SP1, 4.0.4GA and 4.0.5GA
------------------------------------------------------------
-The installation of JBossJTA into JBoss AS is currently a manual process.
-We hope to release an installer in the near future that will automate this
-process.
+This version of JBossTS no longer supports these older
+JBossAS releases. You probably need JBossTS 4.2.3 instead.
-The following steps are required
+Installing JBossTS 4.3 into JBossAS 4.2
+------------------------------------------------------------
+
+Strating with the JBossAS 4.2 release, JBossTS JTA is the default
+transaction manager in JBossAS. For most usage there is no need to
+reinstall or upgrade the transaction manager. Indeed, we recommend
+you stick with the pre-installed version as this has received
+more extensive testing.
+
+Should you wish to update your JBossAS 4.2.x release to use
+JBossTS JTA 4.3 please take the following steps:
+
- download the tar or zip version of the application server
- extract the distribution into an installation directory
- copy the following jars from the JBossJTA installation into the
server/XXX/lib directory of the application server installation
+ overwriting the already present .jar files of the same name
- lib/jbossjta.jar
- lib/jbossjta-integration.jar
- lib/ext/jbossts-common.jar
- copy the following configuration file from the JBossJTA installation into
the server/XXX/conf directory of the application server installation
+ overwriting the existing version
- etc/jbossjta-properties.xml
- - edit the server/XXX/conf/jboss-service.xml file and replace the
- jboss:service=TransactionManager mbean declaration with the following
- <mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService"
- name="jboss:service=TransactionManager">
- <attribute name="TransactionTimeout">300</attribute>
- </mbean>
+Note that JBossTS 4.3 provides a JTA 1.1 implementation, whereas JBossAS
+4.2 ships the JTA 1.0.1b API files. You may therefore also need to copy
+the JTA 1.1 API into the application server's server/XXX/lib dir
+ - lib/ext/jta-1_1-classes.zip
-Application Server Library Modifications
-----------------------------------------
-
-The JBoss 4.0.3SP1, 4.0.4GA and 4.0.5GA application servers require some
-modified librarires before JBossJTA can be used as a replacement. These
-are detailed in the appropriate subdirectory of the jboss directory within
-this installation.
-
-No modifications are required if you are running a cumulative patch for
-JBoss 4.0.4GA.
-
-The application server will now be configured to use the JBossJTA transaction
-manager instead of the JBoss Transaction Manager.
+JBossTS 4.3 is the last JBossTS release that will support JBossAS 4.2.
+Future releases of JBossTS (4.4 onwards) will integrate with JBossAS 5.0 only.
\ No newline at end of file
Modified: labs/jbosstm/trunk/ArjunaJTS/INSTALL
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/INSTALL 2008-03-17 06:54:34 UTC (rev 19031)
+++ labs/jbosstm/trunk/ArjunaJTS/INSTALL 2008-03-17 11:26:31 UTC (rev 19032)
@@ -1,20 +1,20 @@
-Note to users of JBoss 4.0.3SP1, 4.0.4GA and 4.0.5GA:
+Installing JBossJTA into JBoss 4.0.3SP1, 4.0.4GA and 4.0.5GA
+------------------------------------------------------------
This version of JBossTS no longer supports these older
JBossAS releases. You probably need JBossTS 4.2.3 instead.
-Installing JBossTS 4.4 into JBossAS 4.2
+Installing JBossTS 4.3 into JBossAS 4.2 or JBossAS 5.0
------------------------------------------------------------
Starting with JBossAS 4.2, the application server ships with
JBossTS JTA as a default component. You do not need to take
any action if you want JTA support only.
+To change the JTA to the full JTS in JBossAS 4.2 or 5.0, follow these steps:
-To change the JTA to the full JTS in JBossAS 4.2, follow these steps:
-
- download the tar or zip version of the application server
- extract the distribution into an installation directory
@@ -70,9 +70,10 @@
<initializer>org.jboss.tm.iiop.TxServerClientInterceptorInitializer</initializer>
<!-- comment out to disable transaction demarcation over IIOP -->
<initializer>org.jboss.tm.iiop.TxServerInterceptorInitializer</initializer>
- - add the following lines
- <!-- JBoss TS interceptor -->
+ - add the following lines, according to the version of JBossAS you are running
+ <!-- JBoss TS interceptor. Use with AS 4.2 and AS 5.0 -->
<initializer>com.arjuna.ats.jts.orbspecific.jacorb.interceptors.interposition.InterpositionORBInitializerImpl</initializer>
+ <!-- RMI/IIOP tx context interceptor, use with AS 5.0 only, comment out in AS 4.2 -->
<initializer>com.arjuna.ats.jbossatx.jts.InboundTransactionCurrentInitializer</initializer>
For each deployment of JacORB, you will need to ensure that the jacorb.implname in the jacorb.properties
@@ -83,11 +84,25 @@
This may be necessary in cluster setups where the ObjectStore is shared, as
there should be only one recovery manager per ObjectStore.
+Note that JBossTS 4.3 provides a JTA 1.1 implementation, whereas JBossAS
+4.2 ships the JTA 1.0.1b API files. You may therefore also need to copy
+the JTA 1.1 API into the application server's server/XXX/lib dir
+ - lib/ext/jta-1_1-classes.zip
+
+Due to issues with statup ordering, of some versions of AS 5.0 you may need to
+move the mbeans in deploy/iiop-service.xml into conf/jboss-service.xml
+
+If building the JTS To AS integration code from source, you must build against
+a JBOSS_HOME for AS 5.0, even if you intend to run the resulting binaries on AS 4.2
+
Finally, note that starting with JBossAS 4.2, the application server binds to the
localhost address by default. This is inappropriate for distributed transactions,
so please ensure the server is bound to a alternative address.
+JBossTS 4.3 is the last JBossTS release that will support JBossAS 4.2.
+Future releases of JBossTS (4.4 onwards) will integrate with JBossAS 5.0 only.
+
Web Services Transactions
-------------------------
More information about the jboss-svn-commits
mailing list