The SOAP Monitor utility provides a way for web service developers to view the SOAP messages that are being used to invoke the web services, along with the results of those messages. In this utility, a handler has been written and added to the global handler chain. As SOAP requests and responses are received, the SOAP message information is forwarded to a SOAP monitor service. This data can then be accessed with a web browser by navigating to http://localhost:8888/api/SOAPMonitor (where 8888 is the port number on which the web server is running).
The SOAP message information is displayed through a web browser by using an applet that opens a socket connection to the SOAP Monitor service. This applet requires Java plugin 1.3 or higher to be installed in your browser; if you do not have a correct plugin, the browser will prompt you to install one. You can configure the port used by the SOAP Monitor service to communicate with applets (default port is 5001) by editing the web.xml file to change the port used by the Axis2 web application.
Although the SOAP Monitor module is available, for security reasons it is not engaged by default and should be disabled after troubleshooting (i.e., reverse the steps below). Back up all files before modifying them.
jar -xf AlarmPointWebService.aar
(if the "jar" executable is not installed on your server, copy the AlarmPointWebService.aar file to AlarmPointWebService.zip and then extract the contents using a utility such as 7zip).<module ref="soapmonitor"/>
<servlet>
<servlet-name>SOAPMonitorService</servlet-name>
<display-name>SOAPMonitorService</display-name>
<servlet-class>org.apache.axis2.soapmonitor.servlet.SOAPMonitorService</servlet-class>
<init-param>
<param-name>SOAPMonitorPort</param-name>
<param-value>5001</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>default</servlet-name>
<servlet-class>org.mortbay.jetty.servlet.DefaultServlet</servlet-class>
<init-param>
<param-name>acceptRanges</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>dirAllowed</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>redirectWelcome</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>maxCacheSize</param-name>
<param-value>2000000</param-value>
</init-param>
<init-param>
<param-name>maxCachedFileSize</param-name>
<param-value>254000</param-value>
</init-param>
<init-param>
<param-name>maxCachedFiles</param-name>
<param-value>1000</param-value>
</init-param>
<init-param>
<param-name>useFileMappedBuffer</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>SOAPMonitorService</servlet-name>
<url-pattern>/SOAPMonitor</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>default</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
You may see a message asking to install the JRE 1.3 plugin, which you should not allow as this plugin is too old to function correctly. Instead, browse to Java.com and install the current JRE.
Note that the following steps require the Java Development Kit (JDK) to execute.
webserver/webapps/axis2/WEB-INF/lib/soapmonitor-1.3
.webserver/webapps/axis2/WEB-INF/lib/axis2-soapmonitor-servlet-1.6.1.jar
.jar -xf <jarFileName>
org
directory and all of its contents into the webserver/webapps/axis2/ directory.