Configuring the environments

sgc050


The EJB CICS sample application task guide

Set up a CICS TS 2.1 region as an EJB server

This section describes what you need to do to configure CICS as a CORBA participant. You will need to do this to run all IIOP based applications, including enterprise beans, since CICS uses the same RMI-over-IIOP protocol to support client method requests for both CORBA stateless objects and enterprise beans.

Assumptions

To configure CICS TS 2.1 as a CORBASERVER you need to perform the following CICS tasks:
  1. Define CICS startup jobstream
  2. Define CICS resources

Define CICS startup jobstream

  1. Set JCL parameters
  2. REGION
    1000M minimum is recommended

  3. Set parameters in the CICS system initialisation table
  4. EDSALIM
    500M minimum is recommended

    MAXOPENTCBS
    recommended value between 10 - 12

    TCP
    Set TCPIP to YES for every CICS region where the Listener is required.

  5. Set DD statements for CICS datasets
  6. DFHEJDIR
    A recoverable shared file containing the request streams directory. This can be a VSAM file or a coupling facility data table. CICS supplies sample JCL to help you create this file, in the DFHDEFDS member of the SDFHINST library.
    Sample: DFHEJDIR DD DISP=SHR,DSN=<name of file>:

    DFHEJOS
    A non-recoverable shared file used by CICS when CORBASERVERS are installed and to store stateful session beans that have been passivated. This can be a VSAM file or a coupling facility data table. CICS supplies sample JCL to help you create this file, in the DFHDEFDS member of the SDFHINST library.
    Sample: DFHEJOS DD DISP=SHR,DSN=<name of file>:

    Define the underlying VSAM data sets for DFHEJDIR and DFHEJOS. CICS supplies sample JCL to help you do this, in the DFHDEFDS member of the SDFHINST library.

Define CICS resources

