Coexistent installation of 32-bit and 64-bit OpenEdge

You can install a single installation of both 32-bit and 64-bit OpenEdge of the same version on a Windows 64-bit machine. This enables you to use 64-bit OpenEdge server processes for 32-bit OpenEdge clients or vice versa on the same machine. If you migrate an existing 32-bit application to 64-bit OpenEdge and need both platforms available, this allows you to run both platforms on the same machine.

The platforms work independently. You can identify each installation by “32-bit” or “64-bit” that has been appended to names. It avoids any namespace conflicts for the changes that are readily visible to users.

Note: You can install both 32-bit OpenEdge and 64-bit OpenEdge on a 64-bit Windows machine, but you must not install them simultaneously. You should wait for one installation process to complete and only then begin the other. You can have a single installation of each platform for a particular release.

Coexistence of two platforms on the same Windows 64-bit machine requires special considerations, as follows:

Separate install directories

OpenEdge by default provides different install directories for the two platforms. You can change the default directories but make sure that the directories are different for the different platforms.

Separate Program Groups folders

If you install both 32-bit and 64-bit OpenEdge on a 64-bit Windows machine, you can identify them by "32-bit" or "64-bit" when you start OpenEdge from the Start menu.

Separate Uninstall options

You can uninstall only 32-bit OpenEdge or 64-bit OpenEdge at one time; the Uninstall option does not uninstall both the installations together.

When you install OpenEdge, OpenEdge checks if an AdminService exists and, if it does, OpenEdge does not set the new AdminService to start automatically. You have to manually update the relevant ports if you want AdminService of both the platforms to start automatically.

In the Windows Services list, 32-bit and 64-bit OpenEdge have separate entries each for AdminService: AdminService for OpenEdge <version> (32-bit) and AdminService for OpenEdge < version > (64-bit). Make sure that any script that automatically starts AdminService is updated with these names.

Note: If you install or remove AdminService using admsrvc.exe in proenv, for any OpenEdge version higher than 11.5, enter the following parameters depending upon 32-bit or 64-bit OpenEdge that you have installed:

HKEY_CURRENT_USER (HKCU) registry

The HKEY_CURRENT_USER registry key is where user-specific settings are saved. The location of the HKEY_CURRENT_USER registry key for 32-bit OpenEdge is SOFTWARE\PSC\PROGRESS\<version> and for 64-bit is SOFTWARE\PSC\PROGRESS\x64\<version>.

If you have your own installers that write the OpenEdge keys, you must update the installers accordingly. If you write your own registry keys, you can also configure your keys so that if the application can be installed for both 32-bit and 64-bit OpenEdge on the same machine, it will differentiate between the 32-bit and 64-bit registry data. For example, if an application stores user data in HKCU\Software\MyVendor\MyApp\1.1.3, and if the application is run by both 32-bit and 64-bit OpenEdge on the same machine, the application must differentiate between 32-bit and 64-bit registry data.

If you want to check the OpenEdge platform on which your application is running to determine which registry key to write, you can use the PROCESS-ARCHITECTURE function.

32-bit OpenEdge installs only the 32-bit ODBC driver, and 64-bit OpenEdge installs only the 64-bit ODBC driver. In case you require both the drivers, install the SQL Client Access product for the platform-specific ODBC driver.

OE Ultra Controls for .NET (Infragistics NetAdvantage)

When you install OE Ultra Controls for .NET (while installing OpenEdge), the assemblies are registered in the Global Assembly Cache (GAC). If you install both 32-bit and 64-bit OpenEdge on the same machine, only one instance of the assemblies is registered in the GAC. If you install a service pack for an existing OpenEdge installation for a particular platform, the instance of the assemblies is updated to a new (service pack) version of the updated platform as well as the other platform.

WebSpeed Messengers are copied into the Web Server's scripts directory when you install OpenEdge. If you install both 32-bit and 64-bit OpenEdge that contain WebSpeed Messengers, each platform copies the messengers into the same script directory. This means a messenger from one platform could be overwritten by the other.

To avoid this, do one of the following:

After the first platform-specific OpenEdge installation, rename the cgiip.exe messenger files in the Web Server's scripts directory. This allows both 32-bit and 64-bit messengers to run at the same time by providing the correct messenger name in the URL.

When you switch from one messenger to another, copy the messenger files from your required platform's {DLC}\bin directory into the web server scripts directory. This allows either the 32-bit or the 64-bit messenger to run at one time.