Upgrade Guide to ReportServer 3.0.2

In this guide we describe how to upgrade ReportServer 3.0.1 installations (RS3.0.1-5834) to ReportServer 3.0.2. This guide is valid for both ReportServer Enterprise Edition and ReportServer Community Edition as well as for manual installations and Bitnami installer installations. Note that this guide is only valid for upgrades from version 3.0.1. To upgrade from ReportServer 2.2.2 please follow the instructions given here for a manual upgrade and here for an upgrade of the Bitnami stack.

Before we continue, it is always adviseable to have a backup of your system.

The Upgrade in a Nutshell

The upgrade basically consists of replacing the webapp files of ReportServer, that is, the files under TOMCAT/webapps/reportserver (or TOMCAT/webapps/ROOT, depending on your installation) are removed and the freshly downloaded files are copied there instead. In the following we explain the upgrade in detail

Preconditions

In this upgrade guide we assume that you are working with an externalized configuration directory as described in Chapter 5 of the configuration guide. We are also assuming that you use Tomcat as application server. If you installed ReportServer 3.0.1 via the Bitnami installer or followed the best practice tutorial for Linux or Windows. If you are not yet using an external configuration directory, this is a good point to change your setup. As for this upgrade, the main difference is that you do not need to worry about your configuration changes, but can simply do a one-step copy and paste upgrade.

For Bitnami users: We here describe how to upgrade ReportServer without upgrading the entire Bitnami stack. If you want to upgrade the entire stack, please follow the steps outlined in the ReportServer Bitnami Upgrade Guide.

The Upgrade

To upgrade ReportServer, follow these steps.

  1. Download ReportServer 3.0.2 (download links are available on our download page, or in the support portal).
  2. Stop your ReportServer instance.
  3. Go to the webapps directory of Tomcat and there to the directory in which ReportServer is installed. If you used the Bitnami installer this is
    INSTALLATION DIRECTORY/apache-tomcat/webapps/reportserver
    If you followed the installation tutorial this would be
    TOMCAT DIRECTORY/webapps/ROOT
    To check that you have the right folder confirm that this folder contains amongst others a file called ReportServer.html and a folder called ddl.
  4. Clear out the above folder, that is, remove the entire contents.
  5. Unzip ReportServer 3.0.2 and copy everything to the now empty folder. The structure should be identical to before, that is, you should once more find a file called ReportServer.html and a folder called ddl.
  6. Start up Tomcat

This completes the Upgrade to ReportServer 3.0.2. To ensure that installation was successful have a look at your Tomcat log files. Startup should look similar to the following

  _____                       _    _____                            ______       _                       _          
 |  __ \                     | |  / ____|                          |  ____|     | |                     (_)         
 | |__) |___ _ __   ___  _ __| |_| (___   ___ _ ____   _____ _ __  | |__   _ __ | |_ ___ _ __ _ __  _ __ _ ___  ___ 
 |  _  // _ \ '_ \ / _ \| '__| __|\___ \ / _ \ '__\ \ / / _ \ '__| |  __| | '_ \| __/ _ \ '__| '_ \| '__| / __|/ _ \
 | | \ \  __/ |_) | (_) | |  | |_ ____) |  __/ |   \ V /  __/ |    | |____| | | | ||  __/ |  | |_) | |  | \__ \  __/
 |_|  \_\___| .__/ \___/|_|   \__|_____/ \___|_|    \_/ \___|_|    |______|_| |_|\__\___|_|  | .__/|_|  |_|___/\___|
            | |                                                                              | |                    
            |_|                                                                              |_|                    

Version: RS3.0.2-5855 2016-05-29-17-55-24
Code Version: 2016-05-29-17-55-24
Java Version: Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14 (1.8)
VM Args: -Djava.util.logging.config.file=/Applications/reportserver-3.0.2-0/apache-tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms512M -Xmx1536M -Drs.configdir=/Applications/reportserver-3.0.2-0/apps/reportserver/reportserver-conf -Dfile.encoding=UTF8 -Djdk.tls.ephemeralDHKeySize=2048 -Djava.endorsed.dirs=/Applications/reportserver-3.0.2-0/apache-tomcat/endorsed -Dcatalina.base=/Applications/reportserver-3.0.2-0/apache-tomcat -Dcatalina.home=/Applications/reportserver-3.0.2-0/apache-tomcat -Djava.io.tmpdir=/Applications/reportserver-3.0.2-0/apache-tomcat/temp
rs.configdir: /Applications/reportserver-3.0.2-0/apps/reportserver/reportserver-conf (OK)

### DB Config ###
hibernate.dialect: net.datenwerke.rs.utils.hibernate.MySQL5Dialect (OK)
hibernate.connection.driver_class: com.mysql.jdbc.Driver (OK)
hibernate.connection.url: jdbc:mysql://127.0.0.1:3309/bitnami_reportserver (OK)
hibernate.connection.username: bn_reportserver
hibernate.connection.password: **********
hibernate.default_schema: 

Connection Test: OK
Schema Version: RS3.0-7

12:53:33.163 INFO  n.datenwerke.rs.EnvironmentValidator - Performing database update RS3.0-7 -> RS3.0-8
12:53:33.164 INFO  n.datenwerke.rs.EnvironmentValidator - Running script RS3.0-8-MySQL5_UPDATE.sql
12:53:33.344 INFO  n.datenwerke.rs.EnvironmentValidator - Validating database schema...

The important bit is the the third to last row which inidcates that the database upgrade script was successfully executed. Note that this only happens once after the upgrade and that from then on any startup would show an updated schema version, that is:

Schema Version: RS3.0-8

Happy Reporting