Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

> ## Recommended procedure for deploying across versions

> The procedure that Progress Software Corporation recommends for deploying objects across versions is not much different from deploying an object to a central Repository. For more information on Repository object deployment and the tools described in this procedure, see the deployment white papers posted on the following PSDN Web site:

>     http://psdn.progress.com/library/white_papers/dynamicswp/index.ssp

> | To deploy Repository objects across versions:

> 1. Before undertaking any work that needs to be deployed across versions, determine what objects will be affected and what those objects look like in each version. If you plan to create a new object, you can create it in either version (see Step 2). If you plan to change an existing object, determine what additional functionality can be lost in either version.

> 2. Once you understand the affected objects, decide the version where you will do the work. Typically, it is better to do the development work in the later version, where you are likely to add more features. It is always easier to remove functionality from an object than to add it. The version where you do the initial development work is your source version, and the version where you deploy this initial development work is your target version.

> 3. Before doing any work in the source version, reset the data modified status for your source development Repository (using Deployment Reset Data Modified Status from the Administration tool) so you can easily determine what changes you have made.

> 4. Implement your changes.

> 5. Dump all the data you have modified using the dataset export tool (Deployment Dataset Export). The exported ADOs contain the changes that you made.

> 6. Load the ADOs that you exported in Step 5 into the central Repository of your source version using the dataset import tool (Deployment Dataset Import).

> 7. Before doing any work in the target version, reset the data modified status for your target development Repository (using Deployment Reset Data Modified Status from the Administration tool) so you can easily identify the affected objects.

> 8. Load the ADOs that you exported in Step 5 into the development Repository of your target version using the dataset import tool (Deployment Dataset Import). In Dataset Import, be sure to check the Set modified status toggle box so these objects can be easily identifiable after they have been loaded.

> 9. Test the objects you have loaded and redo any work that has been lost during the import.

> 10. Complete any additional functionality required to finish the objects for the target version.

> 11. Dump all the data you have modified in the target development Repository using the dataset export tool (Deployment Dataset Export). The exported ADOs contain the objects you imported from the source version plus any additional changes that you have made.

> 12. Load the ADOs that you exported in Step 11 into the central Repository of your target version using the dataset import tool (Deployment Dataset Import).

> Your cross-version deployment should be complete.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095