CA PPM: Best Practice on How to Execute an Upgrade or Patch Install

Document ID : KB000036520
Last Modified Date : 24/10/2018
Show Technical Document Details
Introduction:

Introduction:

Upgrading or patching CA PPM 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 CA PPM.

If a refresh from another environment to another is needed, please use the following as a guideline.
There are 3 phases in the process: Preparation, Execution, Rollback (if needed)
 

Instructions:

Preparation

1. Have copies of the following:

a. Make a copy of each source PPM_HOME/config/properties.xml file
b. Make a copy of the source CA PPM application folder.
c.  Make a valid backup of the source CA PPM database (MS SQL or Oracle).

NOTE: Please consult the DBA team on this procedure as this involves creating and obtaining a .dmp or .bak file.

Reference https://docops.ca.com/ca-ppm/15-4-1/en/installing-and-upgrading/install-ca-ppm

2.Copy the files from the source to the destination environment

a. Copy the CA PPM application folder to the destination environment.
b. Copy the CA PPM database to the destination environment.

3. Restore the the following in the destination environment
a. Restore the CA PPM application backup to the destination environment.
b. Restore the CA PPM database backup to 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:
a. Set TOMCAT_HOME
b. Set JAVA_HOME
c. Set NIKU_HOME

Execution

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:

a.current JAVA_HOME
b.current TOMCAT_HOME
c.current PPM_HOME

2. Bring up the CSA by performing the following:

a. Run from command line: service add start beacon nsa

b. Open a browser and log on to the CSA. Go to the Database page to enter the database connection information and click the Save button.

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.

c. If Database is 'Available', make a copy of the PPM_HOME\config\properties.xml

3. Start the upgrade installation.
a. Create an installation folder to execute the installation.
b. Obtain the installation media and required thirdparty.libs jar file and place them in the temporary installation folder.
c. From the temporary installation folder, extract the contents of the install.jar file with command: jar -xvf install.jar
d. Run the installation and follow provide the information from the prompted information. 

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. 

e. Allow the upgrade/installation to complete.

NOTE: After it completes, check the following files:
INSTALL_HOME\checkinstall\check-logs\postcheck-results.html
INSTALL_HOME\logs\checkinstall\checkinstall-results_date.zip
INSTALL_HOME\logs\upgrade-ca.log

If any errors are encountered, open a CA PPM 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:
1. Restoring the backup CA PPM application folder
2. Restoring the backup CA PPM database.

Additional Information:
If there are any question or issues encountered, please open a case referencing this article and specify the step with the issue.