Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

JBoss Fuse - Fuse workshop 101 - Part One

DZone's Guide to

JBoss Fuse - Fuse workshop 101 - Part One

· Integration Zone
Free Resource

Share, secure, distribute, control, and monetize your APIs with the platform built with performance, time-to-value, and growth in mind. Free 90-day trial of 3Scale by Red Hat

On my way to Hong Kong for a day of workshop on JBoss Fuse, and as I go through my Slide deck, I cannot find any decent easy workshop for beginners. Therefore I decide make a workshop that is easy for Camel first timer to get their hands dirty.

The first of part of the workshop is an introduction to Camel, it first goes through what is exactly inside JBoss Fuse.

For part one of the workshop, it takes your through the very basic of Camel, one of the very important component inside JBoss Fuse.
Every Camel need to have a runtime container to run in, inside camel we call it a CAMEL CONTEXT.  Inside every Camel context, you can define lots of camel route and registry, don't worry about what those are, we will explain later.










So inside out blueprint xml, you will see a tag called camelContext.



















Next up is camel route, they are a chain of command or process defined by you, as a developer.
Inside the camel route, there are consumer endpoints that listens to the incoming messages, producers the sends message to the destination. and Processor handles validations of the messages, transform message formats and calls the business logics. Basically anything you want to do with the message.





















And the message that is routing throughout the camel route is packaged inside Exchange.
Think of Exchange as an envelope that contains the message from previous step, and message to the next step, on the envelope there will be address of the sender and receiver. If there are any problem with the delivery, there will also be problem stamped or states on top of it, shows what's wrong.






















Each endpoint on Camel has a URI, this URI needs to fill in by you.












And lastly, using Maven to help you build a Fuse project. it'll take care of the 3 nasty things for you, first it's going to generate a profile layout for you by selecting the right archetype. Secondly, you can manage project dependency with i, just like normal maven project. And last but not least, a maven plugin call fabric8 will help you package and deploy your project.














Here are the slides for the workshop:

And here are the lab instructions:


Enjoy!

Continue on to
Workshop part 2 - Data Transformation
Workshop part 3 - Enterprise Integration Patterns

Explore the core elements of owning an API strategy and best practices for effective API programs. Download the API Owner's Manual, brought to you by 3Scale by Red Hat

Topics:

Published at DZone with permission of Christina Lin, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}