Creating the client driver message set
Use the following instructions to create the message sets that define the
messages that are used to drive the client flow.
- Create a new message set project called SampleDriverMessages,
see Message set projects
in the WebSphere Message Broker documentation.
- Create a new message definition file called driverMessage.mxsd,
see Creating a message set
in the WebSphere Message Broker documentation.
- Create a new message called OrderMessage, and a new message called OrderResponse,
see Adding message model objects
in the WebSphere Message Broker documentation.
- Right-click OrderMessage,
click Add Local Element.
- Select localElement and switch to the
Properties view in the Message Definition editor.
- Select (New Complex Type) from the
Type list.
The New Complex Type window is displayed.
- Click OK to create a Local Complex Type.
- To add each of the elements in the following table to OrderMessage,
right-click {Local complexType},
click Add Local Element and rename the element.
OrderMessage
Element Name |
Element Type |
First Name |
xsd:string |
LastName |
xsd:string |
Street |
xsd:string |
City |
xsd:string |
ZipCode |
xsd:string |
PartNumber |
xsd:string |
Quantity |
xsd:int |
- To add each of the elements in the following table to the OrderResponse message,
right-click OrderResponse, click
Add Local Element and rename the element.
OrderResponse
Element Name |
Element Type |
Status |
xsd:string |
AMT |
xsd:int |
PartNo |
xsd:string |
PartQuantity |
xsd:int |
Compare your messages to the following diagram to ensure they have the correct format:
You can now create the web services client message flow, see
Creating the web service client flow.
Back to Building the Asynchronous Consumer sample