TXSeries as coordinator

TXSeries as a transaction manager act as a XA coordinator to WebSphere Application Server to achieve two-phase coordination between these two transaction managers.

Some common transactional deployment scenarios for TXSeries for Multiplatforms are as follows:
  • Scenario 1: The Figure 1 depicts a global transaction model where TXSeries COBOL/C Application access one or more XA resources and requires two-phase coordination with resources managed by WebSphere Application Server.
    Figure 1. Scenario 1
    Scenario 1
  • Scenario 2: The Figure 2 depicts a global transaction model where TXSeries COBOL/C Application access one or more XA resources and requires access to the same data on the same database that is managed by both WebSphere Application Server and TXSeries Region.
    Figure 2. Scenario 2
    Scenario 2
  • Scenario 3: The Figure 3 depicts a global transaction model where TXSeries COBOL/C Application accesses one or more XA resources and requires two-phase coordination with resources managed by WebSphere Application Server and another participant TXSeries Region.
    Figure 3. Scenario 3
    Scenario 3
  • Scenario 4: The Figure 4 depicts a global transaction model where TXSeries COBOL/C Application accesses one or more XA resources and requires two-phase coordination with resources managed by WebSphere Application Server and the boundaries of the Logical Unit of Work.
    Figure 4. Scenario 4
    Scenario 4
    • If WebSphere Application Server is the coordinator, the Logical Unit of Work (LUW1) starts at WebSphere Application Server and TXSeries should not invoke EJB (EXEC CICS LINK) back to WebSphere Application Server on the same LUW1.
    • If TXSeries region is the coordinator, the Logical Unit of Work (LUW2) starts at TXSeries and WebSphere Application Server should not invoke TXSeries Application on the same LUW2.