CA PPM 15.3.0.5 and Jaspersoft Cumulative Patch README Files

Cumulative patches for cappm 15.3 and Jaspersoft are periodically available. Before applying a patch, see the README for important information.
ccppmop153
Cumulative patches for 
Clarity PPM
 15.3 and Jaspersoft are periodically available. Before applying a patch, see the README for important information.
 
 
2
 
 
 SaaS customers can contact CA Support to request patch installation. Any fixes for reports are automatically deployed in your SaaS environment. For on-premise environments, to install the patch and update report content, see the instructions in the README on this page.
 
Clarity PPM
 15.3 Cumulative Patch Summary
Because patches are cumulative, when you install a single patch, it includes all the fixes in all previous patches.
Patch GA Date
Patch Announcement
Aug 29, 2018
Jun 6, 2018
Mar 28, 2018
Jan 31, 2018
Dec 6, 2017
CA PPM 15.3.0.5 Cumulative Patch README File
 
 
4
 
3
 
 
Version #: 15.3.0
Patch #: 5
Platform Specifics:
Database Specifics:
**** NOTE *************************************************************
Patches are intended to be timely fixes and are not fully regression or integration tested, and are only tested against the issues listed below. CA feels confident that this patch will resolve the addressed problems, but customers should be aware that a patch could have adverse side effects to the function of their CA PPM application. Customers should not apply patches directly to production systems without first verifying in a test environment. If any issues arise in the installation or use of this patch, contact CA Support.
***********************************************************************
INCLUDED FILES:
---------------------------------------------
README.txt -> This file
install.sh -> Unix installer
install.bat -> Windows installer
install.xml -> Ant install script
PRE-REQUISITE - ADDITIONAL NOTES:
------------------------------------------------------
- Install only on systems running the version stated above.
ADDITIONAL NOTES:
This patch provides legacy datamart administrators with two new optional parameters for the Datamart Extraction job:
  • Extract Only OBS
  • Extract Only Calendars
To learn more about these optional parameters, see CA PPM Jobs Reference in the Reference section (visible when you log in to docops.ca.com).
---------------------------------
SPECIAL INSTRUCTIONS FOR DE38058
After the patch is applied, the fix for DE38058 does not appear until you upgrade your XOG client software.
See 
XOG Client Installation
 in the XML Open Gateway (XOG) Development Guide in the Reference section (visible when you log in to docops.ca.com).
-------------------------
How to Install the Patch:
------------------------
  1. Back up all files and the database on the target system.
  2. On the CSA server, copy the installer into a temp directory.
  3. Navigate to the temp directory and enter the following command to extract the contents:
      jar xvf <patch_jar_file>
     
  4. Stop all local nsa, app and bg services:
      service stop nsa app bg 
    Note: Allow databases and reports to continue running.
  5. From the temp directory, enter the following command to execute the installer script:
      install.bat
    or
      install.sh
     
  6. Follow the remaining on-screen instructions to complete the installer script.
  7. Start all services:
      service start all
     
  8. If you are running multiple servers in a cluster:
    1. Log in to the CSA and go to the All Services page to shut down any remote app and bg services.
    2. Go to the Distribute All page, select remote servers, and click Distribute.
    3. Return to the All Services page to restart services when the distribution is complete.
    IMPORTANT: If you currently use or want to use the new Jaspersoft Reports and Data Warehouse, choose Step 9 or Step 10. If you do not use these features, skip Steps 9 and 10.
  9. If you are applying this patch and you have already configured Jaspersoft Reports and the Data Warehouse:
    1. From <install_dir>/bin directory command prompt, enter the following command to generate keystore:
      admin jaspersoft keystore
    2. Copy the keystore files generated in <install_dir>/config directory to <Jaspersoft Tomcat Instance Directory>/webapps/<jaspersoftContext>/WEB-INF/config
    3. Enter the following command to upgrade the report content:
      admin content-jaspersoft csk -userName <superuser> -password <password> upgrade -retryCount 50
    4. Restart all PPM services.
    5. Run the Load Data Warehouse Access Rights job.
  10. If you are applying this patch and you want to use the new Jaspersoft Reports and Data Warehouse but have not yet configured them:
    1. From <install_dir>/bin directory command prompt, enter the following command to generate keystore:
      admin jaspersoft keystore
    2. Copy the keystore files generated in <install_dir>/config directory to <Jaspersoft Tomcat Instance Directory>/webapps/<jaspersoftContext>/WEB-INF/config
    3. Enter the following command to install the release content:
      admin content-jaspersoft csk -userName <superuser> -password <password> -retryCount 50
      This command imports 
      jaspersoft_csk.zip
       followed by the file that has patch content (file name for patch content contains 
      jaspersoft_csk_upgrade
      ).
    4. If you encounter any error during the import of the patch content, enter the following command to re-import the patch content:
      admin content-jaspersoft csk -userName <superuser> -password <password> upgrade -retryCount 50 force
    5. Configure the Data Warehouse section in CSA. See CSA: CA PPM System Administration at docops.ca.com/ppmop.
    6. Enter the following command from the <install_dir>/bin directory command prompt to apply the data warehouse patch content:
      admin db dwh-upgrade -Dupgrade.phase=maintenance
    7. Restart all PPM services.
    8. Run the Load Data Warehouse Access Rights job.
--------------------------
How to Uninstall the Patch:
--------------------------
  1. Stop all local nsa, app, and bg services:
      service stop nsa app bg
     
  2. Restore the installation files and database from the backups above.
  3. Start all services:
      service start all
     
  4. If running multiple servers in a cluster:
    1. Log in to CSA and go to the All Services page to shut down any remote app and bg services.
    2. Go to the Distribute All page, select remote servers and click Distribute.
    3. Return to the All Services page to restart services when the distribution is complete.
--------------------------------------------
Issues Fixed in 15.3.0.5
--------------------------------------------
DE37008, DE38650, DE41718: Load Data Warehouse Incremental fails with ORA-01452: Cannot CREATE UNIQUE INDEX; Duplicate keys found ORA-06512...
Steps to Reproduce:
1. Ensure all the prerequisites are met before running the Load Data warehouse job.
2. Run Load Data Warehouse - Full
3. Note it completes successfully
4. Now run Load Data Warehouse - Incremental
Expected Results:The Incremental job to complete successfully.
Actual Results: The jobs fails with error:
 
[CA Clarity][Oracle JDBC Driver][Oracle]ORA-20100: ENCOUNTERED EXCEPTION WHILE INSERTING INTO DWH_INV_TASK_PERIOD_FACTS_LOAD. SQLERRM : ORA-20100: ENCOUNTERED EXCEPTION WHILE INSERTING INTO DWH_INTERNAL_MD. SQLERRM : ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found 
ORA-06512: at "PPM_DWH152.DWH_INV_TASK_PERIOD_FACTS_LOAD"
 
DE38175: New UX Detailed Timesheets Do not Display all data for Submitted Timesheets
Steps to Reproduce:
1. Submit PPM Timesheet for a labor resource by adding 12 or more tasks.
2. Login to New Timesheet UX as the Resource Manager (RM) for the resource who submitted Timesheet in step one above and navigate to 'Review and Approve' page.
3. Click on the name of the resource to open a Timesheet pop up window. Here all the listing of Submitted Timesheets are displayed.
4. Now click on the 'Detailed Timesheet' button to review details all timesheet data entered.
Expected Results: The listing of all the submited Timesheet in step one to be displayed.
Actual Results: The listing on Detailed Timesheet page displays only the first eleven items of submited Timesheets.
DE40259: Portfolio Sync Job is Slow
Steps to Reproduce:
  1. Navigate to Portfolios in classic PPM.
  2. Create a new portfolio.
  3. On the Portfolios Properties page, click on the Actions drop-down button.
  4. Click Synchronize Portfolio Contents.
Expected Results: The Synchronize Portfolio Contents job should complete successfully within a matter of seconds.
Actual Results: The Synchronize Portfolio Contents job is completing after several minutes and is taking longer than expected.
DE34402: Securability Fix
DE34403: Securability Fix
DE34404: Securability Fix
DE39644: Securability Fix
DE41626: Securability Fix
DE36635: New User Experience Timesheet Is Misaligned on Large Screens
STEPS TO REPRODUCE:
Pre-requisite: Use a large screen
1. Open any browser and get to the new UX login page:
2. Ensure the browser tab is maximized
3. Log in and go to the new timesheet UX.
4. Open any timesheet and add some time entries, or edit an existing one that contains time entries
5. Timesheet details appear
STEPS TO REPRODUCE
1. Create a simple Task Object process a Start and Finish steps (Start Step => Finish Step)
2. Set the Start Option to be 'On Demand'.
3. Create an Action in the 'Start' step based on Action Type => 'Manual Action'
4. For the 'Actions' Select 'Approved' and 'Rejected' fields.
5. In the Subject field, select Task 'Name'
6. For 'Assignees', select the users you are currently logged in as from the 'Resource' tab.
7. Click on 'Save and Return' button to come out of the page then specify the 'Finish' to complete and Validate/Activate process
8. In the Task object, create a new 'Action' from the 'Actions' tab which is of Type => 'Process' and select the process
created in the Steps above.
9. From the 'Views' tab, click on 'Actions Menu' for the 'Task List' then click on 'General' link and the Action created in step 8
above to the 'Selected Actions' section. Click on 'Save And Return' button.
10. From CA PPM project list page, open a project => Task list page. Select a Task by clicking on a checkbox then from the
'Actions' dropdown menu click on the Action created in step 8. Process is launched and executed
11. Navigate to CA PPM Home => Organizer page to view the Action Item. Click on Action Item to open then the 'Objects' link.
Expected Results: Task to open successfully
Actual Results: Error message is generated as follows: 'en - Unable to process request - Server or Network error'
DE38373: Annual Plans show incorrect amount in the Financial Forecast Review by Investment Report
Steps to Reproduce:
1. Make sure your DW Entity has annual plan periods defined and active
2. Use a project that is associated to that Entity
3. Create an Annual Type cost plan
a. Make the Annual Amount = $1,000,000
b. Change TSV to month and observe the monthly amounts
c. Change the TSV back to Annual
4. Make sure the Time Slicing job runs
5. Run Load DW Job in Full mode
Expected Results: Planned Amount on Financial Forecast Review by Investment Report shows 1,000,000
Actual Results: Planned Amount on Financial Forecast Review by Investment Report shows 1,000,000.02 (for 2017) and 1,000,000.04 (for 2018).
DE42852: Securability Fix
DE41700: Securability Fix
DE40960: Securability Fix
DE37711: Process Access Right Issue
Steps to Reproduce:
1. Create a CA PPM resource from Administration -> Resources
2. Provide the following access rights to this user
Instance Access right to the process you will create in Step 3:
Process - Start
Process - Autostart
Global Access right:
Project - Navigate
Project - Edit Management All
 
