(ZOS) Calling an enterprise bean from an external address space within a client-initiated transaction
Use this task when you call an WebSphere (EJB) application that is deployed on WAS for z/OS from an external address space within a client-initiated transaction. The Customer Information Control System (CICS ) environment is the only environment where transactional support is supported.
The only environment where transactional semantics are supported is Customer Information Control System (CICS).
Starting with v8.5.0.2, the Customer Information Control System (CICS ) and Information Management System (IMS) are the only environments where transactional support is provided with WOLA.
The client process must be running on a z/OS operating system and the client environment must support transactional semantics. The connection between the client and the WAS is configured to support transactions. Also, the client must have called the Register API with the TRANSACTIONAL flag set to the value of 1.
When running in an IMS dependent region, the IMS environment must be running with RRS=YES.
This process starts when you begin a transaction in a client environment. The client calls an EJB application running on WAS for z/OS and propagates the new transaction to the application server. The semantics for starting a transaction in the client environment varies based on the client environment. Refer to the CICS documentation for information about the semantics for starting a transaction in a CICS client environment. Refer to the IMS documentation for information about the semantics for starting a transaction in an IMS client environment.
Tasks
- Deploy an EJB application on WAS. Use a transaction attribute, such as required, support or mandatory, on the execute method.
- Start a transaction on the client application using the transactional semantics. The client application performs transactional work required in the client environment.
- Use the Invoke (BBOA1INV) API or the Send Request (BBOA1SRQ) API to make a remote call with the client program to the EJB application that is deployed on WAS. The transaction context propagates to the WAS server and the EJB application runs under the transaction context.
- Use the transactional semantics of the client environment to commit or end the transaction independent of the outcome of the WAS server transaction.
The new transaction is propagated to the WAS for z/OS server. The client commits the transaction and a single two-phase commit completes the transaction across the two address spaces.
Related:
Optimized local adapters on WAS for z/OS Optimized local adapters for z/OS APIs WAS transactions BBOC, BBO$, BBO# Deploy and administering enterprise applications Enable optimized local adapters support in CICS Install the WebSphere BBOC, BBO$ and BBO# transactions in CICS