To get the value of a property and store it in a variable, in this case we'll take the attach.path property and save its value in the attachpath variable (BitRock internal variable): So we mostly want to read the values of the properties and change them to other values. Openbravo ERP uses the Java property format for both config/Openbravo.properties and config/log4j.lcf. Example:Ĭommon actions Get/Set values of variables from Java properties files In this section we'll see how to implement the different kind of most used controls, such as a text box, a combo box, etc. And this is implemented in the postInstallationActionList tag. The final choice is saved in the config/Openbravo.properties when the user confirms it with the final "OK" button in the tool. Next, when that window appears (window defined with a parameterList tag) the user can choose between PostgreSQL and Oracle in that combo box. That is, it detects that bbdd.rdbms is set to POSTGRE so it selects PostgreSQL in combo box when that window appears to the user. $ cat /some/erp/root/config/Openbravo.propertiesībdd.url=jdbc:postgresql://localhost:5432įirst, the tool takes the already selected values of those properties in the preInstallationActionList tag. We'll take some lines of config/Openbravo.properties to see what the tool does with them: The setup-properties.xml file has the following general structure: |- setup-properties.xml -> XML file that feeds BitRock InstallBuilder to create the final binaries. Once committed the ant setup task takes the binaries from this URL. |- output/ -> Directory where the binaries are stored. |- licenses/ -> Directory containing the license used in a window. |- images/ -> Directory containing some png images used in the binary. Now let's analyze the structure of the repository we've just checked out: Then check out the setp tool sources, stored in a Subversion repository: $ echo "export PATH=$PATH:/opt/installbuilder/bin" > /home/johndoe/.bashrc $ chown -R johndoe:johndoe /opt/installbuilderĪdd it to the PATH of your everyday user (if you use bash, otherwise do the equivalent in your shell): $ ln -sf installbuilder-5.4.10 installbuilder $ cd /opt & tar zxvf /tmp/installbuilder.tgz Once you have the tar file, uncompress it give it permissions to your everyday user: So ask the Release Management Team to provide you this, if you think you should have it. We do not use the latest version of the package, and it is no longer available in the official download website. The first step to get the environment ready is to install BitRock InstallBuilder. Currently we generate binaries for AIX, FreeBSD (x86 and x86_64), HPUX, Linux (x86, x86_64, IA64 and PPC), OpenBSD, OSX, (open)Solaris (Intel, Sparc) and Windows. And we use a program called BitRock InstallBuilder to build binaries from that XML file. This XML includes a definition of what fields we want to include in each window. The Setup Tool is a binary file that is generated from a XML file. Note that it supports both graphical and command line environments. So the setup tool is always up to date with these changes and provides a simplified way of doing this. While all this files contain templates can be copied and configured by hand, it's hard to keep track of all the files that the development team requires users to configure. Currently the files are the following ones: The Setup Tool offers an easy way for end users to configure all the files required for Openbravo ERP to build and run properly. This includes information like database connection information or a directory for the ERP attachments. It provides a comfortable user interface to configure the basic files required by Openbravo ERP to be built and to run properly. The Setup Tool is used in Openbravo ERP for doing the initial configuration in custom and development installations. 7.1 Get/Set values of variables from Java properties files.
0 Comments
Leave a Reply. |