Defining deployed JAR files using the CICS scanning mechanism

To cause deployed JAR files to be defined and installed into a CorbaServer by the CICS scanning mechanism, place them in the CorbaServer's deployed JAR directory. (The deployed JAR directory is specified by the DJARDIR option of the CORBASERVER definition. It is also known as the “pickup” directory.) When the CorbaServer is installed, CICS scans the pickup directory and automatically installs any deployed JAR files it finds there. (This automatic scan occurs regardless of whether the CorbaServer is installed in enabled or disabled state.)

CICS assumes that a file is a deployed JAR if:
  1. It has a suffix of .jar (in lowercase).
  2. Its base filename is between 1 and 32 characters long. By “base filename” we mean the part of the filename before the suffix, and excluding any file path. For example, the base filename of the file djardir\myDeployedJar.jar is myDeployedJar.
CICS copies any deployed JAR files it finds in the pickup directory to its shelf directory and dynamically creates and installs DJAR definitions for them. The name of the DJAR definition is the name of the deployed JAR file on HFS. For example, a deployed JAR file named /var/cicsts/pickup/TheThreeBears.jar results in a DJAR definition named TheThreeBears.
After the CorbaServer has been installed, you can:

To determine which DJAR resources have been dynamically installed by the scanning mechanism and which statically installed from a CSD or by means of CREATE DJAR, look at the value of the HFSFILE field returned on an INQUIRE DJAR command. If the DJAR has been dynamically installed, the value will begin with the CorbaServer's pickup directory. (You should not put statically-installed deployed JAR files in the pickup directory.) A DJAR name longer than 8 characters will also indicate a dynamically-installed resource.