3. Create a basic On Demand process on the project object, with only one action, for example updating the project description field with the following text - "test"
4. Create an Action on the project object, in order to run a process and associate the above process with the action
5. Add the above action to the Actions menu, available under the project properties view
6. Login as the above user and navigate to a project
7. From the Action menu, run the process , a popup dialog box will appear
8. Click on the YES button , to view the status of the process
Expected Results: The initiated process page should appear, displaying the initiated process
Actual Results: The initiated process does not display the following error message is displayed:
Error 401 - Unauthorized. You are not authorized to view the page. If you are sure you have access, try logging in again or contact your system administrator.
DE36169: New UX Published Status Report has Incorrect Report Date
STEPS TO REPRODUCE:
1. Log in to classic PPM.
2. Navigate to any project and create a draft status report with Report date as "01-Jul-2017"
3. Log in to the CA PPM New User Experience.
4. Navigate to the same project from Step 2.
5. Publish a status report.
Expected Result: The Status Report date is the current date for today.
Actual Result: The Status Report is picking up the report date of the latest draft available in the project (in this example, 01-Jul-2017).
DE37021: NEW UX Task Assignment Error - API-1007: You are not authorized to POST resources. Contact your administrator for security rights.
STEPS TO REPRODUCE:
Pre-requisite:
1. Create a Project
2. Add few team members
3. Make sure that Project Manager does not have any booking rights on the added team members
Steps:
1. Login as Project Manager making use of new UI.
2. Navigate to the project mentioned in the pre-requisite
3. Navigate to the Tasks tab.
4. Create a new task.
5. Click on [+Member] button to add the team member.
6. Search for the user who is already in the team tab in the "Add team Member" popup and click Add.
Expected Results: Team member should get assigned to the task with out any error/issue.
Actual Results: Team member successfully gets assigned to the task, but gets "API-1007 : You are not authorized to POST resource(s). Contact your system administrator for necessary security rights." error.
DE41370: Run Reports (Auto) is classified as a Restricted Right
STEPS TO REPRODUCE :
Check Run Reports (Auto) acces right.
Expected : Report Run (Auto) access right is View-Only
Actual : In licenses portlet, user gets the Restricted license type for Report Run (Auto)
DE42973: Load Data Warehouse Incremental fails with ORA-20100: ENCOUNTERED EXCEPTION... and ORA-30926: unable to get stable set of rows in source tables
Steps to Reproduce:
1. Run the Full Load DWH job
2. Create a financial plan on a project with no plans
3. Run an incremental load
4. Add a risk on the project while incremental is running
Expected Results: Investment Period Facts should populate properly
Actual Result: the DWH load throws an error
--------------------------------------------
Issues Fixed in 15.3.0.4
--------------------------------------------
DE38835: Applying Datamart_Extraction_Job_Def.xml fails
STEPS TO REPRODUCE
1. During the patch installation, seeding Datamart_Extraction_Job_Def fails.
Expected Results: Patch installation is successful.
Actual Results: Patch installation fails at the step above.
DE38186: Securability Fix
This security issue was fixed in this patch.
DE31552: New 'Team Rates Only' parameter to address Rate Matrix Extraction job taking very long time on large datasets
Steps to Reproduce:
1. Log into a PPM server with a large dataset.
2. Go to Home > Reports and Jobs > Jobs.
3. Filter for the Rate Matrix Extraction job, and schedule it to run.
Expected Result: The job should complete successfully in a reasonable time when the new 'Team Rates Only' parameter is checked along with the 'Prepare Rate Matrix Data' parameter.
Actual Result: The job takes a large amount of time to complete.
DE38429: Unable to save changes on a project if a dynamic lookup exists pointing to a sub-object and parent-child object processes exist in the system
Steps to Reproduce
1. Go to Studio > Objects > Create a new sub-object of the Project object called mysubobject.
2. Make it event enabled.
3. Go to Administration > Data Administration > Lookups.
4. Create a dynamic query called Mylookup with query as follows:
SELECT @SELECT:ID:[email protected],@SELECT:CODE:[email protected],@SELECT:NAME:[email protected] FROM odf_ca_mysubobject WHERE @[email protected]
5. Link the lookup to the mysubobject object. Go to Studio > Objects > Project object
6. Create a custom attribute called MyLkp pointing to the Mylookup lookup field.
7. On the Project object views, add the custom field to the General view. (Layout Edit > Project summary)
8. Create a project (in our example, My Project) and go to the Mysubobject list
9. Create a couple of instances of the sub-object.
10. On the Project general page, you now see the MyLkp field.
11. You can choose a value from one of the sub-object instances created.
12. Go to Administration > Data Administration > Processes.
13. Create a process called My_proj_process with the project as primary object.
14. Add a linked object and select the MyLkp attribute.
15. Give any auto-start condition to the process and validate it. The condition is not important, just the status of the process being active.
16. Go to Administration > Data Administration > Processes.
17. Create a process called My_sub_process with the mysubobject as the Primary object.
18. Add a linked object and select the Project object as the parent.
19. Give any auto-start condition to the process and validate it. The condition is not important, just the status of the process being active.
20. Go back to MyProject and click on Save.
Expected Results: The save action should be successful.
Actual results: An error is shown indicating 'Unable to communicate to PPM server. Please try again'.
DE36820: Portlet filter field issue
Steps to Reproduce:
1. Navigate to Home > Projects (or any other list view or portlet)
2. Select the Configure (gear) icon on the portlet
3. Select the List Filter Section tab
4. Select the List Filter Section tab to show the dropdown menu
5. Select the 'Fields' subtab
5. Click on the Properties icon of any field in the list
Expected Results: The properties page for the field is displayed.
Actual Results: A pop-up window is displayed with the error message: "Unable to process request - Server or Network error"
DE38136: The 'Click Here' link that directs to the properties of a task from a notification doesn't work
Steps to Reproduce:
1. Create a process
2. Add the Task object:
3. In the Start Options, select On Demand:
4. Setup the Start step to send notifications:
5. Click on Process - Completed process step
6. Add a link to the body of the notification using the browsing binoculars:
7. You should see the link in the body
8. Click save and return and validate the process:
9. Create an action in the Task Object:
10. Add the action to the Task Properties Action menu list
11. Launch the action from the Task properties
12. After that an email is received
13. When we click on the link, an error message appears with 'System error. Contact your system administrator'
14. We see that the CA PPM generated link contains the wrong ProjectId parameter. The Project Name is being used instead of the internal ID.
Expected Results: The link should correctly redirect to the Task Properties page of the corresponding task.
Actual Results: The link incorrectly directs the user to a page in PPM displaying 'Error: System error. Contact system administrator.'
DE38332: The auto-suggest feature performs poorly when searching for a Department OBS node on Oracle
Steps to Reproduce:
1. Log in to PPM as a Project Manager
2. Go to Home > Projects > [Project] > General Properties page
3. In the Department OBS field, start typing any valid ID from the Department List
Expected: The auto-suggest feature should find the Department OBS values promptly
Actual: The auto-suggest feature in the field takes over five minutes.
DE37316: The auto-suggest feature performs poorly when searching for a Department OBS node
Steps to Reproduce:
1. Log in to a PPM environment where there are many departments defined, along with varying levels of hierarchy.
2. Go to Home > Projects
3. Create a new project
4. Go to Department OBS and select Browse.
5. Type any valid department name in order to see all related values using the auto-suggest functionality.
Expected Result: The auto-suggest feature in the Department OBS field should find the department promptly.
Actual Result: The auto-suggest feature in the Department OBS field takes over a couple of minutes.
DE37269: Synchronize Agile Central Job fails with TASK_STATUS_INVALID_ACTUALS and API errors
Steps to Reproduce:
1. Configure an Agile Central integration in PPM as AC to PPM.
2. Create a project in PPM with the Start Date being the first day of the month and the Finish Date being the last day of the month. Associate it to the AC integration.
3. Run the Synchronize Agile Central Job.
4. Create a feature in AC under the initiative created in AC.
5. Create a user story for the feature and change it to In-progress. Note that the feature Actual Start Date is now today's date.
6. Run the Synchronize Agile Central job. Note that the Task Start Date in PPM has today's date.
7. Add a team member to the project and assign the team member to the task in PPM.
8. Create a timesheet and enter time for the resource using tomorrow's date. Post the timesheet.
9. Make sure the timesheet is posted and the Task Start Date is read-only. Note that the Task Start Date is now tomorrow's date.
10. Change the user story in AC to Accepted. Note that the feature Actual Start Date and Actual End Date in AC are now today's date.
11. Run the Synchronize Agile Central Job.
Expected Result: The Synchronize Agile Central Job completes and task is updated with the information from the feature
Actual Result: The Synchronize Agile Central Job fails with the following error, according to your project setup: There was a problem syncing tasks for the CA PPM project: DC Actuals Oct 400 projmgr.TASK_STATUS_INVALID_ACTUALS. PRJ-07234: Invalid status for task having non-zero actuals."
DE40517: Resources from Agile Central fail to get synced into PPM, when the count of unique owners is greater than 20
Steps to Reproduce:
1. Configure the Agile Central integration as AC to PPM.
2. Create a project in PPM and select the integration previously configured.
3. Run the Synchronize Agile Central job to create the initiative in AC.
4. Create more than 20 features for the initiative in AC.
5. Assign a different owner to each feature previously created.
6. Run the Synchronize Agile Central job again.
Expected Result: All features are created as tasks, and owners are either created as team members or displayed in the Missing Resources portlet.
Actual Result: Some resources are missing.
DE37752: In Advanced Reporting, The Timesheet Detail Report appears to be missing Sunday hours when using MS SQL Server
Steps to Reproduce:
1. Create or use a resource that has a department defined for it.
2. Post a timesheet with hours for that resource, with the hours being included on Sunday as well.
3. Run the Load Data Warehouse Job.
Expected Result: The hours posted for Sunday should show up on the report.
Actual Result: The hours posted for Sunday do not show up on the report.
DE38788: Performance issue with Advanced reporting after upgrading to Oracle 12c
STEPS TO REPRODUCE 
1. Log in to the application.
2. Navigate to Home > Advanced Reporting and run some project-related reports, such as these below:
- Project Status Report
- Project Summary Report
Expected Results: The reports should complete and return results promptly.
Actual Results: The reports are taking a while to return. In reports that have a multi-select filter parameter, when 2 more of items are selected, the reports runs for around 20 - 25 minutes. Other reports take around 15 minutes to run when using a parameter like the OBS Name.Some of the portfolio-related reports are taking a while to run as well.
--------------------------------------------
Issues Fixed in 15.3.0.3:
--------------------------------------------
DE37830: MSSQL Performance issues on the Load Data Warehouse - Incremental run
Steps to Reproduce:
1. Run the Load Data Warehouse - Full Job
2. Open any project that is current
3. Go to the Tasks list
4. Create a task and assign 3 resources to it
5. Create a second task and assign 3 resources to it
6. Create a third task, assign 3 resources, and add some ETC. Then save the task.
7. Run the Load Data Warehouse - Incremental Job
Expected results: The Load Data Warehouse - Incremental Job completes within a reasonable amount of time, provided the small amount of changes made.
Actual Results: The Load Data Warehouse - Incremental Job takes much longer than expected to complete, considerably longer than the Full run of the job.
DE36970: In a Budget Plan, the revision number is duplicated
Steps to Reproduce:
1. Navigate to the Cost Plan list page of any project that has a Plan of Record (for example, POR-1).
2. Create a new Cost Plan called NEW-PLAN-TO-BE-POR and mark this the Plan Of Record.
3. Submit the NEW-PLAN-TO-BE-POR for budget approval.
4. Go to the Budget List page and verify that the revision number is correct.
5. Make POR-1 the Plan of Record.
6. Submit the POR-1 for budget approval.
7. Go to the Budget List page and check the revision number.
Expected Results: The revision number of the submitted budget plan has the highest number and no duplicates appear.
Actual Results: The revision number of the submitted budget plan is 0 and is duplicated.
DE36556: Receiving the error message "ORA-01000: maximum open cursors exceeded " after scheduling multiple instances of the Synchronize Portfolio Job to run at the same time
Steps to Reproduce:
1. Log in to Classic PPM.
2. Schedule many instances of the Synchronize Portfolio Job to run over a specified time period.
Expected Results: Each run of the job completes successfully.
Actual Results: Several instances of the job fail with the error message "ORA-01000: maximum open cursors exceeded ".
DE38499: Securability Fix
DE36645: Error message "Creating instance of: odf personalization" is displayed when using the Resource Management Module in New UX
Steps to Reproduce:
1. Login to the New UX in PPM
2. Go to the Resource Management Module page
3. Click on the Select Filters button in the Investment Resources panel
4. Select the Investment Manager field and choose one from the accompanying list
Expected Results: The investment manager is selected and successfully added to the filter fields.
Actual Results:  An error message of "Creating instance of: odf personalization" is displayed in the top of the page while the filter is processing.
DE37713: Weighted Ranking Rules Bug
Steps to Reproduce:
1. Login to PPM
2. Navigate to Administration > Objects > Project.
3. Create a new attribute with the lookup type called "Yes No" and use the out-of-the-box lookup "PAC_RPT_YESNO".
4. Make this new attribute available in any section of the Project Edit view.
5. Create a new project called "Test1" and save it.
6. In the Edit view of the project, select the value of "No" for the attribute and save.
7. Create another project called "Test2" and save it.
8. In Edit view of the project, select the value of "Yes" for attribute and save.
9. Navigate to Administration > Objects > Portfolio Investment
10. Navigate to the Attribute Registry tab and move the "Yes No" lookup-type attribute from before to the Available Attributes column and save.
11. Navigate to Home > Portfolios and create a new portfolio
12. Navigate to the Contents Editor tab and add the 2 projects projects (Test1 and Test2) under the Individual Investments section.
13. Use the Sync Now button and wait for the sync to complete.
14. Navigate to the Waterlines tab and the 2 projects should be displayed there.
15. Click on the Define Ranking Rules button.
16. For the Primary Constraint, select the Planned Cost. Using the Add button, add the "Yes No" lookup-type attribute.
17. Select the Ranking Method as the "Higher is Better" parameter.
18. Click on the Lookup Value Weighting and assign a 0 weighting to the "No" value, and assign a 1 weighting to the "Yes" value, then save.
19. Now, click on the Run Ranking Rules button.
Expected Results: Project Test2 should be displayed first, followed project Test1, per the ranking rules we defined.
Actual Results: The ranking rules we defined do not appear to have had any impacts on the ranking of the projects. Regardless of the Ranking Method set, the results are the same.
DE37708: Power Filter Evaluated Expression shows incorrect String value
Steps to Reproduce:
1. Login to PPM
2. Navigate to Administration > Lookups
3. Create a new static lookup with the below configuration and then click Save and Continue
Lookup Name: Test Lookup
Lookup ID: test_lookup
Content Source: Customer
Source: Static List
4. Enter the below details in the next page and then click Save and Continue
Hidden Key: LOOKUP_ENUM
Display Attribute: NAME
5. In the next page, create a new list of values using the below information:
Lookup Value Name
ID (LOOKUP_ENUM)
Digital
1
Credit
10
Business Energy
2
Solar
20
6. Create a new Dynamic Query Lookup with below information and then click Save and Continue
Lookup Name: Test Lookup Dynamic Query
Lookup ID: TestLookup_DynamicQuery
Content Source: Customer
Source: Dynamic Query (Do not select any Object)
7. Enter the below query in the Niku Query section then click Save and Continue
SELECT @SELECT:probability.lookup_code:[email protected]
,@SELECT:Probability.name:[email protected]
FROM cmn_lookups_v probability
WHERE probability.lookup_type = 'TEST_LOOKUP'
AND probability.language_code = @where:Param:[email protected]
AND @[email protected]
8. Navigate to Administration > Object > Project
9. Navigate to the Attributes tab and create a new attribute called "Test Power Filter" and associate the created Dynamic Lookup (Test Lookup Dynamic Query)
10. Navigate to Home > Projects
11. Expand the filter section
12. Click on [Build Power Filter]
13. Select the Project object for the Object field, and for the, select the "Test Power Filter" field
14. Click Browse and select Digital. Click Add.
15. Click Add and verify the "Evaluated Expression" and "Expression" values
Expected Results: The expression should show the right ID for the selected value and the evaluated expression should show the correct corresponding value of the ID.
Evaluated Expression = ( Project Test Power Filter = 'Digital' )
Expression = ( project.test_power_filter == lookup("TESTLOOKUP_DYNAMICQUERY", "1") )
Actual Results: The expression shows the right ID, but the evaluated expression does not show the respective value of the ID.
Evaluated Expression = ( Project Test Power Filter = 'Credit' )
Expression = ( project.test_power_filter == lookup("TESTLOOKUP_DYNAMICQUERY", "1") )
DE36233: Attachments in the Collaboration tab don't work properly when using Internet Explorer
Steps to Reproduce:
1. Open PPM in Internet Explorer.
2. Go to Home > Projects.
3. Choose a project that has an attached document to it, and that has an accent in its name, such as "Planificación". A document with the accent can also be attached instead.
4. Go to the Collaboration tab.
5. Go to the document with accent.
6. Click on the name.
Expected Results: The application should prompt you with a download of the document.
Actual Results: The following error message is displayed instead, "The webpage cannot be found".
DE38482: Securability Fix
DE36673: Auto-numbering problem for the Resource ID Attribute
Steps to Reproduce:
1. Create an auto-assignment schema for the Resource ID attribute on the Resource object as follows: RES0000N, where N is the auto-assigned number.
2. Create a new resource in Administration > Resources > New.
3. Wait several hours or days and then create a second ID on the same system.
Expected Result: The generated resource IDs should only have a difference of one between the first resource and the second resource
Actual Result: There is an increasingly large difference between the first resource ID created and the second resource ID that is created later, depending on the amount of time that has passed between creations.
DE36987: The Capacity vs. Allocation by OBS report incorrectly filters out roles
Steps to Reproduce:
1. Create a role, for example QA Leader, and associate it with the Resource Pool OBS/All Groups.
2. Create a resource without selecting any primary role. Associate it with a Resource Pool OBS (for example, External/Onshore) and to a Department OBS (in our example, Corporate/IT).
3. Create a project, for example Project ABC, and add the QA Leader to the project team.
4. Replace the QA Leader role with the resource created in Step 2.
5. Run the Load Data Warehouse Job.
6. Navigate to Home > Advanced Reporting.
7. Open the report Capacity vs. Allocation by OBS.
8. Fill in a general OBS to cover all scenarios.
9. Now select the parameter Populate Resource Role.
10. Select the parameter Storage Architect role .
11. Uncheck the Show Graphs option.
12. Click Apply for the report to return results for this role.
13. Uncheck the role and select the QA Leader role, it should return with the message "No Matching Results"
14. Select both roles (QA Leader and Storage Architect) and run the report.
Expected Result: Report to return data for one role only as the other one has no matching results.
Actual Result: Report returns data for both the 'empty' role and the role with data.
DE35826: Error 401 when removing a tab from General View
Prerequisite: Create a non-administrator level user with the following access rights:
 
