Install and Configure Advanced Reporting with Jaspersoft

Complete the following steps to set up Advanced Reporting with Jaspersoft. Also, configure Jaspersoft to restrict email notifications to trusted domains and set up a dedicated JasperReports server for scheduled reports.
ccppmop142
Complete the following steps to set up Advanced Reporting with Jaspersoft. Also, configure Jaspersoft to restrict email notifications to trusted domains and set up a dedicated JasperReports server for scheduled reports.
Pre-Installation Steps
Before you start the installation, complete the following steps:
Review the Prerequisites
Consider the following information before you install Jaspersoft:
  • Verify that CA PPM is installed or upgraded. For more information, see 
    Installing and Upgrading
    .
  • Verify that the correct version of Java is installed.
  • Verify that the JAVA_HOME variable is set and the PATH environment variable contains the JAVA_HOME\bin location.
  • Verify that the correct version of Tomcat is installed.
  • Create the Jaspersoft schema and set the permissions.
For information about the correct versions, see the 
Clarity Project and Portfolio Management (PPM)
 Release Notes
.
Recommendations
For a successful installation, consider the following recommendations:
Pre-Installation
  • If Tomcat is already installed with no web applications deployed, then use the existing Tomcat. If any other web application is running under Tomcat, then use a fresh Tomcat to install Jaspersoft.
  • Before you run install.bat or install.sh, verify that the correct JAVA_HOME variable and PATH is set.
Post Installation
  • Tomcat provides scripts to run Tomcat as a service. Use those scripts to install the Tomcat service. Before you install the service, verify that the correct JAVA_HOME variable and PATH is set.
  • If you use Oracle, run the following query after the Jaspersoft installation to improve the overall performance of the system.
    exec DBMS_STATS.GATHER_SCHEMA_STATS (ownname => USER, degree => DBMS_STATS.AUTO_DEGREE, estimate_percent => 100, cascade => true, method_opt=> 'FOR ALL COLUMNS SIZE 1');
    We recommend you to run this query frequently.
  • The 
    Output to Host File System
     option saves the report output to a specified folder on the Jasper Reports Server host machine. This option is disabled by default. For information to enable this option, see the Jaspersoft documentation.
  • The governor limit on the Jaspersoft reports database connection has a timeout set to 15 minutes (900000 milliseconds). Report queries running longer than 15 minutes close and an error indicating the timeout is returned to the user. Do not change this setting for better performance and to relieve stress on the database. 
    You can change the setting in the following location:
    webapps/<jasperwebcontext>/WEB-INF/classes/jasperreports.properties
    net.sf.jasperreports.governor.timeout.enabled= true
    net.sf.jasperreports.governor.timeout=900000
  • The governor limit on the Jaspersoft report pages is set to 500. This limit applies to all output formats. You can change this setting in the following location: 
    <tomcatDirectory>/webapps/<jasperwebcontext>/WEB-INF/classes/jasperreport.properties
    net.sf.jasperreports.governor.max.pages.enabled=true 
    net.sf.jasperreports.governor.max.pages=500
    Setting this requires a restart of the Jaspersoft server.
Create the Jaspersoft Schema and Set the Permissions
The following procedures explain how to create the Jaspersoft schema and set the required permissions:
Oracle
Follow these steps:
  1. Create a Tablespace for Jaspersoft.
    CREATE TABLESPACE "PPM_JASPER_TS" DATAFILE '<ORACLE_BASE>\ORADATA\<SID>\PPM_JASPER_TS.DBF' SIZE 500M REUSE AUTOEXTEND ON NEXT 25M MAXSIZE 10G LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
  2. Create a database user and set the required permissions. For example, PPM_JASPERSOFT.
    CREATE USER PPM_JASPERSOFT IDENTIFIED BY PASSWORD123 DEFAULT TABLESPACE PPM_JASPER_TS TEMPORARY TABLESPACE TEMP; GRANT CONNECT TO PPM_JASPERSOFT; GRANT RESOURCE TO PPM_JASPERSOFT; GRANT CREATE SESSION TO PPM_JASPERSOFT;
