The basic migration path for BEA AquaLogic Data Services Platform 2.0.n application and projects is straightforward. This section provides instructions for such upgrades including:
Prior to installing AquaLogic Data Services Platform, a supported version of WebLogic Platform 8.1 must be installed and configured properly. See Supported Configurations in AquaLogic Data Services Platform Release Notes for versions supported by this release.
In order to upgrade an application created under AquaLogic Data Services Platform 2.0x or 2.1 you must first install AquaLogic Data Services Platform 2.5. In a production environment, that installation must be completed for each WebLogic Platform 8.1 domain that you are using with AquaLogic Data Services Platform.
Follow the appropriate preparation, installation, and post-installation steps described in other sections of this document starting with Installation Prerequisites.
There are a several of steps to take when upgrading to the latest version of AquaLogic Data Services Platform.
Applications can be upgraded through WebLogic Workshop or using the AquaLogic Data Services Platform 2.5 Convert utility.
After you have installed AquaLogic Data Services Platform 2.5 you need to upgrade several JAR files in your existing AquaLogic Data Services Platform applications in order to deploy those applications under AquaLogic Data Services Platform 2.5. In WebLogic Workshop the update process is semi-automatic. When you open your application in WebLogic Workshop you will get a message indicated that some AquaLogic Data Services Platform JAR files are out-of-date and asking if you want to update your application.
Choose Yes to update the files. This will automatically cause your application to be built or rebuilt.
Note: | If you choose No, your 2.0 application will not be updated and you will not be able to deploy it under AquaLogic Data Services Platform 2.5. |
If your AquaLogic Data Services Platform 2.0 or 2.1 application is already packaged in an EAR file you can use a command-line utility to upgrade the EAR to AquaLogic Data Services Platform 2.5. The utility inspects the EAR file for out-of-date copies of the following:
If pre-AquaLogic Data Services Platform 2.5 versions of these files are found, they are replaced with 2.5 versions.
To upgrade a Windows-based AquaLogic Data Services Platform 2.0 or 2.1 EAR file to AquaLogic Data Services Platform 2.5 using the Convert migration utility following these steps:
<WL_HOME>\server\bin\setWLSEnv.cmd
<WL_HOME>\liquiddata\bin\convert.cmd myEAR.ear
To upgrade a UNIX-based AquaLogic Data Services Platform 2.0 EAR file to AquaLogic Data Services Platform 2.5 using the Convert migration utility following these steps:
Versions of AquaLogic Data Services Platform prior to version 2.1 managed functions returning sequences by generating additional "arrayOf" types (.xsd
schema files) adjacent to the original schema files. For example, when a data service was created around an XMLtype of customer (customer.xsd
) an XML type arrayOfcustomer (arrayOfCustomer.xsd
) was created automatically. Applications calling functions returning sequences could then utilize the arrayOf type.
This approach to handling functions returning sequences has been deprecated. Instead, functions returning sequences of records are handled by converting each item in the sequence into a service data object (SDO). With AquaLogic Data Services Platform 2.1 and later, Java arrays of SDO are supported. (For details on SDO and handling of sequence SDOs see the Application Developer's Guide.)
If your AquaLogic Data Services Platform project was created using a version of AquaLogic Data Services Platform prior to 2.1 you have a choice:
You can access the Migrate Data Services Project option by right-clicking on your AquaLogic Data Services Platform project (see Figure 5-3).
Note: | As always, it is recommended that you back up your application or project before attempting a migration. |
Note: | After migrating projects, existing Java mediator client code that relied upon the "ArrayOf" types will need to use a sequence of SDO objects instead of the ArrayOf SDO object. |
Note: | Migration of projects to AquaLogic Data Services Platform 2.5 are not reversible. |