The following CICS resources must be defined and installed:

  1. TCPSERVICE
  2. Define and install TCPIPSERVICE resource definitions in the Listener region for every port that the Listener will monitor. The well-known IIOP ports are 683(non-SSL) and 684(SSL) For each definition, set the attributes:

    TCPIPSERVICE: name of the resource definition
    GROUP: as required
    PORTNUMBER: The port or IP address on which CICS will listen for incoming IIOP requests (for example: 683, or 683 and 684)
    PROTOCOL: IIOP
    TRANSACTION: The CICS transaction to start when a request arrives. The CICS IIOP Request Receiver transaction, CIRR, is inserted by default when IIOP is specified as the protocol.

    For example:
    DEFINE TCPIPSERVICE(name) 
         GROUP(name)                      
         IPADDRESS(ip address)
         PORTNUMBER(683) 
         TRANSACTION(CIRR)
         PROTOCOL(IIOP)                         
    
    Default definitions for the following CICS resources, to include in DFHLIST, are supplied in Group DFHIIOP.

  3. CORBASERVER
  4. Define and install a CORBASERVER resource definition to activate the appropriate request processor to execute the IIOP request.
    Note: the DFHEJDIR file must be defined, installed and available before a CORBASERVER can be installed. For the sample CORBASERVER definition set:

    CORBASERVER: CSV1
    GROUP: DFHIIOP
    JNDI PREFIX: SAMP
    SESSBEANTIME: 00,01,00
    SHELF: the path to the shelf root directory that you created in Define shelf directory. Default: /var/cicsts.
    HOST: IP address of the CICS region
    PORT:07873
    SSL:NO
    SSLPORT:NO

    For example:
    DEFINE CORBASERVER(CSV1) 
         GROUP(DFHIIOP)                      
         JNDIPREFIX(SAMP) 
         SESSBEANTIME(00,01,00)
         SHELF(/var/cicsts)
         HOST(ip address)
         PORT(07873)
         SSL(NO)
         SSLPORT(NO)
    

    The attributes of CORBASERVER definition: HOST, SSL, and PORT or SSLPORT must match the corresponding attributes of the TCPIPSERVICE definition:

    CORBASERVER TCPIPSERVICE
    HOST IPADDRESS or DNSGROUP
    SSL SSL
    PORT or SSLPORT PORTNUMBER

  5. PROGRAM
  6. Define and install PROGRAM definitions for the CICS supplied request receiver and request processor programs. Sample resource definitions are supplied in group DFHIIOP.
    Request Receiver PROGRAM definition
    The default request receiver program--named by the default CIRR transaction on REQUESTMODEL definitions--is DFJIIRRS. CIRR and DFJIIRRS are defined in the supplied resource definition group DFHIIOP.

    The following DFHJIIRRS sample definition is supplied in group DFHIIOP:

    DEFINE PROGRAM(DFHIIRRS)       GROUP(DFHIIOP)                          
    DESCRIPTION(CICS IIOP Request Receiver)                         
                  JVM(NO)                                                         
                  JVMCLASS()                     
                  LANGUAGE(Assembler)
                  RELOAD(NO) 
                  EXECKEY(CICS)      
                  RESIDENT(NO)  
                  USAGE(NORMAL)   
                  USELPACOPY(NO)     
                  STATUS(ENABLED) 
                  CEDF(NO)      
                  DATALOCATION(ANY)  
                  DYNAMIC(NO)
    
    Request Processor PROGRAM definition
    The default request processor program--named by the default CIRP transaction on REQUESTMODEL definitions--is DFJIIRP. CIRP and DFJIIRP are defined in the supplied resource definition group DFHIIOP.

    The following DFHJIIRP sample definition is supplied in group DFHIIOP:

    DEFINE PROGRAM(DFJIIRP)       GROUP(DFHIIOP)                          
    DESCRIPTION(CICS IIOP Request Processor)                         
                  JVM(YES)                                                         
                  JVMCLASS(com.ibm.cics.iiop.RequestProcessor)                     
                  LANGUAGE(LE370)
                  RELOAD(NO) 
                  EXECKEY(USER)      
                  RESIDENT(NO)  
                  USAGE(NORMAL)   
                  USELPACOPY(NO)     
                  STATUS(ENABLED) 
                  CEDF(NO)      
                  DATALOCATION(ANY)  
                  DYNAMIC(NO)
    

    The PROGRAM definition for the request processor can have any name, but the JVMCLASS parameter must be set to com.ibm.cics.iiop.RequestProcessor
    If you are not using the default JVM profile DFHJVMPR you must specify the name of your JVM profile on the JVMPROFILE option of the PROGRAM definition.

  7. TRANSACTION
  8. Define and install TRANSACTION definitions for the CICS supplied request receiver and request processor programs. Sample resource definitions are supplied in group DFHIIOP.
    Request Receiver TRANSACTION definition
    The TRANSACTION definition for the request receiver must be CIRR.

    The following default definition is supplied in DFHIIOP:

    DEFINE TRANSACTION(CIRR)      GROUP(DFHIIOP)                      
                  PROGRAM(DFHIIRRS)      TWASIZE(0)                           
                  PROFILE(DFHCICST)      STATUS(ENABLED)                      
                  TASKDATALOC(ANY)       TASKDATAKEY(USER)                    
                  RUNAWAY(SYSTEM)        SHUTDOWN(ENABLED)                    
                  PRIORITY(1)            TRANCLASS(DFHTCL00)                  
                  DTIMOUT(NO)            TPURGE(NO)                           
                  SPURGE(YES)            ISOLATE(NO)                          
                  RESSEC(NO)             CMDSEC(NO)                           
                  RESTART(NO)                                                 
                  DESCRIPTION(Default CICS IIOP Request Receiver transaction) 
    
    Request Processor TRANSACTION definition
    The TRANSACTION definition for the request receiver must be CIRP.

    The following default definition is supplied in DFHIIOP:

    DEFINE TRANSACTION(CIRP)      GROUP(DFHIIOP)                      
                  PROGRAM(DFJIIRP)       TWASIZE(0)                           
                  PROFILE(DFHCICST)      STATUS(ENABLED)                      
                  TASKDATALOC(ANY)       TASKDATAKEY(USER)                    
                  RUNAWAY(SYSTEM)        SHUTDOWN(Disabled)                    
                  PRIORITY(1)            TRANCLASS(DFHTCL00)                  
                  DTIMOUT(NO)            TPURGE(NO)                           
                  SPURGE(YES)            ISOLATE(YES)                          
                  RESSEC(YES)            CMDSEC(YES)                           
                  RESTART(NO)                                                 
                  DESCRIPTION(Default CICS IIOP Request Processor transaction) 

  9. FILE
  10. Provide and install FILE resource definitions for the DFHEJDIR and DFHEJOS files. There are (DFHEJVS, DFHEJCF, and DFHEJVR are not included in the default CICS startup group list, DFHLIST.)

    Note: the DFHEJDIR file must be defined, installed, and available before the CORBASERVER definition can be installed.