Groups -- No groups
Resource Access Rights - Instance:
Resource - Enter Time
Resource - Self (Auto)
User Favorites Menu - Edit
Resource Access Rights - Global:
Organizer - Access
Time Period - XOG Access
Timesheet approval - XOG Access
Timesheets - Approve All
Timesheets - Edit All
Timesheets - Navigate
 
Steps to Reproduce:
1. Under the General view, click Mange Tabs, then click New.
2. Add a new tab then Save.
3. Return to the General view to see the new Tab.
4. Click on the new tab.
5. Go back to the Manage Tabs page and remove the newly added tab.
6. Click Save and Return.
Expected Results: The user should be directed to the available tabs successfully.
Actual Results: The user is shown the error message "Error 401 - Unauthorized to view the page. If you are sure you have access, try logging in again or contact your system administrator.".
DE37806: For any locale other than English, the "HRS" bar does not get populated in the New UX
Steps to Reproduce:
1. Go to Home > Account Settings
2. Change the Locale to "German (Germany)"
3. Navigate to the New UX
4. Go to the Review and Approve tab
5. Filter for Posted Timesheets
Expected Results: The "HRS" bar underneath the name of a resource is populated.
Actual Results: The "HRS" bar is not populated.
DE39624: Reports scheduled from Reports and Jobs fail after a period of time.
Steps to Reproduce:
1. Navigate to Home, Reports and Jobs.
2. Select a report from the list.
3. Select Scheduled and uncheck Immediately under When.
4. Select today's date and time for the start date
5. Scroll down and select Set Recurrence
6. Set the report to run via crontab. For example, use 
*/15 * * * *
 to run every 15 minutes.
