Have any questions?
+44 1234 567 890
Upgrade Guide to ReportServer 6.0.0
In this guide we describe how to upgrade ReportServer installations to the latest ReportServer 6.0.0 version. This upgrade guide is valid for ReportServer installations 5.0.0 and higher. This tutorial is valid both for Enterprise and Community versions, as well as for manual and installer package installations.
If you want to perform a new installation check here: Linux or Windows.
Backup all your data before upgrading.
We've introduced OIDC as a new feature in ReportServer 6.0. Please add 'rs.security.authentication.mode' to your reportserver.properties and choose your type of authentication mode as described in the ReportServer 6.0 Installation Guide for Linux und Windows.
In order to use ReportServer 6.0.0 with Oracle, the following jars (or newer versions) are needed: ojdbc8.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. Note: we recommend to use ojdbc7.jar or newer because of this jdbc driver incompatibility with null parameters in BIRT reports.
Default configuration files are created on first run of ReportServer. Later, when upgrading ReportServer to a newer version, it is probable that newly added configuration files will be missing (i.e. all configuration files added between the version originally installed and the version upgraded to). You can use the "diffconfigfiles" command for finding out these configuration files, check the Administration Guide for details. Note that default values are used for configuration files that are not found.
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.
Since ReportServer 5 we also use Java 21 or higher. That means we also have to configure a higher java configuration too.
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 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 users of the installer packages: We here describe how to upgrade ReportServer without upgrading the entire Bitnami stack.
The Upgrade
To upgrade ReportServer, follow these steps.
- Download the newest version of ReportServer 6.0.0
- Stop your ReportServer instance.
- 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.
- Clear out the above folder, that is, remove the entire contents. If you do not use external configuration, all your drivers will be deleted, since the whole directory is being replaced by the downloaded one. Backup them to easily add them later. These are found on the WEB-INF/lib directory of your reportserver installation.
- Unzip ReportServer 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.
- Completely delete your browser's cache (including all temporary internet files!!!) to ensure you will get the newest files. If you get any error of this type: "Type 'net.datenwerke.rs.base.client.dbhelper.dto.DatabaseHelperDto' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer.For security purposes, this type will not be serialized.: instance = net.datenwerke.rs.base.client.dbhelper.dto.DatabaseHelperDto@62cbf40f at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:667)" you have to delete all browser's cache including all temporary internet files.
- now install the new Java Version 21 and use it for ReportServer (if you are coming from a version older than 5.x.x). On Linux:
$ sudo apt-get update
$ sudo apt install openjdk-21-jdk
$ sudo ln -s /usr/lib/jvm/java-1.21.0-openjdk-amd64 /usr/lib/jvm/default-java
- Check the tomcat configuration (if you are coming from a version older than 5.x.x)
With Java 21 our old trashhandler doesn't work anymore. Thats why we have to delete it in our tomcat configuration
Replace --> JAVA_OPTS="-Djava.awt.headless=true -Xmx4g -XX:+UseConcMarkSweepGC -Dfile.encoding=UTF8"
With --> JAVA_OPTS="-Djava.awt.headless=true -Xmx4g -Dfile.encoding=UTF8"
- Configure and install Keycloak
As of ReportServer 6.0, an OIDC provider (for example Keycloak) can be configured for authentication. To enable this, the option
rs.security.authentication.mode
must be configured in reportserver.properties.
For detailed, step-by-step instructions, please refer to the ReportServer 6.0 Installation Guide for Linux und Windows..
- Start up Tomcat
This completes the Upgrade to the latest ReportServer 6.0.0 version. To ensure that installation was successful have a look at your Tomcat log files. Startup should look similar to the following
_____ _ _____ ______ _ _
| __ \ | | / ____| | ____| | | (_)
| |__) |___ _ __ ___ _ __| |_| (___ ___ _ ____ _____ _ __ | |__ _ __ | |_ ___ _ __ _ __ _ __ _ ___ ___
| _ // _ \ '_ \ / _ \| '__| __|\___ \ / _ \ '__\ \ / / _ \ '__| | __| | '_ \| __/ _ \ '__| '_ \| '__| / __|/ _ \
| | \ \ __/ |_) | (_) | | | |_ ____) | __/ | \ V / __/ | | |____| | | | || __/ | | |_) | | | \__ \ __/
|_| \_\___| .__/ \___/|_| \__|_____/ \___|_| \_/ \___|_| |______|_| |_|\__\___|_| | .__/|_| |_|___/\___|
| | | |
|_| |_|
Version: RS6.1.0
Code Version: 2026-02-12-15-05-19
Java Version: Ubuntu OpenJDK 64-Bit Server VM 21.0.8+9-Ubuntu-0ubuntu122.04.1 (21)
VM Args: --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/jdk.internal.reflect=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java>
Max memory: 16 GB
Groovy Version: 4.0.26
JVM Locale: de_DE
JVM user language: de
JVM user country: DE
JVM user timezone: Etc/UTC
JVM file encoding: UTF8
JVM server time: 2025-08-18T06:41:57.775070717Z[Etc/UTC]
Operation system: Linux 5.15.0-151-generic (amd64)
rs.configdir: /opt/reportserver (OK)
### DB Config ### hibernate.dialect: net.datenwerke.rs.utils.hibernate.PostgreSQLDialect (OK)
hibernate.connection.driver_class: org.postgresql.Driver (OK)
hibernate.connection.url: jdbc:postgresql://localhost:5432/reportserver (OK)
hibernate.connection.username: rs
hibernate.default_schema:
Connection Test: OK
Schema Version: RS3.0-29
### SSL ###
Supported SSL protocols: TLSv1.3, TLSv1.2, TLSv1.1, TLSv1, SSLv3, SSLv2Hello
Default SSL protocols: TLSv1.3, TLSv1.2
Enabled SSL protocols: TLSv1.3, TLSv1.2
13:28:49.084 INFO n.datenwerke.rs.EnvironmentValidator - Performing database update RS3.0-29 -> RS3.0-30
13:28:49.085 INFO n.datenwerke.rs.EnvironmentValidator - Running script RS3.0-30-PostgreSQL_UPDATE.sql
Running Changeset: db/changelog/RS-2026-0227154210.xml::RS-2026-0227154210::infofabrik
Running Changeset: db/changelog/RS-2026-0227154410.xml::RS-2026-0227154410-3::infofabrik
02-Mar-2026 13:28:50.293 INFO [Catalina-utility-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/Library/apache-tomcat/webapps/manager]
02-Mar-2026 13:28:50.320 INFO [Catalina-utility-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/Library/apache-tomcat/webapps/manager] has finished in [27] ms
UPDATE SUMMARY
Run: 2
Previously run: 0
Filtered out: 5
-------------------------------
Total change sets: 7
FILTERED CHANGE SETS SUMMARY
DBMS mismatch: 5
Liquibase: Update has been successful. Rows affected: 2
13:28:50.837 INFO n.datenwerke.rs.EnvironmentValidator - Validating database schema...
13:28:53.894 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.FilterRepositoryResource
13:28:53.894 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.FilterRepositoryResource
13:28:53.894 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.InfoResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.InfoResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.BasicRepositoryResource2
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.BasicRepositoryResource2
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.Query2Resource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.Query2Resource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.OlapDiscoverResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.OlapDiscoverResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.StatisticsResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.StatisticsResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.DataSourceResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.DataSourceResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.SessionResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.SessionResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.ExporterResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.ExporterResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.License
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.License
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - try to bind: net.datenwerke.rs.saiku.server.rest.resources.SaikuI18nResource
13:28:53.895 INFO n.d.r.s.server.rest.SaikuRestModule - done binding: net.datenwerke.rs.saiku.server.rest.resources.SaikuI18nResource
13:28:55.338 WARN n.d.r.c.s.c.ConfigServiceImpl - Configfile scheduler/scheduler.cf could not be loaded. Default values are in effect.
13:28:55.339 WARN n.d.r.c.s.c.ConfigServiceImpl - Configfile exportfilemd/pdfexport.cf could not be loaded. Default values are in effect.
13:28:55.340 WARN n.d.r.c.s.c.ConfigServiceImpl - Configfile exportfilemd/pdfexport.cf could not be loaded. Default values are in effect.
13:28:55.479 INFO n.d.r.s.s.saiku.ThinQueryServiceImpl - loaded thinqueryservice
13:28:55.620 INFO n.d.r.c.s.i.RemoteMessageServiceImpl - Loading messages...
13:29:03.276 INFO n.d.r.c.s.i.RemoteMessageServiceImpl - Available locales: de, hi, lo, pt, lt, hr, lv, hu, zh-CN, hy, uk, id, mk, mn, uz, af, ms, el, mt, en, is, it, my, es, et, eu, vi, ne, ja, ro, nl, no, fi, be, ru, bg, keys, fr, bn, jw, bs, si, ka, sk, sl, ga, gd, ca, sq, sr, kk, km, sv, ko, zh-TW, ta, cs, th, lb, tl, pl, da, tr
[2026-03-02 01:29:06,943] Artifact war: Artifact is deployed successfully
[2026-03-02 01:29:06,943] Artifact war: Deploy took 26,166 milliseconds
13:29:07.182 INFO n.d.r.c.s.j.h.ReportServerExtenderHooker - Start loading ReportServer extensions.
13:29:07.184 INFO n.d.r.c.s.EnvironmentAfterStartupInformation -
Application Server: Apache Tomcat/9.0.86
### PAM Configuration ###
Static PAM configuration: net.datenwerke.rs.authenticator.service.pam.UserPasswordPAMAuthoritative
Finalized PAM configuration: class net.datenwerke.rs.authenticator.service.pam.UserPasswordPAMAuthoritative
13:29:07.589 INFO n.d.r.s.s.search.SearchServiceImpl - Rebuilding search index...
13:29:07.855 INFO n.d.g.s.lateinit.LateInitStartup - Startup completed
The schema version is:
Schema Version: RS3.0-30
Upgrade/Install Demo Data
A final optional step is to install or upgrade your existing demo data. For this, check this link. This step will delete all your existing data in the system.
Happy Reporting