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

258 CICS Transaction Gateway V5
you still need to deploy an application to make use of this support. This is
described in the next section.
10.2.5 Deploying our sample enterprise applications
EAR files generated in WebSphere Studio cannot be directly deployed to
WebSphere Application Server for z/OS. You must use the Application Assembly
Tool (AAT) for z/OS to generate an EAR file that WebSphere can use. Using the
AAT for z/OS also gives you the opportunity to change some deployment
information. We downloaded the AAT for z/OS from the following Web site:
https://www6.software.ibm.com/dl/websphere20/zosos390-p
In this section, we used our sample J2EE enterprise application CTGTesterCCI.
The source code for this application is provided in the additional material for this
book. See Appendix C, “Additional material” on page 389.
Deploying the enterprise application
1. Start the AAT for z/OS by clicking Start -> Programs -> IBM WebSphere for
z/OS -> Application Assembly. In the left pane, right-click Applications and
select Import. Specify the location of the CTGTesterCCI.ear, and click OK.
The file should import successfully.
Next, you will probably receive a few pop-up windows warning about missing
classes (as shown in Figure 10-13). The first one of these was for
javax.resource.ResourceException, to which we answered Yes. We were
then required to select the JAR file containing this class (connector.jar) to be
added to our EAR file. This is because our application was designed to throw
a ResourceException and so this class is needed to generate the deployment
code. To all the other questions we replied No, because we wanted to have
the classes taken from the WebSphere runtime environment, as otherwise we
found that we could have class loader problems.
Important: It is possible to circumvent these errors by adding the JARs to
the variable USER_AAT_CLASSPATH.
Figure 10-13 AAT file import