Maintenance window and quieting Colleague

Colleague patches are applied between 6 and 8 AM every Friday.  Normal priority patches are first applied in the test environment, and then two week later in production.  The development environment can be patched at any time, but usually is patched the night before the maintenance window, as there are only two users who utilize it.

Before patches can be applied to Colleague, the system needs to be quiet.  This means that all users other than the datatel user need to be disconnected from the system. This requires several steps:

1. Stopping the Self-Service websites from the load balancer (https://mc-lb-1.durhamtech.edu/balancer-manager/)

2. Stopping Colleague and Unidata

   systemctl stop colleague-dev
   systemctl stop colleague-test
   systemctl stop colleague-prod
   systemctl stop colleague-base
   systemctl stop unidata

3. Perform RHEL updates and restart server if necessary

   dnf update

4. Restart UniData and Colleague in quiet mode (without WebAPI and gxml listeners)

   systemctl start unidata
   systemctl start colleague-base
   systemctl start colleague-dev
   systemctl start colleague-test-quiet
   systemctl start colleague-prod-quiet

5. Disabling connections in the UI from UIEC (set Y and 0)

A quiet system can be confirmed from the command line by checking for active sessions.  Only the datatel user should have any sessions open.