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

240 CICS Transaction Gateway V5
and CTGTesterCCI) can also convert the input and output data to and from
EBCDIC, defining a data conversion template is optional in this case.
WebSphere configuration
We configured our WebSphere environment to use two different HTTP protocol
catchers, the HTTP Transport Handler function of the WebSphere J2EE Server
and the IBM HTTP Server (see Figure 10-2 on page 241).This means we had
two different processes listening on two different ports, but both of them could
forward HTTP requests into the Web container in the J2EE Server to run our
applications. You will probably need to only use one of the protocol catchers but
we had both configured for test purposes. The primary differences between the
two protocol catchers are as follows:
► HTTP Transport Handler
– Streamlined HTTP listener implemented as a function of the J2EE Server.
– Does not currently support authentication either via HTTPS or via HTTP
basic authentication.
► HTTP Server
– Uses the HTTP Server address space in conjunction with the WebSphere
plugin (as previously used in WebSphere Application Server V3.5).
– Supports HTTP basic authentication, and HTTPS including client
authentication.
Note: Since HTTP basic authentication was not currently supported with the
HTTP Transport Handler at the time of writing this redbook, we used the HTTP
Server environment to demonstrate how to flow the security context from the
client through to our CICS region (see 10.3.2, “HTTP Server and basic
authentication testing” on page 274).
However, subsequent to writing this book, basic authentication and HTTPS
support (not including client authentication) was implemented by the J2EE
Server in APAR PQ59911, and we advise you to use this function if you
require Web client authentication.