Setting up the host system for IIOP

To support IIOP you need to perform the following system tasks:

  1. Giving CICS regions access to z/OS UNIX System Services and HFS directories and files. As part of this task, you will:
    1. Give CICS access to the HFS directories and files that are needed to create JVMs
    2. Create and give CICS access to the HFS working directory that you have specified for input, output, and messages from the JVMs
  2. Setting up JVM profiles and JVM properties files. During this task, you will:
    1. Enable CICS to locate JVM profiles and their associated JVM properties files.
    2. Choose appropriate JVM profiles for your CORBA stateless objects and enterprise beans.
    3. If necessary, customize the JVM profiles and JVM properties files to fit the requirements of your CICS region. (In the course of setting up CICS as a CORBA server, you will need to add some further information to the JVM properties files.)
    Bear in mind when reading Setting up JVM profiles and JVM properties files that, for CORBA stateless objects and enterprise beans:
    • The JVM profile used is that specified on the PROGRAM definition of the request processor program.
    • As for all CICS Java programs, the JVM properties file used is that specified on the JVM profile.
    • The default JVM profile, specified on the PROGRAM definition of the default request processor program, is DFHJVMCD.
    • The default JVM properties file, specified on the default JVM profile, DFHJVMCD, is dfjjvmcd.props.
    • If you plan to use the default JVM profile and JVM properties file with your CORBA stateless object and enterprise bean requests, then you need only to locate DFHJVMCD and dfjjvmcd.props and customize them for your CICS region, as described in Setting up JVM profiles and JVM properties files.

      If you plan to use customized JVM profiles or properties files, you should still make the changes to DFHJVMCD and dfjjvmcd.props that are required to fit with the setup of your CICS region, because DFHJVMCD is used internally by CICS, as well as being used for the default request processor program.

  3. Defining a shelf directory. The shelf directory is used for deployed JAR files.
  4. Defining name servers. This step is necessary only if you need to define name servers for the purposes described in that procedure.