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

1. SC62PJA1 -CICSTS 2.2 AT SC66
2. SCSCPJA4 -CICSTS 2.2 AT SC66
Choose Server to connect to, or q to quit:
2
Enter your CICS User ID:
CICSRS2
Enter your CICS Password:
PASSWORD
Program EC01 returned with data:-
Hex: 32332f30362f30322031303a35373a34370
ASCII text: 23/06/02 10:57:47
6.2.3 EPI to CICS TG for Windows (TCP62)
In this example, we show you how we configured security to allow an EPI-based
Java application to make an authenticated call to CICS using the facilities of the
CICS TG for Windows, using a TCP62 connection to our CICS TS V2.2 region
(Figure 6-6). Since we were using the EPI to access a 3270-based CICS
transaction, we decided to use the TCP62 communication protocol, since EPI is
not supported either by the CICS TCP/IP protocol or by the CICS TG for z/OS.
Windows client
Java
application
Port
2006
Windows 2000
volga
CICS TG V4.0.2
Gateway
daemon
Figure 6-6 EPI to CICS TG for Windows, security scenario
JNI
Client
daemon
EPI request
TCP62
user ID +
password
Virtual
terminal
z/OS
CICS TS V2.2
Region
SCSCPAA6
RACF
Unlike the previous ECI examples, we decided to write our own test applications,
because we wanted to show the difference between signon capable and signon
incapable terminals. Our sample Java applications (SignonCapable and
EPIP
Chapter 6. CICS TG security scenarios 115