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

Since we are using a session bean in a managed environment, several of the
options are now set on the managed connection factory, so it was necessary to
modify only the following parameters:
CICS program name ECIPROG2
COMMAREA length 35
Encoding IBM037
We clicked Submit and received the output HTML form shown in Figure 10-29.
Figure 10-29 CTGTesterCCI response page
The output from ECIPROG2 shows that the request ran successfully in our
secure CICS region SCSCPJA4, and this time ran under the flowed user ID
CICSRS2. This is the client user ID authenticated by the HTTP Server using the
%%CLIENT%% setting in the protection directive. The message DFHSN1400 in the
CICS MSGUSER log also showed that the link user ID was again CBASRU2, the
user ID of the J2EE Server region.
Chapter 10. CICS TG and WebSphere Application Server for z/OS 279