OpenXpertya

openXpertya is an open source comprehensive management solution for companies in Spanish that encompasses ERP and CRM, with integration of B2B or B2C online services (depending on the type of end customer) and even B2E (internal services) and with data export support (links) to the EDI standard (electronic exchange of information between companies: invoices, delivery notes, orders: EDIFACT, UN global standard) and with the possibility of working with multidimensional cubes OLAP (exhaustive analysis of results). All of this is closely adapted to Hispanic and Latin American legislation, both tax, commercial, civil, accounting, etc.

The purpose of openXpertya is to cover broadly, and very closely, all those management needs that a medium or large-sized company could have. It is the global planning of all the company's resources.

All information about the openXpertya application (status, errors, improvements, etc.) is also open, there is no corporate hiding policy or censorship. If something doesn't work, it won't hurt to find out quickly. As a consequence, openXpertya and Open Source projects in general are very quick to react if problems arise or rapid changes to the code are necessary based on certain needs.

Factual background

openXpertya is based on the previous project, also free software called Xpertya.

OpenXpertya Public License

All openXpertya code is licensed under the openXpertya LPO Public License. This license is published in Spanish and is a legal translation, with the necessary adaptations required by changes in legislation of the original SUN CDDL, approved as an open source license by the OSI on January 14, 2005.

The openXpertya Public License includes the same terms of the SUN CDDL license, adding the possibility of relicensing the new code under any other type of license that respects the conditions of this one and expressly under the LGPL license in any case.

The openXpertya Public License was created due to a specific need, by reusing and modifying code from several previous applications with different free software licenses. The only Possible License that allows the maximum possible freedom and at the same time respects the conditions of the free software licenses of each of the modified or reused pieces of code is the CDDL. Which explicitly indicates that the parts of the code extracted from the total product are once again governed by the original license, while the product itself is governed by the LPO itself. To also allow maximum reuse of the new code, its relicensing under the LGPL license or under any other type of free software license is expressly permitted.

This license grants users and programmers all of the four freedoms of free software, and makes it possible to reuse the code along with any other code, regardless of whether it is governed by the license.

OpenXpertya architecture

openXpertya, through the three-layer design environment (3LD or layered programming), provides a methodology for declaring business concepts, defining the interaction with the system, processes to be carried out on the concepts, and finally establishing restrictions to this model and validations.

Thus the three layers, developed under J2EE, are defined in the openXpertya project as follows:

1. In the data layer we have the relational database engine, independent of the application and scalable according to the needs of the final company. The current version of openXpertya works on Oracle, for its power and for being a market standard, but additionally in the following release there will be availability for the use of other database engines such as (Daffodil One$DB, PostgreSQL, Firebird and Sybase ASE Express Edition on Linux).
2. In the Application or Business Server layer, we have the JBOSS application server and the java classes that interact directly with the database (via JDBC).
3. In the Presentation layer we have several possible customers. The main and its packaging variants (direct distribution, via Java Web Start or applet Java), performed directly in Java; but additionally we also have a light client on the web browser (against the JSP pages served from the Apache Tomcat server integrated in JBOSS) with various possible configurations based on the needs of the business processes of the user company and depending on the user's role type that opens in each specific moment.