SQL Server
Follow these steps:
  1. Create a database user. For example, PPM_JASPERSOFT.
  2. Alter database ppm_jaspersoft set arithabort on.
  3. Alter database ppm_jaspersoft set ansi_nulls on. 
  4. Alter database ppm_jaspersoft set quoted_identifier On.
    IF (SELECT (CAST(LEFT(CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR(20)), CHARINDEX('.', CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR(20)), 1) - 1) AS INTEGER))) = 10 BEGIN exec sp_dbcmptlevel 'PPM_JASPERSOFT', @new_cmptlevel=100 END IF (SELECT (CAST(LEFT(CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR(20)), CHARINDEX('.', CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR(20)), 1) - 1) AS INTEGER))) = 11 BEGIN exec sp_dbcmptlevel 'PPM_JASPERSOFT', @new_cmptlevel=110 END IF NOT EXISTS (SELECT 'yes' FROM syslogins WHERE LOWER(name) = LOWER('PPM_JASPERSOFT') ) BEGIN exec sp_addlogin 'PPM_JASPERSOFT','password1234','PPM_JASPERSOFT','us_english' END
  5. Set the isolation level to 
    read committed snapshot
     for SQL Server 2005. 
Make sure that the user can access the system views (syslockinfo, sysindexes...)
begin exec ('alter database PPM_JASPERSOFT set read_committed_snapshot on') exec ('grant VIEW SERVER STATE to PPM_JASPERSOFT') exec ('ALTER LOGIN PPM_JASPERSOFT WITH CHECK_POLICY=OFF') end
USE PPM_JASPERSOFT
Schema owner is referenced in code when executing functions in SQL Server, and is hard-coded to PPM_JASPER. The Login name can differ.
exec sp_grantdbaccess 'PPM_JASPERSOFT','PPM_JASPERSOFT' exec sp_defaultdb 'PPM_JASPERSOFT', 'PPM_JASPERSOFT' exec sp_addrolemember 'db_owner', 'PPM_JASPERSOFT'
Installation and Verification
To install Jaspersoft successfully, complete the following steps:
Install Jaspersoft
Perform the following steps to install Jaspersoft:
Install Jaspersoft in the Jaspersoft Tomcat folder.
Follow these steps:
  1. Complete the following steps to download the Jaspersoft zip file.
    1. Log in to CA Support Online and navigate to the CA Clarity PPM product support page.
    2. Under Quick Access, click Download Center and complete the search information to locate the Jaspersoft zip file: ca_ppm_jaspersoft_5.6.1_4.4.zip.
  2. Save the zip file to a local directory.
  3. Unzip the contents of the file to a new folder. For example: /opt/jasperreports (UNIX) or C:\Jasperreports (Windows).
    Unzip the installer into the root drive to avoid the file name is too long exception. For example, C:\jaspersoft or /fs0/.
  4. Open the command prompt and complete the following steps:
    1. Run the following commands: 
      Linux:
      chmod u+x install.sh 
      install.sh
      Windows:
      install.bat
    2. Select the installation mode.
      • Standalone
        . Installs the Jasper reports server with database. 
      • Cluster
        • Primary Node: Similar to the standalone installation.
        • Additional Node: Deploys the web application only and uses the Primary Node's database.
    3. Select the Database Server Type and provide the information:
      • Oracle - Standalone
        • Enter Oracle DB Hostname
          Specifies the hostname of the Oracle server where the Jaspersoft database is installed (for example, test.ca.com).
        • Enter Oracle DB Port Number
          Specifies the database port on which Oracle is running (for example, 1521).
        • Enter Oracle SID Name
          Specifies the Oracle SID Name (for example, JASPERSOFT)
        • Enter Jaspersoft Db Username
          Specifies the Jaspersoft database user name (for example, PPM_JASPERSOFT).
        • Enter Jaspersoft DB Password
          Specifies the Jaspersoft database user password (for example, password1234).
      • Oracle - Cluster
        • Enter Oracle DB Hostname
          Specifies the hostname of the Oracle server where the Jaspersoft database is installed (for example, test.ca.com).
        • Enter Oracle DB Port Number
          Specifies the database port on which Oracle is running (for example, 1521).
        • Enter Oracle Service Name
          Specifies the Oracle service name (for example, JASPERSOFT).
        • Enter Jaspersoft Db Username
          Specifies the Jaspersoft database user name (for example, PPM_JASPERSOFT).
      • SQL Server
        • Enter sqlserver DB Hostname
          Specifies the hostname of the SQL Server where the Jaspersoft database is installed (for example, test.ca.com).
        • Enter sqlserver DB Port Number
          Specifies the database port on which SQL Server is running (for example, 1433).
        • Enter Jaspersoft DB Name
          Specifies the Jaspersoft database name (for example, JASPERSOFT01).
        • Enter Jaspersoft DB Username
          Specifies the Jaspersoft database user name (for example, PPM_JASPERSOFT).
        • Enter Jaspersoft DB Password
          Specifies the Jaspersoft database user password (for example, password1234).
    4. Enter the Apache Tomcat directory, the location where Jaspersoft is deployed and Tomcat is installed.
    5. Enter the following information:
      • Enter Jaspersoft web app name
        . Specifies the folder name where the Jaspersoft reporting server is deployed. For example, if reportservice is the Jaspersoft web context, then the URL to access the Jaspersoft reports is http://<domain_name>:<portnumber>/reportservice.
      • Enter Jaspersoft web app port
        . Specifies the port on which Jaspersoft runs (for example, 8080).
    6. (Optional) Enter the following information to configure the mail settings: 
      • Do you want to configure Email (y/n)?
        Select Y to configure the mail server.
      • Enter Mail Server Hostname
        Specifies the hostname of the mail server (for example, mail.localhost.com).
      • Enter Mail Server Port
        Specifies the port number of the mail server (for example, 25).
      • Enter Sender Email Protocol
        Specifies the protocol that the mail server supports (for example, exchange). Currently Jaspersoft supports smtp and smtps.
      • Enter Sender Email Username
        Specifies the user name of the mail sender (for example, test).
      • Enter Sender Email Password
        Specifies the password of the mail sender (for example, password123).
      • E
        nter Sender Email Address
        Specifies the mail address of the sender (for example, [email protected]).
  5. Verify the properties you have entered and wait until the installation completes.
