Guidelines for Migrating to OpenEdge 12
Prior to installing OpenEdge 12.0, verify the certified platforms and review deprecated and de-supported features and functionality:
- OpenEdge 12 Platform & Product Availability Guide
Since OpenEdge 12.1, Java is no longer provided with the OpenEdge install media. For further information refer to Article:
When upgrading from an OpenEdge 11 environment to OpenEdge 12.0 specific tasks depend on the site-specific OpenEdge Components that are used. Guidelines for upgrading OpenEdge 11 environments to OpenEdge 12 are outlined in the following OpenEdge Information Hub Documentation:
- Overview of Upgrading to OpenEdge 12.0
Database
OE 11 to 12:
https://docs.progress.com/bundle/openedge-database-management/page/Convert-an-OpenEdge-Release-11-Database-to-OpenEdge-Release-12.html
OE 10 to 12:
https://docs.progress.com/bundle/openedge-database-management/page/Convert-an-OpenEdge-Release-10-database-to-OpenEdge-Release-12.html
Note: Use the same steps as above to convert a DataServer schema holder database to OE 12 schema.
Migrating to OpenEdge 12 PAS for OpenEdge
Migrating an 11.7 PASOE instance requires creating a new instance, recompiling the r-code and regenerating any PDSOE projects that are exporting war files.
Soap .wsm and Rest .paar files can just be deployed to the new instance.
For pre-11.7 projects follow the "Manually upgrade the existing OpenEdge 11-based project"
For migrating Classic AppServer Applications to PASOE refer to the following page in the OpenEdge Information Hub:
OpenEdge 12 Migration: Additional Information:
OpenEdge 12 clients can connect to an OpenEdge 11 database with TCP, but r-code needs to be re-compiled as r-code is not compatible between major releases. OpenEdge 11 clients cannot connect to OpenEdge 12 databases, this includes Classic AppServer Agents or Classic WebSpeed Agents.
OpenEdge Management 12 is abstracted from the AdminServer running on as a PASOE instance webapp
Migrating OpenEdge applications with 32-bit OCX in an OpenEdge 12 64-bit Development environment.
Migrating a Dynamics application from OpenEdge 10.x or 11.0.x to OpenEdge 12.0
OpenEdge 12 Known Issues:
OpenEdge 12 databases fail to compile the code which uses the _startup or _statbase VST:
Installing additional components (products) to an existing OpenEdge 12 installation
Permissions when using earlier versions of dbutils provided in OpenEdge 12 for migration
