Objective
Web Service is one of the key technologies in SOA implementation at present. The new version of WebSphere Process Server (WPS) v6.2.0.1 supports existing JAX-WS bindings by adding support for unreferenced (unreferenced) SOAP message attachments, as shown in Figure 1 below.
Figure 1. SOAP Message Attachment Conversion
The Jax-ws Web Service binding of the WPS runtime captures and attaches a SOAP message attachment to an attachment part of the SMO (Service message Object) that can be used as an intermediary component within the SCA module by the SMO (mediation flow C omponent) between transfer and processing.
This article will provide you with an end-to-end scenario that tells you how to take advantage of this functionality in a real-world application. In this article, you will find the following related content:
How to publish a Java class that has business logic as a WEB service.
How to set up a Web service client.
The interaction of the SCA module with the WEB Service implementation end and its clients.
How the SCA module adds a SOAP message attachment to the WEB service implementation side and its client interaction process.
Part One: Overview of End-to-end scenarios
Figure 2 Below is an end-to-end scenario used by this article to illustrate the functionality of the JAX-WS binding delivery SOAP message attachment, where the arrow refers to the flow direction of the SOAP message attachment, and the calling interface is a two-way interface. In this scenario, the reader can also define the mediation flow component (mediation flows Component) in the SCA module below in Figure 2 to achieve more complex processing logic.
Figure 2. End-to-end Application Scenario Logic diagram