For the Community JS we support MySQL and PostgreSQL (ie we provide scripts for these and test these). JasperServer stores these "resources" in a database. JasperServer needs a place to store the users, roles, reports, input controls, olap views, etc that you create. Probably it is best to call it the JasperServer Repository database. Yes, the repository and the jasperserver database are the same thing. (Like upgrading from MySQL to PostgreSQL.) Because it's more flexible, this is the general recommendation. This will work in your situation, and it will work in the more generic case of moving from one DBMS to another DBMS. These are really MySQL considerations rather than JasperServer considerations.īut Jaspersoft generally recommends js-export and js-import as the way to move data between repositories. Similarly, you could use MySQL's dbdump feature and then run the resulting SQL on the new MySQL instance. but you would have to check with MySQL experts to get a good opinion on this. Copying around MySQL data files might work.
It will be better to use a clean MySQL install. Import all old information using js-importĬopying a new MySQL version on top of the old MySQL is inviting trouble.
#Upgrade mysql enterprise to community install#
Install JasperServer so that it gets deployed to the running app server and MySQL.Start up your app server and new MySQL.It's better to configure things as you want them.) The my.ini that ships with JasperServer wasn't designed with your replication or other requirements in mind. (Copying my.ini is possible, but normally you wouldn't do this. Shutdown JasperServer (app server and database).Export all old information from JasperServer using js-export.Therefore your migration steps would be more like this: Tony's suggestion was to use js-export and js-import to move your JasperServer data. I think that using the "buildomatic" auto-configuration and deploy scripts is a good way to make it easier to control the exact app server and dbs that you want. It has info on using our automated configuration scripts to install to your chosen app server and database type.
#Upgrade mysql enterprise to community upgrade#
Then when you are done with your upgrade you can import your data back in.Īlso, you should take a look at the install guide chapter 5. You would first export all of your repository data from your jasperserver instance (can look at the docs/jasperserver-install-guide.pdf for info on import-export). Then you can re-install jasperserver from the installer, but choose to install to the new "existing" mysql database. I am thinking that it might be simpler to install the MySQL version that you want on you servers. But you would have to swap in the new mysql version and make sure that all the startup scripts and data is put back in. Upgrading the mysql included with the jasperserver installer is probably a little tricky - there would be no change to jasperserver itself (because it just connects to the DB via JDBC/JNDI).
0 kommentar(er)
