Fuse overview

RED HAT JBOSS FUSE

Rob DaviesTechnical Director, FuseSeptember 2014

RED HAT | Fuse Rocks!2

Innovate faster, in a smarter wayA family of a lightweight, enterprise-grade products that are ideal for open hybrid cloud environments

Red Hat JBoss A-MQRed Hat JBoss FuseRed Hat JBoss Fuse Service WorksRed Hat JBoss Data Virtualization


History of Fuse open source Development

2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014

ActiveMQMay 2004

CodeHaus

ServiceMixMay 2005

Camel Mar2007

IONA April 2007

Karaf

ProgressOctober 2008

FuseSource created

October 2010

ASF

LogicBlaze Formed May 2005

CXF Aug 2006 Fabric

Feb 2011

GitHub

Red HatacquireSept 2012

Dec 2013Mar 2013


We work on many open source projects


Leader in Forrester Wave: Hybrid Integration 2014

Red Hat leader in 3 categories:Deep IntegrationCloud IntegrationInternet of things (IOT)


JBoss Fuse Integration Product lineAdditive capabilities to fit different use cases

A-MQ Fuse Fuse Service Works

Messaging Fuse ESBMessaging Fuse ESB

Service DevelopmentService OrchestrationService Governance

Messaging Platform

Integrate applications, devices by notification or exchange of data using multiple protocols in any runtime

Integration Platform

Mediate, transform, route and connect between loosely coupled components, services and applications using enterprise integration patterns

Business Services Platform

Develop and choreograph business services, manage lifecycle, define and enforce service policy and monitor service activity

Business Challenges


Challenge facing enterprises: Enlightened integration beyond the data center

SaaS applications

Cloud applicationsPublic and Private

Distributors

Partners

Data center

Need solution that is● Flexible,● Cloud-friendly,● Inexpensive, and● Has a small footprint


What do some organizations do to address the Integration challenge?

● Do nothing– Manual touch points (expensive solution)– Error prone solutions– Bad customer experience

● Direct links between applications– Inflexible solutions– Difficult to change– Spaghetti code: difficult to maintain across organization– No control and no ability to reuse

● Integration stacks from proprietary vendors– Expensive – Heavyweight and inflexible solutions– Unable to provide better products or services (Business unhappy

that IT is not delivering appropriate products/services)


Challenges of Integrating the Extended Enterprise

●Integrating all enterprise assetsmany business assets are at the edges (outside the data center)●Avoiding centralizing all serviceshub-and-spoke architectures are limiting●Getting deployed quicklylengthy development cycles reduce ROI●Controlling run-away costs from initial outlay to on-going maintenance ●Avoiding creating yet-another legacy systemwant new technology, need to stay agile●Creating infrastructure that can scale up...and downelasticity should be easy


How do you integrate everything...

+HQ + integration stack

...when the enterprise extends far beyond the data center?

partners

devices

cloud / SaaS apps

distributors


Traditional integration stack is too expensive, too difficult to manage and maintain...


...and many make do with batch delivery and hub-and-spoke architecture

point to point

batch

batch

batchpoint to point

point to pointpoint to pointpoint to point

cloud / SaaS apps

distributors

partners

devices


partners

devices

cloud / SaaS apps

distributors

With JBoss Fuse, You Can Integrate Everything...


MQ

MQ

MQ

MQ

MQ

MQ

ESB

ESB

Integration beyond the Data Center – deploy ESBs and brokers at distributers, outlets and devices

No longer limited to hub-and spoke – deploy integration intelligence at any location around the globe

Eliminate batch delivery –brokers can easily and inexpensively be deployed everywhere


What JBoss Fuse Brings to Red Hat’s Customers:

Integration that extends to the edges of enterprise

Easy to deploy – sophisticated tooling, connectors,small footprint makes it easy to deploy with less hardware and limited IT staffing

Many deployment options – deploy on-premise or in the cloud in any configuration, and change on the fly with automated provisioning

