GWME-7.2.1-00 Rollup Patch Installer

You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History
Overview

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. It only includes code, not data, 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.

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.

Prerequisites
  • 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.
Installation Steps
There are currently no attachments on this page.
  1. You MUST have the postgres user password available before running this patch!
  2. Transfer the Rollup Patch installer to your GroundWork server, and place it in an empty directory.
  3. Log in to the command line on the GroundWork server and become root in that directory
  4. Type:
    chmod +x groundwork-7.2.2-gw4013-patch-install.run
    ./groundwork-7.2.2-gw4013-patch-install.run
    

    The installer will ask for the postgres user password. It will then stop, patch and restart the groundwork services.

Important Directives

Because the patch does NOT affect configuration files in some cases you MUST make addition or edit to properties files in order to benefit from the patch.

  1. GWMON-13406 Window for NocBoard Query speed up
    /usr/local/groundwork/config/foundation.properties
    These parameters denote the acceptable size of the search window in time, and affect how much is cached
    If you select a bigger period in NocBoard than you have set here performance will suffer.
    ############################################################################
    # LogMessage Window Service Configuration
    ############################################################################
    logmessage.window.enabled=true
    logmessage.window.size.hours=24
    logmessage.window.update.interval.seconds=5
    
  2. GWMON-13447 Map LDAP groups to GW Roles (fixes for LDAP mapping issues)
    /usr/local/groundwork/config/foundation.properties
    Adding the ldap mapping enable parameter and the "|" or function on the roles container search term
    # Whether LDAP Mapper should be enabled
    core.security.ldap.mapping_enabled = true
    ...
    core.security.ldap.config.windows2012.roles_ctx_dn = ou=GWRoles,dc=company,dc=com|cn=other,dc=company,dc=com
    

    /usr/local/groundwork/config/ldap-mapping-directives.properties
    Adding the mapping of LDAP only groups "aga", "another aga", "ago", "agu" to GW portal only groups
    Notice that a space in an LDAP group name requires the replacement with the string "\u0020"

    #Portal admin group mapping
    GWRoot=gw-portal-administrator
    
    #groundwork admin group mapping
    GWAdmin=gw-monitoring-administrator
    
    #Portal operator group mapping
    GWOperator=gw-monitoring-operator
    
    #Portal user group mapping
    GWUser=gw-portal-user
    
    agr=GWRoot
    another\u0020aga=GWAdmin
    ago=GWOperator
    agu=GWUser
    
Rollback Steps

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.

  1. Log in to the command line on the GroundWork server and become root.
  2. Change to the backup directory, e.g.:
    cd /usr/local/groundwork/backup-gw4013
    
  3. Execute the rollback script:
    ./restore-backup.sh
    

    You will once again need to provide the postgres user password.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.