Steps for Building

The SOAP Monitor module is included with the binary distribution of Axis2 and its module (soapmodule.mar) is included in the packaging of the webservices2.war lib directory during the build. The web.xml file shipped with the webservices2.war has the necessary entries to support the SOAP Monitor. Beyond this the following additional steps are needed to enable this functionality:

1. Create a location on your disk to contain the necessary Axis2 artifacts; e.g.

   cd C:\
               mkdir Axis2-includes

2. As per the Axis2 documentation, you must place the SOAPMonitor applet classes at the root of the WAR file; for example:

   cd C:\Axis2-includes
   jar -xvf 
     %CURAMSDEJ%\ear\webservices2\Axis2\modules\soapmonitor-1.5.1.mar
     org/apache/axis2/soapmonitor/applet/

3. Then, use the following properties when you invoke your web services ear target (websphereWebServices or weblogicWebServices):

   -Daxis2.include.overwrite=true
         -Daxis2.include.location=C:\Axis2-includes

4. The shipped axis2.xml file defines the necessary SOAP Monitor phase elements, but to be functional the following entry needs to be added (similarly to other module entries):

   <module ref="soapmonitor"/>

   This change can be made to the EAR file prior to deployment or for WebSphere in the deployed filesystem.

5. Then to access the SOAPMonitor you would use a URL like this: http://localhost:9082/CuramWS2/SOAPMonitor.
6. Unfortunately the applet doesn't give much information when there is an issue. If you see the error: "The SOAP Monitor is unable to communicate with the server.":
   • Ensure there is not a port conflict; the default as set in web.xml is 5001if so, change that port.
   • This error may occur if you use Microsoft Internet Explorer 6; if so, use a more current browser version.