Web service support for the example application

The web service support extends the example application, providing a web client front end and two versions of a web service endpoint for the order dispatcher component.

The web client front end and one version of the web service endpoint are supplied as enterprise archive files (EARs) that run in the following environments:
Environment EAR files
WebSphere® Application Server Version
ExampleAppClientV8.ear
ExampleAppWrapperClient.ear
DispatchOrderV8.ear
Rational® Developer for System z® uses the web service endpoint for WebSphere Application Server.

The second version of the web service endpoint is supplied as a CICS® service provider application program (DFH0XODE).

Figure 1 shows one configuration of the example application.
Figure 1. The example application configured as a web service provider
The structure of the example application configured as a web service, as described in this topic.
In this configuration, the application is accessed through two different clients:
  • A web browser client connected to WebSphere Application Server, in which ExampleAppClient.ear is deployed.
  • CICS web service client DFH0XECC. This client uses the same BMS presentation logic as the base application but uses module DFH0XCUI instead of DFH0XGUI.

Figure 2 shows another way to configure the example application as a web service.

Figure 2. Alternate web service provider configuration
An alternative configuration of the example application as a web service provider, as described in this topic.

In this configuration, the web browser client is connected to WebSphere Application Server, in which ExampleAppWrapperClient.ear is deployed. In CICS, three wrapper applications (for the inquire catalog, inquire single, and place order functions) are deployed as service provider applications. They in turn link to the base application.