This article has multiple issues. Please help talk page. (Learn how and when to remove these template messages)( or discuss these issues on the Learn how and when to remove this template message)
|Developer(s)||Apache Software Foundation|
16.11.04 / January 2, 2018
|Written in||Java XML FreeMarker Groovy|
|License||Apache License 2.0|
OFBiz is an Apache Software Foundation top level project.
Apache OFBiz is a framework that provides a common data model and a rich set of business processes. All applications are built around a common architecture using common data, logic and process components. Beyond the framework itself, Apache OFBiz offers functionality including:
All Apache OFBiz functionality is built on a common framework. The functionality can be divided into the following distinct layers:
Apache OFBiz uses the concept of "screens" to represent the Apache OFBiz pages. Each page is, normally, represented as a screen. A page in Apache OFBiz consists of components. A component can be a header, footer, etc. When the page is rendered all the components are combined together as specified in the screen definition. Components can be Java Server Pages ([JSP]s) <deprecated>, FTL pages built around FreeMarker template engine, Forms or Menus Widgets. Widgets are an OFBiz specific technology.
The business, or application layer defines services provided to the user. The services can be of several types: Java methods, SOAP, simple services, workflow, etc. A service engine is responsible for invocation, transactions and security.
Apache OFBiz uses a set of well-established open source technologies and standards such as Java, Java EE, XML and SOAP. Although Apache OFBiz is built around the concepts used by Java EE, many of its concepts are implemented in different ways; either because Apache OFBiz was designed prior to many recent improvements in Java EE or because Apache OFBiz authors didn't agree with those implementations.
The data layer is responsible for database access, storage and providing a common data interface to the Business layer. Data is accessed not in Object Oriented fashion but in a relational way. Each entity (represented as a row in the database) is provided to the business layer as a set of generic values. A generic value is not typed, so fields of an entity are accessed by the column name.
Manage research, learning and skills at defaultlogic.com. Create an account using LinkedIn to manage and organize your omni-channel knowledge. defaultlogic.com is like a shopping cart for information -- helping you to save, discuss and share.