Standards-based – commitment to industry standards ensures that JBoss infrastructure is easy to modify and maintain

Centralized management – innovative tooling makes it ease to configure, deploy, manage and maintain integration infrastructure

Open source – less expensive and pay as you go to reduce over all costs in all stages of the project

Technology Overview


Why JBoss Fuse?

Connect islands of information

Reuse of business data, Real-time information exchange

Enhance business information Automate business processes

Decouple applications and services

Standard way for enterprise applications or services to interact

New and improved products/servicesBetter business decisions

Unified customer experience

Better business decisionsNew and improved products/services

Reduce overall IT costs

New and improved products/servicesReduce business errors

More agile/flexible enterpriseReduce overall IT costs

Improved business executionReduce business errorsReduce overall IT costs

Business Benefits


JBoss Fuse: An open source enterprise integration platform and service bus

Enables integration everywhere for a real-time enterprise

New in 6.1- Ubiquitous connectivity 150+ connectors (SalesForce, SAP, Social integration, cloud integration)- Unified management console which leverages Fuse Fabric- Improved High Availability (shared-nothing configuration, LevelDB: Developer preview)- Integration in the Cloud (OpenShift Cartridge: Developer preview )


JBoss Fuse – Open Source Heritage

JBoss Fuse Fabric8

Apache CXF

Apache Camel

Apache ServiceMix

Apache ActiveMQ

hawtio

Apache Karaf

JBoss Fuse Includes:Apache Camel


Enterprise Integration Patterns

A Book by Gregor Hohpe and Bobby Woolf Patterns and Recipes for common integration problems Message Centric Used as the basis for all the major integration products Should be the the first thing to reference when starting an

integration project http://www.eaipatterns.com/

http://www.eaipatterns.com/


What is Apache Camel?

Implementation framework for most commonly used Enterprise Integration Patterns (EIP)

Speeds time to solution and provides multiple connectivity options

Popular and vibrant community Requirement for a really simple way to do integration

• Started as a Sub-project of ActiveMQ in March 2007• 36 committers (15 work for Red Hat)• 80-100k artifact downloads a month• 120k website views a month• 1000 user mailing list posts per month• 200+ connectors and growing• Most widely used integration framework


Apache Camel

Camel provides an embedded DSL (in Java & Spring) for implementing enterprise integration patternsThe DSL uses URIs to define endpoints which are combined by form

integration flows

