The Address Book sample demonstrates how you use the SOAPInput, SOAPReply, and SOAPRequest nodes to both provide and consume a Web service through an HTTP or JMS transport. Two sets of example input messages are provided: one set to call the consumer flow which in turn calls the provider flow, and one set to call the provider flow directly.
The Address Book sample shows one of the methods available for Web services development. In this sample the WSDL has already been dragged onto an existing SOAPInput node, rather than onto the canvas, and the remainder of the flow is built manually. This sample shows you how to work in the SOAP domain.
The WSDL used in the Address Book sample is the same as the samples provided with the Web services feature pack for WebSphere Application Server. You can use IBM Integration Bus with WebSphere Application Server by interchanging the providers and consumers from both samples in the case of SOAP over HTTP. However, the existing Address Book Sample provided with the WebSphere Application Server does not support SOAP over JMS transport. To support SOAP over JMS transport, you must regenerate the Web Service sample by adding JMS binding and port to the WSDL to interoperate with the WebSphere Application Server, see the WSDL file provided with this sample.
The Address Book sample shows you how to set up WS-Security and WS-RM for existing message flows, for both a provider and a consumer. The sample also demonstrates how messages can be recovered if the TCP channel is restarted when WS-Reliable Messaging is enabled.
The WS-RM policy supports only HTTP transport. The policy cannot be applied when the sample is using JMS transport.
The security policy and WS-RM policy used in this sample is the same as the default policy in WebSphere Application Server so that you can interoperate with WebSphere Application Server.
NOTE: In WebSphere Message Broker Version 8.0, IBM Integration Bus v9.0 and later, message model schema files contained in libraries are the preferred way to model messages for most data formats, including the new DFDL domain. Message sets continue to be supported, and are required if you use the MRM or IDOC domains. You can continue to import and deploy message sets for use in message flows. However, if you need to create one or more message sets, message definitions, or message categories when using this sample, you must first enable message set development in the Integration Toolkit. For more information, see Enabling message set development in the IBM Integration Bus documentation.
Click the following links to find out more about the sample and how to get the prebuilt sample to run by using the wizards:
You set up the sample in one of the following ways:
You can import or import and deploy a sample only when you use the information center that is integrated with the Integration Toolkit.
Set up the sample to use JMS transport
When you have finished with the sample, you can remove it in one of the following ways: