European ADempiere Conference Day2

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.


Introduction from the vice president of FHTW

A nice welcome by the vice president, he is welcoming us all and gives some background info about the university. It is located in the former East-Berlin. The university is founded in 1992 as a daughter of TFH, became independent in 1994. The univ has 4 major pilars, Engineering, Computing, Economics, Design. Each of this pilars has a number of main fields of pratice. The university is has 5 locations spread out in Berlin, which also means that traveling from the one to the headquartes takes more then an hour. They are also busy with building a new location, which should simplify a lot for the university.

Ajax client - Posterita

Talk session give by Frederic Tsang, a bit of a hold up in order to get the vnc working and such.

Rational Ajax

  • Application Service Provide
  • Remote access from outside the office
  • Easy deployment
  • Upgrades client easily done
  • Minimize security risks.

Technology Choice

  • Why ZK
    • Vibrant community and among the top projects in Sourceforge
    • Good framework and roadmap
    • Easy development
    • Swing

Technical Breaktrough

  • Adempiere structure
    • Model driven architecture
    • UI definition in DB
  • Adempiere WebUI beta
    • High code complexity
    • Try to replicate functionalities whereby previous mentioned frameworks has exceled.
  • The contect challenge
    • Env.getCtx() is static access to context and is referenced 1549 times in the MayDay release
    • Web is a multi-user environment and retrieving the context for a specific user is a real challenge.

Posterita has solved this problem with their webUI.

Code sample

General speaking ZK is much java alike,which makes transition easier for java developers.

Code sample will be filled in later, once the slides of the presentation are published.

Current Posterita Team

  • Ashley
  • Sendy - Developer
  • Hengsin - Developer

Current status

  • Most window features have been implemented
  • Zoom functionality Implemented
  • item missing couldn't type fast enough :)

Future work

  • Refactoring the Swing client and the ZK client to limit duplicate code
  • Remaining task to be done
    • Grid view
    • Search functionality
    • Processes
    • Reports

Quick Demonstration of Posterita

Flash based demo of Posterita, will be made available after the conference.


Posterita Point Of Sales (POS)

POS uses different technology, but still uses adempiere as back-end.

HR Module

Talk session give by Mahir Masala and Elvis Haracic from Human Resource @ ASA - Prevent Group. They also used Adempiere as a framework to implement their HR module.

About ASA Prevent Group

  • 18 organizations, 3000+ employees
  • 3 divisions
    • Production (5 production plants, carseats and bumpers)
    • Selling (8 organizations, exclusive importer of VW group)
    • Finance and services (5 organizations for insurance)


  • The module contains the standard functionality from adempiere, but has been expanded untill they reach more then 50 tables for Human Resources
  • Courses/Eductation sub-module
  • Vacations & Leaves sub-module
  • Competentions and NSP's sub-module
  • Goals and evaluations
  • Tons of reports

Still to do

  • Payroll integration
  • Financial integration
  • Workflows
  • Integration with Business Partners from adempiere


  • Localisation
  • Custom needs
  • Integration with Adempiere
    • Financial
    • Workflow
    • Project planning
    • Resources & Fixed Assets


Extra unscheduled Session - Call for interfaces

Talk session given by Jan Kantert who works part time in MC Marketing Company GmbH and about to go university after just finishing high school. Probably the youngest to dare face a bazaar in session.

Jan Kantert learned a few minutes before that somebody already implemented web services (SOAP) on Adempiere.

Captured on our irc channel: "Web Services on Adempiere = Adempiere on steroids".

That somebody is Lukasz Kolczynski and Maciej Lizewski. They blow everyone away with their sleek demo of now you don't have it, now you do prototype. They be publishing their steroids soon. This rewrites the law to It is most likely released earlier.

MC Marketing Company GmbH

  • Jan introduces where he works trying to use ADempiere which is a low price retail company

Why Interfaces

  • Not everybody loves Java.
  • Implementation of wireless barcode scanners
  • Automated import/export
  • Connect Business Intelligence software

