Use this task when you want to call an Enterprise JavaBeans® (EJB) application that is deployed on WebSphere® Application Server for z/OS® from an external address space while ignoring the client transaction context.
Prior to version 8.0.0.4, the only environment where transactional semantics are supported is Customer Information Control System (CICS®).
Starting with Version 8.0.0.4, 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 WebSphere Application Server 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 that is running on WebSphere Application Server 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.
In this information ...Related concepts
| IBM Redbooks, demos, education, and more(Index) |