WSE Deployment within the OMII Container
Community Grids Lab,
This document provides details pertaining to the deployment of WS-Evening Web Services ─ WseSink, WseSource and WseSM ─ and the SoapMonitor service within the OMII container. We have tested this software with version 1.2 of the OMII container. We leverage ANT to deploy and undeploy the aforementioned services. We assume that the users have successfully installed ANT on their machine.
We now list the directories relevant to this demo. The variable names here are self-descriptive.
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: Execute the ANT target command build-all in the WSE Base Directory (/usr/local/OMII/webservices/wse).
As depicted in the figures (Figure 1) below this results in the creation of the client and server distribution.
Figure 1: Output of the build-all (Part 1)
Step 2:
We now proceed to deploy the WseSource, WseSink, WseSM and tSoapMonitor services within Tomcat running on port 18080 (Here we note that this port number could be any other number and is under the user’s contro0l) within the OMII Container. The user first needs to use the cd shell command to enter the WSE Server Directory (/usr/local/OMII/webservices/wse/dist/server)
Step 3: Next the user needs to execute the ANT target command deploywse-omiitomcat. This command copies all the necessary files including jar files, classes and resource files to the relevant locations within the OMII Container.
The figures below depict the result of the execution of this ANT target command. The successful completion of this command is a precursor to the deployment of web services within the OMII container.
Step 4: Next the user needs to start Tomcat. This can be done by accessing the OMII TOMCAT HOME directory and executing the startup.sh shell script. The result of this execution is depicted below.
Step 5: To deploy
the SoapMonitor Web Service the user needs to execute the ANT target command soapmonitor within the WSE Server Directory. The command and the
arguments that this command takes is depicted in the snippet below. Here <machine_name> corresponds to the
machine hosting Tomcat and the OMII Container.
|
/usr/local/OMII/webservices/wse/dist/server> ant
deploy-soapmonitor
-Dwse.soapmonitor.axisadmin=-lhttp://<machine_name> :18080/axis
/services/ AdminService
-Dwse.soapmonitor.wsddfile=config/wse/deploy-monitor.wsdd |
A sample execution of this command is depicted in the figure below.
A simple way to verify the deployment of the SOAP Monitor Web Service is by pointing the web browser to the following URL: http://<machine-name>:18080/axis/servlet/AxisServlet . A sample execution of the aforementioned step is depicted in the figure below.
Step 6: To deploy the WseSink Web Service the user needs to execute the deploy-sink ANT target command within the WSE Server Directory. The command and the arguments that this command takes is depicted in the snippet below.
|
/usr/local/OMII/webservices/wse/dist/server
> ant deploy-sink
-Dwse.sink.axisadmin=-lhttp://<machine_name> :18080/axis /services/
AdminService - Dwse.sink.wsddfile=config/wse/eventingSink.wsdd |
The result of a sample execution of this command is depicted below.
A simple way to verify the deployment of the WseSink Web Service is by pointing the web browser to the following URL: http://<machine-name>:18080/axis/servlet/AxisServlet. A sample execution of the aforementioned step is depicted in the figure below.
Step 7: To deploy the WseSource Web Service the user needs to execute the deploy-source ANT target command within the WSE Server Directory. The command and the arguments that this command takes is depicted in the snippet below.
|
/usr/local/OMII/webservices/wse/dist/server
> ant deploy-source
-Dwse.source.axisadmin=-lhttp://<machine_name>:18080/axis /services/
AdminService - Dwse.source.wsddfile=config/wse/eventingSource.wsdd |
The result of a sample execution of this command is depicted below.
A simple way to verify the deployment of the WseSource Web Service is by pointing the web browser to the following URL: http://<machine-name>:18080/axis/servlet/AxisServlet. A sample execution of the aforementioned step is depicted in the figure below. For the user’s convenience we have highlighted the WseSource service in this figure.
Step 8: To deploy the Subscription Manager WseSM Web Service the user needs to execute the deploy-sm ANT target command within the WSE Server Directory. The command and the arguments that this command takes is depicted in the snippet below.
|
/usr/local/OMII/webservices/wse/dist/server
> ant deploy-sm -Dwse.sm.axisadmin=-lhttp://<machine_name>:18080/axis /services/ AdminService - Dwse.sm.wsddfile=config/wse/eventingSM.wsdd |
The result of a sample execution of this command is depicted below.
A simple way to verify the deployment of the WseSM Web Service is by pointing the web browser to the following URL: http://<machine-name>:18080/axis/servlet/AxisServlet. A sample execution of the aforementioned step is depicted in the figure below. For the user’s convenience we have highlighted the WseSM service in this figure.
Users can also un-deploy ALL the Web Services (running within the container) mentioned in this document. We have included ANT target commands which perform this function for the user.
Please note that the Tomcat within the OMII container should be up and running for these commands to take effect.
The snippet corresponding to the commands that un-depoly targeted services have been depicted here for the user’s perusal.
|
WseSink: /usr/local/OMII/webservices/wse/dist/server> ant undeploy-sink - Dwse.sink.axisadmin=- lhttp://<machine_name>: 18080/axis/services/AdminService -Dwse.sink.wsddfile=config/wse/undeploySink.wsdd WseSource: /usr/local/OMII/webservices/wse/dist/server>ant
undeploy-source - Dwse.source.axisadmin=-lhttp
://<machine_name>:18080/axis/services/AdminService
-Dwse.source.wsddfile=config/wse/undeploySource.wsdd WseSM: /usr/local/OMII/webservices/wse/dist/server>ant
undeploy-sm -Dwse.sm.axisadmin=-lhttp://<machine_name>:
18080/axis/services/AdminService -Dwse. sm.wsddfile=config/wse/undeploySM.wsdd SoapMonitor: /usr/local/OMII/webservices/wse/dist/server>
ant undeploy-soapmonitor –Dwse.soapmonitor.axisadmin=-lhttp://<machine_name>:18080/axis/services/AdminService
–Dwse.soapmonitor.wsddfile=config/wse/undeploySoapMonitor.wsdd |
A command which un-deploys all the Web Services and deletes all files related to these services is also available. For the correct execution of the command a user needs to ensure that the Tomcat process is no longer running. The snippet outlining this command is depicted below.
|
/usr/local/OMII/webservices/wse/dist/server>ant
undeploywse-omiitomcat |