Openbravo obx file

Installation of new modules is performed from the Add Modules tab in Module Management window. Remote installation connects to Openbravo Central repository to look for the latest version available of the module to install. It pulls all the module dependencies, installing always the highest compatible version and in case it is needed, updates the currently installed modules to the latest compatible version with the modules to install or update.

That's why this is the recommended way of installing modules. You can look for the module you want to install using the Search text box. When Search button is clicked, the application will connect with Openbravo's Central Repository to look for the modules matching the criteria and will show them, in each module there is a View Details link which will open an information box about the module.

When the module to install is selected and the Install Now button is clicked, the installation process will start. For those instances that are not connected to Internet or for installing modules that are not available in the Central Repository for example, a customer's own private modules , it is possible to install modules from the File System.

First of all you need to obtain the module as an obx file and save it in your file system. The obx files for all published module versions can be downloaded from Central Repository. Once you have the obx file, clicking the Browse File System button will open a dialog window to select the file and afterwards the installation process will start, this process is the same as the explained for Remote Installation.

The only difference is that dependencies will not be installed or updated, so in case a required dependency is not included within the obx file and it is not installed in the instance, the process will stop. In the Installed Modules tab of Module Management window the modules that are installed in the system are displayed, here it is also possible to see information about the modules. To update modules remotely, just click on the Scan for updates button. This process will look in the Central Repository for all the latest compatible versions of the modules installed in the Openbravo instance and will show them as update available.

When there are updates available, a message is shown next to each module and on top of the modules box. It is possible to install the update for just one of the modules by clicking on the link on the left or the module, or to install at once all the available updates by clicking in the link on top of the box.

After doing any of these two actions the installation process will start. Updates through obx files are done, in the same way as installation from file system , from the Add Modules tab clicking the Browse File System button. If in this window is selected a obx file containing a newer version of an already installed module, this module will be updated to this version.

To uninstall modules select them in the modules box and click on the Uninistall selected button. This process will remove the module from modules directory, after uninstalling modules a system rebuild is requiered.

You can apply reference data at client or organization level, so, for example, if a client has two organizations in two different regions, you can apply the appropriate regional accounting structures to each organization. This page has been accessed 21, times. This page was last modified on 27 July , at View source Discuss this page Page history Printable version. Do you want to add them? Participate Communicate Report a bug Contribute Talk to us now!

All modules have a dependency on User Interface Application and in turn, it has a dependency on Openbravo core. In the Dependency window, specify that the module is dependent on User Interface Application.

DB Prefix :at least one db prefix is required when a module also contains database artifacts table, column, constraints, etc. As other howto's in the developers guide will add database artifacts, let's specify at least one DB prefix. Data Package: Tables are linked to a module through the Data Package.

The generated business object for the new table will use the Java Package defined in the Data Package. Other howto's in the developers guide will add new tables so there is a need to specify a data package as illustrated in the image below. At this point you are ready to develop the software artifacts required for the functionality of the module. While developing the relation to the module is maintained in different ways:.

Exporting a module creates a directory for your module under Openbravo ERP root directory and the appropriate XML files for inclusion in the finished module. Modules that are not flagged as being in development are not exported - remember that you must select the In Development checkbox when you define a new module, otherwise it will not be exported. Since we do not have any additional developments yet, only the corresponding folder structure and the module descriptor XML files have been created at this point.

Openbravo ERP validates the database and module artifacts of a module when the module is exported and packaged. See more information on the database validation step.

For a detailed description of this export. The Java package in the source directory should start with the Java package of the module. So for this case org. If using Eclipse , add the newly created module's src folder to the build path of the Eclipse project Java Build Path :. This makes it possible for Eclipse to build the code and have a full-functional Java editor when editing the source code of your module. All modules have a dependency on Openbravo core. In the Dependency window, specify that the module is dependent on core.

DB Prefix :at least one db prefix is required when a module also contains database artifacts table, column, constraints, etc. As other howto's in the developers guide will add database artifacts, let's specify at least one DB prefix.

Data Package: Tables are linked to a module through the Data Package. The generated business object for the new table will use the Java Package defined in the Data Package. Other howto's in the developers guide will add new tables so there is a need to specify a data package as illustrated in the image below.

At this point you are ready to develop the software artifacts required for the functionality of the module. While developing the relation to the module is maintained in different ways:. The Java package in the source directory should start with the Java package of the module. So for this case org. If using Eclipse , add the newly created module's src folder to the build path of the Eclipse project Java Build Path :. This makes it possible for Eclipse to build the code and have a full-functional Java editor when editing the source code of your module.

Exporting a module creates a directory for your module under Openbravo ERP root directory and the appropriate XML files for inclusion in the finished module.

Modules that are not flagged as being in development are not exported - remember that you must select the In Development checkbox when you define a new module, otherwise it will not be exported. Since we do not have any additional developments yet, only the corresponding folder structure and the module descriptor XML files have been created at this point.

Openbravo ERP validates the database and module artifacts of a module when the module is exported and packaged. See more information on the database validation step. For a detailed description of this export.