Demonstration of SOAP interface

Nothing has changed on the server side, which makes an easy deployment possible. Build by using Codehaus XFire.


Preparing for Global Expansion: challenges and opportunities

Talk session given by Joel Stangeland of Idalica Inc. (USA)

Joel Stangeland gets ready

Why is there so much demand

  • Internet Market enables even the smallest companies to use the globe as market place
  • ERP is now an option for most companies, which wasn't the case when there was no opensource/free ERP software, and we all know how expensive SAP is.


  • Not enough people involved
  • Learning Curve, needs no further talk :)
  • Keeping developers who get trained


  • Training and Mentoring would include the following items
Awarded for striking achievement
    • Business Development
    • Implementation
    • Technical
    • Ideas?
  • Documentation
    • Need to make it easier to get started
    • Easier to find stuff
    • Ideas?
  • Rewarding Contributions
    • Project work
    • Marketplace - Adempierebusiness
    • Ideas?

Lunch break

The conference will now be split in 2 rooms, room one will have a workshop about the german localisation and room two will have a workshop about security and privacy. Since I don't speak german I will only cover the workshop about security and privacy.

Security and Privacy Workshop

Talk session by Timo Kontro

Security should be a very important issue for everybody, if one should ask them self the question on how important security is. Most would answer that is very important to them.

Should we publish security holes? And where should we publish them.

What is important and what is the priority of a security issue?

What is the point of publishing them if nobody reacts to it, what is the point of hidding issue when no one is able to see them.

Publishing security issues should be handle with a lot of caution, since our customers depend on how good or bad our security.

How did we manage security issues in the past, for those who don't know we already had a major security issue with the database password being shown in the preferences. Which did mean that every client could get the password.

One of the problems regarding the security is how we are going to handle security issues? The commit committee(CC) has decided that somebody should take the role of head of security. The CC suggested that Timo Kontro should take this role, which he accepted.

Discussion about who we are going to publish and more important which details are going to be published.

Business Development

Talk session given by Donald Ladwig from Idalica Inc.

Donald explaining why you need a Big Mac

ADempiere Community

  • Developers (Technical Focus)
  • Users (Functional Focus - ADempiere User Group)
  • System Integrators (Technical and Functional)

ADempiere User Group

For many users the interface of Sourceforge can be intimidating or too technical. Some users dare not ask questions on a forum for fears of flames.

System Integrators

There should be some sort of certification on the system integrators.

Private forums or not

One of the challenge is how open/closed do we have to be, a complete open forum for partners and customers is something which many customers/partners will object to. It is not about sharing information, it is more about business who want to protect their assets. Most of the time it is the customer who forces you to close up certain information.

Frederick Tsang suggested of setting up a social network to tackle this problem.

Examples of ADempiere implementations

Project Paradigm

Workshop: Developers Documentation

A group of software developers discussed which documentation would help developers, new as well as advanced, in Adempiere development.

The results are collected in the outline for a new Adempiere Developer Corner.

Talk about ADempiere to FHTW Students

Kai and the Schaeffer AG story

Talk session given by Kai Schaeffer

Kai gives a few other closed source ERP programs, and asks if any student has heard of Compiere. Explains a bit about the free nature of open source software. And he also gives a quick introduction on his company Schaeffer AG, this is a repairshop for frontpanels of various machines.

Due to the nature of their business they had very specific requirements for an ERP system. When they went on the market to buy an ERP package, they found out that most of the packages won't enabled them to adjust to their needs. The open source nature of compiere/adempiere enabled them to adjust the ERP package to their specific needs. They appointed someone in their business to get to known compiere/adempiere. They also saw the benefits of the community.

A very quick overview how adempiere was born, using the very well known bazaar and cathedral phrase.

Talk about Adempiere as an Application Framework

Fred tells the whole story

Talk session given by Frederick Tsang

Definition of Framework

