As explained in
Enabling applications to use a JVM, for CORBA stateless objects and
enterprise beans, you need to include the following items on the shareable
application class path that will be used for the request processor program:
- The JAR files for CORBA stateless objects.
- Any classes, such as classes for utilities, that are used by CORBA stateless
objects or enterprise beans, but are not included in the JAR files.
You do not need to include the deployed JAR files (DJARs) for enterprise
beans on the class path.
Specify these items on the shareable application class path by using the
ibm.jvm.shareable.application.class.path system property that will be
used by the JVM for the request processor program. This means that:
- If the JVM for the request processor program is a standalone JVM that
does not use the shared class cache, then use the ibm.jvm.shareable.application.class.path system property in the JVM properties file that is referenced by the
JVM profile named in the JVMPROFILE option of the PROGRAM definition for the
request processor program. For example, if your CORBA stateless objects or
enterprise beans use the default request processor program DFJIIRP (which
is named by the default CIRP transaction on REQUESTMODEL definitions), and
DFJIIRP is set to use the JVM profile DFHJVMCD (which is the default JVM profile
for CICS-supplied system programs), then you need to specify the paths to
the classes in the JVM properties file dfjjvmcd.props (which is
the JVM properties file referenced by DFHJVMCD).
- If the JVM used by the request processor program is a worker JVM that
uses the shared class cache, then use the ibm.jvm.shareable.application.class.path system property in the JVM properties file that is referenced by the
JVM profile for the master JVM that initializes the shared class cache. For
example, take the case where you have created a request processor program
that uses the JVM profile DFHJVMPC (a JVM profile for JVMs that use the shared
class cache), so that your CORBA stateless objects or enterprise beans use
the shared class cache, and your master JVM uses the JVM profile DFHJVMCC
(which is the default JVM profile for a master JVM). In this situation, you
need to specify the paths to the classes in the JVM properties file dfjjvmcc.props, which is the JVM properties file referenced by DFHJVMCC,
instead of in the JVM properties file dfjjvmpc.props, which is
referenced by DFHJVMPC.
When you are adding these items to the shareable application class path,
remember:
- The name of the class itself is not actually specified. The options in
a JVM profile or JVM properties file specify the path to
the class—that is, the full path of the HFS directory in which a class
loader will be able to find the class or the package containing the class.
Where classes or packages have been placed in JAR files (with the extension
.jar), this means that you need to include the name of the JAR file on the
class path as if it were the name of a directory. (Remember that deployed JAR files do not need to be placed on a class path.) If you
need to add any utility classes, see the guidance given earlier in Adding application classes to the class paths for a JVM.
- Use a colon as the separator between paths that you specify on a class
path. (This is defined by the path.separator system property for
the JVM, which you can change.) To include line breaks, use a backslash and
a blank (\ ). “Rules for coding JVM profiles and
JVM properties files” in the CICS® System Definition Guide has a full explanation of
how to code class paths and other items in a JVM profile or JVM properties
file.