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

Results with J2EE application
Next we used our J2EE application, CTGTesterCCI, to call the CICS program
EC01, using the CICS TG ECI resource adapter and the connection factory we
set up previously. This used a local CICS TG (Figure 11-24).
Web browser
IBM
HTTP
Server
Windows
WebSphere AE
CTGTesterCCI
ECI
resource
adapter
local:
CICS TG
Client
daemon
TCP/IP
TCP/IP
Figure 11-24 WebSphere with CTGTesterCCI using local CICS TG
z/OS
CICS Transaction
Server region
SCSCPJA1
To verify this configuration we performed the following steps:
1. We verified that the IBM HTTP Server was running using the steps detailed in
the previous section.
2. We verified that the WebSphere default server was running and that our
application CTGTesterCCI was running using the steps detailed in the
previous section.
3. We opened our Web browser and loaded the welcome page of the
CTGTesterCCI application using the URL http://volga/CTGTesterCCIWeb/.
This displayed the page shown in Figure 11-25 on page 314. The default
parameters were set up to cause the CTGTesterCCI application to make an
ECI call to EC01 on a CICS region, using the ECI resource adapter. The ECI
resource adapter was configured to use the local: protocol and the server
SCSCPJA1, defined in “Configure a connection factory” on page 297.
EC01
volga wtsc66oe.itso.ibm.com
Chapter 11. CICS TG and WebSphere Application Server for Windows 313