CA PPM System Health Report, Customization Discovery, Statistics, and Log Analysis

The health report shows system status for the application, database, and data warehouse. The health report also detects any non-compliant governor settings (maximum data limits). A related discovery analysis report detects system customizations. 
The health report shows system status for the application, database, and data warehouse. The health report also detects any non-compliant governor settings (maximum data limits). A related discovery analysis report detects system customizations. 
The Log Analysis page includes system statistics, daily page or XOG views, and log data.
Required Access Rights
  • To run the Health Report, verify that you have the
    Administration - Application Setup
    global access right.
  • To view the Log Analysis portlets, verify that you have the
    Administration – Access
    right. Also verify that you are assigned to the Log Analysis Access group.
  • To run the tomcat access logs, verify that you have the
    Jobs - Access
    right. Also verify that you have the following instance level job definition access right:
    Job - Run
    Tomcat access log import/analyze
View or Download a
 System Health Report
System health including the
 application servers, database, and data warehouse is important. As an administrator, application support engineer, or help desk technician, you want to maintain operations and minimize downtime. Before contacting other support professionals or engaging with the online community, you want a quick assessment of 
 system health. 
  1. Log in to 
    CA PPM
     with administrative access rights.
  2. Click the
    menu. Under
    Security and Diagnostics
    , select
    Health Report
  3. Select one of the following tabs:
    • Summary
      : This tab lists the health status and completion percentage for the application, database, and data warehouse. The % Completed value calculates the total number of settings that require a value during a new install or upgrade. The health report summary shows you what portion those required settings have a value. For example,
      88% Complete
      indicates that you are still missing valid values for the remaining 12 percent of all settings. When the report shows Setup Complete and a green status icon, the health for that category is good. When setup is not complete, a red icon appears. Click Details to view one of the three other tabs.
    • Application
      : This tab shows application server details. Settings include file locations, URLs, Java version, JVM, LDAP, SSO, SSL, and ports. You also see instance-specific configurations for CSA, background (bg), and beacon services. 
      • To verify settings for the 
        New User Experience
        , expand Application Instance (app), New User Experience. The
        attribute appears with a red icon when a newer version is available but is not deployed. The 
        New User Experience
         features are delivered and updated through a separate Java WAR file. WAR files should have a META-INF folder.
      • To verify settings for governor limits, expand Governor Limits.
      • To switch the status of the on-the-fly RateMatrix property, click Enable or Disable. When enabled, the application applies the PRJ_RT_RATES_EXTRACTION rate matrix options. This setting is disabled by default.
    • Database
      : This tab provides information about database connectivity, table spaces, database options, and server parameters. 
    • Data Warehouse
      : This tab provides information about data warehouse connectivity, table spaces, data warehouse options, and server parameters. Settings include JDBC URL, database timezone mismatch, database size, and ETL job timeout for the Load Data Warehouse job. This tab also includes setup information for time slices and other application settings for the data warehouse. 
      : Click the
      Fix It
      link to navigate to the application page where you can fix the non-compliant setting. For example, a red icon and
      Fix It
      link appear to help you set up entities or time slices.
  4. To view the recommended values for each setting on the Database and Data Warehouse tabs:
    1. The Recommended field provides the required values to achieve compliance and improve system health. If no exact value is recommended, the field remains empty. 
    2. Hover your mouse over the Status icon to view a recommendation to fix the listed item.
    3. As an Oracle database administrator, you might have permissions to V_$PARAMETER. If you do, expand Database Parameters to view the health of your database and data warehouse parameters. If you do not have permissions, hover over the status icon to show the command to grant access.
  5. To export the complete health report to Excel, click the Download Health Report button on the Summary tab. Open the file to view the HealthReport.xls file in Excel.
Command Line Health Report
To run the health report from a command line, enter the following command:
admin healthreport
Health Report Exclusions
In SaaS and FedRAMP environments, the health report database and data warehouse tabs do not list the following items:
  • Database Parameters
  • SQLNET parameters
