Core: System Administrator's Guide

Overview
Core Quick Start
>Configuring OGSA extensions
Configuring the Logging Service

Configuring OGSA extensions

There are two main sections of the server-config.wsdd file that configure OGSA extensions (follow these links for the parameters in each file that pertain to the GT 3.2 Core):

global configuration
persistent services

File Summary
Filename: `server-config.wsdd` Default location: `<gt3-install-location>/etc` (installed with GT 3.2)
Global Configuration
This section configures options that become global throughout the Globus Toolkit. The configuration item (in bold) corresponds to the 'name' attribute in a parameter sub element, and the value is put as a 'value' attribute within the same parameter element:
where:
`schemaRoot <url>`	Optional. Indicates You can use this option if you want the container to read it's schema from a remote server. This can be useful especially for clients so that you don't have to copy around the whole schema directory to the location where you run the client.
`containerThreads <number of threads>`	Optional. This option sets the number of threads used in the standalone container.
`<protocol>Port <port>`	Optional. This option sets the port used to expose services running a particular protocol, e.g., httpPort or httpgPort. In general, the port is determined dynamically but in certain cases it must be defined explicitly (e.g. when deploying to Tomcat.)
`logicalHost <hostname>`	Optional. This option determines the hostname to use instead of default local host. The value can be both FQDN and just hostname.
`publishHostName <true/false>`	Optional. This option determines whether the hostname will be published instead of the IP.
`domainName <domain name>`	Optional. This option determines the domain name to append to host name if the value of `publishHostName` is true and the value of `logicalHost` is not qualified by a domain.
`disableDNS <true/false>`	Optional. This option determines whether or not DNS lookups will be attempted and the `logicalHost` or 'localhost' will be published.
Persistent Services
where:
`persistent <true/false>`	Optional. Indicates whether to treat this service as a persistent grid service, i.e it will be instantiated at container start-up.
`schemaPath <path>`	Optional. Indicates the path inside of http server where WSDL for the persistent service is defined.
`sweepDelay <delay in milliseconds>`	Optional. Indicates the delay between factory sweeps to destroy timed out service instances.
`handleProtocol <protocol>`	Optional. Indicates the protocol used to publish handles. Only https and http are allowed in the current OGSA specification. The default value is `http`. Note: If a non default protocol is selected, it is recommended to accompany this configuration with a global configuration of <protocol>Port. See above.
`lifecycle <true/false>`	Optional. Indicates whether instances are to be checkpointed into the deployment descriptor to maintain state between server lifecycles.

If instance- is prepended to the property name it will configure the instances of the configured service (in case of a factory service) as opposed to the service itself. For a further discussion of configuration variables see Java Programming or look at the properties defined in org.globus.ogsa.ServiceProperties in the API documentation.

In the case of the standalone container some Java System properties can be set to customize where the schemas will be picked up:

-Dorg.globus.ogsa.schema.root : tells the process what remote url can be used to fetch the schemas

-Dorg.globus.ogsa.server.webroot : tells the standalone http server where in the file system the HTTP GET requests should be redirected (must be absolute path)