Web service support for the example application

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

The versions of the web client front end and one version of the web service endpoint are supplied as Java web archive files (WARs) that run in the Java EE 6 web profile environment provided by the latest version of WebSphere® Application Server or the latest CICS® TS Liberty JVM server. The COBOL version of the web service endpoint is supplied as a CICS service provider application program (DFH0XODE).
Table 1. Supplied WARs
File Description
ExampleAppClientV855.war Front end client to catalog manager
ExampleAppWrapperClientV855.war Front end client to web service wrappers
ExampleAppDispatchOrderV855.war Order dispatch web service provider app
These WARs were exported from dynamic web projects. For information about deploying the WAR files, see .
You must enable the jax-ws feature in the Liberty JVM server, for example by adding the following to the Liberty server configuration file, server.xml: 
<feature> jaxws-2.2 </feature>

Figure 1 shows a configuration of the example application with one version of the web client front end and a CICS service provider as the order dispatch web service end point. It also includes a web service client on a CICS system.

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 a Liberty JVM server, in which ExampleAppClientV855.war 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 a configuration of the example application with another version of the web client front end and a CICS service provider as the order dispatch web service end point.

Figure 2. Alternative web service provider configuration
Alternative structure of the example application configured as a web service, as described in this topic.

In this configuration, the web browser client is connected to a Liberty JVM server, in which ExampleAppWrapperClientV855.war 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.

You must change the following configuration so that the dispatch manager on your CICS system can call this end point:
  • Outbound WebService? to YES
  • Outbound WebService URL to the URL where the order dispatch endpoint is deployed, for example:
    http://cics2:8080/exampleApp/dispatchOrder
For further details, see .

Figure 3 shows a configuration of the example application with both of the web client front end and the order dispatch web service end point on a Liberty JVM server.

Figure 3. Web service provider configuration on a Liberty JVM server
Structure of the example application configured as a web service on a Liberty JVM server, as described in this topic.

In this configuration, the web browser client is connected to a Liberty JVM server, in which ExampleAppClientV855.war is deployed. The order dispatch web service end point ExampleAppDispatchOrderV855.war is installed on the Liberty JVM server.

You must change the following configuration so that the dispatch manager on your CICS system can call this end point:
  • Outbound WebService? to YES
  • Outbound WebService URL to the URL where the order dispatch endpoint is deployed, for example:
    http://mylibertyserver:9080/ExampleAppDispatchOrderV855/DispatchOrder
For further details, see .