Translate to Different Languages!

Friday, September 19, 2014

A-MQ vs Fuse vs Fuse Service Works

I saw a blog from Zack at Vizuri comparing JBoss Fuse vs Fuse Service Works.  I thought it would be good to give a brief introduction to the integration products, A-MQ, Fuse and Fuse Service Works, and then share an excerpt from his blog on Fuse vs Fuse Service Works.  I also included some links around Camel on EAP.


JBoss A-MQ
  • Summary: JBoss A-MQ is a high performance, flexible, lightweight messaging platform.
  • Components: ActiveMQ on Karaf
  • High performance messaging-A reliable messaging platform that supports standard messaging paradigms for a real-time enterprise.
  • Cross-language and multi-protocol support-Allows native connectivity from applications written in Java, C, C++. Multiple transport protocols for exchanging data between applications, services and devices. Supports JMS 1.1, TCP, SSL, STOMP, NMS, MQTT, AMQP 1.0.
  • Cloud ready-Deploy on premise, in the cloud or in a hybrid configuration.
  • Download:
JBoss Fuse
  • Summary: JBoss Fuse is a lightweight integration platform.
  • Components: ActiveMQ, Camel, CXF, Fuse Fabric on Karaf
  • Pattern based integration framework-Leverage Apache Camel to provide a full-featured, easy-to-use and intuitive framework for quicker integration solutions.
  • Dynamic configuration and management-Change configuration while container is running. Easily deploy or update services across nodes while the ESB is running. 
  • Multiple connectivity options-Connect to external applications with connectors for JDBC, FTP/SFTP, HTTP/HTTPS, file,, SAP, Twitter, and more.
  • Full support of AMQP 1.0 - provides wire-level compatibility across connections
  • Vast library of connectors - over 150+ out-of-the-box-connectors via Apache Camel
  • Managed integration routes - start, stop, measure and trace Camel routes on-premise or in the Cloud
  • Improved high availability (HA) - embedded message store for shared-nothing HA
  • Download:
Apache Camel
Compose your applications from Enterprise Integration Patterns (EIPs) based on the popular Hohpe and Woolf EIPs.
Apache CXF
Integrate applications with SOAP, XML/HTTP and RESTful HTTP.
Apache ActiveMQ
Provides core messaging within the ESB and for integrating with other applications.
Apache Karaf
Offers a lightweight OSGI-based runtime container for managing the components that compose your applications.
Makes it simple to manage large and distributed, JBoss Fuse deployments from a central location.
JBoss Fuse Service Works
  • Summary: JBoss Fuse Service Works is a service design, development and integration platform
  • Components: Fuse component plus Switchyard, Overlord
  • Core ESB based on JBoss Fuse:
    • Apache Camel – enterprise integration pattern framework
    • Apache CXF – webServices, REST
    • Apache ActiveMQ – robust, high performance messaging
  • Additional value provided by JBoss Fuse Service Works:
    • Lightweight structured service development Framework
    • Service Governance
    • Business Transaction Monitoring
Camel on EAP

Fuse vs Fuse Service Works:

JBoss Fuse Service Works may be a better fit if your organization ... 
  • ​is currently heavily invested in Java™ EE 6 development. The Fuse Service Works service model is similar to that of JEE development. 
  • would like to take advantage of Java™ EE 6 components from your services. Since FSW is embedded in a JEE container, you have full access to JEE components such as persistence and the injection framework. 
  • uses JBoss Enterprise Application Server (EAP) for other components in your infrastructure. Administration tasks such as deployment, clustering, high availability are similar if not the same as that utilized for FSW. 
  • is looking for a robust design-time and runtime service governance platform. 
JBoss Fuse may be a better fit if your organization ...
  • ​does not use Java or Java Enterprise Edition 
  • does not utilize the JBoss Enterprise Application Server Platform (EAP). 
  • uses OSGi in the development of other components in your infrastructure 
  • uses the Apache Karaf container for other components in your infrastructure. 
  • Design-time or runtime service governance is not a major factor in your choice of an integration platform. 
