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

116 CICS Transaction Gateway V5
SignonIncapable) are written to use the EPI support classes, and are available
with the additional materials for this book (see Appendix C, “Additional material”
on page 389). Both of these applications work with the CICS 3270 program,
EPIPROG, which is a very simple BMS-based application that returns a map
displaying the CICS region APPLID, date, time, and the user ID the task ran
under (Figure 6-7).
EPIPROG OUTPUT
APPLID: SCSCPJA4
DATE: 25/06/02
TIME: 00:45:38
USERID: CICSRS2
Figure 6-7 EPIP 3270 screen
The source code (EPIPROG), and the mapset (EPIPMAPS) for this application
are provided in the additional material available with this redbook, along with the
associated map class EPIMAPMap.java.
Signon capable terminals
When using the facilities of the EPI, the CICS TG creates a logical terminal in
CICS for you, which is then used to run the 3270 transaction. For an EPI
application to be able to start a secured CICS transaction on this terminal, it must
supply security credentials (a user ID and password) for the CICS server to
authenticate. There are two options available to do this:
► Sign on to the CICS terminal
The security credentials determined are established at sign-on (by starting a
transaction such as CESN). These credentials are then used for any
subsequent authorization checks when starting other transactions. The user
ID and password need not flow with further requests following the sign-on.
This requires a signon capable EPI terminal.
► Flow a user ID and password with each EPI request
A valid user ID and password must be flowed with each EPI request. This
method does not require the user to sign on to CICS, and so uses a signon
incapable EPI terminal.