A DJAR defines an instance of a deployed JAR file, which contains enterprise beans.
The definition identifies a particular instance of a deployed JAR file (in the sense that it is valid to have multiple versions of the same deployed JAR file deployed in different CorbaServers in the same region). The DJAR definition also associates the JAR file instance with its execution environment, the CorbaServer.
A deployed JAR file is an ejb-jar file, containing enterprise beans, on which code generation has been performed and which has been stored on the hierarchical file system (HFS) used by z/OS®. When the DJAR definition is installed, CICS® copies the deployed JAR file (specified by HFSFILE) into a subdirectory of the HFS shelf directory of the specified CORBASERVER.
Usually, you do not have to code DJAR definitions by hand. Typically, they are created dynamically, by the CICS scanning mechanism.