Monitoring SOAP messages in WebSphere Integration Developer
January 9, 2007 1 Comment
If you are developing a module or mediation module with web services bindings you may be interested in monitoring the SOAP message(s) received at an export or sent from an import. To find out how to do this, read the rest of this post.
1. Open the Servers view in WebSphere Integration Developer (this should be open if you are in the Business Integration perspective, if not open it from Window>Show view>Servers
2. Right click on the server you want to monitor and choose Monitoring>Properties which will present you with the following dialog (click for a clearer image):
3. Click the Add button which will present you with the following dialog:
4. Choose the port you wish to monitor (for SOAP this will typically be the port which has a number like 9081) and click OK. To check which port it is check the value in the Admin Console.
5. Select the monitor you have just added and click Start. The monitor will now listen on the monitor port, capture the message so that you can look at it and then forward it on to the actual port. Your dialog should now look like (click for a clearer image):
In order to actually monitor messages you now need to modify your application so that it uses the monitoring port instead of the actual port by following step 6a or 6b:
6a) If you are monitoring SOAP messages coming into an export, modify your client so that it sends messages to the Monitor port (i.e. 9082 in the picture above) rather than 9081.
6b) If you are monitoring SOAP messages leaving an import, modify your import binding so that the endpoint uses the Monitor port and not the actual port.
7. Test your application in the same way as you did before.
You should now see any SOAP messages sent to the monitoring port captured in the TCP/IP Monitor view which will appear when a message is captured. This view typically appears next to your Servers view in WebSphere Integration Developer.