Clarity
and Jaspersoft Cumulative Patch README Files

ccppmop1591
HID_clarity_readme
Cumulative patches for
Clarity
and Jaspersoft for
Clarity
are periodically available. Before applying a patch, see the README for important information.
Although they are technically not patches, we list the Jaspersoft installers for
Clarity
on this page because they behave like patches for existing
Clarity
customers with Advanced Reporting environments.
  • SaaS Customers:
    Contact Support to request and schedule patch installation on specific
    Clarity
    instances in the On-Demand Portal. Any fixes for reports are automatically deployed in your SaaS environment. Notifications for scheduled mandatory Jaspersoft patches are provided by email to the customer support contacts on file.
  • On-premise Customers:
    To install a patch or update reporting content, download the patch from Support and follow the README instructions on this page.
This section contains the following topics:
2
Clarity
Cumulative Patch Summary
As patches are cumulative in nature, when you install a single patch, it includes all the fixes in all previous patches, keeping you up-to-date. The following table lists the patches that are released so far:
Clarity
Base Release
15.3
15.4.0
15.4.1
15.5.0
15.5.1
15.6.0
15.6.1
15.7.0
15.7.1
15.8.0
15.8.1
Latest Patch:
15.3.0.5
15.4.0.1
15.4.1.4
15.5.0.1
15.5.1.3
15.6.0.1
15.6.1.3
15.7.0.1
15.7.1.3
15.8.0.1
15.8.1.1
JasperReports
6.4.2_5.4.2.15
or
7.1.0.6.1.0.X
6.4.2_5.4.2.15
or
7.1.0.6.1.0.X
6.4.2_5.4.2.15
or
7.1.0.6.1.0.X
6.4.2_5.4.2.15
or
7.1.0.6.1.0.X
7.1.0.6.1.0.X
7.1.0.6.1.0.X
7.1.0.6.1.0.X
7.1.0.6.1.0.X
7.1.0.6.1.0.x
7.1.0.6.1.0.X
Clarity PPM has now been rebranded as Clarity. You can see the new Clarity logo on the login screen and in the New User Experience. The documentation is updated to reflect the new brand. Clarity refers to the New User Experience, and Classic PPM refers to the Classic PPM Studio.
Issues Fixed in 15.8.1.1
DE55928- Incorrect URL in Jaspersoft reporting
Steps to reproduce:
  1. Log in to Classic PPM and Navigate to Advance Reporting.
  2. Pick any Report, schedule, and Run now.
  3. In the Notification select Include reports as repository links in email body.
Actual Result: The link contains encoded URL which points to the Admin Server URL.
Expected Result: The embedded link which you get in email should be routed to app node URL 
DE56590 - Job parameters are not passed to the jobs that have started from Object Actions
Steps to reproduce:
  1. Create a simple process - Start, Finish. The process does not have to do anything.
  2. Create a custom Job definition based on the "com.niku.bpm.jobs.ExecuteProcessJob:
  3. Give a parameter called param_process_code that has a default value of the code of the simple process created in step 1.
  4. Create a custom object.
  5. Create a new job that is based on Action that calls the new custom job that is created in step 2. Ensure that the job is instance specific.
  6. Place the Action on the General Action Menu of the Object's Property page.
  7. Create an instance of the custom object. On the property page of the object use the Actions drop-down to call the Job.
Expected Result: The job executes and calls the process.
Actual Result: The job fails.
DE56344 - Project - Project Dashboard tab takes longer time to load
Steps to reproduce:
  1. Click and open any project.
  2. Navigate to the Dasboard tab.
Expected Result: Able to navigate to Dashboard Tab and all portlets load in the dashboard.
Actual Result: After clicking it takes time to load portlets in the Dashboard Tab.
DE56244 : PPA_WIP month_begin values are not correct for months with 30 calendar days (GCP environment)
Steps to reproduce:
  1. Create a project.
  2. Financially enable the project.
  3. Add a team member that is financially enabled.
  4. Navigate to Home, Financial Management, Transaction Entry.
  5. Create the following transactions for that team member or project:
    • Transaction 1: Transaction Date = 01-May-2020
    • Transaction 2: Transaction Date = 01-June-2020
  6. Run Post Transactions and Post to WIP jobs.
  7. Check the PPA_WIP table and note the month_begin column.
