In an OGSA-DAI GT deployment Tomcat these files are located relative to the root directory of Globus Toolkit as deployed under Tomcat. By default this will be within the directory:

/PATH/TO/TOMCAT/webapps/wsrf/

Within this directory there are the following files and directories

In an OGSA-DAI GT deployment onto the Globus Toolkit standalone container these files are located relative to the root directory of Globus Toolkit.

The activity specification file has name activities.txt and is located in the OGSA-DAI configuration files directory Section 17.2.1, “Configuration files directory”.

The activity specification file declares, for each activity, the following information:

To summarise therefore, each entry is of the form:

id=ACTIVITY-ID 
class=ACTIVITY-CLASS
description=ACTIVITY-DESCRIPTION
CONFIG
[KEY=VALUE]*
END

and the activity specification file consists of 0 or more such entries.

The standard activity specification file can be seen in OGSA-DAI source or binary distributions in deploy/server-config/activities.txt.

The logins file has name the logins.txt and is located in the OGSA-DAI configuration files directory Section 17.2.1, “Configuration files directory”.

The logins file declares zero or more mappings from distinguished names to database usernames and passwords for zero or more OGSA-DAI data resources.

To summarise therefore, each resource can have an entry of form:

id=RESOURCE-ID
[
userID=STRING or *
username=USER
password=PASSWORD
LOGIN-END
]*
END

and the logins file contains zero or more such entries.

An example logins file is as follows, which declares two mappings for BanglesDataResource, two for MadnessDataResource and none for SpecialsDataResource

id=uk.org.ogsadai.BanglesDataResource
userID=/C=USA/O=Music/OU=Bands/L=Bangles/CN=Susanna Hoffs
username=susanna
password=EternalFlame
LOGIN-END
userID=/C=USA/O=Music/OU=Bands/L=Bangles/CN=Debbie Petersen
username=debbie
password=ManicMonday
LOGIN-END
END
id=uk.org.ogsadai.MadnessDataResource
userID=/C=UK/O=Music/OU=Bands/L=Madness/CN=Suggs
username=graham
password=mcpherson
userID=*
username=nutty
password=boys
END
id=uk.org.ogsadai.SpecialsDataResource
END

Resource files are named after their resource. The file name is exactly identical to the resource ID and vice-versa. Resource IDs consist a namespace and a local part. The following are examples of valid resource IDs (and thus also file names):

SomeDataResource
some.company.SomeOtherResource
DataRequestExecutionResource
MySQLDataResource
uk.org.ogsadai.JDBCResource

Resource files reside in a resources directory located in the OGSA-DAI configuration files directory Section 17.2.1, “Configuration files directory”.

	Caution
	All files in resources are assumed to be resource files.

A resource file declares the following information for a resource:

Data request execution resource files use the generic resource format shown above in Section 17.2.4.2, “Resource files format” but also support the following.

Data resource files use the generic resource format shown above in Section 17.2.4.2, “Resource files format” but also support the following.

Session files use the generic resource format shown above in Section 17.2.4.2, “Resource files format” but also support the following.

Data sink files use the generic resource format shown above in Section 17.2.4.2, “Resource files format” but also support the following.

Data source files use the generic resource format shown above in Section 17.2.4.2, “Resource files format” but also support the following.

Request resource files use the generic resource format shown above in Section 17.2.4.2, “Resource files format” but also support the following.

To summarise therefore, a resource file starts with a block of form:

id=RESOURCE-ID
type=RESOURCE-TYPE
creationTime=CREATION-TIME
terminationTime=TERMINATION-TIME
PROPERTIES
[NAME=VALUE]*
END
CONFIG
[KEY=VALUE]*
END
ACTIVITIES
[ACTIVITY-NAME=ACTIVITY-ID]*
END

Data request execution resources then have a block of form:

acceptRequests=[true|false]
ENGINE-CONFIG
[KEY=VALUE]*
END

Section 17.2.7, “Data request execution resource configuration properties” lists OGSA-DAI data request execution resource configuration properties.

Data resources then have a block of form:

dataResourceClass=CLASS-NAME

Section 17.2.8, “Data resource configuration properties and classes” lists OGSA-DAI data resource classes and configuration properties.

Session resources then have a block of form:

defaultTerminationTime=TERMINATION-TIME-IN-MINUTES-GREATER-THAN-OR-EQ-0
SESSION-STATE
[KEY=VALUE]*
END

Data source resources then have a block of form:

defaultTerminationTime=TERMINATION-TIME-IN-MINUTES-GREATER-THAN-OR-EQ-0
bufferSize=BUFFER-SIZE-GREATER-THAN-ZERO

Data sink resources then have a block of form:

defaultTerminationTime=TERMINATION-TIME-IN-MINUTES-GREATER-THAN-OR-EQ-0

Request resources then have a block of form:

defaultTerminationTime=TERMINATION-TIME-IN-MINUTES-GREATER-THAN-1

The standard OGSA-DAI data request execution resource file can be seen in OGSA-DAI source or binary distributions in deploy/server-config/resources/.

Example OGSA-DAI data resource files - which are used in deploying data resources - can be seen in OGSA-DAI source or binary distributions in deploy/config-blanks.

Resource templates are named after the type of resource they are the template for. Resource template IDs have the same format as resource IDs i.e. a namespace and a local part. Section I.3, “Default resource template IDs” lists OGSA-DAIs standard resource template IDs.

Resource template files reside in a resources directory located in the OGSA-DAI configuration files directory Section 17.2.1, “Configuration files directory”.

The format for resource template files is the same as for resource files.

Resource templates for the standard OGSA-DAI session, request, data source and data sink resources can be seen in OGSA-DAI source or binary distributions in deploy/server-config/resourceTemplates/.

The common components configuration file has the name config.txt and is located in the OGSA-DAI configuration files directory Section 17.2.1, “Configuration files directory”.

The common components configuration file declares zero or more configuration values for common OGSA-DAI components.

To summarise therefore, this file is of the form:

[KEY=VALUE1]*

An example common components configuration file can be seen in OGSA-DAI source or binary distributions in deploy/server-config/config.txt.

OGSA-DAI data resources are configured to expose JDBC data resources using the following configuration properties and class name:

OGSA-DAI data resources are configured to expose XMLDB data resources using the following configuration properties and class name:

OGSA-DAI data resources are configured to expose file system data resources using the following configuration properties and class name:

OGSA-DAI data resources are configured to expose resource groups - groups of resource IDs - using the following configuration properties and class name:

Data resources are an OGSA-DAI extensibility point. Third party developers may implement their own data resource classes which will require implementation-specific configuration settings. The third party developers will be able to advise you of these. Please see Chapter 30, How to write a data resource for more details.