Deploying an Enterprise Java application in a CICS bundle to a Liberty JVM server

You can deploy an Enterprise Java application that is packaged as a CICS® bundle in a Liberty JVM server.

1. Create a BUNDLE resource that specifies the directory of the bundle in zFS. Creating a BUNDLE resource causes all associated BUNDLEPARTs to be installed.
   When a WAR, EAR or EBA BUNDLEPART is installed into a Liberty JVM server, an application element is added to the ${server.config.dir}installedApps.xml, and the application file is copied from the BUNDLEDIR into the ${server.config.dir}/installedApps directory. A BUNDLE resource can be created through the following interfaces.
   • CREATE BUNDLE
   • CEDA DEFINE and INSTALL commands
   • CICS Explorer as defined in the substeps
   • How it works: CICS bundle deployment APICICS bundle deployment API
   1. In the CICS SM perspective in CICS Explorer, click Definitions > Bundle Definitions in the CICS Explorer menu bar to open the Bundles Definitions view.
   2. Right-click anywhere in the view and click New to open the New Bundle Definition wizard.
      Enter the details for the BUNDLE resource in the wizard fields.
   3. Install the BUNDLE resource.
2. Optional: Enable the BUNDLE resource to start the Enterprise Java applications in the Liberty server, if the resource was created in the DISABLED state. When the bundle is ENABLED, the Liberty application is started.
3. Inquire the BUNDLE resource to check the state of the bundle resource.
   • When the BUNDLE resource is in an ENABLING state, CICS is starting all the resources in the bundle. The BUNDLE remains in an ENABLING state when one or more Liberty applications included in the bundle are still installing or starting.
   • When the BUNDLE resource is in an ENABLED state, CICS started all the resources in the bundle successfully and all Liberty applications that are included in the bundle start.
   • When the BUNDLE is in a DISABLING state, CICS is stopping all the resources in the bundle. The BUNDLE remains in a DISABLING state when one or more Liberty applications included in the bundle are still stopping.
   • When the BUNDLE resource is in a DISABLED state, CICS stopped all resources in the bundle, or detected that one or more of the Liberty applications stopped. When a BUNDLE moves from an ENABLING state into a DISABLED one, a Liberty application in the bundle might of failed to start, or the application did not install in Liberty before the timeout. The timeout is configured by the JVM system property com.ibm.cics.jvmserver.wlp.bundlepart.timeout.
   1. In CICS Explorer, click Operations > Bundles in the CICS Explorer menu bar to open the Bundles view. Check the state of the BUNDLE resource.
   If the BUNDLE resource failed to install in the enabled state, check the bundle parts for the BUNDLE resource. If any of the bundle parts are in the UNUSABLE state, a message is issued to explain the cause of the problem. For example, this state can indicate that a problem with the CICS bundle in zFS, or the associated JVMSERVER resource is not available. You must discard the BUNDLE resource, resolve the reported issue, and then install the BUNDLE resource again.
4. Optional: To run Enterprise Java application requests on an application transaction, you can create URIMAP and TRANSACTION resources.
   Defining a URI map is useful if you want to control security to the application, because you can map the URI to a specific transaction and use transaction security. Typically, these resources are created as part of the CICS bundle and are managed with the application. However, you can choose to define these resources separately if preferred.
   1. Create a TRANSACTION resource for the application that sets the PROGRAM attribute to DFHSJTHP.
      This CICS program handles the security checking of inbound Enterprise Java requests to the Liberty JVM server. If you set any remote attributes, they are ignored by CICS because the transaction must always attach in the local CICS region.
   2. Create a URIMAP resource that has a USAGE type of JVMSERVER. Set the TRANSACTION attribute to the name of the application transaction and set the SCHEME attribute to HTTP or HTTPS.
      You can also use the USERID attribute to set a user ID. This value is ignored if the application security authentication mechanisms are used. If no authentication occurs and no user ID is set on the URI map, the work runs under CICS default user ID.