See more at:

Monday, September 15, 2014

Advance into an open future

This past Red Hat Summit 2014 I was honored to be able to work on a lab for Fuse Service Works with Keith Babo.  I have moved the lab into a docker container so keep watching for the blog post of the Home Loan Application deployed to Fuse Service Works in a Docker container.   We were lucky to be one of the Top Presenters for Red Hat Summit 2014.  I received my T-Shirt and wanted to reblog the location of the lab and the overview.  We are adding more to it and building some starter kits.   Any feedback is appreciated to improve our labs and make Fuse Service Works full of goodness.  We look forward to having more detailed labs for Red Hat Summit 2015.

Development & governance with Red Hat JBoss Fuse Service Works
Kenneth Peeples — Principal product marketing manager, Middleware, Red Hat
Keith Babo — Principal software engineer, Red Hat
Red Hat JBoss Fuse Service Works is Red Hat’s middleware solution for application integration, messaging, SOA, and service governance requirements. It combines multiple technologies from the middleware portfolio. Camel, CXF and ActiveMQ comprise the core ESB technology, SwitchYard provides the lightweight service development framework, and Overlord provides the design-time and run-time governance.
In this session, we’ll walk you through the Red Hat Fuse Service Works home-loan application. This application processes a home-loan application through the system to arrive at a decision. The application uses multiple technologies, including Camel, business processes, and rules.
You’ll learn how to:
  • Manage application life cycle through design-time governance
  • Capture service activity through run-time governance.
  • Build a SwitchYard application and use Camel, business processes, and rules in the application.

Thursday, September 11, 2014

Evolving your data into a strategic asset with Hortonworks and JBoss

This week we had the Discover Red Hat and Apache Hadoop for the Modern Data Architecture – Part 2 webinar.  I wanted to share the overview along with the demo videos.   The replay of the webinar is here.  The full slide deck is here.  The Hortonworks and Red Hat partner landing page is here.   The source code, supporting files and how to guide are here.  The part 2 webinar contains 2 use cases that utilize the Hortonworks Data Platform and JBoss Data Virtualization.

Use Case 1 combines sentiment data from Hadoop with data from traditional relational sources.

Determine if sentiment data from the first week of the Iron Man 3 movie is a predictor of sales
Cannot utilize social data and sentiment analysis with sales management system
Leverage JBoss Data Virtualization to mashup Sentiment analysis data with ticket and merchandise sales data on MySQL into a single view of the data.

Use Case 2 revolves around geographically distributed hadoop clusters with Data Virtualization securing data by user role.  Use Case 2 combines data from 2 Hortonworks sandboxes.

Secure data according to Role for row level security and Column Masking
Cannot hide region data from region specific users
Leverage JBoss Data Virtualization to provide Row Level Security and Masking of columns

The walk through the demos are below for both Use Cases. There are 4 videos, 2 for each Use Case which cover the setup/configuration and then running the demo.

Use Case 1 Configuration and Running

Use Case 2 Configuration and Running

Friday, September 5, 2014

Docker and JBoss - the perfect combination

Marek Goldman will be leading a vJBUG (Virtual JBoss Users Group) Meetup on Tuesday September 9, 2014. You can watch live and join the discussion in the web chat.  More information and registration is at


Docker is a tool for building portable Linux containers around an application. If you are unfamiliar with Docker, or have heard of it but never used it, then you should definitely come to this session because containers are the new virtualization.

Docker is a revolution in thinking about software distribution. It makes the process of creating images with the whole application stack (OS + application server + application itself) easy and extremely fast. You can share them easily too, and images behave the same way on different machines. Differences between development and production environments are a thing of the past. But that's not everything - Docker helps you run images too by providing an easy to use interface. Sounds like magic, huh?

