|2 - Taverna 2.1.2 Configuration and Installation||caGrid 1.4 Taverna Service Administrators Guide||4 - Verifying the Installation|
Once the Taverna 2.1.2 Workflow Service and the Taverna 2.1.2 Workflow Engine are installed, deploy the Taverna service. Deploying the service consists of notifying the service of where the Taverna 2.1.2 repository is located. This is done in two steps: editing the service.properties file and deploying the service in the Tomcat container.
Before deploying the service in the Tomcat container, edit the service.properties file to set the tavernaDir and baseRepositoryDir entries to point to the correct locations of the Taverna 2.1.2 artifacts.
In addition, the caGrid Taverna workflow service now contains a service property called concurrentWorkflows. The value of this property, as the name suggests, sets the maximum number of workflows allowed to run concurrently at any given time. This allows the administrators to control the load on the service, which is useful in instances when users submit large, memory-intensive workflows such as the Lymphoma prediction workflow. By default, each workflow is allocated 1gb of memory for execution. Administrators can change this memory allocation, depending on the amount of memory resident on the host computer used for deployment of the service.
|You must use absolute paths in the file. Do NOT include environment variables in the paths.|
If you retained the defaults for the caGrid and Taverna installations, the values for the directory and concurrent workflow entries are as follows:
- tavernaDir = $TWS_HOME/taverna
- baseRepositoryDir = $TWS_HOME/taverna/target/repository
The figure below shows a terminal window of the entries in the taverna service.properties file.
Keep in mind that for these instructions, the $TWS_HOME directory is identified as $CAGRID_HOME/caGrid/projects/TavernaWorkflowService, and $CAGRID_HOME is /caGrid-1-0/. If you changed the target directories for the installation of either caGrid or Taverna, be sure to alter the values shown above to reflect the appropriate path(s).
|NOTE: If you have both Taverna 2.0 and 2.1.2 installed, you can use either installation, however you MUST alter the directory entries in this file to point to the installation you want to use.|
Running the ant deployTomcat command deploys the caGrid Taverna Workflow Service in the Tomcat container.
Assuming that you have already set the $CATALINA_HOME environment variable from within $TWS_HOME, run the following command:
When finished, you should receive a Deploy Successful message. If you have not set the $CATALINA_HOME environment variable, you MUST do so prior to this step, being sure the variable points to the location where Tomcat is installed.
In order to verify the installation, deploy the caGrid Taverna workflow service to your Globus installation. This will cause the creation of a client that can be used for testing.