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

The page then includes our common JSP header, which displays the information
specified in the initial form, such as trace level and number of iterations. The rest
of the page then outputs the values of the request attributes using the scriptlet
format , shown in Figure B-44. In our application, the
JavaBean component encoding contains the encoding used to convert the input
COMMAREA into bytes, and is inserted into the HTML output with the JSP
scriplet .
Results COMMAREA
Input:
Output using :
Output using default encoding:
Output in HEX:
Figure B-44 Outputting the results into the HTML
The results page outputs the COMMAREA data converted to a String using the
JVM default encoding, the encoding specified in the form and in a hexadecimal
representation.
error.jsp
The JSP error.jsp is used when an error occurs inside the CICS ECI resource
adapter or our code, resulting in an exception being thrown. It does not display
the output COMMAREA. Instead, it displays the contents of the exception that
occurred and any errors found in the processing of the form parameters by the
servlet.
Application XML
The XML that describes the enterprise application can be examined from within
WebSphere Studio.
Web deployment descriptor
To view the Web application XML, perform the following steps from WebSphere
Studio:
1. From J2EE Perspective Navigator, right-click CTGTesterCCIWeb and select
Edit Deployment Descriptor.
This displays the Web deployment descriptor editor's General tab. Click the
Servlets tab to show the Servlets pane. Click CTGTesterCCIServlet in the
Servlets list (Figure B-45 on page 378).
Appendix B. Sample applications 377