Running WSE within the OMII Container using
the SOAPMonitor
Community Grids Lab,
This document provides
details regarding the usage of the SOAPMonitor for monitoring SOAP request and
response messages while running the WS-Eventing software within the OMII Container.
Note: Here we have
deployed all the services on a Linux machine (156-56-104-135.dhcp-bl.indiana.edu:18080), but we are running the SOAP Monitor on a Windows
machine.
We now list the directories relevant to this demo. The variable names here are self-descriptive.
<machine_name> and port number (where SOAPMonitor, WseSink, WseSource and WseSM services are deployed): 156-56-104-135.dhcp-bl.indiana.edu:18080 OMII HOME: /usr/local/OMII OMII TOMCAT HOME: <omii_home>/jakarta-tomcat-5.0.25 OMII AXIS HOME: <omii_home>/axis-1_2beta WSE Base (distribution) Directory: <omii_home>/webservices/wse WSE Client Directory: <omii_home>/webservices/wse/dist/client WSE Server Directory: <omii_home>/webservices/wse/dist/server Step 1: We have deployed the SOAPMonitor,
WseSink, WseSource and WseSM Services within (156-56-104-135.dhcp-bl.indiana.edu) Tomcat running on port 18080 within OMII
container using our distribution's ant target commands. Here we note
that this port number could be any other number and is under the user’s control. For information pertaining to the deployment
of the aforementioned services please refer to the “FINS-Deployment of WSE within OMII” file located under the “docs/installation” folder. Next, the user needs to ensure that the Tomcat server within the OMII container is up and
running.
Step 2: After running the Tomcat server the user can check the list of deployed
Web Services running within Tomcat instance by pointing the browser to the
following URL
http://<machine_name>:18080/axis/servlet/AxisServlet
Make sure that the list
of displayed services contains the SOAPMonitor, WseSink, Wsesource and WseSM
services.
Step 3: To the SOAPMonitor applet point the browser to the URL listed below
http://<machine_name>:18080/axis/SOAPMonitor,
where <machine_name> is the IP address of the host where all
the services are deployed.
E.g. http://156-56-104-135.dhcp-bl.indiana.edu:18080/axis/SOAPMonitor
Figure 1 depicts the running of the SOAPMonitor on a Windows
machine. Since this is an
applet this information can be accessed from any machine (we just happened to
use a Windows machine, users can use an OS of their choice).
Figure 1 SOAPMonitor running on Windows machine
Step 4: Now the user needs to open a new terminal window on the Linux
machine(156-56-104-135.dhcp-bl.indiana.edu) and use the cd shell
command to enter the WSE Client Directory
(/usr/local/OMII/webservices/wse/dist/client). Next user needs to execute ANT target
command “ant
wseaxis-sinkframe” to run the sink client frame as depicted in the Figure 2 below
Figure 2 Sink Client Frame
This command also
launches the Sink client applet as depicted in the Figure 3 below.
Figure 3 Sink Client Applet
Step 5: In this demo we will be
subscribing to a String Topic. Click
on the “Subscribe Topic” button to subscribe─ this subscribes the user to
the “Literature/Shakespeare” topic. Figure 4 depicts the resulting Subscribe Request sent by the Sink
Client Service to the Sink Web Service.
Figure 4 Subscription Request sent by Sink Client Service
Step 6: The Subscription request
received by the Sink Web Service can be seen from the SOAPMonitor applet window on the Windows machine. Figure 5 depicts the subscription request message received by Sink
Web Service from the Sink Client Service.
Figure 5 Subscription Request received by Sink Web Service from Sink Client Service
Step 7: The same subscription request comes
to the Source Web Service. Figure
6 depicts the subscription request received by Source Web Service from the Sink Web Service.
Figure 6 Subscription Request received by Source Web Service from Sink Web Service
Step 8: The Source Web Service issues a SubscribeResponse back to the sink.
This response contains the subscription identifier generated by the source to
uniquely represent the subscription. This UUID-base subscription identifier is
necessary for all exchanges (renew, status and unsubscribe) pertaining to the
aforementioned subscription. Figure
7 depicts the subscription response received by the Sink Web Service from the Source Web Service.
Figure 7 Subscription Response received by Sink Web Service from Source Web Service
Step
9: At the same
time, Source Web Service also sends the Subscription SOAP message to the
Subscription Manager. This message contains both the original subscription
request from the sink along with the response issued by the source. Figure 8 depicts the SOAP message sent by Source Web Service
to Subscription Manager Service.
Figure 8 Subscription Request and Response received by Subscription Manager Web Service
Step 10: Now User needs to open the new terminal window from Linux
machine(156-56-104-135.dhcp-bl.indiana.edu) and use the cd shell
command to enter the WSE Client Directory (/usr/local/OMII/webservices/wse/dist/client). Next user
needs to execute ANT target command “ant
wseaxis-sourceframe” to run the source client frame as depicted in Figure 9 below
Figure 9 Source Client Frame
This command also
opens the Source client applet as depicted in Figure 10 below.
Figure 10 Source Client Applet
Step 11: Click on “send message” button to send
notifications to the registered sink Web Service. Figure 11 depicts the notification generated by the Source
Client Service.
Figure 11 Notification sent by Source Client Service to Source Web Service
Step 12: Figure 12 depicts the notification sent by the Source Web
Service to the sink Web Service. This information was viewed using the SOAPMonitor.
Figure 12 Notification sent by Source Web Service to Sink Web Service
Step 13: Figure 13 depicts the notification received by the Sink Web
Service from the Source Web Service.
Figure 13 Notification received by Sink Web Service from Source Web Service