CA PPM 14.3 and Jaspersoft Patches

Are you looking for patches to  Release 14.3 and Jaspersoft? You have come to the right place.
ccppmop143
Are you looking for patches to 
Clarity Project and Portfolio Management (PPM)
 Release 14.3 and Jaspersoft? You have come to the right place.
2
For more information about patches, review the following items:
  • Defect Resolution Policy: Includes procedures that describe how customer-reported defects are resolved and important information about patches.
  • Product Release and Support Announcements: Announcements for all 
    Clarity Project and Portfolio Management (PPM)
     releases and cumulative patches, and Jaspersoft cumulative patches.
 
SaaS customers can contact CA Support to request patch installation.
CA PPM Release 14.3 Patch
The following table contains the latest 
Clarity Project and Portfolio Management (PPM)
 14.3 cumulative patch.
Patch
Date
Highlights
Announcement
Readme
Download
CA PPM 14.3 Cumulative Patch 10 (14.3.0.10)
 
Jan 19, 2017
This cumulative patch contains updates and fixes for all previous 14.3 patches.
CA PPM 14.3 Cumulative Patch 10 (14.3.0.10)
  • CLRT-81728: Require Application Add-ins to be signed by Trusted Publisher' is checked in MSP; receive error: "SignatureDescription could not be created for the signature algorithm supplied"
  • CLRT-81533: Securability Fix
  • CLRT-81494: Long hyphen is removed in MSP
  • CLRT-81067: Japanese characters are garbled, when a domain is created with Japanese characters
  • CLRT-80987: Exceptions in the parent calendar are not shown in parent calendar of the MS Project interface
  • CLRT-81346: MSP - Project does not save back into CA PPM from MSP
  • CLRT-81011: Load Data Warehouse job fails with database lock ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
  • CLRT-81083: 'Financial Budget vs. Forecast by Period Detail' report only returns data for Project Investments
  • CLRT-81445: Project Storyboard Report shows Equipment Actual Qty in Labor Hours
  • CLRT-80019: Project Storyboard (Jaspersoft) report has incorrect data for some metrics in Labor Hours and Financial Performance sections
  • CLRT-80173: Error 500 for attributes with the Multi Valued Lookup type in Idea
CA PPM 14.3 Cumulative Patch 9 (14.3.0.9)
  • CLRT-81414 and CLRT-81298: Security fixes
  • CLRT-81236: Posting actuals after the task start date is not distributing the remaining work properly
  • CLRT-80227: A required multi-valued lookup with a numeric key and a parameter results in a system error when no value is selected
  • CLRT-80253: New security model for the Data Warehouse
  • CLRT-79381: The Project Storyboard Jaspersoft report doubles up planned benefit when there is more than one line item in the benefit plan
  • CLRT-80451: Ad Hoc Reporting does not show all financial data when using grouping.
  • More updates and fixes. See the Readme for more information.
CA PPM 14.3 Cumulative Patch 8 (14.3.0.8)
  • CLRT-79254: Jaspersoft Report (Resource Time Review by Manager) days of week are incorrectly labeled.
  • CLRT-80334: Input type code set on Timesheet page of a resource gets set to a blank value when Timesheet is adjusted and subsequently gets submitted.
  • CLRT-80837: Securability fix.
  • CLRT-79816: The Capacity vs Allocation by OBS report does not include Unstaffed Roles even when the 'Include Unstaffed Roles' check box is checked on the filter parameters.
  • Additional updates and fixes.
CA PPM 14.3 Cumulative Patch 7 (14.3.0.7)
  • CLRT-80110: Jaspersoft: Remove empty user folders as part of Create and update Jasper Users.
  • CLRT-80217: PRESTSUM calculated wrong in Task assignment.
  • CLRT-80230: SKIP Level argument in XOG ignores the custom information.
  • CLRT-79316: DWH: Calendar changes cause Capacity reporting hours to go missing.
  • CLRT-80008: Resource Allocations and Assignments report - 'Assignments' row is not exported to Excel for some or all investments.
  • Additional updates and fixes.
CA PPM 14.3 Cumulative Patch 6 (14.3.0.6)
  • CLRT-78953: Performance issue - Project/Idea properties page taking more time.
  • CLRT-77362: MSSQL: Instance rights query runs for too long and does not return any data, causing DWH_INV_SECURITY_V to return 0 rows.
  • Additional updates and fixes.