Verify the Installation
Complete the following steps to validate if the installation was successful.
Follow these steps:
  1. Start the Jaspersoft reporting server if it has not started.
  2. Open 
    http://<domain_name>:<portnumber>/<jasperwebcontext>/
    .
  3. Check if you are able to open the login page of Jaspersoft.
  4. Log in to the Jaspersoft reporting server using the superuser credentials.
  5. Check install.log for any errors.
    This file is available in the folder where the contents of the Jaspersoft installation file were unzipped.
  6. Stop the Jaspersoft reporting server.
Apply the JasperReports Server Cumulative Patch
Apply the JasperReports Server cumulative patch over a successful JasperReports Server installation. For more information about this patch, including highlights and benefits, installation instructions, and how to download the patch, see CA PPM 14.2 and Jaspersoft Patches
Cumulative Patch Pre-Installation
Follow these steps:
  1. Shut down the Tomcat service (where JasperReports Server is deployed).
  2. Back up the JasperReports Server database schema.
  3. Zip the JasperReports Server webapp folder in the Tomcat webapp folder. When you zip the folder, provide a meaningful name for the zip file, identifying the purpose of the backup. Move the zip file to a different location in the file system (for example,
    /fs0/reportservice-backups
    for UNIX or
    C:\Jasperreports\reportservice-backups
    for Windows).
Cumulative Patch Installation
Follow these steps:
  1. Complete the following steps to download the JasperReports Server cumulative patch zip file.
    1. Log in to CA Support Online and navigate to the CA PPM Product Support Page.
    2. Under Quick Access, click Download Center. Search to locate the 
      ca_ppm_jaspersoft_patch_5.6.1_4.7.0.1.2.3.zip
      file and save the zip file to a local directory.
  2. Unzip the contents of the zip file to a new patch folder (for example,
    /opt/jasperreports/patch
    for UNIX or
    C:\Jasperreports\Patch
    for Windows).
  3. Open a command prompt and complete the following steps:
    1. Go to the bin folder under the folder where you extracted the patch (for example,
      /opt/jasperreports/patch/bin
      for UNIX or
      C:\Jasperreports\Patch\bin
      for Windows).
    2. Provide execute permission to the installation scripts.
                     UNIX/Linux
–Run the following command:
                           [[email protected] bin]#chmod u+x *
                     Windows
–Not applicable
     
4. Run the following commands to start the patch installation in interactive mode.
                    UNIX/Linux
