1. What's Wise-Lms?
The name Lms was originally meant to be an acronym standing for Logging Meta Service.
Lms' goal and use are very similar to the Axis' TCP-Mon ones: it logs any tcp communication it handles and gives developers the opportunity to review any request-response communications. As a matter Lms can be used like every proxy-like tools: service consumers connect to a special address the tool listens to, the message is logged and then forwarded to the service provider. At the end of the invocations, the tool shows the whole communication as a collection of request-response couples.
What Lms adds to the usual proxy tool is its web interface that removes the need for a window system (like X) to run it. Of course this is valuable expecially when performing tests on servers since they typically do not have X active.
To achieve this, Lms is a JBoss deployable application (an ear) and has a JMX mbean as application core and a JBoss Seam user interface to make its use easy.
The installation process requires the user to download the Lms binary distribution from the JBoss.org website (http://www.jboss.org/wise/downloads).
1. Extract the Lms.ear from the distribution archive
2. Add the following policy to your application server's login-config.xml:
3. Deploy Lms.ear by simply copying it to your application server's selected deploy directory
<application-policy name = "no-auth">
<login-module code = "org.jboss.security.ClientLoginModule" flag = "required">
Once you browse to http://localhost:8080/Lms/, you'll get the Lms home page. There you have to bind a symbolic name to a real http
address (in most cases a ws endpoint address).
You can start/stop the logging functionality (in stopped logging mode Lms acts just like a proxy), delete the binding, clean all
communication logs. After that, you should use the binding you've just defined: as a matter of fact Lms creates a virtual address given by your application server host & port followed by
/Lms/servlet/auth/log/ and the name you choose for your binding.
Selecting a binding you will see all the logged communications:
Finally clicking on Show you'll see request/response logged in this communication:
Here is a list of suggestions in order to prevent common issues:
- Make sure your binding target addresses can be reached from your host (the host you're running Lms on); as a matter of fact firewall rules and/or network configuration issues in general can eventually prevents Lms from actually acting as a proxy.
- When dealing with webservice endpoint, remember to use the endpoint address and not the published wsdl endpoint address (they often only differ in the ?wsdl suffix) when typing in the binding target address.