7. Submit the scheduled report.
Expected Results: Scheduled reports run every 15 minutes until paused or canceled.
Actual Results: Reports run as expected for a period of time, then fail. Once the scheduled report fails, it continues to fail.
DE39815: Jaspersoft reports run from PPM Reports and Jobs fail intermittently due to job ID from Jaspersoft is missing
Step to Reproduce:
Run 5 recurring reports from PPM Reports and Jobs giving a gap of 2 minutes
Expected Results: All Reports should be completed
Actual Results: Few reports fail
-------------------------------------------
Issues Fixed in 15.3.0.2:
--------------------------------------------
DE38046: Securability Fix
DE37429: Provide an option to run the Datamart Extraction Job with 'Extract Only OBS' or 'Extract Only Calendars' Parameters
DE33331: Assignment Max % Load Setting not exported to Microsoft Project when Windows Regional Settings are set to Portuguese
Steps to Reproduce:
1. Go Administration > Project Management > Settings
2. Make sure the checkbox "MSP Assignment Units Mapping with PPM Assignment Max % Load'' is checked
3. Go to Home > Projects
4. Select any project
5. Create a task and assign any resource
6. Instead of 100%, set the Max % Load to 50%
7. Export to Microsoft Project
Expected Result: The Microsoft Project Interface receives the Max % Load setting in the project
Actual Result: The Microsoft Project Interface does not receive the Max % Load in the project
DE36128: Allocation Costs are not calculated correctly
Steps to Reproduce:
1. Log into PPM and navigate to Home > Projects
2. Create a new project but don't define the rate matrix
3. Navigate to the Team tab and add any resource
4. Allocate the resource for a total of 10 hours.
5. Run the Rate Matrix Job (required to be executed if you have a matrix and the on-the-fly option is turned off)
6. Run the Update Cost Totals action from the Team tab
Expected Result: The allocation cost should either be 0 or should be using 1$ per hour.
Actual Result: The cost is calculated with $3600 per hour. In the above example, the allocation cost shows $36,000
DE37086: In Classic PPM, Incorrect Amounts Appear for Timesheet Totals
Steps to Reproduce:
1. Log into Classic PPM as Timesheet user.
2. Open any Timesheet that has a status of Open.
3. Add a few investments, in this example we used 3. The defect can also be reproduced with 2 investments.
4. Enter time as follows.
a. Day 1;(16/10); INV 1 : 1.99
b. Day 1;(16/10); INV 2 : 5.00
c. Day 1;(16/10); INV 3 : .505
Expected total: 7.495 which is incorrectly displayed as 7.50
5. Click Save and note the day total: Day total shows 7.5 (Correct)
6. Click Save again and note the day total: Day total shows 7.49 (Incorrect)
7. Click Save again and note the day total: Day total shows as 7.49 (Incorrect)
Expected Results: The actual hours at any point in time should be 7.50 in the totals.
Actual Results: The first initial Save in the timesheet page shows the correct 7.50 hours, but subsequent saves shows 7.49, which is incorrect.
DE37225: Email notifications sent by PPM display odd characters in the logo area
Steps to Reproduce:
The below steps are simply to trigger PPM to send an email via an Action Item notification, any method of prompting an email from PPM would apply for this defect
1. Configure an email server in the PPM CSA
2. Create a new resource -- or use an existing one -- but be sure they have a defined and valid email address
3. Go to Home > Organizer > Action Items tab
4. Click on 'New' to create a new Action Item and populate the required fields
5. Check the box titled 'Notify Assignees' and assign it to the resource from Step 2
6. Click 'Save and Return' and await the email notification to be sent out
Expected Result: Email notifications are sent out normally with no peculiar unexpected text
Actual Result: Email notifications are sent out with this text 'â„¢' appended next to the CA PPM logo and text
DE38059: Securability Fix
DE37541: Process is triggered unexpectedly when the Start Condition is not met
Steps to Reproduce:
1. Open a Project that has tasks/milestones
2. Go to Tasks
3. Open the project in the Gantt view by selecting Scheduler - PPM Gantt
4. Click on the Autoschedule menu, and select the Autoschedule with Publish option
5. For the purposes of this defect, we created a process based on the Project object with a Starting Condition of ( Project Status != Project Status [Previous Value] )
6. Observe process gets triggered when condition was not met 
Expected Result: Process should not be triggered as the Start Condition had not been met.
Actual Result: Process is triggered when it should not be.
DE38135: Redirection failure occurs due to JSESSIONID in the URL
Steps to Reproduce:
1. Make sure the browser is not currently opened.
2. Authenticate to PPM (PPM 15.3 in this scenario) via SSO using the following Relaystate
https://cppmxxxx.ondemand.ca.com/niku/app
3. An error message is displayed after successful SSO authentication.
4. The URL shows the presence of the JSESSIONID
https://cppmxxxx-dev.ondemand.ca.com/niku/app;jsessionid=D16EE4350C18985BA0490366F980A4D3
5. Manually remove the JSESSIONID from URL and refresh the page. The PPM page is then displayed properly.
Expected Results: Customer is prompted for their PPM login screen with no issue
Actual Results: The browser displays an 'HTTP 404 Error' 
DE38073: Securability Fix
DE37008: Load Data Warehouse - Incremental fails with error ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found ORA-06512: at "PPM_DWH152.DWH_INV_TASK_PERIOD_FACTS_LOAD"
Steps to Reproduce:
1. Ensure all pre-requisites for the Data Warehouse were met
2. Run the Load Data Warehouse - Full Job
3. Note that it completes successfully
4. Now run the Load Data Warehouse - Incremental Job
Expected Result: The incremental Load Data Warehouse Job should completely successfully
Actual Result: The jobs fails with the error message above 
DE36936: Classic PPM button in the Main Menu of the New User Experience does not function correctly
Steps to Reproduce:
On-Premise Environments:
1. Log into the New UI as an Administrative user and navigate to a project, and then view the tasks
2. Click on the Classic button located in the left navigation pane.
SaaS Environments:
1. Clear the cached data in your web browser.
2. Log into Classic PPM and obtain the JSESSIONID value from the browser session, and update the JSESSIONID value and the domain name in the URL.
3. Open a new tab and paste the updated URL into the address bar. The one in this example is as below:
https://test-server.ondemand.ca.com/pm/;jsessionid=39B24907C84AFDEA270CFCC9D577F308#/projects
4. Click on the Classic menu button in the left navigation pane.
Expected Result: The Classic PPM user interface appears.
Actual Result: An 'HTTP 404' error message appears.
DE38058: Securability Fix
--------------------------------------------
Issues Fixed in 15.3.0.1:
--------------------------------------------
DE37219: Summary Task Duration is Incorrect in PPM After Saving Back from Microsoft Project
Steps to Reproduce:
1. Prerequisite:
Set the Base Calendar in CA PPM to 7 hours per day:
a. In PPM go to Administration > Base Calendars
b. Click on the Base calendar
c. Select the check boxes next to all work days (Mon, Tues, Wed, Thurs, Fri)
d. Click the Set Shifts button
e. Set the following shifts:
Shift 1: 08:00 AM - 12:00 PM
Shift 2: 01:00 PM - 4:00 PM
f. Click Save and Return
2. Create a new project in Microsoft Project
3. Create a Summary task with 2 sub tasks
a. Set up the tasks with the below dates:
 
Summary Task
:
Duration 10.71 days (Default set by MSP with hours per day set to 7)
Start: 10/20/17
Finish: 11/2/17
 
Subtasks
:
Task 1
Duration 5 days
Start: 10/20/17
Finish: 10/26/17
Task 2
Duration 5 days
Start: 10/27/17
Finish: 11/2/17
Ensure there is a Start No Earlier constraint of 10/27/17.
  b. Task type for all tasks: Fixed Units
