Distribute or Copy files after Clarity upgrade / patch
search cancel

Distribute or Copy files after Clarity upgrade / patch

book

Article ID: 389228

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Best practices on applying the changes to other servers in cluster after performing a Clarity upgrade or installing a patch 

Environment

All Supported Clarity Releases

Resolution

Distribute All

  • Stop app and bg services on the local server that was upgraded
  • Open CSA - Distribute All.
  • Select the remote servers and click Distribute. Wait until the distribution is complete before continuing.
  • Once complete, you can bring the other services up

Note: The Distribution may sometimes have issues and we do recommend the Copy of Filesystem method below

Using Copy of the Filesystem 

You can simply copy all Clarity files in a zip file except the /config directory and /logs and replace on server 2 and server 3 (except /config and /logs) and then bring the services up.

This is a second, supported way to distribute the files. To do this, folllow the steps:

  • server 1 - Upgraded server
  • server 2 - Not Yet Upgraded server
    1. Stop and remove services on server 1
    2. Zip the entire Clarity upgraded files on server 1
      Note: On Linux, ensure that the hidden .setup folder is also zipped
    3. On server 2, stop and remove the Clarity services
    4. On server 2, backup $clarity/config and $clarity/logs, then delete the clarity directory
    5. With niku user: Move the zip file from server 1 to server 2, and unzip in server 2, ensure it's the same location / path as expected 
    6. Ensure full permissions are granted to niku user over the directory. Niku must be the owner.
    7. Ensure the new Tomcat and java are installed on server 2 and full permissions are provided to niku user
    8. Now retrieve the previous config from server 2 you backed up earlier
      • Replace the config correctly to ensure the config files are the ones from the previous install
      • Also replace the logs directory so you have all the old logs
    9. Add, deploy and start services on server 2
    10. Add deploy and start services on server 1