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.
The content of this file include:
Define the date and time formats:
ℹ️ Catatan:
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
In war mode a war file is created in lib/${context.name}.war. In class mode only the modified files are deployed into ${catalina.base}/webapps/${context.name}. In none mode everything the servlet container need is copied into the $OB_ROOT/WebContent directory, and no war is generated and no files are copied to the servlet container. This is useful for working with Eclipse.
Tersedia sejak versi 3.0PR15Q4
All properties are explained in detail here.
Tersedia sejak versi 3.0PR17Q2
The read-only pool feature allows to retrieve connections from a secondary (backup) database which allows just read-only operations. Typically, this will be a stand-by database that must have its data updated as much as possible.
See [Read-Only Pool](/Read-Only_Pool) for more details about the configuration of this pool.
Parameters specially useful for developers.
authentication.class: property used configure the authentication manager. Possible values:
From 3.0RC7 on the LAM Authentication Manager is no longer part of the Openbravo 3 distribution but instead available as a module. For details see the projects page.
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
These properties are explained in detail in [Log in security document](/Functional_Documentation/General_Setup#Log_in_security).
Tersedia sejak versi 3.0MP20
default) or not (no-execute). In instances having very resource demandant background processes that affect application responsiveness, can have two different servers with identical openbravo instances linked to a shared database, one of these instances would be used to serve the application to the users and would have no-execute value set in this property, whereas the other one would be used to execute processes so the value would be default. In the instance set not to execute background processes, it will not be allowed to schedule, unschedule nor kill processes, this must be performed in the instance allowing their execution. Note that there is a property which is also relevant for these type of setups: the [import.disable.process](/Retail/Configuration_Guide#Configuring_Web_POS_Import_Transaction_Process) property.Tersedia sejak versi 3.0PR17Q1
wildfly (lower cased) before [building](/Development_Build_Tasks) the application.true when Openbravo is deployed in a clustered environment.Tersedia sejak versi 3.0PR17Q3
ℹ️ Catatan: 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.
ℹ️ Catatan:
The recommended configuration option is [2],Default configurationthat 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>.
ℹ️ Catatan: 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:
properties.path.machine.name which value is the hostName.ant host.name task in each node.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.
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.