4. Save the project back to CA PPM. (At this point, the issue occurs if your work hours are set to 7 hours in Microsoft Project. If your work hours for the project are set to 8 hours in Microsoft Project, it will take an additional round trip of exporting/saving back the project to and from Microsoft Project for the issue to occur.)
5. Go into the Gantt view in CA PPM and check the duration of the Summary task.
Expected Result: The duration of the summary task matches that set in Microsoft Project.
Actual Result: The Duration in CA PPM for the summary task has changed (in the above example, it changed to 9 days).
DE36017: When creating instances of a grand child object via XOG it is actually only creating/updating instances in the first project
Steps to Reproduce:
1. Create a subobject of project object called ks_sub1
2. Create a subobject of object ks_sub1 called ks_sub_sub1
3. Navigate to Home > Projects and create or select any project
4. Under the Properties drop down, select ks sub1 list and create an instance with the name and code set to "ddd"
5. Navigate to Home > Projects and create or select another project.
6. Under the Properties drop down, select ks sub1 list and create an instance with the name and code set to "ddd"
7. Now attempt to create instances via XOG for the ks_sub_sub1 object that was created in Step 2 above
8. Notice that a second instance that should be created in the second project is not created. Instead it updates the same instance that was created in the first project.
Expected Result: Instances should be created/updated for different projects.
Actual Result: Instances are created/updated in the first project mentioned in the XOG input file.
DE35921: The 'Capacity vs Demand by Role' report doesn't show the unstaffed role when only one role is selected
Steps to Reproduce:
1. Create a new role with an availability of 7 hours.
2. Allocate the new role to 2 or 3 projects as a team member, no assignments to tasks and keep the role unstaffed.
3. Run the Load Data Warehouse jobs.
4. Run the Capacity vs. Demand by Role report filtering by the following:
a. Select the role previously created
b. Checked include Unstaffed roles
c. Leave all other filter options as default.
Expected Result: To see data returned for the new role.
Actual Result: The message 'No matching records found' is displayed when only the new role is selected.
DE36585: Financial Forecast Review by Investment report not showing correct numbers
Steps to Reproduce:
1. Financially enable a project and add 2 financially enabled resources. If possible, choose 2 resources with the same TRANSCLASS.
2. Create a task so you can post transactions to it. Do not assign the resources to the task.
3. Create a manual cost plan:
- Group by TRANSCLASS and RESOURCE
- Add costs in the current month for both lines
4. Create and post a total of 4 transactions:
- 2 transactions for each resource
- Use a different transclass on the second transaction for each resource.
5. Post to WIP.
6. Run the Load Data Warehouse job.
7. Run the Financial Forecast Review by Investment report for the investment. Choose Planned as the Financial Planned Type. Choose the correct Fiscal Year.
Expected Result: The numbers in the report should match the cost plan.
Actual Result: The numbers in the report are doubled and do not match the cost plan.
DE36320: ORA-00600 [qctcte1] error when running Portfolio Plan Comparison report
Steps to Reproduce:
1. Configure the Data Warehouse and run the Load Data Warehouse jobs
2. Run the Portfolio Plan Comparison report
Expected Result: the report runs without any issues
Actual Result: The report fails with ORA-00600: internal error code, arguments: [qctcte1], [0], [], [], [], [], [], [], [], [], [], []
DE36486: Not able to configure API Attribute ID on the Investment object for custom attributes.
Steps to Reproduce:
1. Go to Studio and under Objects, filter on "Investment"
2. Drill-down on the Investment object and create a custom attribute
Expected Result: Being able to define an API Attribute ID
Actual Result: User is not able to define an API Attribute ID.
DE36641: Memory leak in PPM Sync job with Agile Central may cause OutOfMemory Exceptions in the BG
This issue was not reproducible in-house. Memory leak noticed in post-mortem analysis of Java heap dumps
showing TimingElements from the PerformanceMonitor for the syncMilestones monitor. This monitor had
a PerformanceMonitor.start() call but no corresponding PerformanceMonitor.end() call, which would
leave the TimingElements in the thread local storage until the thread was re-used by another job.
The change was to add a PerformanceMonitor.end() call for the syncMilestones monitor and to clear
the thread local storage for a job at the end of thread execution.
DE36656: Time Scaled Value Navigation Jumps Periods
Steps to Reproduce:
1. Log into CA PPM and select Administration, Studio, Portlets
2. Click on the New button and select Grid Portlet.
a. Portlet Name: m_mags
b. Portlet ID: m_m1
c. Content Source: Customer
d. Category: Business Intelligence
e. Instance Type: General
f. Object: Cost Plan Detail
3. Go to List Column Section tab > List Column Fields > click New > for the Display Type select Time Scaled Value > click on the Next button
Fill in these fields:
Value Attributes: Actual Cost
Column Label: Test
Display Type: Number
Start Date: Other date
Time Scale: Year
Number of Time Periods: 4
4. Go to the List Column Section tab > List Column Layout > move over the following from Available Columns to Selected Columns:
'Actual Units',
'Investment Code',
'Investment Name',
'Cost Type'
'Test'
5. Then Publish
6. Go to Home > General page > click on Manage My Tabs
7. Click on the New button
Tab Name: Test TSV
8. Go to the Content tab and select m_mags
9. Go back to the General page and click on the Test TSV tab
10. In the Test TSV tab click on Options icon which is located to the right hand side of the screen (it's the cog wheel icon) > select Time-scaled Value
11. Change the 'Time Period Offset' from '4' to '0' > Save and Return
12. You should see the years 2017, 2018, 2019, 2020 for the TSV
13. Go back to the Test TSV page and go to the TSV and click on the > icon to move forward in time
14. Now click on the < icon to move back in time
Expected Results: The yearly time periods 2017, 2018, 2019, 2020 are displayed
Actual Results: The yearly time periods 2013, 2014, 2015, 2016, are shown instead. The display does not display the subsequent 4 periods and the Time Period Offset is now -4
DE35708: Feature is unable to be synced as a task in PPM from Agile Central
Steps to Reproduce:
1. Create a Feature (task) in Agile Central and enter a title for the feature such that it meets the max character limit (256 characters).
2. Run the Synchronize Agile Central job.
Expected Results: Job runs and completes successfully.
Actual Results: The job fails with the following error message: "There was a problem syncing Clarity tasks for Project: Test Project".
DE36575: Synchronize Agile Central job fails when projects or tasks are associated to milestones
Steps to Reproduce:
1. In PPM, create an AC to PPM integration with Agile Central providing the workspace, project and owner.
2. Create a project in PPM and link it to the integration created above.
3. Run the Synchronize Agile Central job (Rally Synchronization job).
4. In Agile Central, add more than 20 milestones to the project used for the integration.
5. Still in Agile Central, create 3 or 4 features to the initiative created for the PPM project.
6. Add all milestones (more than 20) to the features (divide them by each feature).
7. Run the Synchronization Agile Central job again.
Expected Result: Features are created with the respective milestones and job completes.
Actual Result: Job fails with the following error because not all milestones are loaded from Agile Central:
java.lang.ClassCastException com.niku.nmc.agile.AgileIOException: 500 api.internalError API-1019 : Could not process the request due to internal error.
DE35999: Session logout issue while Navigating between Classic and New UX
Steps to Reproduce:
  1. Log in to CA PPM in Chrome or IE.
  2. Click on Home > Link to the New User Experience. (This step assumes you already created an optional menu link as described in the documentation.)
    The New User Experience opens in a new tab while the Classic CA PPM interface remains open in the first tab.
  3. Go back to Classic PPM on the first tab and click on any other menu link to go to another page. For example, click Home, Demand Management, Ideas.
    The Login page appears.
Expected Results: Classic UX should have the user logged in and the user should be able to navigate from the current page to any other page without having to login.
Actual Results: The user is presented with the Login page and has to login in order to go back into the Classic UX.
DE36242: New UI - Incorrect behavior while accessing Project Status Report via notification URL
Steps to Reproduce:
1. Login in to CA PPM using New UI.
2. Navigate to any project and publish a status report
3. Copy the Project Status Report URL. This is what the process sends out via Notifications to Project Managers
4. When accessing the Project Status Report URL while the user is already logged successfully directs the user to the Status Report page
5. Try to access the Project Status Report URL while the user is logged out
Expected Result:
Users should land on the Project Status Report page for the URL they access, even after having to log in
Actual Result:
Users are instead prompted to log in to the New UI and are redirected to the Project List page instead of the Project Status Report page upon logging in
DE36493: New UI - In the Role Request view, the "Allocate To" field is not displaying the resource and primary role
Steps to Reproduce:
1. Log in and navigate to Resource Planning
2. Go to the "Request" view and expand "DBA" and click "BYOD Management" to see the view
3. On the "Allocate To" field search for a resource
Expected Result: The lookup display should show both resource and primary role
Actual Result: The lookup display only shows the resource.
DE36976: The Data Warehouse Investment Summary Table losing data and the Trending Seed data is Invalid
Steps to Reproduce:
1. Run the Full Load DWH job followed by the incremental run.
Expected Result: Data is intact and not lost
Actual Result: Data is lost in the dwh_inv_summary_facts table and the trending seed data has duplicate data that needs removed.
Jaspersoft 6.2.1 Patch for CA PPM 15.3 (No Longer Supported)
Jaspersoft Server Cumulative Patch 6.2.1_5.2.1.4 for CA PPM 14.3, 14.4, 15.1, 15.2, and 15.3 was the minimum supported Jaspersoft cumulative patch through June 28, 2018. Customers must upgrade to JasperReports Server 6.4.2 for CA PPM available in March 2018 or 7.1 (recommended) available since November 2018.
: Effective June 28, 2018, CA no longer supports Jaspersoft 6.2.1. If you are installing Jaspersoft for the first time or upgrading, you must install 6.4.2. The CA download center no longer includes 6.2.1. From 6.4.2 you can upgrade to 7.1.
: New installations of CA PPM 15.3 and upgrades to CA PPM SaaS 15.3 included the 6.2.1 patch. As an administrator for an on-premise environment, after upgrading to CA PPM 15.3, you must install the latest Jaspersoft patch available from CA yourself. You can decide among the following options: upgrade to 6.4.2 (minimum), perform a fresh install of 6.4.2 (and optionally migrate reporting content), or defer (that is, remain on 6.2.1 temporarily until you upgrade CA PPM). For example, you plan to upgrade to CA PPM 15.6 which includes Jaspersoft 7.1.
Jaspersoft Server Cumulative Patch 6.2.1 README
----------------------------------------------------------------
Base Version #: 6.2.1
Patch Version #: 5.2.1.4
----------------------------------------------------------------
 
 
6
 
5
 
 
**** NOTE *****************************************************
Patches are intended to be timely fixes and are not fully regression or integration tested, and are only tested against the issues listed below. CA feels confident that this patch will resolve the addressed problems, but customers should be aware that a patch could have adverse side effects to the function of their application. Customers should not apply patches directly to production systems without first verifying in a test environment.
! Stop Jaspersoft Tomcat services before applying this patch.
Known Issues and Workarounds:
 
Java Exception
: If you encounter "java.io.IOException: CreateProcess error=206, The filename or extension is too long" while applying the patch, shorten the path length of the installation directory. For example, the recommended path for the patch installation directory appears as follows:
Windows:
C:\6.2.1_5.2.1.x.x
Unix, Linux, or OS X:
/fs0/6.2.1_5.2.1.x.x
 
Please Wait Message
: If users encounter a ‘Please Wait’ message that does not disappear when attempting to access the 
Clarity PPM
 Advanced Reporting page after installing Jaspersoft Server Cumulative Patch 6.2.1_5.2.1.4, clear the browser cache on the client machine for each user attempting to access Advanced Reporting.
If any issues arise during the installation or use of this patch, contact CA Support.
****************************************************************
INCLUDED FILES:
----------------------------------------------------------------------
README.txt -> This file
bin/install.sh -> Unix installer
bin/install.bat -> Windows installer
bin/install.xml -> Ant install script
PRE-REQUISITE - ADDITIONAL NOTES:
----------------------------------------------------------------------
- CA PPM customers with Jaspersoft Report Server v6.2.1 can apply this patch.
----------------------------------------------------------------------
HOW TO INSTALL THE PATCH:
-------------------------
1. Stop the application server (Apache Tomcat Server), on which JRS is deployed.
2. Find the root web application folder (e.g. c:\apache-tomcat\webapps\reportservice\).
3. Make a back-up copy of that folder to a new, separate location.
4. Extract the CA PPM Jaspersoft Patch zip file to a location (<patch_dir>).
5. Install the patch: Go the <patch_dir> --> bin folder. The bin folder contains installer scripts, that you need to run on the OS command prompt.
5.1. Interactive Installation
5.1.1. Run command 'install.bat/sh interactive' based on the OS.
5.2. Silent Installation
5.2.1. Run command 'install.bat/sh' based on the OS.
5.2.2. Make sure all the property values in 'install.properties' file, have proper values in it.
5.2.2.1. patch.deploy.tomcat : Tomcat Server base folder absolute path.
5.2.2.2. patch.deploy.jrs.webapp.name : Deployed JRS webapp name.
5.2.2.3. patch.deploy.capb.name : Value should be always 'clarity'.
5.2.2.4. patch.install.mode : Values can be 'standalone' or 'cluster', based on the node your installing the patch. Specify 'standalone' for primary node and 'cluster' for secondary nodes.
APPLICABLE ONLY FOR AZURE ENVIRONMENT:
5.2.2.5. jaas.deploy.environment : By default the value is 'op'. If deploying in azure environment, specify the value of the property as 'azure'.
5.2.2.6. jaas.deploy.environment.compliance.level : By default the value is 'standard'. If deploying in azure environment and for FedRAMP compliance, specify the value of the property as 'fedramp'.
6. Clear the application server (Apache Tomcat Server) 'temp' directory.
7. Clear the application server (Apache Tomcat Server) 'work' directory.
8. Start the Apache Tomcat Server, on which JRS is deployed.
9. Clear browser cache on client.
HOW TO UNINSTALL THE PATCH:
-----------------------
1. Stop the application server (Apache Tomcat Server), on which JRS is deployed.
2. Find the root web application folder (e.g. c:\apache-tomcat\webapps\reportservice\).
3. Restore the all the files under /reportservice from backup.
4. Restart Tomcat instance.
-------------------------
Additional Functionality Delivered in 5.2.1.4:
-------------------------
Korean language support is now available with this patch for Jaspersoft Server 6.2.1
This will be applicable only with CA PPM 15.3 and above versions.
Upgraded Jaspersoft Server Enterprise License to unlimited expiry date
This license file is also bundled along with patch zip artifact (<patch-unzipped-folder>\resources\license\jasperserver.license). Post applying the patch, expected behaviour is that expiry date should change on the server. However, if the expiry date is still not changed on the server, please find the file 'jasperserver.license' in the file-system and replace the same with the license file shared in the patch artifact.
TIBCO has identified CSRF, XXS, and XXE related security vulnerabilities in Jaspersoft Reporting Server v6.2.1 and same were addressed in Jaspersoft Server 6.2.3 by TIBCO
Fixes for these security vulnerabilities have been back-ported to Jaspersoft Server 6.2.1 through this patch.
-------------------------
Issues Fixed in 5.2.1.4:
-------------------------
DE35172: Adhoc views fails to open in Jaspersoft 6.2.1 when there is condition Divisor is equal to zero error
Steps to Reproduce:
1. Created an Ad Hoc View, selecting the Resource Management domain.
2. Selected all fields and click OK.
3. Drag and drop Weekly Start Date to the view’s columns.
4. Drag and drop the Weekly Periods -- Resource -- Available FTE measure to the view’s columns.
5. Drag and drop Resource Name to the rows.
6. Create the first calculated measure by copying and pasting "Available FTE" - Round("Time FTE", 0) into the formula field, calling Measure name Open, validating it then finally click the Create Measure button.
7. Create the second calculated measure, copy and paste Round("Time FTE", 0) into the formula field and call the measure name Complete.
8. Create the third calculated measure, copy and paste ("Complete" % ("Open" + "Complete")) into the formula field and call the measure name % Comp. Create the measure.
9. Drag and drop the newly create % Comp measure to the view’s columns. This step works in Jaspersoft 6.1 and screen shot is attached
Measures created
Open: "Available FTE" - Round("Time FTE", 0)
Complete: Round("Time FTE", 0)
% Comp: ("Complete" % ("Open" + "Complete"))
Expected Results: It should fetch the data.
Actual Results: The adhoc view crashes and error in log ORA-01476: divisor is equal to zero error.
DE32148: Scheduled Report are blank after Jaspersoft migration from 6.1 to 6.2.1
Steps to Reproduce:
1. Login to CA PPM 14.3 or 14.4 which is linked to Jaspersoft 6.1
2. Go to Advance reporting and schedule few reports
3. Set up a Jaspersoft 6.2.1 and migrate the content from 6.1 tenant wise
Expected Results: The scheduled report should run and give the proper data
Actual Results: The schedule report run but it returns blank data
DE33063: Advanced Reporting missing Login As User Functionality
Steps to Reproduce:
1. Log into CA PPM as user with the Jaspersoft ROLE_ADMINISTRATOR role.
2. Select the Home tab then Advanced Reporting.
3. Once in Advanced Reporting select Manage -> Users.
4. Once the list of users display click on a user.
5. View the properties of the user.
Expected Results: Three buttons are visible, Edit, Login as User and Delete User.
Actual Results: Only two buttons are visible Edit and Delete User.
DE33934: Adhoc Views are corrupted with Null Pointer Exception
Steps to Reproduce:
1. Create a new Adhoc view with Resource Management Domain
2. Select Resource Name, investment name, Month Start Date from Calendar Periods, Available hours measure
3. Create a cross tab by adding investment name to rows, month start date & Available Hours to Columns
4. Add Investment name to Filter and select any Project which displays data and apply filter
5. Right Click on Month Start Date and delete Column Summary (This Step is Key as all the views with no Column Summary are having this issue)
6. Save Adhoc View with the results
7. Now change the name of the investment in CA PPM which is used in the filter
8. Run Load Data warehouse job in CA PPM to update investment name in DW
9. And navigate to Advanced Reporting and navigate to saved Adhoc view
10. Try to Open Adhoc view
Expected Results: The Adhoc view should open
Actual Results: The Adhoc view is corrupted and shows null pointer error
-------------------------
Issues Fixed in 5.2.1.3:
-------------------------
DE30551: Jaspersoft - Please wait message disappears when report run in same session by changing the parameter
Steps to Reproduce:
1. Run a report with around 10 parameters click on apply.
2. Report will start generating the data in the report with a message ‘Please wait’ till it fetches the data on the first page.
3. Change the filters by selecting more values to the existing filter options or reducing already added filter values and then click on apply button to generate the data
Expected Result: Please wait message should be there on screen till the first page of report loads completely.
Actual Result: Please Wait message disappears so quickly that user feels the report is completely generated but actually it’s not.
DE32538: When scheduling a Jaspersoft report, Argentina Time zone is not available
Steps to Reproduce:
1. Log into CA PPM as a user with Advanced Reporting access
2. Select Home -> Advanced Reporting
3. Select Reports -> View list
4. Right Click the desired report and select Schedule.
5. On the Create Schedule tab, expand the Time Zone drop down.
Expected Result: Argentina Time Zone available in the list.
Actual Result: Argentina Time Zone is not available in the list.
DE32714: Jasperadmin & Joeuser (two users created by default on creating a new tenant) with Full Admin permissions are having their password set to default for the new tenants
Steps to Reproduce:
1. Execute the command to import tenant from bin folder of CA PPM installation - "admin content-jaspersoft csk -userName superuser -password xxxxxx -fileName jaspersoft_csk.zip"
2. This would create a tenant on Jaspersoft v6.2.1 server with default users as Jasperadmin & Joeuser.
3. Login into Jaspersoft v6.2.1 server, try to login with Jasperadmin/Joeuser credentials from the login page.
Expected Result: Login should not be successful.
Actual Result: Both Jasperadmin/Joeuser are able to login with default password.
IMPORTANT! Please notice after applying this patch, on creating a new tenant,
A) Jasperadmin user will be created with an unknown password. Jaspersoft administrator can update the password.
B) Joeuser will NOT be created by default.
NOTE: The above points do not apply for tenants that are getting migrated.
DE30205: Full project list not displayed in Adhoc view if static lookup from project subobject is added as a field to be displayed
Steps to Reproduce:
1. Create a Project subobject.
2. Add an attribute to the subobject that uses a static lookup.
3. Add the subobject to the data warehouse by selecting the 'Include the sub object in Data Warehouse' check box.
4. In both the Create and Edit view of the subobject General page add the static lookup attribute created in an earlier step.
5. Create an instance of the subobject in say 5 projects and populate the name of the instance as well as lookup value.
6. Execute ‘Load Data warehouse’ job by selecting ‘Full Load’ option.
7. Create an Ad Hoc view under Advanced Reporting section using Project Management domain.
8. On the 'Domain: Project Management' page, drag and drop the Project name from 'Fields' section on the left into 'Rows' section on the right. All project names appear.
9. In the 'Fields' section expand 'Custom' to display the sub object created in step one. Expand the sub object to display attributes. Drag and drop 'Name' attribute into 'Rows' section. All project list still get displayed.
10. In the 'Fields' section under 'Custom' drag-and-drop the subobject lookup attribute into the 'Rows' section.
Expected Result: The list of projects to remain intact.
Actual Result: The list of projects is truncated to display only 5 projects which are ones with subobject instances.
DE32737: Enable JavaScript functions on the Jaspersoft server
Steps to Reproduce:
1. Create a Jaspersoft Studio Report and publish the same to Jaspersoft v6.2.1_5.2.1 server. This report should have some JavaScript functions.
2. Run the report on Jaspersoft v6.2.1 server, once successfully published.
Expected Result: Report should successfully execute.
Actual Result: Report execution fails.
Note: With this Jaspersoft Server Cumulative Patch, 'Permission Prefetcher' is auto-enabled. This will make the Jaspersoft server repository navigation comparatively faster.
-------------------------
Issues Fixed in 5.2.1.2:
-------------------------
CLRT-81493: Output locale in Jaspersoft scheduling options is always set to default
Steps to Reproduce:
1.Login as CA PPM user who has advance reporting rights
2.Navigate to Home->Advanced reporting
3.Schedule a report and check output locale option in scheduling options
Expected Result: Report output locale should be corresponding to the language set for the logged in user in CA PPM.
Actual Result: Report output locale is not set according to the language set in CA PPM
CLRT-81492: All locales present in CA PPM are not present in Jaspersoft scheduling output locale
Steps to Reproduce:
1. Login to CA PPM with user who has advanced reporting access rights
2. Navigate to Home->Advanced reporting
3. View reports list
4. Schedule any report
5. Navigate to scheduling options and observe output locales
Expected Result: Locales present in CA PPM should be supported in Jaspersoft as well.
Actual Result: Only few locales are present in jaspersoft report scheduling options.
CLRT-81491: CA PPM user with ‘Advanced Reporting - Administer’ access right should be able to update the domain schema via Jaspersoft
Steps to Reproduce:
1. Login as a CA PPM user with ‘Advanced Reporting - Administer’ access right.
2. Navigate to Home->Advanced reporting
Expected Result: As a tenant administrator I should get an option to update domain schema from Jaspersoft UI.
Actual Result: No mechanism to update the domain schema from jaspersoft UI.
CLRT-81490: Import and Export capability for tenant administrator in Jaspersoft
Steps to Reproduce:
1. Login as a CA PPM user with ‘Advanced Reporting - Administer’ access right.
2. Navigate to Home->Advanced reporting.
Expected Result: As a tenant administrator I should get an option to export and import selected resources from Jaspersoft UI.
Actual Result: No mechanism to export and import selected resources from Jaspersoft UI.
Steps to Reproduce:
1. Using IE11, login to CA PPM. Make sure there is at least one active desktop application that is not minimized, and make sure there are no other open IE windows or tabs.
2. Click on Advanced Reporting
3. Observe that Jaspersoft screen is either minimized or in background now
4. Click on IE icon in tray to bring screen to forefront or maximize
5. Under Reports, click on View List and observe that Jaspersoft screen is either in background or minimized again
6. Click on IE icon in tray to bring screen to forefront or maximize
7. Click on any stock report and observe that Jaspersoft screen is either in background or minimized again
Expected Result: IE 11 browser should not minimize.
Actual Result: IE 11 browser minimizes.
-------------------------
Issue Fixed in 5.2.1.1:
-------------------------
CLRT-79518: When setting date filters in ad hoc views, the system changes the selected date (for example, filter projects with a finish date >= 1/1/15, the system changes that date to 12/28/14
Steps to Reproduce:
1) Login into CA PPM
2) Click on Home->Advanced Reporting
3) From the main menu, click on Create Ad Hoc Views
4) From Select Data Menu... Select Investment Managements
5) From the Source window, Expand Investment
6) Select the following " Investment Name, Investment ID, Start Date, Finish Date, Click ok
7) Ad Hoc View change "Crosstab to Table"
8) Drag and Drop the following " Investment Name, Investment ID, Start Date, Finish Date from Filed Menu to Columns
9) Right Click on the header of "Finish Date", click on add filter
10) Click on the calendar and select the Date
11) Click on Apply
12) The data will populate correctly, but the "Date will change from 2015-12-18 To 2015-12-16"
13) The Apply Tab will highlight again and if we click again then it will change the date from "2015-12-16 To 2015-12-14"
Expected Result: The Date should not change.
Actual Result: Date changes.
JasperReports Server 6.4.2 for CA PPM README (Minimum Supported Release)
JasperReports Server 6.4.2 is a maintenance release that includes security updates and improvements requested by customers. This update resolves a number of security vulnerabilities associated with 6.2.1, supports same-database upgrades from the previous 6.2.1 release, and introduces new dashboard improvements. 
Highlights of this release include:
  •  
    New Supported Platforms
    : The following components included in the installer are updated: Apache Tomcat 8.5.20, Oracle JDK 8 version 1.8.0_144 (8u144), PostgreSQL 9.3.18 (not supported), and Spring Framework 3.2.18 (not supported).
  •  
    Directory Access Control
    : The improvements include a new option to deny access to directories in the file system of the JasperReports Server host using the ResourceForwardingServlet servlet. The servlet forwards requests from, for example, /runtime/<hex-code>/<my-resource> to the /<my-resource> URL to handle browser caching. Access to the WEB-INF and META-INF directories is always denied. In some circumstances, you may want to deny access to other directories. For example, if you restrict access to certain directories using the security-constraint tag in web.xml, you should also restrict access to those directories using the forwardForbiddenDirectories parameter of the ResourceForwardingServlet servlet. To do so, edit a configuration file.
  •  
    Dashboard Enhancements
    : Dashboards can now be scheduled (limited support). Dashboard export enhancements are also included. Dashboards support hyperlinks for dashlets that can replace the current dashboard with a web page, report, dashboard, or ad hoc view. New formatting options for text dashlets are also available. New Undo, Redo, and Undo All buttons on the dashboard toolbar allow you to undo and redo recent changes made to the dashboard, including changes to input control values. You will also see new Time-Date wildcards for dashlets.
  •  
    Import-Export Enhancements
    : Tenant-level exports show a new Include Dependencies option Organization admins can now export individual resources or entire folders from the repository page. Superusers also have new options to export resources and folders without full paths or dependencies, so that the resulting catalog can be imported by organization admins. A new 
    Include Dependencies
     option is available when exporting. In Jaspersoft 6.2.1, the export.zip contained all the dependencies.
    image2018-2-28 10:53:55.png 
  • PhantomJS library upgrade to 2.2.
  • New Cross-Site Request Forgery (CSRF) protection mechanism.
  • Out-of-Memory fixes for compressed class exceptions.
  • Performance improvements for ad hoc view crosstabs