Expected results: Transaction in May is correct. Month_begin is 2020-05-01 00:00:00.0 / Transaction in June to be 2020-06-01 00:00:00.0
Actual results: Transaction in May is correct. Month_begin is 2020-05-01 00:00:00.0 / Transaction in June is incorrect, being 2020-05-31 00:00:00.0
DE55876 - Timesheet filter using Type=Labor together with an OBS filter generates a System Error 500
Steps to Reproduce:
  1. In Classic PPM go to Home, Timesheets.
  2. In the filter select type=Labor.
  3. Select an OBS to filter by.
  4. Click Filter.
Expected: Results The filter is applied and the applicable results are displayed.
Actual: System Error 50
DE56341 - Query Dependent Lookup Values on the custom object module list page does not preserve the value
Steps to Reproduce:
  1. Log in to Classic PPM and Navigate to Administration, Object.
  2. Create a sub object of Project and name it as aaa (example: AAA).
  3. Create a Dynamic Query lookup called Lookup with the following code:
    select @SELECT:cc.code:[email protected], @SELECT:cc.name:[email protected] from odf_ca_aaa cc where @[email protected] and (cc.odf_parent_id = @WHERE:PARAM:USER_DEF:INTEGER:[email protected])
  4. Create a lookup attribute using the above created dynamic lookup.
  5. Save the attribute and now set the Lookup Parameter Mapping to --Object ID--.
  6. Now Navigate to Modern UX and add the AAA object as a module in your blueprint.
  7. Navigate to AAA module list page and add the attribute Lookup Attribute.
  8. Create an instance of Dependency and fill it value for Lookup Attribute.
  9. Refresh the browser and now the Lookup Attribute value doesn't appear, however in the details layout the value remains.
Expected Results: The value of lookup attribute (Lookup Attribute) should be shown on the list page.
Actual Results: The value of lookup attribute (Lookup Attribute) disappears.
DE55738 - Calculated attribute with DateDiff doesn't work properly in PostgreSQL
Steps to Reproduce:
  1. Using Classic PPM, add the following calculated attribute called:
    "% Schedule Gap" (DateDiff(schedule_finish,baseline_finish,"Day")/+DateDiff(baseline_finish,baseline_start,"Day"))*100
  2. Add the field to the view: "Project Summary::projectGeneral".
  3. Review a project that has the following fields populated:
    • Property Label
    • % Schedule Gap
    • Baseline Start
    • Baseline Finish
    • Finish Date
  4. Review the "% Schedule Gap" field.  The calculation is incorrect.
Expected Results: Calculated attribute using DateDiff report is correct calculation.
Actual Results: Calculated attribute using DateDiff shows "0" or some other incorrect value.
DE50348 - Patch 15.8.1.1: Synchronize Agile Central job is failing in Production
Steps to Reproduce:
  1. Log in to Classic PPM.
    1. Configure Agile Central to Clarity integration.
    2. Create a project and enable Agile Central integration.
  2. Log in to Rally.
    1. Create more than 2000 resources.
    2. Create different user stories and tasks and assign different owners (created from step 2a).
  3. In Classic PPM, run the Synchronize Agile Central job.
Expected Results: Project and tasks are synchronized and the Synchronize Agile Central job is executed successfully.
Actual Results: For some projects, the job fails with the following error in logs:
java.io.IOException: HTTP/1.1 524 Origin Time-out For those projects, the Synchronized checkbox gets unchecked as there are exceptions processing the request.
DE55120 - Patch 15.8.1.1: Rally sync error API-1019 post upgrade to 15.7.1 for some projects
Steps to Reproduce:
  1. Log in to Classic PPM.
    1. Configure Agile Central to Clarity integration.
    2. Create a project and enable Agile Central integration.
  2. Log in to Rally.
    1. Create more than 2000 milestones.
  3. In Classic PPM, run the Synchronize Agile Central job.