–Run the following command:
                        [[email protected] bin]#sh ./install.sh interactive
                    Windows
–Run the following command:
                        C:\Jasperreports\Patch\bin>install.bat interactive
     5. Enter the requested information.
    • Enter Tomcat Home Directory
      . The location where JasperReports Server is deployed and Tomcat is installed.
    • Enter Jaspersoft Server web-application Name
      . The folder name where the JasperReports Server is deployed. For example, if
      reportservice
      is the JasperReports Server web context, the URL to access the JasperReports Server is 
      http://<domain_name>:<portnumber>/reportservice
      . The default value is “reportservice”. To use the default value, press the Enter key.
    • Select Installation Mode
      .
      The default value is “Standalone”. To use the default value, press the Enter key. The modes include the following options:
      • Standalone for a standalone server or for a primary node in a cluster.
      • Cluster for secondary nodes in a cluster.
    • Do you need a dedicated Jaspersoft instance as a report scheduler instance?
      The default value is “no”. To use the default value, press the Enter key. You can provide the following inputs:
      • ‘Yes’, if the user is willing to go for dedicated scheduler instance.
      • ‘No’, if the user is not willing to go for dedicated scheduler instance. Select this option, when you don’t have a clustered Jaspersoft nodes or if you don’t want to disturb the existing configurations.
    • Do you want to make the current instance as report scheduler only instance?
      The default value is “no”. To use the default value, press the Enter key. You can provide the following inputs:
      • ‘Yes’, then the patch will perform the necessary configuration changes to make the current instance a scheduler instance. 
      • ‘No’, the patch will perform the necessary configuration changes to make the current instance a non-scheduler instance.
Post-Patch Installation
Complete the following actions after installing the JasperReports Server cumulative patch:
  • Remove the JasperReports Server Scheduler node from the load-balancer configuration. So that web users cannot connect to the scheduler node. Hence, making it an isolated instance, whose tasks is to, only run the reports that are scheduled by the web users.
  • Clear the application server (Apache Tomcat Server)
    temp
    directory.
  • Clear the application server (Apache Tomcat Server)
    work
    directory.
  • Start the Apache Tomcat Server where JasperReports Server is deployed.
  • Clear the browser cache on the client.
Verify the JasperReports Server Cumulative Patch Installation
Complete the following steps to verify that the JasperReports Server cumulative patch installation was successful.
Follow these steps:
  1. Start the JasperReports Server, if it is not already started.
  2. Open the following URL:
    http://<domain_name>:<portnumber>/<jasperwebcontext>/
  3. Verify that you can open the JasperReports Server login page.
  4. Log in to the JasperReports Server using valid credentials.
  5. Open the following URL:
    http://<domain_name>:<portnumber>/<jasperwebcontext>/version.htm
  6. Verify the installed patch version:
    CA PPM Jaspersoft Release Patch Version = 4.7.0.1
Post-Installation Steps
After you have successfully installed Jaspersoft, complete the following steps:
Generate the Key Store File
To authenticate 
Clarity Project and Portfolio Management (PPM)
 and Jaspersoft, generate a trusted key store for each organization.
Follow these steps:
  1. Go to <clarity_home>/bin.
  2. Run the following command to generate a key store from the CSA:
    admin jasper keystore
    To specify key and password, enter: 
    admin jasper generate [-key <key> -password <password>]
    These commands generate the following files in <install>/config/ and <install>/META-INF/reporting/store. 
    • <orgname>.jks (key store file)
    • <orgname>.properties (information about the key)
    The available file is used depending on the J2EE server such as IBM WebSphere or Tomcat.
  3. Copy these files from the <clarityinstall\config> folder to the <Tomcat>/webapps/<jasperwebcontext>/WEB-INF/config folder where Jaspersoft is installed. For example, <Tomcat>/webapps/reportservice/WEB-INF/config.
    For clustered environments, copy these files in the same location on each of the nodes in the cluster.
If
Clarity Project and Portfolio Management (PPM)
is deployed on IBM WebSphere, use the following steps:
  1. Generate the key store using IBM JDK.
    • Set JAVA_HOME to IBM JDK.
      Example: SET JAVA_HOME=C:\PROGRA~2\IBM\WebSphere\AppServer\java_1.7_64
    • Run the
      admin jasper keystore
      command.
  2. Copy the generated keystore to the Jaspersoft Tomcat server.
