Openbravo community edition vs professional

It is strongly recommended that you subscribe to the Openbravo update and security distribution lists. The on-update-announce openbravo. The on-security-announce openbravo. In case of error you will be able to rollback to the previous release. There are two possible ways of doing it: online and offline, depending if the server has an Internet connection or not. If you prefer to work from the command line, you can use the following commands to apply maintenance patches.

Note: From version 2. If you are planning to develop your installation of Openbravo ERP, it is strongly recommended that you use the modular development process. The Modularity area of the wiki tells you everything you need to know about developing, installing and publishing modules.

Before you begin any development effort, make sure you have read and understood the information on developing modules. New development is required if you want to change the system behavior of Openbravo ERP. For example, you may want to add a new window or modify a particular process. Development is an iterative process that makes the system potentially unstable, so development should always take place outside of the production environment.

Any change that requires compilation should also take place in the development environment first. It does not provide alternative environments for development and testing purposes, so you must create these alternative environments on other machines.

It also describes how to synchronize these environments. It is important that you do not perform any development activity on the production environment, although it is safe to perform basic configuration tasks such as defining document types, roles and clients.

You are strongly advised to perform any development tasks in a separate development environment. For complex developments and for organizations with strict change management policies, you may also need to move changes into a testing environment where they can be validated by end users before they go live in the production environment. In simpler situations moving the developments from the development environment to the production environment may be sufficient.

The development environment does not need to be a mirror of the production environment and it does not need an Openbravo ERP installation, it just needs the necessary tools to develop Openbravo ERP. For more information about installing these tools, consult the environment installation page of the wiki. It may also be useful to have a testing environment. The development environment is used for testing purposes by the developer while the testing environment is the system where the end users can test the application and the new developments.

The colored lines represent the differing levels of environment setup from the simplest to the most complex:. The first stage of the process is to copy the working Openbravo ERP application from the production environment to the development environment.

It is important to ensure that the development environment is up to date with the production environment, otherwise previous changes may be lost when you deploy the new development in the production environment. If you have already set up and configured a development environment, it is important to keep it up to date to prevent losing changes from previous development when new developments are deployed to the production environment.

To update the development environment:. Once you have created a development environment you can develop it and compile it without affecting the production system. The procedures described above for creating and updating a development environment do not copy transactional or master user data into the development environment.

In most situations, transferring user data from the production environment to the development environment is not advisable because of privacy issues. Where sample data is required for testing, you can create sample data in the development environment.

Data in the development is retained when you update the environment. If it is necessary to create a development environment with real user data, the recommended method is to create a mirror of the production system. The new environment is created by backing up the production database and restoring it as a development database. To create a mirror of the production system, follow these instructions.

In a production Openbravo ERP system it is usual and recommended to have a testing environment. Among its benefits we could highlight the ability for end users to test new features in advance and for the system integrator to test new customization deployments. Before any of these testings happen, it is important to make sure that the ERP in the testing environment is identical to the one in the production environment.

Check the article explaining the replication process , or learn how get to use the command line tool that implements that process. When code changes have been fully tested, update them on the production environment using the following process:.

The free trial is a "system key" that gets emailed to you, and which you use to activate your Openbravo instance , converting it from Community Edition to Professional Edition.

It does not include any software. Many more premium features and commercial modules are under development for Openbravo 3, and we release an official maintenance pack every month. Our detailed Product Roadmap shows you what is coming in the next 5 quarters. Openbravo Professional Edition Solutions contain extensive commercial functionality that is conveniently packaged and configured to meet the needs of a particular horizontal functional area, customer segment, or industry vertical.

For example Openbravo for Retail is a fully-integrated, multichannel-capable retail management solution that includes a state of the art web point of sale module; here is the information to install and configure this solution, which is available via the free trial.

A number of commercial modules are available free with a subscription to Openbravo 3 Professional Edition, and all of these are also available with your free trial. Installing modules is exciting, but first things first!

I see pre-loaded demo data, and the first thing I want to do is to get rid of it and add my own data. How do I set up Openbravo with my own data? That preloaded demo data is provided to verify the installation and allow you to easily test the system on the hardware of your choice. To load your own data, you must first create a new "Client", since Openbravo is a multi-tenant system and the name we use for each tenant is "client".

The Quick Guide is a step by step guide to configuring Openbravo with your own data, and the section Setup Client and Organization tells you how to create a new Client and a new Organization.

To create a fully working "conference room pilot" with your own data using Openbravo, you must first execute the step-by-step instructions in the Business Setup section of the Quick Guide. Only then can you start executing business processes like purchasing and selling products. Professional Edition. Available from source code repository. Life cycle duration. Until the next release is available.

Extended guarantee. Available as packaged OBX file. One click update from the Module Management window. Openbravo aims at publishing a new release of the Community Edition twice a year, approximately at six months intervals. Although the community edition is provided without warranty and with no support from Openbravo, this edition's QA process is open to the community. Each Community Edition, therefore, has received quality approval from both the Openbravo QA team and the community and it is suitable for production usage.

Once released, defects can be reported against this edition but no guarantee is offered on when they will be fixed. All bugs are fixed in the main repository. As a general rule the Mercurial commit messages contain the issue ID it fixes.

As a general rule, bug fixes are only packaged as part of subsequent versions of the community edition. That said, Openbravo is committed to having a stable and productive Community Edition and, at its own discretion, may release Maintenance Packs for existing releases before the next one is published.