To maintain more than one Progress OpenEdge version on a Windows system, install the planned version as described in the; Installation and Configuration Documentation, Performing an OpenEdge Installation in Windows, with the following additional considerations:
1. When prompted for the various Destination Directories during installation, ensure that a distinct directory is used for each installed Progress OpenEdge version.
For example,
- When prompted for the Installation Destination Directory, enter the pathname of a separate directory in which to install each version. Ensure the directory specified is not the same as that used for other installed versions. It is imperative not to mix version executables.
- When prompted for a Working Directory, the directory specified must not be a subdirectory of the Installation Directory. While not mandatory, ideally not the same working directory used for other installed versions. Use a separate default working directory for each installed Progress OpenEdge version.
2. If AdminServers run concurrently on the same machine, then they will need to be configured to run on different ports. For further information refer to Article
How To Configure Multiple Versions of AdminServer To Be Run Concurrently since OpenEdge 10.1B 3. If the ubroker.properties is used for both environments, or if any of the default ubrokers (NS1, asbroker1, wbtman1 etc)are used, these will need to be configured with the
unique listening ports with unique UUID's. Article
How to create a new UUID for a UBroker in the ubroker.properties 4. Starting from OpenEdge 10.1C04, 10.2x, 11.x, a web-based tool called either
OpenEdge Explorer (OEE) or
OpenEdge Management (OEM) is used to configure the managed Server environment (Unified brokers and Databases). This runs on a Jetty web server, which is started when the AdminServer is started. With concurrent AdminServers, the Jetty web server will also need to run on different ports (default 9090). For further information refer to Article
How to change the default http listener port used by OpenEdge Management / Explorer ? 5. Progress always checks for
environment variables when starting up a session. The required information is read from the Windows Registry or from the progress .ini file (-basekey -ininame ) since Progress 8.2x. This applies for both client and server versions.
- Ensure that there are no OS Environment Variables point to a specific Progress OpenEdge version, for example the DLC, PROMSGS or PATH environment variables.
- Ensure that the environment does not mix executable versions or environment versions. The PROENV.bat file is tailored during installation to provide a shell that sets the correct environment variables for the installed version.
6.
Prior to OpenEdge 11.5.0
- While multiple Progress OpenEdge versions can run simultaneously on the same Windows machine, only one of the same Major.Minor version can be installed on the same Windows server, irrespective of the OpenEdge bit-version.
- This is due to the fact that the InstallShield script used by the setup program records Progress' configuration information into the Windows registry using the version number as a key. The Windows registry prohibits duplicate registry entries to be created. A duplicate installation of the same version of the product cannot be supported.
Starting from OpenEdge 11.5.0
- A Install new feature was added that allows 32-bit and 64-bit installations of the same Major.Minor version to co-exist on Windows.
- It is still not possible to have multiple installations of the same Major.Minor and bitness on a single Windows machine.
- For example, 11.5.0 32-bit and 11.5.0 64-bit can coexist in separate installations on the same windows server but two installations of 11.5.0 32-bit cannot co-exist on the same Windows server. A further example: a 32-bit oe12.2.14 and a 64-bit oe12.2.14 can be installed on the same Windows machine, since they are of different bitness; whereas having two 64-bit oe12.2 installations (e.g. 12.2.14 in one installation directory, 12.2.16 in another) simultaneously on the same Windows machine is not possible.
- For further details, see Article Can the same version of 32-bit and 64-bit products be installed on the same Windows machine?
