ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How to Upgrade PMO Accelerator

book

Article ID: 212428

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS STARTER PACK-CLARITY PPM

Issue/Introduction

We would like to upgrade PMO accelerator, how can we do that? 

Environment

Release : Any

Component : CA PPM ADD-INS (CSP,PMO,DM,EVM)

Resolution

Pre-upgrade steps:


Check to make sure the PMO Accelerator is installed for Clarity PPM.

To do this, run the following query on the Clarity database:
select * from cmn_install_history order by installed_date desc

Look for the 'csk' entry, it should be the same version as your Clarity version if PMO was installed on the server.  If it's not, proceed with the upgrade (If the version is multiple releases behind, you have to check if you have the correct PMO upgrade path)

 

Upgrade steps for PMO

To upgrade the PMO accelerator, there is two parts:

  1. Bring the services down and run the command on the server:

    admin content csk
  • This applies PMO to the database and the Clarity Application server
  • If you have more than 1 server, then run it on 1 server only and then Distribute to the others.

 

  1. Once you complete the install from command line, go to Administration - Content Add-Ins - Accelerator: Program Management Office - Items
  • There you have to select the items you'd like to update and that are not installed or pending upgrade and click Install.
  • This will overwrite existing portlets, views and lookups in Clarity with the newest PMO version.

                     IMPORTANT: Before upgrading any items, make sure there is no impact to any customizations in the system (such as views) that would get overwritten when upgrading the items. We recommend as best practice to apply any non-Views items first. Installing the PMO Views will remove user views customizations, and must only be done if this is not considered to be an issue

Impact: Usually the concerns of overwriting are about the custom Views, so you may want to skip updating the Views or at least some of them. It is safe to leave the views non-updated. If you don't update the portlets or lookups, some of them may stop functioning so those are recommended to be applied.