Recovering resources in the Liberty JVM server
Using Java™ Transaction API (JTA) to coordinate transactional updates. CICS® recoverability options are limited for local and remote transactions.
JTA can be used in a Java Web application to coordinate transactional updates to CICS resources and other third party XA resource managers. See Java Transaction API (JTA).
In this scenario the Liberty transaction manager is the transaction coordinator and stores its recovery information in the JTA transaction log on the zFS filing system. On an emergency restart, the JVM server will automatically be reinstalled and the Liberty transaction manager will initiate XA transaction recovery as soon as the JVM server initialization is complete. This process will ensure that any indoubt units-of-work in CICS and transactions in third party resource managers are recovered.
The integrity of both the CICS system log and the Liberty transaction log is critical in enabling CICS to perform successful recovery if the Liberty JVM server fails whilst recoverable updates are still in-flight. Manually tailoring server.xml tells you more about how to configure a Liberty JVM server, and how to control the location of the zFS directory used to store the Liberty transactional log. The CICS system log documentation provides information on setting up the CICS system log.