Interoperating with OGSA-DAI WSRF 2.2

OGSA-DAI WSI 2.2 clients and data transport activities can inter-operate with any OGSA-DAI data service written using OGSA-DAI WSI 2.2. They can also, however, interoperate with services written using OGSA-DAI WSRF 2.2.

WS-Addressing 1.0

In OGSA-DAI WSI the ID of a data service resource is provided as part of the URL of the data service when contacting the service on the server. In contrast, for OGSA-DAI WSRF it is added to the operation invocation in the form of a so-called WS-Addressing header.

We bundle the Apache implementation of WS-Addressing 1.0. This is in thirdparty/addressing-1.0.jar.

The source is available here:

http://ws.apache.org/addressing

If you compile from source we recommend building a JAR called addressing-1.0.jar and placing this in the thirdparty directory.

Configuring the Server

To configure OGSA-DAI, server-side, to support interoperability with OGSA-DAI WSRF you should:

• Copy the client-side handler descriptor (the OGSA-DAI skeletons/client-config.wsdd file) into the OGSA-DAI classes directory in your container i.e.:

  $ cp OGSA-DAI/skeletons/client-config.wsdd CONTAINER/webapps/axis/WEB-INF/classes
  

Configuring Clients

To configure OGSA-DAI's pre-bundled clients you need to:

• Copy the client-side handler descriptor (the OGSA-DAI skeletons/client-config.wsdd file) into the OGSA-DAI base directory i.e.:

  $ cp OGSA-DAI/skeletons/client-config.wsdd OGSA-DAI
  

To configure your own clients you need to ensure that the client-config.wsdd file is in a directory which is in your CLASSPATH.