Installing the CCI Connector sample

  1. If you have not already done so when running the CICSConnectionFactoryPublish and CICSConnectionFactoryRetract samples, add the JAR file containing the sample programs, /usr/lpp/cicsts/cicsts31/samples/cci/CICSCCISamples.jar, to the CLASSPATH statement in the JVM profile that the programs will use. As supplied, the sample programs use the CICS-supplied sample JVM profile DFHJVMPR, which is the default if no JVM profile is specified in the program's resource definition. CICS installs DFHJVMPR into the /usr/lpp/cicsts/cicsts31/JVMProfiles directory (where cicsts31 is the value of the CICS_DIRECTORY variable used by the DFHIJVMJ job during CICS installation).

    Place your edited version of DFHJVMPR in the HFS directory specified on the JVMPROFILEDIR system initialization parameter. (In a default CICS installation, JVMPROFILEDIR specifies /usr/lpp/cicsts/cicsts31/JVMProfiles.)

  2. Ensure that the connector.jar and dfjcci.jar files are in the “trusted middleware” classpath used by the JVM.
    Note: When you install CICS, connector.jar is installed into the %JAVA_HOME%/standard/jca directory and dfjcci.jar is installed into the /usr/lpp/cicsts/cicsts31/lib directory, as described in Compiling CCI applications. These directories are in the default trusted middleware classpath. Thus, assuming that your trusted middleware classpath is the same as, or based on, the default path, you shouldn't need to do anything.
  3. Ensure that the name server is running.
  4. Use the CICSConnectionFactoryPublish program to create a ConnectionFactory object for use by the CCI Connector for CICS® TS, and to publish it to the name server. See Publishing a connection factory using CICSConnectionFactoryPublish.
  5. Use CEDA to install transaction CCCI from group DFH$CCI.
  6. Use CEDA to install definitions of the CICS Java and COBOL programs. Install programs DFJ$CCIC and DFH0CCIS from group DFH$CCI.
    Note: If your CICS region uses program autoinstall, this step is not required.