Deploying Data Service Resources

These pages describe how to deploy data service resources. After deployment, data service resources can be exposed by data services.

The characteristics of a data service resource are specified in a data service resource file, the format of which is described below. There are two ways to create a data service resource file and deploy a data service resource:

• Create or edit a data service resource file using a text editor, then deploy the data service resource using the command-line client.
• Create or edit a data service resource file and optionally deploy a data service resource using the GUI client.

As a reminder, we provide a list of supported data resources.

Data Service Resource Files

A data service resource file is used to specify the properties of your data service resource. This is a simple properties file consisting of argument=value values. You can reuse the same file to deploy the same data service resource under different names or to customise a specific configuration in small or major ways. Alternatively you can just write a new file each time.

In the OGSA-DAI WSRF distribution directory we provide an example: data.service.resource.properties. The file is fully commented.

The properties are as follows:

• dai.resource.id= - name for the data service resource.
• dai.data.resource.type=[Relational | XML | Files | MultiResource] - the type of data resource to which the data service resource provides access.
• dai.product.name= - data resource product name (optional - ignored for files and multi resources).
• dai.product.vendor= - data resource product vendor (optional - ignored for files and multi resources).
• dai.product.version= - data resource product version (optional - ignored for files and multi resources).
• dai.data.resource.uri= - data resource URI. This must be compatible with the driver class specified next (ignored for multi resources).
• dai.driver.class= - data resource driver class name (ignored for files and multi resources).
• dai.credential= - Grid certificate credentials of a user permitted to access the data resource. If omitted then any user will be allowed access (ignored for multi resources).
• dai.user.name= - data resource user name. Optional only if there is no user name required for a database (ignored for multi resources).
• dai.password= - corresponding data resource password. Optional if there is no user name required, or if the password is null (ignored for multi resources).
• dai.data.service.resource.uri.one= - for multi resources only, the URL of a service exposing the first of the aggregated relational resources.
• dai.data.service.resource.id.one= - for multi resources only, the ID of the first of the aggregated relational resources.
• dai.data.service.resource.description.one= - for multi resources only, a description of the first of the aggregated relational resources (optional).
• dai.data.service.resource.uri.two= - for multi resources only, the URL of a service exposing the second of the aggregated relational resources.
• dai.data.service.resource.id.two= - for multi resources only, the ID of the second of the aggregated relational resources.
• dai.data.service.resource.description.two= - for multi resources only, a description of the second of the aggregated relational resources (optional).