Explanation of Target Commands Used in build.xml
Community Grids Lab,
This document provides
a description of each of the commands used in the build.xml file. Also provided is a build.properties file where users can initialize all the
arguments for the various ANT target commands. Users can, if they so desire,
also override the modified default parameters (contained in the
build.properties) while running the individual target commands.
Listed below is the
list of variables in the build.properties file. For each such variable we have include
a description of the information encapsulated within these variables and their
current default values. It is expected
that the users will modify the values associated with these properties to suit
their execution environment.
omii.catalina.home
─ Holds the location of wse root directory on OMII Container installed
machine. Typically this directory will be inside OMII installed directory.
omii.catalina.home=/usr/local/OMII/jakarta-tomcat-5.0.25
omiitomcat ─ Holds the
Tomcat home directory. In this case it is Tomcat inside the OMII container.
This variable is same as Catalina home variable but defined exclusively for
Tomcat to execute Start and Stop commands from terminal
omiitomcat=/usr/local/OMII/jakarta-tomcat-5.0.25/
omiiwse ─ Holds the
tomcat installed directory. In this case it is tomcat inside the OMII container
omiiwse=/usr/local/OMII/webservices/wse
wse.source.hostname ─ Holds the
value of Source host name. You have to change the value to your local machine.
This variable is used while running WSE on the Filter Pipeline.
wse.source.hostname=mountain.ucs.indiana.edu
wse.source.port ─
Holds the
wse.source.port=19000
wse.source.address
─ Holds the Source running on port 19000 on FilterPipeline.
wse.source.address=tcp://mountain.ucs.indiana.edu:19000
wse.submanager.address ─Holds the Subscription Manager running on port 20000 on
FilterPipeline.
wse.submanager.address=tcp://mountain.ucs.indiana.edu:20000
wse.submanager.hostname ─Holds the
value of Subscription Manager host name. You have to change the value to your
local machine. This variable is used while running WSE on the Filter Pipeline.
wse.submanager.hostname=mountain.ucs.indiana.edu
wse.submanager.port ─Holds the
Subscription Manager
wse.submanager.port=20000
wse.sink.hostname ─Holds the
value of Sink host name. You have to change the value to your local machine.
This variable is used while running WSE on the Filter Pipeline.
wse.sink.hostname=mountain.ucs.indiana.edu
wse.sink.port ─Holds
the Sink
wse.sink.port=21000
wse.sink.address ─Holds
the Sink running on port 21000 on FilterPipeline.
wse.sink.address=tcp://mountain.ucs.indiana.edu:21000
wse.sink2.hostname ─Holds the
value of Sink2 host name. You have to change the value to your local machine.
This variable is used while running WSE on the Filter Pipeline.
wse.sink2.hostname=mountain.ucs.indiana.edu
wse.sink2.port ─Holds
the Sink2 port number running on FilterPipeline.
wse.sink2.port=22000
wse.sink2.address ─Holds the
Sink2 running on port 22000 on FilterPipeline
wse.sink2.address=tcp://mountain.ucs.indiana.edu:22000
wse.sink.axisadmin
─Holds the admin service URL for the Sink running on OMII Container.
wse.sink.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
wse.sink.deploy.wsddfile ─Holds the Sink Deployment Descriptor file name and location.
wse.sink.deploy.wsddfile=config/wse/eventingSink.wsdd
wse.sink.undeploy.wsddfile
─Holds
the Sink Undeployment Descriptor file name and location.
wse.sink.undeploy.wsddfile=config/wse/undeploySink.wsdd
wse.source.axisadmin ─Holds the
admin service URL for the Source running on OMII Container.
wse.source.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
wse.source.deploy.wsddfile
─Holds
the Source Deployment Descriptor file name and location.
wse.source.deploy.wsddfile=config/wse/eventingSource.wsdd
wse.source.undeploy.wsddfile
─Holds
the Source Undeployment Descriptor file name and location.
wse.source.undeploy.wsddfile=config/wse/undeploySource.wsdd
wse.sm.axisadmin ─Holds the
admin service URL for the Subscription Manager running on OMII Container.
wse.sm.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
wse.sm.deploy.wsddfile
─Holds
the Subscription Manager Deployment Descriptor file name and location.
wse.sm.deploy.wsddfile=config/wse/eventingSM.wsdd
wse.sm.undeploy.wsddfile
─Holds
the Subscription Manager Undeployment Descriptor file name and location.
wse.sm.undeploy.wsddfile=config/wse/undeploySM.wsdd
wse.soapmonitor.axisadmin
─Holds
the admin service URL for SOAPMonitor service running on OMII Container.
wse.soapmonitor.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
wse.smmonitor.deploy.wsddfile ─Holds the SOAPMonitor service Deployment Descriptor file name
and location.
wse.smmonitor.deploy.wsddfile=config/wse/deploy-monitor.wsdd
wse.soapmonitor.undeploy.wsddfile
─Holds
the SOAPMonitor service Undeployment Descriptor file name and location.
wse.soapmonitor.undeploy.wsddfile=config/wse/undeploySoapMonitor.wsdd
wse.sinkproxy.axisadmin
─Holds
the admin service URL for the Sink Proxy Service running on OMII Container.
wse.sinkproxy.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
wse.sinkproxy.deploy.wsddfile
─Holds
the Sink Proxy Service Deployment Descriptor file name and location.
wse.sinkproxy.deploy.wsddfile=config/wse/eventingSinkProxy.wsdd
wse.sinkproxy.undeploy.wsddfile ─Holds the Sink Proxy Service Undeployment Descriptor file name
and location.
wse.sinkproxy.undeploy.wsddfile=config/wse/undeploySinkProxy.wsdd
wse.smproxy.axisadmin variable ─Holds
the admin service URL for the Subscription Manager Proxy Service running on
OMII Container.
wse.smproxy.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
wse.smproxy.deploy.wsddfile
─Holds
the Subscription Manager Proxy Service Deployment Descriptor file name and
location.
wse.smproxy.deploy.wsddfile=config/wse/eventingSMProxy.wsdd
wse.smproxy.undeploy.wsddfile
─Holds
the Subscription Manager Proxy Service
Undeployment Descriptor file name and location.
wse.smproxy.undeploy.wsddfile=config/wse/undeploySMProxy.wsdd
wse.sourceproxy.axisadmin ─Holds the admin service URL for the Source Proxy service running
on OMII Container
wse.sourceproxy.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
wse.sourceproxy.deploy.wsddfile
─Holds
the Source Proxy service Deployment Descriptor file name and location.
wse.sourceproxy.deploy.wsddfile=config/wse/eventingSourceProxy.wsdd
wse.sourceproxy.undeploy.wsddfile ─Holds the Source Proxy service Undeployment Descriptor file
name and location.
wse.sourceproxy.undeploy.wsddfile=config/wse/undeploySourceProxy.wsdd
wse.servlet.url ─Holds the
Axis Servlet URL.
wse.servlet.url=-http://localhost:18080/axis/servlet/AxisServlet
wse.webservice.sink ─Holds the
Sink Web Service name.
wse.webservice.sink=WseSink
wse.webservice.source ─Holds the
Source Web Service name.
wse.webservice.source=WseSource
wse.webservice.sm ─Holds the
Subscription Manager Web Service name.
wse.webservice.sm=WseSM
wse.webservice.sinkproxy
─Holds
the Sink ProxyWeb Service name.
wse.webservice.sinkproxy=WseSinkProxy
wse.webservice.sourceproxy
─Holds
the Source proxy Web Service name.
wse.webservice.sourceproxy=WseSourceProxy
wse.webservice.smproxy
─Holds
the Subscription manager proxy Web Service name.
wse.webservice.smproxy=WseSMProxy
wse.webservice.
soapmonitor ─Holds
the SOAPMonitor Web Service name.
wse.webservice.soapmonitor=SOAPMonitorService
prepare: Creates classes directory under current
directory structure
Usage: $ant prepare
compile: Compiles all files under the src folder and
copies all the class files to classes folder by preserving the same directory
structure. It also creates NbWebInfra.jar file and puts under lib directory.
Usage: $ant
client-dir: Creates client directory from base
directory structure.
Usage: $ant client-dir
server-dir: Creates server directory from base directory
structure.
Usage: $ant server-dir
ServerWar: Builds wse.war file for server distribution
Usage: $ant ServerWar
build-server: Creates server distribution.
Usage: $ant build-server
build-client: Creates client distribution
Usage: $ant build-client
build-all: Creates client and server distribution
Usage: $ant build-all
start: Starts tomcat server.
Usage: $ant start
stop: Stops tomcat server.
Usage: $ant stop
release: Echoed a message”
WS-Eventing Release: Aug-2004 http://www-128.ibm.com/developerworks/webservices/library/specification/ws-eventing/"
to standard output
Usage: $ant release
jar: Creates a jar file called NbWebInfra.jar from all the files of classes’
folder and put it into lib folder
Usage: $ant jar
build-doc: Generates java doc
Usage: $ant build-doc
clean: Cleans all generated class files and documentation.
Usage: $ant clean
test: Run JUnit tests for cgl.narada.wsinfra.util,
cgl.narada.wsinfra.wsa.impl and cgl.narada.wsinfra.wse.impl package.
Usage: $ant test
wse-version: Displays Web Services-Eventing info on OMII
Usage: $ant wse-version
deploywse-omiitomcat: Copies all jar, classes, configuration
Files required for deployment of web services within OMII Tomcat Instance.
Usage: $ant deploywse-omiitomcat
undeploywse-omiitomcat: Deletes all jar, classes and configuration
files previously copied for deployment of web services within OMII container.
Usage: $ant undeploywse-omiitomcat
deploy-sink: Deploys sink service on OMII Container running on port 18080
Usage: $ ant deploy-sink
-Dwse.sink.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.sink.deploy.wsddfile=config/wse/eventingSink.wsdd
test-sink: Test the deployed Sink web service on OMII Container running on port
18080
Usage: $ ant test-sink -Dwse.servlet.url=http://localhost:18080/axis/servlet/AxisServlet
-Dwse.webservice.sink=WseSink
undeploy-sink: Undeploys sink service from OMII Container running on port 18080
Usage: $ ant undeploy-sink
-Dwse.sink.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.sink.undeploy.wsddfile=config/wse/undeploySink.wsdd
deploy-sm: Deploys SM service on OMII Container running on port 18080
Usage: $ ant deploy-sm
-Dwse.sm.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.sm.deploy.wsddfile=config/wse/eventingSM.wsdd
test-sm: Test the deployed Subscription Manager web service on OMII Container
running on port 18080
Usage: $ ant test-sm -Dwse.servlet.url=http://localhost:18080/axis/servlet/AxisServlet
-Dwse.webservice.sm=WseSM
undeploy-sm: Undeploys SM service from OMII Container running on port 18080
Usage: $ ant undeploy-sm
-Dwse.sm.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.sm.undeploy.wsddfile=config/wse/undeploySM.wsdd
deploy-source: Deploys source service on OMII Container running on port 18080
Usage: $ ant deploy-source -Dwse.source.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.source.deploy.wsddfile=config/wse/eventingSource.wsdd
test-source: Test the deployed Source web service on OMII Container running on
port 18080
Usage: $ ant test-source -Dwse.servlet.url=http://localhost:18080/axis/servlet/AxisServlet
-Dwse.webservice.source=WseSource
undeploy-source: Undeploys source service from OMII Container running on port 18080
Usage: $ ant undeploy-source
-Dwse.source.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.source.undeploy.wsddfile=config/wse/undeploySource.wsdd
deploy-soapmonitor: Deploys soapmonitor service on OMII
Container
Usage: $ ant deploy-soapmonitor
-Dwse.soapmonitor.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.soapmonitor.deploy.wsddfile=config/wse/deploy-monitor.wsdd
test-soapmonitor: Test the deployed SOAP Monitor service on
OMII Container running on port 18080
Usage: $ ant test-soapmonitor
-Dwse.servlet.url=http://localhost:18080/axis/servlet/AxisServlet
-Dwse.webservice.soapmonitor=SOAPMonitorService
undeploy-soapmonitor: Undeploys soapmonitor service from OMII
Container
Usage: $ ant undeploy-soapmonitor
-Dwse.soapmonitor.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.soapmonitor.undeploy.wsddfile=config/wse/undeploySoapMonitor.wsdd
deploy-sinkproxy: Deploys sink proxy service on OMII
Container running on port 18080
Usage: $ ant deploy-sinkproxy
-Dwse.sinkproxy.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.sinkproxy.deploy.wsddfile=config/wse/eventingSinkProxy.wsdd
test-sinkproxy: Test the deployed Sink Proxy web service on OMII Container running on
port 18080
Usage: $ ant test-sinkproxy
-Dwse.servlet.url=http://localhost:18080/axis/servlet/AxisServlet -Dwse.webservice.sinkproxy=WseSinkProxy
undeploy-sinkproxy: Undeploys sink proxy service from OMII
Container running on port 18080
Usage: $ ant undeploy-sinkproxy
-Dwse.sinkproxy.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.sinkproxy.undeploy.wsddfile=config/wse/undeploySinkProxy.wsdd
deploy-smproxy: Deploys sm proxy service on OMII Container running on port 18080
Usage: $ ant deploy-smproxy
-Dwse.smproxy.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.smproxy.deploy.wsddfile=config/wse/eventingSMProxy.wsdd
test-smproxy: Test the deployed Subscription Manager Proxy web service on OMII
Container running on port 18080
Usage: $ ant test-smproxy -Dwse.servlet.url=http://localhost:18080/axis/servlet/AxisServlet
-Dwse.webservice.smproxy=WseSMProxy
undeploy-smproxy: Undeploys SM proxy service from OMII
Container running on port 18080
Usage: $ ant undeploy-smproxy
-Dwse.smproxy.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.smproxy.undeploy.wsddfile=config/wse/undeploySMProxy.wsdd
deploy-sourceproxy: Deploys source service on OMII Container
running on port 18080
Usage: $ ant deploy-sourceproxy
-Dwse.sourceproxy.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.sourceproxy.deploy.wsddfile=config/wse/eventingSourceProxy.wsdd
test-sourceproxy: Test the deployed Source Proxy web service
on OMII Container running on port 18080
Usage: $ ant test-sourceproxy
-Dwse.servlet.url=-http://localhost:18080/axis/servlet/AxisServlet
-Dwse.webservice.sourceproxy=WseSourceProxy
undeploy-sourceproxy: Deploys source proxy service from OMII
Container running on port 18080
Usage: $ ant undeploy-sourceproxy
-Dwse.sourceproxy.axisadmin=-lhttp://localhost:18080/axis/services/AdminService
-Dwse.sourceproxy.undeploy.wsddfile=config/wse/undeploySourceProxy.wsdd
wseaxis-source: Runs source service client endpoint
Usage: $ant wseaxis-source
wseaxis-sink: Runs sink service client endpoint
Usage: $ant wseaxis-sink
wseaxis-sourceframe: Runs source service client endpoint as a
Frame
Usage: $ant wseaxis-sourceframe
wseaxis-sinkframe: Runs sink service client endpoint as a
frame
Usage: $ant wseaxis-sinkframe
wseaxis-sourceproxy: Runs source proxy service client
Usage: $ant wseaxis-sourceproxy
wseaxis-sinkproxy: Runs sink proxy service client
Usage: $ant wseaxis-sinkproxy
wse-source: Starts source service end
point.
Usage: $ ant
wse-source -Dwse.source.hostname=mountain.ucs.indiana.edu
-Dwse.source.port=19000 -Dwse.submanager.address=tcp://mountain.ucs.indiana.edu:20000
wse-sm: Starts subscription manager service end point.
Usage: $ ant wse-sm
-Dwse.submanager.hostname=mountain.ucs.indiana.edu -Dwse.submanager.port=20000
wse-sink: Starts first sink service end point.
Usage: $ ant wse-sink
-Dwse.sink.hostname=mountain.ucs.indiana.edu -Dwse.sink.port=21000
-Dwse.source.address=tcp://mountain.ucs.indiana.edu:19000
wse-sink2: Starts second sink service end point.
Usage: $ ant wse-sink2
-Dwse.sink2.hostname=mountain.ucs.indiana.edu -Dwse.sink2.port=22000
-Dwse.source.address=tcp://mountain.ucs.indiana.edu:19000