Professional Documents
Culture Documents
Version Control
Version Author Date Change
2.0 Stefan Huehner May 29th, 2018 Client side system requirements and others sections filled in
3.0 Alexandre Fanzeres May 30th, 2018 Openbravo deploy options filled in
4.0 Patricia San Juan Dec 10th, 2018 New section added named “Backups” for On premise
5.0 Patricia San Juan Oct 30th, 2020 Updated minor versions
Table of Contents
Version Control
Table of Contents
Introduction
I. Introduction
Openbravo is a software solution vendor that offers a global POS and retail management software
with the aim of helping midsize and large businesses to successfully manage their retail operations.
“Openbravo Commerce Suite” is Openbravo's commercial offering for the Retail Industry. This suite
offers a unique store solution or cash register system, composed by a set of modules that once
installed on top of Openbravo, deliver the retail functionality provided by Openbravo and the
technology to extend and create new retail functionality to adapt Openbravo as required.
Besides that, Openbravo Commerce Suite is backed by a complete back office functionality that is
the Openbravo Business Suite. The Openbravo business suite offers a comprehensive business
management solution with built-in ERP capabilities.
This document is intended to describe high-level the operating system and database recommended
by Openbravo as well as the minimum stack required for Openbravo to properly work, together with
the use of a set of hardware and monitoring tools that guarantee a proper conservation of the data.
Openbravo agrees to keep the regulatory documents until the end of the third year following the
year in which the software or cash system ceases to be released.
As a web application, Openbravo can be used on any device that is capable of running current web
browsers.
As for most web based applications, a faster CPU and more RAM makes the GUI snappier and
more pleasant to use. Larger displays also make users more productive using wide grids, forms and
multiple tabs. To give an example: a computer with an i3 processor with 4GB RAM and display with
a 1680x1050 resolution is a comfortable setup for the Openbravo 3 web client.
Chrome 68 69 or higher
Safari 8 9 or higher
3Mbit/s <=10
10Mbit/s <=20
100Mbit/s <=100
Introduction
There are two options to deploy Openbravo, Openbravo Cloud or On-premise instances.
Openbravo cloud is a single-tenant platform as a services option that enables businesses to deploy
Openbravo solutions on virtual servers in Amazon Web Services (AWS). It can only be subscribed
in combination with an Openbravo Professional or Enterprise edition. This is Openbravo's
recommended deployment option. If choosing Openbravo Cloud option, Openbravo Cloud
operations will be in charge of the complete technical operation (operating system, database,
system software stack (server)).
If an Openbravo client chooses to set up Openbravo on premise, that implies that Openbravo does
not host that instance but the customer. Therefore Openbravo is not responsible for backups and
restoration policies within that environment, neither database access control procedures or
database management.
Below table shows the differences between these two deploying options:
Openbravo Cloud
Cloud Infrastructure
It consists of multiple components - starting from AWS infrastructure and services, throughout
monitoring, security and automation services (fully managed by Openbravo) up to application layer
directly serving requests to end customers.
Operating system
For Cloud deployments Openbravo uses a custom Ubuntu Linux Operating System prepared with
all tools and with the precompiled Openbravo application. Also, as part of the Cloud solution, the
server is deployed in a private AWS network with all security and access rules preconfigured. Only
Openbravo´s cloud administrators have admin rights in the Linux server.
Database management
In cloud deployments Openbravo uses only PostgreSQL as the database backend. The database is
part of the prebuilt image we use and comes with all standard security and performance
configurations to guarantee the system integrity.
To ensure reliability and to meet agreed SLA requirements Openbravo manages following backups
definition :
Java SE 7
PostgreSQL 9.3.x
Barman 1.5.x
Hardware
In cloud deployments Openbravo uses AWS instances to host the application. The instance type is
determined before the implementation taking into account the number of concurrent users, expected
growth and users access profile.
On premise
Operating system
For on premise install Openbravo recommends to use Linux flavor while learning how to develop in
Openbravo, because the amount of useful development tools provided by these operating systems
are vastly superior to the rest, at least in regards to Openbravo.
Database management
Openbravo can be deployed in instances running either with PostgreSQL or Oracle, as both
databases are supported. Openbravo recommends using the PostgreSQL database.
Java SE 7, 8 7
Hardware
When installing on premise the hardware server needs to be adequate for the intended usage (Data size,
concurrent user or terminal count). Any production install should be done on up to date server quality
hardware. For example some recent Intel Xeon CPU, and some enterprise quality disks i.e. SSD for best
performance or some fast magnetic disks.
● As example a very small install with only a few concurrent users (<10) could run easily with only 2
cpu cores available and 4-8GB of system memory.
● A bigger install for example 250 concurrent ERP users and additional 650 terminals needs a much
bigger system like 40 cpu cores and 160 GB of system memory.
Backups
In such instances, it is under the responsibility of the company using the system to keep the data
well securely stored and make sure that backups can be recovered from periodically. In other words,
the company using the system must be aware of data retention responsibility within the scope of
cash register systems legislation requirements in France.
According to that, Openbravo enforces the creation of backups at least on a daily basis and
according to the Openbravo instructions that can be found in this Openbravo wiki page Backups.
In summary, in order to configure a good backup policy of your instance, Openbravo recommends to
follow below listed steps:
Munin
Munin is used to keep track of application and infrastructure trends, with the aim of providing
statistics data to be used by the Openbravo support team to evaluate the root cause of a problem.
This tools provide Openbravo with some graphics, such as the one shown below:
Nagios
Nagios is used to proactively monitor application and infrastructure events, sending alerts to the
Openbravo support team, in case something fails. For instance the application stops responding or
a performance parameter reaches an alarm state, causing the end customer to perceive a bad
application experience.
pgBadger
pgBadger is used by Openbravo and Cloud teams to monitor PostgreSQL statistics and trends, in
order to mainly check end-customer’s environment performance.
V. Openbravo replacement
In the case of replacement of the Openbravo Commerce system by the end-customer, archived files
containing all of the payment data recorded, will be at end-customer disposal as described in the “Archiving “
related sections of the OB Functional Specification file v 5.0.
The “csv” archive format provided can be easily imported in other systems.