Defining bundle dependencies

You can define the dependencies for a CICS® bundle by editing the bundle manifest file (cics.xml) with the Bundle Manifest editor.

About this task

You can add bundle dependencies as imports in the manifest file. Bundle dependencies are CICS resources that typically must be present in the CICS region for the BUNDLE resource to install in an enabled state. For example, you can specify that a TCPIPSERVICE must be available before the BUNDLE resource can be enabled.

You can make imports optional, so that the BUNDLE resource always installs in an enabled state even if the dependency is not met.

Procedure

  1. Navigate to the META-INF folder of the bundle you want to work with.
  2. Double-click the cics.xml manifest file. The Bundle Manifest editor opens and displays all of the current resources that are required for this bundle, including the ID and version of the bundle.
  3. Click Add. The import properties dialog opens.
  4. Enter the resource type in the CICS resource type list. You can press Ctrl + Space to display content assistance.
  5. Enter a name for the resource.
  6. Select whether the import is required or optional before the BUNDLE resource can be enabled. The default behavior is that the import is required and the BUNDLE resource cannot be enabled until the dependency is met. If you select Optional, the BUNDLE resource is installed even if the dependency is not met in the CICS region.
  7. Click OK. The resource is added to the list of imported resources that are required by this bundle.
  8. Click Save.

Results

You have defined the CICS resources that are required by the CICS bundle.

What to do next

You can add CICS resources to the Bundle project. These resources are created dynamically when the BUNDLE resource is installed in the CICS region.