: Install or upgrade your reporting environment using the installer provided by CA. On-premise customers can decide among the following options: upgrade the same database from 6.2.1 to 6.4.2, perform a fresh install with 6.4.2 (and optionally migrate reporting content), or defer (that is, remain on 6.2.1 temporarily until you upgrade CA PPM). For example, you plan to upgrade to CA PPM 15.4 which includes JasperReports Server 6.4.2. Due to security fixes, we recommend that you upgrade to 6.4.2 as soon as possible. JasperReports Server 6.2.1 will be End of Service as of June 28, 2018.
JasperReports Server 7.1 for CA PPM README (Recommended Release)
JasperReports Server 7.1 is the newest release that includes new features, enhancements, and security updates. All CA PPM SaaS customers automatically receive this new release. CA PPM on-premise customers must use the CA PPM Jaspersoft installer to apply it. The installer is a customized wrapper written on top of the original third-party installer.
: After installing or upgrading to CA PPM 15.3 or higher, you must upgrade your reporting environment using the installer provided with CA PPM. On-premise customers can upgrade the same database to 7.1, or perform a fresh install of 7.1, and optionally migrate their reporting content. Jasperosoft 6.4.2 is also supported. You cannot remain on JasperReports 6.2.1 (supported ended June 28, 2018). Due to security fixes, we recommend that customers on all releases of CA PPM upgrade to 7.1 as soon as possible. For a visual summary of your options, see CA PPM Jaspersoft 7.1 Upgrade Assistant 
Highlights of the 7.1 release include:
  • Resolves a number of security vulnerabilities associated with previous releases including 6.4.2.
  • Supports same-database upgrades from the previous 6.4.2 release.
  • New Visualize.js
  • New Jaspersoft Studio data source support for domains and TIBCO Spotfire® information links
  • Improved JasperMobile App Experience
  • JasperReports engine simple text in field property expressions
  • TIBCO Datasource Visualization JDBC driver
  • Native Java 8 support (no longer supports Java 7, SOAP APIs, and Jaspersoft REST API v1.0)
  • Security Fixes
  • New Ad Hoc Views
 
