01 March 2010 - 3.5 user guide eclipse intellij netbeans maven download nightly forum bugs blog sf.net eviware


Eviware Logo

Testing WS-RelibleMessaging Services Using SoapUI

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.

  1. Download Axis2 and Sandesha2 from the Apache site.
  2. Unzip Axis2 to the directory of your choice. The directory will be reffered to as AXIS2_HOME from here on. You will also need to create an environment variable with the same name and set it to the directory.
  3. Unzip the Sandesha2 file
  4. Read through the Sandesha2 install instructions

    1. You will need to copy all the jar files to the lib folder
    2. The phases already include the RMPhase entries in Axis2.xml in the 1.5 version, although you might need to add them if you are using another version
    3. c. For the purposes of this tutorial, there is no need to build the war file, just copy the files to the correct places
  5. You will find the RMSampleService in the folder you unzipped the Sandesha2 files to under samples/services. Simply copy the RMSampleService.aar file to the repository/modules directory in AXIS2_HOME
  6. Start the server by running axis2server.bat or axis2server.sh in the AXIS2_HOME/bin directory

Now that you have set up the Axis2/Sandesha2 combination, you are ready to connect to it using SoapUI

  1. If you have not changed any of the settings, the wsdl for the service should be at http://localhost:8080/axis2/services/RMSampleService?wsdl. Create a new project in SoapUI using this WSDL.
  2. 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>
                
  3. In the request properties on the lower left, set the Skip SOAP action property to true.

    The Request properties

  4. 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.

    The WSA Properties tab

  5. In the WS-ReliableMessaging Tab, activate reliable messaging, and set it to use version 1.1 in the dropdown below.

    The WSRM Properties tab

  6. You can now run the request, which will execute the request as a sequence

You can see the WSRM feedback in the WSRM log

The WSRM Log


Next: Web Service Code Tool Integrations