End Here: Common Steps After All New Installs and Upgrades

ccppmop1593
Perform the following steps after a new installation or upgrade to
Classic PPM
.
4
4
Activity
Install Add-ins and Connectors
The PMO Accelerator is required. Your organization can extend the product with optional add-ins and connectors.
  • If you are upgrading from Release 14.3 or higher, the following add-ins are upgraded automatically:
    • PMO Accelerator
    • Accelerator for the PMBOK
    • CA Agile Planning (deprecated)
  • If you are upgrading from Release 14.2 or earlier, you must manually upgrade all installed add-ins.
  • We recommend installing only the PMO add-in and completing the upgrade; then, once the system is up, you can add other add-ins and connectors.
The Release Notes provide the supported add-in versions that are compatible with new installations or upgrades to each release.
The following subtle change might be perceived as unexpected by users upgrading from 14.3 or earlier releases: starting with Release 14.4, the default
Status Report Status
lookup values changed from
Minor Variance
to
Needs Help
and from
Significant Variance
to
At Risk
. The
On Track
value remained the same.
Verify Upgraded Users Can Access the Necessary Reports
The following small change applies only to customers upgrading from older releases such as Release 14.2 or 14.3 to Release 15.3 or any higher release. In 14.2 and 14.3, access right groups included instance-level rights on legacy CABI (Business Objects) reports. In Release 15.3 or higher, reports are available as part of the PMO add-in with PMO access groups. The old
Report Administrator
and
Report Users
access groups have been removed.
No action is required; however, verify user access to the necessary reports.
Delete Process Instance Job
After a new installation or upgrade, the application defines a recurrent quarterly schedule for the Delete Process Instance job. This job cleans up obsolete BPM_ERRORS table entries as far back as 90 days (one quarter). This default behavior helps control the size of the BPM_ERRORS table.
No action is required; however, you have options. The upgrade process truncates the records in the BPM_ERRORS table and moves them into BPM_ERRORS_BKP. At this point, the upgrade has successfully reduced the size of the original table. No further action is required.
However, as an option, you can retrieve the data if you need it for auditing or troubleshooting purposes.
  • On-Premise Administrators
    : To restore the last 90 days of data from the backup table to the BPM_ERRORS table, run the following query:
INSERT INTO BPM_ERRORS SELECT * FROM BPM_ERRORS_BKP WHERE LAST_UPDATED_DATE >= (SELECT (MAX(LAST_UPDATED_DATE)-91) CUTOFF_DATE FROM BPM_ERRORS_BKP) AND NOT EXISTS (SELECT 1 FROM BPM_ERRORS WHERE BPM_ERRORS_BKP.ID = BPM_ERRORS.ID);
  • SaaS Administrators
    : Contact CA Support to request restoration of the data.
Optimize Oracle 12c Performance
As an administrator, you can take steps to optimize performance for environments using Oracle 12c R2.
If you have local installations of Oracle 12c R2, you might detect a regression issue with Oracle 12c when ORDERED hint is used in structured queries. We recommend applying the following fix locally.
  1. From a command prompt, enter this series of commands in Oracle:
    sqlplus / as sysdba ALTER SYSTEM SET "_fix_control" = '17800514:0'; Exit;
  2. For systems using Oracle 12c R2 (12.2.0.1), set the optimizer to 12.1.0.2. Run the following command:
    ALTER SYSTEM SET OPTIMIZER_FEATURES_ENABLE= '12.1.0.2' SCOPE=BOTH;
  3. Verify your parameters appear similar to the following example: Download Example File
Optimize Oracle 19c Performance
As an administrator, you can take steps to optimize performance for environments using Oracle 19c R2.
If you have local installations of Oracle 19c R2, you might detect a regression issue with Oracle 19c when ORDERED hint is used in structured queries. We recommend applying the following fix locally.
  1. For systems using Oracle 19c, run the following command:
    ALTER SYSTEM SET OPTIMIZER_FEATURES_ENABLE= '19.1.0.2' SCOPE=BOTH;
  2. Verify your parameters appear similar to the following example: Download Example File.
Note:
Adjust the memory management parameters based on your environment.
Optimize PostgreSQL Performance
You can use the
Clarity
15.9.3
PostgreSQL.conf
and
Clarity
15.9.3
pg_hba.conf
files to review the sample PostgreSQL database configuration. The pg_hba.conf file enables password authentication.
Some key points to note are:
  • Max_connections (Depends on Memory)
  • Shared_Buffers (Depends on Memory)
  • Max_worker_processes (Depends on CPU/Memory)
  • Max_parallel_workers_per_gather (Depends on CPU/Memory)
  • effective_cache_size (Depends on Memory)
