A tip for upgrading to 2.0 on ubuntu
Submitted by Matt Young on Sun, 15/04/2018 - 12:24
- Tomcat uses has it's JVM set in /etc/default/tomcat7 or in the init.d script.
- openvpms won't work with 1.7 anymore so you need to tell tomcat to use 1.8
- sudo nano /etc/default/tomcat7
-
uncomment line JAVA_HOME=/usr/lib/jvm/openjdk-6-jdk and change its value to JAVA_HOME=/usr/lib/jvm/java-8-oracle
Re: A tip for upgrading to 2.0 on ubuntu
It is my understanding that Java 8 has been required since the release of 1.9 (requirements) so I would assume that this would have been sorted by now on upgraded servers. Not to hijack this thread, but I think the real problem with Ubuntu and 2.0 is that since 16.04, Ubuntu has been using MySQL 5.7 and OVPMS is stuck at 5.5. With 18.04 coming out later this month (also using 5.7), that leaves only one year until 14.04 (with MySQL 5.5) reaches EOL. If OVPMS doesn't move to 5.7 by 4/19, or a usable workaround outlined, then it will be at that time that it hits the fan between OVPMS 2.x and a supported LTS Ubuntu release.
Sam Longiaru
Kamloops, Canada
Re: A tip for upgrading to 2.0 on ubuntu
Upgrading to MySQL 5.7 is scheduled for OpenVPMS 2.1: OVPMS-1959
The main issue will be updating all of the SQL reports to ensure that they work with 5.7 without the sql_mode workaround described in the JIRA.
If you want to work on this, let me know.
-Tim
Re: A tip for upgrading to 2.0 on ubuntu
Tim,
This sounds like a helpful project. I'm certainly no Tim G. when it comes to MySQL but I'll PM you and we can talk about how this might work.
Thanks,
Sam
Re: A tip for upgrading to 2.0 on ubuntu
I currently run 1.9 on 5.7 ...it can be done if you tweak the MYSQL conf options quite easily.
Re: A tip for upgrading to 2.0 on ubuntu
Hi Ben
What are the mysql configuration options to allow OpenVPMS 1.9 to be run with mysql 5.7?
Cheers
Damien
Re: A tip for upgrading to 2.0 on ubuntu
Damien,
There was a discussion here when I initially looked into migrating my servers to 16.04. While the config parameters seemed to work, the problem was some of the reports. Tim has since referenced two Jiras - 1420 and 1959 that show the config options and outline plans for 2.1. All pretty timly given the release of 18.04 last month.
Hope this helps,
Sam