Configuring transaction support - distributed systems only
You must register the database with the coordination queue manager before using the stand-alone database logger. This protects the log data by using global transactions on distributed systems. The database acts as an XA resource manager and the queue manager as an XA transaction manager.
About this task
If you are using z/OS®, do not carry out any of these steps because WebSphere® MQ File Transfer Edition for z/OS uses the Resource Recovery Service (RRS), which is a prerequisite.
Procedure
What to do next
For more information about completing these steps, see the following topics in the WebSphere MQ V7.0.1 product documentation and the following developerWorks article:
- This topic describes XA registration in general terms, with specifics applicable to C programs: Scenario 1: Queue manager performs the coordination. Not all the databases that are mentioned here are supported by WebSphere MQ when you use a Java application such as WebSphere MQ File Transfer Edition. Do not follow the instructions in this linked topic to create switch files. These instructions apply to native code programs only. For the database logger, which is a Java program, use the instructions in the following topic instead: Configuring JTA/JDBC coordination on platforms other than Windows.
- This topic is applicable specifically to the approach used by the WebSphere MQ File Transfer Edition database logger: JTA/JDBC coordination using WebSphere MQ classes for Java.
- You might also find the following IBM® developerWorks article useful: Configuring and using XA transactions with WebSphere MQ V6 Classes for Java.