The r-code compatibility rules in OpenEdge (Refer to Article P124103, OpenEdge 10.x and 11.x R-CODE bit compatibility rules ) dictate that 32 bit r-code cannot run on a 64 bit server using a 64 bit version of OpenEdge prior to 11.0. Therefore to deploy to 64 bit products on 64 bit servers, the source code requires recompilation. Since there isn't a 64 bit GUI client (until OpenEdge 11.3), r-code compilation will have to be performed by either a character or batch client. The difficulty is that in deployment environments, a Development license is not usually installed, so the compilation of the 32-bit source code to 64 bit r-code presents a dilemma.
Two Options are therefore available for deploying 32 bit application code to 64 bit servers production environments prior to OpenEdge 11.0.
Option 1: Encrypt 32-bit source code with XCODE
Use a Windows 32 bit Development client to encrypt the source using xcode. Refer to Article P147079, How to encrypt a source code using Xcode
2. Create a program that will compile your code and precompile it into r-code. (e.g. COMPILE VALUE(paramProgramPath) <options>)
3. Copy the compiler .r and encrypted application programs to the 64 bit server.
4. On the 64 bit server use -rx parameter at startup and execute the compiler program.
Option 2: Use a 64-bit development license
1. Install a 64 bit development server license on the server.
2. Copy the source code to the 64 bit environment.
3. Compile the code with the _progres character client using the Application Compiler from the Tools menu.
4. Run the code using the _progres character client.
