Once you have obtained the source code follow these steps to install it.
Editing the Configuration files
- Move to the OpenbravoERP-3.0PR19Q1 directory in a command line terminal and run:
- Configure the Openbravo.properties and log4j.lcf files using the console application.
Note: More about setup ant task can be found at Openbravo.properties#Edition.
Note: On a windows based system all path in Openbravo.properties with a \ character need to be written as \\ . This applies for example to the source.path and attach.path settings.
The ant setup tool currently has a known bug not following this for source.path setting.
Extra system configuration
Before the installation one more system level setup is needed.
One file which is delivered with the Openbravo sourcecode is needed to be available inside a folder of the ant installation.
The file needed to be made available is:
That file needs to made available inside the ANT_HOME/lib (The lib subfolder of the ant installation done earlier).
That can be done by either copying the file once or creating a symlink (ln -s on linux or using mklink on a windows 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
If you find problems running install.source, check the Installation/Troubleshooting article
To access Openbravo type http://ip-address/openbravo in your web browser. Use Openbravo as the username and openbravo as the password.
NOTE: The username is Openbravo, with an uppercase O. The password is openbravo, with a lowercase o. The system is case-sensitive, and you need to type both data elements correctly to access it.
Known Issues / Special System Specific Notes
- MMC restart functionality is not available and must not be used. Reason is that is replaces the running tomcat and requires custom installation with the way tomcat start/stop is managed which is i.e. not compatible with the windows tomcat service manager.
- Instead of using it the normal system specific restart method must be used.
- MMC rebuild combined with system specific restart can fail in some specific cases. If a Openravo update does replace third-party jar libraries (i.e. updating them) then using the MMC rebuild + a non MMC restart can lead to failures on the tomcat start.
- To avoid this both the rebuild & restart can be done on the command line.
- If that error happens a full recompile (ant compile.complete.deploy) & tomcat restart can be done to correct the situation.