Restart Jaspersoft
Complete the following steps to stop or start Jaspersoft.
Follow these steps:
  1. Navigate to the <tomcathome>/bin directory.
  2. To stop, run one of the following files:
    • shutdown.sh (Linux)
    • shutdown.bat (Windows)
  3. To restart, run one of the following files:
    • startup.sh (Linux)
    • startup.bat (Windows)
The Jaspersoft content cannot be imported without starting the reporting service.
Set Up the Data Warehouse
The Advanced Reporting content that includes out-of-the-box domains uses the Data Warehouse. After installing and configuring the Jaspersoft reporting server, run the Load Data Warehouse job to update the domains with custom attributes. We recommend that you set up the Data Warehouse before installing the Jaspersoft reporting server. Later you only run the Load Data Warehouse job to update the domains.
Complete all the steps mentioned in Install and Configure the Data Warehouse under 
Installing and Upgrading
to complete the following actions:
  • Create the Data Warehouse schema.
  • Create the Data Warehouse dblink.
  • Verify that the Data Warehouse Status is Available and the dblink is created in CSA.
Configure the Jaspersoft Server Properties
Set the server properties for the Jaspersoft server in CA Clarity System Administration (CSA).
Follow these steps:
  1. Log in to CSA.
    The default login URL for CSA depends on the application server running 
    Clarity Project and Portfolio Management (PPM)
    :
    • Apache Tomcat
      http://<
      hostname
      >:8090/niku/app
    • IBM WebSphere
      http://<
      hostname
      >:9080/nsa/app
  2. Click Servers in the left navigation pane, and then click the name of the local server in the list.
  3. With the Properties tab selected, click the Reporting subtab.
  4. In the 
    Report Server: Jaspersoft
     section, complete the requested information. The following fields require explanation:
    • Vendor
      Specifies the report vendor. For this section, only Jaspersoft is available.
    • Status
      Indicates whether the Jaspersoft server is available.
    • Web URL
      Specifies the web URL for the Jaspersoft server. For example, http://<jaspersoft-hostname>:8080/<jasperwebcontext>.
    • User
      Specifies the Jaspersoft user name who performs system tasks that require administration access. The default user is ppmjasperadmin. You can change the default user name before you import Jaspersoft Advanced Reporting content. The import creates the user. Do not change the user name after you import the Advanced Reporting content.
    • Database ID
      Not applicable.
    • Organization Name
      Specifies the organization name (tenant) that is created on the Jaspersoft server.
      If you do not see the
      Report Server: Jaspersoft
      section by default, configure the following tag in <clarityInstallFolder>/properties.xml:
      <reportServer id="jaspersoft" webUrl="http://<serverName>:<portnumber>/<jaspersoftwebcontext>" context="/<jaspersoftwebcontext>" home="" serviceUrl="http://<serverName>:<portnumber>" volumeName="" username="ppmJasperAdmin" vendor="jaspersoft" databaseId="Niku" jndiName="jdbc/clarity" dwJndiName="jdbc/dwh" orgId="<orgID>" />
  5. Click Save.
Execute the Installation Commands
Before you run these commands, verify that you have completed the following tasks:
  • Data Warehouse status is set to Available.
  • The Data Warehouse database link is created.
  • The Organization Name and Web URL are defined.
Follow these steps:
  1. Open a command prompt and navigate to the 
    Clarity Project and Portfolio Management (PPM)
     runtime bin directory.
  2. Run the following command: 
    admin content csk
    The installation process begins and information displays on the screen. The information is captured and stored in the admin.log file that is located in the logs directory. The output files are stored in the logs/content/xog/csk directory.
  3. Navigate to the 
    Clarity Project and Portfolio Management (PPM)
     runtime bin directory.
  4. Run the following command to import the Jaspersoft advanced reporting content: 
    admin content-jaspersoft csk -userName superuser -password <password>
    If you have any specific file to import, add the 
    -filename
     parameter.
    For more information, see
    Import the Jaspersoft Advanced Reporting Content for the PMO Accelerator
    .
  5. Review the screen output and the logs for important information after the installation completes.
