Updating Java EE applications in a Liberty JVM server

There are three methods to update Java™ EE applications in a Liberty JVM server: refresh the CICS® bundles, update the applications in the drop-ins folder, and use <application> elements.

About this task

The process to update Java EE applications in a Liberty server depends on how the applications are deployed:

Applications deployed in CICS bundles
In this scenario, the application must be added as a bundle part to a CICS bundle project using CICS Explorer® and then exported to z/OS® File System (zFS). It is then installed into CICS using a BUNDLE definition that refers to the exported project.
Applications deployed directly to the Liberty drop-ins folder
In this scenario, the Java archive is copied directly to a previously defined drop-ins directory.
Applications deployed in an <application> element into server.xml
In this scenario, a reference to the application is added into server.xml, together with further application attributes and descriptive elements.

Procedure

Applications deployed in CICS bundles

To refresh the CICS bundle, a bundle that contains the Java EE application must already be installed and enabled in the CICS region. For more information, see Deploying a Java EE application in a CICS bundle to a Liberty JVM server.
1. In the Bundles view in CICS Explorer, disable the BUNDLE resource for the CICS bundle that you want to update.
  
  Note: The applications that are part of that CICS bundle are removed from the Liberty server run time and are not available from this point until the last step completes. Any users of these services suffer a service outage.
2. Export the new version of the CICS bundle that contains the Java EE application to the same zFS location as the old version.
3. In the Bundles view in CICS Explorer, enable the BUNDLE resource definition to pick up the Java EE application. The applications are reinstalled into the Liberty server.
4. Check the status of the CICS bundle in CICS Explorer. The CICS bundle is listed with a state of active.
When the new version of the Java EE application becomes active, it is used for all new requests.

Applications deployed directly to the Liberty drop-ins folder

To use the drop-ins directory with a Liberty server, the server.xml configuration must be updated to enable this function. For more information, see Deploying Java EE applications directly to a Liberty JVM server.
1. Export the new version of the archive (WAR, EAR, or EBA) from your Eclipse environment.
  
  Note: The applications that are part of that CICS bundle are removed from the Liberty server run time. Any users of these services suffer a service outage.
2. Copy this new archive into the drop-ins directory, replacing the original version.
  
  The Liberty server scans the directory, uninstalls the previous version, and installs the new version.
When the new version of the Java EE application becomes active, it is used for all new requests.

Applications deployed in an <application> element into server.xml

To allow applications to be dynamically updated, the updateTrigger attribute of the <applicationMonitor> element must be set to polled. For more information, see Controlling dynamic updates.
1. Export the new version of the archive (WAR, EAR, or EBA) from your Eclipse environment.
  
  Note: The applications that are part of that CICS bundle are removed from the Liberty server run time. Any users of these services suffer a service outage.
2. Copy this new archive into the location specified in your <application> element.
  
  The Liberty server scans the file for modification and if a change is detected, it uninstalls the previous version and installs the new version.
When the new version of the Java EE application becomes active, it is used for all new requests.