MIgration from 3.1 to 3.5 community version

[vsoneta]

Need to know how can I migrate my data from 3.1 jasperserver to 3.5. Can anyone knows any documentation... we just bought couple of weeks back the documentation for 3.1 and found that someof the stuffs are not supported in 3.1 so need to try 3.5. Please help me...Using tomcat 6.0, MYSQL server 5.0.

[lrout]

use the export-import utility to migrate your data from 3.1 to 3.5.

for exporting jasperserver data --

 

 cd <JS_3.1_installation_dir>/scripts

Linux :  ./js-export.sh --everything --output-dir js-data_backup.zip

Copy the js_data_backup.zip to <JS_3.5_installation_dir>/scripts

For importing JS data --

Linux : ./js-import.sh --input-dir  js-data_backup.zip

make sure to keep a backup of jasperserver table before following above steps.

 

Thanks

Lipika

 

 

 

Post Edited by lrout at 04/30/2009 10:35

Post Edited by lrout at 04/30/2009 10:36

[vsoneta]

Those commands are in Linux... how about in windows?

[mryzhikova]

Please look at the install guide thats shipped with the application. We are including steps for upgrade for Windows there.

thx!

marina

[yashdeep]

Hi!

In Windows u can use

C:\cd <jasperInstallation>/scripts

C:\..JS.\scripts> js-export --everything --output-zip <path>Backup.zip

Copy the Backup.zip to JS 3.5 folder then use

C:\..JS3.5\scripts>js-import --input-zip <path>Backup.zip

Thanks & Regards,

Yash

 

[tkavanagh]

Hi Folks,

There is also an upgrade script so that the database can be upgraded "in place".

However, because encryption is now turned on by default in 3.5.0, it is not simple to do the database upgrade. There are a few additional manual steps.

I think it is better to do the upgrade by using import-export (as described above). The import automatically does the password encryption handling for you.

Here is the text from the release notes that descibes the "in place" database upgrade:

 

3. Upgrade Notes

In JasperServer 3.5, user password encryption has been turned
on by default to enhance security. Because most pre-3.5
customers have not been running with encryption enabled, the
upgrade steps need to account for this change. After the
completed upgrade, users will not be able to login to
JasperServer if the JIUser.password column has plain text
passwords.

In the Install Guide the recommended upgrade procedure uses the
new buildomatic scripts (and import-export) to handle upgrade.
In this case, password encryption from 3.1 to 3.5 is handled
automatically.

See section 7, "Upgrade from JasperServer 3.0 or 3.1 to 3.5"
in the <js-install>/docs/JasperServer-Install-Guide.pdf for
detailed upgrade steps.

The script:

<js-install>/scripts/upgrade/upgrade-mysql-3.1.0-3.5.0-WARNING.sql

does not handle password encryption automatically. If this script
is run, all passwords will still be unencrypted. See the comments
at the top of the script file for hints on how to handle
encryption on the upgrade scenario.