Configure Users for Advanced Reporting
To set up advanced reporting with Jaspersoft, configure users for advanced reporting.
Follow these steps:
  1. Log in to CA PPM.
  2. Assign one of the following access rights to users working on Advanced Reporting:
    • Advanced Reporting - Navigate
      Allows a user to navigate to Advanced Reporting and use the tools as a Jaspersoft user.
    • Advanced Reporting - Administer
      Allows a user to navigate to Advanced Reporting and use the tools as a Jaspersoft administrator.
Assign any of the advanced reporting access rights to access the Advanced Reporting page. For advanced reporting access rights, see .
Run the Data Warehouse Jobs
Run the following jobs in the order provided.
Synchronize the 
Clarity Project and Portfolio Management (PPM)
 users with assigned access rights to their corresponding Jaspersoft users and roles: 
  • Create and Update Jaspersoft Users
Populate the Data Warehouse with data from the 
Clarity Project and Portfolio Management (PPM)
 database:
  • Time Slicing
    This job splits time varying data into a relational format.
    The first run of this job can take substantial time.
  • Load Data Warehouse
    This job extracts the data from the 
    Clarity Project and Portfolio Management (PPM)
     database, transforms the data, and loads the data into the Data Warehouse.
    This job is initially disabled. Enable this job before you run it.
    Before you run this job, open the properties for any custom object or attribute that you want to include and select the 
    Include in the Data Warehouse
     option. This option must be selected for custom objects or attributes to be populated in the Data Warehouse.
    If you are running the job for the first time to populate the Data Warehouse, select the Full Load configuration in the job parameters.
    The following actions require you to rerun the Load Data Warehouse job after the initial population:
    • Deleting an attribute or clearing the Include in the Data Warehouse option for the attribute in Studio.
    • Changing the data type of an attribute.
    • Adding a language to the Data Warehouse.
    • Changing a timeslice date to include a larger timeframe.
  • Load Data Warehouse Access Rights
    This job loads the access privileges for resources and investments from the 
    Clarity Project and Portfolio Management (PPM)
     database to the Data Warehouse.
     This job is initially disabled. Enable this job before you run it.
When the Load Data Warehouse Access Rights and Load Data Warehouse jobs run, the jobs write standard messages to the Jobs logs and detailed messages to the Data Warehouse logs. The default Data Warehouse log files are bg-dwh.log and bg-ca.log. To review the detailed Data Warehouse log messages, navigate to the Data Warehouse logs (under the standard Jobs logs) in Clarity System Administration. You can enable more logging by changing the Kettle Log Level in Clarity System Administration (Logs, Edit Configuration). Use the detailed messages to monitor job progress and to analyze Data Warehouse load failures.
Follow these steps:
  1. Open Home and from Personal, click Reports and Jobs.
  2. Open the Jobs tab.
  3. Locate the job that you want to run and click the name.
    You can page and scroll down the list or you can use the filter to narrow your choices.
  4. Complete the requested information for the job.
    You can start the job immediately or you can schedule a time. You can also indicate resources or groups you want to notify.
  5. Click Submit.
Restart the CA PPM Services
Complete the following steps to restart the services.
Follow these steps:
 
  1. Log in to CA Clarity System Administration.
  2. Open Home, and click All Services.
  3. Select the check boxes next to the CA Clarity Application (app) and CA Clarity Background (bg) services.
  4. Click Start.
Additional Information for Jaspersoft
Multicasting and Cache Distributing over RMI
Multicast is a method of sending IP packets to a group of interested receivers. These packets are only sent to the members of a multicast group with the help of a multicast router. A multicast group is assigned Class D addresses (224.0.0.0 - 239.255.255.255). The first 4 bits of a multicast address should be 1110 and the remaining 28 bits represent different groups.
In some cases, Linux distributions do not have multicast enabled by default and the /etc/hosts file does not include the IP address that is associated with the server host name. As a result, you may encounter the 
hostname associated with the localhost in /etc/hosts
 error. Associate the host name in /etc/hosts with the IP address that is set to the server network interface or to the external static NAT IP address of the server.
