Upgrade Jaspersoft and Migrate Advanced Reporting Content

ccppmop144
If you installed Jaspersoft in a previous release, upgrade the version of the application. Also, update the Advanced Reporting content for the current release. In addition, you can export, import, and migrate Advanced Reporting content.
If you have already installed
Clarity Project and Portfolio Management (PPM)
 with JasperReports Server 6.1.0, skip to
Apply the JasperReports Server Cumulative Patch
.If you have already installed
Clarity Project and Portfolio Management (PPM)
 with JasperReports Server 6.1.0, skip to
Apply the JasperReports Server Cumulative Patch
.
Upgrade the Jaspersoft Server
Upgrade your Jaspersoft server to enable Jaspersoft improvements and Advanced Reporting content enhancements. This upgrade process requires that you first export the server-level content from the previous 
Clarity Project and Portfolio Management (PPM)
 release. You then provide this content zip when prompted during the Jaspersoft upgrade process.
 
Follow these steps:
  1. Verify that a previous release of Jaspersoft report server is configured.
  2. Verify that the previous
    Clarity Project and Portfolio Management (PPM)
     release is installed and the Jaspersoft server is associated with it. 
  3. Verify that the csk content was imported into the server that you want to export.
  4. Export the server-level data from the Jaspersoft server using the Jaspersoft UI (Manage, Server Settings, Export). The <content>.zip file is created in the specified folder. 
  5. Download the latest JDK 8 and Tomcat 7 software from the vendors. Set JAVA_HOME and JRE_HOME and verify that the correct java8 and jre8 executables are referenced in the PATH environment variable.
    Examples:
    (Windows) 
    set PATH=%JAVA_HOME%\bin;%PATH%
     
    (Linux) 
    export PATH=$PATH:$JAVA_HOME/bin
  6. Back up the existing Jaspersoft instance (WebApp) and database (database/schema).
  7. Create a Jaspersoft database/schema with a new name before starting the upgrade.
    : During the installation or when the Tomcat service on the Jaspersoft server starts up or shuts down, you may receive the following warning messages:
    Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=32m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
    You can safely ignore these warnings. The PermSize and MaxPermSize parameters are not supported in JDK 1.8. The MetaspaceSize parameter is used instead.
  8. If this upgrade is a second attempt at upgrade, perform the following actions before starting the upgrade process again:
    1. Delete the <Tomcat7>\<WebApp> folder, if it was created.
      Examples:
      (Windows) rmdir <Tomcat7>\webapps\<reportservice>
      (Linux) rm -rf <Tomcat7>/webapps/<reportservice>
    2. Delete the Jaspersoft schema/database and recreate it. Sample queries for supported vendors are provided in Install and Configure Advanced Reporting with Jaspersoft.
      Delete Oracle Schema/Database:
      DROP USER [JS User] CASCADE;
      Delete SQL Server Schema/Database:
      DROP DATABASE [PPM_JASPERSOFT];
      DROP LOGIN [PPM_JASPERSOFT];
      Note:
       We recommend that you extract the installer into a new folder.
  9. When performing upgrades in cluster mode, complete the following steps carefully:
    1. For the primary node, select the Upgrade option and proceed with the upgrade by pointing to the content zip file that was exported from the previous Jaspersoft instance.
    2. For the secondary node, complete the following steps:
      • Select New when prompted for the Installation type.
      • Installation mode: Cluster
      • Cluster Node: Additional (Web-app deploy Only)
      • Complete the Installation. Verify your data and all the cluster nodes are behaving as expected. 
        Provide the Primary node database details when prompted.
  10. Download the Jaspersoft 6.1.0 installer from Support.
  11. Extract the installer, preferably into the root drive (for example, C:\jaspersoft or /fs0/jaspersoft) to avoid the “file name is too long" exceptions during the upgrade process.
  12. Before you proceed with the upgrade, create a file default_master.properties in the buildomatic directory of the Jaspersoft Installer (for example, C:\jaspersoft\buildomatic\ or /fs0/jaspersoft/buildomatic) and create the following parameter: ignoreRecreateDB=true
  13. Run the install.bat/install.sh command from the extraction directory.
  14. Select the upgrade option for your installation type.
  15. When you are prompted for the content zip file, provide the absolute path (including the zip file name) that you generated during the Prerequisites phase.
  16. Enter 
    Y
     to proceed with the upgrade.
  17. Enter the requested information.
    Enter Apache Tomcat7 Directory               : Location on machine where Tomcat7 is installed.
    Enter Jaspersoft Web App Name                : Name of the folder where Jaspersoft is being deployed, for example, reportservice.Enter Jaspersoft Web App Port                : Port on which Jaspersoft should run - default 8080. Email configurations: Choose 'Y' to setup Email configurations    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 the mail server supports. Currently Jaspersoft 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]
  18. Select the Installation Mode.
     1) Standalone                               : For standalone servers   Select DB Server type    1) MSSQL       a) Enter SQL Server Hostname          : Hostname of the server where SQL Server is installed, for example, HOSTNAME       b) Enter SQL Server Port Number       : Database port on which SQL Server is running, for example, 1433       c) Enter Jaspersoft Database Name     : Jaspersoft database name (default = PPM_JASPERSOFT)       d) Enter Jaspersoft Database Username : Jaspersoft Username, for example, PPM_JASPERSOFT       e) Enter Jaspersoft Database Password : Jaspersoft Password    2) Oracle       1) Oracle Standalone        a) Enter Oracle Database Hostname    : Hostname of the server where Oracle is installed, for example, localhost        b) Enter Oracle Database Port Number : Database port on which Oracle is running, for example, 1521        c) Enter Jaspersoft Database Username: Jaspersoft database user name, for example, PPM_JASPERSOFT        d) Enter Jaspersoft Database Password: Jaspersoft password        e) Enter Oracle version         1) 11.2.0.4 or Higher         2) 12.1.0.2 or Higher        f) Enter Oracle SID Name             : Oracle SID, for example, <ORACLESID>
           2) Oracle Cluster (RAC)        a) Enter Oracle Database Hostname    : Hostname of the server where Oracle is installed, for example, localhost        b) Enter Oracle Database Port Number : Database port on which Oracle is running, for example, 1521        c) Enter Jaspersoft Database Username: Jaspersoft database user name, for example, PPM_JASPERSOFT        d) Enter Jaspersoft Database Password: Jaspersoft password        e) Enter Oracle Service Name         : Oracle Service Name, for example, <SERVICENAME>
      2) Cluster            : For Cluster based deployments    a) Primary Node                          : For prompts, refer to Standalone installation.    b) Additional Node (Web-app deploy only) : Deploys the web app only using Primary Node Database/Schema. For prompts, refer to Standalone installation.    
    Important!
     When deploying an additional node, provide the database details for the Primary Node.
       
  19. Confirm the properties that you entered and wait until the installation completes.
  20. Monitor the upgrade progress.
  21. After the Tomcat service starts, you can log in to the Jaspersoft server at the following location using the credentials superuser/superuser:
    http://<MACHINE_NAME>:<PORT>/<JASPERSOFT_WEB_APP_NAME>
    (for example, http://jaspersoftserver:8080/reportservice/)
  22. Open a command prompt and navigate to the 
    Clarity Project and Portfolio Management (PPM)
     runtime bin directory.
  23. Run the following command (to verify that you have latest csk changes):
      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.
  24. Navigate to the 
    Clarity Project and Portfolio Management (PPM)
     runtime bin directory.
  25. Run the following command to import the Jaspersoft Advanced Reporting content: 
      admin content-jaspersoft csk -userName superuser -password <password> upgrade
    If you have a specific file to import, add the -filename parameter.
    Note:
     For more information, see Import the Jaspersoft Advanced Reporting Content for the PMO Accelerator. 
  26. Review the screen output and the logs for important information after the installation completes.
Generate the Key Store File
To authenticate 
Clarity Project and Portfolio Management (PPM)
 and Jaspersoft, generate a trusted key store for each organization. If you are upgrading your product release, use the following procedure to regenerate the keys and copy the key store files.We recommend that you use a new Tomcat folder during an upgrade. The key store files are not automatically copied to the new Jaspersoft context.
  1. Navigate to <clarity_home>/bin.
  2. Run the following command to generate a key store from the CSA:
    admin jaspersoft keystore 
    To specify a key and password, enter the following command: 
    admin jaspersoft 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 to <Tomcat>/webapps/<jasperwebcontext>/WEB-INF/config (where Jaspersoft is installed). 
    Example:
     <Tomcat>/webapps/reportservice/WEB-INF/config
    Note:
     For clustered environments, copy these files to the same location on each of the nodes in the cluster. 
  4. Start the Tomcat service where the Jaspersoft reporting server is deployed.
    Note:
     The Jaspersoft content cannot be imported without starting the reporting service. 
  5. (Optional) Repeat the steps to regenerate the key or change the organization.
Memory Leak Errors May Appear in Tomcat Logs after Stopping or Starting the Server
Occasionally, you may see the following error messages in Tomcat, especially when you are restarting the Jaspersoft Reports servers after maintenance. These errors have been reported on the Linux platform, although they may be seen in Windows as well.Related to these errors, you may notice that the Tomcat process does not exit gracefully, or that Advanced Reporting is not accessible even though the port is available.
org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks SEVERE: The web application [/reportservice] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [[email protected]]) and a value of type [java.util.Hashtable] (value [{SESSION_ID=5C55FD9CCE7272C7FF20B2E6D122F97D, USER_ID=admin|abc123}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks SEVERE: The web application [/reportservice] created a ThreadLocal with key of type [net.sf.jasperreports.engine.fonts.FontUtil$1] (value [[email protected]]) and a value of type [java.util.HashSet] (value [[Arial]] ) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. SEVERE: The web application [/reportservice] created a ThreadLocal with key of type [java.lang.InheritableThreadLocal] (value [[email protected]]) and a value of type [org.springframework.security.authentication.UsernamePasswordAuthenticationToken] (value [org.springframew[email protected]cd0a3791: Principal: MetadataUserDetails: admin; Credentials: [PROTECTED]; Authenticated: true; Details: null; Granted Authorities:
 
Resolution:
 Use the following procedure to resolve this problem.
  1. Verify that the Jaspersoft Tomcat process is not present after performing a shutdown (for example, 
    "ps -ef | grep tomcat"
    ).
  2. If the process is present, kill the process gracefully (for example, 
    kill -9 <ProcessID>
    ).
  3. Start up the Tomcat process again.
Apply the JasperReports Server Cumulative Patch
Apply the JasperReports Server cumulative patch after you have completed a successful JasperReports Server installation. This patch and the CA JDBC Adapter allow you to access Jaspersoft Studio without using a virtual private network (VPN).You can then build reports with Jaspersoft Studio without the need for VPN access to the database servers. This patch also corrects a number of issues that previously occurred with the JasperReports Server.For more information about the corrected issues, see the README.txt file that accompanies the patch.
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.
    2. Under Quick Access, click Download Center. 
    3. Search to locate the 
      ca_ppm_jaspersoft_patch_6.1.0_5.1.0.2.31.zip
       file.
    4. 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.
Post-Patch Installation
Complete the following actions after installing the JasperReports Server cumulative patch:
  • 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 the following credentials:
    Username: superuser
    Password: superuser
  5. Open the following URL:
    http://<domain_name>:<portnumber>/<jasperwebcontext>/version.htm
  6. Verify the installed patch version:
    CA PPM Jaspersoft Release Patch Version = 5.1.0.2
Update Profile Attributes
After you complete the JasperReports Server version upgrade and regenerate the key store file, update the profile attributes.
  1. Open a command prompt in
    install directory
    /bin.
  2. Execute the following command:
admin update jasperParameters
This command updates the profile attributes so that the attributes can be re-encrypted.
Upgrade Advanced Reporting Content
If you installed Advanced Reporting content previously, upgrade the content for the current release.
  1. Open a command prompt in 
    install directory
    /bin.
  2. Execute the following command:
admin content-jaspersoft <contentPackId> upgrade [-userName <user name>] [-password <password>] [-force]
  • ContentPackId: 
    Provide the add-in ID to associate with the Advanced Reporting content installation.
  • userName: 
    Enter the super user Jaspersoft user name.
  • password: 
    Enter the password for the Jaspersoft super user.
  • force: 
    (Optional) Use this option to re-import the upgrade content only. You can decide to use this option after you performed a previous upgrade and you noticed a data inconsistency with the content. The force option is only applicable with the upgrade option.
Restore Domains after Upgrading Advanced Reporting Content
The domains that you import during the Jaspersoft Advanced Reporting content upgrade can become corrupt. Domain corruption can occur while adding or removing customizations during the Load Data Warehouse job. The domains and reports in the application exhibit the following signs of data corruption:
  • Incorrect data
  • Existing data that does not appear
  • Reports that do not run correctly.
You can restore the domains. Use a command option to import the domains and run a dynamic domain update.
  1. Open a command prompt in 
    install directory/bin
  2. Execute the following command:
    admin content-jaspersoft <contentPackId> restoreDomains [-userName <userName>] [-password <password>]
  • ContentPackId: 
    Provide the add-in ID to associate with the Advanced Reporting content installation.
  • userName: 
    Enter the super user Jaspersoft user name.
  • password: 
    Enter the password for the Jaspersoft super user.
 
Export, Import, or Migrate Advanced Reporting Content
You can move content to satisfy the following use cases:
  • Move content from a development environment to a test environment or production.
  • Move content from one Jaspersoft reports server to another version after an upgrade.
  • Move content from more than one tenant across servers.
Prerequisites
  • Access Rights
    : This functionality is available only to users with the 
    Advanced Reporting – Administer
     access right. Migration does not require access to the system where the server is installed.
  • Review Dependencies
    : Jaspersoft Studio reports and views often have dependencies on other resources. These dependencies can include data sources, domains, input controls, queries, and language bundles. For example, a report might depend on images, input data types, and a data source. An exported report includes all dependencies even if they are stored in folders that were not selected during the export. The migration of content with dependencies also creates the same folder structure on the target server. The imported content replaces any existing resources on the target server.
Export Content
You can export individual resources or an entire folder of the repository. 
  1. Log in to the
    Clarity Project and Portfolio Management (PPM)
     source environment.
  2. Click
    Home
    ,
    Personal
    ,
    Advanced Reporting
    .
  3. Select
    View
    ,
    Repository
    .
    You can also export resources such as reports, Ad Hoc views, from the Library page.
  4. To select more than one resource, press the
    Ctrl
    key. When viewing the repository, you can select an entire folder in the left panel.
  5. Right-click the selected folder or resources and select
    Export
    .
    The Export Resources dialog appears:
    The image shows the Export Resources options
  6. (Optional) You can change the default name of the zip file.
  7. The export provides the following options:
    Include report jobs
    : When checked, the export includes scheduled report jobs with any reports in your repository selection.
    Include repository permissions
    : When checked, the export includes any explicit permissions on all items in your repository selection. Clear this check box if you want the exported items to inherit the permissions of the target repository.
  8. Click
    Export
    . The server generates the zip file and your browser prompts you to save the file. Depending on the size of your repository and the selected options, it might take several minutes to generate the file.
! Resources are exported with their dependencies, even if the dependencies are not included in your selection. The export can be large and might take a long time to generate and then download. During this time, the export operation can affect server performance. For this reason we do not recommend exporting large amounts of data.
Import Content
After you export, you can import the exported zip file.
  1. Log in to the 
    Clarity Project and Portfolio Management (PPM)
     target environment.
  2. Click 
    Home
    Personal
    Advanced Reporting
    .
  3. Select
    Manage
    ,
    Organizations
    .
  4. In the left panel, right-click the target organization and select
    Import
    .
    The Import dialog appears:
    The image shows the Import to Org options
  5. Click
    Browse
    to select the zip file to import.
    The dialog allows only the zip archive format. You can import only files created by the export.
  6. The import provides the following options:
    Update
    : When checked, the Update option imports only resources that are new to the current organization (different URI).
    Skip user updates
    : This option allows you to keep the current definition of any users that also exist in the imported organization, in case the exported zip file includes users.
    Include themes
    : When checked, the Include themes option imports any themes that exist in the imported organization.
  7. Click
    Import
    . The server uploads the zip file and imports its contents into the organization. If there are any broken dependencies in the catalog, the server displays a message with three choices:
    Skip
    : This option does not import the resource with the broken dependency, but continues to import other resources.
    • 
    Include
    : Attempts to import the resource with the broken dependency. The import succeeds if there is already a resource in the destination that satisfies the dependency. If the dependency is not satisfied in the destination, the resource is skipped and the import continues.
    Cancel
    : Stops the import operation.
  8. (Optional) You can import into a different organization. If the source organization has a different ID than the target organization, the import merges the content of the export into the selected organization.
    The following message appears:
    The file being imported contains a top-level organization name that does not match the currently selected organization
    Import file: <source organization ID>
    Selected organizations: <target organization ID>
    Content is merged into <target organization ID>.
  9. Click
    Continue Import
    to start the import. When merging organizations with the update option, the contents of the import override the target organization for any resource with the same name and location. The import might take a long time to upload and then process. During this time, the import operation can affect server performance. For this reason we do not recommend importing large amounts of data.
 
Export Jaspersoft Advanced Reporting Content Using the Command Line
Jaspersoft super users and tenant administrators can use the export command to export all Jaspersoft Advanced Reporting content from the JasperReports server (the same or a different instance).Your exported Jaspersoft Advanced Reporting content can include tenant level data, folders, reports, domains, input controls, roles, users, server settings, or the public folder.
Partial export of the Jaspersoft content is not supported with this command.
Do not use the export command (admin jaspersoft export) to create a content zip file for use in upgrading Jaspersoft. Export the tenant-level data from the Jaspersoft server using either the Jaspersoft UI (Manage, Server Settings, Export) or the Jaspersoft export command (js-export.bat in <JaspersoftInstaller>/buildomatic/).
Follow these steps:
  1. Stop the Jaspersoft server before using the export command.
  2. review any resource dependencies outside of the organization that can block the operation.
  3. Open a command prompt and go to 
    install directory
    /bin.
  4. Execute the following command:
    admin jaspersoft export [-orgName t1,t2,t3,..., tn] [-fileName zipfile name] [-includePublic=true]|[-includeServerSettings=true] -fromUserName <superuser> -fromPassword <superuser_password> -fromUrl <JSURL> -allOrgs -properties -overwrite
    • orgName
      : Specify the organization IDs of the tenants to be exported. Separate multiple IDs with commas. If this parameter does not include organization IDs, help information is displayed. Omit this parameter if you want to export only the public folder (or the server settings) and no tenants.
    • fileName
      : Enter the name of the zip file that you are exporting the Advanced Reporting content to. You can export single or multiple tenants to this file. You can specify a target directory path.
    • includePublic:
      (Optional)
       
      This parameter exports the public folders at the global level from the server. This parameter is not specific to a tenant, but applies to the source server (which encompasses all tenants on the source server).
    • includeServerSettings:
      (Optional)
       
      This parameter exports the server settings at the global level from the server. This parameter is not specific to a tenant, but applies to the source server (which encompasses all tenants on the source server).
    • fromUserName
      : Enter the super user Jaspersoft user name.
    • fromPassword
      : Enter the password for the Jaspersoft super user.
    • fromUrl
      : Provide the URL of the source server.
    • allOrgs
      : Exports all the organizations from the Jaspersoft report server.
    • properties
      : Specify the name of the properties file that contains the export command parameters. Use this option instead of specifying the parameters individually in the command.
    • overwrite
      : This parameter overwrites a previously created export zip file, if the file exists.
The export command fails in the following cases:
  • Required parameters are missing.
  • The include option folder name is not public (for example, you specify -includeTemp instead of -includePublic).
  • User credentials are not for the Jaspersoft super user.
  • The orgName parameter is included in the command, but tenants are not specified.
 
Import Jaspersoft Advanced Reporting Content Using the Command Line
Jaspersoft super users and tenant administrators can use the import command to import all Jaspersoft Advanced Reporting content from the JasperReports server (the same or a different instance).
 
1. You can only import the content if the organization IDs match between the export and import servers. You cannot import content that was exported from an organization with a different organization ID. 
2. You can only import the content zip file that has been exported using the command-line Export command.
  1. Stop the Jaspersoft Server.
  2. Open a command prompt at 
    install directory/bin
     
  3. Execute the following command:
admin jaspersoft import [-orgName t1,t2,t3,..., tn] [-fileName zipfile name] -toUserName <superuser> -toPassword <superuser_password> -toUrl <JSURL> -silent
    • orgName
      : Specify the organization IDs of the tenants to be imported. Separate multiple IDs with commas. If this parameter does not specify tenants, then all the tenants in the zip file are imported. 
    • fileName
      : Enter the name of the zip file that you are importing. If you do not specify a filename, help information is displayed.
    • toUserName
      : Enter the super user Jaspersoft user name.
    • toPassword
      : Enter the password for the Jaspersoft super user.
    • toUrl
      : Provide the URL of the target server.
    • silent
      : Permits the silent creation of tenants on the destination Jaspersoft report server. This parameter creates all tenants automatically on the destination Jaspersoft server. If you do not use this parameter, you are prompted to create the tenants.
If the tenant names in the orgName parameter and zip file do not match, the following hint appears:Tenant doesn't exist do you want to create? Y/N
  • Enter 
    Y
     to create new tenants and continue with the import.
  • Enter 
    N
     to cancel the import and exit. 
The partial import or export of Jaspersoft content is not supported with this command.
The import command fails in the following cases:
  • Required parameters are missing.
  • User credentials are not for the Jaspersoft super user.
  • Content zip file is corrupted.
  • An incorrect zip file (exported using the Jaspersoft UI or js-export.bat utility) is used for the import.
 
Migrate Jaspersoft Advanced Reporting Content
As a Jaspersoft administrator, you can export and import the Jaspersoft Advanced Reporting content. This content includes views, reports, custom domains, dashboards, and their dependencies. You can also migrate tenant level data, folders, reports, jobs, domains, input controls, roles, and users.These migration options are helpful when moving custom advanced reporting content between test and production environments.
To use these migration features and to update domain schema, apply Jaspersoft server cumulative patch 6.2.1_5.2.1.2.6.
The migrate command moves the Jaspersoft Advanced Reporting content to a different Jaspersoft server. 
You can only migrate Jaspersoft Advanced Reporting content if the source and destination servers have matching organization IDs. You cannot migrate content between organizations that have different organization IDs. 
Migration Example
You have an environment with a single Jaspersoft Reports Server that is shared by multiple 
Clarity Project and Portfolio Management (PPM)
 instances, or tenants. That is, on the same server, different organizations and tenants are provisioned, one for each instance. When the server needs to be updated to a newer version, 
all
 organizations and tenants on that server are upgraded. However, not all organizations and tenants on the current server may be ready to upgrade.In this case, you can complete an installation of Jaspersoft with the newer version on a different server, and then migrate the content of selected organizations and tenants from the existing server to the new server.
Follow these steps:
  1. Open a command prompt in the 
    install directory
    /bin and execute the following command:
    admin jaspersoft migrate [-orgName t1,t2,t3,..., tn] [-fileName zipfile name] [-includePublic=true]|[-includeServerSettings=true] -fromUserName <source user name> -fromPassword <source_password> -fromUrl <sourceURL> 
    -toUrl <destination url> 
    [-toUserName <destination user name>] [-toPassword <destination password>] -allOrgs -silent
    • orgName
      —Specify the organization IDs of the tenants to be migrated (separate multiple IDs with commas). If this parameter does not include organization IDs, help information is displayed. Omit this parameter if you want to migrate only the public folder (or the server settings) and no tenants. Use the allOrgs parameter instead of orgName to migrate all tenants.
    • includePublic—
      (Optional)
       
      This parameter migrates the public folders at the global level from the server. This parameter is not specific to a tenant, but applies to the source server (which encompasses all tenants on the source server).
    • includeServerSettings—
      (Optional)
       
      This parameter migrates the server settings at the global level from the server. This parameter is not specific to a tenant, but applies to the source server (which encompasses all tenants on the source server).
    • fromUserName
      —Enter the super user Jaspersoft user name for the source tenant.
    • fromPassword
      —Enter the password for the Jaspersoft super user for the source tenant.
    • fromUrl
      —Provide the URL of the source server.
    • toUrl
      Provide the URL of the target server.
    • toUserName
      —Enter the super user Jaspersoft user name for the destination tenant.
    • toPassword
      —Enter the password for the Jaspersoft super user for the destination tenant.
    • allOrgs
      —This parameter migrates all tenants from the Jaspersoft report server.
    • silent
      —This parameter permits the silent creation of tenants on the destination Jaspersoft report server. This parameter creates all tenants automatically on the destination Jaspersoft server. If you do not use this parameter, you are prompted to create the tenants.
      If the tenant names in the orgName parameter and zip file do not match, the following hint appears:
      Tenant doesn't exist do you want to create? Y/N
      • Enter 
        Y
         to create new tenants and continue with the import.
      • Enter 
        N
         to cancel the import and exit. 
  2. Update the properties.xml file with the following information: 
    • Destination Jaspersoft URL 
    • Organization ID
  3. The exported set of folders and files include resources in the repository, such as reports and their dependencies. The exported content is compressed in a single zip archive file.
The content of the zip file is not intended for external access. The zip file contains files in several private formats. The XML syntax is not publicly available and the data files are not meant to be accessed.  
Synchronize the CA PPM Context with Jaspersoft
After you migrate (or import) content to a target tenant, you can change the user profile attributes or the domain schema name for the Jaspersoft administrator user. When content is moved from one Jaspersoft server to another Jaspersoft server in a different environment, the underlying 
Clarity Project and Portfolio Management (PPM)
 server is also different from the source. The database that the server connects to is also different from the source.This command adjusts the Jaspersoft configuration so that reports and other content work seamlessly. It synchronizes the 
Clarity Project and Portfolio Management (PPM)
 server and database details to the targeted Jaspersoft tenant. It also updates the target tenant with the user profile attributes and the domain schema name from the source 
Clarity Project and Portfolio Management (PPM)
 context for the Jaspersoft administrator user.
  1. Update the properties.xml file for the 
    Clarity Project and Portfolio Management (PPM)
     instance that connects to the targeted Jaspersoft server or tenant with the following information: 
    • Destination Jaspersoft URL 
    • Organization ID
  2. Select the target tenant name and user profile attribute values from the properties.xml file.
  3. Run the following command from the 
    Clarity Project and Portfolio Management (PPM)
    target system after you import or migrate the tenant content:
    admin jaspersoft syncPPMContext -userName <username> -password <password>
    • username:
      Enter the superuser Jaspersoft user name for the Jaspersoft report server.
    • password:
      Enter the superuser Jaspersoft password for the Jaspersoft report server.
      Note
      : The migrate command fails if you include the syncPPMContext option and the credentials are not for the Jaspersoft super user.
  
View Database Schema Differences
Organization IDs and database schema names in the source environment are typically different from the target environment. You can view information about the organization ID and database schema names.
  1. Log in to 
    Clarity Project and Portfolio Management (PPM)
    .
  2. Select
    Administration
    ,
    General Settings
    ,
    System Options
    .
  3. View the Advanced Reporting section. 
Update Domain Schema
When resources are imported to a target server where the database schema names are different from the source server, the resources do not work as expected. This behavior occurs when domains are imported, or are included in the import as a dependency. Domains keep references to the database schema from the source server. We recommend you to update the target server domain schema to eliminate any schema mismatch.
Follow these steps:
  1. Log in to CA PPM.
  2. Click
    Home
    ,
    Personal
    ,
    Advanced Reporting
    .
  3. Select
    Manage
    ,
    Update Domain Schema
    .
  4. Select the
    Domain Name
    from the target server that requires an update.
  5. Select the
    Domain Schema
    corresponding to the database accessed by the domain:
    • CA PPM Database Schema
      : Select this option for domains accessing the PPM transactional database.
    • Data Warehouse Database Schema
      : Select this option for domains accessing the Data Warehouse database. Select this option for all out-of-the-box domains included in the Advanced Reporting Content.
  6. Click
    Update
    .
The following image shows a successful example: image2017-7-25 12:56:47.png