Run the Oracle Table Analyze Job
On-premise customers should run the Oracle Table Analyze job after the upgrade is done to gather schema statistics. The expected time for this job to complete depends on the size of the database. We recommend that you run this job right after the upgrade and at off-peak hours thereafter.
If you use a custom statistics job, refer to the updated Oracle Table Analyze Job procedure in the
Classic PPM
schema in Release 15.x (CMN_JOB_ANALYZE_SP) and make necessary corrections in the custom statistics job.
Enable
Clarity
Introduced in Release 15.1, the
Clarity
feature-set has grown exponentially. When upgrading from the previous release to the current GA release, you experience little, if any, disruption, much like applying a patch. However, if you are upgrading from 15.2, 15.1, or a previous 13.x or 14.x release, see the following details:
  • After an upgrade from a 15.x release that had
    Clarity
    enabled to the current release where you already installed the PMO Accelerator,
    Clarity
    remains enabled. Configure any new features (for example, new access rights or new settings) as described in the release notes and change impact documentation.
  • After an upgrade from Release 15.1, 15.2, or 15.3 that had
    Clarity
    enabled, to any newer release where you have not yet installed the PMO Accelerator,
    Clarity
    is disabled. A message on the
    Classic PPM
    system options page reminds you to install the PMO Accelerator before activating
    Clarity
    .
  • After an upgrade from any release where you did not have or did not enable
    Clarity
    , activating it resets all fields in the Default Time Entry Options to their default values. If you previously configured any of these fields to no longer use the default values, revisit this configuration page after enabling
    Clarity
    and new timesheets.
Jaspersoft Sender Email Address
The sender email address is the address that appears when JasperSoft sends an email notification for a scheduled report. JasperSoft lets you set the sender email address at the JasperSoft Reporting Server (JRS) level, but not at the tenant (organization) level.
  • SaaS Environments
    : The following address is the default sender email address value for the JasperSoft reporting server for
    Clarity
    SaaS implementations:
  • On-Premise Environments
    : The following address is the default sender email address value for the JasperSoft reporting server for on-premise implementations:
    [email protected]_domain.com
    (On-Premise only)
    For information about changing this default value during installation, see
    Installing
    .
    (On-Premise only)
    To change the default value after installation, perform the following steps:
    1. Locate and open the js.quartz.properties file in a text editor.
    2. Edit the
      report.scheduler.mail.sender.from
      property to include your sender email address and save the file.
    3. Restart the JRS.
Enable or Disable Features
  • In
    Classic PPM
    , configure portlets and portlet pages as appropriate to expose or hide the features your organization would like to use.
  • In
    Clarity
    , configure blueprints and access rights to provide users with the appropriate sections, fields, visuals, modules, and permissions to access application pages and functionality.
Review and Update Access Rights
Update the access right assignments for users, groups, objects, and OBS instances with new or updated access rights that are introduced in each release. See
Clarity
Access Rights Reference
.
  • New Installations
    : By default, all new users in a typical setup of
    Clarity
    with timesheets are granted the following minimal set of access rights:
    Resource - Enter Time
    Resource - Self (Auto)
    User Favorites Menu - Edit
    They are also members of a group named
    Basic group for user access
    , which we recommend you populate with at least the following three (3) default global access rights to get all users started:
Account Settings - NavigateOrganizer - AccessProjects - Navigate
  • Upgrades
    : The application preserves all the access right assignments from the previous release.
Clear Your Browser Cache
After an upgrade or after changing their access rights, users could encounter a blank page until they clear their browser cache, cookies, and history files. The steps vary by web browser. If you see different results in Google Chrome incognito mode, that generally indicates you can clear your browser cache to achieve the same results for the user in normal mode.
  • Be careful not to clear passwords or other sensitive data if you normally store this data in your browser
  • Also try logging out and then logging back in again to reset your permissions.
Update Client Applications
  • Advise XOG users to install the newest version of the XOG client.
  • If your users run the Schedule Connect clients, Microsoft Project (MSP) or Open Workbench (OWB), each user needs to verify their version of MSP or OWB with the specified minimum supported client software in the release notes. Do not automatically update MSP or OWB. Sometimes the newest version is not compatible.
  • If necessary, install or update the JRE available from Oracle.