from("activemq:topic:Quotes”) .filter().xpath("/quote/product = ‘widget’”) .to("mqseries:WidgetQuotes") .filter().xpath("/quote/product = ‘gadget’”) .to("mqseries:GadgetQuotes");


Some Integration Patterns

JBoss Fuse Includes:Apache CXF


Apache CXF

• Entered Apache Incubator in August 2006

• Leading open source web services stack for Java

• Best feature support

• Most flexible approach

• Configure using annotations• Manipulate configuration directly in code• Configure using Spring

• JAX-WS and JAX-RS Certified

• DOSGi reference implementation of OSGi Remote Services Specification


Apache CXF: Rest

• Representational State Transfer – based on Roy Fielding’s doctoral thesis on HTTP

• HTTP verbs provide actions on resources:• GET to retrieve current state of a resource• PUT to replace the current state of a resource• POST to create a new resource• DELETE to remove a resource

• Powerful and flexible structure for resource oriented-systems• GET – guaranteed safe, responses can be cached• PUT and DELETE – are idempotent


Apache CXF: JAX-WS – Standard SOAP Services

• Uses source code annotations• Defines interface representing service• Attach actual implementation to interface• Supply pre-generated WSDL for the service

• Reference implementation uses JAXB data binding• can generate code from existing service definition• CXF provides wsdl2Java tool• CXF provides wsdl2corba tool

JBoss Fuse Includes:Apache ActiveMQ


What is Apache ActiveMQ?

• Top level Apache Software Foundation project

• Wildly popular, high performance, reliable message broker

• Clustering and Fault Tolerance

• Supports publish/subscribe, point to point, message groups, out of band messaging and streaming, distributed transactions,

• Myriad of connectivity options

• Native Java, C/C++, and .NET

• STOMP protocol enables Ruby, JS, Perl, Python, PHP, ActionScript, ...

• Embedded and standalone deployment options


Apache ActiveMQ – Enterprise Features

FailoverHigh AvailabilityClusteringScaling

Head Office

FuseMQClusters

JBoss Fuse Includes:Apache Karaf


Apache Karaf

● Apache Karaf is a small OSGi based runtime which provides a lightweight container onto which various components and applications can be deployed

● Supports the latest OSGi 4.3 containers: Apache Felix Framework 4.0 and Eclipse Equinox 3.8


Apache Karaf

Features Include ● Hot deployment● Dynamic configuration● Logging System● Provisioning● Native OS integration● Extensible Shell console● Remote access● Security framework based on JAAS● Instance Management


Apache Karaf console

karaf@root> osgi:list


Working with bundleskaraf@root> osgi:list | grep camel


Deploy with features

Features group bundles into a logical unit of deployment

Installing feature "Foo" installs bundles A, B, C and D


Karaf Camel Commands

Start/stop routes and contexts deployed in ESB

View route XML and stats

Many commands available

JBoss Fuse Includes:Fabric8


http://fabric8.io

• Simplifies deployments

• Provides management tools for centralized

configuration

• Visualize your middleware with HawtIO

• Polycontainer

• Blurs the line of PaaS


Why Fabric8?

● Configuration of JBoss Fuse and A-MQ may be complex.

● Enterprise deployments without fabric require a lot of manual and often repetitive configuration that is easy to get wrong.

● Enterprises may need to deploy across different environment, on-premise, on a private cloud, on a public cloud and a combination of these.

● Enterprise deployments need location transparency, and support of failover of endpoints.


http://fabric8.io

• Provides cluster capabilities, coordination Service discovery, load balancing, failover Deploy to cloud (IaaS, PaaS)Supported as JBoss Fuse (managed)

• fabric8 1.0 is in Fuse 6.1


Architecture


Core Concepts

• Fabric registry • Holds all configuration data • Runtime registry for looking up distributed services

• Profile • Describes the container set up • Features, Bundles, ConfigAdmin PIDs, system properties • Hierarchical structure • Container versioning

• Agent • Runs on each container • Communicates with registry to make sure container provisioned

correctly


How’s Fabric8 different from Puppet/Chef ?

• Middleware centric • Container agnostic • Deep knowledge about the running processes • Consistent configuration • Visualizations • Versioning built in, upgrades, rollbacks, selective

upgrade, etc • Use puppet/chef to provision your machines, use

fabric8 to provision and manage your middleware/ apps

JBoss Fuse Includes:hawtio


http://hawt.io


http://hawt.io

JBoss Fuse Includes:Lots of other stuff …


JBoss Fuse Tooling

● Fuse Fabric Perspective● Fuse route Editor● Debugging Tools

Red Hat JBoss Fuse


JBoss Fuse An open source enterprise service bus

Enables integration everywhere for a real-time enterprise


Why JBoss Fuse? - Integration everywhere

Reduces the pain of integrating disparate applications, services and devices

Faster time to solutionBased on commonly used enterprise integration pattern based framework (Apache Camel)

Integrate all enterprise assets Extensive connectivity options

Cloud-readyFoundation to run integration capability in the cloud

Easier to configure, monitor, manage and maintain Lightweight, smaller IT footprint

Multiple deployment optionsCentralized, distributed, embedded

Lower total cost of ownership Easier to get started, easier to consume pricing


What is included in a Managed Subscription?Support for the features provided by Fuse Fabric:

Provisioning – the ability to provision new brokers on local or remote hardware using fabric agents.

Configuration Management – centrally manage the configuration of any number of brokers, apply a broker “profile” to newly created brokers for consistency, and store broker profiles centrally in git.

Fabric patching mechanism – distribute patches uniformly amongst your brokers using fabric

Unified Management console (Hawt.io console) to manage fabric features

The A-MQ Fabric Gateway (currently tech-preview)

JBoss ON for monitoring and alerting


Unified Management ConsoleJBoss Fuse or JBoss A-MQ instances can be joined into a managed fabric.

Once joined to a managed fabric the management console is able to manage all members of the fabric.


Unified Management ConsoleFuse Fabric and the management console simplifies the creation and management of master/slave broker groups, networks of brokers, or individual brokers.


Unified Management ConsoleCamel routes, REST endpoints and SOAP endpoints running of Fuse instances are visible and manageable in the management console.


Use JBoss Fuse Today

● No need to rip and replaceJBoss Fuse works with existing infrastructure

● Get up and running fastApache Camel implements EIPs with minimal code

● Reduce the cost of future expansionFree yourself from vendor lock-in

● Extend integration to all facets of your businessRemove the limitations of your existing infrastructure

● Deploy easily on-premise or in the CloudSophisticated tooling brings about rapid ROI

Customer Success:Sabre Holdings


Travel: Customer Success with JBoss Fuse

● National US travel gateway – Sabre Holdings● Was using inflexible, expensive-to-maintain

proprietary infrastructure based on a TPF mainframe installed in the 60s

● Predicted rapid growth and need to add customer services to stay competitive, and the aging infrastructure was a viability

Challenges:● Large: managing 32,000 transactions a second

(that's over 1.4B a day), and growing● Mission-critical: lost transaction = failed travel

itinerary


Travel: Customer Success with JBoss Fuse

Requirements:●Need to quickly connect Suppliers

●Need to isolate mainframe application from consumers (suppliers, internal applications)

●Need to distribute integration solution across multiple locations

Solution:●JBoss Fuse (Fuse ESB Enterprise) + Consulting

Benefits:●Successful supplier migration●No system failures●Fast partner content deployment●Extremely scalable, enterprise-class QOS●Enterprise-class support●Significant cost-savings


More Customer Successes with JBoss Fuse

Customer Success:Federal Aviation Authority


NextGen

Next Generation Air Transport System (NextGen) Consists of five elements:Automatic dependent surveillance-broadcastSystem Wide Information ManagementNext Generation Data CommunicationsNext Generation Network Enabled WeatherNAS voice switch


SWIM Project Overview

SWIM will:• Implement a Service-Oriented Architecture (SOA) in the

National Airspace System (NAS)• Allow the FAA to create new system interfaces more

quickly and cost effectively than is possible today• Facilitate the data-sharing that is required for NextGen


SWIM System

NextGen Applications

FTI IP Backbone

En RouteControllers

TerminalControllers

Non-FAA Users(e.g., Airlines, DoD

DHS, etc.)FAA

Command Center

SWIM Enterprise Infrastructure


FAA Selects Fuse for SWIM

FAA identified the need to introduce Service-Oriented Architecture

FAA issued a request or proposal (RFP) to multiple vendors

FuseSource offered multiple technical advantages

FAA offered some major challengesMoving from point-2-point to SOAScalabilityReliability

Fuse was selected – on openness, standards, ROI and TCO


Why Fuse?

Innovative Technology – enabled moving away from a fixed network connection custom point-to-point data interfaces

Reduce Cost – from using an open source core and subscription model

Enterprise QoS – from decades of experience building mission-critical systems and enterprise security and administration components

Incremental Adoption – enabling migrating from an existing system gradually and safely

Reliability – proven robust performance and responsive and knowledgeable professional services organization


Learn More About SWIM visit:www.swim.gov

www.swim.gov provides: • Program overview• News announcements• Q&A• Key documentation

• Newsletters • Briefings• Compliance documents• and more….

http://www.swim.gov/


QuestionsQuestionsand and DiscussionDiscussion

Documents

Fuse overview