Upgrade to TeamForge 17.11 on same hardware: RHEL/CentOS 6.9/7.4

The following instructions are valid for upgrading to TeamForge 17.11 on the same hardware on both RHEL/CentOS 6.9/7.4 platforms. Specific steps, if applicable only for a particular RHEL/CentOS platform, are called out explicitly.

Before you begin:

Plan your upgrade

TeamForge 17.11 supports both RHEL/CentOS 6.9 and 7.4. See TeamForge installation requirements
For the ETL service to run as expected in a distributed TeamForge installation, all servers must have the same time zone.
While you can run both EventQ and TeamForge on the same server, CollabNet recommends such an approach only for testing purposes. It's always recommended to run EventQ on a separate server for optimal scalability. See EventQ installation requirements.
Installing or upgrading TeamForge needs root privileges. You must log on as root or use a root shell to install or upgrade TeamForge.
In a distributed setup, stop TeamForge services on all the servers while upgrading to TeamForge 17.11.
Reset the PASSWORD_CONTROL_EFFECTIVE_DATE token while upgrading to TeamForge 17.8. If not reset, the Password Control Kit (PCK) disables, deletes or expires user accounts immediately.