Hi Jukka,
You described it well, just copy over the driver files from old release before
step 5.
Since, I guess, you did not change tables or fields in your schema between your
release change no need to worry about ALTER.
You asked "would you recommend extracting on top of the old release?". No that
would uselessly complicate things
This said, in order to have the documentation associated with its release, we are moving some part of the documentation from the wiki, or other old
way of documenting, to AsciiDoc.
About the DBMS driver, you can find the README.adoc file in the main directory of your OFBiz installation. You can transform it into
HTML:https://asciidoctor.org/docs/convert-documents/
Then you will find a section about DBMS drivers: "Setup an external database like
MySQL, PostgreSQL, etc", it says:
Setup an external database like MySQL, PostgreSQL, etc
To setup an external database instead of the default embedded Apache Derby,
you will need to follow the following instructions:
1.
Find the JDBC driver suitable for your database using one of the
following options:
*
Search for the JDBC driver injcenter
<https://bintray.com/bintray/jcenter>and place it in build.gradle dependencies
e.g.|runtime
'mysql:mysql-connector-java:5.1.36'|
OR
*
Download the JDBC driver jar and place it in $OFBIZ_HOME/lib or the
lib sub-directory of any component
2.
Modify the entityengine.xml file located in
$OFBIZ_HOME/framework/entity/config to switch the default database to the one
you selected. For
more details you can read the relevant section in thetechnical setup
guide
<https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Technical+Production+Setup+Guide>
HTH
BTW, it's still unofficial, but the documentation for the R17 branch (our stable one) is present at https://ci.apache.org/projects/ofbiz/site/
(Javadoc is for the trunk)
Jacques
Le 05/05/2020 à 09:58, Jukka Palko a écrit :
Hello Pierre,
Thanks, I'm glad that the tarball is the way to go.
So would the recommendation be to
1. get the new tarball
2. extract that to a new directory hierarchy (not on top of the old OFBiz
files)
3. copy/alter the modified files in the new release to match the external
database connections which in my install are only:
- framework/entity/config/entityengine.xml (mariadb datasources)
- build.gradle (to include org.mariadb.jdbc driver)
- ~/.gradle/gradle.properties (gradle tuning)
4. copy over customization files that may have been created during usage of old
release if any (I'm not quite familiar yet how these customizations are being
located on disk/database)
5. use the new release hierarchy in which executing
- ./gradlew clean
- ./gradlew "ofbiz --load-data readers=seed"
- ./gradlew ofbiz
6. check everything works as earlier
Or do I need to somehow otherwise run a extra command to get gradle to
download the mariadb driver to the new release directory hierarchy as I used
the build.gradle way to define it's driver instead of downloading the driver
files manually? Or just copy over the driver files from old release before step
5?
The page also referred to a lot of database ALTER commands which hopefully are
not necessary to be individually gathered from the page and executed against
the DB. Sorry, not quite on my familiar ground with this but I'm trying to get
to grips with the product so I can explain what does what in the base system.
:)
Or would you recommend extracting on top of the old release after having made
a backup of the old release directory hierachy from which to pull certain
earlier files?
Best regards,
Jukka
On Tuesday, 5 May 2020 10.16.22 EEST Pierre Smits wrote:
Hi Jukka,
Yes, you are correct in understanding that the project has moved from svn
to git. There may still be pages in the wiki and elsewhere that are not
reflecting that.
That being said, using a release is the way to go for doing an
implementation for 'production' purposes. The project advises not to use
code directly from the repositories for production purposes.
Met vriendelijke groet,
Pierre Smits
*Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since
2008 (without privileges)
*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
Apache Steve <https://steve.apache.org>, committer
On Tue, May 5, 2020 at 9:07 AM Jukka Palko <[email protected]> wrote:
Thank you Pierre.
Yes, the setup was directly with MariaDB as the backend as there was not
much interest in
using the embedded DB in the future in comparison to the rich features of
an external
RDBMS and the person going to maintain the database does understand
MySQL/MariaDB
from previous experience.
I can see that the page you referred me to shows as the first command to
run subversion
update. I have done the install using a tarball.
Would it be recommendable to do the install initially rather with getting
the sources using
subversion/git than downloading the tarball for future ease of upgrading?
Have I
understood correctly that the project has been changing toward git with
the newer code
branches?
I also just noticed actually that I had not found this page, or just
missed the bit earlier, that
actually does refer to svn commands:
https://cwiki.apache.org/confluence/display/OFBIZ/
Demo+and+Test+Setup+Guide[1]
<https://cwiki.apache.org/confluence/display/OFBIZ/
Demo+and+Test+Setup+Guide%5B1%5D>
Best regards,
Jukka
On Tuesday, 5 May 2020 09.40.22 EEST Pierre Smits wrote:
Hi Jukka,
First of all: welcome!
If you're still evaluating OFBiz in a non-production setup (e.g. with
the
embedded Apache Derby RDBMS as the data store) you can just replace the
16.11.07 code by the 17.12.03 code in the folder of your choice.
However, if you already setup your OFBiz implementation with an external
(production-grade) RDBMS - like MySQL/PostgreSQL/etc. - and have
production
data in play, you need to do more.
Not only do you need have backups of your data and the various
configuration files, but you also need to assess whether replacement of
the
16.11.07 code with the new version has an impact on customisation you
may
have. There may be data (entity) model changes in play:
https://cwiki.apache.org/confluence/display/OFBIZ/
Revisions+Requiring+Data+Migration+-+upgrade+ofbiz
Met vriendelijke groet,
Pierre Smits
*Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/>
since
2008 (without privileges)
*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
Apache Steve <https://steve.apache.org>, committer
On Tue, May 5, 2020 at 8:26 AM Jukka Palko <[email protected]> wrote:
Hello,
I tried to ask this question with my protonmail email earlier on
upgrading
to 17.12.01 but I think protonmail is a bit troubled with mailing
lists.
So, a retry with my GMail subscribed to the list.
I'm basically completely new to OFBiz but not new to system
administration
in
general with more than 20 years of Linux and Unix experience.
My question is what are the upgrade procedures for an OFBiz
installation. I
have done a MariaDB database on Debian 10 and configured OFBiz to use
that
as
the backend.
I can write up a wiki page of the install should that be found useful.
I
basically did the documentation in a text file of the procedures used
as
I'm trying to help a local small business in starting to use the
software.
The installation was built using command
./gradlew --parallel-threads=8 cleanAll loadDefault
I configured a systemd service file for the installation as follows:
------
[Unit]
Description=OFBiz Service Daemon
After=network.target auditd.service
After=network-online.target
Wants=network-online.target
[Service]
User=ofbiz
WorkingDirectory=/srv/ofbiz/apache-ofbiz
ExecStart=/srv/ofbiz/apache-ofbiz/gradlew ofbiz
ExecStop=/srv/ofbiz/apache-ofbiz/gradlew 'ofbiz --shutdown'
[Install]
WantedBy=multi-user.target
------
The installation is running fine I guess which is to say that it does
not
seem
to complain on any web page I've browsed on it thus far.
However, I did the install while 16.11.07 was the newest version and
now
there
is the version 17.12.03 available. What are the update/upgrade steps
to
move
my install from the previous version to the new one?
Best regards,
Jukka Palko
