View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

Openbravo.properties

Contents

Introduction

Several parameters should be configured for Openbravo to work correctly. These parameters can be configured through a graphical interface using the setup tool or by hand.

Contents

The content of this file include:

Date/time format

Define the date and time formats:

Bulbgraph.png   After changing any of those properties above a complete re-compilation must be done, a smartbuild is not sufficient. This is needed as those values are incorporated in various generated files. Therefore, after changing any of these properties, ant compile.complete.deploy must be executed

General

Database

Apache JDBC Connection Pool

Bulbgraph.png   This feature is available starting from 3.0PR15Q4.

All properties are explained in detail here.

Tomcat Manager

Development parameters

Parameters specially useful for developers.

Authentication

authentication.class: property used configure the authentication manager. Possible values:

This is an example using the default authentication manager.

authentication.class=org.openbravo.authentication.basic.DefaultAuthenticationManager
#authentication.class=org.openbravo.authentication.lam.LamAuthenticationManager
#authentication.class=org.openbravo.authentication.basic.AutologonAuthenticationManager
#authentication.autologon.username=Openbravo

Add-ons

Hibernate

Safe mode

Log in security

These properties are explained in detail in Log in security document.

Bulbgraph.png   Available from 3.0MP12

Others

Bulbgraph.png   This feature is available starting from 3.0MP20.
Bulbgraph.png   This feature is available starting from 3.0PR17Q1.

Edit

Bulbgraph.png   Available from 3.0PR15Q1

Openbravo.properties is a plain text file that you can edit manually by duplicating the Openbravo.properties.template file or using the assistant (console application).

Since 3.0PR15Q1 to configure Openbravo.properties file can (and in fact must) be done via console application. For that, go to the directory with the working clone of the repository and execute setup ant task:

cd openbravo-root
ant setup

The invocation of this ant target will compile and execute automatically a console application.By going through the console application provide all requested information and at the end, select Accept to apply the changes and close the application.

Bulbgraph.png   The recommended configuration option is [2], Default configuration that is the fastest option to configure the Openbravo.Properties file. Then you can change some specific properties.

As a result of these actions a new file Openbravo.properties, containing specified settings, will be created in config subdirectory.


Before 3.0PR15Q1 Openbravo.properties is a plain text file that you can edit manually by duplicating the Openbravo.properties.template file or using the graphical assistant (wizard).

To configure it using the wizard, first run the ant setup command to download the setup tool that matches your operating system and architecture:

cd openbravo-root
ant setup

Then, go to the config/ directory and run the setup-properties tool. For example, in Linux:

cd openbravo-root/config
./setup-properties-linux.bin

As a result of these actions a new file Openbravo.properties, containing specified settings, will be created in config subdirectory.

Note: If there is no setup binary for your operating system and architecture, send a request to <staff.rm at openbravo dot com>.

Overriding properties per instance

Bulbgraph.png   Available from 3.0PR15Q2

Openbravo installations within a Tomcat clustering can define some properties to be different between different cluster nodes while sharing a common Openbravo.properties file for the common properties.

This can be done by creating new properties files for each node wanting to override some properties. These files must be placed in the same config directory than common Openbravo.properties and be named hostName.Openbravo.properties, where hostName references the name of each node. Name of each host can be defined in 3 different manners:

For example, having a cluster of 3 nodes named app1, app2 and app3. All the 3 nodes share the same webapp and sources directories. Background processes want to be run only in app1 node. In this case there would be a common Openbravo.properties file containing all the properties where background.policy would be set to no-execute. In addition there would be a app1.Openbravo.properties with background.policy set to default. In this manner, app1 instance would use the common Openbravo.properties for all the properties but for background.policy which would be overrident to default.

Developers: getting values for properties

The way to obtain the actual value for a concrete property is using OBPropertiesProvider.getInstance().getOpenbravoProperties().getProperty("propertyName") where propertyName is the name of the property to get the value for. OBPropertiesProvider manages file path location and property overwriting.

Retrieved from "http://wiki.openbravo.com/wiki/Openbravo.properties"

This page has been accessed 26,878 times. This page was last modified on 21 November 2016, at 13:13. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.