Administration
caGrid Transfer 1.4 Administrators Guide
 |
 |
 |
 |
Contents |
 |
 |
 |
 |
Deploying a Service that Uses caGrid Transfer
The caGrid Transfer service MUST be deployed to the same container that the invoking grid service in deployed. Like all caGrid services, only Tomcat and JBoss are currently supported. Prior to deployment of caGrid Transfer, Globus must be deployed to the container, and (if desired) security configuration must be completed. This can be accomplished by the caGrid Installer, or manually by following the instructions provided by Globus
.
After you have installed and setup your container, you can deploy the caGrid Transfer Service. This is accomplished by entering the caGrid Transfer project directory: From the top of the caGrid release:
cd projects/transfer
Then deploy to either Tomcat or JBoss (tomcat example below):
ant -Dno.deployment.validation=true deployTomcat
Next, deploy your service by entering the services directory:
cd <my services directory>
Then deploy to either Tomcat or JBoss (tomcat example below):
ant deployTomcat
Configuring the Transfer Service
The service.properties file of the Transfer Service contains properties that can configure the Transfer service in certain ways. If you change any of these properties you will need to redeploy the Transfer Service as described above and restart the container.
| Property | Description |
|---|---|
| transferServletPathName=/caGridTransfer/TransferServlet | The web path that the transfer servlet was deployed to. By default this is correct, however, if you modified the build and deploy of the transfer webapp you may be deploying it to another webapp. If this is the case it the grid service will need to know the change and this property will tell it. |
| storageDirectory=transferCache | This is the storage directory which is relative to the etc directory of this deployed transfer grid service. This can be changed to store on other locations on the machine, however, they must be relative paths from the etc directory of the transfer grid service once it is deployed to the container. |
| defaultTransferServiceContextTerminationTimeInMinutes=30 | This property controls the default termination time that gets set on a transfer resource when it is created. It will automatically remove itself after 30 minutes to help keep the disk clean. This can be modified based on the usage pattern you plan to have on this server. If there are many little transfers that are picked up immediately you can make this shorter and if the transfers are large and may hang around for a while before being transferred you can make this a larger number. |