|
|
| (3 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | Adempiere Enterprise Solution Conceptual Glossary Is A Unified Adempiere Language (UAL):
| + | #REDIRECT [[Glossary]] |
| − | Lets Start Learning Our New Language :+)
| + | |
| − | (Soheil Qanbari)<br>
| + | |
| − | '''Adempiere Architecture Solution UAL'''
| + | |
| − | Architecture is King... ;)
| + | |
| − | | + | |
| − | '''A'''
| + | |
| − | Application Dictionary (AD) :
| + | |
| − | AD is the most important developer tool given by Adempiere.Like Elements, Tables,
| + | |
| − | Columns, References, Windows, Tabs, Fields, etc.
| + | |
| − | Architecture:
| + | |
| − | The fundamental organization of a system, embodied in its components, their relationships
| + | |
| − | to each other and the environment, and the principles governing its design and evolution.
| + | |
| − | Architecture has two meanings depending upon its contextual usage:
| + | |
| − | 1. A formal description of a system, or a detailed plan of the system at component
| + | |
| − | level to guide its implementation
| + | |
| − | 2. The structure of components, their inter-relationships, and the principles and
| + | |
| − | guidelines governing their design and evolution over time.
| + | |
| − | Architecture Description:
| + | |
| − | An architecture description is a formal description of an information system, organized in
| + | |
| − | a way that supports reasoning about the structural properties of the system. It defines
| + | |
| − | the components or building blocks that make up the overall information system, and
| + | |
| − | provides a plan from which products can be procured, and systems developed, that will work
| + | |
| − | together to implement the overall system. It thus enables you to manage your overall IT
| + | |
| − | investment in a way that meets the needs of your business.
| + | |
| − | Architecture Framework:
| + | |
| − | An architecture framework is a tool which can be used for developing a broad range of
| + | |
| − | different architectures. It should describe a method for designing an information system
| + | |
| − | in terms of a set of building blocks, and for showing how the building blocks fit
| + | |
| − | together. It should contain a set of tools and provide a common vocabulary. It should also
| + | |
| − | include a list of recommended standards and compliant products that can be used to
| + | |
| − | implement the building blocks.
| + | |
| − | | + | |
| − | '''C'''
| + | |
| − | Callout :
| + | |
| − | A callout can be looked at as an extension at the field level.
| + | |
| − | | + | |
| − | '''D'''
| + | |
| − | Data Dictionary:
| + | |
| − | A data dictionary is a set of metadata that contains definitions and representations of
| + | |
| − | data elements. Within the context of a DBMS, a data dictionary is a read-only set of
| + | |
| − | tables and views. The data dictionary is database in its own dictionary. Amongst other
| + | |
| − | things, a data dictionary holds the following information: <br>
| + | |
| − | * Precise definition of data elements
| + | |
| − | * Usernames, roles and privileges
| + | |
| − | * Schema objects
| + | |
| − | * Integrity constraints
| + | |
| − | * Stored procedures and triggers
| + | |
| − | * General database structure
| + | |
| − | * Space allocations
| + | |
| − | | + | |
| − | '''E'''
| + | |
| − | Enterprise:
| + | |
| − | An Enterprise in this context " Enterprise Architecture" is any collection of
| + | |
| − | organizations that has a common set of goals and/or a single bottom line. In that sense,
| + | |
| − | an enterprise can be a government agency, a whole corporation, a division of a
| + | |
| − | corporation, a single department, or a chain of geographically distant organizations
| + | |
| − | linked together by common ownership.
| + | |
| − | Enterprise Modeling:
| + | |
| − | Enterprise modelling is the process of improving the enterprise performance through the
| + | |
| − | creation of enterprise models. This includes the modelling of both business processes and
| + | |
| − | IT.Also An enterprise model is a computational representation of the structure,
| + | |
| − | activities, processes, information, resources, people, behavior, goals, and constraints
| + | |
| − | of a business, government, or other enterprises.
| + | |
| − | | + | |
| − | '''M'''
| + | |
| − | Meta Data:
| + | |
| − | Metadata is structured, encoded data that describe characteristics of information-bearing
| + | |
| − | entities to aid in the identification, discovery, assessment, and management of the
| + | |
| − | described entities.Also Metadata is a set of optional structured descriptions that are
| + | |
| − | publicly available to explicitly assist in locating objects.
| + | |
| − | | + | |
| − | Module :
| + | |
| − | A New Module in Adempiere is * Table-Column structure * Input handling and validation
| + | |
| − | rules * Document Type & Print Format * Define Default Accounts * Workflow Process *
| + | |
| − | Callout definition and process-button definition consolidated via Report & Process *
| + | |
| − | Final Consolidation in Windows under the Menu tree
| + | |
| − | | + | |
| − | '''P'''
| + | |
| − | Package Description: (Contributed By [[User:Bmovaqar|Bahman]])
| + | |
| − | org.compiere.swing :
| + | |
| − | Expands nearly all 'swing' widgets' capabilities to adhere to ADempiere conditions
| + | |
| − | (popup, LaF, etc.)
| + | |
| − | org.compiere.grid :
| + | |
| − | Shows tabs, table and controls grid and single row display. In other words, manages the
| + | |
| − | top-level entities in a window (ie. tab, table, tabpane and grid display)
| + | |
| − | org.compiere.minigrid :
| + | |
| − | Manages entities inside a grid (what org.compiere.grid offers); ie. checkbox rendering,
| + | |
| − | column information, selected row ID, etc.)
| + | |
| − | org.compiere.ed :
| + | |
| − | Provides utilities such as calculator and calendar. Also, offers editors of several
| + | |
| − | types eg. HTML editor and has some useful visual classes inside, like file location
| + | |
| − | dialoque or color editor dialogue. In addition contains some visual forms to enter data
| + | |
| − | in, mostly for the sake of control.
| + | |
| − | org.compiere.grid.tree :
| + | |
| − | Handles displaying trees and panels they are shown inside of.
| + | |
| − | org.compiere.plaf :
| + | |
| − | Concentrates on LaF and related issues like translation.
| + | |
| − | org.compiere.apps :
| + | |
| − | Uses org.compiere.swing, org.compiere.grid, org.compiere.minigrid, org.compiere.ed to
| + | |
| − | show application windows and dialogues, eg. process, process parameters, login dialogue.
| + | |
| − | It also contains the application applet.
| + | |
| − | org.compiere.apps.forms :
| + | |
| − | Using facilities in org.compiere.apps shows forms that do something behind without using
| + | |
| − | processes.
| + | |
| − | org.compiere.apps.graph :
| + | |
| − | Provides some basic graphic utilities and handles graphs and diagrams.
| + | |
| − | org.compiere.apps.search :
| + | |
| − | Contains search and find dialogues, also some useful info windows, eg. InfoBPartner,
| + | |
| − | InfoGeneral, InfoPayment; and VSchedule, VschedulePanel, VScheduleTimePanel (??).
| + | |
| − | org.compiere.apps.wf :
| + | |
| − | Provides classes to display WF nodes, panels, etc.
| + | |
| − | org.compiere.impexp :
| + | |
| − | Offers processes and Mclasses to handle import, import format and conversion of OFX to
| + | |
| − | XML.
| + | |
| − | org.compiere.cm :
| + | |
| − | Some basic request handlers (eg. login, BPartner creation, update, etc.), broadcasting
| + | |
| − | utilities and finally a string utility class.
| + | |
| − | org.compiere.cm.cache :
| + | |
| − | Manages web caches, eg. container, container element, web projects, etc.
| + | |
| − | org.compiere.cm.extend :
| + | |
| − | Nothing to be said!
| + | |
| − | org.compiere.cm.request :
| + | |
| − | Provides classes for request creation and update.
| + | |
| − | org.compiere.cm.utils :
| + | |
| − | Offers facilities such as access logger, request analyser and tree to XML.
| + | |
| − | org.compiere.cm.xml :
| + | |
| − | XML generation from XSLT templates.
| + | |
| − | org.compiere.db :
| + | |
| − | Provides database interfaces for Adempiere RDBMS (Oracle, PostgreSQL, DB2, etc.) and
| + | |
| − | drivers which handle the top-level operations such as shutdown, working with catalogues
| + | |
| − | and data sources and etc. It also provides a connection dialogue and a utility to
| + | |
| − | recreate ADempiere's database.
| + | |
| − | org.compiere.dbPort :
| + | |
| − | Converison of SQL to database's native SQL and JDBC performance test.
| + | |
| − | org.compiere.install :
| + | |
| − | Handles issues related to setup & installation, like application server configuration,
| + | |
| − | database configurtion, etc.
| + | |
| − | org.compiere.jsf :
| + | |
| − | Provides dynamic action listener and field lookup, property resolver and some facilities
| + | |
| − | for web UI such as menu.
| + | |
| − | org.compiere.ldap :
| + | |
| − | As the name implies, handles LDAP connectivity.
| + | |
| − | org.compiere.model:
| + | |
| − | Contains the whole solution's model classes (M & X), also persistent object, payment
| + | |
| − | processors and scheduling and scriptlet model.
| + | |
| − | org.compiere.PackOut :
| + | |
| − | Module integration and extraction management
| + | |
| − | org.compiere.pos :
| + | |
| − | POS window and panels display.
| + | |
| − | org.compiere.print :
| + | |
| − | Contains application archive & report engine wrappers and handles report control and
| + | |
| − | display as it contains all the print element's model classes.
| + | |
| − | org.compiere.print.layout :
| + | |
| − | Holds the application print engine and handles the page layout.
| + | |
| − | org.compiere.process :
| + | |
| − | The repository of nearly all processes it the system. They vary extensively.
| + | |
| − | org.compiere.report :
| + | |
| − | Some semi-process report engines (?) and report models, eg. report column and report
| + | |
| − | line.
| + | |
| − | org.compiere.report.core :
| + | |
| − | Handles report creation.
| + | |
| − | org.compiere.server :
| + | |
| − | Provides several servers including accounting, alert and e-mail.
| + | |
| − | org.compiere.session :
| + | |
| − | Provides ADempiere session and status beans.
| + | |
| − | org.compiere.sla :
| + | |
| − | SLA assertions: delivery accuracy and goal process.
| + | |
| − | org.compiere.sqlj :
| + | |
| − | SQLJ helpers; also provides account, Bpartner, payment, invoice, etc. related functions.
| + | |
| − | org.compiere.tools :
| + | |
| − | Contains file utilities and an RMI registry lister.
| + | |
| − | org.compiere.util :
| + | |
| − | Offers cache, cache management, log management, logging facilities, database related
| + | |
| − | utilities, language management and a lot more.
| + | |
| − | org.compiere.wf :
| + | |
| − | Focuses on WF elements' models as well as the document WF manager, activity manager,
| + | |
| − | process manager and WF validation.
| + | |
| − | org.compiere.web :
| + | |
| − | Provides server monitoring and status.
| + | |
| − | org.compiere.wstore :
| + | |
| − | Web store: that's all!
| + | |
| − | org.compiere.www :
| + | |
| − | Holds several servlets such as login, lookup, process, window, etc. lookup.
| + | |
| − | | + | |
| − | | + | |
| − | '''R'''
| + | |
| − | Routing:
| + | |
| − | A routing is a description of which operations (process steps) have to be carried out and
| + | |
| − | in which order to produce a material (product).
| + | |
| − | | + | |
| − | '''S'''
| + | |
| − | SQL Procedure :
| + | |
| − | An SQL Procedure can be looked at as an extension at the process level.
| + | |
| − | | + | |
| − | '''T'''
| + | |
| − | 2Pack :
| + | |
| − | It's related with Translating Dictionary Modifications from one Adempiere system to
| + | |
| − | another.
| + | |
| − | | + | |
| − | '''X'''
| + | |
| − | XML2AD :
| + | |
| − | It imports several XML files into the database in order to modify the Application
| + | |
| − | Dictionary of ADempiere.
| + | |
