Before you can use the Web client, you must deploy
the appropriate enterprise archive (EAR) for the client into one of the supported
environments and configure it to call the appropriate end points in your CICS® system.

The supported environments for the ExampleAppClient.ear
client application are:
- WebSphere® Application
Server Version 5 Release 1
- WebSphere Studio
Application Developer Version 5 Release 1 with a WebSphere unit test environment
- WebSphere Studio
Enterprise Developer Version 5 Release 1 with a WebSphere unit test environment.
The supported environments for the ExampleAppClientV6.ear client application
are:
- WebSphere Application
Server Version 6
- Rational® Application
Developer Version 6 or later with a WebSphere unit test environment
- WebSphere Developer
for zSeries® Version
6 or later with a WebSphere unit test environment

- Enter the following in your Web browser: http://myserver:9080/ExampleAppClientWeb/,
where myserver is the hostname of
the server on which the Web service client is installed. The
example application displays the following page:

This figure contains a high-resolution graphic that
is not supported in this display format. To view the graphic, please use the
CICS Information Center.
- Click the CONFIGURE button to bring up the
configuration page. The configuration page is displayed.

This figure contains a high-resolution graphic that
is not supported in this display format. To view the graphic, please use the
CICS Information Center.
- Enter the new endpoints for the Web service. There are
three endpoints to configure:
- Inquire catalog
- Inquire item
- Place order
- In the URLs replace the string 'myCicsServer'
with the name of the system on which your CICS is running.
- Replace the port number '9999'
with the port number configured in the TCPIPSERVICE, in the example this to
30000.
- Click the SUBMIT button.
The Web application is now ready to run.
Note: The URL the Web services invoke is stored in an HTTP session.
It is therefore necessary to repeat this configuration step each time a browser
is first connected to the client.