F
frank.meulblok
Guest
My first thought is that you should have been working on phasing out Dynamics for a few years already. The signs that it's dead-end technology that you want to move away from started to appear way back in OpenEdge 10.0A, when it did not even get updated to support the new datatypes. Followed by not being updated to use client-principal-based authentication (available since 10.1A if memory serves), it officially being deprecated in 10.2B (+/- 1 release) etc. It's becoming less and less sustainable as time goes by, and that trend is NOT going to reverse. (What will you do when the 32-bit OpenEdge for Windows gets the axe ?) That little rant aside: 1. Code changes to support the PASOE may turn out to be minimal. AFAIK the ADM2 code Dynamics is based on did get a few fixes to be deployable on a PASOE. If I'm correct there, and assuming your application was designed to run in stateless mode (which Dynamics was primarily targetted at), you should be able to get quite far by opening up the APSV transport on the PASOE and changing your AppServer partition definitions to use the PASOE's AppServer URL. You will still miss out on all the new security features etc. that the PASOE provides though. 2. Regarding going back to classic AppBuilder - better check if that's actually still available in OpenEdge 12. Also, keep in mind this KB article knowledgebase.progress.com/.../Will-it-be-possible-to-run-an-OpenEdge-Dynamics-application-to-OpenEdge-12-0 , and make sure to carry over the Dynamics code from an older release. AFAIK the Dynamics-specific tooling is also part of that set of code. Otherwise you'll be stuck developing on an older release and deploying on a newer one. With all the complications that introduces during building & testing.
Continue reading...
Continue reading...