Expected Results: Project and tasks sync successfully and the Synchronize Agile Central job is executed successfully.
Actual Results: For some projects, the job fails with the following error: There was a problem syncing tasks for the CA PPM project: <Project Name>500api.internalErrorAPI-1019 : Could not process the request due to internal error.
DE56197 - OBS filtering on Custom Object is not working
SUMMARY: Unable to filter  OBS unit on Customer Objects
Steps to reproduce:
  1. Log in to Classic PPM as Administrator.
  2. Create a customer master object (example: Suman Custom Object) and API enable the object.
  3. Either create an OBS or use an existing OBS and associate the object created (example: Suman Custom Object).
  4. Once the OBS association is done, you can enable the API Attribute in order to see even in Clarity.
  5. Go to the Custom object Menu from Classic PPM and create couple of instance for the object created and update the OBS unit.
  6. Configure the Custom Object List Page to add OBS Unit in filter and list section.
  7. On the filter section select an OBS Unit and filter.
Expected Results: The list page should fetch the result based on the OBS UNIT match.
Actual Results: The list page does not show any records even when filter value matches.
Workaround: Log in to Clarity and filter the OBS unit and it shows the correct value.
DE56615 - Process Start Instance Right is not checked properly resulting in the user being unable to start a process if they just have that instance right
Steps to reproduce:
  1. Create a simple process on a sub-object of the project object. Status Report is a good one to use.
  2. Add an Action for this process to the sub-object.
  3. Add the action to the General Action menu of the sub-object's list page.
  4. Create a new user and grant the following rights:
    1. Give the following Global rights:
      • Project Navigate
      • Project Management Navigate
      • Project Tiles Navigate
      • Tasks Navigate
      • Account Navigate
      • Knowledge Base Access
    2. Give the following Instance rights:
      • Process Start on the process created
      • Project EditManagement on a few projects
      • Edit All Status Reports (or whatever sub-object you created the process on)
      • Create Status Report (or whatever sub-object you create the process one)
  5. Log in as the new user.
  6. Go to a project you can access.
  7. Create an instance of the sub-object.
  8. Go to the list page.
  9. Select that instance and Click Actions and select the process you create to start it.
Expected Results: A pop-up displays telling you the process is initiated.
Actual Results: A pop-up displays telling you there was a problem initiating the process and to contact the administrator.
DE55962 - Rally Timesheet Integration: Unable to get to My Timesheet when accessing Clarity timesheet from the integration.html used by Rally
Steps To Reproduce:
  1. Access the following URL:
    http://host:port/pm/integration.html#
    This is the URL for the timesheet integration that Rally will use.
  2. In non-SSO enter your credentials on the login page and click Login.
Expected Results: My timesheet page shows up with the current periods timesheet displayed.
Actual Results: A couple of toaster messages appear: API-1006: The value 'undefined' for Attribute 'resourceId' is not in expected format or is invalid. In addition, an error is written to the Javascript console.
In the SSO environment the message "My Timesheet is not configured for Clarity" is displayed.
DE55963 - PPMSSO: Rally-Timesheet integration doesn't set RelayState properly to take user to their Timesheet after logging into their IDP
Steps to Reproduce:
  1. Set up Clarity for SSO.
  2. Use a Federated SSO IDP and configure Clarity to redirect through avagoext.okta.com to that IDP when needed.
  3. Open a new Incognito Window in Clarity.
  4. Enter the URL to the Clarity system with
    /pm/integration.html#
    as the path.
Expected Result: After signing in to the Federated SSO IDP the user is redirected to
/pm/integration.html#
and their current timesheet is displayed.
Actual Result: After signing in to the Federated SSO IDP the user is redirected to the RelayState set in the errorUrl of the Clarity properties.xml file.
DE54074 - MVL Attributes with same underlying lookup cause the DWH Full & Incremental Load to Fail when they both are included for Datawarehouse.
Steps to Reproduce:
  1. Log in To Classic PPM.
  2. Navigate to Administration, Data Administration, Lookups.
  3. Create a Dynamic lookup.
  4. Under Parent Windows select the Hidden key as "user_name" and Display Attribute as "full_name".
  5. Navigate to Administration, Studio, Objects.
  6. Search for Project Object.
  7. Click on Project Object and navigate to Attributes.
  8. Create an Attribute of Type Multi Value Lookup with the lookup created on Step 3 and include it in Datawarehouse.
  9. Create another attribute of Type Multi Value Lookup with the lookup created on Step 3 and include it in Datawarehouse.
  10. Add both the attributes to Project - Edit views.
  11. Select the value of 'admin' for both the attributes for a single project.
  12. Run the Load Datawarehouse Job - Full Load.
