Chapter 3. OTS and J2EE Transaction Service management
3.1. Starting the Run-time System
Run-time support for the JBoss Transaction Service consists of run-time packages and the OTS Transaction Manager server. By default JBoss Transaction Service does not use a separate Transaction Manager server. Instead, transaction managers are co-located with each application process. This improves performance and application fault-tolerance by removing external dependencies of applications upon other services for proper function.
If your application requires a separate transaction manager, set the
com.arjuna.ats.jts.transactionManager environment variable to yes. The system locates the transaction manager using an ORB-specific mechanism. It might be registered with a name server, added to the ORB’s initial references, listed in a references file specific to JBoss Transaction Service, or located by the ORB’s specific location mechanism.
You can override the default registration mechanism by setting the
com.arjuna.orbportability.resolveService environment variable to one of the following values:
CONFIGURATION_FILE, the default value- causes the system to use the
CosServices.cfgfile. -
NAME_SERVICE - JBoss Transaction Service attempts to use a name service to register the transaction factory. If this is not supported by the ORB, an exception will be thrown.
-
BIND_CONNECT - JBoss Transaction Service uses the ORB-specific bind mechanism. If this is not supported by the ORB, an exception will be thrown.
-
RESOLVE_INITIAL_REFERENCES - JBoss Transaction Service attempts to register the transaction service with the ORB's initial service references.
