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 two 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 second version of the web service endpoint is supplied as a CICS service provider application program (DFH0XODE).
File Description
ExampleAppClientV855.war Web service front end client to catalog manager
ExampleAppWrapperClientV855.war Web service front end client to web service wrappers
ExampleAppDispatchOrderV855.war Order dispatch web service provider application
These WARs were exported from Dynamic Web Projects. For information about deploying the WAR files, see Deploying applications to a JVM server.
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 CICS service provider as the order dispatch web service end point. It also includes a web service client on a CICS system.

The image shows another version of web client front end, with CICS service provider as the order dispatch web service end point.
In this configuration, the application is accessed through two different clients:
  • A web browser client connected to 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 another version of web client front end, with CICS service provider as the order dispatch web service end point.

The image shows another version of web client front end, with CICS service provider as the order dispatch web service end point.

In this configuration, the web browser client is connected to 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.

In order for Dispatch Manager on your CICS system to call this end point, you need to change the following configuration using the ECFG configuration transaction:
  • Outbound WebService? to YES
  • Outbound WebService URI to the URI where the Dispatch Order end point is being deployed on, e.g. http://cics2:8080/exampleApp/dispatchOrder
For further details on setting up the example application, see Configuring the example application.

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 Liberty JVM server.

The image shows a configuration of an application with both of the web client front end and the order dispatch web service end point on Liberty JVM server.

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

In order for Dispatch Manager on your CICS system to call this end point, you need to change the following configuration using the ECFG configuration transaction

  • Outbound WebService? to YES
  • Outbound WebService URI to the URI where the Dispatch Order end point is being deployed on, e.g. http://mylibertyserver:9080/ExampleAppDispatchOrderV855/DispatchOrder

    For further details on setting up the example application, see Configuring the example application.