How To Upgrade from the Previous Release

This page provides information on how to upgrade from the previous release of OGSA-DAI (2.1) to the current release (2.2).

These are guidelines only and have not been tested. However if you run into problems when upgrading please do not hesitate to contact the OGSA-DAI team at:

http://bugs.ogsadai.org.uk.

Upgrading Your OGSA-DAI Deployment

To update your OGSA-DAI deployment within web service containers (providing your containers are still supported by the current release of OGSA-DAI) make the following changes. You may wish to consult the pages where are files located after deployment as you do this.

1. Update the XML Schema with the new schema in schema/ogsadai/xsd/activities
2. Update the OGSA-DAI JARs with the new JARs in lib
3. For OGSA-DAI WSI only:
   • In what follows:
     • WEBAPP is the WebApp into which OGSA-DAI WSI has been deployed (this is usually axis).
     • PORT is the port number upon which your container accepts connections (this is usually 8080).
   • Edit the schema/ogsadai/wsi/data_service.wsdl file in your container:
     1. Change the import line:

        <wsdl:import 
          namespace="http://ogsadai.org.uk/namespaces/2005/10/service/wsi/dataservice/bindings" 
          location="data_bindings.wsdl"/>
        

        to

        <wsdl:import 
          namespace="http://ogsadai.org.uk/namespaces/2005/10/service/wsi/dataservice/bindings" 
          location="http://localhost:PORT/WEBAPP/schema/ogsadai/wsi/data_bindings.wsdl"/>
        

     2. Make sure the soap:address element is as follows:

        <soap:address location="http://localhost:PORT/WEBAPP/services/"/>
        

   • Edit the schema/ogsadai/wsi/configurable_data_service.wsdl file in your container:
     1. Change the import line:

        <wsdl:import 
          namespace="http://ogsadai.org.uk/namespaces/2005/10/service/wsi/dataservice/bindings" 
          location="configurable_data_bindings.wsdl"/>
        

        to

        <wsdl:import 
          namespace="http://ogsadai.org.uk/namespaces/2005/10/service/wsi/dataservice/bindings" 
          location="http://localhost:PORT/WEBAPP/schema/ogsadai/wsi/configurable_data_bindings.wsdl"/>
        

     2. Make sure the soap:address element is as follows:

        <soap:address location="http://localhost:PORT/WEBAPP/services/"/>
        

4. For all deployed data service resources:
   • Edit the activity configuration file (activityConfig.xml).
   • Change the XML Schema name in the location attribute of the basePerformDocumentSchema element from general.xsd to perform.xsd
5. For all deployed relational data service resources:
   • Edit the data resource configuration file (dataResourceConfig.xml).
   • Remove the relationalMetaData element.
6. If you wish your deployed resources to expose our new activities then we recommend redeploying your resource.
7. Update code for any 3rd party activities:
   • Import statements will need to be updated for classes and interfaces that have been moved. The most common of these are shown in the Release Notes.
   • Note especially the changes to exceptions. We recommend the use of
     • uk.org.ogsadai.activity.ActivitySpecificationException for exceptions that are caused by problems with how a client has configured an activity (e.g. bad parameters). This replaces the old uk.org.ogsadai.common.exception.engine.activity.ActivityUserException.
     • uk.org.ogsadai.activity.ActivityExecutionException for exceptions that are caused by internal problems (e.g. some server-side problem outwith a client's control occurs). This replaces the old uk.org.ogsadai.common.exception.engine.activity.ActivitySystemException.

Upgrading Clients

• Update clients to compile under the new client toolkit APIs and handle the new exceptions if required.
• Import statements will need to be updated for classes and interfaces that have been moved. The most common of these are shown in the Release Notes.