Nils Preusker

technical consultant

camunda services GmbH

camunda

consulting company

with a strong focus on

BPM

business

IT

alignment

BPM

Business

Process

Management

BPM

Life Cycle

Process

Discovery

Process

Documentation

Process

Analysis

Process

Design

Process

Implementation

Process

Controlling

OMG*

Standard

* Object Management Group

Version

2.0

released in

2011

Model

and

Notation

BPM + Java =

Let's start with an example:

Imagine you expect

a file

to be dropped...

into a

folder

... the file might contain

XML

or CSV data.

So we'll need to

transform it

... before we can pass it to some service for further processing.

In Java, this would require a lot of

Code

While in Camel, we can just write:

from("file:///my/dir").
  unmarshal(...).
  to("bean:myService");
      

less code
=
fewer bugs

But there is more...

Camel

allows you to specify all kinds of

end-points

in order to work with different

transports

End-points

are usually specified by a

URI or URL

such as file:///some/directory

transports

refer to the underlying

protocol

i.e. file, HTTP or FTP

Camel provides a

simple

programming

interface

to technologies that are otherwise

complex

...and Camel also provides

standard

implementations

for common

integration tasks

EIPs*

(*Enterprise Integration Patterns)

One such pattern is the Message Endpoint: "How does an application connect to a messaging channel to send and receive messages?"

Another example is the Message Translator: "How can systems using different data formats communicate with each other using messaging?"

EIPs

provide a

graphical

notation

as well as a

common

language

for common integration tasks