Transaction management

CICS® Transaction Gateway includes a resource adapter that can provide LocalTransaction support or XATransaction support.

The cicseci.rar resource adapter provides LocalTransaction support when deployed on any supported JEE application server. It can also provide XATransaction support when deployed with the custom property xasupport=on on any supported JEE application server connecting to a remote CICS Transaction Gateway for z/OS®. It also provides global transaction support when using WebSphere® Application Server for z/OS with CICS Transaction Gateway on z/OS in local mode.

To provide for different transactional qualities of service for JEE applications, you can deploy the CICS resource adapter into the JEE application server and create multiple connection factories on it. Each of these connection factories can be configured with a different quality of service.

See Deploying CICS resource adapters for information about installing the resource adapters.

Start of change
Managed mode
If you are running multiple interactions with CICS using the ECI resource adapter, you might want to group all actions together to ensure that they either all succeed or all fail. The preferred way is to let the JEE application server manage the transactions which are then known as container-managed transactions. You can use the LocalTransaction or UserTransaction interface. Such transactions are known as bean-managed transactions. Bean-managed transactions that use the LocalTransaction interface can group work performed only through the resource adapter; the UserTransaction interface allows all transactional resources in the application to be grouped. The cicseci.rar resource adapter with xasupport enabled and with bean-managed transactions supports the UserTransaction and LocalTransaction interfaces.
The cicseci.rar resource adapter with xasupport disabled and bean-managed transactions supports the LocalTransaction interface. The cicseci.rar resource adapter with xasupport disabled and bean-managed transactions supports the LocalTransaction interface.
Nonmanaged mode
When the ECI resource adapter is used in nonmanaged mode, interactions with CICS will be non-transactional by default (synconreturn). Only the LocalTransaction interface is available for applications using nonmanaged mode, and any global transaction context, such as provided by the UserTransaction interface, will be ignored by the ECI resource adapter.
End of change

Restrictions on WebSphere Application Server for z/OS

On WebSphere Application Server for z/OS, you cannot use the local transaction interface if you have configured the ECI resource adapter to run in local mode. In this environment, if you plan to connect to CICS using the local protocol, do not attempt to get a LocalTransaction object from the connection (that is, do not call the method getLocalTransaction() on your connection object). In managed mode, attempts to call getLocalTransaction() result in a NotSupportedException being thrown. In nonmanaged mode, the results are unpredictable.

Samples

JEE ECI sample programs are provided in the <install_path>\samples subdirectory and as a deployable EAR file in the <install_path>\deployable subdirectory.

For more information, see Resource adapter samples.


Information Information

Feedback


Timestamp icon Last updated: Wednesday, 27 August 2014


https://ut-ilnx-r4.hursley.ibm.com/tgzos_latest/help/topic/com.ibm.cics.tg.zos.doc//progguide/topics/ccla215.html