| Main |
| Home |
| Tyrex |
| API |
| Configuration |
| Using Tyrex |
| Services |
| TP Monitoring |
| OTS |
| JNDI |
| Security |
| Databases |
| Tomcat |
| Download |
| Resources |
| License |
| Bugs |
| Changelog |
| Contributors |
| Library |
| Lists/Forums |
| CVS |
 |
Introduction
How to configure Tyrex to be used as an OTS?
How to configure OpenORB to run Tyrex ?
How to start Tyrex as an OTS server ?
Problems
Introduction
This document quickly explains how to configure OpenORB to run Tyrex as an OTS. It also explains how to start Tyrex as an OTS server.
How to configure Tyrex to be used as an OTS?
Extend your classpath by adding the OpenORB jar file and the 'ots.jar' file provided with the Tyrex distribution. Start the Tyrex build file by supplying the following argument : iiop. After the build, a jar file named 'tyrex-X.X.X-iiop.jar' is available. Add this jar file in your classpath.
How to configure OpenORB to run Tyrex ?
To configure OpenORB, please edit the OpenORB configuration file ( OpenORB.xml ). Defines a new
module to describe the OTS :
<module name="tyrex" initializer="tyrex.corba.Initializer" />
Then, define a new profile :
<profile name="ots" extends="default">
<import module="transaction" />
</profile>
When you start a CORBA application that want to use the Tyrex OTS, be sure to use the
To be able to resolve the 'TransactionService' initial reference, you have to extend the InitRef module, by adding :
<property name="TransactionService" value="corbaname:rir:#Tyrex/TransactionFactory" />
How to start Tyrex as an OTS server ?
To start Tyrex as an OTS server, just start the following class :
java tyrex.corba.OTSServer
Several options are available :
-naming : this option is used to bind the transaction factory to the naming service
with the following name tyrex\TransactionFactory
-ior : this option implies the generation of a file named 'ots.ior' that contains the
transaction factory IOR.
Problems
If you encounter problems with the OTS server send a detailed email to Tyrex Users' Mailing List.
The email should contain:
- A stacktrace if one is available - The database used, including version number, if one is used - The JDBC driver version number, if one is used - Instructions on how to reproduce the problem - Version of OpenORB, and a copy of your OpenORB.xml file