A REQUESTMODEL resource defines how an Internet Inter-ORB Protocol
(IIOP) inbound request is mapped to the CICS® transaction that is to be initiated.
IIOP inbound requests may be:
- Client requests for enterprise beans
- Client requests for CORBA stateless objects
The inbound IIOP request is formatted according to CORBA standards; it
does not specify a CICS transaction name explicitly. REQUESTMODEL definitions
define templates that are compared with the inbound IIOP message to identify
the type of request. CICS uses the following attributes to select the request
model that most closely matches the inbound request:
- CORBASERVER
- TYPE
- BEANNAME
- INTFACETYPE
- MODULE
- INTERFACE
- OPERATION
For detailed information about how inbound requests are matched with
request models, see
Java™ Applications
in CICS.
The TRANSACTION attribute of the selected REQUESTMODEL specifies the name
of a CICS TRANSID, which associates the IIOP request with a set of execution
characteristics such as security, priority, and monitoring data.
Note: - You cannot install a REQUESTMODEL definition if the attributes used for
matching requests have identical values to a previously installed definition
with a different name. Upper case, lower case, and mixed case values of attributes
which are otherwise similar are considered to be identical.
If you try,
the install is rejected and a message is written to CSMT indicating the name
of the conflicting REQUESTMODEL.
- The following attributes were introduced in CICS Transaction Server for z/OS®, Version 2 Release 1:
- BEANNAME
- CORBASERVER
- INTFACETYPE
- INTERFACE
- MODULE
- OPERATION
- TYPE
If you specify any of these attributes in a request model definition,
then you cannot specify OMGMODULE, OMGINTERFACE, or OMGOPERATION. You can
install the definition in CICS Transaction Server for z/OS, Version 2 or
later, but not in CICS Transaction Server for OS/390®, Version 1 Release 3 The
following attributes, introduced in
CICS Transaction Server for OS/390, Version 1 Release 3,
are obsolete, but supported for compatibility purposes:
- OMGMODULE
- OMGINTERFACE
- OMGOPERATION
If you specify any of these attributes in a request model definition,
then you cannot specify BEANNAME, CORBASERVER, INTFACETYPE, MODULE, OPERATION,
or TYPE. You can install the definition in
CICS Transaction Server for OS/390, Version 1 Release 3 but
not in
CICS Transaction Server for z/OS, Version 2 or
later.
- The CORBA attributes (MODULE and INTERFACE) must specify the interface
which is directly implemented by the objects they are required to match (known
as the most derived interface). If you specify an interface which is
not the most derived interface, the CORBA attributes will not match requests
for objects that implement that interface.
Consider this example:
- Interface B is derived by inheritance from interface A.
- Object x implements interface B (and,
indirectly, interface A)
In this case, you must specify CORBA attributes which will match the
most derived interface (
B), and not interface
A.