[jboss-cvs] JBossAS SVN: r88099 - branches/Branch_5_x/jbossas/transactions.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri May 1 05:57:18 EDT 2009
Author: jhalliday
Date: 2009-05-01 05:57:18 -0400 (Fri, 01 May 2009)
New Revision: 88099
Modified:
branches/Branch_5_x/jbossas/transactions/README.txt
branches/Branch_5_x/jbossas/transactions/build.xml
Log:
Update docs and install script for optional transaction components. JBTM-6851
Modified: branches/Branch_5_x/jbossas/transactions/README.txt
===================================================================
--- branches/Branch_5_x/jbossas/transactions/README.txt 2009-05-01 09:55:23 UTC (rev 88098)
+++ branches/Branch_5_x/jbossas/transactions/README.txt 2009-05-01 09:57:18 UTC (rev 88099)
@@ -1,37 +1,21 @@
+JTS
+---
+
To remove the default JTA implementation of the transaction service and replace it with the JTS for
-full distributed transaction support, follow the steps below.
+full distributed transaction support, run 'ant jts' or follow the steps below.
-- Do not attempt to use a server with both the JTA and JTS .jar files or both the JTA and JTS config files present.
+- By default the transaction libraries are installed in JBOSS_HOME/common/lib and used by every server configuration.
+ Each server configuration has its own transaction config file, JBOSS_HOME/server/<config>/conf/jbossts-properties.xml
-- By default the JTA libraries are installed in JBOSS_HOME/common/lib and used by every server configuration.
- Each server configuration has its own JTA config file, JBOSS_HOME/server/<config>/conf/jbossjta-properties.xml
-
-- To replace the JTA with JTS for every server <config> dir (not recommended):
- delete JBOSS_HOME/common/lib/jbossjta.jar
- delete JBOSS_HOME/common/lib/jbossjta-integration.jar
- copy jbossjts.jar, jbossjts-integration.jar and jbossjts-jacorb.jar to JBOSS_HOME/common/lib
- delete the JBOSS_HOME/server/<config>/conf/jbossjta-properties files
- copy jbossjts-properties.xml to each of the JBOSS_HOME/server/<config>/conf directories
- Add jacorb to any server config that does not already contain it
- Follow the file editing steps below for each server config
-
- To replace the JTA with JTS for a single server <config> dir:
- copy JBOSS_HOME/common/lib/jbossjta.jar and JBOSS_HOME/common/lib/jbossjta-integration.jar to
- JBOSS_HOME/server/<config>/lib/ for each server you wish to continue using it with
- delete JBOSS_HOME/common/lib/jbossjta.jar
- delete JBOSS_HOME/common/lib/jbossjta-integration.jar
- copy jbossjts.jar, jbossjts-integration.jar and jbossjts-jacorb.jar to
- JBOSS_HOME/server/<config>/lib for each server you wish to use it with i.e. the one that don't have the JTA.
- For each server using the JTS, delete JBOSS_HOME/server/<config>/conf/jbossjta-properties.xml
- and copy jbossjts-properties.xml to JBOSS_HOME/server/<config>/conf/ instead.
- Follow the file editing steps below for each server config using the JTS.
+ For each server using the JTS, delete JBOSS_HOME/server/<config>/conf/jbossts-properties.xml
+ and copy jbossts-properties.xml from this dir to JBOSS_HOME/server/<config>/conf/ instead.
-
- complete the installation by making the following edits to the server configuration
(These are difficult to automate with ant and hence are manual steps for now)
- - edit the conf/jbossjts-properties.xml file and remove the
+ - edit the conf/jbossts-properties.xml file and remove the
recovery extension property containing the value
"com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule"
@@ -68,7 +52,7 @@
For each deployment of JacORB, you will need to ensure that the jacorb.implname in the jacorb.properties
file is unique.
-If running an external recovery manager, edit conf/jbossjts-properties.xml to remove
+If running an external recovery manager, edit conf/jbossts-properties.xml to remove
the recovery activator property named "com.arjuna.ats.arjuna.recovery.recoveryActivator_1".
This may be necessary in cluster setups where the ObjectStore is shared, as
there should be only one recovery manager per ObjectStore.
@@ -79,3 +63,24 @@
There is a short article on the JBoss wiki that describes some typical JTS
usage scenarios. It is available at the url https://www.jboss.org/community/docs/DOC-13179
+
+
+XTS (Web Services Transactions)
+-------------------------------
+
+Install XTS to the desired server by running 'ant xts' or following the steps below.
+
+- Unzip the jbossxts.sar file into a directory server/<config>/deploy/jbossxts.sar/
+
+Embedded Tools
+--------------
+
+WARNING: The tools are a prototype and unsupported component, aimed at providing diagnostic information
+regarding the status of transactions, particularly for crash recovery. The tools currently use swing, so are
+suitable only for use from the local host and not in remote or headless situations.
+
+Install the tools using 'ant tools' or by following the steps below.
+
+- Copy the jbossts-tools.jar file to server/<config>/deploy/
+
+The tools swing GUI can then be started from the server's JMX console.
Modified: branches/Branch_5_x/jbossas/transactions/build.xml
===================================================================
--- branches/Branch_5_x/jbossas/transactions/build.xml 2009-05-01 09:55:23 UTC (rev 88098)
+++ branches/Branch_5_x/jbossas/transactions/build.xml 2009-05-01 09:57:18 UTC (rev 88099)
@@ -15,45 +15,67 @@
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
MA 02110-1301, USA.
- (C) 2008,
+ (C) 2008, 2009
@author JBoss, a division of Red Hat.
-->
<!--
- Ant build script to mostly automate the installation of JBossTS JTS into JBossAS.
+ Ant build script to mostly automate the installation of JBossTS components into JBossAS.
@author Jonathan Halliday (jonathan.halliday at redhat.com), September 2008.
@author Ivo Studensky (istudens at redhat.com)
-->
-<project name="jts-install" default="install" basedir=".">
+<project name="jbossts-install" default="usage" basedir=".">
- <!-- Select which server the JTS will install into. Must have an ORB configured.
+ <!-- Select which server the JBossTS component will install into.
+ For JTS, must have an ORB configured.
+ For XTS, must have JBossWSNative configured.
Path relative to our location (docs/examples/transactions) -->
- <property name="jts.server.dir" value="../../../server/all"/>
+ <property name="target.server.dir" value="../../../server/all"/>
- <target name="install">
+ <target name="usage">
+ <echo message="Usage: 'ant jts' : installs JBossTS JTS (distributed JTA) component"/>
+ <echo message=" 'ant xts' : installs JBossTS XTS (Web Services Transactions) component"/>
+ <echo message=" 'ant tools' : installs the embedded transactions tools."/>
+ <echo message=" WARNING: tools are prototype and unsupported"/>
+ </target>
- <!-- rename the JTA properties file rather than deleting it,
+ <!-- install XTS into the designated server. We expand the .sar to make it easier to
+ reference individual .jar files in a user's classpath or edit the config files. -->
+ <target name="xts">
+ <mkdir dir="${target.server.dir}/deploy/jbossxts.sar"/>
+ <unzip src="jbossxts.sar" dest="${target.server.dir}/deploy/jbossxts.sar/"/>
+ </target>
+
+ <!-- deploy the embedded tools into the designated server -->
+ <target name="tools">
+ <copy file="jbossts-tools.sar" todir="${target.server.dir}/deploy/"/>
+ </target>
+
+ <!-- install the JTS into the designated server -->
+ <target name="jts">
+
+ <!-- rename the JTA version of the properties file rather than deleting it,
as it may have customizations we don't want to lose. -->
- <move file="${jts.server.dir}/conf/jbossts-properties.xml"
- tofile="${jts.server.dir}/conf/jbossts-properties-old-for-jta.xml"/>
+ <move file="${target.server.dir}/conf/jbossts-properties.xml"
+ tofile="${target.server.dir}/conf/jbossts-properties-old-for-jta.xml"/>
- <copy file="jbossts-properties.xml" todir="${jts.server.dir}/conf/"/>
+ <copy file="jbossts-properties.xml" todir="${target.server.dir}/conf/"/>
- <echo message="Transaction service libraries and configuration installed."/>
+ <echo message="Transaction service configuration file installed."/>
<!-- rewrite the config files for the server that is using JTS -->
- <antcall target="modify-config-files">
- <param name="server.dir" value="${jts.server.dir}"/>
+ <antcall target="modify-jts-config-files">
+ <param name="server.dir" value="${target.server.dir}"/>
</antcall>
- <echo message="JTS config files updated for ${jts.server.dir}"/>
+ <echo message="JBossAS config files updated to run JTS in config ${target.server.dir}"/>
</target>
- <target name="modify-config-files">
+ <target name="modify-jts-config-files">
<!--
- edit the conf/jbossjts-properties.xml file and remove the
+ edit the conf/jbossts-properties.xml file and remove the
recovery extension property containing the value
"com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule"
-->
@@ -64,7 +86,7 @@
<!--
- In deploy/transaction-beans.xml, update the TransactionManager class and dependencies as follows:
+ In deploy/transaction-jboss-beans.xml, update the TransactionManager class and dependencies as follows:
<bean name="TransactionManager" class="com.arjuna.ats.jbossatx.jts.TransactionManagerService">
...
<start>
More information about the jboss-cvs-commits
mailing list