This documents the complete range of options available when deploying OGSA-DAI.
To build a GAR file run:
$ ant buildGAR -Dgt.dir=$GLOBUS_LOCATION \ [-Ddai.gar=GAR-LOCATION] \ [-Ddai.host=HOST] \ [-Ddai.port=PORT] \ [-Ddai.webapp=WEBAPP] \ [-Ddai.dres.service.name=DRES-SERVICE] \ [-Ddai.dris.service.name=DRIS-SERVICE] \ [-Ddai.dsos.service.name=DSOS-SERVICE-NAME] \ [-Ddai.dsis.service.name=DSIS-SERVICE-NAME] \ [-Ddai.sms.service.name-SMS-SERVICE-NAME] \ [-Ddai.rms.service.name=RMS-SERVICE-NAME]
where:
GAR-LOCATION - destination file for
GAR file. Default build/dai.gar.
HOST - host on which server is
running. This must not
be localhost since the host
name is inserted into the OGSA-DAI server configuration and is
used in the construction of web service endpoint references.
PORT - port number on server
accepts requests. Default 8080.
WEBAPP - name of OGSA-DAI webapp.
Default wsrf.
DRES-SERVICE - data request execution
service name. Default
DataRequestExecutionService.
DRIS-SERVICE - data resource
information service name. Default
DataResourceInformationService.
DSOS-SERVICE - data source service
name. Default
DataSourceService.
DSIS-SERVICE - data sink service
name. Default
DataSinkService.
SMS-SERVICE - session management
service name. Default
SessionManagementService.
RMS-SERVICE - request management
service name. Default
RequestManagementService.
Choosing a service name SERVICE-NAME
results, after deployment, in a service with URL:
http://HOST:PORT/WEBAPP/services/GAR-NANE/SERVICE-NAME
where GAR-NAME is the prefix
of the GAR file name e.g. dai.
To deploy an OGSA-DAI GT GAR file onto the Globus Toolkit container
$ ant deployGAR -Dgt.dir=$GLOBUS_LOCATION \ [-Ddai.gar=GAR-LOCATION] \ [-Ddai.host=HOST] \ [-Ddai.port=PORT] \ [-Ddai.webapp=WEBAPP]
The GAR file will be deployed into Globus Toolkit
container. The GAR file prefix (e.g.
dai determines the name of the
directory where deployment descriptors and other configuration files
go in the Globus Toolkit etc
directory.
To deploy an OGSA-DAI GT GAR file onto Tomcat
$ ant deployGARTomcat -Dgt.dir=$GLOBUS_LOCATION \ -Dtomcat.dir=$CATALINA_HOME \ [-Ddai.gar=LOCATION-OF-BUILT-GAR] \ [-Ddai.host=HOST] \ [-Ddai.port=PORT] \ [-Ddai.webapp=WEBAPP]
![]() | Note |
|---|---|
This mode of deployment is not supported by GT. This is our own
version. GT recommend deployment into a GT container
(e.g. using deployGAR) and then
deploying the GT container as a whole into Tomcat using the Globus
Toolkit using deployTomcat command.
|
To build a GAR file and then deploy the GAR file onto the Globus Toolkit container
$ ant buildAndDeployGAR
This command just invokes the buildGAR
and deployGAR commands so the
command-line options are as for these two commands.
To build a GAR file and then deploy the GAR file into Tomcat
$ ant buildAndDeployGARTomcat
This command just invokes the
buildGARTomcat and
deployGARTomcat commands so the
command-line options are as for these two commands.
To summarize, there are three possible deployment and usage approaches:
The Globus Toolkit deployGAR
command can be run as follows:
$ ant -f $GLOBUS_LOCATION/share/globus_wsrf_common/build-packages.xml \ deployGar -Dgar.name=GAR-NAME.gar
For example:
$ ant -f $GLOBUS_LOCATION/share/globus_wsrf_common/build-packages.xml \ deployGar -Dgar.name=dai.gar
Useful links: