Upgrading a standalone JReport Server and an integrated JReport Server involves different processes while sharing some common steps. Both updated JReport Servers require converting the report resources in the old version in order to comply with the new server version.
Before upgrading, the old version JReport Server should be shut down.
JReport Server 13 provides two migration tools in <install_root>\bin
folder, which can help you to convert all the resources on the previous version of JReport Server before version 6.0. Resources the migration tools cover include the security information (realm, user, group, protection, and ACL), report resources (catalog and reports), scheduled tables, completed tables, version and version tables, and other relevant information (such as fonts, NLS, and style groups).
Note: When installing the JReport Server 13 into the same directory as the old version, the report level resources in the old version will be maintained and not be replaced by the report resources of V13.
To upgrade a version later than V6.0 (included) to V13, take the steps below. Here is a case showing you how to upgrade V11.1 to V13, provided that the old JReport Server is located in C:\JReport\Server11.1.
C:\JReport\Server11.1\bin
folder.
C:\JReport\Server11.1\derby\derby.properties
if derby is in use and remember it.
C:\JReport\Server11.1
. In the Choose Installation Set screen, choose Typical Installation for Standalone Server. In the System Database screen, check the Trial Database radio button, and set the port number same as the port number mentioned in step 2. You can make the upgrade using the migration tool MigrationV52.bat (MigrationV52.sh for Unix) that is available in the <install_root>\bin
folder. This tool is used to convert all the resources of the versions between V5.2 Build 590 (included) and V6 (excluded) to the resources of JReport Server 13. If you install the new version to the same folder as the old one, the parameter can be omitted.
Case 1: Installing JReport Server 13 to a new folder (recommended)
C:\JREntServer595
. Install JReport Server 13 to a new folder C:\JReport\ServerV13
. DO NOT start the newly installed JReport Server.
<install_root>\bin
, and run MigrationV52 C:\JREntServer595
.Case 2: Installing JReport Server 13 to the folder where the old version resides
C:\JREntServer595
. Install JReport Server 13 to the same location. DO NOT start the newly installed JReport Server.
<install_root>\bin
, and run MigrationV52.bat
.You can do the upgrade using the migration tool MigrationBV52.bat (MigrationBV52.sh for Unix) that is available in the <install_root>\bin
folder. This tool is used to convert all the resources of versions lower than V5.2 Build 590 to the resources of JReport Server 13. If you install the new version to the same folder as the old one, the parameter can be omitted.
Case 1: Installing JReport Server 13 to a new folder (recommended)
C:\JREntServer580
. Install JReport Server 13 to a new folder C:\JReport\ServerV13
. DO NOT start the newly installed JReport Server.
<install_root>\bin
, and run MigrationBV52 C:\JREntServer580
.Case 2: Installing JReport Server 13 to the folder where the old version resides
C:\JREntServer580
. Install JReport Server 13 to the same location. DO NOT start the newly installed JReport Server.
<install_root>\bin
, and run MigrationBV52.bat
.By now, if the previous version of JReport Server is later than V6.0 (included), the integrated JReport Server has already been upgraded to V13. But if the previous version is earlier than V6.0, go to step 4 and you need do further upgrade.
For a previous version between V5.2 Build 590 (included) and V6 (excluded): in the DOS window, switch to <reporthome>\bin
, and run MigrationV52.bat
.
For a previous version earlier than V5.2 Build 590 (excluded): in the DOS window, switch to <reporthome>\bin
, and run MigrationBV52.bat
.
Clear the temporary files or cached files on the application server. Take Tomcat as an example, remove the temp and work directories in D:\Tomcat
.