CA PPM 14.3 Patch 5 (14.3.0.5)
  • CLRT-79475: Some uppercase characters cause Resource Name to appear blank in MSP.
  • CLRT-79927: App service cannot be reached, Could not retrieve a valid tenant message thrown in logs.
  • CLRT-78878: Users cannot navigate back to CA PPM correctly from Jaspersoft reports by clicking on hyperlinks in the report.
  • .Additional updates and fixes.
CA PPM 14.3 Patch 4 (14.3.0.4)
  • CLRT-79397: "SSL is used but processed externally" setting in the NSA breaks the ability to run a report in Advanced Reporting.
CA PPM 14.3 Patch 3 (14.3.0.3)
  • CLRT-78908: Inconsistent Y Axis of Chart Portlet when a minimum and maximum value of the Y axis is set.
  • CLRT-79496: Updating start and/or finish date of proxy task does not update the parent start and/or finish date(s).
  • CLRT-79214: Performance with Jaspersoft against large data set.
  • Additional updates and fixes.
CA PPM 14.3 Patch 2 (14.3.0.2)
  • CLRT-79149: Adjust Button Not available in the timesheet when the project is closed for time entry.
  • CLRT-77207: OWB - Auto schedule ignores the resource availability when using priorities.
  • Additional updates and fixes.
CA PPM 14.3 Patch 1 (14.3.0.1)
  • CLRT-78948: Department Resource Filter: Error 500 - Internal Server Error. The server could not retrieve the document due to server-configuration or other technical problems. Contact your site administrator.
  • CLRT-79064: Firefox javascript error when filtering tasks under "Add task" in a Timesheet.
  • Additional updates and fixes.
Minimum Jaspersoft Patch for 
Clarity Project and Portfolio Management (PPM)
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 is the minimum supported Jaspersoft cumulative patch through June 28, 2018. Customers are encouraged to upgrade to JasperReports Server 6.4.2 for CA PPM available in March 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.
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 Project and Portfolio Management (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 THIS 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 THIS PATCH:
-----------------------
1. Stop the application server (Apache Tomcat Server), on which JRS is deployed.
2. Find the root web application folder (for example, 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 Expiration Date
This license file is also bundled along with patch zip artifact (<patch-unzipped-folder>\resources\license\jasperserver.license). After applying the patch, the expected behavior is that the expiration date should change on the server. However, if the expiration date is still not changed on the server, replace the jasperserver.license file in the file-system with the license file provided in this patch.
TIBCO Security Updates for CSRF, XXS, XXE, and Related Vulnerabilities
TIBCO has identified CSRF, XXS, XXE, and related security vulnerabilities in JasperReports Server 6.2.1 and has provided fixes in JasperReports Server 6.3.2. Fixes for these security vulnerabilities have been backported to JasperReports 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: Both the above points does not apply for tenants that are getting migrated.
DE30205: Full project list not displayed in Adhoc view if static lookup from project sub object is added as a field to be displayed
Steps to Reproduce:
1. Create a Project sub object. 
2. Add an attribute to the sub object that uses a static lookup. 
3. Add the sub object to data warehouse by selecting the 'Include the sub object in Data Warehouse' checkbox. 
4. In both the Create and Edit view of the sub object General page add the static lookup attribute created in step two. 
5. Create an instance of the sub object 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 get displayed. 
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 sub object 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 sub object 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
JasperReports Server 6.4.2 is a maintenance release that includes security updates and improvements requested by customers. CA PPM 14.3 and higher on-premise customers must 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.
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
 
 
HARDWARE AND SOFTWARE REQUIREMENTS
------------------------------------------------
See the CA PPM Release Notes and TIBCO Documentation.
 
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 the CA PMM Jaspersoft 6.4.2_5.4.2, user will be prompted whether the user is opting for a separate scheduler instance.
  • If the answer is 'yes', then the user will be prompted about whether the user is willing to make the current instance on which the installer is being applied a scheduler instance.
    • If the answer is 'yes', the installer will perform the necessary configuration changes to make the current instance a scheduler instance.
    • If the answer is 'no', the installer will perform 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.
Note that 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_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 7 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 (for example, 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 (for example, <ORACLESID>).
If Oracle Cluster (RAC) 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 Service Name : Oracle SERVICENAME - E.g.: <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>. For example, http://jaspersoftserver:8080/reportservice/ using the credentials superuser/superuser.