Expected Results: Full Load or Incremental Load Complete Successfully.
Actual Results:Full Load fails and Incremental both fail with the following error message: DWH_CMN_MV_LOOKUP ORA-01427: single-row subquery returns more than one row
DE54888 - New UX - Filtering on Project Grid reverts back to original results
Steps to reproduce:
  1. Connect to a large customer dataset (see environmental details below).
  2. Go to Projects - Grid
  3. Note the number of projects there.
  4. Now quickly add a filter, i.e. Active =Yes.
  5. Note the amount of projects changing down.
  6. Within 5 seconds, note the amount of projects reverting to initial number.
Expected Results: The filter results to stay as they are.
Actual Results: Results are reverted to the original filter.
Workaround: None.
Enhancements added: #12345 - Description of enhancement for customer
Schema changes: PostgreSQL function CMN_DATE_TIME_DIFF_FCT
Reporting changes: none
XOG API changes: none
Patches are intended to be timely fixes and are not fully regression or integration tested, and are only tested against the issues listed below. We feel confident that this patch will resolve the defects targeted in this patch, but a patch could have adverse side effects to the function of your
Clarity
application. Do 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 Support.
Files Included In the Patch
  • README.txt
  • install.sh - Unix installer
  • install.bat - Windows installer
  • install.xml - Ant install script
Prerequisites
Install only on systems running the version stated above.
Install the Patch
Follow these steps:
  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. Run the following command to stop all local nsa, app and bg services: service stop nsa app bg
  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. Run the following command to 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.
    4. 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:
    2. admin jaspersoft keystore
    3. Copy the keystore files generated in the path - <install_dir>/config directory to <Jaspersoft Tomcat Instance Directory>/webapps/<jaspersoftContext>/WEB-INF/config
    4. Enter the following command to upgrade the report content:
    5. admin content-jaspersoft csk -userName <superuser> -password <password> upgrade -retryCount 50
    6. Restart all
      Clarity
      services.
    7. 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:
    2. admin jaspersoft keystore
    3. Copy the keystore files generated in <install_dir>/config directory to <Jaspersoft Tomcat Instance Directory>/webapps/<jaspersoftContext>/WEB-INF/config
    4. 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).
    5. 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
    6. Configure the Data Warehouse section in CSA. See CSA: CA PPM System Administration at docops.ca.com/ppmop.
    7. Enter the following command from the <install_dir>/bin directory command prompt to apply the data warehouse patch content:
      1. admin db dwh-upgrade -Dupgrade.phase=maintenance
      2. Restart all PPM services.
      3. Run the Load Data Warehouse Access Rights job.
Uninstall the Patch
Follow these steps:
  1. Run the following command to 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. Run the following command to start all services: service start all
  4. If you are running multiple servers in a cluster, log in to CSA and go to the All Services page to shut down any remote app and bg services.
  5. Go to the Distribute All page, select remote servers and click Distribute.
  6. Return to the All Services page to restart services when the distribution is complete.
JasperReports Server 7.1 for
Clarity
README (Recommended Version)
JasperReports Server 7.1 is the newest release that includes new features, enhancements, and security updates. All
Clarity
SaaS customers automatically receive this new release.
Clarity
on-premise customers must use the
Clarity
Jaspersoft installer to apply it. The installer is a customized wrapper written on top of the original third-party installer.
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
    Clarity
    Release Notes and TIBCO Documentation.
  • Clarity
    SaaS customers enjoy an automatic upgrade to JasperReports 7.1.
  • Clarity
    15.7 on-premise customers must download the
    Clarity
    Jaspersoft 7.1 installer, which is a customized wrapper written on top of the original third-party installer. Only the installer can be used to install Jaspersoft and integrate it with
    PPM classique
    for reporting.
