JFire

Infobox_Software
name = JFire



caption =
developer = [http://www.NightLabs.org www.NightLabs.org]
latest release version = 0.9.4-beta tough trader
latest release date = release date|2008|7|7
operating_system = Windows, Linux, Unix
genre = ERP, CRM, SCM
license = LGPL
website = [http://www.jfire.org/ www.jfire.org]

JFire is an ERP and CRM system.

The system has been written entirely in Java and is based on the technologies JavaEE 1.4 (formerly J2EE), JDO 2, Eclipse RCP 3. Hence, both client and server can easily be extended and it requires only a relatively low effort to customize it for specific sectors or companies.

Currently, JFire is still in the beta status of development, but it already provides modules for user and access rights control, accounting, store management, direct online trade with other companies or end-customers (e.g. via a web shop), an editor for 2-dimensional graphics and other useful plugins. A reporting module which is based on BIRT allows for the editing and rendering of reports, statistics and similar documents (e.g. invoices).

Even though the main goal of the project is to serve as a robust and flexible framework and thus to ease the implementation of sector-specific applications, it contains modules for the out-of-the-box usage in small and medium-sized enterprises.

Because JFire uses JDO as persistence layer, it is independent of the underlying database management system (DBMS) and spares developers the error-prone work of writing SQL. Furthermore, the use of JDO makes it possible to employ other DBMS types (e.g. object databases). According to the project's website, JFire is shipped with the JDO2 reference implementation JPOX, which supports many relational databases and db4o.

Even though JavaEE, JDO and Eclipse RCP provide many advantages, they have the disadvantage that they require a longer training period than older technologies (e.g. direct SQL).

JFire was published in January 2006 under the conditions of the GNU Lesser General Public License (LGPL). Therefore, it is Free Software and everyone can redistribute it, modify it and use it free of charge.

History

The history of JFire starts in 2003, when the company NightLabs decided to develop a new ticket sales and distribution software. Because they wanted to base this new system on an ERP within one integrated application suite (rather than multiple separate programs), they started to search for a suitable framework. After some research and evaluations, they decided to launch such an ERP framework project based on new technologies like JDO and Eclipse RCP, which make it easy for other projects to build upon.

When first released in January 2006, it quickly gained attention in the Eclipse community: The German Eclipse Magazine published an article in May 2006 [cite journal | title=Eclipse Magazine (Germany) | year=2006 | volume=7 | issue=3.06 ] , the project was invited to the EclipseCon 2006 [cite web | title=EclipseCon 2006: JFire - Open Source RCP based ERP framework | url=http://www.eclipsecon.org/2006/Sub.do?id=406 | date=June 23, 2006| accessdate=2007-07-06] , the Eclipse Magazine India published an article in December 2006 [cite journal | title=Eclipse Magazine (India) | year=2006 | volume=5 ] and in April 2007, the JFire project was invited to the Eclipse Forum Europe, where it impressed the BIRT team with its graphical parameter workflow builder [cite web | title=BIRT World: JFire and BIRT | url=http://birtworld.blogspot.com/2007/05/jfire-and-birt.html | date=May 15, 2007| accessdate=2007-07-06] .

Goal

The project's main goal is to provide a framework which eases development of sector-specific ERP systems. In this aspect, it differs significantly from most other ERP projects, which aim primarily at being an out-of-the-box solution directly for end-users.

The JFire project team believes that the demands directed at ERP software vary in such a high degree, that a complete solution has some major disadvantages: In their opinion, such one-fits-all-solutions confront their users either with too much configuration and too little clarity or do not provide enough flexibility.

Therefore, most of the numerous JFire modules serve mainly as a base for extensions and cannot be used directly by end users (or only partially).

Architecture

JFire consists of two parts - the server and different types of clients. So far, the most comprehensive client is a rich client. Additionally, there exists a JSP web client, which currently supports only a part of the functionality (e.g. a web shop). Some applications built on JFire employ other types of clients, as well (e.g. mobile devices used in Yak, an access control system). Because JFire enables different companies/organisations to cooperate directly, a server acts as client to other servers, as well. Each organisation has its own JDO datastore, which guarantees a very high degree of protection of privacy. Between organisations, only data essentially required by the business partner are exchanged.

Following the framework idea, JFire is built very modular: In the client, it consists of OSGi plug-ins based on the Eclipse Rich Client Platform (RCP) and in the server, JFire is composed of JavaEE EAR modules. Due to its modularity, JFire is used as base for non-ERP applications, too, which employ a smaller number of modules (e.g. only the user, access rights and organisation management).

References

External links

* [http://www.jfire.org www.jfire.org - Official Project Site]
* [http://www.jpox.org/docs/guides/jdo/jfire/index.html JPOX.org, Tutorials and Examples: JFire: JDO2 in use]