CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

all the CICS regions with which your J2EE Server whishes to communicate. Full
details on how to configure EXCI connections are supplied in Chapter 4, “EXCI
connections to CICS” on page 65.
The main choice you must make is to decide if you will use a generic or specific
EXCI pipe to communicate with CICS. The default is to use a generic pipe (which
is basically an unamed pipe). If you wish to use a specific pipe you must define
the DFHJVPIPE environment variable in the J2EE Server instance that will be
used for the CICS connector support. This value must match the NETNAME
parameter of an installed EXCI CONNECTION definition in CICS.
We recommend using specific EXCI pipes, as this provides for better monitoring
and accounting within CICS. The same specific pipe can still be used by multiple
J2EE Server instances, to connect to the same CICS region so this does not limit
your ability to work with multiple J2EE Servers in a workload management
environment.
Defining the EXCI library to your J2EE Server
The J2EE Server that will use the CICS ECI resource adapter needs to access
and load the CICS module DFHXCSTB from the SDFHEXCI library supplied with
CICS. This library will typically be called CICSTS13.CICS.SDFHEXCI or
CICSTS22.CICS.SDFHEXCI, depending on the CICS release and naming
conventions you use.
To enable this you will need to complete one of the following steps:
► Add module DFHXCSTB to the LPA.
► Add the SDFHEXCI library to either the system linklist concatenation, or to
the STEPLIB concatenation of the J2EE Server.
We added our SDFHEXCI data set CICSTS22.CICS.SDFHEXCI to the STEPLIB
in the startup procedure of the J2EE Server instance.
Surrogate security profiles
As a user of the CICS TG and the EXCI, the J2EE Server will be subject to RACF
surrogate security checking. If surrogate security checking is enabled in
DFHXCOPT, the EXCI options table, the user ID of the EXCI job (in our case the
user ID of the J2EE Server region) will require read access to the
USERID.DFHEXCI SURROGAT class profile, where USERID is the user ID
flowed in the EXCI request. This authorizes the J2EE Server user ID to act as a
surrogate for the user ID specified by the clients that may invoke J2EE
applications. We defined the following profile, as we wished to give a universal
access of READ to all users (in effect disabling surrogate security) for testing
purposes:
RDEFINE SURROGAT *.DFHEXCI UACC(READ)OWNER (CICSRS1)
Chapter 10. CICS TG and WebSphere Application Server for z/OS 251