In this guide we describe the upgrade process from Bitnami ReportServer instances to ReportServer. In case you are running ReportServer 2.2.2 we advice to perform a full stack upgrade as described in this tutorial. If you are already running on ReportServer 3.0.1 you can alternatively choose to upgrade only ReportServer as described here.
With ReportServer 3.0 we have introduced some changes in licensing and now provide two versions of ReportServer: ReportServer Community Edition and ReportServer Enterprise Edition. In the cause of this restructuring we have moved some of the functionality that was previously available in the Open Source version of ReportServer to ReportServer Enterprise (see a detailed comparison between the two versions). In particular, scripting is no longer available in the open source variant of ReportServer. A trial version of ReportServer Enterprise Edition including full scripting capabilities is available on request from mailto:email@example.com
If you require any of the following features and do not wish to purchase ReportServer Enterprise Edition, please do not upgrade to Reportserver 3.0: Scripting, Dynamic List Templates, Dynamic List Pivot Mode, SAP Crystal, Database Bundles or Conditional Scheduling: click here for a detailed comparison between ReportServer Enterprise and ReportServer Community.
The following upgrade installation gives a step by step description of how to upgrade the Bitnami ReportServer Stack to either ReportServer 3.0 Community Edition or ReportServer 3.0 Enterprise Edition. The upgrade consists of the following steps.
The first step is to download the updated Bitnami ReportServer Stack. You can find download links on our download page. Note that you can upgrade both to ReportServer Enterprise or to ReportServer Community. Once you have downloaded the installer, keep the file in a safe location and proceed with the next steps without starting the installation process. We'll do so in just a moment, but before need to export the necessary files from the old ReportServer version and power down ReportServer 2.2.2.
To export all relevant data from your current ReportServer installation, log into ReportServer with a super user account (or an account that has the rights to access the Terminal and upload files to the fileserver). Go to the administration module and there to ReportServer's fileserver. Download the following file package archive file. Please make sure to download the correct package corresponding to the version you are upgrading from.
Upload the file to ReportServer's fileserver (for example to the root folder) and open a terminal CTRL+ALT+T). Execute the package by running the pkg install command and provide the uploaded file as parameter. If you uploaded the file to the root folder this would be
pkg install fileserver/upd-exp-XXX.pkg
where XXX needs to be replaced by the correct version number.
After installing the exporter package, go to the following URL
There you should find a few notes on how to proceed and most importantly a single button saying Continue. Click the Continue to start the export. This should trigger an output such as the following:
2016-03-30 18-55-43: Initializing... 2016-03-30 18-55-43: ### DB Config ### hibernate.dialect: net.datenwerke.rs.utils.hibernate.MySQL5Dialect hibernate.connection.driver_class: com.mysql.jdbc.Driver hibernate.connection.url: jdbc:mysql://127.0.0.1:3309/bitnami_reportserver hibernate.connection.username: bn_reportserver hibernate.connection.password: a04970aca0 hibernate.default_schema: Bitnami basedir: /Applications/reportserver-18.104.22.16839-5 persistence.xml: /Applications/reportserver-22.214.171.12439-5/apache-tomcat/webapps/reportserver/WEB-INF/classes/META-INF/persistence.xml (OK) reportserver.properties: /Applications/reportserver-126.96.36.19939-5/apache-tomcat/webapps/reportserver/WEB-INF/classes/reportserver.properties (OK) mysqldump: /Applications/reportserver-188.8.131.5239-5/mysql/bin/wrapper (OK) openssl: /Applications/reportserver-184.108.40.20639-5/common/bin/openssl (OK) rsversion: RS2.2.2-5639 2016-03-30 18-55-43: running mysqldump 2016-03-30 18-55-45: Warning: Using a password on the command line interface can be insecure. 2016-03-30 18-55-45: zip 2016-03-30 18-55-45: Created: /Applications/reportserver-220.127.116.1139-5/apache-tomcat/webapps/reportserver/backup/rs-db-2016-03-30-18-55-43.sql.bin 2016-03-30 18-55-45: Done. The export completed successfuly. Please click here to download the archive: rs-db-2016-03-30-18-55-43.sql.bin
Important here is the link at the end of the output which is of the form rs-db-2016-03-30-18-55-43.sql.bin. Click the link to download the export file and store it in a safe place.
Once that we have exported all relevant data from the old instance, we can stop the old server. You can stop ReportServer by using the server monitor application that was installed with ReportServer. You find it in the installation directory. The manager application should be called manager-PLATFORM where platform could be linux-x64, windows or osx.
You should keep it as backup until you are sure that the new version is running smoothly and all data got properly imported.
We are now ready to start install ReportServer 3.0. For this start the installer and follow the instructions. In case you are asked to specify ports for MySQL (i.e., MariaDB) or Tomcat stop the installation and make sure that you have properly shutdown the old version of ReportServer.
Once ReportServer 3.0 has been installed open it up and login with the user you provided during the installation. (On the first start it might be necessary to clear your browser cache.) There again go to the administration module and ReportServer's fileserver. Download the following importer package
Upload the file to ReportServer's file server, for example, into the root folder. The next step is as before, we'll install the importer package via the pkg install command.
pkg install fileserver/upd-imp.pkg
Now again point your browser to the URL
which now contains instructions on how to import the previously exported file.
Select the exported file (rs-db-somedate.sql.bin) and click Continue. The import starts and may take a while depending on how large your system was. You should see something along the following lines on the console.
2016-03-31 08-54-24: Initializing... 2016-03-31 08-54-24: Bitnami basedir: /Applications/reportserver-18.104.22.16834-4 rs.configdir: /Applications/reportserver-22.214.171.12434-4/apps/reportserver/reportserver-conf BackupFile: /Applications/reportserver-126.96.36.19934-4/apache-tomcat/temp/upload_32c8ec7e_fddb_4c96_af17_a92e5d75fe08_00000003.tmp (OK) openssl: /Applications/reportserver-188.8.131.5234-4/common/bin/openssl (OK) mysql: /Applications/reportserver-184.108.40.20634-4/mysql/bin/mysql (OK) 2016-03-31 08-54-24: unzip 2016-03-31 08-54-24: found rs-db-2016-03-30-18-08-22.sql 2016-03-31 08-54-24: found reportserver.properties 2016-03-31 08-54-24: found persistence.xml 2016-03-31 08-54-24: update reportserver.properties 2016-03-31 08-54-24: rs.crypto.passwordhasher.hmac.passphrase: 6cf708658c8b8f87a5f2c4ee8bb537e587a2d0fcfb4b8131e80809cd780dd950e7c2efdc65166c4 2016-03-31 08-54-24: rs.crypto.pbe.salt: The salt to be used for encryption. This should simply be a long string. 2016-03-31 08-54-24: update persistence.properties 2016-03-31 08-54-24: hibernate.connection.password: a04970aca0 2016-03-31 08-54-24: url: jdbc:mysql://127.0.0.1:3315/bitnami_reportserver 2016-03-31 08-54-24: connect jdbc... 2016-03-31 08-54-24: shutdown entity manager 2016-03-31 08-54-24: drop 2016-03-31 08-54-25: create 2016-03-31 08-54-25: grant 2016-03-31 08-54-25: import sql 2016-03-31 08-54-30: 2016-03-31 08-54-30: Done. The import completed successfuly. You have to restart the server before you can log in.
Once the importer finished you are almost done. All that is left to do is to restart ReportServer. For this go to the installation directory and open the manager-PLATFORM application. There go to Manage Servers and restart Tomcat. You should then be able to log in with your old accounts.