>>-REQUESTMODEL(name)--GROUP(groupname)-------------------------> .-TRANSID(CIRP)--------. >--+-------------------+--+----------------------+--------------> '-DESCRIPTION(text)-' '-TRANSID(transaction)-' >--CORBASERVER(corbaserver)-------------------------------------> .-TYPE(GENERIC)--| Attributes for TYPE(GENERIC) |-. >--+-------------------------------------------------+--------->< +-TYPE(EJB)--| Attributes for TYPE(EJB) |---------+ '-TYPE(CORBA)--| Attributes for TYPE(CORBA) |-----' Attributes for TYPE(GENERIC) |--BEANNAME(*)--INTFACETYPE(BOTH)--INTERFACE(*)--MODULE(*)--OPERATION(*)--| Attributes for TYPE(EJB) |--+-BEANNAME(bean)--+-INTFACETYPE(BOTH)---+--+-OPERATION(operation)-+-+--| | +-INTFACETYPE(HOME)---+ '-OPERATION(*)---------' | | '-INTFACETYPE(REMOTE)-' | '-BEANNAME(generic bean)--INTFACETYPE(BOTH)--OPERATION(*)-----------' Attributes for TYPE(CORBA) |--+-+----------------+--+-INTERFACE(interface)--+-OPERATION(operation)-+-+-+--| | '-MODULE(module)-' | '-OPERATION(*)---------' | | | '-INTERFACE(*)--OPERATION(*)---------------------' | '-MODULE(generic module)--INTERFACE(*)--OPERATION(*)---------------------'
Acceptable characters:
You
can also use accented alphabetic characters. For information
about entering mixed case information, see Entering mixed case attributes. |
If you specify a generic value for BEANNAME, then you must specify INTFACETYPE(BOTH) and OPERATION(*).
For CORBA REQUESTMODELs—that is, if TYPE is CORBA—this field should be blank.
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
If a generic CORBASERVER is specified, BEANNAME, the CORBA attributes (MODULE and INTERFACE), and the COMMON attributes (OPERATION) must all be an asterisk (*); INTFACETYPE must be BOTH.
If any of the obsolete attribute values (OMGINTERFACE, OMGMODULE and OMGOPERATION) is present in the request model definition, CORBASERVER must be blank.
Acceptable characters:
Any
lower case characters you enter are converted to upper case. |
The GROUP name can be up to eight characters in length. Lowercase characters are treated as uppercase characters. Do not use group names beginning with DFH, because these characters are reserved for use by CICS.
For CORBA REQUESTMODELs—that is, if TYPE is CORBA—this field should be blank.
If any of the obsolete attribute values (OMGINTERFACE, OMGMODULE and OMGOPERATION) is present in the request model definition, INTFACETYPE must be blank.
Acceptable characters:
You
can also use accented alphabetic characters. For information
about entering mixed case information, see Entering mixed case attributes. |
Case is significant and should match the original Java or IDL source. However, to comply with CORBA, installation of REQUESTMODELS that specify INTERFACE with values differing only in case from previously installed definitions, will be rejected.
If a generic INTERFACE is specified, the common attributes (OPERATION) must be an asterisk (*).
For EJB REQUESTMODELs—that is, if TYPE is EJB—this field should be blank.
If any of the obsolete attribute values (OMGINTERFACE, OMGMODULE and OMGOPERATION) is present in the request model definition, INTERFACE must be blank.
Acceptable characters:
You
can also use accented alphabetic characters. For information
about entering mixed case information, see Entering mixed case attributes. |
Case is significant and should match the original Java or IDL source. However, to comply with CORBA, installation of REQUESTMODELS that specify MODULE with values differing only in case from previously installed definitions, will be rejected.
If you specify a generic value for MODULE, then you must specify INTERFACE(*) and OPERATION(*).
To indicate the default package, leave this field blank and specify a non-blank (but possibly generic) INTERFACE.
For EJB REQUESTMODELs—that is, if TYPE is EJB—this field should be blank.
If any of the obsolete attribute values (OMGINTERFACE, OMGMODULE and OMGOPERATION) is present in the request model definition, MODULE must be blank.
Acceptable characters:
You
can also use accented alphabetic characters. For information
about entering mixed case information, see Entering mixed case attributes. |
You can use the CREA supplied transaction to manage REQUESTMODEL definitions for enterprise beans. CREA creates REQUESTMODEL definitions with correctly-mangled method names in the OPERATION field.
For detailed information about how Java names are mapped to IDL names, see the OMG Java to IDL mapping, published by the Object Management Group (OMG), and available from www.omg.org.
If any of the obsolete attribute values (OMGINTERFACE, OMGMODULE and OMGOPERATION) is present in the request model definition, OPERATION must be blank.
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
The transaction definition must have as its initial program a JVM program whose JVMClass is com.ibm.cics.iiop.RequestProcessor. It must be installed in all the AORs of the logial EJB server; it need not be installed in listener regions that are not also AORs.
If any of the obsolete attribute values (OMGINTERFACE, OMGMODULE and OMGOPERATION) is present in the request model definition, TYPE must be blank.
TYPE(GENERIC) | TYPE(EJB) | TYPE(CORBA) | |
---|---|---|---|
BEANNAME | valid | valid | invalid |
INTFACETYPE | valid | valid | invalid |
MODULE | valid | invalid | valid |
INTERFACE | valid | invalid | valid |
OPERATION | valid | valid | valid |