Note: Service packs were replaced by updates with the introduction of LTS and non-LTS versions.
Current LTS and non-LTS versions - https://docs.progress.com/bundle/openedge-life-cycle/page/OpenEdge-Life-Cycle.html
LTS vs non-LTS version FAQ - https://community-archive.progress.com/documents/OpenEdge/FAQ_OpenEdge_12.2_Product_Life_Cycle_Policy_&_Long_Term_Support_Release.pdf
For example:
11.7.<update>
12.2.<update>
Updates are different than minor or major upgrades as it is an in-place process.
For example:
11.7.4 -> 11.7.14 is an in-place update.
11.4 -> 11.7 is a minor upgrade and requires a new install.
11 -> 12 is a major upgrade and requires a new install plus database migration.
The instructions below include the term "service pack" for legacy reasons but the same information applies to current "updates".
Progress Service Pack were introduced in Progress 9.1D and they are not installed the same way as Patches were in previous versions.
A Service Pack/Update uses an installation program (Installshield on Windows Systems and proinst on Unix systems) whereas patches were simply a zip (on Windows) or a tar (on UNIX) file to apply on the top of an existing installation, by overwriting the existing installed files.
With the introduction of Progress Service Pack/Updates, it is necessary to unzip (on Windows) or extract the tar (on Unix) the Service Pack/Update file into a temporary directory, then execute setup.exe (on Windows) or proinst (on UNIX) from the Service Pack/Update media.
Prior to the installation of the Progress Service Pack/Update
STOP all instances of Progress processes (this includes the WebSpeed messenger, OE adapters and servlets running on a third-party webserver and/or Tomcat) that are running for the version the Service Pack/Update is being applied against. If all processes are not shutdown, the Service Pack/Update will not continue.
Note: Newer versions may ask permission to try and stop the processes automatically.
Once the Service Pack/Update has been downloaded from the Progress Electronic Software Download Center (ESD) for the same major version, Operating System and bit-version as the current install:
To install a Progress OpenEdge Service Pack/Update on Windows:
0. With the same user credentials as were originally used to install the current version (Local Administrator)
1. Save the ESD download file into a temporary directory.
2. Create a new folder to use when unzipping the self-extracting Service Pack/Update. Do not use the current %DLC% or any %DLC% sub-directory.
3. Extract/Unzip the zip the Service Pack/Update into the new folder.
4. Run "setup.exe" from the folder where the files where unzipped (not setup.exe from the current install directory %DLC%).
5. Progress will detect the current Progress OpenEdge install directory for the same version and begin the installation of the Service Pack/Update.
To install a Progress OpenEdge Service Pack/Update on Unix:
0. With the same user credentials as were originally used to install the current version (root)
1. Save the file into a clean temporary directory which is not the current $DLC or a sub-directory of $DLC.
2. Extract the tar file into the new directory then chmod 777 * on the content of the directory.
3. On AIX platforms: Run "/usr/sbin/slibclean" to remove any currently unused modules in kernel and library memory.
4. Execute proinst from the folder where the Service Pack/Update files where extracted.
5. The install routine will ask for the current Progress install directory and begin the installation of the Service Pack/Update. If the $DLC environment variable is set, the install directory will be pre-populated waiting confirmation.
6. Post-install ensure permissions are as the Unix site has designed these, for example:
$DLC/bin directory:
chown root _*
chmod 4775 _*
chmod 755 _sql*
chmod 755 _waitfor
Some of the files installed by the Service Pack/Update may have ownership(owner group) that looks like this "1353 110".
These are intended to be non-existing users in the OS.
After the install, the installation files with this ownership set will have to be changed to the same ownership as the files already on the same directory ( e.g. root root or root progress).
If the Service Pack/Update has been unzipped or the tar extracted over the top of the existing installation, the Progress OpenEdge base (FCS) version will have to be reinstalled before applying the Service Pack/Update as the core installation is corrupted.
The default behavior of the Progress Service Pack/Update installation is to make a backup copy of the current install directory to allow backing out of the newly applied Service Pack/Update, if necessary. Failure to backup the current install directory means that recovery of the previous installation is only possible by a complete reinstall of the original product and previous Service Pack/Update as may apply.
Each Service Pack/Update contains a READMESP text file providing install instructions.
Scripts that have been copied by the Major version's installation into usr/bin are not touched by the Service Pack/Update installer. There is no need to remove and re-add these scripts unless the READMESP.txt have specific instructions to do so.
