ERP 2.50:Openbravo ERP Installation/Custom Installation
A custom installation provides you with maximum deployment flexibility and full control over the technology stack and its configuration. However, it can be laborious and requires a high degree of experience.
For this reason, we recommend to novice users not to attempt custom installations and to instead install Openbravo ERP in other recommended architectures.
A custom installation allows you to choose your preferred deployment topology, depending on your data volume and user load:
- Single server.
- Dual server, with one database server and one application server.
- Multi-server, with multiple servers running a database RAC and multiple application servers with a load balancer.
Technology Stack Installation
You can optimize your installation of Openbravo ERP, depending on how you intend to use it:
- For production environments, follow these installation steps.
- For development environments, follow these installation steps.
Downloading Openbravo ERP
You can to obtain a copy of the source code by either:
- Downloading a source code tarball.
- Checking out the source code from the Openbravo Mercurial repository.
Downloading the tarball
You can download a tarball of the Openbravo ERP source code from SourceForge.
Once the download is complete, you can extract the code with the following command:
tar -xvf OpenbravoERP-2.50xx.tar.bz2
If you are using Windows, make sure you uncompress this file with a tool capable of managing long file names, like 7-zip. Using 7-zip is the recommended option for Windows users.
Once the Mercurial client is installed, move to the directory to which you want to check out the source code.
To check out the latest source code tag, type the command:
$ hg clone http://code.openbravo.com/erp/devel/main OpenbravoERP-3.0PR17Q3.1 $ hg up 3.0PR17Q3.1
In order for the Module Management Console to work correctly it is necessary that the user running the Tomcat process is a trusted user to access the Mercurial repository, trust from Mercurial's point of view. If you are running Tomcat with the same user that has done the hg clone, then you can skip this step. Otherwise, add the tomcat user (e.g. tomcat) to the trusted group:
$ mkdir /etc/mercurial $ cat << EOF >> /etc/mercurial/hgrc [trusted] users = tomcat EOF
Openbravo ERP Installation
Once you have obtained the source code follow these steps to install it.
Editing the Configuration files
- Move to the OpenbravoERP-2.50MPX in a command line terminal and run:
- Move to the OpenbravoERP-2.50MPX/config directory.
- Access the graphical configuration wizard:
- Linux: make executable and run setup-properties-linux.bin
- If you face any segfaults running this tool, add --mode xwindow or --mode text as an argument.
- Windows: run setup-properties-windows.exe
- Configure the Openbravo.properties and log4j.lcf files using the configuration wizard.
These configuration wizard can also run in text mode without a graphical system. It will detect the correct display mode for your system.
Before starting with installation, check that Openbravo.properties and log4j.lcf files (in the config directory) have been properly configured. If not, edit them manually.
- In the command line type:
- The ant install.source command creates the database from *.xml files and installs Openbravo ERP
Using Openbravo ERP
Navigate to the Openbravo ERP installation guide to discover how to use Openbravo ERP.
If you have explicitly selected war as the deploy.mode during the setup, you must deploy the openbravo.war file into the Apache Tomcat context directory using the command:
If you are using PostgreSQL database, you must clean the database before you access Openbravo ERP to prevent performance issues. Use the command:
vacuumdb -f -z -h ''hostname'' -d ''dbname'' -U ''username''
Replacing hostname with the actual hostname of your DB server, dbname with the database name (by default openbravo), and username with the name of the DB user (by default tad).
Before you access your Openbravo instance, it is strongly recommended that you run the following command to validate your system configuration: