Examples

Figure Figure 1 shows an example of an enterprise bean-specific REQUESTMODEL definition.
Figure 1. Example of an enterprise bean-specific REQUESTMODEL definition
 Requestmodel   : DFH$EJB
 Group          : DFH$EJB
 Description  ==> EJB HelloWorld sample
 Corbaserver  ==> EJC1
 TYpe         ==> Ejb                Corba | Ejb | Generic
EJB PARAMETERS
 Beanname     ==> HelloWorld
 (Mixed Case) ==>
              ==>
              ==>
 INTFacetype  ==> Both               Both | Home | Remote 
CORBA PARAMETERS
 Module       ==> 
 (Mixed Case) ==>
              ==>
              ==>
 INTErface    ==> 
 (Mixed Case) ==>
              ==>
              ==>
COMMON PARAMETERS
 OPeration    ==> *
 (Mixed Case) ==>
              ==>
              ==>
TRANSACTION ATTRIBUTES
 TRansid      ==> EJHE
CICS TS V1R3 ATTRIBUTES
 OMGModule      :
 OMGInterface   :
 OMGOperation   :
Note: The transaction definition for EJHE should be copied from that of CIRP. Any attributes of the transaction definition can be changed except the program name, which must be that of a JVM program whose JVMClass is com.ibm.cics.iiop.RequestProcessor.
Figure Figure 2 shows an example of a stateless CORBA REQUESTMODEL.
Figure 2. Example of a stateless CORBA REQUESTMODEL
 Requestmodel   : DFH$IIRH
 Group          : DFH$IIOP
 Description  ==> Hello world CORBA Java server sample
 Corbaserver  ==> IIOP
 TYpe         ==> Corba              Corba | Ejb | Generic
EJB PARAMETERS
 Beanname     ==> 
 (Mixed Case) ==>
              ==>
              ==>
 INTFacetype  ==>                    Both | Home | Remote 
CORBA PARAMETERS
 Module       ==> hello
 (Mixed Case) ==>
              ==>
              ==>
 INTErface    ==> HelloWorld
 (Mixed Case) ==>
              ==>
              ==>
COMMON PARAMETERS
 OPeration    ==> *
 (Mixed Case) ==>
              ==>
              ==>
TRANSACTION ATTRIBUTES
 TRansid      ==> IIHE
CICS TS V1R3 ATTRIBUTES
 OMGModule      :
 OMGInterface   :
 OMGOperation   :
Note: The transaction definition for IIHE should be copied from that of CIRP. Any attributes of the transaction definition can be changed except the program name, which must be that of a JVM program whose JVMClass is com.ibm.cics.iiop.RequestProcessor.
Figure Figure 3 shows an example of a generic definition that matches any enterprise bean or stateless CORBA object request. This example changes the default request processor transaction from CIRP to EJB1.
Figure 3. Example of a generic definition that matches any enterprise bean or stateless CORBA object request
 Requestmodel   : GENERIC
 Group          : TEST
 Description  ==> Generic default definition
 Corbaserver  ==> *
 TYpe         ==> Generic            Corba | Ejb | Generic
EJB PARAMETERS
 Beanname     ==> *
              ==>
              ==>
              ==>
 INTFacetype  ==> Both               Both | Home | Remote 
CORBA PARAMETERS
 Module       ==> *
              ==>
              ==>
              ==>
 INTErface    ==> *
              ==>
              ==>
              ==>
COMMON PARAMETERS
 OPeration    ==> *
              ==>
              ==>
              ==>
TRANSACTION ATTRIBUTES
 TRansid      ==> EJB1
CICS TS V1R3 ATTRIBUTES
 OMGModule      :
 OMGInterface   :
 OMGOperation   :
Note: The transaction definition for EJB1 should be copied from that of CIRP. Any attributes of the transaction definition can be changed except the program name, which must be that of a JVM program whose JVMClass is com.ibm.cics.iiop.RequestProcessor.