HARDWARE AND SOFTWARE REQUIREMENTS
 
------------------------------------------------
  • See the CA PPM Release Notes and TIBCO Documentation.
  • CA PPM SaaS customers enjoy an automatic upgrade to JasperReports 7.1.
  • CA PPM 15.3 on-premise customers must download the CA PPM Jaspersoft 7.1 installer, which is a customized wrapper written on top of the original third-party installer. Only the CA installer can be used to install Jaspersoft and integrate it with CA PPM for reporting.
Express Install Steps for JasperReports Server 6.4.2 or 7.1
 Only the CA installer can be used to install Jaspersoft and integrate it with CA PPM for reporting. Do not install software, download patches, or apply hot fixes directly from TIBCO. Only 
ca_ppm_jaspersoft_7.1.0_6.1.0.28.zip
 on 
Tomcat 8.5.30
 with 
JDK 1.8_171
 is certified and supported. Due to performance issues, we recommend avoiding Tomcat 8.5.31.
 
Note
: You can also follow these steps to install or upgrade Jaspersoft 6.4.2 on your legacy 6.2.1 reporting environment (6.2.1 is no longer supported). The steps for 6.4.2 are almost identical to the steps for 7.1. We recommend 7.1; however, 6.4.2 is also supported.
Use the CA PPM Jaspersoft installer, a customized wrapper written on top of the original third-party installer.
 Only the CA installer can be used to install Jaspersoft and integrate it with CA PPM for reporting. Do not install software, download patches, or apply hot fixes directly from TIBCO. See CA Download Center.
