Difference between revisions of "Software Developer's Guide"

From iDempiere en
m
(included JPiere)
Line 37: Line 37:
  
 
== Localization ==
 
== Localization ==
−
* [[Localization]] using language packs
+
* [[Localization]]: use of language packs
−
* [[Install german language Pack|Example of German localization]] by changing country settings and installing a language pack
+
* [[Install german language Pack|Example of German localization]]: example of changing country settings and installing a language pack for Germany
 
* [[Multi-Lingual_Jasper|Multilingual reports in Jasper]]
 
* [[Multi-Lingual_Jasper|Multilingual reports in Jasper]]
 +
* [[Plugin: JPiere (Localization Japan)|JPiere set of iDempiere Plugins for Japan]]: still work in progress so documentation is incomplete
  
 
== Integration ==
 
== Integration ==

Revision as of 09:02, 24 August 2017

This guide explains to Software Developers and System Administrators how to configure and customise iDempiere. Solid technical experience is required.

Status: This is Work in Progress, but it may be useful as it is.

Introduction

The core iDempiere system supplies a range business functionality straight out of the box, such as role-based access, organisational structure, accounting, procurement, warehousing, and so on, but it is also flexible enough to be adapted to meet new requirements as they arise, using these mechanisms:

  • Configuration: changing the system using built-in facilities such as modifying field labels, setting parameters, modifying workflows, and using report-writers;
  • Localization: adapting the system for a specific country, region or language by adding locale-specific components and translating the terminology;
  • Integration: linking disparate software applications and platforms using predefined interfaces so that the subsystems function together as one system to support the enterprise objectives;
  • Extension: creating new functionality by adding database attributes and plugins which do not affect the core system;
  • Modification: you have access to the source code so you can turn your system into a tar pit, or big ball of mud, so don't modify the code or database schema by hand unless you intend to push the code into the trunk.

This guide explains how iDempiere can be adapted to meet new business requirements, without changing the codebase.

Configuration

Login window

Themes

These themes can be installed as plug-ins. Use them as a base for developing your own custom theme.

Dashboard configuration

WorkFlows

Report Writer

Localization

Integration

Extension

Deploying externally developed plug-ins

The iDempiere community has developed a large collection of plug-ins and and made them available for download and deployment. These can deployed directly into the running application using the Apache Felix interface. The Eclipse development environment is not needed.

Development environment for customising plug-ins

You will need to set up the Eclipse development environment in order to develop plug-ins, as follows:

Developing custom plug-ins

Once the development environment has been set up, you can follow these guides to develop various types of plug-ins:

Deploying plug-ins

Plug-ins can be deployed and managed dynamically, using the Apache Felix Web Console:

Build a customised instance of iDempiere

Install and run iDempiere

Structure of iDempiere

  • Equinox OSGi framework: describes OSGi and the technology stack that was used to build iDempiere so you can see how the system hangs together
  • Eclipse Buckminster Component Assembly: looks at the use of Buckminster in the iDempiere project so that you can get a better understanding of the build process, and how Buckminster manages the components

References

Cookies help us deliver our services. By using our services, you agree to our use of cookies.