Upgrading or patching a Clarity instance can result in errors, therefore it is important in taking the necessary steps to back up the current application folders and database files related to Clarity.
If a refresh from another environment to another is needed, please use the contents within this article as a guideline.
There are 3 phases in the process: Preparation, Execution, Rollback (if needed).
1. Have copies of the following:
NOTE: Please consult the DBA team on this procedure as this involves creating and obtaining a .dmp or .bak file.
2.Copy the files from the source to the destination environment
3. Restore the the following in the destination environment
NOTE: Please consult the DBA team on this procedure as involves importing or restoring a .dmp or .bak file.
4. Verify the following paths are valid on the destination environment:
After verifying the refresh from the source to destination environment is complete, please do the following:
1. Modify the PPM_HOME\config\properties.xml file to have the valid paths:
2. Bring up the CSA by performing the following:
Confirm the database is 'Available'. If it is not available, please open a case to troubleshoot.
To ensure the information is saved in the database, run the command: admin general upload-config
NOTE: It may also be required that the Jaspersoft Service and DWH database be available. If this is required, please open a case to discuss the next steps.
3. Start the upgrade installation.
NOTE: Check if there are any WARNINGS or ERRORS that can cause an upgrade failure by reviewing the TEMP_INSTALL\checkinstall\check-logs\precheck-results.html
If there are any, please correct the error before rerunning the install again.
If any errors are encountered, open a Clarity issue for assistance.
Rollback (if needed)
In certain situations, a rollback is needed to back out of a patch or upgrade.
A rollback consists of:
If there are any questions or issues encountered, please open a case referencing this article and specify the step with the issue.