diff --git a/ArjunaCore/docs/development_guide/en-US/About_This_Guide.xml b/ArjunaCore/docs/development_guide/en-US/About_This_Guide.xml index f58740b6..36d838c5 100644 --- a/ArjunaCore/docs/development_guide/en-US/About_This_Guide.xml +++ b/ArjunaCore/docs/development_guide/en-US/About_This_Guide.xml @@ -1,6 +1,6 @@ + %BOOK_ENTITIES; ]> diff --git a/ArjunaCore/docs/development_guide/en-US/Appendix_Object_Store_Implementations.xml b/ArjunaCore/docs/development_guide/en-US/Appendix_Object_Store_Implementations.xml index 30f072c9..0433d5cf 100644 --- a/ArjunaCore/docs/development_guide/en-US/Appendix_Object_Store_Implementations.xml +++ b/ArjunaCore/docs/development_guide/en-US/Appendix_Object_Store_Implementations.xml @@ -15,7 +15,7 @@ implementations and plugging into an application. - This release of JBoss Transaction Service contains several different implementations of a basic object store. Each + This release of &PRODUCT; contains several different implementations of a basic object store. Each serves a particular purpose and is generally optimized for that purpose. Each of the implementations implements the ObjectStoreAPI interface, which defines the minimum operations which must be provided for an object store implementation to be used by the Transaction Service. You can override the default @@ -28,9 +28,9 @@ - JBoss Transaction Service programmers do not usually need to interact with any of the object store implementations + &PRODUCT; programmers do not usually need to interact with any of the object store implementations directly, apart from possibly creating them in the first place. Even this is not necessary if the default store - type is used, since JBoss Transaction Service creates stores as necessary. All stores manipulate instances of the + type is used, since &PRODUCT; creates stores as necessary. All stores manipulate instances of the class ObjectState. These instances are named using a type (via the object's type() operation) and a Uid. @@ -82,7 +82,7 @@ - All of the stores have a common root directory that is determined when JBoss Transaction Service is + All of the stores have a common root directory that is determined when &PRODUCT; is configured. This directory name is automatically prepended to any store-specific root information. @@ -118,7 +118,7 @@ Since transactional objects are concurrency-controlled through LockManager, you do not need to impose additional locking at the file level. The basic ShadowingStore implementation handles - file-level locking. Therefore, the default object store implementation for JBoss Transaction Service, + file-level locking. Therefore, the default object store implementation for &PRODUCT;, ShadowNoFileLockStore, relies upon user-level locking. This enables it to provide better performance than the ShadowingStore implementation. diff --git a/ArjunaCore/docs/development_guide/en-US/ArjunaCore_Development_Guide.ent b/ArjunaCore/docs/development_guide/en-US/ArjunaCore_Development_Guide.ent index abbcf212..a3fb653d 100644 --- a/ArjunaCore/docs/development_guide/en-US/ArjunaCore_Development_Guide.ent +++ b/ArjunaCore/docs/development_guide/en-US/ArjunaCore_Development_Guide.ent @@ -1,4 +1,5 @@ - + - + + diff --git a/ArjunaCore/docs/development_guide/en-US/Book_Info.xml b/ArjunaCore/docs/development_guide/en-US/Book_Info.xml index 983d3bc6..ab08ed91 100644 --- a/ArjunaCore/docs/development_guide/en-US/Book_Info.xml +++ b/ArjunaCore/docs/development_guide/en-US/Book_Info.xml @@ -12,7 +12,7 @@ 0 - This guide is most relevant to engineers who are responsible for administering JBoss Transactions + This guide is most relevant to engineers who are responsible for administering &PRODUCT; installations. Although this guide is specifically intended for service developers, it will be useful to anyone who would like to gain an understanding of transactions and how they function. diff --git a/ArjunaCore/docs/development_guide/en-US/General_Transaction_Issues.xml b/ArjunaCore/docs/development_guide/en-US/General_Transaction_Issues.xml index 333a6539..77547b36 100644 --- a/ArjunaCore/docs/development_guide/en-US/General_Transaction_Issues.xml +++ b/ArjunaCore/docs/development_guide/en-US/General_Transaction_Issues.xml @@ -104,7 +104,7 @@ - Therefore, JBoss Transaction Service provides runtime options to enable possible threading optimizations. By setting the + Therefore, &PRODUCT; provides runtime options to enable possible threading optimizations. By setting the CoordinatorEnvironmentBean.asyncBeforeSynchronization environment variable to YES, during the beforeSynchronization phase a separate thread @@ -209,13 +209,13 @@ - Default timeout values for other JBoss Transaction Service components, such as JTS, may be different and you should consult the + Default timeout values for other &PRODUCT; components, such as JTS, may be different and you should consult the relevant documentation to be sure. When a top-level transaction is created with a non-zero timeout, it is subject to being rolled back if it has not - completed within the specified number of seconds. JBoss Transaction Service uses a separate reaper thread which + completed within the specified number of seconds. &PRODUCT; uses a separate reaper thread which monitors all locally created transactions, and forces them to roll back if their timeouts elapse. If the transaction cannot be rolled back at that point, the reaper will force it into a rollback-only state so that it will eventually be rolled back. @@ -238,7 +238,7 @@ If a value of 0 is specified for the timeout of a top-level transaction, or no timeout is - specified, then JBoss Transaction Service will not impose any timeout on the transaction, and the transaction will + specified, then &PRODUCT; will not impose any timeout on the transaction, and the transaction will be allowed to run indefinitely. This default timeout can be overridden by setting the CoordinatorEnvironmentBean.defaultTimeout property variable when using to the required timeout value in seconds, when using ArjunaCore, ArjunaJTA or ArjunaJTS. diff --git a/ArjunaCore/docs/development_guide/en-US/Overview.xml b/ArjunaCore/docs/development_guide/en-US/Overview.xml index 7ab94f3e..0de4e479 100644 --- a/ArjunaCore/docs/development_guide/en-US/Overview.xml +++ b/ArjunaCore/docs/development_guide/en-US/Overview.xml @@ -22,9 +22,9 @@ Stand-Alone Transaction Manager - Although JBoss Transaction Service can be embedded in various containers, such as JBoss Application Server, it - remains a stand-alone transaction manager as well. There are no dependencies between the core JBoss Transaction - Service and any container implementations. + Although &PRODUCT; can be embedded in various containers, such as &APPSERVER;, it + remains a stand-alone transaction manager as well. There are no dependencies between the core &PRODUCT; and any + container implementations. diff --git a/ArjunaCore/docs/development_guide/en-US/fallback_content/Legal_Notice.xml b/ArjunaCore/docs/development_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..a60284a0 100644 --- a/ArjunaCore/docs/development_guide/en-US/fallback_content/Legal_Notice.xml +++ b/ArjunaCore/docs/development_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/ArjunaCore/docs/failure_recovery_guide/en-US/About_This_Guide.xml b/ArjunaCore/docs/failure_recovery_guide/en-US/About_This_Guide.xml index 6e8f5894..9b84e544 100644 --- a/ArjunaCore/docs/failure_recovery_guide/en-US/About_This_Guide.xml +++ b/ArjunaCore/docs/failure_recovery_guide/en-US/About_This_Guide.xml @@ -1,24 +1,24 @@ + %BOOK_ENTITIES; ]> About This Guide - The Failure Recovery for TxCore and TXOJ contains information on how to use JBoss Transactions 4.10.0 failure recovery system when not + The Failure Recovery for TxCore and TXOJ contains information on how to use &PRODUCT; failure recovery system when not embedding it within an application server or using TXOJ.
Audience - This guide is most relevant to engineers who are responsible for administering JBoss Transactions 4.10.0 installations. + This guide is most relevant to engineers who are responsible for administering &PRODUCT; installations.
Prerequisites - You should have installed JBoss Transactions 4.10.0. The reader should be familiar with the main Failure Recovery Guide. + You should have installed &PRODUCT;. The reader should be familiar with the main Failure Recovery Guide.
diff --git a/ArjunaCore/docs/failure_recovery_guide/en-US/ArjunaCore_Failure_Recovery_Guide.ent b/ArjunaCore/docs/failure_recovery_guide/en-US/ArjunaCore_Failure_Recovery_Guide.ent index 8a341d0a..6c18bdd3 100644 --- a/ArjunaCore/docs/failure_recovery_guide/en-US/ArjunaCore_Failure_Recovery_Guide.ent +++ b/ArjunaCore/docs/failure_recovery_guide/en-US/ArjunaCore_Failure_Recovery_Guide.ent @@ -1,7 +1,6 @@ - + - - + - + diff --git a/ArjunaCore/docs/failure_recovery_guide/en-US/Author_Group.xml b/ArjunaCore/docs/failure_recovery_guide/en-US/Author_Group.xml index d3fda6f9..a038bd37 100644 --- a/ArjunaCore/docs/failure_recovery_guide/en-US/Author_Group.xml +++ b/ArjunaCore/docs/failure_recovery_guide/en-US/Author_Group.xml @@ -1,6 +1,6 @@ + ]> diff --git a/ArjunaCore/docs/failure_recovery_guide/en-US/Book_Info.xml b/ArjunaCore/docs/failure_recovery_guide/en-US/Book_Info.xml index 170ba653..5e280d35 100644 --- a/ArjunaCore/docs/failure_recovery_guide/en-US/Book_Info.xml +++ b/ArjunaCore/docs/failure_recovery_guide/en-US/Book_Info.xml @@ -1,6 +1,6 @@ + %BOOK_ENTITIES; ]> @@ -12,7 +12,7 @@ 0 - The ArjunaCore Failure Recovery Guide contains information on how to use JBoss Transaction Service to develop + The ArjunaCore Failure Recovery Guide contains information on how to use &PRODUCT; to develop applications that use transaction technology to manage business processes. diff --git a/ArjunaCore/docs/failure_recovery_guide/en-US/Further_failure_recovery.xml b/ArjunaCore/docs/failure_recovery_guide/en-US/Further_failure_recovery.xml index 5fd7dc13..7facdd5d 100644 --- a/ArjunaCore/docs/failure_recovery_guide/en-US/Further_failure_recovery.xml +++ b/ArjunaCore/docs/failure_recovery_guide/en-US/Further_failure_recovery.xml @@ -1,10 +1,11 @@ + +%BOOK_ENTITIES; ]> Introduction - In this chapter we shall cover information on failure recovery that is specific to TxCore, TXOJ or using JBossTS outside the scope of a + In this chapter we shall cover information on failure recovery that is specific to TxCore, TXOJ or using &PRODUCT; outside the scope of a supported application server.
Embedding the Recovery Manager @@ -27,7 +28,7 @@
Additional Recovery Module Classes - JBossTS provides a set of recovery modules that are responsible to manage recovery according to the nature of the participant and its + &PRODUCT; provides a set of recovery modules that are responsible to manage recovery according to the nature of the participant and its position in a transactional tree. The provided classes over and above the ones covered elsewhere (that all implements the RecoveryModule interface) are: @@ -40,7 +41,7 @@
Understanding Recovery Modules - The failure recovery subsystem of JBossTS will ensure that results of a transaction are applied consistently to all resources affected + The failure recovery subsystem of &PRODUCT; 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 @@ -61,8 +62,8 @@ resources, an attempt to activate the Transactional Object (as when trying to get a lock) will fail.
The Recovery Manager - The failure recovery subsystem of JBossTS requires that the stand-alone Recovery Manager process be running for each ObjectStore - (typically one for each node on the network that is running JBossTS applications). The RecoveryManager file is located in the package + The failure recovery subsystem of &PRODUCT; requires that the stand-alone Recovery Manager process be running for each ObjectStore + (typically one for each node on the network that is running &PRODUCT; applications). The RecoveryManager file is located in the package com.arjuna.ats.arjuna.recovery.RecoveryManager. To start the Recovery Manager issue the following command: java com.arjuna.ats.arjuna.recovery.RecoveryManager @@ -138,10 +139,10 @@ the original process to see if they are still in progress - In previous versions of JBossTS there was no contact mechanism, and the backoff period had to be long enough to avoid catching + In previous versions of &PRODUCT; there was no contact mechanism, and the backoff period had to be long enough to avoid catching transactions in flight at all. From 3.0, there is no such risk. - Two recovery modules (implementations of the com.arjuna.ats.arjuna.recovery.RecoveryModule interface) are supplied with JBossTS, + Two recovery modules (implementations of the com.arjuna.ats.arjuna.recovery.RecoveryModule interface) are supplied with &PRODUCT;, supporting 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 RecoveryEnvironmentBean.recoveryExtensions. These will be invoked on each pass of the periodic recovery in the sort-order of the property @@ -176,13 +177,13 @@ absolute value) The kinds of item that are scanned for expiry are: - TransactionStatusManager items: one of these is created by every application process that uses JBossTS – they contain the information + TransactionStatusManager items: one of these is created by every application process that uses &PRODUCT; – they contain the information that allows the RecoveryManager to determine if the process that initiated the transaction is still alive, and what the transaction status is. The expiry time for these is set by the property com.arjuna.ats.arjuna.recovery.transactionStatusManagerExpiryTime (in hours – default is 12, zero - means never expire). The expiry time should be greater than the lifetime of any single JBossTS-using process. + means never expire). The expiry time should be greater than the lifetime of any single &PRODUCT;-using process. The Expiry Scanner properties for these are: Recovery Environment Bean XML @@ -207,7 +208,7 @@ In order to recover from failure, we have seen that the Recovery Manager contacts recovery modules by invoking periodically the methods periodicWorkFirstPass and periodicWorkSecondPass. Each Recovery Module is then able to manage recovery according the type of resources that need - to be recovered. The JBoss Transaction product is shipped with a set of recovery modules (TOReceveryModule, XARecoveryModule…), but it is + to be recovered. The &PRODUCT; product is shipped with a set of recovery modules (TOReceveryModule, XARecoveryModule…), but it is possible for a user to define its own recovery module that fit his application. The following basic example illustrates the steps needed to build such recovery module
@@ -271,7 +272,7 @@ Once started, the Recovery Manager will automatically load the listed Recovery modules. - The source of the code can be retrieved under the trailmap directory of the JBossTS installation. + The source of the code can be retrieved under the trailmap directory of the &PRODUCT; installation.
diff --git a/ArjunaCore/docs/failure_recovery_guide/en-US/Preface.xml b/ArjunaCore/docs/failure_recovery_guide/en-US/Preface.xml index 6a6b8fc7..e6004e89 100644 --- a/ArjunaCore/docs/failure_recovery_guide/en-US/Preface.xml +++ b/ArjunaCore/docs/failure_recovery_guide/en-US/Preface.xml @@ -1,6 +1,6 @@ + ]> Preface diff --git a/ArjunaCore/docs/failure_recovery_guide/en-US/Revision_History.xml b/ArjunaCore/docs/failure_recovery_guide/en-US/Revision_History.xml index 1cbb179d..d35a0459 100644 --- a/ArjunaCore/docs/failure_recovery_guide/en-US/Revision_History.xml +++ b/ArjunaCore/docs/failure_recovery_guide/en-US/Revision_History.xml @@ -1,13 +1,7 @@ - - - - - - -]> + +]> Revision History diff --git a/ArjunaCore/docs/failure_recovery_guide/en-US/fallback_content/Legal_Notice.xml b/ArjunaCore/docs/failure_recovery_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..6d4489a6 100644 --- a/ArjunaCore/docs/failure_recovery_guide/en-US/fallback_content/Legal_Notice.xml +++ b/ArjunaCore/docs/failure_recovery_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/ArjunaJTA/docs/administration_guide/en-US/Book_Info.xml b/ArjunaJTA/docs/administration_guide/en-US/Book_Info.xml index d1539817..a51aa89e 100644 --- a/ArjunaJTA/docs/administration_guide/en-US/Book_Info.xml +++ b/ArjunaJTA/docs/administration_guide/en-US/Book_Info.xml @@ -4,11 +4,11 @@ %BOOK_ENTITIES; ]> - JBossJTA Administration Guide - Administration of the &PRODUCT; toolkit, which implements the JTA API in the &PRODUCT; + &PRODUCT; Administration Guide + Administration of the &PRODUCT; toolkit, which implements the JTA API in the &PARENT_PRODUCT; Transaction Service - JBossJTA - 4.15.1 + &PRODUCT; + &VERSION; 1 1 diff --git a/ArjunaJTA/docs/development_guide/en-US/JBossJTA_Development_Guide.ent b/ArjunaJTA/docs/development_guide/en-US/JBossJTA_Development_Guide.ent index b068e373..7adc8e6c 100644 --- a/ArjunaJTA/docs/development_guide/en-US/JBossJTA_Development_Guide.ent +++ b/ArjunaJTA/docs/development_guide/en-US/JBossJTA_Development_Guide.ent @@ -1,4 +1,8 @@ - + + + + - + + diff --git a/ArjunaJTA/docs/development_guide/en-US/JDBC.xml b/ArjunaJTA/docs/development_guide/en-US/JDBC.xml index f7ae2e76..8700077b 100644 --- a/ArjunaJTA/docs/development_guide/en-US/JDBC.xml +++ b/ArjunaJTA/docs/development_guide/en-US/JDBC.xml @@ -11,12 +11,12 @@ &PRODUCT; supports construction of both local and distributed transactional applications which access databases using the JDBC APIs. JDBC supports two-phase commit of transactions, and is similar to the XA X/Open - standard. JBossTS provides JDBC support in package com.arjuna.ats.jdbc. A list of the tested - drivers is available from the JBossTS website. + standard. &PARENT_PRODUCT; provides JDBC support in package com.arjuna.ats.jdbc. A list of the tested + drivers is available from the &PARENT_PRODUCT; website. Only use the transactional JDBC support provided in package com.arjuna.ats.jdbc when you are - using JBossTS outside of an application server, such as JBoss Application Server, or another container. Otherwise, + using &PARENT_PRODUCT; outside of an application server, such as &APPSERVER;, or another container. Otherwise, use the JDBC support provided by your application server or container.
diff --git a/ArjunaJTA/docs/development_guide/en-US/Preface.xml b/ArjunaJTA/docs/development_guide/en-US/Preface.xml index a95cd6b2..bedad1de 100644 --- a/ArjunaJTA/docs/development_guide/en-US/Preface.xml +++ b/ArjunaJTA/docs/development_guide/en-US/Preface.xml @@ -9,9 +9,9 @@
Prerequisites - ArjunaTA works in conjunction with ArjunaCore. In addition to the documentation here, consult the ArjunaCore - documentation, which ships as part of ArjunaCore and is also available on the JBoss Transaction Service website - at . + &PRODUCT; works in conjunction with ArjunaCore. In addition to the documentation here, consult the ArjunaCore + documentation, which ships as part of ArjunaCore and is also available on the &PARENT_PRODUCT; website + at .
diff --git a/ArjunaJTA/docs/development_guide/en-US/Revision_History.xml b/ArjunaJTA/docs/development_guide/en-US/Revision_History.xml index 2e981b85..ca304049 100644 --- a/ArjunaJTA/docs/development_guide/en-US/Revision_History.xml +++ b/ArjunaJTA/docs/development_guide/en-US/Revision_History.xml @@ -35,6 +35,20 @@ + + 2 + Thu Jan 16 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + diff --git a/ArjunaJTA/docs/development_guide/en-US/Using_JBossTA_In_Application_Servers.xml b/ArjunaJTA/docs/development_guide/en-US/Using_JBossTA_In_Application_Servers.xml index 97ce4bdd..24aeed78 100644 --- a/ArjunaJTA/docs/development_guide/en-US/Using_JBossTA_In_Application_Servers.xml +++ b/ArjunaJTA/docs/development_guide/en-US/Using_JBossTA_In_Application_Servers.xml @@ -6,29 +6,29 @@ Using &PRODUCT; in application servers - JBoss Application Server is discussed here. Refer to the documentation for your application server for differences. + &APPSERVER; is discussed here. Refer to the documentation for your application server for differences.
Configuration - When &PRODUCT; runs embedded in JBoss Application Server, the transaction system is configured primarily through the - transaction-jboss-beans.xml deployment descriptor, which overrides properties read from the - default properties file embedded in the .jar file. + When &PRODUCT; runs embedded in &APPSERVER;, the transaction subsystem is configured primarily through the + jboss-cli configuration tool, which overrides properties read from the default properties + file mbedded in the .jar file. Common configuration attributes - CoordinatorEnvironmentBean.defaultTimeout + default-timeout - The default transaction timeout to be used for new transactions. Specified as an integer in seconds. + The default transaction timeout to be used for new transactions. Specified as an integer in seconds. - CoordinatorEnvironmentBean.enableStatistics + enable-statistics This determines whether or not the transaction service should gather statistical information. This @@ -41,19 +41,19 @@
- See the transaction-jboss-beans.xml file and the JBoss Application Server administration and - configuration guide for further information. + See the jboss-cli tool and the &APPSERVER; administration and configuration guide for further + information.
Logging - To make JBossTS logging semantically consistent with JBoss Application Server, the + To make &PARENT_PRODUCT; logging semantically consistent with &APPSERVER;, the TransactionManagerService modifies the level of some log messages, by overriding the value of the LoggingEnvironmentBean.loggingFactory property in the jbossts-properties.xml file. Therefore, the value of this property has no effect on the - logging behavior when running embedded in JBoss Application Server. By forcing use of the log4j_releveler + logging behavior when running embedded in &APPSERVER;. By forcing use of the log4j_releveler logger, the TransactionManagerService changes the level of all INFO level messages in the transaction code to DEBUG. Therefore, these messages do not appear in log files if the filter level is INFO. All other log messages behave @@ -65,16 +65,16 @@ The services The TransactionManager bean provides transaction management services to other - components in JBoss Application Server. There are two different version of this bean and they requires different configuration. Take - care to select the transaction-jboss-beans.xml suitable for your needs (local JTA or JTS). + components in &APPSERVER;. There are two different version of this bean and they requires different configuration. + Use jboss-cli to select JTA or JTS mode.
Ensuring transactional context is propagated to the server - You can coordinate transactions from a coordinator which is not located within the JBoss server - , such as when using transactions created by an external OTS server. To ensure the transaction context is propagated via + You can coordinate transactions from a coordinator which is not located within the &APPSERVER;, + such as when using transactions created by an external OTS server. To ensure the transaction context is propagated via JRMP invocations to the server, the transaction propagation context factory needs to be explicitly set for the JRMP invoker proxy. This is done as follows: diff --git a/ArjunaJTA/docs/development_guide/en-US/fallback_content/Legal_Notice.xml b/ArjunaJTA/docs/development_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..33757151 100644 --- a/ArjunaJTA/docs/development_guide/en-US/fallback_content/Legal_Notice.xml +++ b/ArjunaJTA/docs/development_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/ArjunaJTA/docs/installation_guide/en-US/Book_Info.xml b/ArjunaJTA/docs/installation_guide/en-US/Book_Info.xml index 3ead3da9..a1236e1a 100644 --- a/ArjunaJTA/docs/installation_guide/en-US/Book_Info.xml +++ b/ArjunaJTA/docs/installation_guide/en-US/Book_Info.xml @@ -4,10 +4,10 @@ %BOOK_ENTITIES; ]> - JBossJTA Installation Guide - Stand-alone Installation Guide for JBossJTA - JBossJTA - 4.15.1 + &PRODUCT; Installation Guide + Stand-alone Installation Guide for &PRODUCT; + &PRODUCT; + &VERSION; 1 1 diff --git a/ArjunaJTA/docs/quick_start_guide/en-US/Preface.xml b/ArjunaJTA/docs/quick_start_guide/en-US/Preface.xml index 582068f2..dcd80e54 100644 --- a/ArjunaJTA/docs/quick_start_guide/en-US/Preface.xml +++ b/ArjunaJTA/docs/quick_start_guide/en-US/Preface.xml @@ -10,11 +10,11 @@ Prerequisites &PRODUCT; - works in conjunction with the rest of the JBoss Transactions suite. In addition to the documentation here, consult the &PRODUCT; + works in conjunction with the rest of the &PARENT_PRODUCT; suite. In addition to the documentation here, consult the &PRODUCT; documentation, which ships as part of &PRODUCT; - and is also available on the JBoss Transaction Service website + and is also available on the &PARENT_PRODUCT; website at - + .
diff --git a/ArjunaJTA/docs/quick_start_guide/en-US/Quick_Start_to_JTA.xml b/ArjunaJTA/docs/quick_start_guide/en-US/Quick_Start_to_JTA.xml index 505b9f85..89fe2427 100644 --- a/ArjunaJTA/docs/quick_start_guide/en-US/Quick_Start_to_JTA.xml +++ b/ArjunaJTA/docs/quick_start_guide/en-US/Quick_Start_to_JTA.xml @@ -1,6 +1,7 @@ +%BOOK_ENTITIES; ]> Quick Start to JTA @@ -14,7 +15,7 @@ The key Java packages (and corresponding jar files) for writing basic JTA applications are: - com.arjuna.ats.jts: this package contains the JBossTS implementations of the JTS and JTA. + com.arjuna.ats.jts: this package contains the &PARENT_PRODUCT; implementations of the JTS and JTA. com.arjuna.ats.jta: this package contains local and remote JTA implementation support. @@ -23,8 +24,8 @@ com.arjuna.ats.jdbc: this package contains transactional JDBC support. - All of these packages appear in the lib directory of the JBossTS installation, and should be added to the programmer’s CLASSPATH. - In order to fully utilize all of the facilities available within JBossTS, it will be necessary to add some additional jar files to your + All of these packages appear in the lib directory of the &PARENT_PRODUCT; installation, and should be added to the programmer’s CLASSPATH. + In order to fully utilize all of the facilities available within &PARENT_PRODUCT;, it will be necessary to add some additional jar files to your classpath. See bin/setup-env.sh or bin\setup-env.bat for details.
@@ -121,7 +122,7 @@
JDBC and Transactions - ArjunaJTS supports the construction of both local and distributed transactional applications which access databases using the JDBC APIs. + &PARENT_PRODUCT; JTS supports the construction of both local and distributed transactional applications which access databases using the JDBC APIs. JDBC supports two-phase commit of transactions, and is similar to the XA X/Open standard. The JDBC support is found in the com.arjuna.ats.jdbc package. The ArjunaJTS approach to incorporating JDBC connections within transactions is to provide transactional JDBC drivers through which all diff --git a/ArjunaJTA/docs/quick_start_guide/en-US/Revision_History.xml b/ArjunaJTA/docs/quick_start_guide/en-US/Revision_History.xml index f4cb7bd6..3ee4f39e 100644 --- a/ArjunaJTA/docs/quick_start_guide/en-US/Revision_History.xml +++ b/ArjunaJTA/docs/quick_start_guide/en-US/Revision_History.xml @@ -21,6 +21,20 @@ + + 2 + Thu Jan 16 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + diff --git a/ArjunaJTA/docs/quick_start_guide/en-US/fallback_content/Legal_Notice.xml b/ArjunaJTA/docs/quick_start_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..f6286755 100644 --- a/ArjunaJTA/docs/quick_start_guide/en-US/fallback_content/Legal_Notice.xml +++ b/ArjunaJTA/docs/quick_start_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/ArjunaJTS/docs/administration_guide/en-US/Book_Info.xml b/ArjunaJTS/docs/administration_guide/en-US/Book_Info.xml index b7fea364..8fb0425e 100644 --- a/ArjunaJTS/docs/administration_guide/en-US/Book_Info.xml +++ b/ArjunaJTS/docs/administration_guide/en-US/Book_Info.xml @@ -4,10 +4,10 @@ %BOOK_ENTITIES; ]> - JBossJTS Administration Guide - Administration of the JBossJTS toolkit, used as part of the Transaction Service - JBossJTS - 4.15.1 + &PRODUCT; Administration Guide + Administration of the &PRODUCT; toolkit, used as part of the Transaction Service + &PRODUCT; + &VERSION; 1 1 Current locates the factory in a manner specific to the ORB: using the name service, through resolve_initial_references, or via the CosServices.cfg file. The CosServices.cfg file is similar to resolve_initial_references, and is automatically updated when the transaction factory is started on a particular machine. Copy the file to each - JBossTS instance which needs to share the same transaction factory. + &PARENT_PRODUCT; instance which needs to share the same transaction factory. If you do not need subtransaction support, set the OTS_SUPPORT_SUBTRANSACTIONS property @@ -1363,15 +1363,15 @@
- JBossTS specifics + &PARENT_PRODUCT; specifics A SubtransactionAwareResource which raises an exception to the commitment of a transaction may create inconsistencies within the transaction if other SubtransactionAwareResources think the transaction committed. To prevent this possibility - of inconsistency, JBossTS forces the enclosing transaction to abort if an exception is raised. + of inconsistency, &PARENT_PRODUCT; forces the enclosing transaction to abort if an exception is raised. - JBossTS also provides extended subtransaction aware resources to overcome this, and other problems. See Section + &PARENT_PRODUCT; also provides extended subtransaction aware resources to overcome this, and other problems. See Section for further details. @@ -1425,7 +1425,7 @@
- JBossTS specifics + &PARENT_PRODUCT; specifics Synchronizations must be called before the top-level transaction commit protocol starts, and after it completes. By default, if the transaction is instructed to roll back, the Synchronizations associated with the @@ -1556,12 +1556,12 @@ In a single-address space application, transaction contexts are implicitly shared between clients and objects, regardless of whether or not the objects support the TransactionalObject interface. To preserve distribution transparency, where implicit transaction propagation is supported, you can - direct JBossTS to always propagate transaction contexts to objects. The default is only to propagate if the object + direct &PARENT_PRODUCT; to always propagate transaction contexts to objects. The default is only to propagate if the object is a TransactionalObject. Set the OTS_ALWAYS_PROPAGATE_CONTEXT property variable to NO to override this behavior. - By default, JBossTS does not require objects which support the TransactionalObject + By default, &PARENT_PRODUCT; does not require objects which support the TransactionalObject interface to invoked within the scope of a transaction. The object determines whether it should be invoked within a transaction. If so, it must throw the TransactionRequired exception. Override this default by setting the OTS_NEED_TRAN_CONTEXT shell environment variable to @@ -1604,7 +1604,7 @@ participate in the commit protocol. Interposed coordinators form a tree structure with their parent coordinators. - To use interposition, ensure that JBossTS is correctly initialized before creating objects. Also, the client and + To use interposition, ensure that &PARENT_PRODUCT; is correctly initialized before creating objects. Also, the client and server must both use interposition. Your ORB must support filters or interceptors, or the CosTSPortability interface, since interposition requires the use of implicit transaction propagation. To use interposition, set the OTS_CONTEXT_PROP_MODE property variable @@ -1612,7 +1612,7 @@ - Interposition is not required if you use the JBossTS advanced API. + Interposition is not required if you use the &PARENT_PRODUCT; advanced API.
@@ -1753,9 +1753,9 @@
- JBossTS specifics + &PARENT_PRODUCT; specifics - Where support from the ORB is available, JBossTS supports X/Open checked transaction behavior. However, unless + Where support from the ORB is available, &PARENT_PRODUCT; supports X/Open checked transaction behavior. However, unless the OTS_CHECKED_TRANSACTIONS property variable is set to YES, checked transactions are disabled. This is the default setting. @@ -1768,10 +1768,10 @@ In a multi-threaded application, multiple threads may be associated with a transaction during its lifetime, sharing the context. In addition, if one thread terminates a transaction, other threads may still be active within it. In a distributed environment, it can be difficult to guarantee that all threads have finished with a - transaction when it terminates. By default, JBossTS issues a warning if a thread terminates a transaction when + transaction when it terminates. By default, &PARENT_PRODUCT; issues a warning if a thread terminates a transaction when other threads are still active within it, but allow the transaction termination to continue. You can choose to block the thread which is terminating the transaction until all other threads have disassociated themselves from - its context, or use other methods to solve the problem. JBossTS provides the + its context, or use other methods to solve the problem. &PARENT_PRODUCT; provides the com.arjuna.ats.arjuna.coordinator.CheckedAction class, which allows you to override the thread and transaction termination policy. Each transaction has an instance of this class associated with it, and you can implement the class on a per-transaction basis. @@ -1830,7 +1830,7 @@
- Summary of JBossTS implementation decisions + Summary of &PARENT_PRODUCT; implementation decisions @@ -1855,15 +1855,15 @@ - If you try to commit a transaction when there are still active subtransactions within it, JBossTS rolls back + If you try to commit a transaction when there are still active subtransactions within it, &PARENT_PRODUCT; rolls back the parent and the subtransactions. - JBossTS includes full support for nested transactions. However, if a resource raises an exception to the + &PARENT_PRODUCT; includes full support for nested transactions. However, if a resource raises an exception to the commitment of a subtransaction after other resources have previously been told that the transaction committed, - JBossTS forces the enclosing transaction to abort. This guarantees that all resources used within the + &PARENT_PRODUCT; forces the enclosing transaction to abort. This guarantees that all resources used within the subtransaction are returned to a consistent state. You can disable support for subtransactions by setting the OTS_SUPPORT_SUBTRANSACTIONS variable to NO. diff --git a/ArjunaJTS/docs/development_guide/en-US/Overview.xml b/ArjunaJTS/docs/development_guide/en-US/Overview.xml index 6e4e50fa..e6be6d93 100644 --- a/ArjunaJTS/docs/development_guide/en-US/Overview.xml +++ b/ArjunaJTS/docs/development_guide/en-US/Overview.xml @@ -28,7 +28,7 @@ - This ability to roll back an operation if any part of it fails is what JBoss Transactions is all about. This guide + This ability to roll back an operation if any part of it fails is what &PARENT_PRODUCT; is all about. This guide assists you in writing transactional applications to protect your data. @@ -231,7 +231,7 @@ A collection of services that support functions for using and implementing objects. Such services are necessary for the construction of any distributed application. The Object Transaction Service (OTS) is the - most relevant to JBossJTS. + most relevant to &PRODUCT;. @@ -256,7 +256,7 @@ - The OTS specification allows, but does not require, nested transactions. JBossTS is a fully compliant version of + The OTS specification allows, but does not require, nested transactions. &PARENT_PRODUCT; is a fully compliant version of the OTS version 1.1 draft 5, and support nested transactions. diff --git a/ArjunaJTS/docs/development_guide/en-US/Preface.xml b/ArjunaJTS/docs/development_guide/en-US/Preface.xml index 16c10d20..f529108e 100644 --- a/ArjunaJTS/docs/development_guide/en-US/Preface.xml +++ b/ArjunaJTS/docs/development_guide/en-US/Preface.xml @@ -9,7 +9,7 @@
Audience - This guide is specifically intended for service developers using JBoss Transactions. It is also contains useful + This guide is specifically intended for service developers using &PARENT_PRODUCT;. It is also contains useful information about how transactional applications work in general. diff --git a/ArjunaJTS/docs/development_guide/en-US/Revision_History.xml b/ArjunaJTS/docs/development_guide/en-US/Revision_History.xml index 91c2e798..bf4ee53f 100644 --- a/ArjunaJTS/docs/development_guide/en-US/Revision_History.xml +++ b/ArjunaJTS/docs/development_guide/en-US/Revision_History.xml @@ -35,6 +35,20 @@ + + 3 + Thu Jan 16 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + diff --git a/ArjunaJTS/docs/development_guide/en-US/Trailmap.xml b/ArjunaJTS/docs/development_guide/en-US/Trailmap.xml index fa32dba8..6a343146 100644 --- a/ArjunaJTS/docs/development_guide/en-US/Trailmap.xml +++ b/ArjunaJTS/docs/development_guide/en-US/Trailmap.xml @@ -1,38 +1,35 @@ - - - - +%BOOK_ENTITIES; ]> Trail map
Introduction - JBoss Transaction Service (JBossTS) assures complete, accurate business + &PARENT_PRODUCT; assures complete, accurate business transactions for any Java based applications, including those written for the Java EE and EJB frameworks. - JBossTS is a 100% Java implementation of a distributed transaction management system + &PARENT_PRODUCT; is a 100% Java implementation of a distributed transaction management system based on the Sun Microsystems Java EE Java Transaction Service (JTS) standard. Our implementation of the JTS utilizes the Object Management Group's (OMG) Object Transaction Service (OTS) model for transaction interoperability as recommended in the Java EE and EJB standards. Although any JTS-compliant product will allow - Java objects to participate in transactions, one of the key features of JBossTS - is it's 100% Java implementation. This allows JBossTS to support fully distributed + Java objects to participate in transactions, one of the key features of &PARENT_PRODUCT; + is it's 100% Java implementation. This allows &PARENT_PRODUCT; to support fully distributed transactions that can be coordinated by distributed parties. -JBossTS runs can be run both as an embedded distributed service of an application - server (e.g. JBossAS), affording the user all the added benefits of the +&PARENT_PRODUCT; runs can be run both as an embedded distributed service of an application + server (e.g. &APPSERVER;), affording the user all the added benefits of the application server environment such as real-time load balancing, unlimited linear scalability and unmatched fault tolerance that allows you to deliver an always-on solution to your customers. It is also available as a free-standing Java Transaction Service. In addition to providing full compliance with the latest version of the JTS -specification, JBossTS leads the market in providing many advanced features such +specification, &PARENT_PRODUCT; leads the market in providing many advanced features such as fully distributed transactions and ORB portability with POA support. - JBossTS is tested on HP-UX 11i, Red Hat Linux, Windows Server 2003, + &PARENT_PRODUCT; is tested on HP-UX 11i, Red Hat Linux, Windows Server 2003, and Sun Solaris 10, using Sun's JDK 5. It should howerver work on any system with JDK 5 or 6. - The Java Transaction API support for JBossTS comes in two flavours: + The Java Transaction API support for &PARENT_PRODUCT; comes in two flavours: a purely local implementation, that does not require an ORB, but obviously requires all coordinated resources to reside within the same JVM. a fully distributed implementation. Key features @@ -47,19 +44,19 @@ as fully distributed transactions and ORB portability with POA support. transactional objects (TO) for Java ORB independence via the ORB portability layer - This trail map will help you get started with running JBoss transaction service product. + This trail map will help you get started with running &PARENT_PRODUCT; product. It is structured as follows: - 1. Installation Content: This trail describes the content installed by the JBossTS distribution - 2. The Sample Application: This trail describes via a set of examples how JBossTS is used to build transactional applications + 1. Installation Content: This trail describes the content installed by the &PARENT_PRODUCT; distribution + 2. The Sample Application: This trail describes via a set of examples how &PARENT_PRODUCT; is used to build transactional applications 3. Deploying and testing the Sample Application: This trail describes how to deploy and to test the sample application 4. Making the Sample Application Persistent: This trail describes tools allowing to build a persistent application - 5. Recovery from Failure: This trail describes via a simple scenario how JBossTS manages recovery from failure. + 5. Recovery from Failure: This trail describes via a simple scenario how &PARENT_PRODUCT; manages recovery from failure. 6. Where Next?: This trail indicates where to find additional information In addition to the trails listed above, a set of trails giving more explanation on concept around - transaction processing and standards, and also a quick access to section explaining how to configure JBossTS + transaction processing and standards, and also a quick access to section explaining how to configure &PARENT_PRODUCT; are listed in the section "Additional Trails". Note:When running the local JTS transactions part of the trailmap, you will need to start the recovery manager: java com.arjuna.ats.arjuna.recovery.RecoveryManager -test @@ -382,7 +379,7 @@ them has a particular role. Main components are described below. environment. For this aim various distributed transaction processing standards have been developed by international standards organizations. Among these organizations, We list three of them which are mainly - considered in the JBoss Transaction Service product: + considered in the &PARENT_PRODUCT; product: The X/Open model and its successful XA interface @@ -995,10 +992,10 @@ public void transfer(double amount) {
- Configuring the JBoss Transaction Service + Configuring the &PARENT_PRODUCT; This trail provides information on the way to configure environmental variables - needed to define the behaviour of transactional applications managed with JBossTS. - Basically, the behaviour of the JBossTS product is configurable through property + needed to define the behaviour of transactional applications managed with &PARENT_PRODUCT;. + Basically, the behaviour of the &PARENT_PRODUCT; product is configurable through property attributes. Although these property attributes may be specified as command line arguments, it is more convenient to organise and initialise them through properties files. @@ -1057,7 +1054,7 @@ public void transfer(double amount) { com.arjuna.ats.arjuna.common.varDir - JBossTS needs to be able to write temporary files to a well known location + &PARENT_PRODUCT; needs to be able to write temporary files to a well known location during execution. By default this location is var. However, by setting the varDir property variable this can be overridden. Directory name @@ -1066,7 +1063,7 @@ public void transfer(double amount) {
ObjectStore management -The JBossTS layer requires an object store for transaction management logs. Within +The &PARENT_PRODUCT; layer requires an object store for transaction management logs. Within the transaction service installation, object store is updated regularly whenever transactions are created, or when Transactional Objects for Java is used. In a failure free environment, the only object states which should reside within the @@ -1081,11 +1078,11 @@ the object store assuming it is an exclusive resource. The location of the ObjectStore is specified in via the properrty com.arjuna.ats.arjuna.objectstore.objectStoreDir that can be passed with the java flag "-D". For convenience this property is defined in the properties file jbossts-properties.xml, and its value is set - during the JBossTS installation. At any time, the location of the ObjectStore + during the &PARENT_PRODUCT; installation. At any time, the location of the ObjectStore may be changed.
Configuring OutputSometimes it is desirable, mainly in case of debugging, to have some form of - output during execution to trace internal actions performed. JBossTS uses the + output during execution to trace internal actions performed. &PARENT_PRODUCT; uses the logging tracing mechanism provided by the Arjuna Common Logging Framework (CLF) version 2.4, which provides a high level interface that hides differences that exist between logging APIs such Jakarta log4j, JDK 1.4 logging API or dotnet @@ -1106,15 +1103,15 @@ the object store assuming it is an exclusive resource. generates the debugging. Facility code: for instance the package or sub-module within which debugging is generated, e.g., the object store.According to these variables the Common Logging Framework defines three interfaces. A particular product may implement its own classes according to its own finer - granularity. JBossTS uses the default Debugging level and the default Visibility - level provided by CLF, but it defines its own Facility Code. JBossTS uses + granularity. &PARENT_PRODUCT; uses the default Debugging level and the default Visibility + level provided by CLF, but it defines its own Facility Code. &PARENT_PRODUCT; uses the default level assigned to its commonLoggers objects (DEBUG). However, it uses the finer debugging features to disable or enable debug messages. Finer - values used by the JBossTS are defined below: -Debugging level – JBossTS uses the default values defined in the class + values used by the &PARENT_PRODUCT; are defined below: +Debugging level – &PARENT_PRODUCT; uses the default values defined in the class com.arjuna.common.util.logging.CommonDebugLevel
Debug LevelValueDescription
NO_DEBUGGING0x0000A commonLogger object assigned with this values discard all debug requests
CONSTRUCTORS 0x0001Diagnostics from constructors
DESTRUCTORS0x0002Diagnostics from finalizers.
CONSTRUCT_AND_DESTRUCTCONSTRUCTORS | DESTRUCTORSDiagnostics from constructors and finalizers
FUNCTIONS0x010Diagnostics from functions
OPERATORS0x020Diagnostics from operators, such as equals
FUNCS_AND_OPSFUNCTIONS | OPERATORSDiagnostics from functions and operations.
ALL_NON_TRIVIALCONSTRUCT_AND_DESTRUCT | FUNCTIONS - | OPERATORSDiagnostics from all non-trivial operations
TRIVIAL_FUNCS0x0100Diagnostics from trivial functions.
TRIVIAL_OPERATORS:0x0200Diagnostics from trivial operations, and operators.
ALL_TRIVIALTRIVIAL_FUNCS | TRIVIAL_OPERATORSDiagnostics from all trivial operations
FULL_DEBUGGING0xffffFull diagnostics.
Visibility level – JBossTS uses the default values defined in the class - com.arjuna.common.util.logging.CommonVisibilityLevel
Debug LevelValueDescription
VIS_NONE0x0000No Diagnostic
VIS_PRIVATE0x0001only from private methods.
VIS_PROTECTED0x0002only from protected methods.
VIS_PUBLIC0x0004only from public methods.
VIS_PACKAGE0x0008only from package methods.
VIS_ALL0xffffFull Diagnostic
Facility Code – JBossTS uses the following values
Facility Code Level ValueDescription
FAC_ATOMIC_ACTION0x00000001atomic action core module
FAC_BUFFER_MAN0x00000004state management (buffer) classes
FAC_ABSTRACT_REC0x00000008abstract records
FAC_OBJECT_STORE0x00000010object store implementations
FAC_STATE_MAN0x00000020state management and StateManager)
FAC_SHMEM0x00000040 shared memory implementation classes
FAC_GENERAL0x00000080general classes
FAC_CRASH_RECOVERY0x00000800detailed trace of crash recovery module and classes
FAC_THREADING0x00002000threading classes
FAC_JDBC0x00008000JDBC 1.0 and 2.0 support
FAC_RECOVERY_NORMAL0x00040000normal output for crash recovery manager
To ensure appropriate output, it is necessary to set some of the finer debug + | OPERATORSDiagnostics from all non-trivial operationsTRIVIAL_FUNCS0x0100Diagnostics from trivial functions.TRIVIAL_OPERATORS:0x0200Diagnostics from trivial operations, and operators. ALL_TRIVIALTRIVIAL_FUNCS | TRIVIAL_OPERATORSDiagnostics from all trivial operationsFULL_DEBUGGING0xffffFull diagnostics.Visibility level – &PARENT_PRODUCT; uses the default values defined in the class + com.arjuna.common.util.logging.CommonVisibilityLevel
Debug LevelValueDescription
VIS_NONE0x0000No Diagnostic
VIS_PRIVATE0x0001only from private methods.
VIS_PROTECTED0x0002only from protected methods.
VIS_PUBLIC0x0004only from public methods.
VIS_PACKAGE0x0008only from package methods.
VIS_ALL0xffffFull Diagnostic
Facility Code – &PARENT_PRODUCT; uses the following values
Facility Code Level ValueDescription
FAC_ATOMIC_ACTION0x00000001atomic action core module
FAC_BUFFER_MAN0x00000004state management (buffer) classes
FAC_ABSTRACT_REC0x00000008abstract records
FAC_OBJECT_STORE0x00000010object store implementations
FAC_STATE_MAN0x00000020state management and StateManager)
FAC_SHMEM0x00000040 shared memory implementation classes
FAC_GENERAL0x00000080general classes
FAC_CRASH_RECOVERY0x00000800detailed trace of crash recovery module and classes
FAC_THREADING0x00002000threading classes
FAC_JDBC0x00008000JDBC 1.0 and 2.0 support
FAC_RECOVERY_NORMAL0x00040000normal output for crash recovery manager
To ensure appropriate output, it is necessary to set some of the finer debug properties explicitly as follows: <properties> <!-- CLF 2.4 properties --> <property @@ -1162,7 +1159,7 @@ the object store assuming it is an exclusive resource. Introduction Many ORBs currently in use support different versions of CORBA and/or the Java language mapping. - The JBoss Transaction Service only supports the new Portable Object Adapter + &PARENT_PRODUCT; only supports the new Portable Object Adapter (POA) architecture described in the CORBA 2.3 specification as a replacement for the Basic Object Adapter (BOA). Unlike the BOA, which was weakly specified and led to a number of different (and often conflicting) implementations, the @@ -1172,7 +1169,7 @@ the object store assuming it is an exclusive resource. differences between ORB implementations, notably in the area of threading. Note, instead of talking about the POA, this manual will consider the Object Adapter (OA). - Because the JBoss Transaction Service must be able to run on a number of different + Because &PARENT_PRODUCT; must be able to run on a number of different ORBs, we have developed an ORB portability interface which allows entire applications to be moved between ORBs with little or no modifications. This portability interface is available to the application programmer in the form of several Java classes. @@ -1338,11 +1335,11 @@ public static void main(String[] args) For additional details on the features provided by the ORB Portability API - refer to the documentation provided by the JBossTS distribution. + refer to the documentation provided by the &PARENT_PRODUCT; distribution.
- JBossTS Failure Recovery - The failure recovery subsystem of JBossTS will ensure that results of + &PARENT_PRODUCT; Failure Recovery + The failure recovery subsystem of &PARENT_PRODUCT; 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) @@ -1395,7 +1392,7 @@ activators and recovery modules, which are then dynamically loaded. Each recovery activator, which implements the com.arjuna.ats.arjuna.recovery.RecoveryActivator interface, is used to instantiate a recovery class related to the underlying -communication protocol. Indeed, since the version 3.0 of JBossTS, the +communication protocol. Indeed, since the version 3.0 of &PARENT_PRODUCT;, the Recovery Manager is not specifically tied to an Object Request Broker or ORB, which is to specify a recovery instance able to manage the OTS recovery protocol the new interface RecoveryActivator is provided to identify specific @@ -1491,10 +1488,10 @@ value is negative, the first scan is delayed until after the first interval diff --git a/docs/development_guide/en-US/Troubleshooting.xml b/docs/development_guide/en-US/Troubleshooting.xml index 43e977af..f7bba399 100644 --- a/docs/development_guide/en-US/Troubleshooting.xml +++ b/docs/development_guide/en-US/Troubleshooting.xml @@ -6,7 +6,7 @@ Troubleshooting - This chapter covers issues that you may hit when developing applications with JBoss Transactions. + This chapter covers issues that you may hit when developing applications with &PRODUCT;.
WS-BA Participant-Completion Race Condition diff --git a/docs/development_guide/en-US/fallback_content/Legal_Notice.xml b/docs/development_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..23a233a8 100644 --- a/docs/development_guide/en-US/fallback_content/Legal_Notice.xml +++ b/docs/development_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/docs/failure_recovery_guide/en-US/About_This_Guide.xml b/docs/failure_recovery_guide/en-US/About_This_Guide.xml index 9e38f011..284ea6e4 100644 --- a/docs/failure_recovery_guide/en-US/About_This_Guide.xml +++ b/docs/failure_recovery_guide/en-US/About_This_Guide.xml @@ -6,19 +6,18 @@ About This Guide - The Failure Recovery Guide contains information on how to use JBossTS. + The Failure Recovery Guide contains information on how to use &PRODUCT;.
Audience - This guide is most relevant to engineers who are responsible for administering JBoss - Transactions installations. + This guide is most relevant to engineers who are responsible for administering &PRODUCT; installations.
Prerequisites - You should have installed JBossTS. + You should have installed &PRODUCT;.
diff --git a/docs/failure_recovery_guide/en-US/Architecture_of_the_recovery_manager.xml b/docs/failure_recovery_guide/en-US/Architecture_of_the_recovery_manager.xml index a13ea0f6..3410749d 100644 --- a/docs/failure_recovery_guide/en-US/Architecture_of_the_recovery_manager.xml +++ b/docs/failure_recovery_guide/en-US/Architecture_of_the_recovery_manager.xml @@ -1,6 +1,7 @@ +%BOOK_ENTITIES; ]> Architecture of the Recovery Manager @@ -253,17 +254,17 @@ the same Object Store and in which case should not conflict with each other, e.g., roll back transactions that they do not understand. Therefore, when running recovery it is necessary to - tell JBossTS which types of transactions it can recover and + tell &PRODUCT; which types of transactions it can recover and which transaction identifiers it should ignore. - When necessary each transaction identifier that JBossTS + When necessary each transaction identifier that &PRODUCT; creates may have a unique node identifier encoded within it and - JBossTS will only recover transactions and states that match a - specified node identifier. The node identifier for each JBossTS + &PRODUCT; will only recover transactions and states that match a + specified node identifier. The node identifier for each &PRODUCT; instance should be set via the com.arjuna.ats.arjuna.nodeIdentifier property. This value must - be unique across JBossTS instances. The contents of this should + be unique across &PRODUCT; instances. The contents of this should be alphanumeric and not exceed 10 bytes in length. If you do not - provide a value, then JBossTS will fabricate one and report the + provide a value, then &PRODUCT; will fabricate one and report the value via the logging infrastructure. How this value is used will depend upon the type of resources being recovered and will be discussed within the @@ -285,7 +286,7 @@ configured in JTA mode). - Changing versions of JBossTS or the application server on the new node + Changing versions of &PRODUCT; or the application server on the new node is not supported. @@ -348,8 +349,8 @@
- JBossTS Recovery Module Classes - JBossTS provides a set of recovery modules that are + &PRODUCT; Recovery Module Classes + &PRODUCT; provides a set of recovery modules that are responsible to manage recovery according to the nature of the participant and its position in a transactional tree. The provided classes (that all implements the RecoveryModule @@ -402,14 +403,14 @@ ask each resource manager to return the transactions that are currently in a prepared or heuristically completed state. - When running XA recovery it is necessary to tell JBossTS - which types of Xid it can recover. Each Xid that JBossTS creates - has a unique node identifier encoded within it and JBossTS will + When running XA recovery it is necessary to tell &PRODUCT; + which types of Xid it can recover. Each Xid that &PRODUCT; creates + has a unique node identifier encoded within it and &PRODUCT; will only recover transactions and states that match a specified node identifier. The node identifier to use should be provided to - JBossTS via the property JTAEnvironmentBean.xaRecoveryNodes; + &PRODUCT; via the property JTAEnvironmentBean.xaRecoveryNodes; multiple values may be provided in a list. A value of ‘*’ will - force JBossTS to recover (and possibly rollback) all + force &PRODUCT; to recover (and possibly rollback) all transactions irrespective of their node identifier and should be used with caution. The contents of com.arjuna.ats.jta.xaRecoveryNode should be alphanumeric and @@ -443,7 +444,7 @@ com.arjuna.ats.internal.jta.recovery.jts, handles recovery of XA resources (databases etc.) used in JTA. - JBossTS supports two JTA implementations: a purely local + &PRODUCT; supports two JTA implementations: a purely local version (no distributed transactions) and a version layered on the JTS. Recovery for the former is straightforward. In the following discussion we shall implicitly consider on the JTS @@ -455,7 +456,7 @@ far enough for a JTA Resource Record to be written in the ObjectStore. A JTA Resource record contains the information needed to link - the transaction, as known to the rest of JBossTS, to the database. + the transaction, as known to the rest of &PRODUCT;, to the database. Resource-initiated recovery is necessary for branches where a failure occurred after the database had made a persistent record of the transaction, but before the JTA ResourceRecord was @@ -476,7 +477,7 @@ Resource-initiated recovery has to be specifically configured, by supplying the Recovery Manager with the appropriate information for it to interrogate all the databases (XADataSources) that have - been accessed by any JBossTS application. The access to each + been accessed by any &PRODUCT; application. The access to each XADataSource is handled by a class that implements the com.arjuna.ats.jta.recovery.XAResourceRecovery interface, as illustrated in Figure 4. Instances of classes that implements the @@ -574,7 +575,7 @@
Recovering XAConnections - When recovering from failures, JBossTS requires the ability to + When recovering from failures, &PRODUCT; requires the ability to reconnect to databases that were in use prior to the failures in order to resolve any outstanding transactions. Most connection information will be saved by the transaction service during its @@ -584,12 +585,12 @@ occurs before such information can be saved, but after the database connection is used). In order to recreate those connections it is necessary to provide implementations of the - following JBossTS interface + following &PRODUCT; interface com.arjuna.ats.jta.recovery.XAResourceRecovery, one for each database that may be used by an application. if using the transactional JDBC driver provided with - JBossTS, then no additional work is necessary in order to ensure + &PRODUCT;, then no additional work is necessary in order to ensure that recovery occurs. To inform the recovery system about each of the @@ -669,7 +670,7 @@ The iterator based approach used by XAResourceRecovery leads to a requirement for implementations to manage state, which makes them more complex than necessary. - As an alternative, starting with JBossTS 4.4, users may + As an alternative, starting with &PRODUCT; 4.4, users may provide an implementation of the public interface @@ -682,13 +683,13 @@ only one XAResource in the array, as the recover() call on it can return multiple Xids. Unlike XAResourceRecovery instances, which are configured via - the xml properties file and instantiated by JBossTS, instances of + the xml properties file and instantiated by &PRODUCT;, instances of XAResourceRecoveryHelper and constructed by the application code - and registered with JBossTS by calling + and registered with &PRODUCT; by calling XARecoveryModule.addXAResourceRecoveryHelper(...) - The initialize method is not called by JBossTS in the current + The initialize method is not called by &PRODUCT; in the current implementation, but is provided to allow for the addition of further configuration options in later releases. XAResourceRecoveryHelper instances may be deregistered, after @@ -709,13 +710,13 @@ Shipped XAResourceRecovery implementations Recovery of XA datasources can sometimes be implementation dependant, requiring developers to provide their own - XAResourceRecovery instances. However, JBossTS ships with several + XAResourceRecovery instances. However, &PRODUCT; ships with several out-of-the-box implementations that may be useful. These XAResourceRecovery instances are primarily intended - for when running JBossTS outside of a container such as JBossAS, + for when running &PRODUCT; outside of a container such as &APPSERVER;, since they rely upon XADataSources as the primary handle to - drive recovery. If you are not running JBossTS stand-alone then + drive recovery. If you are not running &PRODUCT; stand-alone then you should consult the relevant integration documentation to ensure that the right recovery modules are being used. @@ -754,7 +755,7 @@ initialise operation. In the case of BasicXARecovery and JDBCXARecovery this should be the location of a property file and - is specified in the JBossTS configuration file. For example: + is specified in the &PRODUCT; configuration file. For example: com.arjuna.ats.jta.recovery.XAResourceRecoveryJDBC=com.arjuna.ats.internal.jdbc.recovery.JDBCXAResourceRecovery;thePropertyFile @@ -818,7 +819,7 @@ AtomicActions that are assumed to have completed. For instance, if a failure occurs after a participant has been told to commit but before the transaction system can update the log, then upon - recovery JBossTS recovery will attempt to replay the commit + recovery &PRODUCT; recovery will attempt to replay the commit request, which will obviously fail, thus preventing the log from being removed. This is also used when logs cannot be recovered automatically for other reasons, such as being corrupt or zero @@ -826,7 +827,7 @@ appended with /Expired. AtomicActionExpiryScanner is disabled by default. To enable - it simply add it to the JBossTS properties file. You do not need + it simply add it to the &PRODUCT; properties file. You do not need to enable it in order to cope with (move) corrupt logs.
@@ -854,7 +855,7 @@
TransactionStatusManager This object acts as an interface for the Recovery Manager to - obtain the status of transactions from running JBossTS application + obtain the status of transactions from running &PRODUCT; application processes. One TransactionStatusManager is created per application process by the class com.arjuna.ats.arjuna.coordinator.TxControl. Currently a tcp connection is used for communication between the diff --git a/docs/failure_recovery_guide/en-US/Book_Info.xml b/docs/failure_recovery_guide/en-US/Book_Info.xml index 98fee6d1..51a319e4 100644 --- a/docs/failure_recovery_guide/en-US/Book_Info.xml +++ b/docs/failure_recovery_guide/en-US/Book_Info.xml @@ -5,8 +5,8 @@ ]> Failure Recovery Guide - JBoss Transactions - 4.15.1 + &PRODUCT; + &VERSION; 0 0 diff --git a/docs/failure_recovery_guide/en-US/Configuration_options.xml b/docs/failure_recovery_guide/en-US/Configuration_options.xml index 039ac29c..bc982fa9 100644 --- a/docs/failure_recovery_guide/en-US/Configuration_options.xml +++ b/docs/failure_recovery_guide/en-US/Configuration_options.xml @@ -1,12 +1,13 @@ +%BOOK_ENTITIES; ]> Configuration Options
Recovery Protocol in OTS - Overview - JBossTS is highly configurable. For full details of the configuration mechanism used, see the Programmer's Guide. + &PRODUCT; is highly configurable. For full details of the configuration mechanism used, see the Programmer's Guide. The following table shows the configuration features, with default values shown in italics. More details about each option can be found in the relevant sections of this document. You need to prefix each property in this table with the string com.arjuna.ats.arjuna.recovery. The diff --git a/docs/failure_recovery_guide/en-US/Failure_Recovery_Guide.ent b/docs/failure_recovery_guide/en-US/Failure_Recovery_Guide.ent index 481fd01a..0936d3df 100644 --- a/docs/failure_recovery_guide/en-US/Failure_Recovery_Guide.ent +++ b/docs/failure_recovery_guide/en-US/Failure_Recovery_Guide.ent @@ -1,7 +1,7 @@ - + - - + + - + diff --git a/docs/failure_recovery_guide/en-US/How_JBossTS_manages_the_OTS_recovery_protocol.xml b/docs/failure_recovery_guide/en-US/How_JBossTS_manages_the_OTS_recovery_protocol.xml index 3707b818..f94ee084 100644 --- a/docs/failure_recovery_guide/en-US/How_JBossTS_manages_the_OTS_recovery_protocol.xml +++ b/docs/failure_recovery_guide/en-US/How_JBossTS_manages_the_OTS_recovery_protocol.xml @@ -1,9 +1,10 @@ +%BOOK_ENTITIES; ]> - How JBossTS manages the OTS Recovery Protocol + How &PRODUCT; manages the OTS Recovery Protocol
Recovery Protocol in OTS - Overview To manage recovery in case of failure, the OTS specification has defined a recovery protocol. Transaction’s participants in a doubt status @@ -22,11 +23,11 @@ failure occurring during the transaction.
- RecoveryCoordinator in JBossTS + RecoveryCoordinator in &PRODUCT; On each resource registration a RecoveryCoordinator Object is expected to be created and returned to the application that invoked the register_resource operation. Behind each CORBA object there should be an object implementation or Servant object, in POA terms, which performs operations made on a RecoveryCoordinator object. Rather than to create a RecoveryCoordinator object with its associated servant on each - register_resource, JBossTS enhances performance by avoiding the creation of servants but it relies on a default RecoveryCoordinator object with + register_resource, &PRODUCT; enhances performance by avoiding the creation of servants but it relies on a default RecoveryCoordinator object with it’s associated default servant to manage all replay_completion invocations. In the next sections we first give an overview of the Portable Object Adapter architecture, then we describe how this architecture is used to provide RecoveryCoordinator creation with optimization as explained above. @@ -200,7 +201,7 @@ reference used by the client. Among these information there are the IP address and the port number where resides the server and also the POA name. To perform - replay_completion invocations, the solution adopted by JBossTS is to provide one Servant, per machine, and located in the + replay_completion invocations, the solution adopted by &PRODUCT; is to provide one Servant, per machine, and located in the RecoveryManager process, a separate process from client or server applications. The next section explains how the indirection to a default Servant located on diff --git a/docs/failure_recovery_guide/en-US/Revision_History.xml b/docs/failure_recovery_guide/en-US/Revision_History.xml index a0b947c0..17928939 100644 --- a/docs/failure_recovery_guide/en-US/Revision_History.xml +++ b/docs/failure_recovery_guide/en-US/Revision_History.xml @@ -1,13 +1,7 @@ - - - - - - -]> +]> Revision History @@ -26,6 +20,20 @@ + + 2 + Thu Jan 16 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + diff --git a/docs/failure_recovery_guide/en-US/fallback_content/Legal_Notice.xml b/docs/failure_recovery_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..c6f262b3 100644 --- a/docs/failure_recovery_guide/en-US/fallback_content/Legal_Notice.xml +++ b/docs/failure_recovery_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/docs/transactions_overview_guide/en-US/About_This_Guide.xml b/docs/transactions_overview_guide/en-US/About_This_Guide.xml index 54031a7f..68cea3d9 100644 --- a/docs/transactions_overview_guide/en-US/About_This_Guide.xml +++ b/docs/transactions_overview_guide/en-US/About_This_Guide.xml @@ -6,7 +6,7 @@ About This Guide - The Transaction Fundamentals describes what transactions are, why ACID transactions are good in most cases but extended transactions are necessary in other areas, and other useful information to best use JBossTS. + The Transaction Fundamentals describes what transactions are, why ACID transactions are good in most cases but extended transactions are necessary in other areas, and other useful information to best use &PRODUCT;.
Audience diff --git a/docs/transactions_overview_guide/en-US/Book_Info.xml b/docs/transactions_overview_guide/en-US/Book_Info.xml index 3e406eae..420d45c0 100644 --- a/docs/transactions_overview_guide/en-US/Book_Info.xml +++ b/docs/transactions_overview_guide/en-US/Book_Info.xml @@ -5,8 +5,8 @@ ]> Transactions Overview Guide - JBoss Transactions - 4.15.1 + &PRODUCT; + &VERSION; 0 0 diff --git a/docs/transactions_overview_guide/en-US/Revision_History.xml b/docs/transactions_overview_guide/en-US/Revision_History.xml index c55521ed..901616cf 100644 --- a/docs/transactions_overview_guide/en-US/Revision_History.xml +++ b/docs/transactions_overview_guide/en-US/Revision_History.xml @@ -21,6 +21,20 @@ + + 2 + Thu Jan 16 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + diff --git a/docs/transactions_overview_guide/en-US/Transactions_Overview_Guide.ent b/docs/transactions_overview_guide/en-US/Transactions_Overview_Guide.ent index 850aa515..8703379a 100644 --- a/docs/transactions_overview_guide/en-US/Transactions_Overview_Guide.ent +++ b/docs/transactions_overview_guide/en-US/Transactions_Overview_Guide.ent @@ -1,7 +1,7 @@ - + - - + + - + diff --git a/docs/transactions_overview_guide/en-US/fallback_content/Legal_Notice.xml b/docs/transactions_overview_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..6281fe62 100644 --- a/docs/transactions_overview_guide/en-US/fallback_content/Legal_Notice.xml +++ b/docs/transactions_overview_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/docs/txbridge_guide/en-US/About_This_Guide.xml b/docs/txbridge_guide/en-US/About_This_Guide.xml index 29924a8c..17f82789 100644 --- a/docs/txbridge_guide/en-US/About_This_Guide.xml +++ b/docs/txbridge_guide/en-US/About_This_Guide.xml @@ -8,21 +8,29 @@ The Transaction Bridging Guide contains information on how to use &PRODUCT;. This guide provides information on how to integrate JTA (XA) and XTS (WS-AT) transactions using - the transaction bridge. + the transaction bridge. It provides a low level details on how the TXBridge is implemented and how to use it + manually. + + Note + + Use the XTS administration and development guide for an explanation of how to use the TXBridge automatically. + +
Audience This guide is most relevant for application developers working in environments that - integrate traditional JavaEE transactions usage and transactional Web Services. + integrate traditional JavaEE transactions usage and transactional Web Services, and need a low level control of + the TXBridge. Also for the developers who want to participate in the project.
Prerequisites - JBossTS uses the Java programming language and this manual assumes that you are familiar + &PRODUCT; uses the Java programming language and this manual assumes that you are familiar with programming in Java. In addition, a familiarity with the JTA and XTS components of - JBossTS is assumed. You should read the relevant Programmer's Guides before tackling this + &PRODUCT; is assumed. You should read the relevant Programmer's Guides before tackling this document.
diff --git a/docs/txbridge_guide/en-US/Book_Info.xml b/docs/txbridge_guide/en-US/Book_Info.xml index 2da0d15e..d35ec500 100644 --- a/docs/txbridge_guide/en-US/Book_Info.xml +++ b/docs/txbridge_guide/en-US/Book_Info.xml @@ -5,8 +5,8 @@ ]> Transaction Bridging Guide - JBoss Transactions - 4.15.1 + &PRODUCT; + &VERSION; 0 0 diff --git a/docs/txbridge_guide/en-US/Design_Notes.xml b/docs/txbridge_guide/en-US/Design_Notes.xml index 3fafcdd0..9d0433e4 100644 --- a/docs/txbridge_guide/en-US/Design_Notes.xml +++ b/docs/txbridge_guide/en-US/Design_Notes.xml @@ -1,6 +1,7 @@ +%BOOK_ENTITIES; ]> Design Notes @@ -9,7 +10,7 @@ This section records key design points relating to the bridge implementation. The target audience for this section is software engineers maintaining or extending the transaction bridge implementation. It is unlikely to contain material useful to users, except in so far as - they wish to contribute to the project. An in-depth knowledge of JBossTS internals may be + they wish to contribute to the project. An in-depth knowledge of &PRODUCT; internals may be required to make sense of some parts of this appendix. The txbridge is written as far as possible as a user application layered on top of the JTA and XTS implementations. It accesses these underlying components through standard or supported @@ -61,7 +62,7 @@ the identity of the separately logged JTA subordinate tx (a Uid). XTS is responsible for - the top level coordinator log. JBossTS is responsible for the JTA + the top level coordinator log. &PRODUCT; is responsible for the JTA subordinate tx log and 3rd party RMs are each responsible for their own. @@ -70,7 +71,7 @@ which the crash occurred: RM log only: In this case, the InboundBridgeRecoveryManager's XAResourceOrphanFilter - implementation will be invoked via JBossTS XARecoveryModule, + implementation will be invoked via &PRODUCT; XARecoveryModule, will recognize the orphaned Xids by their formatId (which they inherit from the JCA subordinate, which diff --git a/docs/txbridge_guide/en-US/Introduction.xml b/docs/txbridge_guide/en-US/Introduction.xml index 1c7973a2..15407542 100644 --- a/docs/txbridge_guide/en-US/Introduction.xml +++ b/docs/txbridge_guide/en-US/Introduction.xml @@ -1,6 +1,7 @@ +%BOOK_ENTITIES; ]> Introduction @@ -20,9 +21,9 @@ In distributed applications, the JTA implementation may provide propagation of transaction context and transaction control calls between containers (JVMs) using either a propriety transport or JTS, the Java mapping of the CORBA OTS standard on an RMI/IIOP transport. In - JBossTS, both local and distributed (JTS) implementations of the JTA are available. + &PRODUCT;, both local and distributed (JTS) implementations of the JTA are available. In Web Services applications, ACID transaction management and interoperable context - propagation is provided for by the WS-AT standard. JBossTS XTS provides an implementation of + propagation is provided for by the WS-AT standard. &PRODUCT; XTS provides an implementation of both the 1.0 and 1.2 versions of this standard. Bridging is provided only on the more recent version. At the time of writing the standard covers only the web services API and protocol, not the Java API through which the protocol may be driven. Therefore, XTS provides a custom @@ -37,7 +38,7 @@
Transaction Bridging We use the term Transaction Bridging to describe the process of linking the JavaEE and Web - Services transaction domains. The transaction bridge component (txbridge) of JBossTS provides + Services transaction domains. The transaction bridge component (txbridge) of &PRODUCT; provides bi-directional linkage, such that either type of transaction may encompass business logic designed for use with the other type. The technique used by the bridge is a combination of interposition and protocol mapping. @@ -58,7 +59,7 @@ Transaction interposition in a distributed JTA environment - + diff --git a/docs/txbridge_guide/en-US/Known_Limitations.xml b/docs/txbridge_guide/en-US/Known_Limitations.xml index 961bf311..8c5fad9f 100644 --- a/docs/txbridge_guide/en-US/Known_Limitations.xml +++ b/docs/txbridge_guide/en-US/Known_Limitations.xml @@ -1,6 +1,7 @@ +%BOOK_ENTITIES; ]> Known Limitations @@ -48,7 +49,7 @@ the correct recovery of any external transaction manager used in that role. The transaction bridge does not currently provide dedicated tooling for the manual resolution of orphaned subordinates, instead relying on the general purpose objectstore maintenance tooling - provided by JbossTS. + provided by &PRODUCT;. Note that crash recovery will not behave correctly for outbound bridged transactions if diff --git a/docs/txbridge_guide/en-US/Revision_History.xml b/docs/txbridge_guide/en-US/Revision_History.xml index 9cfd7c91..e868b1c6 100644 --- a/docs/txbridge_guide/en-US/Revision_History.xml +++ b/docs/txbridge_guide/en-US/Revision_History.xml @@ -21,6 +21,20 @@ + + 2 + Thu Jan 23 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + diff --git a/docs/txbridge_guide/en-US/Transaction_Bridge_Architecture.xml b/docs/txbridge_guide/en-US/Transaction_Bridge_Architecture.xml index 77470dd4..0336024f 100644 --- a/docs/txbridge_guide/en-US/Transaction_Bridge_Architecture.xml +++ b/docs/txbridge_guide/en-US/Transaction_Bridge_Architecture.xml @@ -1,6 +1,7 @@ +%BOOK_ENTITIES; ]> Transaction Bridge Architecture @@ -28,7 +29,7 @@ being local to the container in which it operates, whilst the Web Service protocol provides for transaction context propagation between servers. This is an accurate representation of the - situation that exists where the local JTA version of JBossTS is being used alongside JBossTS + situation that exists where the local JTA version of &PRODUCT; is being used alongside &PRODUCT; XTS in an application server. However, it is an oversimplification of the situation where the JTS @@ -115,7 +116,7 @@ transaction bridge deployed. - The call arrives at a web service container, which must have JBossTS JTA or JTS, XTS + The call arrives at a web service container, which must have &PRODUCT; JTA or JTS, XTS and the transaction bridge deployed. The JAX-WS handler chain for the web service should have both the XTS WS-AT transaction header processor and the inbound bridge handler registered, such that they are invoked in that order. @@ -172,7 +173,7 @@ A client starts a JTA transaction and invokes a remote transactional Web Service in - the scope of that transaction. The client must have JBossTS JTA (or JTS) and XTS deployed, + the scope of that transaction. The client must have &PRODUCT; JTA (or JTS) and XTS deployed, as well as the transaction bridge. The coordinator used for the JTA transaction is the root coordinator. The server hosting the target web service needs a WS-AT transaction implementation but not a JTA or the transaction bridge. @@ -230,7 +231,7 @@ DurableParticipants (outbound). In general the former will be from XA datasources or messaging systems, whilst the latter will be custom implementations. In either case it is important to ensure recovery is correctly configured for the resource manager(s) before using them in - production, via the bridge or otherwise. The JBossTS documentation set details crash recovery + production, via the bridge or otherwise. The &PRODUCT; documentation set details crash recovery configuration, as does the application server administration guide. For resource manager specific information e.g. Oracle db permissions settings for recovery connections, please consult the vendor's documentation. @@ -238,7 +239,7 @@ hosts. Resolving the transaction may require more than one crash recovery cycle, due to ordering constrains on the events taking place during recovery. If a transaction fails to recover after all servers have been restored to service for more than two recovery cycles - duration, the JBossTS objectstore browser and server logs may be useful for diagnosing the + duration, the &PRODUCT; objectstore browser and server logs may be useful for diagnosing the issue. Where a transaction involves multiple bridges the number of recovery cycles required to resolve it may further increase. For systems requiring maximum availability it is therefore not recommended to span a transaction through more than one bridge. diff --git a/docs/txbridge_guide/en-US/Transaction_Bridging_Guide.ent b/docs/txbridge_guide/en-US/Transaction_Bridging_Guide.ent index 974e753e..11bc82ea 100644 --- a/docs/txbridge_guide/en-US/Transaction_Bridging_Guide.ent +++ b/docs/txbridge_guide/en-US/Transaction_Bridging_Guide.ent @@ -1,7 +1,7 @@ - + - - + + - + diff --git a/docs/txbridge_guide/en-US/Using_the_Transaction_Bridge.xml b/docs/txbridge_guide/en-US/Using_the_Transaction_Bridge.xml index a381c0ff..bf062f62 100644 --- a/docs/txbridge_guide/en-US/Using_the_Transaction_Bridge.xml +++ b/docs/txbridge_guide/en-US/Using_the_Transaction_Bridge.xml @@ -1,6 +1,7 @@ +%BOOK_ENTITIES; ]> Using the Transaction Bridge @@ -11,12 +12,47 @@ bridge functions.
- Deployment + Enabling - The txbridge.jar file should be placed in JBossAS server/lt;config>/deploy directory. - The server must also be running JBossTS JTA (the default transaction manager) or JTS, and also - JBossTS XTS. The versions of all these components must be consistent. + TXBridge is integrated with the XTS subsystem of the &APPSERVER;. The XTS subsystem is enabled using the + standalone-xts.xml configuration + + Starting &APPSERVER; with XTS Enabled + + + Change to the &APPSERVER; directory: + + + cd $JBOSS_HOME + + + + + Copy the example XTS configuration into the configurations directory: + + + cp docs/examples/configs/standalone-xts.xml standalone/configuration + + + + + Start &APPSERVER;, specifying the xts configuration: + + + Linux: + + + bin/standalone.sh --server-config=standalone-xts.xml + + + Windows: + + + bin\standalone.bat --server-config=standalone-xts.xml + + +
Inbound Bridging @@ -59,69 +95,6 @@ chain registered only on the former. This limitation may be addressed in future versions.
-
- Demonstration Application - A simple demonstration application is available to show usage of the bridge. It is modeled - to some extent on the XTS 'Night Out' demonstrator application, with which readers are assumed - to be familiar. - Since transactions mostly run without visible effect, the demo is useful mainly as an - example of how to utilize the bridge. The bridge implementation does however contain trace - level - logging for most functions. Used in conjunction with verbose logging from XTS, the - transaction - manager, the Web Service stack and the EJB container, this can be used to gain a - detailed - understanding of the flow of events in the system. Alternatively, stepping though the - demo using - a source debugger can be instructive. - - To deploy and run the demo application, edit demo/build.xml to ensure the jbossas.home and - jbossas.server properties are set correctly, then execute 'ant dist' to build the application - artifacts. Start the application server, then deploy the service side of the demo using 'ant - deploy-service' Once it has deployed, the client app can be similarly installed using 'ant - deploy-client'. Depending on your server configuration, the client will then be accessible - from - e.g. - http://localhost:8080/txbridge-demo-client/ - -
- Inbound Bridge - The demonstrator exposes a EJB3 SLSB as a transactional web service ('Bistro') via the - inbound bridge. Note that the code implementing this service is standard EJB with JSR-181 - annotations and has no compile time dependency on XTS or the txbridge. The only point of - linkage is the usage of the @HandlerChain(file = "jaxws-handlers-server.xml") annotation to - reference a xml file containing the XTS and txbridge handlers, as detailed above. Other than - this the service side of the application uses only standard JavaEE elements and has no - direct knowledge of WS-AT transactions. - A client starts a WS-AT transaction and makes an invocation on the web service. The - client does not use JTA (XA) transactions. It uses @HandlerChain(file = - "jaxws-handlers-client.xml") to register the XTS header context processor, but is otherwise - similar to the XTS demo client. - - In this demo, the inbound bridge converts the WS-AT context to a JTA one and invokes the - EJB - in that scope. By default the EJB is backed by the hsqldb embedded in JBossAS, for ease - of - deployment. This database does not support XA, so the resource registered for it uses - LRCO (see ArjunaCore Development Guide for a discussion of LRCO). - However, this point is not significant to the demo. Curious uses can readily use a true - XA - database by deploying it into JBossAS via the usual <xa-datasource> in a -ds.xml - file, then alter the demo's dd/persistence.xml to reference it. - -
-
- Outbound Bridge - The demonstrator client application can also be used to invoke the XTS Night Out demo - Restaurant Service via the outbound bridge. Deploy the XTS demo application services, then - select the 'JTA' transaction type in the client. In this scenario the client uses a JTA - transaction only, whilst the service understands WS-AT type transactions only. Note that the - client has its own copy of the service API, annotated with @HandlerChain(file = - "jaxws-handlers-client.xml"), which is the only point of linkage with the transaction - bridge. Once again neither the client nor server have any compile time dependency on the - bridge. -
-
Loops and Diamonds In distributed environments that utilize transaction bridging, it is possible to construct @@ -159,11 +132,11 @@
Distributed JTA and the JTS - The JavaEE transaction engine in JBossTS comes in two varieties. These are the local only + The JavaEE transaction engine in &PRODUCT; comes in two varieties. These are the local only JTA, which does not support propagation of transaction context or transaction control calls between JVMs and the JTAX, which provides the JTA API implemented by a JTS engine that does support distributed usage. - JBossAS uses the local JTA implementation by default, but can be reconfigured to use the + &APPSERVER; uses the local JTA implementation by default, but can be reconfigured to use the JTS via the JTA API, such that it supports distributed transactions without requiring any changes to business applications. In environments requiring transaction propagation of JTA transactions, it is feasible to @@ -172,7 +145,7 @@ transactional business logic calls. In the latter case the transport is Web Services for both transaction control and business logic. From a transaction management perspective the JTS solution is preferred, due to simplicity - (no protocol mapping is needed), maturity (JBossTS JTS was the world's first JTS + (no protocol mapping is needed), maturity (&PRODUCT; JTS was the world's first JTS implementation and has been extensively used and tested in production environments) and performance (binary vs. xml). It is possible to use transactions that propagate context on some calls via JTS and on @@ -184,26 +157,25 @@
Logging - The transaction bridge uses the jboss-logging system. When running inside JBossAS 6, - logging is configured via the server's deploy/jboss-logging.xml file. To enable full logging - for the transaction bridge, which may be useful for debug purposes, the following should be - used: + The transaction bridge uses the jboss-logging system. When running inside &APPSERVER;, + logging is configured via logging subsystem's configuration in standalone-xts.xml file. To enable full logging + for the transaction bridge, which may be useful for debug purposes, the following logger should be added: Configuring Transaction Bridge Logging Note that the transaction bridge is a thin layer on top of the XTS and JTA/JTS components of - JBossTS, and that it also interacts with other parts of the application server. To gain a + &PRODUCT;, and that it also interacts with other parts of the application server. To gain a comprehensive understanding of the system's operation, it may be necessary to enable verbose - logging for some of these other components also. The JBossTS logging system is discussed in + logging for some of these other components also. The &PRODUCT; logging system is discussed in detail in the accompanying documentation set, but for ease of reference the following may be used to enable verbose logging: Configuring verbose logging - Note also that deployment ordering issues can result in JBossTS components, including the + Note also that deployment ordering issues can result in &PRODUCT; components, including the transaction bridge, becoming active before the logging system is fully configured. In such cases a default logging level may apply during startup, resulting in some more detailed debug messages being missed. diff --git a/docs/txbridge_guide/en-US/fallback_content/Legal_Notice.xml b/docs/txbridge_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..8db3dbd8 100644 --- a/docs/txbridge_guide/en-US/fallback_content/Legal_Notice.xml +++ b/docs/txbridge_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/docs/txbridge_guide/en-US/images/interposition.gif b/docs/txbridge_guide/en-US/images/interposition.gif deleted file mode 100644 index 2258c586..00000000 Binary files a/docs/txbridge_guide/en-US/images/interposition.gif and /dev/null differ diff --git a/docs/txbridge_guide/en-US/images/interposition.png b/docs/txbridge_guide/en-US/images/interposition.png new file mode 100644 index 00000000..0dfc85d6 Binary files /dev/null and b/docs/txbridge_guide/en-US/images/interposition.png differ diff --git a/docs/xts_administration_and_development_guide/en-US/Transactions_XTS_Administration_And_Development_Guide.ent b/docs/xts_administration_and_development_guide/en-US/Transactions_XTS_Administration_And_Development_Guide.ent index 7cb5e717..6c6e24ab 100644 --- a/docs/xts_administration_and_development_guide/en-US/Transactions_XTS_Administration_And_Development_Guide.ent +++ b/docs/xts_administration_and_development_guide/en-US/Transactions_XTS_Administration_And_Development_Guide.ent @@ -3,4 +3,4 @@ - \ No newline at end of file + \ No newline at end of file diff --git a/docs/xts_administration_and_development_guide/en-US/extras/example-client-context-handlers.java b/docs/xts_administration_and_development_guide/en-US/extras/example-client-context-handlers.java deleted file mode 100644 index b00db5aa..00000000 --- a/docs/xts_administration_and_development_guide/en-US/extras/example-client-context-handlers.java +++ /dev/null @@ -1,6 +0,0 @@ -MyService order = service.getPort(portName, MyService.class); - -BindingProvider bindingProvider = (BindingProvider) order; -List handlers = new ArrayList(1); -handlers.add(new JaxWSHeaderContextProcessor()); -bindingProvider.getBinding().setHandlerChain(handlers); \ No newline at end of file diff --git a/docs/xts_administration_and_development_guide/en-US/extras/example-jboss-beans.xml b/docs/xts_administration_and_development_guide/en-US/extras/example-jboss-beans.xml deleted file mode 100644 index fcd64bf5..00000000 --- a/docs/xts_administration_and_development_guide/en-US/extras/example-jboss-beans.xml +++ /dev/null @@ -1,10 +0,0 @@ -+ -+ -+ -+ -+ - - - - - \ No newline at end of file diff --git a/docs/xts_administration_and_development_guide/en-US/extras/example-wsc-registration.xml b/docs/xts_administration_and_development_guide/en-US/extras/example-wsc-registration.xml deleted file mode 100644 index 6c7edaed..00000000 --- a/docs/xts_administration_and_development_guide/en-US/extras/example-wsc-registration.xml +++ /dev/null @@ -1,7 +0,0 @@ - - - - - - - \ No newline at end of file
NameDescriptionPossible ValueDefault Value
com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriodInterval in seconds between initiating the periodic recovery modulesValue in seconds120
com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriodInterval in seconds between first and second pass of periodic recoveryValue in seconds10
com.arjuna.ats.arjuna.recovery.recoveryExtensionXIndicates a periodic recovery module to use. X is the occurence number of the recovery module among a set of recovery modules. These modules are - invoked in sort-order of namesThe class name of the periodic recovery module JBossTS provides a set classes given in the RecoveryManager-properties.xml file
com.arjuna.ats.arjuna.recovery.recoveryActivator_XIndicates a recovery activator to use. X is the occurence number of the - recovery activator among a set of recovery activators. The class name of the periodic recovery activatorJBossTS provide one class that manages the recovery protocol specified + invoked in sort-order of namesThe class name of the periodic recovery module &PARENT_PRODUCT; provides a set classes given in the RecoveryManager-properties.xml file
com.arjuna.ats.arjuna.recovery.recoveryActivator_XIndicates a recovery activator to use. X is the occurence number of the + recovery activator among a set of recovery activators. The class name of the periodic recovery activator&PARENT_PRODUCT; provide one class that manages the recovery protocol specified by the OTS specification
com.arjuna.ats.arjuna.recovery.expiryScannerXXXExpiry scanners to use (order of invocation is random). Names must begin - with "com.arjuna.ats.arjuna.recovery.expiryScanner"Class nameJBossTS provides one class given in the RecoveryManager-properties.xml file
com.arjuna.ats.arjuna.recovery.expiryScanIntervalInterval, in hours, between running the expiry scanners. This can be + with "com.arjuna.ats.arjuna.recovery.expiryScanner"Class name&PARENT_PRODUCT; provides one class given in the RecoveryManager-properties.xml file
com.arjuna.ats.arjuna.recovery.expiryScanIntervalInterval, in hours, between running the expiry scanners. This can be quite long. The absolute value determines the interval - if the value is negative, the scan will NOT be run until after one interval has elapsed. If positive the first scan will be immediately @@ -1508,20 +1505,20 @@ value is negative, the first scan is delayed until after the first interval
Installation Content
Verifying Installation -When installed, the binary release of JBossTS, JTS version, should have the following structure. +When installed, the binary release of &PARENT_PRODUCT;, JTS version, should have the following structure. /bin: this directory contains commands to run the OTS transaction manager server (if required) and the Recovery Manager, - and scripts to configure environment variables needed to execute JBossTS./docs: this directory contains + and scripts to configure environment variables needed to execute &PARENT_PRODUCT;./docs: this directory contains documentation on the way to installing, administering and programming ArjunaCore, - JBossTS JTA and JBossTS JTS./etc: this directory contains appropriate - properties files that can be used to configure the behaviour of the JBoss Transaction Service./htdocs: this directory describes - all APIs defined by JBossTS + &PARENT_PRODUCT; JTA and &PARENT_PRODUCT; JTS./etc: this directory contains appropriate + properties files that can be used to configure the behaviour of the &PARENT_PRODUCT;./htdocs: this directory describes + all APIs defined by &PARENT_PRODUCT; /idl: this directory contains the CORBA idl files that may be registered with your interface repository prior to running any applications. /jacorb: This directory contains the jacorb distribution. /lib: this directory contains the - jar files that contains packages defined by the JBossTS. These jar files + jar files that contains packages defined by the &PARENT_PRODUCT;. These jar files shall be added in the CLASSPATH /services: this directory contains the appropriates scripts, jar and configuration files allowing to start and stop standalone Transaction Service and Recovery Manager @@ -1530,14 +1527,14 @@ When installed, the binary release of JBossTS, JTS version, should have the foll
Testing your installation - To ensure that your JBossTS installation is fully operational, we will run the simple demo. + To ensure that your &PARENT_PRODUCT; installation is fully operational, we will run the simple demo. Please follow these steps before running the transactional applications Ensure you have the Ant build system installed. Ant is a Java build tool, similar to make. It is available for free from http://ant.apache.org/ The sample application requires version 1.5.1 or later. The PATH and CLASSPATH environment variables need to be set appropriately - to use JBoss Transaction Service. To make this easier, we provide a shell + to use &PARENT_PRODUCT;. To make this easier, we provide a shell script setup_env.sh (and for Windows a batch file setup_env.bat) in the directory <jbossts_install_root>/bin/ @@ -1549,8 +1546,8 @@ When installed, the binary release of JBossTS, JTS version, should have the foll the directory <jbossts_install_root>/trail_map/lib Add the generated jar file to the CLASSPATH environment variable. - Ensure that the jacorb is added in your CLASSPATH. Use only the patched version that ships with JBossTS. - Ensure that JBossTS jar files appear before jacorb jar files. + Ensure that the jacorb is added in your CLASSPATH. Use only the patched version that ships with &PARENT_PRODUCT;. + Ensure that &PARENT_PRODUCT; jar files appear before jacorb jar files. Start the server. src/com/arjuna/demo/simple/HelloServer.java">(HelloServer.java) (Note: The source code for the trailmap is fully documented and can often contain very useful tips and information that may not be reflected elsewhere in the trailmap) @@ -1581,11 +1578,11 @@ When installed, the binary release of JBossTS, JTS version, should have the foll Hello - called within a scope of a transaction
Setting properties -The JBoss Transaction Service has been designed to be highly configurable at runtime through the use of various +&PARENT_PRODUCT; has been designed to be highly configurable at runtime through the use of various property attributes. Although these attributes can be provided at runtime on the command line, it is possible (and may be more convenient) to specify them through the -properties file jbossts-properties.xml located under the /etc directory of the JBossTS distribution. - More details on the way to configure the behavior of JBossTS can be found in the section on configuration. +properties file jbossts-properties.xml located under the /etc directory of the &PARENT_PRODUCT; distribution. + More details on the way to configure the behavior of &PARENT_PRODUCT; can be found in the section on configuration.
@@ -1594,7 +1591,7 @@ properties file jbossts-properties.xml located under the /etc directory of the JDK releases from 1.2.2 onwards include a minimum ORB implementation from Sun. If using such a JDK in conjunction with another ORB it is necessary to tell the JVM which ORB to use. This happens by specifying the org.omg.CORBA.ORBClass - and org.omg.CORBA.ORBSingletonClass properties. In earlier versions of the JBossTS + and org.omg.CORBA.ORBSingletonClass properties. In earlier versions of the &PARENT_PRODUCT; it was necessary to specify these properties explicitly, either on the command line of in the properties file. However, it is no longer a requirement to do this, as the ORB Portability classes @@ -2039,7 +2036,7 @@ properties file jbossts-properties.xml located under the /etc directory of the transaction processing standards have been developed by international standards organizations. Among these organizations, We list three of them which are - mainly considered in the Jboss Transaction Service + mainly considered in the &PARENT_PRODUCT; product: @@ -2078,15 +2075,15 @@ properties file jbossts-properties.xml located under the /etc directory of the
- JBossTS Overview + &PARENT_PRODUCT; Overview - JBoss Transaction Service (JBossTS) assures + &PARENT_PRODUCT; assures complete, accurate business transactions for any Java based applications, including those written for the Java EE and EJB frameworks. - JBossTS is a 100% Java implementation of a + &PARENT_PRODUCT; is a 100% Java implementation of a distributed transaction management system based on the Sun Microsystems Java EE Java Transaction Service (JTS) standard. Our implementation of the JTS @@ -2095,15 +2092,15 @@ properties file jbossts-properties.xml located under the /etc directory of the interoperability as recommended in the Java EE and EJB standards. Although any JTS-compliant product will allow Java objects to participate in transactions, - one of the key features of JBossTS is it's 100% Java - implementation. This allows JBossTS to support fully + one of the key features of &PARENT_PRODUCT; is it's 100% Java + implementation. This allows &PARENT_PRODUCT; to support fully distributed transactions that can be coordinated by distributed parties. - JBossTS runs can be run both as an embedded + &PARENT_PRODUCT; runs can be run both as an embedded distributed service of an application server - (e.g. JBossAS), affording the user all the + (e.g. &APPSERVER;), affording the user all the added benefits of the application server environment such as real-time load balancing, unlimited linear scalability and unmatched fault @@ -2114,18 +2111,18 @@ properties file jbossts-properties.xml located under the /etc directory of the In addition to providing full compliance with - the latest version of the JTS specification, JBossTS + the latest version of the JTS specification, &PARENT_PRODUCT; leads the market in providing many advanced features such as fully distributed transactions and ORB portability with POA support. - JBossTS works on a number of operating systems including + &PARENT_PRODUCT; works on a number of operating systems including Red Hat linux, Sun Solaris and Microsoft Windows XP. It requires a Java 5 or later environment. - The Java Transaction API support for JBossTS comes + The Java Transaction API support for &PARENT_PRODUCT; comes in two flavours: @@ -2237,7 +2234,7 @@ properties file jbossts-properties.xml located under the /etc directory of the
Deploying and Testing The Banking Application - Assuming that the JBoss Transactioning product has + Assuming that the &PARENT_PRODUCT; product has been installed, this trail provides a set of examples that show how to build transactional applications. Two types of transactional @@ -2259,8 +2256,7 @@ properties file jbossts-properties.xml located under the /etc directory of the The PATH and CLASSPATH environment variables - need to be set appropriately to use JBoss - Transaction Service. To make this easier, we + need to be set appropriately to use &PARENT_PRODUCT;. To make this easier, we provide a shell script setup_env.sh (and for Windows a batch file setup_env.bat) in the directory @@ -2296,7 +2292,7 @@ properties file jbossts-properties.xml located under the /etc directory of the
Local transaction with JTA - To configure JBossTS for such transaction, edit the + To configure &PARENT_PRODUCT; for such transaction, edit the jbossts-properties.xml file and set the following properties to the appropriate values: @@ -2312,7 +2308,7 @@ properties file jbossts-properties.xml located under the /etc directory of the
Distributed transaction with JTA - While for a distributed transactions case, JBossTS need + While for a distributed transactions case, &PARENT_PRODUCT; need to be configured as follow: <property @@ -2340,7 +2336,7 @@ properties file jbossts-properties.xml located under the /etc directory of the To illustrate the programming interfaces - possibilities enabled by JBossTS, the banking + possibilities enabled by &PARENT_PRODUCT;, the banking application is provided in several versions: a version that uses the JTA API and a second that uses JTS/OTS interfaces. @@ -2363,11 +2359,11 @@ properties file jbossts-properties.xml located under the /etc directory of the
Running The Banking application with JTA
- Configuring JBossTS + Configuring &PARENT_PRODUCT; Program Applications that create transactions using te JTA interface may invoke as well local services as remote services. When a remote invocation need to be performed, the current transactional context need to be propagated -to the remote service in order to involve it to the transaction in progress. JBoss Transaction Service allows the -possibility to provide such feature using the facilities provided by JTS and ORB. More precisely JBossTS need to be configured +to the remote service in order to involve it to the transaction in progress.&PARENT_PRODUCT; allows the +possibility to provide such feature using the facilities provided by JTS and ORB. More precisely &PARENT_PRODUCT; need to be configured to determine in which type of transaction, local or distributed, the JTA interface is used.
@@ -2463,7 +2459,7 @@ ERROR - javax.transaction.RollbackException Building The Banking Application with JTA From an architectural point of view of JTA, the bank client is considered as an application program able to manage transactions via the javax.transaction.UserTransaction interface. The following portion of code illustrates how a JTA transaction is - started and terminated when the client asks to transfer money from one account to another. This also describes what are JBossTS packages that need to be used + started and terminated when the client asks to transfer money from one account to another. This also describes what are &PARENT_PRODUCT; packages that need to be used in order to obtain appropriate objects instances (such UserTransaction). Note: The code below is a simplified view of the BankClient.java program. Only the transfer operation is illustrated; other operations manage transactions in the same way. (see for details the src/com/arjuna/demo/jta/localbank/BankClient.java) @@ -2498,7 +2494,7 @@ public class BankClient try { - //the following instruction asks a specific JBossTS + //the following instruction asks a specific &PARENT_PRODUCT; //class to obtain a UserTransaction instance javax.transaction.UserTransaction userTran = com.arjuna.ats.jta.UserTransaction.userTransaction(); @@ -2703,8 +2699,8 @@ public class AccountResource implements XAResource
Running The Banking application with JTS The JTS version of the Banking application means that the Object Request Broker - will be used. The JBossTS distribution is provided to work with the bundled JacORB version - To describe the possibilities provided by JBossTS to build a transactional + will be used. The &PARENT_PRODUCT; distribution is provided to work with the bundled JacORB version + To describe the possibilities provided by &PARENT_PRODUCT; to build a transactional application according to the programming models defined by the OTS specification, the Banking Application is programmed in different ways. @@ -2726,7 +2722,7 @@ public class AccountResource implements XAResource
Running The Banking application with JTS The JTS version of the Banking application means that the Object Request Broker - will be used. The JBossTS distribution is provided to work with the bundled JacORB version + will be used. The &PARENT_PRODUCT; distribution is provided to work with the bundled JacORB version Note: Ensure that the jacorb jar files are added in your CLASSPATH To launch the JTS version of the Banking application, execute the following java program @@ -2819,7 +2815,7 @@ minor code: 50001 completed: No
Using a stand-alone Transaction Server - By default JBossTS does not use a separate transaction manager server: transaction + By default &PARENT_PRODUCT; does not use a separate transaction manager server: transaction managers are co-located with each application process to improve performance and improve application fault-tolerance. When running applications which require a separate transaction manager, you must set the com.arjuna.ats.jts.transactionManager @@ -2834,7 +2830,7 @@ minor code: 50001 completed: No
Running The Banking application with JTS The JTS version of the Banking application means that the Object Request Broker - will be used. The JBossTS distribution is provided to work with the bundled JacORB version + will be used. The &PARENT_PRODUCT; distribution is provided to work with the bundled JacORB version Note: Ensure that the jacorb jar files are added in your CLASSPATH In a separate window launch the Recovery Manager, as follow. @@ -2953,7 +2949,7 @@ minor code: 50001 completed: No
Using a stand-alone Transaction Server - By default JBossTS does not use a separate transaction manager server: transaction + By default &PARENT_PRODUCT; does not use a separate transaction manager server: transaction managers are co-located with each application process to improve performance and improve application fault-tolerance. When running applications which require a separate transaction manager, you must set the com.arjuna.ats.jts.transactionManager @@ -2968,7 +2964,7 @@ minor code: 50001 completed: No
Running the example on several machines - It is possible to run the JBoss Transaction Service and recovery manager processes on a different machine and have clients access these + It is possible to run the &PARENT_PRODUCT; Transaction Service and recovery manager processes on a different machine and have clients access these centralized services in a hub-and-spoke style architecture. All that must be done is to provide the clients with enough information to contact the transaction service (such as the ORB's NameService). @@ -3048,7 +3044,7 @@ minor code: 50001 completed: No done in the indirect mode. The following portion of code illustrates how a JTS transaction is started and terminated when the client asks to transfer money from one account to another. - This also describes what are JBossTS packages that need to be used in order + This also describes what are &PARENT_PRODUCT; packages that need to be used in order to obtain appropriate objects instances (such Current). Note: The code below is a simplified view of the BankClient.java program. Only the transfer operation is illustrated; other operations manage transactions @@ -3087,7 +3083,7 @@ import com.arjuna.ats.internal.jts.ORBManager; try { - //the following instruction asks a specific JBossTS class to obtain a Current instance + //the following instruction asks a specific &PARENT_PRODUCT; class to obtain a Current instance Current current = OTSManager.get_current(); System.out.println("Beginning a User transaction to get balance"); current.begin(); @@ -3116,7 +3112,7 @@ import com.arjuna.ats.internal.jts.ORBManager; myORB.initORB(args, null); //Initialise the ORB myOA.initOA(); //Initialise the POA - // The ORBManager is a class provided by JBossTS to facilitate the association + // The ORBManager is a class provided by &PARENT_PRODUCT; to facilitate the association // of the ORB/POA with the transaction service ORBManager.setORB(myORB); ORBManager.setPOA(myOA); @@ -3354,7 +3350,7 @@ module arjuna { The following portion of code illustrates how a JTS transaction is started and terminated when the client asks to transfer money from one account to another. - This also describes what are JBossTS packages that need to be used in order + This also describes what are &PARENT_PRODUCT; packages that need to be used in order to obtain appropriate objects instances (such Current). Note: The code below is a simplified view of the BankClient.java program. Only the transfer operation is illustrated; other operations manage transactions @@ -3376,7 +3372,7 @@ public class BankClient try { //the following instruction asks a specific - //JBossTS class to obtain a Current instance + //&PARENT_PRODUCT; class to obtain a Current instance Current current = OTSManager.get_current(); System.out.println("Beginning a User transaction to get balance"); current.begin(); @@ -3669,7 +3665,7 @@ module arjuna { }; The following portion of code illustrates how a JTS transaction is started and terminated when the client asks to transfer money from one account to another. - This also describes what are JBossTS packages that need to be used in order + This also describes what are &PARENT_PRODUCT; packages that need to be used in order to obtain appropriate standard JTS API objects instances (such Current). Note: The code below is a simplified view of the BankClient.java program. Only the transfer operation is illustrated; other operations manage transactions @@ -3694,7 +3690,7 @@ public class BankClient try { //the following instruction asks a - // specific JBossTS class + // specific &PARENT_PRODUCT; class // to obtain a Current instance Current current = OTSManager.get_current(); System.out.println("Beginning a User @@ -3960,7 +3956,7 @@ public class AccountResource done in the indirect mode. The following portion of code illustrates how a JTS transaction is started and terminated when the client asks to transfer money from one account to another. - This also describes what are JBossTS packages that need to be used in order + This also describes what are &PARENT_PRODUCT; packages that need to be used in order to obtain appropriate objects instances (such Current). Note: The code below is a simplified view of the BankClient.java program. Only the transfer operation is illustrated; other operations manage transactions @@ -4002,7 +3998,7 @@ public class BankClient try { //the following instruction asks a specific - // JBossTS class to obtain a Current instance + // &PARENT_PRODUCT; class to obtain a Current instance Current current = OTSManager.get_current(); System.out.println("Beginning a User transaction to get balance"); @@ -4240,7 +4236,7 @@ public class AccountResource extends org.omg.CosTransactions.ResourcePOA - Using the JBoss Transactional Object For Java + Using the &PARENT_PRODUCT; Object For Java (TXOJ) mechanisms Overview of the Transactional Object @@ -4255,7 +4251,7 @@ public class AccountResource extends org.omg.CosTransactions.ResourcePOA application as a relational database. Developing applications with JDBC - and JBossTS + and &PARENT_PRODUCT; The banking application as a relational database accessed with @@ -4477,7 +4473,7 @@ public class AccountResource extends org.omg.CosTransactions.ResourcePOA Distributed Configuration The banking application with Transactional Object for Java (TXOJ) is configured to use JTS interfaces as the API to create the transaction, then an ORB to deploy - it. The JBossTS distribution is provided to work with the bundled JacORB version + it. The &PARENT_PRODUCT; distribution is provided to work with the bundled JacORB version Note: Ensure that the jacorb jar files are added in your CLASSPATH
@@ -4942,14 +4938,14 @@ file.close();
- Developing applications with JDBC and JBossTS JTS - JBossTS JTS supports the construction of both local and distributed transactional + Developing applications with JDBC and &PARENT_PRODUCT; JTS + &PARENT_PRODUCT; JTS supports the construction of both local and distributed transactional applications which access databases using the JDBC APIs. JDBC supports two-phase commit of transactions, and is similar to the XA X/Open standard. The JDBC support is found in the com.arjuna.ats.jdbc package.
Transactional Driver - The JBossTS JTS approach to incorporating JDBC connections within transactions + The &PARENT_PRODUCT; JTS approach to incorporating JDBC connections within transactions is to provide transactional JDBC drivers through which all interactions occur. These drivers intercept all invocations and ensure that they are registered with, and driven by, appropriate transactions. There is a single type of transactional @@ -4990,13 +4986,13 @@ DriverManager.registerDriver(arjunaJDBC2Driver); Connection con = DriverManager.getConnection(url, username, password); From its version 2.0, the JDBC API has introduced a new way to obtain instances of the Connection class. This is the case of the interfaces DataSource and XADataSource - that creates transactional connections. When using a JDBC 2.0 driver, JBossTS + that creates transactional connections. When using a JDBC 2.0 driver, &PARENT_PRODUCT; will use the appropriate DataSource whenever a connection to the database is made. It will then obtain XAResources and register them with the transaction via the JTA interfaces. It is these XAResources which the transaction service will use when the transaction terminates in order to drive the database to either commit or rollback the changes made via the JDBC connection. - There are two ways in which the JBossTS JDBC 2.0 support can obtain XADataSources. + There are two ways in which the &PARENT_PRODUCT; JDBC 2.0 support can obtain XADataSources. These will be explained in the following sections. Note, for simplicity we shall assume that the JDBC 2.0 driver is instantiated directly by the application. @@ -5032,12 +5028,12 @@ Connection connection = arjunaJDBC2Driver. Many JDBC implementations provide proprietary implementations of XADataSources that provide non-standard extensions to the specification. In order to allow the application to remain isolated from the actual JDBC 2.0 implementation - it is using and yet continue to be able to use these extensions, JBossTS + it is using and yet continue to be able to use these extensions, &PARENT_PRODUCT; hides the details of these proprietary implementations using dynamic class instantiation. In addition, the use of JNDI is not required when using this mechanism because the actual implementation of the XADataSource will be directly instantiated, albeit in a manner which will not tie an application - or driver to a specific implementation. JBossTS therefore has several classes + or driver to a specific implementation. &PARENT_PRODUCT; therefore has several classes which are for specific JDBC implementations, and these can be selected at runtime by the application setting the dynamicClass property appropriately: @@ -5101,18 +5097,18 @@ Connection connection = arjunaJDBC2Driver.connect("jdbc:arjuna:
Using the Connection Once the connection has been established (for example, using the java.sql.DriverManager.getConnection - method), all operations on the connection will be monitored by JBossTS. Once + method), all operations on the connection will be monitored by &PARENT_PRODUCT;. Once created, the driver and any connection can be used in the same way as any other JDBC driver or connection. - JBossTS connections can be used within multiple different transactions simultaneously, + &PARENT_PRODUCT; connections can be used within multiple different transactions simultaneously, i.e., different threads, with different notions of the current transaction, - may use the same JDBC connection. JBossTS does connection pooling for each + may use the same JDBC connection. &PARENT_PRODUCT; does connection pooling for each transaction within the JDBC connection. So, although multiple threads may use the same instance of the JDBC connection, internally this may be using a different connection instance per transaction. With the exception of close, all operations performed on the connection at the application level will only be performed on this transaction-specific connection. - JBossTS will automatically register the JDBC driver connection with the transaction + &PARENT_PRODUCT; will automatically register the JDBC driver connection with the transaction via an appropriate resource . When the transaction terminates, this resource will be responsible for either committing or rolling back any changes made to the underlying database via appropriate calls on the JDBC driver. @@ -5120,7 +5116,7 @@ Connection connection = arjunaJDBC2Driver.connect("jdbc:arjuna:
Further reading More details on the way to manage applications using the JDBC API can be found - in the JBossTS Programming Guide. + in the &PARENT_PRODUCT; Programming Guide.
The banking application as a relational database accessed with JDBC @@ -5290,7 +5286,7 @@ If an xa error is returned you can use the following property property Note Although, this version of the banking application creates JTA local transactions, - the way to manipulate JDBC API and the associated JBossTS mechanisms in the + the way to manipulate JDBC API and the associated &PARENT_PRODUCT; mechanisms in the case of distributed transactions is the same.
@@ -5305,14 +5301,14 @@ If an xa error is returned you can use the following property property - JBossTS ensures that results of a transaction are applied consistently to all resources involved in - a transaction, even in the presence of failure. To recover from failure, JBossTS relies on its Recovery + &PARENT_PRODUCT; ensures that results of a transaction are applied consistently to all resources involved in + a transaction, even in the presence of failure. To recover from failure, &PARENT_PRODUCT; relies on its Recovery Manager. Basically, the Recovery Manager is a daemon process that invokes a set of well known Recovery Modules periodically in two steps; a first to determine transactions in doubt state and a second step to continue the completion of those transactions found in the first step. Since different type of resources may be - involved in a transaction, different type of Recovery Modules may exist. JBossTS provides several type of + involved in a transaction, different type of Recovery Modules may exist. &PARENT_PRODUCT; provides several type of modules that manage resources according to their position in the transaction tree (root, subordinate, leaf) or the nature of the data itself, transactional object for java or XAResource as seen in the previous trail. @@ -5325,7 +5321,7 @@ If an xa error is returned you can use the following property property Running the Recovery Manager This section provides only brief information on running the recovery manager from provided scripts. - For complete information on the recovery manager (including how to configure it), see the JBoss TS recovery information. + For complete information on the recovery manager (including how to configure it), see the &PARENT_PRODUCT; recovery information.
Windows @@ -5362,11 +5358,11 @@ If an xa error is returned you can use the following property property The Recovery Process and XAResources - The JBossTS recovery manager provides support for recovering XAResources whether or not they are Serializable. XAResources that do + The &PARENT_PRODUCT; recovery manager provides support for recovering XAResources whether or not they are Serializable. XAResources that do implement the Serializable interface are handled without requiring additional programmer defined classes. For those XAResources that need to recover but which cannot implement Serializable, it is possible to provide a small class which is used to help recover them. - This example shows the JBossTS recovery manager recovering a Serializable XAResource and a non-Serializable XAResource. + This example shows the &PARENT_PRODUCT; recovery manager recovering a Serializable XAResource and a non-Serializable XAResource.
The demo's components The application consists of four classes. Each class is well documented and it is recommended that the provided code is inspected to gain useful insight into some of the nuances of the recovery process. @@ -5375,34 +5371,34 @@ If an xa error is returned you can use the following property property Programmer-defined support of the Serializable XAResource is only required in the XAResource implementation class src/com/arjuna/demo/recovery/xaresource/ExampleXAResource.java">ExampleXAResource.javaProgrammer-defined support of the non-Serializable XAResource is required both in the XAResource implementation class src/com/arjuna/demo/recovery/xaresource/NonSerializableExampleXAResource.java">NonSerializableExampleXAResource, - and in a class that implements a helper for the JBossTS recovery process + and in a class that implements a helper for the &PARENT_PRODUCT; recovery process src/com/arjuna/demo/recovery/xaresource/NonSerializableExampleXAResourceRecovery.java">NonSerializableExampleXAResourceRecovery.java
XAResourceRecovery registration - When recovering from failures, JBossTS requires the ability to reconnect to the resource managers + When recovering from failures, &PARENT_PRODUCT; requires the ability to reconnect to the resource managers that were in use prior to the failures in order to resolve any outstanding transactions. In order to recreate those connections for non-Serializable XAResources it is necessary to - provide implementations of the following JBossTS interface com.arjuna.ats.jta.recovery.XAResourceRecovery. + provide implementations of the following &PARENT_PRODUCT; interface com.arjuna.ats.jta.recovery.XAResourceRecovery. To inform the recovery system about each of the XAResourceRecovery instances, it is necessary to specify their class names through property variables in the jbossts-properties.xml file. Any property variable which starts with the name XAResourceRecovery will be assumed to represent one of these instances, and its value should be the class name. - When running XA transaction recovery it is necessary to tell JBossTS which types of - Xid it can recover. Each Xid that JBossTS creates has a unique node - identifier encoded within it and JBossTS will only recover transactions + When running XA transaction recovery it is necessary to tell &PARENT_PRODUCT; which types of + Xid it can recover. Each Xid that &PARENT_PRODUCT; creates has a unique node + identifier encoded within it and &PARENT_PRODUCT; will only recover transactions and states that match a specified node identifier. The node identifier to - use should be provided to JBossTS via a property that starts with the + use should be provided to &PARENT_PRODUCT; via a property that starts with the name com.arjuna.ats.jta.xaRecoveryNode (multiple values may - be provided). A value of * will force JBossTS to recover (and possibly + be provided). A value of * will force &PARENT_PRODUCT; to recover (and possibly rollback) all transactions irrespective of their node identifier and should be used with caution. The recovery module for the non-Serializable XAResource must be deployed in order to provide support to recover the non-Serializable XAResource. - If this step was missed out the Serializable XAResource would recover OK but JBossTS would have no knowledge of the non-Serializable XAResource + If this step was missed out the Serializable XAResource would recover OK but &PARENT_PRODUCT; would have no knowledge of the non-Serializable XAResource and so it could not recover it. To register the non-Serializable XAResource XAResourceRecovery module, add an entry to the jbossts-properties.xml. Under the element <properties depends="jts" name="jta">, add: @@ -5427,10 +5423,10 @@ If an xa error is returned you can use the following property property Specify the transaction manager type to use - The recovery manager will work in the same manner for either the JTA or JTS implementation. By default the JBoss Transaction Service + The recovery manager will work in the same manner for either the JTA or JTS implementation. By default &PARENT_PRODUCT; is configured to use a JTS transaction manager, in order to configure it to use a JTA transaction manager a change must again be made to the jbossts-properties.xml. See "Testing JTA" for more information on how to configure - the JBossTS transaction manager to use JTA rather than JTS. + the &PARENT_PRODUCT; transaction manager to use JTA rather than JTS. If you do change the transaction manager type remember to reconfigure the recovery manager as follows: @@ -5463,7 +5459,7 @@ If an xa error is returned you can use the following property property
The Recovery Process and AbstractRecordsWARNING: Implementing a RecoveryModule and AbstractRecord is a very advanced feature of the transaction service. It should only - be performed by users familiar with the all the concepts used in the JBoss Transactions product. Please see the ArjunaCore guide for more + be performed by users familiar with the all the concepts used in the &PARENT_PRODUCT; product. Please see the ArjunaCore guide for more information about RecoveryModules and AbstractRecords. The following sample gives an overview how the Recovery Manager invokes a module to recover from failure. This basic sample does not aim to present a complete process to recover from failure, but mainly to illustrate @@ -5488,7 +5484,7 @@ If an xa error is returned you can use the following property property A Recovery Module (src/com/arjuna/demo/recoverymodule/SimpleRecoveryModule.java">SimpleRecoveryModule.java) that consists to read the content of the file used to store the status of the participant, to determine that status and print a message indicating if a recovery action is needed or not. - Using the provided JBossTS Recovery Modules ensures that resources are correctly recovered. This sample illustrates + Using the provided &PARENT_PRODUCT; Recovery Modules ensures that resources are correctly recovered. This sample illustrates how to define and register its own module. It's the responsibility of the module to re-create the appropriate objects using information retrieved from a log. diff --git a/ArjunaJTS/docs/development_guide/en-US/fallback_content/Legal_Notice.xml b/ArjunaJTS/docs/development_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..79002cdf 100644 --- a/ArjunaJTS/docs/development_guide/en-US/fallback_content/Legal_Notice.xml +++ b/ArjunaJTS/docs/development_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/ArjunaJTS/docs/orbportability_guide/en-US/Book_Info.xml b/ArjunaJTS/docs/orbportability_guide/en-US/Book_Info.xml index 41f87aa1..c1d75b1f 100644 --- a/ArjunaJTS/docs/orbportability_guide/en-US/Book_Info.xml +++ b/ArjunaJTS/docs/orbportability_guide/en-US/Book_Info.xml @@ -4,9 +4,9 @@ %BOOK_ENTITIES; ]> - JBossJTS ORB Portability Guide - JBossJTS - 4.15.1 + &PRODUCT; ORB Portability Guide + &PRODUCT; + &VERSION; 1 1 diff --git a/ArjunaJTS/docs/orbportability_guide/en-US/JBossJTS_ORB_Portability_Guide.ent b/ArjunaJTS/docs/orbportability_guide/en-US/JBossJTS_ORB_Portability_Guide.ent index 7d8ce85c..01df4bb9 100644 --- a/ArjunaJTS/docs/orbportability_guide/en-US/JBossJTS_ORB_Portability_Guide.ent +++ b/ArjunaJTS/docs/orbportability_guide/en-US/JBossJTS_ORB_Portability_Guide.ent @@ -1,7 +1,9 @@ - + + - - + + + - + diff --git a/ArjunaJTS/docs/orbportability_guide/en-US/ORB_Portability_API.xml b/ArjunaJTS/docs/orbportability_guide/en-US/ORB_Portability_API.xml index 4ab50507..c18f561e 100644 --- a/ArjunaJTS/docs/orbportability_guide/en-US/ORB_Portability_API.xml +++ b/ArjunaJTS/docs/orbportability_guide/en-US/ORB_Portability_API.xml @@ -45,10 +45,10 @@ it within the ORB class. This method should be used in preference to the raw ORB interface since the - JBoss Transaction Service + &PARENT_PRODUCT; requires a reference to the ORB. If this method is not used, setOrb must be called prior to using - JBoss Transaction Service + &PARENT_PRODUCT; . @@ -76,7 +76,7 @@ addAttribute - : this method allows the application to register classes with JBoss Transaction Service + : this method allows the application to register classes with &PARENT_PRODUCT; which will be called either before, or after the ORB has been initialised. See the section titled ORB and OA Initialisation. If the ORB has already been initialised then the @@ -168,7 +168,7 @@ addAttribute - : this method allows the application to register classes with JBoss Transaction Service + : this method allows the application to register classes with &PARENT_PRODUCT; which will be called either before or after the OA has been initialised. See below. If the OA has already been initialised then the attribute object will not be added, and false @@ -298,7 +298,7 @@ Initialisation code The - JBoss Transaction Service + &PARENT_PRODUCT; requires specialised code to be instantiated before and after the ORB and the OA are initialised. This code can be provided at runtime through the @@ -433,7 +433,7 @@ CONFIGURATION_FILE - : as described in the Using the OTS Manual, the JBoss Transaction Service supports an + : as described in the Using the OTS Manual, the &PARENT_PRODUCT; supports an initial reference file where references for specific services and objects can be stored and used at runtime. The file, CosServices.cfg, consists of two columns: the service name (in the case of the OTS server TransactionService) and the IOR, separated by a diff --git a/ArjunaJTS/docs/orbportability_guide/en-US/Preface.xml b/ArjunaJTS/docs/orbportability_guide/en-US/Preface.xml index 5c00d2ed..51095b5f 100644 --- a/ArjunaJTS/docs/orbportability_guide/en-US/Preface.xml +++ b/ArjunaJTS/docs/orbportability_guide/en-US/Preface.xml @@ -10,11 +10,11 @@ Prerequisites &PRODUCT; - works in conjunction with the rest of the JBoss Transactions suite. In addition to the documentation here, consult the &PRODUCT; + works in conjunction with the rest of the &PARENT_PRODUCT; suite. In addition to the documentation here, consult the &PRODUCT; documentation, which ships as part of &PRODUCT; - and is also available on the JBoss Transaction Service website + and is also available on the &PARENT_PRODUCT; website at - + .
diff --git a/ArjunaJTS/docs/orbportability_guide/en-US/Revision_History.xml b/ArjunaJTS/docs/orbportability_guide/en-US/Revision_History.xml index 66420895..3a4df84c 100644 --- a/ArjunaJTS/docs/orbportability_guide/en-US/Revision_History.xml +++ b/ArjunaJTS/docs/orbportability_guide/en-US/Revision_History.xml @@ -21,6 +21,20 @@ + + 2 + Thu Jan 16 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + diff --git a/ArjunaJTS/docs/orbportability_guide/en-US/fallback_content/Legal_Notice.xml b/ArjunaJTS/docs/orbportability_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..3bec1dc0 100644 --- a/ArjunaJTS/docs/orbportability_guide/en-US/fallback_content/Legal_Notice.xml +++ b/ArjunaJTS/docs/orbportability_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/ArjunaJTS/docs/quick_start_guide/en-US/Book_Info.xml b/ArjunaJTS/docs/quick_start_guide/en-US/Book_Info.xml index db3e9d03..f2a4dcbc 100644 --- a/ArjunaJTS/docs/quick_start_guide/en-US/Book_Info.xml +++ b/ArjunaJTS/docs/quick_start_guide/en-US/Book_Info.xml @@ -4,9 +4,9 @@ %BOOK_ENTITIES; ]> - JBossJTS Quick Start Guide - JBossJTS - 4.15.1 + &PRODUCT; Quick Start Guide + &PRODUCT; + &VERSION; 1 1 diff --git a/ArjunaJTS/docs/quick_start_guide/en-US/JBossJTS_Quick_Start_Guide.ent b/ArjunaJTS/docs/quick_start_guide/en-US/JBossJTS_Quick_Start_Guide.ent index 0a07034e..7f22a6c9 100644 --- a/ArjunaJTS/docs/quick_start_guide/en-US/JBossJTS_Quick_Start_Guide.ent +++ b/ArjunaJTS/docs/quick_start_guide/en-US/JBossJTS_Quick_Start_Guide.ent @@ -1,7 +1,9 @@ - + + - - + + + - + diff --git a/ArjunaJTS/docs/quick_start_guide/en-US/Preface.xml b/ArjunaJTS/docs/quick_start_guide/en-US/Preface.xml index 250dc45e..04fc9cef 100644 --- a/ArjunaJTS/docs/quick_start_guide/en-US/Preface.xml +++ b/ArjunaJTS/docs/quick_start_guide/en-US/Preface.xml @@ -10,11 +10,11 @@ Prerequisites &PRODUCT; - works in conjunction with the rest of the JBoss Transactions suite. In addition to the documentation here, consult the &PRODUCT; + works in conjunction with the rest of the &PARENT_PRODUCT; suite. In addition to the documentation here, consult the &PRODUCT; documentation, which ships as part of &PRODUCT; - and is also available on the JBoss Transaction Service website + and is also available on the &PARENT_PRODUCT; website at - + .
diff --git a/ArjunaJTS/docs/quick_start_guide/en-US/Quick_Start_to_JTS_OTS.xml b/ArjunaJTS/docs/quick_start_guide/en-US/Quick_Start_to_JTS_OTS.xml index 94691788..a0befdca 100644 --- a/ArjunaJTS/docs/quick_start_guide/en-US/Quick_Start_to_JTS_OTS.xml +++ b/ArjunaJTS/docs/quick_start_guide/en-US/Quick_Start_to_JTS_OTS.xml @@ -1,6 +1,7 @@ +%BOOK_ENTITIES; ]> Quick Start to JTS/OTS diff --git a/ArjunaJTS/docs/quick_start_guide/en-US/Revision_History.xml b/ArjunaJTS/docs/quick_start_guide/en-US/Revision_History.xml index 3f21bf20..94ca1ff1 100644 --- a/ArjunaJTS/docs/quick_start_guide/en-US/Revision_History.xml +++ b/ArjunaJTS/docs/quick_start_guide/en-US/Revision_History.xml @@ -21,6 +21,20 @@ + + 2 + Thu Jan 16 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + diff --git a/ArjunaJTS/docs/quick_start_guide/en-US/fallback_content/Legal_Notice.xml b/ArjunaJTS/docs/quick_start_guide/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..9156f37d 100644 --- a/ArjunaJTS/docs/quick_start_guide/en-US/fallback_content/Legal_Notice.xml +++ b/ArjunaJTS/docs/quick_start_guide/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/XTS/background/en-US/About_This_Guide.xml b/XTS/background/en-US/About_This_Guide.xml index 0e3adeb9..d9371438 100644 --- a/XTS/background/en-US/About_This_Guide.xml +++ b/XTS/background/en-US/About_This_Guide.xml @@ -1,7 +1,6 @@ - %BOOK_ENTITIES; ]> @@ -42,7 +41,7 @@
Prerequisites - JBoss Transaction Service uses the Java programming language and this manual assumes that you are familiar with + &PRODUCT; uses the Java programming language and this manual assumes that you are familiar with programming in Java. Additional helpful skills are outlined in . @@ -54,7 +53,7 @@ This guide presents overview information for all of the above. However, to aid in understanding the Web Services - component of JBoss Transaction Service, the WS-C, WS-Atomic Transaction Transactions: XTS Background Guide Background for using the XTS Module of &PRODUCT; to provide Web Services Transactions - JBoss Transactions + &PRODUCT; 0 0 - The "XTS Background Guide" contains background information, which is important to understand, before you can use JBoss Transaction Service to develop service-based + The "XTS Background Guide" contains background information, which is important to understand, before you can use &PRODUCT; to develop service-based applications, that use transaction technology to manage business processes. diff --git a/XTS/background/en-US/Introduction.xml b/XTS/background/en-US/Introduction.xml index 0310224a..eadbc1d1 100644 --- a/XTS/background/en-US/Introduction.xml +++ b/XTS/background/en-US/Introduction.xml @@ -25,7 +25,7 @@ WSDLWeb Services Description Language - The XML Transaction Service (XTS) component of JBoss Transaction Service supports the + The XML Transaction Service (XTS) component of &PRODUCT; supports the coordination of private and public Web Services in a business transaction. Therefore, to understand XTS, you must be familiar with Web Services, and also understand something about transactions. This chapter introduces XTS and provides a brief overview of the technologies that form the Web Services standard. Additionally, this chapter @@ -35,7 +35,7 @@ documentation. - JBoss Transaction Service provides the XTS component as a transaction solution for Web Services. Using XTS, business + &PRODUCT; provides the XTS component as a transaction solution for Web Services. Using XTS, business partners can coordinate complex business transactions in a controlled and reliable manner. The XTS API supports a transactional coordination model based on the WS-Coordination, WS-Atomic Transaction, and WS-Business Activity specifications. @@ -47,7 +47,7 @@ (WS-T) transaction protocols that utilize this framework. - JBoss Transaction Service implements versions 1.1, and 1.2 of these three specifications. Version + &PRODUCT; implements versions 1.1, and 1.2 of these three specifications. Version specifications are available from . @@ -151,7 +151,7 @@ published via JaxWS, without developer intervention. The only requirement is that transactional client applications and transactional web services must reside within a domain capable of hosting JaxWS endpoints, such as an - application server. JBoss Application Server can provide this functionality. + application server. &APPSERVER; can provide this functionality.
diff --git a/XTS/background/en-US/Revision_History.xml b/XTS/background/en-US/Revision_History.xml index 1b5d8e3d..45f5a9fe 100644 --- a/XTS/background/en-US/Revision_History.xml +++ b/XTS/background/en-US/Revision_History.xml @@ -7,6 +7,20 @@ Revision History + + 2 + Thu Jan 16 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + 1 Thursday Feb 21 2013 diff --git a/XTS/background/en-US/Transactions_Overview.xml b/XTS/background/en-US/Transactions_Overview.xml index 23b766e3..cd074d29 100644 --- a/XTS/background/en-US/Transactions_Overview.xml +++ b/XTS/background/en-US/Transactions_Overview.xml @@ -263,7 +263,7 @@ Two Phase Commit - The classical two-phase commit approach is the bedrock of JBoss Transaction Service, and more generally of Web + The classical two-phase commit approach is the bedrock of &PRODUCT;, and more generally of Web Services transactions. Two-phase commit provides coordination of parties that are involved in a transaction. The general flow of a two-phase commit transaction is described in . diff --git a/XTS/background/en-US/Transactions_XTS_Background_Guide.ent b/XTS/background/en-US/Transactions_XTS_Background_Guide.ent index d98beef5..64739951 100644 --- a/XTS/background/en-US/Transactions_XTS_Background_Guide.ent +++ b/XTS/background/en-US/Transactions_XTS_Background_Guide.ent @@ -1,5 +1,5 @@ - + - + - \ No newline at end of file + \ No newline at end of file diff --git a/XTS/background/en-US/fallback_content/Legal_Notice.xml b/XTS/background/en-US/fallback_content/Legal_Notice.xml index 70b0c8d4..94f6a580 100644 --- a/XTS/background/en-US/fallback_content/Legal_Notice.xml +++ b/XTS/background/en-US/fallback_content/Legal_Notice.xml @@ -1,5 +1,7 @@ +%BOOK_ENTITIES; ]> diff --git a/blacktie/docs/userguide/en-US/User_Guide.ent b/blacktie/docs/userguide/en-US/User_Guide.ent index 63a31e54..490995df 100644 --- a/blacktie/docs/userguide/en-US/User_Guide.ent +++ b/blacktie/docs/userguide/en-US/User_Guide.ent @@ -1,7 +1,7 @@ - - + + - + diff --git a/docs/development_guide/en-US/Book_Info.xml b/docs/development_guide/en-US/Book_Info.xml index 8c345692..0c2d0165 100644 --- a/docs/development_guide/en-US/Book_Info.xml +++ b/docs/development_guide/en-US/Book_Info.xml @@ -5,14 +5,14 @@ ]> Development Guide - Development reference guide for the JBoss Transactions suite of software - JBoss Transactions - 4.15.1 + Development reference guide for the &PRODUCT; suite of software + &PRODUCT; + &VERSION; 0 0 - Development reference guide for the JBoss Transactions suite of software + Development reference guide for the &PRODUCT; suite of software diff --git a/docs/development_guide/en-US/Configuration_Options.xml b/docs/development_guide/en-US/Configuration_Options.xml index 4519381e..4d648982 100644 --- a/docs/development_guide/en-US/Configuration_Options.xml +++ b/docs/development_guide/en-US/Configuration_Options.xml @@ -227,10 +227,10 @@
- JBossJTA Configuration options + &PRODUCT; JTA Configuration options The canonical reference for configuration options is the javadoc of the various EnvironmentBean classes. For - JBossJTA, these classes are the ones provided by ArjunaCore, as well as: + &PRODUCT; JTA, these classes are the ones provided by ArjunaCore, as well as: @@ -246,10 +246,10 @@
- JBossJTS Options + &PRODUCT; JTS Options The canonical reference for configuration options is the javadoc of the various - EnvironmentBean classes, For ArjunaJTS these are the ones + EnvironmentBean classes, For &PRODUCT; JTS these are the ones provided by ArjunaCore, as well as: diff --git a/docs/development_guide/en-US/Development_Guide.ent b/docs/development_guide/en-US/Development_Guide.ent index dfc948f0..ab86f4cd 100644 --- a/docs/development_guide/en-US/Development_Guide.ent +++ b/docs/development_guide/en-US/Development_Guide.ent @@ -1,7 +1,7 @@ - + - - + + - + diff --git a/docs/development_guide/en-US/Important_Log_Messages.xml b/docs/development_guide/en-US/Important_Log_Messages.xml index ad3c3393..a25155ab 100644 --- a/docs/development_guide/en-US/Important_Log_Messages.xml +++ b/docs/development_guide/en-US/Important_Log_Messages.xml @@ -1,13 +1,8 @@ - - - - - - -]> +%BOOK_ENTITIES; +]> Important Log Messages The transaction manager can generate a lot of logging information when configured to log in trace level. diff --git a/docs/development_guide/en-US/Preface.xml b/docs/development_guide/en-US/Preface.xml index 3ae7dc55..d36dd572 100644 --- a/docs/development_guide/en-US/Preface.xml +++ b/docs/development_guide/en-US/Preface.xml @@ -1,6 +1,6 @@ + ]> Preface diff --git a/docs/development_guide/en-US/Revision_History.xml b/docs/development_guide/en-US/Revision_History.xml index d8a25afe..c5369afe 100644 --- a/docs/development_guide/en-US/Revision_History.xml +++ b/docs/development_guide/en-US/Revision_History.xml @@ -35,6 +35,20 @@ + + 3 + Thu Jan 16 2014 + + Gytis + Trikleris + gytis@redhat.com + + + + Update to Wildfly and Narayana + + + diff --git a/docs/development_guide/en-US/Tools.xml b/docs/development_guide/en-US/Tools.xml index 855c5556..78dae13c 100644 --- a/docs/development_guide/en-US/Tools.xml +++ b/docs/development_guide/en-US/Tools.xml @@ -22,7 +22,7 @@
Browse and Manage Transactions Using an Application Server - The JBoss EAP and WildFly application servers provide a command-line based Management CLI which supports the ability to browse and manipulate transaction records. + The &APPSERVER; provides a command-line based Management CLI which supports the ability to browse and manipulate transaction records. This functionality is provided by the interaction between the Transaction Manager (TM) and the Management API of the application server. To start the CLI on a non-windows based OS type the following command in application server install directory: @@ -43,7 +43,7 @@ This command refreshes the Log Store for server groups which use the profile default in a managed domain. For a standalone server, remove the profile=default from the command. - /profile=default/subsystem=transactions/log-store=log-store/:probe + /subsystem=transactions/log-store=log-store/:probe View All Prepared Transactions @@ -51,7 +51,7 @@ To view all prepared transactions, first refresh the log store (see ), then run the following command, which functions similarly to a filesystem ls command. - ls /profile=default/subsystem=transactions/log-store=log-store/transactions + ls /subsystem=transactions/log-store=log-store/transactions Each transaction is shown, along with its unique identifier. Individual operations can be run against an individual transaction (see ). @@ -66,7 +66,7 @@ To view information about a transaction, such as its JNDI name, EIS product name and version, or its status, use the :read-resource CLI command. - /profile=default/subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-b66efc2\:4f9e6f8f\:9:read-resource + /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-b66efc2\:4f9e6f8f\:9:read-resource @@ -76,7 +76,7 @@ Each transaction log contains a child element called participants. Use the read-resource CLI command on this element to see the participants of the transaction. Participants are identified by their JNDI names. - /profile=default/subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-b66efc2\:4f9e6f8f\:9/participants=java\:\/JmsXA:read-resource + /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-b66efc2\:4f9e6f8f\:9/participants=java\:\/JmsXA:read-resource The result may look similar to this: @@ -107,7 +107,7 @@ Each transaction log supports a :delete operation, to delete the transaction log representing the transaction. - /profile=default/subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-b66efc2\:4f9e6f8f\:9:delete + /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-b66efc2\:4f9e6f8f\:9:delete If failures occur, transaction logs may remain in the object store until crash recovery facilities have resolved the transactions they represent. @@ -150,7 +150,7 @@ If a transaction needs recovery, you can use the :refresh CLI command to be sure it still requires recovery, before attempting the recovery. - /profile=default/subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-b66efc2\:4f9e6f8f\:9:refresh + /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-b66efc2\:4f9e6f8f\:9:refresh @@ -283,7 +283,7 @@ java -Dcom.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqJournalEnvironm
Embedded Console - Transaction management is integrated into the JBoss EAP and WildFly application servers. + Transaction management is integrated into the &APPSERVER;.
@@ -333,8 +333,7 @@ jconsole -J-Djava.class.path="$CLASSPATH" -pluginpath $INSTALL_ROOT/lib/narayana
View Transaction Statistics using an Application Server - If you are using the Transaction Manager (TM) inside the JBoss EAP or - WildFly application servers and if the TM statistics are enabled, then + If you are using the Transaction Manager (TM) inside the &APPSERVER; and if the TM statistics are enabled, then you can view statistics about the TM and transaction subsystem using tools provide by the application server. @@ -371,7 +370,7 @@ jconsole -J-Djava.class.path="$CLASSPATH" -pluginpath $INSTALL_ROOT/lib/narayana - /host=master/server=server-one/subsystem=transactions/:read-attribute(name=number-of-transactions,include-defaults=true) + /subsystem=transactions/:read-attribute(name=number-of-transactions,include-defaults=true) @@ -384,7 +383,7 @@ jconsole -J-Djava.class.path="$CLASSPATH" -pluginpath $INSTALL_ROOT/lib/narayana - /host=master/server=server-one/subsystem=transactions/:read-attribute(name=number-of-committed-transactions,include-defaults=true) + /subsystem=transactions/:read-attribute(name=number-of-committed-transactions,include-defaults=true) @@ -397,7 +396,7 @@ jconsole -J-Djava.class.path="$CLASSPATH" -pluginpath $INSTALL_ROOT/lib/narayana - /host=master/server=server-one/subsystem=transactions/:read-attribute(name=number-of-aborted-transactions,include-defaults=true) + /subsystem=transactions/:read-attribute(name=number-of-aborted-transactions,include-defaults=true) @@ -410,7 +409,7 @@ jconsole -J-Djava.class.path="$CLASSPATH" -pluginpath $INSTALL_ROOT/lib/narayana - /host=master/server=server-one/subsystem=transactions/:read-attribute(name=number-of-timed-out-transactions,include-defaults=true) + /subsystem=transactions/:read-attribute(name=number-of-timed-out-transactions,include-defaults=true) @@ -423,7 +422,7 @@ jconsole -J-Djava.class.path="$CLASSPATH" -pluginpath $INSTALL_ROOT/lib/narayana - /host=master/server=server-one/subsystem=transactions/:read-attribute(name=number-of-heuristics,include-defaults=true) + /subsystem=transactions/:read-attribute(name=number-of-heuristics,include-defaults=true) @@ -436,7 +435,7 @@ jconsole -J-Djava.class.path="$CLASSPATH" -pluginpath $INSTALL_ROOT/lib/narayana - /host=master/server=server-one/subsystem=transactions/:read-attribute(name=number-of-inflight-transactions,include-defaults=true) + /subsystem=transactions/:read-attribute(name=number-of-inflight-transactions,include-defaults=true) @@ -449,7 +448,7 @@ jconsole -J-Djava.class.path="$CLASSPATH" -pluginpath $INSTALL_ROOT/lib/narayana - /host=master/server=server-one/subsystem=transactions/:read-attribute(name=number-of-application-rollbacks,include-defaults=true) + /subsystem=transactions/:read-attribute(name=number-of-application-rollbacks,include-defaults=true) @@ -462,7 +461,7 @@ jconsole -J-Djava.class.path="$CLASSPATH" -pluginpath $INSTALL_ROOT/lib/narayana - /host=master/server=server-one/subsystem=transactions/:read-attribute(name=number-of-resource-rollbacks,include-defaults=true) + /subsystem=transactions/:read-attribute(name=number-of-resource-rollbacks,include-defaults=true)