Make sure that the /etc/hosts has the IP address together with the IP: 127.0.0.1 and does not contain the entry for loopback address - 127.0.1.1
$ cat /etc/hosts
127.0.0.1 localhosthost.localdomain localhost
Configure Multicasting in Linux
The following procedure explains how to configure multicasting in Linux.
Follow these steps:
  1. Enable multicast on the eth0 interface.
    1. Log in as a root user on all the instances in the cluster where Jaspersoft is installed.
    2. Run the following command to enable multicasting on eth0:
      $ /sbin/ifconfig eth0 multicast
      All the instances should be in the same network subnet.
    3. Run the following command to check if your network interface supports multicast:
      $ /sbin/ifconfig - a
      The Multicast attribute is present in the fourth line of the eth0 properties only if the kernel is complied with the multicast support.
  2. To configure the map network interface to send multicast traffic, add a default route for multicast traffic to the specific NIC. For example, the following command allows eth0 to send multicast traffic:
    $ route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0
    To check if multicast routing is configured, run the following command:
    $ /sbin/route - n
  3. Run the following command to display the multicast group membership information. 
    netstat - g
    Once the route add command is run on all servers, ping the multicast IP with the following command: 
    Ping 
    -c <host ip address>
All the IP addresses that are available in the current configured multicast environment appear.
Configure Cache Distribution over RMI
The following procedure explains how to configure cache distribution over RMI on Jaspersoft Report servers.
Follow these steps:
  1. Stop the Tomcat server.
  2. Go to <tomcat>/webapps/reportservice/WEB-INF.
  3. Open the - ehcache.xml file in an editor.
  4. Uncomment and configure the following XML element sections in the file.
    • <cacheManagerPeerProviderFactory
      class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
      properties="hostName=10.131.112.249,peerDiscovery=automatic,multicastGroupAddress=228.0.0.1,multicastGroupPort=4446,timeToLive=1"/>
    • <cacheManagerPeerListenerFactory
      class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
      properties="hostName=10.131.112.249,port=40011,remoteObjectPort=40012,socketTimeoutMillis=120000"/>
  5. Uncomment the following XML element sections to allow distribution of this cache:
    • <cacheEventListenerFactory
      class="net.sf.ehcache.distribution.RMICacheReplicatorFactory"
      properties="replicateAsynchronously=true, replicatePuts=false, replicateUpdates=true,replicateUpdatesViaCopy=false, replicateRemovals=true "/>
    • <bootstrapCacheLoaderFactory
      class="net.sf.ehcache.distribution.RMIBootstrapCacheLoaderFactory"
      properties="bootstrapAsynchronously=true, maximumChunkSizeBytes=5000000"/>
  6. Save the file.
  7. Similarly, uncomment and configure the same XML sections in <tomcat>/webapps/reportservice/WEB-INF/ehcache_hibernate.xml and <tomcat>/webapps/reportservice/WEB-INF/classes/ehcache_hibernate.xml.
  8. Repeat the steps for all the instances of Jaspersoft that are available in the cluster.
  9. Before you start Tomcat, delete or clean the Tomcat temp directory and the work/Catalina/localhost directory.
Configure a Dedicated JasperReports Server for Running Scheduled Reports
You can deploy the JasperReports Server as a standalone application or in a cluster for high concurrency.
You can dedicate JasperReports Server instances to act as scheduler instances and JasperReports Server instances to serve web requests. The instances serving web requests are part of the load balancer and are non-scheduler instances.
When deploying the JasperReports Server in a cluster, we recommend that you dedicate one or more JasperReports Server instances for processing scheduled reports. The dedicated instances share the same repository. They are not part of the load balancer that serves web requests such as running unscheduled reports or using the ad hoc views.        
In a standalone deployment, only a single JasperReports server instance is available. The single instance acts as the scheduler instance and is responsible for the following items:
  • Processing scheduled reports
  • Serving normal web requests
During interactive installation of the patch, you can specify whether you want to go for a dedicated scheduler instance. Answer 'no' if you are running only a single JasperReports Server instance.
If you answer 'yes', then specify whether you want to make the current instance where you are applying the patch a scheduler instance.
  • If you answer 'yes', then the patch performs the necessary configuration to make the current instance a scheduler instance.
  • If you answer 'no' (for instances which are part of the load balancer), the patch performs the necessary configuration to make the current instance a non-scheduler instance.
