Party

User, person, organisation or other entity (where entity is not an OFBiz "Entity" but rather entity in the legal sense) implied in at least one process modelled and implemented by OFBiz.

eg : administrator of the website; a company dealing goods and/or services via the website; an OFBiz customer assigned a unique party identifier, etc.

ERP

CRM

E-Business

E-Commerce

The buying and selling of goods or services over electronic systems.

MRP

SCM

CMMS/EAM

Vendor

Role of a party that sells something with the system

Supplier

Role of a party that something if purchased from

Component

An OFBiz component is a directory used by the OFBiz framework to specify and load application server resources necessary to execute an OFBiz instance. Each OFBiz component must have a unique name (typically the name of the root directory for the component) and a configuration file called: "ofbiz-component.xml". Component resources may include, but are not limited to: webapps, Java source/classes, classpath resources, scripts, entity definitions, entity data files, service definitions, service and entity ECA rules, test suites, and encryption keystores. A component contains applications and/or the lower level tools and definitions needed by applications. A component can be used for self-contained extensions, including applications and logic/data modifications, to the suite of tools and applications that come with OFBiz.

Application

A part of Component (at the user level) beginning with the ~webapp directory. A single component may contain several applications each mounted on a unique URL. Within each component, the "ofbiz-component.xml" file defines the available applications and how those applications shall be mounted on URLs.

Examples: OOTB the Accounting component has three applications: Accounting, AP and AR.