|Last update: Nov 30th, 2018, with version 7.2.2-4108|
The Rollup Patch installer is a cumulative patch, and is a step closer to the "continuous deployment" method of updating. The patch installer is intended to be used independent of Technical bulletins, though some Technical Bulletins may depend upon the Rollup Patch already having been applied, and some of the code we supplied in Technical bulletins originally may be superseded in a given version of the Rollup Patch. Generally, we recommend applying the rollup patch first, then looking at the Technical bulletins and applying them as needed. The rollup only includes code, not data or configuration, and does no scripted updates, so for some things you will still need the Technical Bulletins, as they can apply scripted updates and make configuration changes.
The rollup patch installer does make database schema updates, so you will need to have a valid postgres user password for the database (see Prerequisites, below). It is not necessary to run the patch installer on a database-server-only installation of GroundWork.
Since it is a cumulative patch, you need only install the latest version - there is no need to install each version of it sequentially. The Rollup Patch Installer is also reversible - it makes a backup of everything it changes, and you can use a simple process to reverse the updates it makes.
If you install two or more sequential rollups and need to roll them back, simply apply the rollback scripts in the reverse order of the rollup patches.
- You will need a short downtime window, as the Rollup Patch Installer stops all GroundWork services for update.
- You will also need root user access to the GroundWork server.
- You will need to know the postgres user password for the database.
If you have several GroundWork servers in a parent-child configuration, you may run the rollup on any server in any order. Note that it will interrupt monitoring briefly when you apply or roll back.
|You MUST have the postgres user password available before running this patch!|
- Transfer the Rollup Patch installer to your GroundWork server, and place it in an empty directory.
- Log in to the command line on the GroundWork server and become root in that directory
The installer will ask for the postgres user password. It will then stop, patch and restart the groundwork services.
Hopefully you will not need to roll the changes back. If you have any issue after the patch, please let GroundWork Support know as soon as you can. We do extensively test each change, and we do integration and system tests on each Rollup, but we recognize you may need to get back to where you were.
Note that no configuration files will be altered or rolled back, that is up to you to control.
- Log in to the command line on the GroundWork server and become root.
- Change to the backup directory, e.g.:
- Execute the rollback script:
You will once again need to provide the postgres user password.
Because this rollup patch does affect configuration files, in some cases you must make additions or edits in order to benefit from the new features and fixes in the patch. The following is a list of such edits you may want to make, depending upon how you use GroundWork, and whether you make use of a particular feature.
- GWMON-13406 Window for NocBoard Query speed up
File to edit:
These parameters denote the acceptable size of the search window in time, and affect how much data is cached.
If you select a bigger period in NocBoard than you have set here, performance will suffer. Make sure the window size is right for your installation.
Changes to this file are effective after you restart GroundWork Services.
- GWMON-13447 Map LDAP groups to GW Roles (fixes for LDAP mapping issues)
File to edit:
Adding the ldap mapping enable parameter and the "|" or function on the roles container search term extends the places that GroundWork will look for users and role mappings. This can add significant redundancy to your authentication/authorization setup with LDAP or AD.
File to edit:
You can add the mapping of LDAP only groups to GW portal only groups, for example: "aga", "another aga", "ago", "agu", below.
Notice that a space in an LDAP group name requires the replacement of that space with the string "\u0020"
Changes to these files are effective after you restart GroundWork Services.
- GWMON-13501 LDAP Group to Role equivalent recursive tour de mort fix.
You may use a notation for ldap mapping that sets GROUPNAME=GROUPNAME (where the ldap group and the GW role are identically spelled).
The details of what issues and features are changed in this version of the rollup patch are detailed [here.]