Installing MariaDB and Java
Installing MariaDB and Java
Disclaimer:
Our intent is to provide accurate and up to date content on this document; however, that is not
always possible. THEREFORE, ALL CONTENT, SERVICES AND FUNCTIONS ON THIS DOCUMENT ARE
PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. Some jurisdictions do not allow the
exclusion of certain implied warranties in which event any required warranty applies to the
minimum extent legally required. Content is provided for informational purposes only and should
not be relied on. Although the information on this Document may include statements on various life
events and financial, legal or tax concerns, it is provided for informational purposes only, and is not
intended and should not be relied upon as legal, tax or personalized advice.
Content may contain inaccuracies or errors and may change. No warranty or representation is made
that the information on this Site is complete, accurate, up-to-date or error-free or that known
defects will be corrected. Contents, services, products or functions available at this document may
be changed or updated at any time without notice; but the Chromis POS Team has no obligation to
update this document, so information may be out-of-date at any given time.
All rights reserved. No part of this publication may be reproduced, distributed, or transmitted
in any form or by any means, including photocopying, recording, or other electronic or
mechanical methods, without the prior written permission of the author, except in the case of
brief quotations embodied in critical reviews and certain other non-commercial uses
permitted by copyright law. For permission requests, email the author, subjected “Attention:
Author Permissions,” at the email address below.
Table of Contents
Introduction .................................................................................................................................. 4
Preparing the System.................................................................................................................... 7
Installing MariaDB ................................................................................................................... 7
HeidiSQL ................................................................................................................................ 14
Installing Java......................................................................................................................... 19
Introduction
Overview
The goal of any retail management software is to help you focus on your sales and your customers. It
is this goal that is the driving force behind Chromis.
Chromis Pos is designed to be a feature rich Point of Sale (POS) system, which can run a large variety
of hardware. The overall concept is that the core system can be configured by the user, allowing
functions to be enabled if required.
Background
Since 2013 work has been done on the project, firstly with new features and significant changes to
an open source POS. Most of these changes were born to assist a small shop implementing a
solution that was fit for purpose, and responding to requests of other users.
It was the nature of these changes and the ability to control its own destiny that Chromis was
started. The first release of Chromis was in 2015, since which it has undergone a significant
metamorphosis. There is a strategic plan to continue the development of the product, and offer a
richer platform for the user.
At the time of writing Chromis does not include any Credit\Debit card integration due to PCI
regulations, it is intended to investigate these at a later date.
Chromis POS (Point of Sale) is designed to run on hardware which is capable of running
Java\OpenJDK. The better the hardware the better the performance, it has been run on the later
raspberry Pi’s.
However, consideration should be given to the database server that will be used. If it is intended
that the database will reside on the same hardware, ensure that you selection is able to meet its
requirements.
Software
The following software is required to run Chromis. (all versions are correct at the time of writing)
Chromis has been tested with the following OpenJDK platforms (all Java 11.0.11), with limited
testing.
• BellSoft Liberica
• Microsoft JDK
• Amazon Corretto
• Zulu
• AdoptOpen JDk (hotspot)
• AdoptOpenJDk (Open9)
Oracle’s Java has been excluded from the testing due to the licensing changes and any usage that is
not development must be paid for.
Chromis is currently designed to run exclusively using MySQL or MariaDB database, this may change
at a later date.
It is also import to note that upgrading to Version 1.0 and above from a lower version is not possible,
this due the large amount of database changes from the earlier versions.
There is a migration utility available which will export a limited set of data from an older version into
the latest release.
• MySQL
• MariaDB
Our recommendations
There are a number of steps and decisions to make, in preparing your system to run Chromis.
Install Java
Database Server
As stated, Chromis currently only supports MariaDB or MySQL. Regardless of the database engine
selected, you need to decide where the database installation will reside.
For the purpose of this documentation, it is assumed that all of the required software will reside on
a single piece of hardware.
You need to ensure that the hardware is capable of running a database server, administration client
and Pos if that is your choice.
If you intend to run a multi till setup then the database must always be available to service all the
tills.
In this section we will take a look how to install MariaDB. It does not cover any configuration away
from the basics to setup a running database server ready to run Chromis. These notes are based
around using the Windows MSI installer.
Go to the MariaDB downloads page and download the latest version 10.6.5 release at the time of
writing.
https://mariadb.org/download/?t=mariadb&p=mariadb&r=10.6.5&os=windows&cpu=x86_64&pkg=
msi&m=serverion
Click ‘Next’
Leave all the settings as the defaults (change the location if required) and click ‘Next’
Assign a password for the ‘root’ user, keep this in a secure location, as it will also be required later.
If you wish to allow the server to be accessed from another machine by the ‘root’ user enable this
option.
Select ‘Use UTF8 as default’
Leave the ‘Default instance properties’ as its default. Then click ‘Next’.
Click ‘Install’
HeidiSQL
As part of the Windows installation of MariaDB, HeidiSQL will be installed, this a free database
administration GUI tool.
This tool will now be used to configure MariaDB ready for use.
Open HeidiSQL.
Once open a session needs to be created. Click ‘New’ to create a new session.
The first time that a connection is required the only details we have are the ‘root’ user, these will be
used at this stage. Enter the password created earlier into the password field.
Now the user which will be used by the Chromis application stack needs to be created.
Click ‘Add’
Enter the details for the account that will be used for Chromis.
Select ‘Global Privileges’ this will grant all permissions to user you have created.
Test the account by closing HeidiSQL and re-opening only this time pass in the details of the new
rather than ‘root’.
Installing Java
The next stage is to ensure that Java & JavafX are installed. Since Version 8 of Java, JavafX no longer
comes as part of the install process. There are some releases that do include the JavaFx runtimes.
This installation covers the use of Liberica JRE 11 (BellSoft), (as this does come with the JavaFX
runtimes needed and development is completed against this supplier’s release), but a couple of
other versions have been tested.
It is recommended that the full version is downloaded as this comes with the JavaFX files required to
run the application and the JavaFX install can be skipped.
Click ‘Next’
Click ‘Install’
Click ‘Finish’
JavaFX-SDK
Now we need to install Javafx-SDK. This is required if the java version installed does not include the
JavaFX runtime files).
The package does not come with an installer therefore must be done manually. The zip contains a
folder (javafx-sdk-11.0.2), with all the files required, extract this to your ‘Program Files’ directory.
The JavaFX directory must now be added to the PATH variable. Select ‘Path’ from the lower panel
and ‘Edit’
Providing you used the default the entry is as above. Click ‘OK’ to save the entry and exit out the
‘Advance System Setting’ by click on ‘OK’ all the way.
You are now ready to move the next stage, setting up Chromis.