Upgrade Guide to ReportServer 3.0.3-beta

In this guide we describe how to upgrade ReportServer 3.0.2 installations (RS3.0.2-5855) to ReportServer 3.0.3-beta. 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.2.

If you want to perform a new installation: You can install 3.0.3-beta analogously to 3.0.2, as described in the installation guides: Linux or Windows. Instead of decompressing RS3.0.2-5855.zip, decompress RS-3.0.3-NIGHTLY.zip to the tomcat webapps directory, and then perform the database upgrade described below by executing the sql statements for your database.

Since this is a beta release, install only in a test system. Backup all your data before installing.

In ReportServer 3.0.3, the Saiku and Mondrian libraries were upgraded to 3.8 and 4.3.0.1, respectively. These are in most of the cases not backward compatible. This means the following:
  • Pivot table variants: you have to create new variants, configure them, and save them again.
  • Mondrian datasources: if your Mondrian XML schema is defined in reportserver, you shall upgrade the schema to version 4, i.e. it must contain: "<Schema name="YourSchema" metamodelVersion="4.0">". More information here.

In order to use reportserver-3.0.3-beta with Oracle, the following jars (or newer versions) are needed: ojdbc6.jar, orai18n.jar, xdb6.jar and xmlparserv2.jar. These are needed because of the new XML/JSON support. Please download and copy them to the WEB-INF/lib directory.

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.2 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.

The Upgrade

To upgrade ReportServer, follow these steps.

  1. Download ReportServer 3.0.3-beta (download links are available on our 3.0.3-beta page.).
  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.3-beta 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.
  6. Execute the following sql statements (one by one!) to upgrade your reportserver database. You may have to change them depending on the database you are using. Note that with the 3.0.3 release (not beta), this process will be automatic.
      
    alter table RS_SAIKU_REPORT add hide_parents boolean null;
    update RS_SAIKU_REPORT set hide_parents = true;
    alter table RS_SAIKU_REPORT modify  column hide_parents boolean not null;
    
    alter table RS_SAIKU_REPORT_A add hide_parents boolean null;
    update RS_SAIKU_REPORT_A set hide_parents = true;
    
    alter table RS_TABLE_REPORT add hide_parents boolean null;
    update RS_TABLE_REPORT set hide_parents = true;
    alter table RS_TABLE_REPORT modify column hide_parents boolean not null;
    
    alter table RS_TABLE_REPORT_A add hide_parents boolean null;
    update RS_TABLE_REPORT_A set hide_parents = true;
    
    alter table RS_SCHED_ACTION_MAIL_REPORT add compress boolean null;
    							
  7. Completely delete your browser's cache to ensure you will get the newest files.
  8. Start up Tomcat

This completes the Upgrade to ReportServer 3.0.3-beta. To ensure that installation was successful have a look at your Tomcat log files.

Happy Reporting