If you plan on using Globus Toolkit with Tomcat then you need to deploy Globus Toolkit onto Tomcat.

	Note
	If you deploy Globus Toolkit as a root user and want users with other accounts on your file system to be able to start it up and shut it down then, after deploying it, you'll need to do a chown or similar to give them permission to do so.

If you do not plan to use Tomcat but just the Globus Toolkit stand-alone container then please skip on to Chapter 37, Deploy OGSA-DAI.

The Globus Toolkit user doc contains full information on how to do this but this is summarised below.

	Important
	If you are planning to use transport level security then the task of deploying Globus Toolkit onto Tomcat is more complex than that presented here. See the Globus Toolkit documentation.

If you are not using security and want to avoid startup errors being logged then you may want to edit:

$GLOBUS_LOCATION/etc/globus_wsrf_core/server-config.wsdd

and comment out the lines:

<parameter name="containerSecDesc" 
           value="etc/globus_wsrf_core/global_security_descriptor.xml"/>

i.e.:

<!--
<parameter name="containerSecDesc" 
           value="etc/globus_wsrf_core/global_security_descriptor.xml"/>
-->

To deploy Globus Toolkit into Tomcat run the following:

$ cd $GLOBUS_LOCATION
$ ant -f share/globus_wsrf_common/tomcat/tomcat.xml deployTomcat \
      -Dtomcat.dir=$CATALINA_HOME

If you have deployed the full Globus Toolkit (and not Globus Toolkit Web Services Core) and plan to use MDS registration and the Globus index service but are NOT using security then you'll need to patch a file in Tomcat.