Kbase P125995: How to move older versions of ADM2 to newer OpenEdge releases ?
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  10/02/2009 |
|
Status: Verified
GOAL:
How to move older versions of ADM2 to newer OpenEdge releases ?
GOAL:
How to migrate to later OpenEdge release while maintaining same ADM2 version ?
GOAL:
How to avoid changes in behavior when migrating SmartObjects based applications ?
GOAL:
How to migrate V9 ADM application to OE?
GOAL:
How to migration ADM2 application?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
When migrating to newer OpenEdge releases, existing applications using SmartObjects may show differences in behavior due to changes in the SmartObjects (ADM2) framework code.
Such changes may be implemented to fix bugs, to add new features or to improve overall behavior.
To avoid issues occurring from such changes, it is advised that during the initial phase of the upgrade the existing ADM2 code from the older release is used.
The following steps outline how to set up the migrated environment to allow for a smooth transition.
-- Preparing for development --
1. create a new directory within application code path, containing subdirectory called src.
2. From old Progress release, copy the files from <install>\gui to the <new source dir>\src directory
3. From old Progress release, copy the directory <install>\src\adm2 to the <new source dir>\src directory (creating <new dir>\src\adm2 and subdirectories)
4. In the new OpenEdge release, add the <new source dir>\ and <new source dir>\src\ to the propath.
-- Preparing for deployment --
5. Create a directory <rcode dir>\gui in application deployment path (= path where r-code is stored).
Add subdirectories \gui\adm2, \gui\adm2\custom, \gui\adm2\image, \gui\adm2\support, \gui\adm2\template. (This replicates directory structure created under \src)
6. Use application compiler to recompile the old ADM2 version under the new OpenEdge release:
Compile the "<new source dir>\src\adm2" directory and specify "<rcode dir>\gui\adm2" under compile -> save into.
(Depending on how the environment is set up, this may be combined with compiling the rest of the application code)
7. Copy the contents of <new source dir>\src\adm2\image to <rcode dir>\gui\adm2\image
8. Add <rcode dir>\gui\ to the propath used at run-time
Note that this is meant to prevent issues on the short term.
After the migration is complete, it is advised to start testing with the current version of the ADM2 shipped with the newer OpenEdge release in order to ensure the framework code itself can also be upgraded.