01 March 2010 - 3.5 |
For the purposes of this tutorial, we will be using Axis2 v1.5 and Sandesha2 v1.3, although the steps should remain the same for other versions.
In order to get the Axis2 server set up with Sandesha2 for testing, you will need to perform the following steps.
Read through the Sandesha2 install instructions
Now that you have set up the Axis2/Sandesha2 combination, you are ready to connect to it using SoapUI
Go to the RMSampleServiceSoap11Binding, we will be using the echoString operation for the rest of this tutorial. There will be a request (Request 1), that was already created with the project. You will need to replace the contents of the request with the following (the wsdl does not seem to reflect the structure that the RMSampleService really expects):
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:user="http://userguide.samples.sandesha2"> <soapenv:Header/> <soapenv:Body> <user:echoString xmlns:temp="http://tempuri.org/"> <temp:Text>Hello World!</temp:Text> <temp:Sequence>sequence</temp:Sequence> </user:echoString> </soapenv:Body> </soapenv:Envelope>
In the request properties on the lower left, set the Skip SOAP action property to true.
Enable WSA under the WSA tab, disable the Add Default WSA action checkbox, and set the action name to echoString. Either turn on Randomly Generate MessageID, or enter a MessageID in the box below.
In the WS-ReliableMessaging Tab, activate reliable messaging, and set it to use version 1.1 in the dropdown below.
You can see the WSRM feedback in the WSRM log