ADL Middleware Server - HTTP Test Forms

The forms on this page (which work under Firefox and Safari, but not under IE7... sorry!) exercise the client services of a middleware server. The server can be selected from the menu below or specified by entering a base URL (should end with a '/').

After selecting a server, press the load button to load the server's configuration into the forms (not necessary, but a great convenience).

Middleware services

(help)
(hide)
The query servlet/service asynchronously queries one or more collections for items that match one or more constraints. The general structure of the ADL query language is defined by ADL-query.dtd and the standard ADL search buckets that constraints may be placed against are described under client interfaces. The return is an integer that identifies both the running query and the corresponding result set.

query

Enter or paste a query into the following box, or use the query builder forms below. Then press query to submit the query.

query builder

collections

ranking-method

maximum-results

(help) (hide) Enter query region coordinates in signed decimal degrees. If east is less than west, the region crosses the ±180° meridian.
bucket
operator
north
south
east
west

(help) (hide) Enter date range endpoints in YYYY-MM-DD notation.
bucket
operator
begin
end


bucket
operator
vocabulary
term


bucket
operator
text

(help) (hide) The identifier namespace is optional.
bucket
operator
namespace
identifier

(help) (hide) The unit of measure is optional.
bucket
operator
unit
value

(help) (hide) The target should be a fully-qualified ADL identifier, e.g., "adl_catalog:314159".
bucket
operator
target

(help) (hide) The results servlet/service accesses a result set. The `status` and `wait` operations both return the status of the result set as an XML document; the difference is that `wait` blocks until the result set is complete. The `get` operation returns the result at index index; the `multiget` operation, the results at indices [from, to). In both cases, which of the three standard ADL metadata views to return per result is specified by views as a comma-separated list of view names. The `get-query` operation returns the query that created the result set as an XML document. The `delete` operation deletes the result set.
id
op
index
from
to
views

(help) (hide) The metadata servlet/service returns a view of the metadata for a collection item. The item is specified by a qualified identifier using the syntax `collection:localIdentifier`. The view may be one of the three standard ADL metadata views (`adl:bucket`, `adl:browse`, or `adl:access`) or any other view supported by the item. The fictitious view `adl:view-list` returns a list of the views supported by the item.
view
id

(help) (hide) The reference servlet/service creates a collection that is a proxy to a remote collection. The remote collection is specified by a remote middleware server identified by an RMI or HTTP base URL and a remote collection name. The general syntax of an RMI base URL is `rmi://hostname[:port][/prefix/]`; if the URL includes a service prefix, it should end with a '`/`' (otherwise, the prefix is assumed to be "`/edu/ucsb/adl/middleware/rmi/`", which it is by default). The collection is referred to locally as localname if supplied.
baseurl
collection
localname

(help) (hide) The unload servlet/service unloads the drivers for a collection. Any subsequent reference to the collection will cause the collection's configuration files to be reloaded.
collection

Administrative servlets

(help) (hide) The cache_control servlet starts a background thread to preload a metadata cache, stops a previously-started thread, or empties a metadata cache. All options operate on a specified collection and metadata view. If "`*`" is specified for the view, all of the collection's caches are operated on.
op
collection
view

last modified 2009-07-20 10:29