Run Required Jobs
Run the required jobs as listed in Jobs Reference. Resume any scheduled jobs that you paused before your upgrade.
At minimum, repopulate the required datamart tables:
  • Datamart Extraction job
  • Datamart Rollup job
(On-Premise only)
Run the Oracle Table Analyze job after the upgrade is done to gather schema statistics. The expected time for this job to complete depends on the size of your database. We recommend that you run this job right after the upgrade and at off-peak hours thereafter. If you use a custom statistics job, refer to the updated Oracle Table Analyze Job procedure in the
Classic PPM
schema in Release 15.x (CMN_JOB_ANALYZE_SP) and make necessary corrections in the custom statistics job.
Data Warehouse Required
Installation of the
Clarity
data warehouse is required.
  • SaaS environments already include this integrated system component.
  • As an on-premise administrator, if you have not already done this step, deploy the data warehouse.
  • After the upgrade is completed, run the Load Data Warehouse job and use the "full load" option.
You can configure it for reporting, lookup queries, and trending, or even decide not to use it. However, it must be installed and working in all environments, on-premise and SaaS.
Generate an AWR Report for Troubleshooting
Use AWR reports to troubleshoot performance issues and find offending queries that may cause performance problems. This standard Oracle elapsed time report has evolved over the years and had several names.
In Oracle, the AWR report is the latest time-series report.
  1. Run the following SQL*Plus script in the $ORACLE_HOME/rdbms/admin directory:
  2. awrrpt.sql is a text-based report.
  3. awrrpti.sql is a HTML-based report for online publishing of time-series reports.
  4. The remaining procedures in the dbms_workload_repository package are awr_report_text and awr_report_html, which generate the AWR report for the specified snapshot range in text or HTML formats, respectively.
Example
: The following script segment shows how to retrieve the AWR text report for any snapshot range or duration:
SELECT output FROM TABLE(dbms_workload_repository.awr_report_text (37933856,1,2900,2911 ));
The awr_report_text output shows the data for the following four arguments that you specified in the stored procedure:
  • Database ID: 37933856
  • Instance number for RAC: 1
  • Starting snapshot number: 2900
  • Ending snapshot number: 2911
Access Optional Integrated GEL Scripts
This item typically applies after a SaaS upgrade; however, on-premise customers can also review this item if they have similar GEL integrations in place.
If you have developed integrations that leverage a shared directory that can be called in GEL scripts, the following required code illustrates the proper GEL syntax to use with the integration location:
GelParams: <gel:parameter var="ShareFolder" default="/fs0/clarity1/share"/>
The
ShareFolder
parameter is the same folder that is accessed through your SFTP account associated with your environment folder. You can create optional subdirectories in the GEL parameter.
When using GEL with the XML Open Gateway (XOG) using the
<soap:invoke>
tag, instead of hard-coding the endpoint to a specific host URL, you may specify
<soap:invoke endpoint="internal">
to allow GEL to automatically determine the correct SOAP URL for the local environment. This convention prevents situations where a database restored from production into a non-production environment has XOG URLs that still specify the production environment.
For any GEL scripts where the
NIKU_HOME
variable is hard-coded, use the following syntax to dynamically retrieve this information:
<core:invokeStatic className="java.lang.System" method="getenv" var="NIKU_HOME"> <core:arg value="NIKU_HOME"/> </core:invokeStatic> <gel:parse file="${NIKU_HOME}/config/properties.xml" var="properties"/>
Run a Health Report
All supported releases of
Clarity
include a new System Health Report.
  1. Resolve all problems using the application, online help available by clicking Help or visiting docops.ca.com, Support KB articles, and
    Clarity
    Online Community.
Conduct Your Own UAT and Regression Testing
Once an upgraded non-production environment has been provided by your SaaS or on-premise upgrade team, familiarize yourself with the new features, test any expected bug fixes, and complete your unit, regression, and user acceptance testing.
Your testing should cover the following:
• Testing scripts developed during your initial implementation
• Applicable bug fixes
• New functionality you plan to deploy
• Custom reports
• Data integrations
• Custom Processes with GEL scripting
• Custom Portlets with NSQL data providers
• Add-In packages and related configurations
• Global Delivery (GD) components
Complete your post-upgrade review and testing within 45 to 60 days, if not sooner. If your testing exceeds 90 days, due to new releases, service packs, and patches, we recommend that you validate a new upgrade against new production data.
If testing reveals any issues, questions, or concerns about the delivered environment, open a new ticket specific to each issue to ensure the appropriate attention and expertise are applied in a timely manner. Do not update the original upgrade ticket with post-upgrade issues.