Distribute All has errors after Clarity upgrade

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

You have upgraded one of the three servers successfully. However seeing errors when trying to distribute to the other servers.

Some error you might be receiving:

• /app/clarity/install/.setup/scripts/deploy.xml:141: /app/clarity/install/.setup/scripts/deploy.xml:142: The following error occurred while executing this line:
• /app/clarity/install/.setup/scripts/deploy.xml:179: The following error occurred while executing this line:
• /app/clarity/install/.setup/scripts/j2ee/tomcat/deploy.xml:546: Parent /Server/Service/Engine/Host/Context[@path='/niku'] not found in document
  
  

Or the service that was distributed to, may not be working / starting anymore /hanging upon startup

Environment

Release : All Supported Clarity releases

Resolution

Troubleshooting Distribute 

Please ensure you are following the correct steps to distribute to the other server.

Check the following:

• Are the other two servers available in CSA, and visible?
• Are the services running?
• Are you using multicast or JDBC ping?

Using Copy of the Filesystem as an alternate way to distribute

Note that using Distribute All is not required, and if you have upgraded on server 1, 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. 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