Use this update method when service outages can be tolerated
during the update process. No new CICS® resources
are created, but you might need to update the existing BUNDLE resource
definition.
Before you begin
To replace the CICS bundle
completely, an updated CICS bundle
that contains the new version of the OSGi bundle must be present in
zFS.
Procedure
To replace an existing OSGi bundle in an OSGi JVM server
with a new version of the OSGi bundle, use the following steps.
- In the Bundles view in CICS Explorer®, disable and discard
the BUNDLE resource for the CICS bundle
that you want to update. The OSGi services that are part of that CICS bundle are removed from the
OSGi framework and are not listed in the OSGi Services view
of CICS Explorer.
Note: No services that are implemented by the OSGi bundle are
available in the OSGi framework from this point until the completion
of step 3, so any users of these services suffer a service outage.
- Optional: Edit the BUNDLE resource definition
if the updated CICS bundle
is deployed in a different directory in zFS.
- In the Bundles view in CICS Explorer, install
the BUNDLE resource definition to pick up the changed OSGi bundle.
The OSGi bundles and services in the CICS bundle
are installed in the OSGi framework.
- Check the status of the OSGi bundle in the OSGi
Bundles view in CICS
Explorer. The new version of the OSGi bundle is listed with a
state of active.
- In the OSGi Services view in CICS Explorer, check that
the new version of all the OSGi services that are implemented by the
new version of the OSGi bundle are in the active state.
Results
The new version of the OSGi bundle is used for all new
service requests. Existing requests continue to use the old version.
The symbolic version of the OSGi bundle increases, indicating that
the Java™ code is updated.