In this session, right after introduction to Docker, Marek will dive into examples showing how you can leverage this tool to create a deployment environment for your applications. You will see how to cluster JBoss EAP and deploy an application to it. Marek will share some tips and tricks too: for example how to manage logs or customize the configuration of JBoss EAP to be able to deploy your applications.

Wednesday, September 3, 2014

New integration scenarios highlighted in JBoss BPM Suite & JBoss FSW integration demo

Eric Schabell has started us out on a great demo with 2 of our Red Hat JBoss Middleware products.  This demo shows off the integration between JBoss BPM Suite and JBoss FSW. This initial announcement provides an automated installation (repeatable) in minutes where you get JBoss BPM Suite running on an instance of JBoss EAP and a separate instance of JBoss FSW on its very own EAP instance. There are plans to expand this demo project with various integration scenarios or use cases, but for now we start with just a single story around using JBoss FSW governance integration to manage your rules, events, data models, processes, and other BPM artifacts.


We will be expanding this project in the coming days to include a Switchyard services application that will leverage a Fuse camel route which in turn makes a call to a process running on JBoss BPM Suite.

Governance workflow
There will be more expansion such as calling a Switchyard services application from a BPM process and much more so stay tuned. The project can be found on github and has documentation to get you up and running in minutes.

Governance process

The S-RAMP and DTGov tooling comes with a standard process that was designed using the same BPM Suite tools you are using to create your process projects.
Email task notification
It models the process you work through when you run mvn deploy in the provided demo project, which uploads the project artifacts into the S-RAMP repository and automatically starts a process instance for the new artifact.

Installing and running

The following steps will get you up and running in a matter of minutes with this fully automated and repeatable demo:
  1. Add products to installs directory.
  2. Run '' or 'init.bat'.
  3. Copy this code snippet into your ~/.m2/settings.xml (authorization for s-ramp repository):
    <!-- Added for BPM Suite Governance demo -->
Follow the instructions on the screen to start JBoss BPM Suite server and JBoss Fuse Service Works server.
   Login to http://localhost:8180/business-central  (u:erics / p:bpmsuite1!).

   Login to http://localhost:8080/s-ramp-ui         (u:erics / p:jbossfsw1!)

   As a developer you have a modified project pom.xml (found in projects/customer)
   which includes an s-ramp wagon and s-ramp repository locations for transporting any
   artifacts we build with 'mvn deploy'.

        $ mvn deploy -f projects/customer/evaluation/pom.xml

   The customer project now has been deployed in s-ramp repository where you can view
   the artifacts and see that the governance process in the s-ramp was automatically
   started. Claim the approval task in dashboard available in your browser and see the
   rewards artifact deployed in /tmp/dev copied to /tmp/qa upon approval:

        http://localhost:8080/s-ramp-ui            u:erics/p:jbossfsw1!       

   The example of promoting through dev to qa to stage to prod is an example of using
   a local filesystem for this demo.

       $ ls /tmp/dev/


       $ ls /tmp/qa/

Note that the setup puts JBoss FSW product on port 8080 and JBoss BPM Suite on port 8180 (offset 100).

Artifact repository
The FSW S-RAMP and DTGov installation is configured to automatically react to any deployments of the provided customer evaluation project, kicking off an instance of the process to start evaluating and approving or rejecting the artifact build for the next level of your infrastructure. The current demo setup just uses the following file system locations to show progression but you can configure this to make use of existing continuous integration infrastructure in your own enterprise as needed.
  • /tmp/dev
  • /tmp/qa
  • /tmp/stage
  • /tmp/prod
If at each stage you approve the task waiting in the S-RAMP UI, it will copy the artifact to the new /tmp/dev folder, but after approving the waiting task you will find a new copy in /tmp/qa. deployment stage. This video walks you through the installation and BPM artifact governance use case in just under 10 minutes:
We hope you enjoy this new demo showcasing JBoss FSW governance integration with JBoss BPM Suite.