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. This topic applies to CICS integrated-mode Liberty only.
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 WebSphere Application Server or a CICS TS Version 5.3 Liberty JVM server. The COBOL version of the web service endpoint is supplied as a CICS® service provider application program (DFH0XODE).
| 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 Deploying applications to a JVM server.
</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.

- 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.

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.
- Outbound WebService? to YES
- Outbound WebService URL to the URL where the order dispatch endpoint is deployed, for example:
http://cics2:8080/exampleApp/dispatchOrder
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.

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.
- Outbound WebService? to YES
- Outbound WebService URL to the URL where the order dispatch endpoint is deployed, for example:
http://mylibertyserver:9080/ExampleAppDispatchOrderV855/DispatchOrder