Kbase P115954: Considerations for ADM2 and Dynamics applications deployed on 64-bit platforms in OpenEdge 10.1A and
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/16/2009 |
|
Status: Verified
GOAL:
Considerations for ADM2 and Dynamics applications deployed on 64-bit platforms in OpenEdge 10.1A and later
GOAL:
How to deploy a Dynamics application on a 64-bit platform?
GOAL:
How to deploy an ADM2 application on a 64-bit platform?
GOAL:
Use cases for ADM2 or Dynamics applications to be deployed in 64-bit platforms
GOAL:
What needs to be done if there are customizations to the ADM2 when deploying to 64-bit platform?
GOAL:
What needs to be done if there are customizations to Dynamics when deploying to 64-bit platform?
FACT(s) (Environment):
UNIX
Linux x86 64-bit
OpenEdge 10.1x
Dynamics
OpenEdge 10.1A 64-bit
OpenEdge 10.1B 64-bit
FIX:
OpenEdge 10.1x 64-bit r-code is not portable to 32-bit platforms and vice versa. 64-bit r-code needs to be generated (compiled) with a 4GL compiler on a 64-bit platform, and 32-bit r-code needs to be generated (compiled) with a 4GL compiler on a 32-bit platform.
This means that 64-bit platforms will only be able to run r-code compiled on a 64-bit platform.
Customers need to be aware that this change will impact their ADM2 or Dynamics applications if they need to deploy them on 64-bit platforms. If this is the case then the customer does not need to deploy and recompile the framework product code to the 64 bit server. The easiest solution is to obtain a Development Server license for the 64 bit platform, which is free of charge and includes the 64 bit r-code.
The deployment use cases, including the corresponding packaging and compilation of the relevant application components on each case are:
1) ADM2 application with no ADM2 customizations, to be deployed to UNIX, Linux 32-bit platforms - Customer builds app with OpenEdge Studio or OpenEdge Architect. Customer compiles app with _progres on Windows and moves application code and shipped ADM2 code to deployed machines. This is what is done today.
2) ADM2 application with ADM2 customizations, to be deployed to UNIX, Linux 32-bit platforms - Customer builds app with OpenEdge Studio or OpenEdge Architect. Customer compiles app and customizations with _progres on Windows and moves application code and customized, compiled ADM2 code to deployed machines. This is what is done today.
3) ADM2 application with no ADM2 customizations, to be deployed to UNIX, Linux 64-bit platforms - Customer builds app with OpenEdge Studio or OpenEdge Architect. Customer moves application to OpenEdge Development Server on 64-bit machine to compile it. Customer moves their compiled app and tty/ADM2 (from OpenEdge Development Server) code to deployed machines.
4) ADM2 application with ADM2 customizations, to be deployed to UNIX, Linux 64-bit platforms - Customer builds app with OpenEdge Studio or OpenEdge Architect. Cus.tomer moves application and customizations to OpenEdge Development Server on 64-bit machine for compilation. Customer moves their compiled app and customized, compiled ADM2 code to deployed machines.
5) Progress Dynamics application with no Dynamics customizations, to be deployed to UNIX, Linux 32-bit platforms - Customer builds app with OpenEdge Studio. Customer compiles app with _progres on Windows and moves application code and shipped tty/dynamics code to deployed machines. This is what is done today.
6) Progress Dynamics application with Dynamics customizations to be deployed to UNIX, Linux 32-bit platforms - Customer builds app with OpenEdge Studio. Customer compiles app and customizations with _progres on Windows and moves application code and customized, compiled dynamics code to deployed machines. This is what is done today.
7) Progress Dynamics application with no Dynamics customizations, to be deployed to UNIX, Linux 64-bit platforms - Customer builds app with OpenEdge Studio. Customer moves application to OpenEdge Development Server on 64-bit machine to compile it. Customer moves their compiled app and tty/dynamics (from OpenEdge Development Server) code to deployed machines.
8) Progress Dynamics application with Dynamics, customizations, to be deployed to UNIX, Linux 64-bit platforms - Customer builds app with OpenEdge Studio. Customer moves application and customizations to OpenEdge Development Server on 64-bit machine for compilation. Customer moves their compiled app and customized, compiled dynamics code to deployed machines..