: Apply the patch to all the JasperReports Server instances. Also, select the appropriate option during installation to make the instance where you are applying the patch a scheduler or a non-scheduler instance.
Restrict Advanced Reporting Notifications to Trusted Email Domains
In Advanced Reporting, users can email reports either as hyperlinks to the report page or as attachments. When scheduling the reports, users can specify the email addresses for sending the reports notifications and job alerts. Sometimes, reports contain confidential information and users may want to validate the email addresses before sending the notifications. As a 
Clarity Project and Portfolio Management (PPM)
 administrator, you can specify trusted email domains (for example, ca.com)  using commands in
Clarity Project and Portfolio Management (PPM)
 so that notifications are not sent to email addresses outside these domains. In Jaspersoft, a user can specify any email address for notification when scheduling a report. However, before sending the emails,
Clarity Project and Portfolio Management (PPM)
 filters out the email addresses that do not match the trusted domains.
Example
In Jaspersoft, the user wants to send email notifications to two email addresses. The first belongs to the trusted email domains and the second does not belong to the trusted domains. In this case, the email notification is sent to the email address which is part of the trusted email domains. The second email notification is not send. A message is logged in the log file, if the log category set as INFO.
: If you do not specify a list of trusted email domains from
Clarity Project and Portfolio Management (PPM)
, Jaspersoft report emails and job alerts are sent to all email addresses that the user specifies when scheduling reports.
Alternatively, you can disable email notifications so that no report notification or job alert is sent. If Jaspersoft email notifications are disabled in 
Clarity Project and Portfolio Management (PPM)
, a message is logged in the log file, if the log category is set as INFO.
You can configure the notification restrictions at the organization (tenant) level specified for a particular
Clarity Project and Portfolio Management (PPM)
instance.
Follow these steps:
Invoke the following commands from the
Clarity Project and Portfolio Management (PPM)
command-line interface:
  • Run the following command to add trusted email domains.
    admin jasper email -addDomains
    <comma_separated_list_of_trusted_domains>
    A message appears indicating that the list of trusted domains were added successfully.
  • Run the following command to display the list of existing trusted email domains:
    admin jasper email listDomains
  • Run the following command to remove email domains from the existing list of trusted email domains:
    admin jasper email -removeDomains
    <comma_separated_list_of_domains_to_remove>
  • Run the following command to disable report emails and job status notifications, regardless of the configuration of trusted domains:
    admin jasper email disableNotifications
    A message appears indicating that email and job notifications are disabled.
  • Run the following command to re enable report emails and job status notifications:
    admin jasper email enableNotifications
    A message appears indicating that email and job notifications are now enabled.
Check the Installer Version
For information about the installer version, check the following files:
  • Read me file (Pre-installation)
  • version.html file that is created after you install Jaspersoft (Post installation). For example, reportservice/version.html
If Jaspersoft is HTTPS Enabled
Complete the following steps if Jaspersoft is HTTPS enabled.
Follow these steps:
  1. Use your browser to download and save the certificate from the Jaspersoft URL. For example, save it as SETI_JAAS_CER.cer.
  2. From the command prompt, navigate to JDK_HOME on the server where 
    Clarity Project and Portfolio Management (PPM)
     is installed.
  3. Navigate to jre\lib\security. For example, C:\devenv\ca\jdks\jdk1.7.0_67\jre\lib\security>.
  4. Run the following command:
    keytool -importcert -keystore cacerts -alias tomcat7 -storepass changeit -file SETI_JAAS_CER.cer -trustcacerts
  5. Restart 
    Clarity Project and Portfolio Management (PPM)
    .
    To delete an entry from the key store, run the following command: 
    keytool -delete -keystore cacerts -alias tomcat7 -storepass changeit
    The downloaded certificate is deleted from the certificate store.
Stop or Start Jaspersoft
Complete the following steps to stop or start Jaspersoft.
Follow these steps:
  1. Navigate to the <tomcathome>/bin directory.
  2. To stop, run one of the following files:
    • shutdown.sh (Linux)
    • shutdown.bat (Windows)
  3. To restart, run one of the following files:
    • startup.sh (Linux)
    • startup.bat (Windows)
Uninstall Jaspersoft
To uninstall Jaspersoft, complete the following steps:
Follow these steps:
  1. Stop the Tomcat service where the Jaspersoft reporting server is deployed.
  2. Rename the existing 
    <jasperwebcontext>
     folder.
  3. Backup the Jaspersoft database.
  4. Drop the Jaspersoft database from the database server.