Updating Java EE applications in a Liberty JVM server
There are three methods to update Java™ EE applications in a Liberty JVM server - refreshing the CICS® bundles, updating the applications in the drop-ins folder, and using <application> elements.
About this task
The process for updating 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 along with further application attributes and descriptive elements.
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 .
- 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 completion of step four. Any users of these services suffer a service outage.
- Export the new version of the CICS bundle containing the Java EE application to the same zFS location as the old version.
- 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.
- Check the status of the CICS Bundle in CICS Explorer. The CICS bundle is listed with a state of active.
The new version of the Java EE application is used for all new requests, when it becomes active.
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 .
- 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.
- Copy this new archive into the drop-ins directory, replacing the original version.
The Liberty server scans the directory and uninstalls the previous version and installs the new version.
The new version of the Java EE application is used for all new requests, when it becomes active.
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.
- 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.
- 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.
The new version of the Java EE application is used for all new requests, when it becomes active.