- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Installing GT
- Platform Notes
- Migrating from GT2
- Migrating from GT3
- PDF version
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces
- Resource Properties
- Performance Studies
Table of Contents
The WS Replica Location Service (WS RLS) provides a Web services interface for the existing Replica Location Service (RLS). The features of the RLS have been preserved and interfaces should look familiar to users accustomed to working with the RLS. In most cases the interfaces are semantically similar (or identical) to the RLS operations, but effort has been made to adapt the interfaces to conform to expected style and conventions more typical of Web services. The interfaces consist of the WS-ReplicaLocationCatalog and the WS-ReplicaLocationIndex, representing the RLS Local Replica Catalog (LRC) and RLS Replica Location Index (RLI).
Features in GT 4.1.2 WS RLS
- Initial implementation of the WS RLS, which provides a Web services interface to the existing RLS.
- WS-ReplicaLocationCatalog: WSDL-defined interface for performing LRC operations, including creating/adding/deleting mappings, defining/undefining attribute definitions, and creating/modifying/removing attributes. The interface also defines a conceptual set of WS-ResourceProperties based upon which queries may be performed.
- A simple query dialect which may be used to form expressions to be used to query the WS-RLS based on logical/target names and attributes.
- WS-ReplicaLocationIndex: WSDL-defined interface for performing RLI operations. Since the RLI is used as a read-only query interface (querying the index of logical name entries), the WSDL defines domain specific operations. The operation of interest is the standard QueryResourceProperties.
The following problems and limitations are known to exist for WS RLS at the time of the 4.1.2 release:
- At this time, WS RLS only supports a limited query response for WS-ReplicaLocationIndex (i.e., index) lookups. When querying the index for a given logical name (say 'my-logical-name-x1105') the response is the URL for the catalogs that contain entries corresponding to the logical name (say 'https://mycataloghost:8443'). The limitation to this interface is that the complete URL path is not included in the response. Only the scheme, hostname, and port of the URL are returned to the client. The client must append the remaining path to form the complete URL suitable for contacting the catalog (in this example 'https://mycataloghost:8443/wsrf/services/ReplicaLocationCatalogService').
- At this time, dateTime attribute values are not supported. If you are interested in this feature, please contact us.
- At this time, the command-line tools for the WS RLS do not support the documented '-' option, which is intended to allow for command-line parameters to be read from
WS RLS depends on the following GT components:
- Java WS Core
- WS Authentication and Authorization
- Replica Location Service (RLS)
WS RLS depends on the following 3rd party software:
Protocol changes since GT 4.0
API changes since GT 4.0
Exception changes since GT 4.0
Schema changes since GT 4.0
Associated standards for WS RLS:
- Conforms to WS-RF family of specifications and WS-Addressing and WS-Security.
See GT 4.1.2 WS RLS for more information about this component.