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

310 CICS Transaction Gateway V5
Example 11-1 Viewing the status of the Client daemon connection
C:\>CICSCLI -L
CCL8001I CICSCLI - CICS Client Control Program
CCL0002I (C) Copyright IBM Corporation 1994,2001. All rights reserved.
CCL8041I The CICS Client is using the following servers:
CCL8042I Server 'SCSCPJA1' (using 'TCPIP' to 'wtsc66oe.itso.ibm.com') is
available
For more details on configuring the TCP/IP protocol with the CICS TG, refer
to Chapter 5, “TCP/IP connections to CICS” on page 81.
4. To start our WebSphere Application Server, we selected Start -> Programs
-> IBM WebSphere -> Application Server V4.0 AE -> Start Admin Server.
We also started the administrative console to allow us to view the status of the
resources in our WebSphere domain. We started this using the path Start ->
Programs -> IBM WebSphere -> Application Server V4.0 AE ->
Administrator’s Console.
The default server in our WebSphere administrative domain was started, as
indicated by the green disk beside the server instance.
5. To determine if the CTGTesterECI application was running, from the
administrative console we expanded WebSphere Administrative Domain ->
Enterprise Applications and right-clicked the CTGTesterECI node. We
selected Show Status from the pop-up menu. The resulting pop-up window
showed that the CTGTesterECI Web application was running on the default
server (Figure 11-21).
Figure 11-21 Status window showing the CTGTesterECI application running
Note: Each individual application can be started by right-clicking their node
and selecting Start from the pop-up menu. The default server can also be
restarted by stopping and starting it. Starting a server will also start all
applications that run inside it.
6. We opened our Web browser and loaded the welcome page of the
CTGTesterECI application using the URL http://volga/CTGTesterECIWeb/.
This displayed the page shown in Figure 11-22 on page 311. The default