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

340 CICS Transaction Gateway V5
Field Name Purpose
COMMAREA input commareaInput COMMAREA data
COMMAREA length commareaLength Length of the COMMAREA
Encoding encoding Encoding to convert data to before
sending and after receiving
Gateway daemon URL gatewayURL URL of the Gateway daemon to use
Gateway daemon port gatewayPort Port of the Gateway daemon
CICS Server server Server name as defined to the Client
daemon to use
User ID username User name to flow on the ECI request
Password password Password to flow on the ECI request
Mirror transaction mirror Transaction to use on the CICS server
Trace trace Whether to enable CICS TG Java client
trace
The action of the HTML form is to call the servlet CTGTesterECIServlet, using
the POST method to send the parameters. This means that the parameters are
sent in the HTTP request body. Because an HTTP POST request is intended to
affect some sort of change on the Web server, a Web browser will prompt to
resubmit the data if the user clicks Refresh on the results page. Conversely, the
GET method could be used, which sends the parameters on the HTTP request
URL. Because HTTP GETs are not intended to alter anything on the Web server,
the results page of such a request can be refreshed without a prompt being
shown.
Servlet
In the following section, we describe the major code sections in the
CTGTesterECIServlet servlet and how the servlet functions.
The servlet is defined to be in the package itso.cics.eci.testereci. Figure B-3
on page 341 shows the import statements used to give us access to the Java
packages used in the servlet. The import of javax.servlet and
javax.servlet.http give us access to the Java Servlet API set of classes; the
import of java.io, java.util and java.text are required for utility classes used
in the servlet; the import of com.ibm.ctg.client provides the CICS TG Java
class library.