Upgrading from 3.5 or Earlier
If you are running JasperServer version 3.5, you must upgrade in two steps:
|1.||Upgrade from version 3.5 to version 3.7.|
|2.||Upgrade from version 3.7 to version 6.0.|
The steps to perform this upgrade are documented in the JasperServer Installation Guide for the 3.7 release. Download the JasperServer 3.7 WAR file distribution zip package to get the relevant files and documentation. The Installation Guide is in the docs folder.
If you are running a JasperServer version earlier than 3.5, first upgrade to 3.7, then to 6.0.
Best Practices for Upgrading under Windows
There are two standard procedures for installing JasperReports Server. The two installation methods are the following:
|1.||Installing with the Binary Installer and Bundled Components|
The binary installer is an executable which can put all of the components in place to run JasperReports Server. So, for instance, if you take the default choices during the installation, you will get the Apache Tomcat application server, the PostgreSQL database and Java execution environment.
However, it should be kept in mind that these components are specially configured to run JasperReports Server. These components are also “hard coded” so that they apply to a specific version of JasperReports Server. This is true with the Windows Start Menu items created to start and stop JasperReports Server.
|2.||Installing to Pre-existing Components|
When installing a “Production” type instance of JasperReports Server, it is common to pre-install the main components before installing JasperReports Server. This is because the System Administrator will have more control over updating and upgrading these components such as Apache Tomcat (or any other certified application server), PostgreSQL (or any other certified database) and Java.
Once the Administrator puts these pre-existing components in place, there are two ways to install JasperReports Server:
|a.||Using the War File ZIP distribution (file name:
JasperReports Server will be installed to the existing components using the js-install.bat scripts. The Administrator will create a default_master.properties file that will specify where to find the application server and database components.
|b.||Using the Binary Installer (file name:
The installer will prompt the Administrator to specify where to find the application server and database components.
If you are installing JasperReports Server under the Windows operating system and you intend to have this be a long running instance that will be upgraded with future releases then it is recommended that you install to pre-existing components. This will reduce any confusion that might be caused after an upgrade is completed by having Windows Start Menu items that show an older version (that is, the originally installed version number) of JasperReports Server.