Governor Settings (Maximum Data Limits)
Governor settings optimize performance by enforcing maximum limits on specific data. For example, the maximum size allowed for an uploaded document is 20 megabytes and the maximum number of rows you can export to Excel is 25,000. These limits help prevent a minority of users from degrading the performance of all other users.
The following table lists the recommended and enforced governor settings for this release:
Governor Setting
Default Value
Maximum file size for a document. (Only applies during initial upload. Any pre-existing documents that exceed the setting are not affected.)
Maximum number of rows that you can export to Excel.
Maximum number of rows that can be fetched in a list view or grid portlet. (Only applies if you configure aggregation on the list view or grid portlet.)
Maximum number of query rows that you can retrieve using a GEL script. (Only applies to select queries that run in GEL scripts.)
Maximum number of tasks in a timesheet.
Maximum number of nodes that you can read or write through XOG.
Maximum number of attributes in a portfolio.
Maximum number of roles in a portfolio.
Maximum time for an export to Excel before ending the export.
Maximum number of to-do items for a task.
to-do items
Download a Customization Discovery Analysis Report
This report was designed for CA Technologies Global Delivery teams, CA Support, and advanced administrators when preparing to migrate an on-premise environment to a SaaS environment. Some customizations allowed in an on-premise environment might not be permitted in a SaaS environment. Non-compliant objects and other factors determine an estimated level of complexity on the report cover page.
  1. Log in to 
    CA PPM
     with administrative access rights.
  2. Click the 
     menu. Under 
    Security and Diagnostics
    , select 
    Health Report
  3. Below the Summary tab, click the 
    Download Discovery Analysis Report
     button. The output contains about 20 tabs of data including non-compliant objects, data sources, and grid portlets. Discuss these customizations before upgrading or changing environments.
  4. (Optional) For large deployments, the Discovery Analysis report is also available as a job for your convenience. To prepare this report, select the Active check box for the PPM Customization Discovery Analysis job. The job results in an Excel spreadsheet which can also be emailed to the recipient as specified in the job parameters at the time of execution.
More Information
  • See
    PPM Customization Discovery Analysis
    in Jobs Reference.
View System Statistics and Log Data
Use the Log Analysis portlets to examine system performance. These portlets automate the process of parsing the application server log files and storing them in the database for visual analysis. Use these portlets to identify performance bottlenecks, frequently accessed features, response times, peak hours, and more.
  1. Log in to 
    CA PPM
     with administrative access rights.
  2. Refer to the
    Required Access Rights
    section at the start of this document. To get the data in these portlets, you are running a job to export the data from the server and import it into the application database.
  3. Click the 
     menu. Under 
    Security and Diagnostics
    , select 
    Log Analysis
  4. Select one of the following tabs:
    1. System Stats by Hour/Day
      : Use this tab to view average server response times, total sessions, and a list of the slowest actions performed for a specific day.
    2. System Stats by Month
      : Use this tab to view monthly page views and XOG requests for all servers or grouped by server. You can also view monthly session counts. 
    3. Daily Page/XOG Views
      : Use this tab to analyze the top 20 slowest pages. For example, you could troubleshoot the slowest pages and then optimize them for improved performance. This tab includes page views by service or server, daily page views, average response times by day, XOG requests by service or server, their average response times, and the total number of XOG calls by day.
  5. Enter your filter criteria:
    1. Select a
    2. Select an
      such as
    3. Select a
      such as
      or a specific application server.
    4. Click
  6. To export the data, click the
    Log Data Export
    tab. Specify the
    and the date range for the exported data. Each row of exported data shows the date, total page views by all users, the average page response time in seconds, the total number of XML Open Gateway (XOG) requests, the average XOG response time, and the unique session count for that day.
  7. To configure any of the portlets on these tabs, click
    if available. To export the data to Excel or PowerPoint, click Export to Excel or Export to PowerPoint. Not all portlets support these options.
In the following Average Response Time by Server example, slower response times were observed at 9:00 am for a specific day. Further analysis revealed a group of users running similar queries, jobs, and processes. Response times were improved when a time-consuming process was rescheduled.
Log Analysis portlet example.
The following example shows the data that you can find in the Slow Actions by Day portlet.
Time (secs)
Session Cookie
20180223 14:20:10
20180223 14:21:34
20180223 15:44:17
20180223 15:45:08
The associated username for a session ID helps you trace user activity in the system. For example, after user_01 deleted a custom object in Studio, user_02 began to notice delays and slower performance on another page indicated in the URL column.
: When a user logs in to the application, a trigger records their username and associated session ID cookie value.