A software framework is a reusable design for a software system (or subsystem). This is expressed as a set of abstract classes and the way their instances collaborate for a specific type of software (Johnson and Foote 1988; Deutsch 1989). Software frameworks can be object-oriented designs. Although designs don't have to be implemented in an object-oriented language, they usually are. A software framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project. Various parts of the framework may be exposed through an API. (Taken from

Application Networks

  • Banks do not know how to make GOOD software
  • It is not their business
  • No bank wants ready-made software (off the shelf)
  • Every one has different complex types of derivatives
  • Built a framework for these banks
  • Banks leapfrog development by using JRisk
  • JRisk is a framework

Application Networks becomes Reuters Financial

in other words they got acquired


  • Application framework
  • To make something simple it is hard, to make something hard it is simple
  • Own test framework, No JUnit
  • Own DB Layer, No Hibernate
  • Own webframework

New adventure

  • Learn from previous experiences
  • built a web application
  • used JUNit
  • Used Hibernate

Not enough

  • Kept increasing scope of software
  • maintenance was getting difficult
  • Things that were not necessary before became essential
  • example Invoicing was not need so was export to PDF

Future is Open Source

  • Follow the money
  • VCs increasingly unwilling to invest in a company that doesn't leverage open source
  • Enterprises looking for open source
  • Over the next 10 years most software will move to open source licensing

Value Proposition

  • Vendors: Alignment with customers
  • Customers

Finally an Answer

  • Adempiere is an opensource ERP/CRM
  • Not only a framework but a business application framework
  • Although not perfect, it is by far the best option available
  • The product is good technically
  • Philosophical underpinning is strong

Future Proof

  • Consistently ranked top 5 in
  • Strong community
  • Everyone has a voice
  • Adempiere is here is to stay

Open target

  • unique in adempiere
  • open source vs open target
  • the degree of openness is beyond any project
  • easy to start a new project within adempiere
  • open source but also open to contribute

Web Applications

  • Dealer communication system
  • reworked webstore


We will assist a diversity of verticals built on Adempiere.

Why contribute

The bazaar way by Red1

Small Flash based demo of Posterita

Which ended with some windows of compiere

Talk session given by Redhuan D. Oon

Red1 attempts more german words

ERP is complex, no matter which view point a person takes. He starts by explaining what a community is all about. He gives some information on how he got involved with compiere, by taking out of his guestbook, worldwide praise to get the energy going.

Adempiere Foundation

Talk session given by Joel Stangeland from Idalica Inc.

Reasons why it's good to have a legal entity

  • There is a company behind a piece of software
  • From a copyright point of view - easier to have one name instead of many names
  • To protect your Intellectual Property
  • To act as a governor of public goods
  • Customers demand a legal entity
  • Process for managing contributed funds
  • In case we are approached by a centralized project
  • Coordination role for creating infrastructure and marketing
  • Marketing issues should be managed central, like for our mayday release
  • Manage contributions
  • Holding trademarks
  • Convergence (talk to other projects)

Reasons why it's bad to have a legal entity

  • It should not be confused with the control for the project or the bazaar
  • Threat of being sued by Compiere
  • Impression that this is the only 'right' entity to offer services/projects

General principles of the Adempiere Foundation:

  • Rules of Transparency
  • Rules on Conflict of Interests
  • Rules of Accountability
  • Non-profit (public good/social enterprise)
  • Non-discriminatory (race, religion, country, gender)
  • Guidelines to protect from direct competition with external providers
  • Salary guidelines in place
  • Caretaker of community
  • Mgmt team should have representations from (1) End Users, (2) Developers and (3) Implementors
  • Rules of Non-exclusion
  • It should be simple / minimal
  • Everlasting
  • Cannot be stopped
  • No one owns it
  • Independent from business side

A committee was formed to review the principles, draft by-laws and propose the activities of the foundation.

The following are members of the Review Committee:

The timeline to complete the review is 1 month, by June 30th, 2007.

You can keep up to date with the The Foundation Project in the wiki.

See Also