Express Install Steps for JasperReports Server 7.1
Only the installer can be used to install Jaspersoft and integrate it with
Clarity
for reporting. Do not install software, download patches, or apply hotfixes 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 to 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.
Your upgrade to 7.1 might require you to first update to 6.4.2. For example, you have 15.1 with Jaspersoft 6.2.1. When you upgrade to 15.6, your reporting environment remains at 6.2.1. Upgrade to 6.4.2 first and then upgrade to 7.1.
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 the installation of Jaspersoft 7.1 for
Clarity
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.
Select the appropriate option during installation to make the said instance a scheduler or a non-scheduler instance. If you are running only a single instance of JasperReports server, then select
no
when you are prompted to separate 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 and Upgrade
  1. Download the installer from the Download Center.
  2. 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.
  3. Unzip the installer in the root directory to avoid a long path exception.
  4. Run the installer file:
    • Windows
      - Run install.bat
    • Linux
      - Run chmod u+x install.shRun install.sh
  5. Select Installation Type:
    • New
      - This installs Jaspersoft as a brand new installation.
    • Upgrade
      - This upgrades the existing Jaspersoft installation.
  6. Enter Apache Tomcat 8.5 Directory: Location on the machine where Tomcat is installed.
  7. Enter Jaspersoft Web App Name: The name of the folder where Jaspersoft is being deployed (for example, reportservice).
  8. Enter Jaspersoft Web App Port: The JasperReports server port. The default is 8080.
  9. Configure Email:
    1. Select
      Y
      to setup email configuration
      1. Enter Mail Server Hostname: Hostname of the mailserver (for example, mail.localhost.com).
      2. Enter Mail Server Port: Port number of mailserver (for example, 25).
      3. Enter Sender Email Protocol: Protocol that mail server supports. Jaspersoft currently supports SMTP and SMTPS.
      4. Enter Sender Email Username: Username of the Mail Sender (for example, test).
      5. Enter Sender Email Password: Password of the Mail Sender (for example, password123).
      6. Enter Sender Email Address: Sender Mail Address (for example, [email protected]).
    2. Select
      N
      to skip email configuration
  10. Select the Installation Mode:
    • Standalone: For standalone servers
    • Cluster: For cluster-based deployments
    • If you selected cluster mode
      • Primary Node: Same as a standalone installation
      • Additional Node (Web-app deploy only): Just deploys the web app only and uses primary node database/schema
  11. Do you need a dedicated Jaspersoft instance as a report scheduler instance?
    • Yes: Choose this option if you want to have a separate scheduler instance.
    • No: Choose this option if you do not want a separate scheduler instance
  12. If you have selected Yes in the previous step: Do you want to make the current instance as a report-scheduler-only instance?
    • Yes: Choose this option to have the installer perform the necessary configuration changes and make the current instance a scheduler instance.
    • 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.
  13. Select DB Server type
    • MSSQL
    • Oracle
    MSSQL
    1. MSSQL Server Hostname: Enter MSSQL server hostname (E.g.: HOSTNAME)
    2. Do you want to use a named instance?
    • Yes: Choose this if you are using a MSSQL server named instance for the Jaspersoft installation.
    • No: Choose this if you are using a default MSSQL server with a static port number.
    • Yes
      • 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
    • No
      • 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
    Oracle
    • Oracle Standalone
    • Oracle Cluster (RAC)
    Oracle Standalone
    1. Enter the Oracle Database Hostname: The Oracle server hostname - E.g.: HOSTNAME
    2. Enter the Oracle Database Port Number: Database port on which oracle is running - E.g.: 1521
    3. Enter the Jaspersoft Database Username: Jaspersoft database - E.g.: PPM_JASPERSOFT
    4. Enter the Jaspersoft Database Password: Jaspersoft password
    5. Enter the Oracle SID Name: Oracle SID - E.g.: <ORACLESID>
    Oracle Cluster (RAC)
    1. Enter the Oracle Database Hostname (the Oracle server hostname; for example, HOSTNAME).
    2. Enter the Oracle Database Port Number (for example, 1521).
    3. Enter the Jaspersoft Database Username (for example, PPM_JASPERSOFT).
    4. Enter the Jaspersoft Database Password.
    5. Enter the Oracle Service Name (for example, SERVICENAME).
    1. Confirm the properties that you entered and wait until the installation completes.
  14. 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
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
    Clarity
    administrators, project managers, and a few business analysts.
  • If this is not convenient, create users in
    Clarity
    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.