TIBCO JasperReports Server Upgrade Guide Jasper Reports
User Manual:
Open the PDF directly: View PDF .
Page Count: 65
Download | |
Open PDF In Browser | View PDF |
JASPERREPORTS® SERVER UPGRADE GUIDE RELEASE 6.4 http://www.jaspersoft.com Copyright ©2005-2017 TIBCO Software Inc. All Rights Reserved. TIBCO Software Inc. This is version 0217-JSP64-08 of the TIBCO JasperReports Server Upgrade Guide. TABLE OF CONTENTS Chapter 1 Introduction 1.1 Server Upgrade Distributions 1.1.1 About Bundled Apache Ant Chapter 2 Overlay Upgrade 2.1 Introduction to the Overlay Upgrade 2.2 Upgrade Steps Overview 2.3 Plan Your Upgrade 2.4 Back Up Your JasperReports Server Instance 2.5 Unpack the Overlay Upgrade Package 2.6 Check for JDBC Driver (Oracle, SQL Server, DB2) 2.7 Run the Overlay Upgrade 2.8 Rerun the Overlay Upgrade 2.9 Rollback Procedure 2.10 Starting and Logging into JasperReports Server 6.4 2.10.1 Clearing Your Browser Cache 2.10.2 Logging into JasperReports Server 2.11 Additional Tasks to Complete the Upgrade 2.11.1 Handling JasperReports Server Customizations 2.11.2 Clearing the Application Server Work Folder 2.11.3 Clearing the Application Server Temp Folder 2.11.4 Clearing the Repository Cache Database Table 2.12 Running Overlay Upgrade a Second Time Chapter 3 Upgrading from 6.3 to 6.4 3.1 Upgrade Steps Overview 3.2 Upgrading with Customizations 3.3 Back Up Your JasperReports Server Instance 3.4 Preparing the JasperReports Server 6.4 WAR File Distribution 3.5 Configuring Buildomatic for Your Database and Application Server 3.5.1 Example Buildomatic Configuration 3.5.2 Additional Step when Using JBoss 7 (and Oracle, SQL Server, or DB2) 3.6 Upgrading to JasperReports Server 6.4 3.6.1 js-upgrade Test Mode TIBCO Software Inc. 7 8 8 11 11 12 12 12 12 13 13 14 14 15 15 15 15 15 15 16 16 16 17 17 17 18 18 18 19 20 21 22 3 TIBCO JasperReports Server Upgrade Guide 3.6.2 Output Log Location 3.6.3 Errors 3.7 Starting and Logging into JasperReports Server6.4 3.7.1 Clearing Your Browser Cache 3.7.2 Logging into JasperReports Server 3.8 Additional Tasks to Complete the Upgrade 3.8.1 Handling JasperReports Server Customizations 3.8.2 Clearing the Application Server Work Folder 3.8.3 Clearing the Application Server Temp Folder 3.8.4 Clearing the Repository Cache Database Table 3.9 Old Manual Upgrade Steps: 6.3 to 6.4 Chapter 4 Upgrading from 4.5 - 6.2 to 6.4 4.1 Upgrade Steps Overview 4.2 Upgrading with Customizations 4.3 Back Up Your JasperReports Server Instance 4.4 Exporting Current Repository Data 4.4.1 Exporting from the UI 4.4.2 Using Buildomatic Scripts to Export Data 4.4.3 Using the js-export Script to Export Data 4.5 Preparing the JasperReports Server 6.4 WAR File Distribution 4.6 Configuring Buildomatic for Your Database and Application Server 4.6.1 Example Buildomatic Configuration 4.6.2 Additional Step when Using JBoss 7 (and Oracle, SQL Server, or DB2) 4.7 Upgrading to JasperReports Server 6.4 4.7.1 js-upgrade Test Mode 4.7.2 Output Log Location 4.7.3 Errors 4.8 Starting and Logging into JasperReports Server 6.4 4.8.1 Clearing Your Browser Cache 4.8.2 Logging into JasperReports Server 4.9 Additional Tasks to Complete the Upgrade 4.9.1 Handling JasperReports Server Customizations 4.9.2 Clearing the Application Server Work Folder 4.9.3 Clearing the Application Server Temp Folder 4.9.4 Clearing the Repository Cache Database Table 4.10 Old Manual Upgrade Steps Chapter 5 Upgrading JasperServer 4.2.1 or Earlier 5.1 Upgrading from 4.2.1 or Earlier 5.2 Best Practices for Upgrading on Windows Chapter 6 Upgrading from the Community Project 6.1 General Procedure 6.2 Backing Up Your JasperReports Server CP Instance 6.2.1 Backing Up Your JasperReports Server CP WAR File 6.2.2 Backing Up Your JasperReports Server Database 4 22 22 22 22 22 23 23 23 23 23 24 25 25 25 26 26 26 27 27 28 28 28 30 31 31 31 32 32 32 32 32 32 33 33 33 33 35 35 35 37 37 38 38 38 TIBCO Software Inc. 6.3 Exporting Your CP Repository Data 6.4 Preparing the JasperReports Server 6.4 WAR File Distribution 6.5 Configuring Buildomatic for Your Database and Application Server 6.5.1 Example Buildomatic Configuration 6.6 Upgrading to the Commercial Version of JasperReports Server 6.4 6.7 Starting and Logging into JasperReports Server 6.4 6.7.1 Clearing Your Browser Cache 6.7.2 Logging into the Commercial Version of JasperReports Server 6.4 6.8 Re-Configuring XML/A Connections (Optional) 6.9 Additional Tasks to Complete the Upgrade 6.9.1 Handling JasperReports Server Customizations 6.9.2 Clearing the Application Server Work Folder 6.9.3 Clearing the Application Server Temp Folder 6.9.4 Clearing the Repository Cache Database Table Appendix A Planning Your Upgrade A.1 Changes in 6.4 That May Affect Your Upgrade A.1.1 Removal of the Impala Connector A.2 Changes in 6.2.1 That May Affect Your Upgrade A.2.1 Removal of the Impala Connector A.3 Changes in 6.2 That May Affect Your Upgrade A.3.1 Renaming of Ad Hoc Templates A.4 Changes in 6.1 That May Affect Your Upgrade A.4.1 Changes to Themes A.5 Changes in 6.0.1 That May Affect Your Upgrade A.5.1 Migrating External Authentication Sample Files A.5.2 Migrating Customizations A.5.3 Changes to Security Classes in JasperReports Server 6.0.1 A.6 Changes in 6.0 That May Affect Your Upgrade A.6.1 Changes to Custom Data Sources A.6.2 Changes to Domain Security Files A.7 Changes in 5.6.1 That May Affect Your Upgrade A.8 Changes in 5.6 That May Affect Your Upgrade A.8.1 Removal of Commercial JDBC Drivers A.8.2 Changes to OLAP Engine Appendix B Working With JDBC Drivers B.1 Open Source JDBC Drivers B.1.1 PostgreSQL Example B.1.2 MySQL Example B.2 Commercial JDBC Drivers B.2.1 Oracle Example B.2.2 SQL Server Example B.2.3 DB2 Example TIBCO Software Inc. 38 39 39 39 40 41 41 42 42 42 43 43 43 43 45 46 46 47 47 47 47 48 48 51 51 52 53 60 60 60 60 61 61 61 62 62 62 63 63 64 64 65 5 TIBCO JasperReports Server Upgrade Guide 6 TIBCO Software Inc. CHAPTER 1 INTRODUCTION TIBCO JasperReports® Server builds on TIBCO JasperReports® Library as a comprehensive family of Business Intelligence (BI) products, providing robust static and interactive reporting, report server, and data analysis capabilities. These capabilities are available as either stand-alone products, or as part of an integrated end-to-end BI suite utilizing common metadata and provide shared services, such as security, a repository, and scheduling. The server exposes comprehensive public interfaces enabling seamless integration with other applications and the capability to easily add custom functionality. This section describes functionality that can be restricted by the software license for JasperReports Server. If you don’t see some of the options described in this section, your license may prohibit you from using them. To find out what you're licensed to use, or to upgrade your license, contact Jaspersoft. The heart of the TIBCO Jaspersoft® BI Suite is the server, which provides the ability to: • • • • • Easily create new reports based on views designed in an intuitive, web-based, drag and drop Ad Hoc Editor. Efficiently and securely manage many reports. Interact with reports, including sorting, changing formatting, entering parameters, and drilling on data. Schedule reports for distribution through email and storage in the repository. Arrange reports and web content to create appealing, data-rich Jaspersoft Dashboards that quickly convey business trends. For users interested in multi-dimensional modeling, we offer Jaspersoft® OLAP, which runs as part of the server. While the Ad Hoc Editor lets users create simple reports, more complex reports can be created outside of the server. You can either use Jaspersoft® Studio or manually write JRXML code to create a report that can be run in the server. We recommend that you use Jaspersoft Studio unless you have a thorough understanding of the JasperReports file structure. You can use the following sources of information to learn about JasperReports Server: • • Our core documentation describes how to install, administer, and use JasperReports Server and Jaspersoft Studio. Core documentation is available as PDFs in the doc subdirectory of your JasperReports Server installation. You can also access PDF and HTML versions of these guides online from the Documentation section of the Jaspersoft Community website. Our Ultimate Guides document advanced features and configuration. They also include best practice recommendations and numerous examples. You can access PDF and HTML versions of these guides online from the Documentation section of the Jaspersoft Community website. TIBCO Software Inc. 7 TIBCO JasperReports Server Upgrade Guide • • • Our Online Learning Portal lets you learn at your own pace, and covers topics for developers, system administrators, business users, and data integration users. The Portal is available online from the Professional Services section of our website. Our free samples, which are installed with JasperReports Library, Jaspersoft Studio, and JasperReports Server, are available and documented online. Please visit our GitHub repository. If you have a subscription to our professional support offerings, please contact our Technical Support team when you have questions or run into difficulties. They're available on the web at and through email at http://support.tibco.com and js-support@tibco.com. JasperReports Server is a component of both a community project and commercial offerings. Each integrates the standard features such as security, scheduling, a web services interface, and much more for running and sharing reports. Commercial editions provide additional features, including Ad Hoc views and reports, advanced charts, dashboards, Domains, auditing, and a multi-organization architecture for hosting large BI deployments. 1.1 Server Upgrade Distributions The following distribution packages are available for JasperReports Server. Distribution Package Description Overlay Upgrade zip Available only with the Commercial version of JasperReports Server. Supports upgrade from version 4.7 or later. Supports only the Apache Tomcat application server. Supports all certified repository databases. Supports upgrade and rollback of upgrade changes. Provides assistance with identifying customized files in your environment. Supports Windows, Linux, Mac, and other platforms. File name is: TIB_js-jrs_6.4.0_overlay.zip WAR File Distribution Zip Supports upgrade from version 4.5 or later. Supports all certified application servers. Supports all certified repository databases. Supports Windows, Linux, Mac, and other platforms. File name is: TIB_js-jrs_6.4.0_bin.zip 1.1.1 About Bundled Apache Ant We recommend Apache Ant version 1.9.4, which is bundled with the Overlay Upgrade ZIP and the War File Distribution ZIP. The Ant scripts used for upgrade come with Windows and Linux batch scripts pre-configured to use the bundled version of Apache Ant. If you want to run your own version of Apache Ant, version 1.8.1 or later is required. The bundled Apache Ant includes an additional jar This jar (ant-contrib.jar) enables conditional logic in Ant. If you're running your own Ant you should copy the ant-contrib.jar to your/lib folder. 8 TIBCO Software Inc. Chapter 1 Introduction On Linux and Solaris, the Ant commands may not be compatible with all shells. If you get errors, use the bash shell explicitly. For more information, see the information on the bash shell in the Troubleshooting appendix of the JasperReports Server Installation Guide. TIBCO Software Inc. 9 TIBCO JasperReports Server Upgrade Guide 10 TIBCO Software Inc. CHAPTER 2 OVERLAY UPGRADE This chapter describes the overlay process for upgrading to JasperReports Server 6.4 and contains the following sections: • • • • • • • • • • • • 2.1 Introduction to the Overlay Upgrade Upgrade Steps Overview Plan Your Upgrade Back Up Your JasperReports Server Instance Unpack the Overlay Upgrade Package Check for JDBC Driver (Oracle, SQL Server, DB2) Run the Overlay Upgrade Rerun the Overlay Upgrade Rollback Procedure Starting and Logging into JasperReports Server 6.4 Additional Tasks to Complete the Upgrade Running Overlay Upgrade a Second Time Introduction to the Overlay Upgrade The overlay upgrade procedure is currently available only for the JasperReports Server Commercial edition installed with the WAR file and only with the Apache Tomcat application server. • • • The overlay upgrade supports only the Apache Tomcat application server. The overlay upgrade supports only JasperReports Server installations using the WAR file. The binary installer is not supported. All certified databases are supported. The overlay upgrade supports upgrading from JasperReports Server versions 4.7 and later to JasperReports Server 6.4. Although the overlay upgrade does offer a rollback feature, you should always back up your database and application before upgrading. This section uses a 6.3 to 6.4 upgrade as an example. TIBCO Software Inc. 11 TIBCO JasperReports Server Upgrade Guide 2.2 Upgrade Steps Overview These are the general steps used in this section: 1. Plan your upgrade. 2. Back up your current JasperReports Server instance. (The overlay tool will automatically back up your war file and ask if you've backed up your database.) 3. Download and unpack the new JasperReports Server overlay upgrade 6.4 package zip file. 4. Run the upgrade steps. The overlay upgrade procedure will help you to identify any modifications or extensions you've made to your JasperReports Server instance. It's always best practice to back up your application and database before upgrading. 2.3 Plan Your Upgrade See Appendix A, “Planning Your Upgrade ,” on page 45 to determine if any customizations you've made to your existing version of JasperReports Server are affected by changes to the updated version. 2.4 Back Up Your JasperReports Server Instance First back up your JasperReports Server WAR file and jasperserver database so you can restore them if necessary. Perform these steps from the command line in a Windows or Linux shell. Back up your JasperReports Server War File: 1. Create a folder where you can save your jasperserver-pro war file. For example, C:\JS_BACKUP or /opt/JS_BACKUP. 2. Copy /webapps/jasperserver-pro to /JS_BACKUP Back up your jasperserver Database: 1. Create a folder (if you did not do so in the step above) where you can save your jasperserver database, For example, C:\JS_BACKUP or /opt/JS_BACKUP. 2. Run the following commands for PostgreSQL: • PostgreSQL cd /JS_BACKUP pg_dump --username=postgres 2.5 jasperserver > js-db-dump.sql Unpack the Overlay Upgrade Package The overlay upgrade package comes in a file named: TIB_js-jrs_6.4.0_overlay.zip. 1. 12 Download the overlay upgrade package from TIBCO Jaspersoft Technical Support (http://support.tibco.com) or contact your sales representative. TIBCO Software Inc. Chapter 2 Overlay Upgrade 2. Extract all files from TIB_js-jrs_6.4.0_overlay.zip. Create or choose a destination folder, such as C:\JS_OVERLAY on Windows, /home/ /JS_OVERLAY on Linux, or /Users/ /JS_OVERLAY on Mac. 3. The overlay upgrade package unpacks into a folder named: overlay This document refers to this folder location as: 2.6 Check for JDBC Driver (Oracle, SQL Server, DB2) As of version 5.6.1, JasperReports Server uses the TIBCO JDBC drivers for the Oracle, SQL Server, and DB2 commercial databases. If you want to use a different JDBC driver, you need to copy it to the correct location. If you use Oracle or DB2, you must also use your existing version of the db.template.properties file. See Appendix B, “Working With JDBC Drivers,” on page 62 for more information. 2.7 Run the Overlay Upgrade The overlay upgrade works only with the Tomcat application server. It supports all certified JasperReports Server databases. You can perform the overlay upgrade whether or not you have local customizations. 1. Stop the Tomcat application server 2. Make sure your database is running 3. Run the following commands: cd overlay install • You're prompted to specify a path to a working folder: You can accept the default or specify an alternate folder Press enter to accept the default “../overlayWorkspace” • You're are prompted to back up your jasperserver database. If you haven't yet: Choose “y” for yes to continue • You are prompted to shutdown your Tomcat instance: You can stop Tomcat now if you have not already done so Choose “y” for yes to continue • You're prompted to specify a path to your master.properties file: For a 6.3 instance it might be similar to: C:\Jaspersoft\jasperreports-server-6.3\buildomatic\default_master.properties /opt/jasperreports-server-6.3/buildomatic/default_master.properties Enter the full path and file name for your default_master.properties file • For final verification, the overlay prompts you for the path to your application server: If you haven’t moved it, it's located in the path to: Press enter to accept the default if it's correct • The overlay will begin updating your system: Your jasperserver-pro war file will be automatically backed up Potential customizations in your environment will be analyzed TIBCO Software Inc. 13 TIBCO JasperReports Server Upgrade Guide • You're prompted to review the report on customizations if you choose to: Choose “y” for yes to continue with the upgrade The jasperserver database will be upgraded The jasperserver-pro war file will be upgraded The core data resources will be upgraded in the jasperserver repository database When the overlay upgrade has finished, start Tomcat, and log in to test the upgraded JasperReports Server. If upgrade was successful, you'll see BUILD SUCCESSFUL on the command line 2.8 Rerun the Overlay Upgrade If you exit the overlay install for any reason, you can re-run the overlay by simply running the same command: overlay install By default, the overlay runs in resume mode (resumeMode=true) This means your answers to previous prompts will be remembered. If you want to re-run the overlay “from scratch”, run the following command: overlay install -DresumeMode=false For more information on the overlay options run: overlay help 2.9 Rollback Procedure If you encounter an error with the overlay upgrade, use the following rollback procedure: 1. Stop Tomcat. 2. Run the following command: overlay rollback 3. Specify the path to the working folder: The default is ../overlayWorkspace 4. The tool will ask if you've rolled back your JasperReports Server database: The default is no You're required to manually restore your database . 5. When the tool has finished, restore your database (see below), start Tomcat, and test JasperReports Server. To restore your JasperReports Server Database: 1. Go to the directory location where you saved the backup of your jasperserver database For example, C:\JS_BACKUP or /opt/JS_BACKUP. 2. Run the following commands for PostgreSQL: cd /opt/JS_BACKUP pg_restore --username=postgres 14 jasperserver < js-db-dump.sql TIBCO Software Inc. Chapter 2 Overlay Upgrade 2.10 Starting and Logging into JasperReports Server 6.4 Start your application server. Your database should already be running. 2.10.1 Clearing Your Browser Cache Before you log in, make sure you and your end users clear the browser cache. JavaScript files, which enable the UI elements of JasperReports Server, are typically cached by the browser. Clear the cache to ensure that the newer files are used. 2.10.2 Logging into JasperReports Server Log in using the following URL, user IDs, and passwords: URL: http://localhost:8080/jasperserver-pro User ID Password Description superuser System-wide administrator jasperadmin Administrator for the default organization Your JasperReports Server instance has now been upgraded to 6.4. If you have startup or login problems, refer to the Troubleshooting appendix of the JasperReports Server Installation Guide. 2.11 Additional Tasks to Complete the Upgrade Perform these tasks with the application server shutdown. 2.11.1 Handling JasperReports Server Customizations If you made modifications to the original JasperReports Server application, these configurations are typically found in the WEB-INF/applicationContext-*.xml set of files. You'll need to manually copy configuration changes, like client-specific security classes or LDAP server configurations, from your previous environment and integrate them with your upgraded environment. 2.11.2 Clearing the Application Server Work Folder Application servers have work folders where JasperReports Server files are compiled and cached and other objects are stored. When you update the WAR file or license, the buildomatic deploy-webapp-pro target should automatically clear the application server’s work directory, but it’s a good practice to double-check. A permission problem, or some other problem, could prevent the clearing of the work folder. To clear the work folder in Tomcat: 1. Change directory to /work. 2. Delete all the files and folders in this directory. TIBCO Software Inc. 15 TIBCO JasperReports Server Upgrade Guide 2.11.3 Clearing the Application Server Temp Folder JasperReports Server uses caching to speed operations within the application. Caching files are created and stored in the application server, usually in a temp folder. Clear this temp folder to avoid any post-upgrade conflicts. To clear the temp folder in Apache Tomcat: 1. Change directory to /temp 2. 2.11.4 Delete all the files and folders in this directory Clearing the Repository Cache Database Table In the jasperserver database, compiled JasperReports Library resources are cached in the JIRepositoryCache table for increased efficiency at runtime. Because the JasperReports Library JAR is typically updated with each new release, old cached items can get out of date and cause errors at runtime. If you encounter errors that mention a JasperReports Library “local class incompatible,” check your repository cache table. In summary, you can clear your jasperserver database cache table as part of this upgrade process whether or not there are errors. To manually clear the repository cache database table, run a SQL command similar to one shown below: update JIRepositoryCache set item_reference = null; delete from JIRepositoryCache; 2.12 Running Overlay Upgrade a Second Time If you run the overlay upgrade a second time, the overlay logic will ask if you want to resume the last run of the overlay, so that your previous answers to questions are remembered and reused. The overlay procedure will ask: “We have detected that overlay install was already run. Do you want to resume last run? Default is 'y' ([y], n):” Choose “y” for yes if you do not want to change any information previously given to the overlay Choose “n” for no if you would like to enter new or different information One reason for entering “n” for no would be if you did not give a valid path to your default_master.properties file the first time you executed the overlay. 16 TIBCO Software Inc. CHAPTER 3 UPGRADING FROM 6.3 TO 6.4 This chapter describes the recommended procedure for upgrading to JasperReports Server 6.4 from version 6.3. The examples show you how to upgrade using the js-upgrade shell scripts. This chapter contains the following sections: • • • • • • • • • 3.1 Upgrade Steps Overview Upgrading with Customizations Back Up Your JasperReports Server Instance Preparing the JasperReports Server 6.4 WAR File Distribution Configuring Buildomatic for Your Database and Application Server Upgrading to JasperReports Server 6.4 Starting and Logging into JasperReports Server6.4 Additional Tasks to Complete the Upgrade Old Manual Upgrade Steps: 6.3 to 6.4 Upgrade Steps Overview These are the general steps used in this section: 1. Identify your customizations. 2. Back up your current JasperReports Server instance. 3. Download and set up the new 6.4 JasperReports Server WAR file distribution zip. 4. Run the js-upgrade script as described in 3.6, “Upgrading to JasperReports Server 6.4,” on page 21. If your current instance of JasperReports Server has modifications or extensions, keep track of these and reintegrate them into your 6.4 instance after upgrading. 3.2 Upgrading with Customizations If your current instance of JasperReports Server has modifications or extensions, keep track of these and reintegrate them into your 6.4 instance after upgrading. See Appendix A, “Planning Your Upgrade ,” on page 45 to determine if any customizations you've made to your existing version of JasperReports Server are affected by changes to the updated version. TIBCO Software Inc. 17 TIBCO JasperReports Server Upgrade Guide 3.3 Back Up Your JasperReports Server Instance First back up your JasperReports Server WAR file and jasperserver database so you can restore them if necessary. Perform these steps from the command line in a Windows or Linux shell. This backup example is for Tomcat with the PostgreSQL or MySQL database. For other databases, consult your DB administration documentation for backup information. Back up your JasperReports Server War File: 1. Create a folder where you can save your jasperserver-pro war file. For example, C:\JS_BACKUP or /opt/JS_BACKUP. 2. Copy /webapps/jasperserver-pro to /JS_BACKUP Back up your jasperserver Database: 1. Create a folder (if you did not do so in the step above) where you can save your jasperserver database, For example, C:\JS_BACKUP or /opt/JS_BACKUP. 2. Run the following commands for PostgreSQL or MySQL: • PostgreSQL cd /JS_BACKUP pg_dump --username=postgres • jasperserver > js-db-dump.sql MySQL cd /JS_BACKUP Windows: mysqldump --user=root --password= jasperserver > js-db-dump.sql Linux: mysqldump --user=root --password= --host=127.0.0.1 jasperserver > js-db-dump.sql For MySQL, If you receive an error about packet size, see the Troubleshooting appendix of the JasperReports Server Installation Guide. 3.4 Preparing the JasperReports Server 6.4 WAR File Distribution Use the buildomatic js-upgrade scripts included in the 6.4 WAR file distribution ZIP release package to carry out the upgrade. The WAR file distribution comes in a compressed ZIP file named TIB_js-jrs_6.4.0_ bin.zip. Follow these steps to obtain and unpack the WAR file distribution ZIP file: 1. Download the WAR file distribution from TIBCO Jaspersoft Technical Support (http://support.tibco.com) or contact your sales representative. 2. Extract all files from TIB_js-jrs_6.4.0_bin.zip. Choose a destination, such as a C:\Jaspersoft folder on Windows, /home/ on Linux, or /Users/ on Mac. After you unpack the WAR File Distribution, the resulting location will be known as: 3.5 Configuring Buildomatic for Your Database and Application Server This upgrade procedure uses the js-upgrade-samedb shell script. 18 TIBCO Software Inc. Chapter 3 Upgrading from 6.3 to 6.4 For Unix, the bash shell is required for the js-upgrade scripts. If you're installing to a non-Linux Unix platform such as HP-UX, IBM AIX, FreeBSD or Solaris, you need to download and install the bash shell. See the Troubleshooting appendix of the JasperReports Server Installation Guide for more information. This section shows example configurations for the PostgreSQL, MySQL, and Oracle databases. Other databases are similar. 3.5.1 Example Buildomatic Configuration The default_master.properties file handles the upgrade configuration. We provide a sample configuration file for each database. You must specify your database credentials and application server location, and rename the file to default_master.properties. 3.5.1.1 PostgreSQL Example To configure default_master.properties for PostgreSQL: 1. Locate the postgresql_master.properties sample configuration file: Database Master Properties File PostgreSQL /buildomatic/sample_conf/postgresql_master.properties 2. Copy the file to /buildomatic 3. Rename the file default_master.properties 4. Edit default_master.properties for your database and application server: Database Sample Property Values PostgreSQL appServerType=tomcat6 [tomcat7, jboss, glassfish2, glassfish3] appServerDir=c:\\Apache Software Foundation\\Tomcat 7 dbUsername=postgres dbPassword=postgres dbHost=localhost 3.5.1.2 MySQL Example To configure default_master.properties for MySQL: 1. Locate the mysql_master.properties sample configuration file: Database Master Properties File MySQL /buildomatic/sample_conf/mysql_master.properties 2. Copy the file to /buildomatic 3. Rename the file default_master.properties 4. Edit default_master.properties for your database and application server. TIBCO Software Inc. 19 TIBCO JasperReports Server Upgrade Guide Database Sample Property Values MySQL appServerType=tomcat6 [tomcat7, jboss, glassfish2, glassfish3] appServerDir=C:\\Apache Software Foundation\\Tomcat 7 dbUsername=root dbPassword=password dbHost=localhost 3.5.1.3 Oracle Example To configure default_master.properties for Oracle: 1. Locate the oracle_master.properties sample configuration file: Database Master Properties File Oracle /buildomatic/sample_conf/oracle_master.properties 2. Copy the file to /buildomatic 3. Rename the file to default_master.properties 4. Edit default_master.properties for your database and application server. Database Sample Property Values Oracle appServerType=tomcat6 [tomcat7, tomcat6, jboss, glassfish2, glassfish3] appServerDir=c:\\Apache Software Foundation\\Tomcat-7 (for example) dbUsername=jasperserver dbPassword=password sysUsername=system sysPassword=password dbHost=localhost 3.5.1.4 Using Vendor's Drivers for Commercial Databases JasperReports Server versions 5.6.1 and later include the TIBCO JDBC drivers for the following commercial databases: Oracle, SQL Server, or DB2. If you want to use a different JDBC driver, you need to copy it to the correct location and edit default_master.properties before running the upgrade steps. See Appendix B, “Working With JDBC Drivers,” on page 62 for more information. 3.5.2 Additional Step when Using JBoss 7 (and Oracle, SQL Server, or DB2) If your application server is JBoss 7, your database is Oracle, SQL Server, or DB2 — and you're not using the TIBCO JDBC driver — you'll need to make an explicit reference to your JDBC driver so JBoss 7 will know its exact file name. 1. First update your default_master.properties file to specify the exact name (artifactId and version) of your JDBC driver. To do this: a. Edit: /buildomatic/default_master.properties b. Look for the section "Setup JDBC Driver", then uncomment and edit these two lines: # maven.jdbc.artifactId=ojdbc5 # maven.jdbc.version=11.2.0 20 TIBCO Software Inc. Chapter 3 Upgrading from 6.3 to 6.4 So they look like this: maven.jdbc.artifactId=ojdbc5 maven.jdbc.version=11.2.0 (This will work for a driver with the file name: ojdbc5-11.2.0.jar) c. Uncomment the line: jdbcDriverMaker=native 2. Edit your jboss-deployment-structure.xml file so that it specifies the JDBC filename: a. Edit: /buildomatic/install_resources/jboss/jboss-deploymentstructure.xml b. Look for the section "Setup JDBC Driver" c. Uncomment and edit the line for your database type (for instance): So it looks like this: (This will work for a driver with the filename: ojdbc5-11.2.0.jar) 3.6 Upgrading to JasperReports Server 6.4 Now that your buildomatic scripts are configured, you can complete the upgrade. Make sure you've backed up your jasperserver database before proceeding. Make sure you've backed up your old JasperReports Server WAR file before proceeding. 1. Stop your application server 2. Start your database server 3. Run the following commands: Commands Description cd /buildomatic js-upgrade-samedb.bat (Windows) Upgrade jasperserver-pro war file, upgrade jasperserver database to 6.4, add 6.4 repository resources into the database ./js-upgrade-samedb.sh (Linux) Upgrade jasperserver-pro war file, upgrade jasperserver database to 6.4, add 6.4 repository resources into the database TIBCO Software Inc. 21 TIBCO JasperReports Server Upgrade Guide 3.6.1 js-upgrade Test Mode Use the test option to run the js-upgrade script in test mode. For example, on Windows, enter: cd /buildomatic js-upgrade-samedb.bat test In test mode, the js-upgrade scripts check your default_master.properties settings and validate your application server location and its ability to connect to your database. Test mode can help you debug issues like an incorrect database password without altering your system. 3.6.2 Output Log Location The js-upgrade script creates an output log that captures both standard and error output. If problems occur during script execution, or you just want to remember which options you chose, open the output log file located here: /buildomatic/logs/js-upgrade- - .log 3.6.3 Errors If you encounter errors running the js-upgrade script, first look at the output log to see if you can spot the errors. For help, refer to the Troubleshooting appendix of the JasperReports Server Installation Guide. The information in this appendix applies to both js-upgrade scripts and js-install scripts. If you need to modify values in your default_master.properties file, you can simply edit the file. When you run the js-upgrade script again, it uses the new values. 3.7 Starting and Logging into JasperReports Server6.4 Start your application server. Your database should already be running. 3.7.1 Clearing Your Browser Cache Before you log in, make sure you and your end users clear the browser cache. JavaScript files, which enable the UI elements of JasperReports Server, are typically cached by the browser. Clear the cache to ensure that the newer files are used. 3.7.2 Logging into JasperReports Server Log in using the following URL, user IDs, and passwords: URL: http://localhost:8080/jasperserver-pro 22 User ID Password Description superuser System-wide administrator jasperadmin Administrator for the default organization TIBCO Software Inc. Chapter 3 Upgrading from 6.3 to 6.4 Your JasperReports Server instance has now been upgraded to 6.4. If you have startup or login problems, refer to the Troubleshooting appendix of the JasperReports Server Installation Guide. 3.8 Additional Tasks to Complete the Upgrade Perform these tasks with the application server shutdown. 3.8.1 Handling JasperReports Server Customizations If you made modifications to the original JasperReports Server application, these configurations are typically found in the WEB-INF/applicationContext-*.xml set of files. You'll need to manually copy configuration changes, like client-specific security classes or LDAP server configurations, from your previous environment and integrate them with your upgraded environment. 3.8.2 Clearing the Application Server Work Folder Application servers have work folders where JasperReports Server files are compiled and cached and other objects are stored. When you update the WAR file or license, the buildomatic deploy-webapp-pro target should automatically clear the application server’s work directory, but it’s a good practice to double-check. A permission problem, or some other problem, could prevent the clearing of the work folder. To clear the work folder in Tomcat: 1. Change directory to /work. 2. 3.8.3 Delete all the files and folders in this directory. Clearing the Application Server Temp Folder JasperReports Server uses caching to speed operations within the application. Caching files are created and stored in the application server, usually in a temp folder. Clear this temp folder to avoid any post-upgrade conflicts. Typically, the temp folder used by an application server corresponds to the path referenced by the java.io.tmpdir Java system property. For Apache Tomcat the temp folder is /temp. To clear the temp folder in Apache Tomcat: 1. Change directory to /temp 2. 3.8.4 Delete all the files and folders in this directory Clearing the Repository Cache Database Table In the jasperserver database, compiled JasperReports Library resources are cached in the JIRepositoryCache table for increased efficiency at runtime. Because the JasperReports Library JAR is typically updated with each new release, old cached items can get out of date and cause errors at runtime. If you encounter errors that mention a JasperReports Library “local class incompatible,” check your repository cache table. In summary, you can clear your jasperserver database cache table as part of this upgrade process whether or not there are errors. TIBCO Software Inc. 23 TIBCO JasperReports Server Upgrade Guide To manually clear the repository cache database table, run a SQL command similar to one shown below: update JIRepositoryCache set item_reference = null; delete from JIRepositoryCache; 3.9 Old Manual Upgrade Steps: 6.3 to 6.4 This section describes the older, manual upgrade steps used before we implemented the js-upgrade shell scripts in release 4.0. They're provided here mainly as a reference for internal use. We recommend using the js-upgrade shell scripts described in the beginning of this chapter instead of these manual commands: Commands Description cd /buildomatic js-ant upgrade-6.3-6.4-pro Execute SQL script to upgrade database to 6.4. Execute script buildomatic/install_ resources/sql/ /upgrade- -6.3.0-6.4.0pro.sql js-ant import-minimal-for-upgrade-pro Load themes and other core resources for 6.4. Note: "import-minimal-for-upgrade" will import core resources in an "update" mode so that the older 6.3 core resources will be overwritten. Additionally, the "skip-userupdate" option will be applied so that the superuser and jasperadmin users will not have their passwords modified. 24 js-ant import-sample-data-upgrade-pro (Optional) Load the 6.4 sample data. js-ant deploy-webapp-pro Delete old 6.3 war file, deploy the 6.4 war file. TIBCO Software Inc. CHAPTER 4 UPGRADING FROM 4.5 - 6.2 TO 6.4 This chapter describes the recommended procedure for upgrading from JasperReports Server 4.5 through 6.2 to JasperReports Server 6.4. If you're upgrading from version 6.3 to 6.4, we recommend the procedure in Chapter 3, “Upgrading from 6.3 to 6.4,” on page 17. This upgrade procedure uses the JasperReports Server WAR File Distribution ZIP release package and the included buildomatic scripts. Our examples are for upgrading from version 6.2. This chapter contains the following sections: • • • • • • • • • • 4.1 Upgrade Steps Overview Upgrading with Customizations Back Up Your JasperReports Server Instance Exporting Current Repository Data Preparing the JasperReports Server 6.4 WAR File Distribution Configuring Buildomatic for Your Database and Application Server Upgrading to JasperReports Server 6.4 Starting and Logging into JasperReports Server 6.4 Additional Tasks to Complete the Upgrade Old Manual Upgrade Steps Upgrade Steps Overview These are the general steps used in this section: 4.2 1. Plan your upgrade. 2. Back up your current JasperReports Server instance. 3. Export your existing repository data. For example, export your 6.2 data. 4. Download and set up the new 6.4 JasperReports Server WAR file distribution zip. 5. Run the js-upgrade script as described in 4.7, “Upgrading to JasperReports Server 6.4,” on page 31. Upgrading with Customizations If your current instance of JasperReports Server has modifications or extensions, keep track of these and reintegrate them into your 6.4 instance after upgrading. See Appendix A, “Planning Your Upgrade ,” on TIBCO Software Inc. 25 TIBCO JasperReports Server Upgrade Guide page 45 to determine if any customizations you've made to your existing version of JasperReports Server are affected by changes to the updated version. 4.3 Back Up Your JasperReports Server Instance First back up your JasperReports Server WAR file and jasperserver database so you can restore them if necessary. Perform these steps from the command line in a Windows or Linux shell. This backup example is for Tomcat with the PostgreSQL or MySQL database. For other databases, consult your DB administration documentation for backup information. Back up your JasperReports Server War File: 1. Create a folder where you can save your jasperserver-pro war file. For example, C:\JS_BACKUP or /opt/JS_BACKUP. 2. Copy /webapps/jasperserver-pro to /JS_BACKUP Back up your jasperserver Database: 1. Create a folder (if you did not do so in the step above) where you can save your jasperserver database, For example, C:\JS_BACKUP or /opt/JS_BACKUP. 2. Run the following commands for PostgreSQL or MySQL: • PostgreSQL cd /JS_BACKUP pg_dump --username=postgres • jasperserver > js-db-dump.sql MySQL cd /JS_BACKUP Windows: mysqldump --user=root --password= jasperserver > js-db-dump.sql Linux: mysqldump --user=root --password= --host=127.0.0.1 jasperserver > js-db-dump.sql For MySQL, If you receive an error about packet size, see the Troubleshooting appendix of the JasperReports Server Installation Guide. 4.4 Exporting Current Repository Data You need to export your old repository data. Use the JasperReports Server export utility to export using: • • • 4.4.1 the JasperReports Server UI (version 5.0 or later) the buildomatic scripts (if you originally installed using buildomatic). the js-export.bat/.sh script found in the /buildomatic folder. Exporting from the UI In JasperReports Server version 5.0, we added import-export functionality to the UI. Administrators who log in with the superuser account can export all repository data to a file on their machine. Important: If you have a very large amount of repository data, it might be better to run export from the command line instead of from the UI. 26 TIBCO Software Inc. Chapter 4 Upgrading from 4.5 - 6.2 to 6.4 Warning: Export from the UI in Release 5.1 has a bug. So, it's best to export from the command line if upgrading from 5.1. If you do export from the UI with 5.1, you can unpack the resulting export.zip file, edit the index.xml file and change the string “5.0.0 CE” to 5.1.0 PRO”. See the JasperReports Server Administrator Guide for details. To export your 6.2 repository data from the UI do the following: 1. Start a web browser on your server (so you can save to the server’s hard disk). 1. Log into JasperReports Server using the superuser account. 2. Navigate to the Export tab page: Manage > Server Settings > Export. 3. Click the Export button to accept the default values 4. When you're prompted to save the file, save to a location on the hard disk. Remember that the export.zip file will need to be accessible from the command line where you run the upgrade commands. So, if you save the zip locally you'll need to upload it to the server where you're running the upgrade commands. 4.4.2 Using Buildomatic Scripts to Export Data If you configured buildomatic and your default_master.properties file for export as described in the JasperReports Server Administrator Guide, you can use buildomatic to export your repository data. For example, to export 6.2 repository data, use the following commands: 1. Navigate to the buildomatic directory: cd /buildomatic 2. Run buildomatic with the export target: Windows: js-ant.bat export-everything -DexportFile=js-6.2-export.zip Linux: ./js-ant export-everything -DexportFile=js-6.2-export.zip Note the location of this export file so that you can use it during the 6.4 upgrade process. 4.4.3 Using the js-export Script to Export Data To use the js-export.bat/.sh script, navigate to the buildomatic folder, for example, /buildomatic. If you're using the PostgreSQL database the js-export script should already be configured to run. If you're using a different database, or you've changed database passwords, you may need to update the js-export configuration. Run the following commands: 1. Navigate to the buildomatic directory: cd /buildomatic 2. Run the js-export script: Windows: js-export.bat --everything --output-zip js-6.2-export.zip Linux: js-export.sh --everything --output-zip js-6.2-export.zip Note the location of this export file so that you can use it during the 6.4 upgrade process. TIBCO Software Inc. 27 TIBCO JasperReports Server Upgrade Guide 4.5 Preparing the JasperReports Server 6.4 WAR File Distribution Use the buildomatic js-upgrade scripts included in the 6.4 WAR file distribution ZIP release package to carry out the upgrade. The WAR file distribution comes in a compressed ZIP file named TIB_js-jrs_6.4.0_ bin.zip. Follow these steps to obtain and unpack the WAR file distribution ZIP file: 1. Download the WAR file distribution from TIBCO Jaspersoft Technical Support (http://support.tibco.com) or contact your sales representative. 2. Extract all files from TIB_js-jrs_6.4.0_bin.zip. Choose a destination, such as a C:\Jaspersoft folder on Windows, /home/ on Linux, or /Users/ on Mac. After you unpack the WAR File Distribution, the resulting location will be known as: 4.6 Configuring Buildomatic for Your Database and Application Server This upgrade procedure uses the js-upgrade-newdb shell script. For Unix, the bash shell is required for the js-upgrade scripts. If you're installing to a non-Linux Unix platform such as HP-UX, IBM AIX, FreeBSD or Solaris, you need to download and install the bash shell. See the Troubleshooting appendix of the JasperReports Server Installation Guide for more information. This section shows example configurations for the PostgreSQL, MySQL, and Oracle databases. Other databases are similar. 4.6.1 Example Buildomatic Configuration The default_master.properties file handles the upgrade configuration. We provide a sample configuration file for each database. You must specify your database credentials and application server location, and rename the file to default_master.properties. 4.6.1.1 PostgreSQL Example To configure default_master.properties for PostgreSQL: 1. 28 Locate the postgresql_master.properties sample configuration file: Database Master Properties File PostgreSQL /buildomatic/sample_conf/postgresql_master.properties 2. Copy the file to /buildomatic 3. Rename the file default_master.properties 4. Edit default_master.properties for your database and application server: TIBCO Software Inc. Chapter 4 Upgrading from 4.5 - 6.2 to 6.4 Database Sample Property Values PostgreSQL appServerType=tomcat6 [tomcat7, jboss, glassfish2, glassfish3] appServerDir=c:\\Apache Software Foundation\\Tomcat 7 dbUsername=postgres dbPassword=postgres dbHost=localhost 4.6.1.2 MySQL Example To configure default_master.properties for MySQL: 1. Locate the mysql_master.properties sample configuration file: Database Master Properties File MySQL /buildomatic/sample_conf/mysql_master.properties 2. Copy the file to /buildomatic 3. Rename the file default_master.properties 4. Edit default_master.properties for your database and application server. Database Sample Property Values MySQL appServerType=tomcat6 [tomcat7, jboss, glassfish2, glassfish3] appServerDir=C:\\Apache Software Foundation\\Tomcat 7 dbUsername=root dbPassword=password dbHost=localhost 4.6.1.3 Oracle Example To configure default_master.properties for Oracle: 1. Locate the oracle_master.properties sample configuration file: Database Master Properties File Oracle /buildomatic/sample_conf/oracle_master.properties 2. Copy the file to /buildomatic 3. Rename the file to default_master.properties 4. Edit default_master.properties for your database and application server. TIBCO Software Inc. 29 TIBCO JasperReports Server Upgrade Guide Database Sample Property Values Oracle appServerType=tomcat6 [tomcat7, tomcat6, jboss, glassfish2, glassfish3] appServerDir=c:\\Apache Software Foundation\\Tomcat-7 (for example) dbUsername=jasperserver dbPassword=password sysUsername=system sysPassword=password dbHost=localhost 4.6.1.4 Using Vendor's Drivers for Commercial Databases JasperReports Server versions 5.6.1 and later include the TIBCO JDBC drivers for the following commercial databases: Oracle, SQL Server, or DB2. If you want to use a different JDBC driver, you need to copy it to the correct location and edit default_master.properties before running the upgrade steps. See Appendix B, “Working With JDBC Drivers,” on page 62 for more information. 4.6.2 Additional Step when Using JBoss 7 (and Oracle, SQL Server, or DB2) If your application server is JBoss 7, your database is Oracle, SQL Server, or DB2 — and you're not using the TIBCO JDBC driver — you'll need to make an explicit reference to your JDBC driver so JBoss 7 will know its exact file name. 1. First update your default_master.properties file to specify the exact name (artifactId and version) of your JDBC driver. To do this: a. Edit: /buildomatic/default_master.properties b. Look for the section "Setup JDBC Driver", then uncomment and edit these two lines: # maven.jdbc.artifactId=ojdbc5 # maven.jdbc.version=11.2.0 So they look like this: maven.jdbc.artifactId=ojdbc5 maven.jdbc.version=11.2.0 (This will work for a driver with the file name: ojdbc5-11.2.0.jar) c. Uncomment the line: jdbcDriverMaker=native 2. Edit your jboss-deployment-structure.xml file so that it specifies the JDBC filename: a. Edit: /buildomatic/install_resources/jboss/jboss-deploymentstructure.xml b. Look for the section "Setup JDBC Driver" c. Uncomment and edit the line for your database type (for instance): So it looks like this: (This will work for a driver with the filename: ojdbc5-11.2.0.jar) 30 TIBCO Software Inc. Chapter 4 Upgrading from 4.5 - 6.2 to 6.4 4.7 Upgrading to JasperReports Server 6.4 Now that your buildomatic scripts are configured, you can complete the upgrade. Make sure you've backed up your jasperserver database before proceeding. Make sure you've backed up your old JasperReports Server WAR file before proceeding. 1. Stop your application server 2. Start your database server 3. Run the following commands: Commands Description cd /buildomatic Change to buildomatic directory js-upgrade-newdb.bat \js-6.2-export.zip (Windows) Upgrade jasperserver-pro war file, drop and recreate the database, import data file from previous version. ./js-upgrade-newdb.sh /js-6.2-export.zip (Linux) Upgrade jasperserver-pro war file, drop and recreate the database, import data file from previous version. On MySQL, if you receive an error about packet size, see the Troubleshooting appendix of the JasperReports Server Installation Guide. If you have auditing enabled, see the section about including audit events in the Troubleshooting appendix of the JasperReports Server Installation Guide. 4.7.1 js-upgrade Test Mode Use the test option to run the js-upgrade script in test mode. For example, on Windows, enter: cd /buildomatic js-upgrade-newdb.bat test /js-6.2-export.zip In test mode, the js-upgrade scripts check your default_master.properties settings and validate your application server location and its ability to connect to your database. Test mode can help you debug issues like an incorrect database password without altering your system. 4.7.2 Output Log Location The js-upgrade script creates an output log that captures both standard and error output. If problems occur during script execution, or you just want to remember which options you chose, open the output log file located here: /buildomatic/logs/js-upgrade- - .log TIBCO Software Inc. 31 TIBCO JasperReports Server Upgrade Guide 4.7.3 Errors If you encounter errors running the js-upgrade script, first look at the output log to see if you can spot the errors. For help, refer to the Troubleshooting appendix of the JasperReports Server Installation Guide. The information in this appendix applies to both js-upgrade scripts and js-install scripts. If you need to modify values in your default_master.properties file, you can simply edit the file. When you run the js-upgrade script again, it uses the new values. 4.8 Starting and Logging into JasperReports Server 6.4 Start your application server. Your database should already be running. 4.8.1 Clearing Your Browser Cache Before you log in, make sure you and your end users clear the browser cache. JavaScript files, which enable the UI elements of JasperReports Server, are typically cached by the browser. Clear the cache to ensure that the newer files are used. 4.8.2 Logging into JasperReports Server Log in using the following URL, user IDs, and passwords: URL: http://localhost:8080/jasperserver-pro User ID Password Description superuser System-wide administrator jasperadmin Administrator for the default organization Your JasperReports Server instance has now been upgraded to 6.4. If you have startup or login problems, refer to the Troubleshooting appendix of the JasperReports Server Installation Guide. 4.9 Additional Tasks to Complete the Upgrade Perform these tasks with the application server shutdown. 4.9.1 Handling JasperReports Server Customizations If you made modifications to the original JasperReports Server application, these configurations are typically found in the WEB-INF/applicationContext-*.xml set of files. You'll need to manually copy configuration changes, like client-specific security classes or LDAP server configurations, from your previous environment and integrate them with your upgraded environment. 32 TIBCO Software Inc. Chapter 4 Upgrading from 4.5 - 6.2 to 6.4 4.9.2 Clearing the Application Server Work Folder Application servers have work folders where JasperReports Server files are compiled and cached and other objects are stored. When you update the WAR file or license, the buildomatic deploy-webapp-pro target should automatically clear the application server’s work directory, but it’s a good practice to double-check. A permission problem, or some other problem, could prevent the clearing of the work folder. To clear the work folder in Tomcat: 1. Change directory to /work. 2. 4.9.3 Delete all the files and folders in this directory. Clearing the Application Server Temp Folder JasperReports Server uses caching to speed operations within the application. Caching files are created and stored in the application server, usually in a temp folder. Clear this temp folder to avoid any post-upgrade conflicts. Typically, the temp folder used by an application server corresponds to the path referenced by the java.io.tmpdir Java system property. For Apache Tomcat the temp folder is /temp. To clear the temp folder in Apache Tomcat: 1. Change directory to /temp 2. 4.9.4 Delete all the files and folders in this directory Clearing the Repository Cache Database Table In the jasperserver database, compiled JasperReports Library resources are cached in the JIRepositoryCache table for increased efficiency at runtime. Because the JasperReports Library JAR is typically updated with each new release, old cached items can get out of date and cause errors at runtime. If you encounter errors that mention a JasperReports Library “local class incompatible,” check your repository cache table. In summary, you can clear your jasperserver database cache table as part of this upgrade process whether or not there are errors. To manually clear the repository cache database table, run a SQL command similar to one shown below: update JIRepositoryCache set item_reference = null; delete from JIRepositoryCache; 4.10 Old Manual Upgrade Steps This section describes the older, manual upgrade steps used before we implemented the js-upgrade shell scripts in release 4.0. They're provided here mainly as a reference for internal use. We recommend using the js-upgrade shell scripts described in the beginning of this chapter instead of these manual commands. Commands Description cd /buildomatic TIBCO Software Inc. 33 TIBCO JasperReports Server Upgrade Guide Commands Description js-ant drop-js-db Deletes and recreates your jasperserver db. Make sure your original database is backed up. js-ant create-js-db js-ant init-js-db-pro js-ant import-minimal-pro js-ant import-upgrade -DimportFile=" " The -DimportFile should point to the and of the js-6.2-export.zip file you created earlier. On Windows, you must use double quotation marks (“) if your path or filename contains spaces. On Linux, you must use double quotation marks, escaped with a backslash (\”) in this case. Note: "import-upgrade" will import resources from the 6.2 instance in a "non-update" mode (so that core resources from 6.4 will stay unchanged). Additionally, the "updatecore-users" option will be applied so that the superuser and jasperadmin users will have the same password as set in the 6.2 instance. 34 js-ant import-sample-data-upgrade-pro (Optional) This step is optional; it loads the new sample data. The old sample data is overwritten, so you may need to redo certain changes such as configuring the sample data sources for your database. js-ant deploy-webapp-pro Deletes the existing older war file, deploys the new war file. TIBCO Software Inc. CHAPTER 5 5.1 UPGRADING JASPERSERVER 4.2.1 OR EARLIER Upgrading from 4.2.1 or Earlier If you're running JasperServer version 4.2.1, your upgrade requires two steps: 1. Upgrade from version 4.2.1 to version 6.3. 2. Upgrade from version 6.3 to version 6.4. The steps for this upgrade are documented in the JasperServer Installation Guide for the 6.3 release. Download the JasperServer 6.3 WAR file distribution zip package to get the relevant files and documentation. The Installation Guide is in the docs folder. Download the JasperServer 6.3 WAR file distribution zip package from TIBCO Jaspersoft Technical Support (http://support.tibco.com) or contact your sales representative. If you're running a JasperServer version earlier than 3.7, first upgrade to 3.7, then to 6.3, then to 6.4. 5.2 Best Practices for Upgrading on Windows The two methods for installing JasperReports Server are: 1. Installing with the Binary Installer and Bundled Components The binary installer is an executable that puts all the components in place to run JasperReports Server. For example, if you take the default installation choices, you'll get the Apache Tomcat application server, the PostgreSQL database and Java execution environment. But keep in mind that these components are specially configured to run a specific version of JasperReports Server. This applies to the Windows Start Menu items created to start and stop JasperReports Server. 2. Installing to Pre-existing Components When installing a “Production” instance of JasperReports Server, you may want to install the main components before you install JasperReports Server. This way you have more control over updating and upgrading components like the application server, database, and Java. Once you put these components in place, you have two options for installing JasperReports Server: a. Use the War File ZIP distribution (file name: TIB_js-jrs_6.4.0_bin.zip) You'll install JasperReports Server to the existing components using the js-install.bat scripts. You'll create a default_master.properties file that specifies the location of the application server and database components. TIBCO Software Inc. 35 TIBCO JasperReports Server Upgrade Guide b. Use the Binary Installer, TIB_js-jrs_6.4.0__installer-windows-x64.exe The installer will prompt you for the location of the application server and database components. If you intend to upgrade your Windows installation with future releases of JasperReports Server, we recommend installing to pre-existing components. This will reduce any post-upgrade confusion caused by the Windows Start Menu showing the older version of JasperReports Server. 36 TIBCO Software Inc. CHAPTER 6 UPGRADING FROM THE COMMUNITY PROJECT If you're running a Community Project (CP) instance of JasperReports Server and want to upgrade to a commercial version of JasperReports Server, follow the instructions in this chapter. This upgrade process uses the JasperReports Server commercial WAR File Distribution release package and the included buildomatic scripts. This CP to commercial upgrade procedure is valid only for upgrade within a major JasperReports Server release, for example 6.0 CP to 6.0 commercial. This chapter contains the following sections: • • • • • • • • 6.1 General Procedure Backing Up Your JasperReports Server CP Instance Exporting Your CP Repository Data Preparing the JasperReports Server 6.4 WAR File Distribution Configuring Buildomatic for Your Database and Application Server Upgrading to the Commercial Version of JasperReports Server 6.4 Starting and Logging into JasperReports Server 6.4 Re-Configuring XML/A Connections (Optional) General Procedure The upgrade procedure consists of the following main steps: 1. Back up your JasperReports Server CP instance. 2. Export your CP repository data. 3. Upgrade your instance to JasperReports Server Commercial. 4. Import your CP repository data. If you customized or extended JasperReports Server CP, you need to keep track of these modifications and integrate them with your JasperReports Server commercial instance after completing the upgrade. TIBCO Software Inc. 37 TIBCO JasperReports Server Upgrade Guide 6.2 Backing Up Your JasperReports Server CP Instance Back up the old JasperReports Server CP WAR file and jasperserver database in case a problem occurs with the upgrade. Perform these steps from the command line in a Windows or Linux shell. These instructions assume you have Tomcat application server and the PostgreSQL or MySQL database. Other application servers require a similar procedure. If you have another database, consult your DB administration documentation for back up information. 6.2.1 Backing Up Your JasperReports Server CP WAR File For example, for Apache Tomcat, back up the jasperserver directory from the /webapps folder: 6.2.2 1. Go to the directory. 2. Make a new directory named js-cp-war-backup. 3. Copy /webapps/ jasperserver to /js-cp-war-backup. 4. Delete the /webapps/jasperserver directory. Backing Up Your JasperReports Server Database Go to the location where you originally unpacked your CP WAR file distribution zip. (Or create a new local folder to hold your backup file.) 1. Go to the directory. 2. Run one of the following commands: • For PostgreSQL on Windows or Linux: cd pg_dump --username=postgres • jasperserver > js-db-cp-dump.sql For MySQL on Windows: mysqldump --user=root --password= jasperserver > js-db-cp-dump.sql For MySQL on Linux: mysqldump --user=root --password= --host=127.0.0.1 jasperserver >jsdb-cp-dump.sql For MySQL, if you receive an error about packet size, see the Troubleshooting appendix of the JasperReports Server Installation Guide. 6.3 Exporting Your CP Repository Data Before exporting your CP repository data, check to see if you have the default_master.properties file in this directory. /buildomatic/default_master.properties This file holds settings specific to your JasperReports Server instance, such as your application server location and your database type and location. If you don't have this file, see 6.5.1, “Example Buildomatic Configuration ,” on page 39. 38 TIBCO Software Inc. Chapter 6 Upgrading from the Community Project To export your CP repository data: 1. Navigate to the buildomatic directory: cd /buildomatic 2. Run buildomatic with the export target: Windows: js-ant.bat export-everything-ce -DexportFile=js-cp-export.zip Linux: ./js-ant export-everything-ce -DexportFile=js-cp-export.zip This operation uses the export option --everything, which collects all your repository data. Remember the path to your exported file. You need to specify it when you import to your commercial JasperReports Server repository. 6.4 Preparing the JasperReports Server 6.4 WAR File Distribution Use the buildomatic scripts included in the commercial 6.4 WAR file distribution release package for the upgrade. Follow these steps to obtain and unpack the commercial 6.4 WAR file distribution ZIP file: 1. The WAR file distribution comes in a compressed ZIP file named TIB_js-jrs_6.4.0_bin.zip. Download the WAR file distribution from TIBCO Jaspersoft Technical Support (http://support.tibco.com) or contact your sales representative. 2. Extract all files from TIB_js-jrs_6.4.0_bin.zip. Choose a destination, such as C:\Jaspersoft on Windows, /home/ on Linux, or /Applications on Mac OSX. After you unpack the WAR File Distribution Zip, the resulting location is known as: 6.5 Configuring Buildomatic for Your Database and Application Server This upgrade procedure uses the buildomatic scripts included with the WAR File Distribution ZIP release package. 6.5.1 Example Buildomatic Configuration The default_master.properties file handles the upgrade configuration. We provide a sample configuration file for each database. You must specify your database credentials and your application server location, and rename the file to default_master.properties. 6.5.1.1 PostgreSQL Example This example uses PostgreSQL (the same general logic applies to other databases). 1. Copy postgresql_master.properties from: /buildomatic/sample_conf 2. Paste the file to: /buildomatic 3. Rename the file to: default_master.properties 4. Edit default_master.properties for your database and application server. Sample property values are: appServerType=tomcat6 (or tomcat7, tomcat5, jboss, glassfish) TIBCO Software Inc. 39 TIBCO JasperReports Server Upgrade Guide appServerDir=c:\\Apache Software Foundation\\tomcat-6.0.26 (for example) dbUsername=postgres dbPassword=postgres dbHost=localhost 6.5.1.2 MySQL Example This example uses MySQL (the same general logic applies to other databases). 1. Copy mysql_master.properties from: 2. Paste the file to: 3. Rename the file to: default_master.properties 4. Edit default_master.properties for your database and application server. Sample property values are: /buildomatic/sample_conf /buildomatic appServerType=tomcat6 (or tomcat7, tomcat5, jboss, glassfish) appServerDir=c:\\Apache Software Foundation\\tomcat-6.0.26 (for example) dbUsername=root dbPassword=password dbHost=localhost 6.6 Upgrading to the Commercial Version of JasperReports Server 6.4 After configuring the default_master.properties file, you can complete the upgrade. Make sure you've backed up your jasperserver database before proceeding. Make sure you've backed up your old JasperReports Server WAR file before proceeding. 1. Stop your application server. 2. Start your database server. 3. Run the following commands: Commands Description cd /buildomatic js-ant drop-js-db js-ant create-js-db js-ant init-js-db-pro js-ant import-minimal-pro 40 The first command deletes your jasperserver db. Make sure it's backed up. The other commands recreate and initialize the database. Adds superuser, Themes, and default tenant structure. TIBCO Software Inc. Chapter 6 Upgrading from the Community Project Commands Description js-ant import-upgrade -DimportFile= /js-cpexport.zip -DimportArgs="--include-server-settings" The -DimportFile argument should point to the js-cp-export.zip file you created earlier. On Windows, you must use double quotation marks (“) if your path or filename contains spaces. On Linux, you must use double quotation marks escaped with a backslash (\”) in this case. js-ant import-sample-data-upgrade-pro (Optional) Loads the 6.4 commercial sample data. js-ant deploy-webapp-cp-to-pro Delete the CP war file, and deploy the commercial (pro) war file. On MySQL, if you receive an error about packet size, see the Troubleshooting appendix of the JasperReports Server Installation Guide. 6.7 Starting and Logging into JasperReports Server 6.4 Before starting the server: 1. Set up the JasperReports Server License. Copy the /jasperserver.license file to the C:\Users\ directory (Windows 7 example) For information about how to set up the license, see the JasperReports Server Installation Guide. 2. Delete any files in the \temp folder. 3. Delete any files, directories, or sub-directories in \work\Catalina\localhost. 4. Delete any jasperserver*.xml files that might exist in \conf\Catalina\localhost. 5. (Optional) Move any existing \logs files into a backup directory to clean up old CP log data. For instructions on clearing directories, see 6.9, “Additional Tasks to Complete the Upgrade,” on page 42. Now start your Tomcat, JBoss, or GlassFish application server. Your database should already be running. 6.7.1 Clearing Your Browser Cache Before you log in, make sure you and your end-users clear the Browser cache. JavaScript files, which enable UI elements of JasperReports Server, are typically cached by the browser. Clear the cache to ensure that the newer files are used. TIBCO Software Inc. 41 TIBCO JasperReports Server Upgrade Guide 6.7.2 Logging into the Commercial Version of JasperReports Server 6.4 Log in using the following URL, user IDs, and passwords: URL: http://localhost:8080/jasperserver-pro User ID Password Description superuser superuser System-wide administrator jasperadmin jasperadmin Administrator for the default organization Your jasperadmin password might be reset to the default setting by the upgrade operation. For example, the jasperadmin password might be reset to jasperadmin. For security reasons, you should change your jasperadmin and superuser passwords to non-default values. Your JasperReports Server instance has now been upgraded from Community Project (CP) to commercial. If startup or login problems occur, refer to the Troubleshooting appendix of the JasperReports Server Installation Guide. 6.8 Re-Configuring XML/A Connections (Optional) XML/A connection definitions contain a username and password for connecting the Web Services to the server. A commercial edition of JasperReports Server supports multi-tenancy, which allows multiple organizations on a single instance. The default organization is organization_1. Each user (except superuser) must belong to a specific organization. After upgrading to the commercial JasperReports Server, users belong to the default organization. You need to update XML/A connection definitions to include the organization the user belongs to. The XML/A connection also specifies an instance URI. You'll need to update this URI to the commercial instance. Edit your XML/A connections as shown in the following examples: • User IDs Change “jasperadmin” to “jasperadmin|organization_1” Change “joeuser” to “joeuser|organization_1” • URI values Change: http://localhost:8080/jasperserver/xmla to http://localhost:8080/jasperserver-pro/xmla 6.9 Additional Tasks to Complete the Upgrade Perform these tasks with the application server shutdown. 42 TIBCO Software Inc. Chapter 6 Upgrading from the Community Project 6.9.1 Handling JasperReports Server Customizations If you made modifications to the original JasperReports Server application, these configurations are typically found in the WEB-INF/applicationContext-*.xml set of files. You'll need to manually copy configuration changes, like client-specific security classes or LDAP server configurations, from your previous environment and integrate them with your upgraded environment. 6.9.2 Clearing the Application Server Work Folder Application servers have work folders where JasperReports Server files are compiled and cached and other objects are stored. When you update the WAR file or license, the buildomatic deploy-webapp-pro target should automatically clear the application server’s work directory, but it’s a good practice to double-check. A permission problem, or some other problem, could prevent the clearing of the work folder. To clear the work folder in Tomcat: 1. Change directory to /work. 2. 6.9.3 Delete all the files and folders in this directory. Clearing the Application Server Temp Folder JasperReports Server uses caching to speed operations within the application. Caching files are created and stored in the application server, usually in a temp folder. Clear this temp folder to avoid any post-upgrade conflicts. Typically, the temp folder used by an application server corresponds to the path referenced by the java.io.tmpdir Java system property. For Apache Tomcat the temp folder is /temp. To clear the temp folder in Apache Tomcat: 1. Change directory to /temp 2. 6.9.4 Delete all the files and folders in this directory Clearing the Repository Cache Database Table In the jasperserver database, compiled JasperReports Library resources are cached in the JIRepositoryCache table for increased efficiency at runtime. Because the JasperReports Library JAR is typically updated with each new release, old cached items can get out of date and cause errors at runtime. If you encounter errors that mention a JasperReports Library “local class incompatible,” check your repository cache table. In summary, you can clear your jasperserver database cache table as part of this upgrade process whether or not there are errors. To manually clear the repository cache database table, run a SQL command similar to one shown below: update JIRepositoryCache set item_reference = null; delete from JIRepositoryCache; TIBCO Software Inc. 43 TIBCO JasperReports Server Upgrade Guide 44 TIBCO Software Inc. APPENDIX A PLANNING YOUR UPGRADE Some of the new and enhanced features in JasperReports Server can affect your deployment, and you should plan your upgrade accordingly. Before upgrading make sure to: • • Review this information carefully and determine how the changes described affect your deployment. Back up your current JasperReports Server installation and repository. The versions and their affected functionality are: • • • • • • • • Changes in 6.4 affect the Impala community connector. Changes in 6.2.1 affect the Impala community connector. Changes in 6.2 affect the default Ad Hoc templates. Changes in 6.1 affect themes. Changes in 6.0.1 affect Spring Security, including external authentication and customizations involving Spring Security. Changes in 6.0 affect custom data sources and security files for Domains. Changes in 5.6.1 affect commercial JDBC drivers. Changes in 5.6 affect commercial JDBC drivers as well as XML/A connections. Changes are cumulative, so review all topics that affect you. For example, if you're upgrading from 5.6 to 6.1, you may be affected by changes in 5.6, 6.0, and 6.0.1. This section describes only those changes that can significantly impact your existing deployment. For an overview of new features, improvements, and bug fixes see the release notes in the root directory of the distribution. For information on how to use the new features, see the JasperReports Server User Guide or the JasperReports Server Administrator Guide. This chapter contains the following sections: • • • • • • • • Changes in 6.4 That May Affect Your Upgrade Changes in 6.2.1 That May Affect Your Upgrade Changes in 6.2 That May Affect Your Upgrade Changes in 6.1 That May Affect Your Upgrade Changes in 6.0.1 That May Affect Your Upgrade Changes in 6.0 That May Affect Your Upgrade Changes in 5.6.1 That May Affect Your Upgrade Changes in 5.6 That May Affect Your Upgrade TIBCO Software Inc. 45 TIBCO JasperReports Server Upgrade Guide A.1 Changes in 6.4 That May Affect Your Upgrade A.1.1 Removal of the Impala Connector JasperReports Server provides new and updated drivers for various databases. In the 6.2 release, the previous connector for Impala that had been available on the Jaspersoft community website was replaced with two new options: • • TIBCO Impala JDBC driver (also called Progress) Simba JDBC driver (Cloudera-endorsed JDBC interface) By default, the new release supports the new JDBC drivers, and the old Impala connector cannot be used. You should update your Impala data sources to use the new drivers. For more information, see the JasperReports Server Administrator Guide. If you wish to continue using the Impala connector that was previously available from the community website, modify the install as described below. 1. Add the following files to the /WEB-INF/lib directory: 2. • hive-service-0.12.0-cdh5.1.3.jar • zookeeper-3.4.5-cdh5.1.3.jar • avro-1.7.5-cdh5.1.3.jar • commons-compress-1.4.1.jar • hadoop-core-1.2.1.jar • hive-ant-0.12.0-cdh5.1.3.jar • hive-common-0.12.0-cdh5.1.3.jar • hive-exec-0.12.0-cdh5.1.3.jar • hive-jdbc-0.12.0-cdh5.1.3.jar • jasperserver-hive-connector-bugfix-SNAPSHOT.jar • js-hive-datasource-1.2.1-cdh5.jar • paranamer-2.3.jar • parquet-hadoop-bundle-1.2.5-cdh5.1.3.jar • xz-1.0.jar Delete the file applicationContext-HiveDatasource.xml from the /WEB-INF directory: If you do not add the files listed, data sources that use the old Impala connector will cause errors when running reports that rely on them. 46 TIBCO Software Inc. Appendix A Planning Your Upgrade A.2 Changes in 6.2.1 That May Affect Your Upgrade A.2.1 Removal of the Impala Connector JasperReports Server provides new and updated drivers for various databases. In this release, the previous connector for Impala that was available on the Jaspersoft community website is replaced with two new options: • • TIBCO Impala JDBC driver (also called Progress) Simba JDBC driver (Cloudera-endorsed JDBC interface) By default, the new release supports the new JDBC drivers, and the old Impala connector cannot be used. You should update your Impala data sources to use the new drivers. For more information, see the JasperReports Server Administrator Guide. If you wish to continue using the Impala connector from the community website, you must replace the following JAR files in the .../WEB-INF/lib directory: Replace With This hive-service-0.13.1.jar hive-service-0.12.0-cdh5.1.3.jar zookeeper-3.4.6.jar zookeeper-3.4.5-cdh5.1.3.jar Unless you replace the files listed in the table, data sources that use the old Impala connector will cause errors when running reports that rely on them. A.3 Changes in 6.2 That May Affect Your Upgrade A.3.1 Renaming of Ad Hoc Templates Due to minor changes to Ad Hoc templates in 6.2, the default template files have been renamed, for example, actual_size.510.jrxml has been renamed actual_size.620.jrxml. During upgrade, templates with an earlier version number are overwritten by the new template. If you have customized the default template and kept the same file name, your changes will be overwritten. To avoid this, make a copy of your customized template with a unique name and upload it to your template directory (by default, Public > Templates) using Add Resource > File > Style Template. In general, if you want to customize the Ad Hoc templates, we recommend you rename the existing template and set the new template as a default, rather than overwriting the existing template. See the JasperReports Server Administrator Guide for more information. TIBCO Software Inc. 47 TIBCO JasperReports Server Upgrade Guide A.4 Changes in 6.1 That May Affect Your Upgrade A.4.1 Changes to Themes The look and feel of the JasperReports Server web interface has been redesigned to modernize the application's appearance. To accomplish this, markup and styles have been modified. As a result of these modifications, custom themes developed for the previous interface will need to be updated for the new interface. The following table lists the changes made to the user interface and describes some of the steps necessary to update custom themes in overrides_custom.css. The main changes are in the banner, body, footer, and login page. The changes to the login page are extensive. Instead of attempting to update an existing login page, you should re-implement the login page in the new default theme. For information on developing new themes, see the JasperReports Server Administrator Guide and the JasperReports Server Ultimate Guide. Table A-1 Updating Themes in JasperReports Server 6.1 Element Classname and Modifications File Notes Banner .banner containers.css Default value: height: 32px containers.css Default value: top: 32px bottom: 17px Give custom value to height Body #frame Set custom top and bottom values that position the body of the application between the banner and footer without overlap This value needs to be equal to or greater than the height of .banner The bottom position needs to be adjusted only if the height of the footer is changed 48 TIBCO Software Inc. Appendix A Planning Your Upgrade Element Classname and Modifications File Notes Banner Logo #logo theme.css Default values: height: 22px width: 176px Give custom values to height and width that match the dimensions of your logo margin-top: 6px margin-right: 4px margin-bottom: 0 margin-left: 8px Adjust margins around the logo if needed Banner Main Navigation .menu.primaryNav .wrap containers.css height: 31px line-height: 31px containers.css height: 32px Set height and line-height to 1px shorter than .banner Banner Main Navigation Home icon .menu.primaryNav #main_home .wrap > .icon Banner Main Navigation Item arrow icon .menu.primaryNav .node > .wrap > .icon Set height to be the same as .banner width: 14px background-position: 0 -164px background-position: 0 -163px (IE8-9) Set values for width and background-position to fit your image. containers.css Set height to your desired value, with the maximum value being the same height measurement as the .banner element. height: 32px background-position: left -79px width: 11px Set background-position and width to a value that properly displays the default or your custom image. Banner Main Navigation Item arrow icon TIBCO Software Inc. .menu.primaryNav .wrap.over .menu.primaryNav .wrap.pressed Set background-position to a value that properly displays the default or your custom image. containers.css background-position is not explicitly defined, the value is cascaded from .menu.primaryNav .node > .wrap > .icon This only needs to be adjusted if you want a different color disclosure indicator for the pressed and over states of the main menu links 49 TIBCO JasperReports Server Upgrade Guide Element Classname and Modifications File Notes Banner Search container #globalSearch.searchLockup controls.css margin-top: 5px Banner Metadata #metalinks li themes.css line-height: 20px Footer #frameFooter containers.css height: 17px Set margin-top to desired value that will vertically center it within the banner. Set line-height to the desired value that will vertically center it within the banner. Set height if you want it to be anything other than the default value. Login page 50 Re-implement in new theme. TIBCO Software Inc. Appendix A Planning Your Upgrade A.5 Changes in 6.0.1 That May Affect Your Upgrade JasperReports Server uses the Spring Security framework to implement security throughout the product. In JasperReports Server 6.0.1, the Spring Security framework was updated from Spring Security 2.0.x to 3.2.5. For many users, this upgrade will have no impact. However, you may need to make some changes if you have implemented the following: • • A.5.1 External authentication – If you have implemented external authentication or single sign-on in your server implementation, you need to update your implementation: • If you implemented external authentication using one of the sample files included in the project, you need to reimplement your changes in the updated sample files in JasperReports Server 6.0.1. • If you implemented a custom external authentication solution, you need to migrate your solution to the new framework. Customizations – If you have customized the server using Spring Security classes, you need to migrate your solution to the new framework. Migrating External Authentication Sample Files If you have implemented external authentication using one of the sample-applicationContext .xml files in the /samples/externalAuth-sample-config directory, do the following to migrate your changes to JasperReports Server 6.0.1: 1. Before upgrading, back up your applicationContext- .xml file (for example, applicationContext-externalAuth-LDAP.xml), located in the /WEB-INF directory of your previous version of JasperReports Server. 2. Update your server installation to JasperReports Server 6.0.1, as described in the JasperReports Server Upgrade Guide. As of JasperReports Server 6.0.1, you can customize the default admin users created when external authentication creates a new organization. Optionally you can also encrypt the admin's password in the configuration files. If you want to encrypt the default password, you need to set this up before installation or upgrade. See the JasperReports Server External Authentication Cookbook and the JasperReports Server Security Guide for more information. 3. In the new installation, locate the sample file that corresponds to the file you implemented previously. For example, if you implemented applicationContext-externalAuth-LDAP.xml, locate /samples/externalAuth-sample-config/sample-applicationContext-externalAuth-LDAP.xml. 4. Rename the JasperReports Server 6.0.1 sample file to remove the sample- prefix. For example, rename sample-applicationContext-externalAuth-LDAP.xml to applicationContext-externalAuth-LDAP.xml. 5. Configure the properties in the new sample file to match the properties in your existing sample file. To do this: a. Locate each bean you modified in the previous version. b. Find the same bean in the JasperReports Server 6.0.1 sample. The names of the beans are the same in each version. c. Copy or re-enter the properties you need for your server, taking care not to copy over class names or class packages. TIBCO Software Inc. 51 TIBCO JasperReports Server Upgrade Guide Although the bean names are the same in the JasperReports Server 6.0.1 sample files, the name and package of the class in many bean definitions have changed. Make sure not to overwrite the new names with the old ones. d. Save the JasperReports Server 6.0.1 sample file. e. Rename the JasperReports Server 6.0.1 sample file to remove sample- prefix. For example, rename sample-applicationContext-externalAuth-LDAP.xml to applicationContext-externalAuth-LDAP.xml. f. Place the modified file in the /WEB-INF directory. A.5.1.1 Wrapper Classes To reduce the impact of future upgrades, we created wrapper classes for the Spring Security classes used in the external authentication sample files. Table A-2, “Wrapper Classes in JasperReports Server 6.0.1,” on page 53 shows the correspondence between Spring Security classes in earlier versions of JasperReports Server and the new wrapper classes in JasperReports Server 6.0.1. A.5.2 Migrating Customizations At a minimum, you need to change the names and paths of the Spring Security classes you reference in any customizations you've made to JasperReports Server. The Spring Security codebase was significantly restructured from 2.x to 3.x. Many classes were moved to new packages and some classes were renamed. Table A-3, “Mapping of Spring Classes from 2.0.x to 3.2.5,” on page 55 shows the mapping from 2.0.x to 3.2 for important Spring Security classes used in JasperReports Server. This table is for information only. It has not been verified with the Spring Security project and is not guaranteed to be correct. Additional information is included in the Spring Security 3.2.5 source code. You can also search the internet. 52 TIBCO Software Inc. Appendix A Planning Your Upgrade A.5.3 Changes to Security Classes in JasperReports Server 6.0.1 Table A-2 Wrapper Classes in JasperReports Server 6.0.1 Spring Security 2.0.x Class 3.x External Authentication Wrappers org.springframework.security.ui.ExceptionTranslationFilter com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.JSExceptionTranslationFilter org.springframework.security.providers.ProviderManager com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.JSProviderManager org.springframework.security.ui.AuthenticationDetailsSourceImpl com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.JSAuthenticationDetailsSourceImpl org.springframework.security.ui.cas.CasProcessingFilterEntryPoint com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.cas.JSCasAuthenticationEntryPoint org.springframework.security.providers.cas.CasAuthenticationProvider com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.cas.JSCasAuthenticationProvider org.jasig.cas.client.validation.Cas20ServiceTicketValidator com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. jasig.JSCas20ServiceTicketValidator org.springframework.security.providers.cas.cache.EhCacheBasedTicketCache com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.JSEhCacheBasedTicketCache org.springframework.cache.ehcache.EhCacheFactoryBean com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.JSEhCacheFactoryBean org.springframework.security.userdetails.ldap.LdapUserDetailsService com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.ldap.JSLdapUserDetailsService TIBCO Software Inc. 53 TIBCO JasperReports Server Upgrade Guide Spring Security 2.0.x Class 3.x External Authentication Wrappers org.springframework.security.ldap.search.FilterBasedLdapUserSearch com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.ldap.JSFilterBasedLdapUserSearch org.springframework.security.ldap.populator.DefaultLdapAuthoritiesPopulator com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.ldap.JSDefaultLdapAuthoritiesPopulator org.springframework.security.ui.cas.ServiceProperties com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.cas.JSCASServiceProperties org.springframework.security.providers.ldap.authenticator.BindAuthenticator com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.ldap.JSBindAuthenticator org.springframework.security.ldap.populator.DefaultLdapAuthoritiesPopulator com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.ldap.JSDefaultLdapAuthoritiesPopulator org.springframework.security.providers.ldap.LdapAuthenticationProvider com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.ldap.JSLdapAuthenticationProvider org.springframework.http.client.SimpleClientHttpRequestFactory com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.JSSimpleClientHttpRequestFactory org.springframework.jdbc.datasource.DriverManagerDataSource com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.jdbc.JSDriverManagerDataSource org.springframework.security.providers.preauth.PreAuthenticatedAuthenticationProvider com.jaspersoft.jasperserver.api.security.externalAuth.wrappers. spring.preauth.JSPreAuthenticatedAuthenticationProvider 54 TIBCO Software Inc. Appendix A Planning Your Upgrade Table A-2 shows the 2.0.x Spring Security classes. Note that three of the Spring Security classes in the table have moved to different packages: ExceptionTranslationFilter moved to org.springframework.security.web.access.ExceptionTranslationFilter ProviderManager moved to org.springframework.security.authentication.ProviderManager AuthenticationDetailsSourceImpl moved to org.springframework.security.authentication.AuthenticationDetailsSourceImpl Table A-3 Mapping of Spring Classes from 2.0.x to 3.2.5 Spring Security 2.0.x Class Spring Security 3.2 Class org.springframework.security.context.SecurityContextHolder org.springframework.security.core.context.SecurityContextHolder org.springframework.security.Authentication org.springframework.security.core.Authentication org.springframework.security.util.FilterChainProxy org.springframework.security.web.FilterChainProxy org.springframework.security.providers.anonymous. AnonymousProcessingFilter org.springframework.security.web.authentication. AnonymousAuthenticationFilter org.springframework.security.ui.basicauth. BasicProcessingFilter org.springframework.security.web.authentication.www. BasicAuthenticationFilter org.springframework.security.ui.basicauth. BasicProcessingFilterEntryPoint org.springframework.security.web.authentication.www. BasicAuthenticationEntryPoint org.springframework.security.ui.ExceptionTranslationFilter org.springframework.security.web.access.ExceptionTranslationFilter org.springframework.security.ui.webapp. AuthenticationProcessingFilterEntryPoint org.springframework.security.web.authentication. LoginUrlAuthenticationEntryPoint org.springframework.security.ui.webapp. AuthenticationProcessingFilter org.springframework.security.web.authentication. UsernamePasswordAuthenticationFilter TIBCO Software Inc. 55 TIBCO JasperReports Server Upgrade Guide Spring Security 2.0.x Class Spring Security 3.2 Class org.springframework.security.context. HttpSessionContextIntegrationFilter org.springframework.security.web.context. SecurityContextPersistenceFilter org.springframework.security.vote.AffirmativeBased org.springframework.security.access.vote.AffirmativeBased org.springframework.security.vote.AuthenticatedVoter org.springframework.security.access.vote.AuthenticatedVoter org.springframework.security.intercept.web. FilterSecurityInterceptor org.springframework.security.web.access.intercept. FilterSecurityInterceptor com.jaspersoft.jasperserver.api.security.JSSwitchUserProcessingFilter com.jaspersoft.jasperserver.war.common.JSSwitchUserProcessingFilter org.springframework.security.acl.basic.AclObjectIdentity org.springframework.security.acls.model.ObjectIdentity org.springframework.security.GrantedAuthority org.springframework.security.core.GrantedAuthority org.springframework.security.userdetails.User org.springframework.security.core.userdetails.User org.springframework.security.core. AuthenticationServiceException org.springframework.security.authentication. AuthenticationServiceException org.springframework.security.AuthorizationServiceException org.springframework.security.access.AuthorizationServiceException org.springframework.security.providers. UsernamePasswordAuthenticationToken org.springframework.security.authentication. UsernamePasswordAuthenticationToken org.springframework.security.core.GrantedAuthorityImpl org.springframework.security.core.authority.GrantedAuthorityImpl org.springframework.security.vote.BasicAclEntryVoter org.springframework.security.acls.AclEntryVoter org.springframework.security.vote.AccessDecisionVoter org.springframework.security.access.AccessDecisionVoter org.springframework.security.acl.AclEntry org.springframework.security.acls.model.Acl 56 TIBCO Software Inc. Appendix A Planning Your Upgrade Spring Security 2.0.x Class Spring Security 3.2 Class org.springframework.security.ConfigAttributeDefinition Collection org.springframework.security.ConfigAttribute org.springframework.security.access.ConfigAttribute org.springframework.security.AuthorizationServiceException org.springframework.security.access.AuthorizationServiceException org.springframework.security.afterinvocation.AfterInvocationProvider org.springframework.security.access.AfterInvocationProvider org.springframework.security.AccessDeniedException org.springframework.security.access.AccessDeniedException org.springframework.security.acl.AclManager org.springframework.security.acls.model.AclService org.springframework.security.concurrent.SessionRegistry org.springframework.security.core.session.SessionRegistry org.springframework.security.concurrent.SessionInformation org.springframework.security.core.session.SessionInformation org.springframework.security.SecurityConfig org.springframework.security.access.SecurityConfig org.springframework.security.AuthorizationServiceException org.springframework.security.access.AuthorizationServiceException org.springframework.security.providers.encoding.PasswordEncoder org.springframework.security.authentication.encoding.PasswordEncoder org.springframework.security.ui.WebAuthenticationDetails org.springframework.security.web.authentication.WebAuthenticationDetails org.springframework.security.providers.dao.DaoAuthenticationProvider org.springframework.security.authentication.dao.DaoAuthenticationProvider org.springframework.security.ui.switchuser. SwitchUserGrantedAuthority org.springframework.security.web.authentication.switchuser. SwitchUserGrantedAuthority org.springframework.security.vote.AbstractAclVoter org.springframework.security.access.vote.AbstractAclVoter org.springframework.security.providers.anonymous. AnonymousAuthenticationToken org.springframework.security.authentication. AnonymousAuthenticationToken TIBCO Software Inc. 57 TIBCO JasperReports Server Upgrade Guide Spring Security 2.0.x Class Spring Security 3.2 Class org.springframework.security.afterinvocation.AfterInvocationProvider org.springframework.security.access.AfterInvocationProvider org.springframework.security.AccessDeniedException org.springframework.security.access.AccessDeniedException org.springframework.security.core.AuthenticationManager org.springframework.security.authentication.AuthenticationManager org.springframework.security.ui.cas.CasProcessingFilter org.springframework.security.cas.web.CasAuthenticationFilter org.springframework.security.ui.rememberme.NullRememberMeServices org.springframework.security.web.authentication.NullRememberMeServices org.springframework.security.util.UrlUtils org.springframework.security.web.util.UrlUtils org.springframework.security.providers.AuthenticationProvider org.springframework.security.authentication.AuthenticationProvider org.springframework.security.userdetails.jdbc.JdbcDaoImpl org.springframework.security.core.userdetails.jdbc.JdbcDaoImpl org.springframework.security.BadCredentialsException org.springframework.security.authentication.BadCredentialsException org.springframework.security.userdetails.memory.UserAttribute org.springframework.security.core.userdetails.memory.UserAttribute org.springframework.security.context.SecurityContext org.springframework.security.core.context.SecurityContext org.springframework.security.providers.TestingAuthenticationToken org.springframework.security.authentication.TestingAuthenticationToken org.springframework.security.userdetails.ldap.LdapUserDetails org.springframework.security.ldap.userdetails.LdapUserDetails org.springframework.security.vote.RoleVoter org.springframework.security.access.vote.RoleVoter org.springframework.security.intercept.method.aopalliance. MethodSecurityInterceptor org.springframework.security.access.intercept.aopalliance. MethodSecurityInterceptor org.springframework.security.vote.UnanimousBased org.springframework.security.access.vote.UnanimousBased 58 TIBCO Software Inc. Appendix A Planning Your Upgrade Spring Security 2.0.x Class Spring Security 3.2 Class org.springframework.security.afterinvocation.AfterInvocationProviderManager org.springframework.security.access.intercept.AfterInvocationProviderManager org.springframework.security.providers.ProviderManager org.springframework.security.authentication.ProviderManager org.springframework.security.ui.AuthenticationDetailsSourceImpl org.springframework.security.authentication.AuthenticationDetailsSourceImpl org.springframework.security.afterinvocation. BasicAclEntryAfterInvocationCollectionFilteringProvider org.springframework.security.acls.afterinvocation .AclEntryAfterInvocationCollectionFilteringProvider org.springframework.security.userdetails.memory.InMemoryDaoImpl org.springframework.security.core.userdetails.memory.InMemoryDaoImpl org.springframework.security.event.authentication.LoggerListener org.springframework.security.authentication.event.LoggerListener org.springframework.security.wrapper. SecurityContextHolderAwareRequestFilter org.springframework.security.web.servletapi. SecurityContextHolderAwareRequestFilter org.springframework.security.afterinvocation. BasicAclEntryAfterInvocationProvider org.springframework.security.acls.afterinvocation. AclEntryAfterInvocationProvider org.springframework.security.concurrent.SessionRegistryImpl org.springframework.security.core.session.SessionRegistryImpl TIBCO Software Inc. 59 TIBCO JasperReports Server Upgrade Guide A.6 Changes in 6.0 That May Affect Your Upgrade A.6.1 Changes to Custom Data Sources Changes to the Spring configuration in JasperReports Server 6.0 can affect custom data sources. This change specifically affects beans which implement the ReportDataSourceServiceFactory interface . Prior to JasperReports Server 6.0, if code in JasperReports Server accessed a bean of this type, it got the actual instance of the Spring bean as configured in the Spring XML file, and it could be cast to the concrete class. In JasperReports Server 6.0 and later, beans of this type are intercepted and other code sees a dynamic proxy instead of the actual bean. Since proxies can only represent interfaces, existing code that tries to cast the bean to a concrete class will break. Casting is usually done to get access to methods on a more specific class or interface. You can update your custom data sources as follows: • • A.6.2 To access methods on an existing interface, either do a cast to that interface, or inject the property using the existing interface so no cast is needed. To access methods not on an existing interface, create an interface with the methods you need and have the target object implement that interface. Changes to Domain Security Files In JasperReports Server 6.0, we added support for hierarchical attributes, which can be assigned at the server, organization, or user level. Existing Domain security files only detect attributes assigned at the user level. Even if other attributes are present, the security file does not detect them. See the section "Working with Hierarchical Attributes" in the JasperReports Server Security Guide for information on how to update your security file. A.7 Changes in 5.6.1 That May Affect Your Upgrade In 5.6.1, Jaspersoft added TIBCO JDBC drivers for the following commercial databases: • • • • Oracle SQL Server DB2 Hive — available as a data source only; cannot be used for the JasperReports Server repository database. The new drivers have the following impact: • • • 60 If you're upgrading and want to use your current driver for the repository, you must copy the driver to the correct location and modify default_master.properties for the driver you choose. See the section on your upgrade procedure for more information. If you're using WebLogic or WebSphere and want to use a TIBCO driver, you need to set up the driver in your application server console. See the JasperReports Server Installation Guide or the JasperReports Server Administrator Guide for more information. For supported Hive platforms other than Impala and Cloudera 5, you must use the TIBCO JDBC driver. TIBCO Software Inc. Appendix A Planning Your Upgrade A.8 Changes in 5.6 That May Affect Your Upgrade The following changes in 5.6 and later can significantly affect your deployment: • • A.8.1 Removal of commercial JDBC drivers: if you're using a commercial JDBC driver, you need to copy it to the correct location in your upgraded JasperReports Server. Changes to OLAP engine: Due to change between versions of the OLAP engine, if you use Jaspersoft OLAP's XML/A functionality to connect to a remote JasperReports Server's XML/A sources, you must take additional steps to complete your upgrade to 5.6. Removal of Commercial JDBC Drivers The following commercial database drivers were removed from the JasperReports Server 5.6 package: Oracle, SQL Server, or DB2. You'll need to obtain a JDBC driver before running the upgrade. In this case, for Oracle, because you most likely have an Oracle JDBC driver in your existing JasperReports Server instance, it's simplest to copy it from that location: Copy from: /buildomatic/conf_source/db/oracle/jdbc/ .jar Copy to: /buildomatic/conf_source/db/oracle/jdbc A.8.2 Changes to OLAP Engine If you use Jaspersoft OLAP's XML/A functionality to connect to a remote JasperReports Server’s XML/A sources, you must take additional steps to complete your upgrade to 5.6. This is because of a change between versions of the OLAP engine. Once the new version of JasperReports Server is installed and running, locate all the XML/A connections that point to a remote JasperReports Server instance. Then edit the DataSource field to specify JRS as the DataSource portion of its value. For example, in previous versions, the Foodmart XML/A connection specified: Provider=Mondrian;DataSource=Foodmart; During upgrade, this connection must be changed to: Provider=Mondrian;DataSource=JR Note that for 5.6, the trailing semicolon should be removed (the older 5.5 syntax includes a semicolon at the end). For more information about creating and editing XML/A connections, refer to the Jaspersoft OLAP User Guide. Note that if your instance hosts multiple organizations, XML/A connections will fail for superuser. This limitation applies exclusively to the superuser account. To test connections in servers that host multiple organizations, we recommend that you log in as jasperadmin or another administrative account other than superuser. One reason you might have XML/A connections to remote instances of JasperReports Server is to create a loadbalanced Jaspersoft OLAP environment. For more information, refer to the Jaspersoft OLAP Ultimate Guide. TIBCO Software Inc. 61 APPENDIX B WORKING WITH JDBC DRIVERS This section describes how to set up your installation to use a driver other than the default driver. B.1 Open Source JDBC Drivers For open source JDBC drivers, buildomatic is set up to use a single default driver. If you want to use a driver other than the default driver, you can modify the buildomatic property files that determine the default JDBC driver. The buildomatic JDBC driver property files are set up to point to a specific driver jar. This allows for multiple driver jar files in the same buildomatic/conf_source/db/ /jdbc folder. During the installation procedure only the default driver jar is copied to your application server. If you want to use a newer JDBC driver version or a different JDBC driver, you can modify the buildomatic properties seen in your default_master.properties file. B.1.1 PostgreSQL Example The buildomatic/conf_source/db/postgresql/jdbc folder contains these driver files: postgresql-9.2-1002.jdbc3.jar postgresql-9.2-1002.jdbc4.jar If, for instance, you want to change the default driver used by PostgreSQL from type jdbc4 to jdbc3, edit your default_master.properties file: Overlay upgrade: /buildomatic/default_master.properties Other upgrade: /buildomatic/default_master.properties Uncomment and change: # maven.jdbc.version=9.2-1002.jdbc4 To: maven.jdbc.version=9.2-1002.jdbc3 When you next run a buildomatic command, such as deploy-webapp-pro, the jdbc3 driver will be copied to your application server. TIBCO Software Inc. 62 TIBCO JasperReports Server Upgrade Guide B.1.2 MySQL Example The buildomatic/conf_source/db/mysql/jdbc folder contains this driver file: mariadb-java-client-1.1.2.jar If, for instance, you want to use a JDBC driver built and distributed by the MySQL project, such as mysqlconnector-java-5.1.30-bin.jar, you first need to download the driver from the MySQL Connector/J download location: https://dev.mysql.com/downloads/connector/j/ Next, change your buildomatic configuration properties to point to this new driver. Edit your default_master.properties file: Overlay upgrade: /buildomatic/default_master.properties Other upgrade: /buildomatic/default_master.properties Uncomment and change: # jdbcDriverClass=com.mysql.jdbc.Driver # maven.jdbc.groupId=mysql # maven.jdbc.artifactId=mysql-connector-java # maven.jdbc.version=5.1.30-bin To: jdbcDriverClass=com.mysql.jdbc.Driver maven.jdbc.groupId=mysql maven.jdbc.artifactId=mysql-connector-java maven.jdbc.version=5.1.30-bin B.2 Commercial JDBC Drivers As of version 5.6.1, JasperReports Server includes the TIBCO JDBC drivers for the following commercial databases. You can connect to these databases using the TIBCO JDBC driver without additional steps. The drivers are located in the \buildomatic\conf_source\db\ \jdbc directory, where X.Y is the version number: • • • Oracle – TIoracle-X.Y.jar SQL Server – TIsqlserver-X.Y.jar DB2 – TIdb2-X.Y.jar These drivers require a valid JasperReports Server license. The driver is for use by JasperReports Server only, and after installation or upgrade, the driver jar must be located under the jasperserver-pro directory, for example /tomcat/jasperserver-pro/WEB-INF/lib. If you're using the default settings for the driver, you don't need to edit default_master.properties. You can also choose to use the driver supplied by the database vendor as described below. For upgrade, this section assumes you have already downloaded the jar file for the database you want to use. 63 TIBCO Software Inc. Appendix B Working With JDBC Drivers B.2.1 Oracle Example 1. Copy your Oracle driver to the following directory: Overlay upgrade: /buildomatic/conf_source/db/oracle/native.jdbc Other upgrade: /buildomatic/conf_source/db/oracle/native.jdbc 2. Change to the /buildomatic directory and open default_master.properties in a text editor. 3. Go to the Additional Settings section in this file. 4. Go to the first setup item, Setup Standard Oracle JDBC Driver. 5. Follow the instructions to uncomment the required properties and enable your driver. The following example shows how to set up default_master.properties to point to a driver named ojdbc6-11.2.0.3.jar using SID: # 1) Setup Standard Oracle JDBC Driver # # Uncomment and modify the value to native jdbcDriverMaker=native # # Uncomment and modify the value in order to change the default # 1a) Driver will be found here: /buildomatic/conf_source/db/oracle/native.jdbc # maven.jdbc.groupId=oracle maven.jdbc.artifactId=ojdbc6 maven.jdbc.version=11.2.0.3 If you're using an Oracle service name instead of an SID, uncomment the line serviceName= and add your service name. 6. B.2.2 Save the default_master.properties file. SQL Server Example 1. Copy your SQL Server driver to the following directory: Overlay upgrade: /buildomatic/conf_source/db/sqlserver/native.jdbc Other upgrade: /buildomatic/conf_source/db/sqlserver/native.jdbc 2. Change to the /buildomatic directory and open default_master.properties in a text editor. 3. Go to the Additional Settings section in this file. 4. Go to the first setup item, Setup Standard SQL Server JDBC Driver. TIBCO Software Inc. 64 TIBCO JasperReports Server Upgrade Guide 5. Uncomment the required properties and enable your driver. The following example shows how to set up default_master.properties to point to a driver named sqljdbc-1.6.jar: # 1) Setup Standard SQLServer JDBC Driver # # Uncomment and modify the value to native jdbcDriverMaker=native # # Uncomment and modify the value in order to change the default # Driver will be found here: /buildomatic/conf_source/db/sqlserver/native.jdbc # maven.jdbc.groupId=sqlserver maven.jdbc.artifactId=sqljdbc maven.jdbc.version=1.6 6. B.2.3 Save the default_master.properties file. DB2 Example 1. Copy your DB2 driver to the following directory: Overlay upgrade: /buildomatic/conf_source/db/db2/native.jdbc Other upgrade: /buildomatic/conf_source/db/db2/native.jdbc 2. Change to the /buildomatic directory and open default_master.properties in a text editor. 3. Go to the Additional Settings section in this file. 4. Go to the first setup item, Setup Standard DB2 JDBC Driver. 5. Uncomment the required properties and enable your driver. # 1) Setup Standard DB2 JDBC Driver # # Uncomment and modify the value to native jdbcDriverMaker=native # # Uncomment and modify the value in order to change the default # Driver will be found here: /buildomatic/conf_source/db/db2/native.jdbc # maven.jdbc.groupId=ibm maven.jdbc.artifactId=db2jcc maven.jdbc.version=9.7 6. Add the following additional properties, setting the correct values for your installation. For example: db2.driverType=4 db2.fullyMaterializeLobData=true db2.fullyMaterializeInputStreams=true db2.progressiveStreaming=2 db2.progressiveLocators=2 dbPort=50000 js.dbName=JSPRSRVR sugarcrm.dbName=SUGARCRM foodmart.dbName=FOODMART 7. 65 Save the default_master.properties file. TIBCO Software Inc.
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : No Page Count : 65 Page Mode : UseOutlines Language : en-US Producer : madbuild Create Date : 2017:01:09 10:28:15-08:00 Modify Date : 2017:01:09 10:28:15-08:00 Title : TIBCO JasperReports Server Upgrade Guide Author : TIBCO Software Inc. Subject :EXIF Metadata provided by EXIF.tools