: Install or upgrade your reporting environment using the installer provided by CA. On-premise customers can decide among the following options: upgrade the same database from 6.2.1 to 6.4.2, perform a fresh install with 6.4.2 (and optionally migrate reporting content), or defer (that is, remain on 6.2.1 temporarily until you upgrade CA PPM). For example, you plan to upgrade to CA PPM 15.4 which includes JasperReports Server 6.4.2. Due to security fixes, we recommend that you upgrade to 6.4.2 as soon as possible. JasperReports Server 6.2.1 will be End of Service as of June 28, 2018.
------------------------------------------------
 
Known Issue with Fresh Installations of Jaspersoft 7.1
 
In on-premise environments, you might observe the following 
Failed to execute: create index 
entry in the installation logs during a new installation of Jaspersoft 7.1.0 on Oracle 11g R2 or 12c:
 
[exec] [exec] init-js-db-pro:
[exec] [exec] [echo] For JDBC driver the artifactId and version properties are set:
[exec] [exec] [echo] maven.jdbc.artifactId=ojdbc8
[exec] [exec] [echo] maven.jdbc.version=12.2.0.1.0
[exec] [exec] [echo] Specified JDBC driver jar exists
[exec] [exec] [advanced-sql] Executing resource: /fs0/clarity1/install_cd/ca_ppm_jaspersoft_7.1.0/buildomatic/install_resources/sql/oracle/js-pro-create.ddl
[exec] [exec] [advanced-sql] 0 rows affected
[exec] [exec] [advanced-sql] 
Failed to execute: create index
 idx46_jiresfldr_hidden_idx on JIResourceFolder(hidden)
[exec] [exec] [advanced-sql] java.sql.SQLException: ORA-01408: such column list already indexed
[exec] [exec] [advanced-sql] 0 rows affected
[exec] [exec] [advanced-sql] Executing resource: /fs0/clarity1/install_cd/ca_ppm_jaspersoft_7.1.0/buildomatic/install_resources/sql/oracle/quartz.ddl
 
: You can ignore this entry. The warning appears to be alerting you about a duplicate index creation scenario; however, it is not a valid warning.
  • This warning has no impact on your installation and does not affect any Jaspersoft 7.1 functionality. 
  • CA Engineering teams confirmed that all the DDL commands are successfully executed after the reported warning.
  • The warning only appears on new Oracle installations; it does not occur with supported versions of Microsoft SQL Server 
IMPORTANT
------------------------------------------------
JasperReports Server can be deployed as a standalone application or in a cluster for high concurrency. Clustered JasperReports Server Instances will use thread-safe access to their private repository database. As a result, any number of JasperReports Server instances can share the same repository thus present the same environment to users.
When JasperReports Server is deployed in a cluster, it is advised to dedicate one or more JasperReports Server instances in the cluster to process the execution of scheduled reports. These dedicated instances will share the same repository but will not be part of the load balancer to serve web requests, such as executing reports through the UI and/or exploring data through ad hoc views.
For standalone deployment where only a single instance of JasperReports server is available, the instance will process report scheduling as well serve normal web requests, such as report execution through the UI and/or exploring data through ad hoc views.
We are providing a mechanism to make dedicated JasperReports server instances as scheduler instances, and the instances that are part of the load balancer to serve web requests as non-scheduler instances.
During installation of Jaspersoft 7.1 (or 6.4.2) for CA PPM you are prompted about a separate scheduler instance:
  • If you answer YES, you are prompted to decide if you want to make the current instance on which the installer is being applied a scheduler instance.
    • If YES, the installer performs the necessary configuration changes to make the current instance a scheduler instance.
    • If NO, the installer performs the necessary configuration changes to make the current instance a non-scheduler instance. To get full advantage of this configuration, ensure the non-scheduler instances are part of the load balancer.
The user must select the appropriate option during installation to make the said instance a scheduler or a non-scheduler instance.
If running only a single instance of JasperReports server, then select 'no' when being prompted on separating the scheduler instance as a dedicated instance.
PREREQUISITES
------------------------------------------------
- Set the JAVA_HOME environment variable and ensure the correct Java8 executable is present in the PATH environment variable.
- Create a new Jaspersoft Database/Schema before starting the installation and upgrade.
For Upgrades:
- Export the Jaspersoft content to a zip file (exported from Jaspersoft UI only).
- Take a backup of the existing Jaspersoft instance (the Webapp) and database (Database/Schema).
INSTALLATION/UPGRADE
------------------------------------------------
1. Download the installer from the CA Download Center. Unzip ca_ppm_jaspersoft_<Jaspersoft Version>_<CA PPM Jaspersoft Version>.zip to a folder. For example, ca_ppm_jaspersoft_7.1.0_6.1.0.28.zip or ca_ppm_jaspersoft_6.4.2_5.4.2.15.zip. Unzip the installer in the root directory to avoid a long path exception.
2. Run the installer:
a) If on Windows:
Run install.bat
b) If on Linux:
Run chmod u+x install.sh
Run install.sh
------------------------------------------------
Select Installation Type:
1) 
New
: This installs Jaspersoft as a brand new installation
2) 
Upgrade
: This upgrades the existing Jaspersoft installation
Enter Apache Tomcat 8.5 Directory: Location on the machine where Tomcat is installed
Enter Jaspersoft Web App Name: The name of the folder where Jaspersoft is being deployed (for example, reportservice).
Enter Jaspersoft Web App Port: The JasperReports server port. The default is 8080.
 
Email configuration
1) Y: To setup email configuration
a) Enter Mail Server Hostname: Hostname of the mailserver (for example, mail.localhost.com).
b) Enter Mail Server Port: Port number of mailserver (for example, 25).
c) Enter Sender Email Protocol: Protocol that mail server supports. Jaspersoft currently supports smtp and smtps.
d) Enter Sender Email Username: Username of the Mail Sender (for example, test).
e) Enter Sender Email Password: Password of the Mail Sender (for example, password123).
f) Enter Sender Email Address: Sender Mail Address (for example, [email protected]).
2) N: To skip email configuration
 
Select the Installation Mode
1) Standalone: For standalone servers
2) Cluster: For cluster-based deployments
If you selected cluster mode:
1) Primary Node: Same as standalone installation
2) Additional Node (Web-app deploy only): Just deploys the web app only and uses primary node database/schema
Do you need a dedicated Jaspersoft instance as a report scheduler instance?
1) Yes: Choose this option if you want to have a separate scheduler instance.
2) No: Choose this option if you do not want a separate scheduler instance.
If Yes is selected in the previous step: Do you want to make the current instance as a report-scheduler-only instance?
1) Yes: Choose this option to have the installer perform the necessary configuration changes and make the current instance a scheduler instance.
2) No: Choose this option for instances that are part of the load balancer. The installer performs the necessary configuration changes and makes the current instance a non-scheduler instance.
Select DB Server type:
1) MSSQL
2) Oracle
If MSSQL is selected:
MSSQL Server Hostname: Enter MSSQL server hostname (E.g.: HOSTNAME)
Do you want to use a named instance?
a) Yes: Choose this if you are using a MSSQL server named instance for the Jaspersoft installation.
b) No: Choose this if you are using a default MSSQL server with a static port number.
If Yes is selected: 
  • Enter the MSSQL Server Instance Name: The named instance configured on the MSSQL server
  • Enter the Jaspersoft Database Name: Jaspersoft database name - default: PPM_JASPERSOFT
  • Enter the Jaspersoft Database Username: Jaspersoft Username - e.g.: PPM_JASPERSOFT
  • Enter the Jaspersoft Database Password: Jaspersoft Password 
If No is selected:
  • Enter the MSSQL Server Port Number: Database port on which MSSQL server is running - E.g.: 1433
  • Enter the Jaspersoft Database Name: Jaspersoft database name - default: PPM_JASPERSOFT
  • Enter the Jaspersoft Database Username: Jaspersoft Username - E.g.: PPM_JASPERSOFT
  • Enter the Jaspersoft Database Password: Jaspersoft Password
If Oracle is selected
1) Oracle Standalone
2) Oracle Cluster (RAC)
If Oracle Standalone is selected:
a) Enter the Oracle Database Hostname: The Oracle server hostname - E.g.: HOSTNAME
b) Enter the Oracle Database Port Number: Database port on which oracle is running - E.g.: 1521
c) Enter the Jaspersoft Database Username: Jaspersoft database - E.g.: PPM_JASPERSOFT
d) Enter the Jaspersoft Database Password: Jaspersoft password
e) Enter the Oracle SID Name: Oracle SID - E.g.: <ORACLESID>
If Oracle Cluster (RAC) is selected:
a) Enter the Oracle Database Hostname (the Oracle server hostname; for example, HOSTNAME).
b) Enter the Oracle Database Port Number (for example, 1521).
c) Enter the Jaspersoft Database Username (for example, PPM_JASPERSOFT).
d) Enter the Jaspersoft Database Password.
e) Enter the Oracle Service Name (for example, SERVICENAME).
3. Confirm the properties that you entered and wait until the installation completes.
4. After the Tomcat service starts, log in to 
http://<MACHINE_NAME>:<PORT>/<JASPERSOFT_WEB_APP_NAME>
 using the credentials 
superuser/superuser
.
For example:
NOTE: During the installation, the license file is copied to the installation directory and user folder automatically.
 
Jaspersoft Upgrade Tips
:
  • For best results, always clear the browser cache on each client workstation after installing, upgrading, or patching Jaspersoft.
  • The Create and Update Jaspersoft Users job Full Sync option deletes all user folders with no content.
  • Create a small amount of custom Jaspersoft folders for each team. For example, only for PPM admins, project managers, and a few business analysts.
  • If this is not convenient, create users in PPM and place a small file inside each folder to avoid it from being deleted.
  • For better performance, do not create more than 500 user folders.