RED HAT1
SAP BRIEFING:
September 24, 2013
Ted Jones, Kenny Peeples & Ray Ploski
RED HAT2
Agenda
● Introductions
● Section 1 - Red Hat JBoss Developer Program
● Section 2 - Red Hat JBoss Fuse 6 Overview
DEMO – Integrating SAP NetWeaver Gateway
with Red Hat JBoss Fuse and Android
● Section 3 - Red Hat JBoss Data Virtualization 6 Overview
DEMO – Integrating SAP NetWeaver Gateway
with Red Hat JBoss Data Virtualization and Android
● Section 4 – Developer References
RED HAT3
Join the Red Hat JBoss Developer Program Today
● Sign up for your account
now at JBoss.org
● Download JBoss
Developer Studio
● Get productive!
RED HAT4
Section 1
Red Hat JBoss
Developer Program
RED HAT5
Dev Program - Benefits
● Access to Enterprise Binaries
● Build your apps on stable and certified codebase
● No need to migrate your applications from Community
● Access to Enterprise Developer Forums
● Collaborate with Red Hat experts and other enterprise
developers.
● Exclusive Enterprise Content
● Quickstarts, tutorials and webinars available only to
Developer Program members.
6 RED HAT
Enables integration everywhere for a real-
time enterprise
JBoss Fuse 6.0
A small-footprint, flexible, open source ESB
New in 6.0:
JBDS + Fuse IDE
JON + Fabric Management Console
Rebranding, repackaging
RED HAT7
Section 2
Red Hat JBoss Fuse 6.0
8 RED HAT
JBoss A-MQ – Value Proposition
Value Proposition:
– Easier to configure, monitor,
manage and maintain: Small IT
footprint
– Multiple deployment options –
centralized, distributed, embedded:
Small IT footprint
– Proven and robust platform: Based
on popular Apache ActiveMQ,
Standards-based reliable
messaging & High-performance
– Multiple connectivity options: Multi-
standards and multi-platform
support
– Real-time and reliable integration:
Supports messaging paradigms:
Pub/Sub, Point-2-Point, Store and
forward
New in 6.0:
AMQP 1.0 support (Tech Preview)
JBoss Developer Studio to include
Fuse IDE
JBoss Operations Network + Fabric
Management Console
Rebranding, repackaging
9 RED HAT
JBoss Fuse 6.0 – Value Proposition
Value Proposition:
– Easier to configure, monitor,
manage and maintain: Small IT
footprint
– Multiple deployment options –
centralized, distributed, embedded:
Small IT footprint
– Faster time to solution: Apache
Camel, excellent integration
development platform and tooling
– Integrate all enterprise assets:
Extensive connectivity options
– Lower total cost of ownership
– Innovative integration platform:
based on popular open source
projects with vibrant community
New in 6.0
– JBoss Developer Studio to include
Fuse IDE
– JBoss Operations Network (JON) +
Fabric Management Console (FMC)
– Rebranding, repackaging
RED HAT10
JBoss Fuse/A-MQ 6.0
● Fuse ESB, MQ Enterprise, rebranded
● AMQP 1.0 Tech Preview
JBoss Fuse/A-MQ 6.1
● AMQP 1.0 full support
● Component updates
● Additional certifications
JBoss Fuse Service Works 6.0
● Core ESB + SwitchYard
● Repository/Governance
● Integrated Tooling
● EAP 6.1
JBoss Fuse Service Works 6.1
● Expanded Governance/BAM
● Towards API management
● EAP 6.2
11 RED HAT
Apache Camel v2.10
● Intergration framework based on Enterprise Integration
Patterns
http://camel.apache.org/enterprise-integration-patterns.html
● Routing and Mediation Rules can be defined in Domain-
Specific Languages (DSL) including Java-based Fluent API,
Spring or Blueprint XML Configuration Files and Scala
DSL
● Provides support for Bean Binding and seamless integration
with frameworks such as Spring, Blueprint and Guice
● Extensive component implementations via URIs
http://camel.apache.org/components.html
RED HAT JBOSS12
What is Camel?
Apache Camel uses URIs to work directly with any kind of
Transport or messaging model such as HTTP, ActiveMQ,
MINA or CXF, as well as pluggable Components and Data
Format options. Apache Camel is a small library with minimal
dependencies for easy embedding in any Java application.
Example below using EIP and components for quick
integration.
RED HAT JBOSS13
Example usage of Enterprise Integration Patterns
14 RED HAT
Apache ActiveMQ v5.8
● Open source messaging and Integration Patterns server
● Full support of EIP via the Apache Camel Library
http://activemq.apache.org/enterprise-integration-patterns.html
● Supports JMS 1.1, J2EE 1.4 and JCA 1.5
● Multiple Language Clients and Protocols Supported
http://activemq.apache.org/cross-language-clients.html
● Future AMQP Support
RED HAT JBOSS15
What is A-MQ?
JBoss A-MQ is based on Apache ActiveMQ is the powerful open
source messaging and Integration Patterns server.
A-MQ supports the MQTT protocol and will automatically map
between JMS/NMS and MQTT clients.
RED HAT JBOSS16
What is MQTT?
MQTT is a machine-to-machine (M2M)/”Internet of Things”
publish/subscribe messaging transport.
It was designed as an extremely lightweight publish/subscribe
messaging transport.
It is useful for connections with remote locations where a small
code footprint is required and/or network bandwidth is at a
premium.
RED HAT JBOSS17
How is MQTT used in A-MQ?
Easy to enable MQTT in A-MQ
• <transportConnectors><transportConnector name="mqtt" uri="mqtt://localhost:1883
"/></transportConnectors>
MQTT uses ActiveMQ Security for Authentication and
Authorization
• JAAS for Authentication
• Authorization policies will be applied when you try to access
(read/write) certain destinations
• Configurable MessageAuthorizationPolicy to allow you to
authorize each message using some content based
authorization policy of your choosing
18 RED HAT
Apache CXF v2.6
● Apache CXF is an open source services framework. CXF
helps you build and develop services using frontend
programming APIs, like JAX-WS and JAX-RS.
● These services can speak a variety of protocols such as
SOAP, XML/HTTP, RESTful HTTP, or CORBA and work
over a variety of transports such as HTTP, JMS or JBI
19 RED HAT
Apache CXF – Standards Support
JSR Support
● JAX-WS - Java API for XML-Based Web Services (JAX-WS) 2.0 - JSR-224
● Web Services Metadata for the Java Platform - JSR-181
● JAX-RS - The Java API for RESTful Web Services - JSR-311
● SAAJ - SOAP with Attachments API for Java (SAAJ) – JSR-67
WS-* and related Specifications Support
● Basic support: WS-I Basic Profile 1.1
● Quality of Service: WS-Reliable Messaging
● Metadata: WS-Policy, WSDL 1.1 - Web Service Definition Language
● Communication Security: WS-Security, WS-SecurityPolicy, WS-SecureConversation, WS-
Trust (partial support)
● Messaging Support: WS-Addressing, SOAP 1.1, SOAP 1.2, Message Transmission
Optimization Mechanism (MTOM)
20 RED HAT
Apache CXF – Transports and Bindings
● Transports: HTTP, Servlet, JMS, In-VM and many others
via the Camel transport for CXF such as SMTP/POP3, TCP
and Jabber
● Protocol Bindings: SOAP, REST/HTTP, pure XML
● Data bindings: JAXB 2.x, Aegis, Apache XMLBeans,
Service Data Objects (SDO), JiBX
● Formats: XML Textual, JSON, FastInfoset
● Extensibility API allows additional bindings for CXF,
enabling additional message format support such as
CORBA/IIOP
21 RED HAT
Apache Karaf v2.3
● 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
22 RED HAT
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
23 RED HAT
JBoss Fuse Fabric v7.2
● Fuse Management Console is accessed through a port on the
server to which the Fuse Management Console server is
deployed.
● The console will provide a view of the fabric to which the
Fuse Management Console server is connected.
● Containers are deployed into the fabric and configured using
profiles.
● There are several different types of containers that can be
deployed. Some are used to manage the fabric while others
host applications
24 RED HAT
Why Fuse Fabric?
● 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.
25 RED HAT
Fabric Key Features
 Support Hybrid deployments – on
premise, on cloud, on both

Endpoints can be relocated

Endpoints can be load balanced

Endpoints can be elastic

Endpoints can be highly available
 Distributed Configuration

Configuration may be accessed
across
multiple domains

Configuration is highly available
 Distributed Management

Easy elastic scaling of services

Monitoring and control of resources
JBoss A-MQ
Camel Endpoints
Fuse IDE Fuse Management Console
JBoss Fuse
26 RED HAT
Fuse Fabric uses Apache Zookeeper
Zookeeper is an Apache Distributed Registry Service
Zookeeper
Registry
Clusters
JBoss
Fuse
JBoss
Fuse
JBoss
Fuse
27 RED HAT
JBoss Fuse Tooling
● Fuse Fabric Perspective
● Fuse route Editor
● Debugging Tools
28 RED HAT
JBoss Fuse or JBoss Fuse Service Works
Capabilities JBoss Fuse JBoss Fuse Service
Works
Messaging (ActiveMQ)
Integration Framework
(Apache Camel, Apache CXF)
Services Framework
(Lightweight service
framework,SOA, SCA)
Service Orchestration and
business rules processing
Service registry and repository
Service Governance
(Design, control and manage)
Activity Monitoring
(View, plan, SLA, Operational)
Management and Monitoring
Container: Apache Karaf
Container: JBoss EAP
RED HAT29
Product What is it Used for Scenarios
Red Hat JBoss
A-MQ
Messaging App2App,
Device2Device,
Device2App
connectivity
Just need messaging;
All end points in
customer control;
Common message
and protocol format
Red Hat JBoss
Fuse
ESB
Messaging
Integration Distributed
environments (retail
branches);
Custom stacks
(investment banking)
Red Hat JBoss
SOA Platform
Service Platform
(SwitchYard)
BPEL
Registry/Repository
ESB
Messaging
EAP
Integration;
Governance;
Application, cloud,
mobile service
development and
deployment (SCA)
HQ/Central Hubs
(State/Local Govt;
Telco; Healthcare;
Retail HQ);
Red Hat JBoss Integration Product Positioning
RED HAT30
Multiple Products solving multiple problems
JBoss A-MQ
JBoss Fuse
(Includes A-MQ)
JBoss Fuse Service Works
(Includes JBoss Fuse)
Additional Capabilities
Additional Capabilities
Small-footprint messaging platform, eliminating batch delivery
“JBoss A-MQ for messaging oriented middleware requirements and use-cases”
Integration/ESB platform for integrations that can extend outside the data center
“JBoss Fuse for integration/ESB requirements and use-cases”
Service design, development and integration platform that enables
responsive and innovative enterprise
“JBoss Fuse Service Works for
integration/ESB+SOA+Orchestration+Governance requirements and use-
cases”
RED HAT31
RED HAT32
Section 3
Red Hat JBoss
Data Virtualization 6.0
RED HAT33
Data Virtualization – Overview
Data Virtualization Process
● Accessing data from disparate systems (databases, files,
services, applications, etc.)
● Integrating and transforming the data, creating canonical
abstraction
● Exposing information
● as a single-source
● through a variety of data access methods to support different tools
and applications
● access is in “real-time” from original sources
● Hide transformation and connectivity details from
information consumers
RED HAT34
Data Virtualization – Benefits
Why Data Virtualization?
● Quickly derive value from your data assets
● Present it to your users in the form they want
through the tools they use.
● Build a flexible, agile information infrastructure
that lets you quickly respond to change
● Complements existing technologies and
approaches (SOA, EAI, ETL)
● Gain control of your information sprawl
Data Virtualization
RED HAT35
Usage pattern: Connect and Compose
● Connect to sources, integrate, federate, transform data
● Create foundational data views
xml
databases
warehouses
spreadsheets
services
<sale/>
<value/>
</ sale >
files
applications
…
Existing sources
and silos of data
Integrated set of
standard data
views
Finance, HR
Inventory,
Logistics
RED HAT36
Red Hat JBoss Data Services Platform
RED HAT37
RED HAT38
Section 4
Developer References
RED HAT39
To learn more
• http://www.jboss.org/products
• http://www.github.com/FuseByExample
• http://camel.apache.org/
• http://camel.apache.org/sap-netweaver.html
• http://cxf.apache.org/
• http://karaf.apache.org/
• http://activemq.apache.org/
• https://github.com/kpeeples/jboss-fuse-bitmoney-demo
• http://java.dzone.com/articles/android-mqtt-activemq
• https://github.com/jsherman1/android-mqtt-demo
• https://github.com/fusesource/mqtt-client
• http://tools.android.com/recent/dealingwithdependenciesinandroidprojects
More information and online resources
RED HAT40
To learn more
• Visit the “Red Hat JBoss Enterprise Middleware for SAP” page on SCN
– http://scn.sap.com/docs/DOC-39134
http://www.redhat.com/products/jbossenterprisemiddleware/data-services/
Download/Install the media tool sets.
• http://sapnetweavergatewayonfedora.fedorapeople.org (OS and VM)
• http://scn.sap.com/docs/DOC-31221 (SAP NetWeaver Gateway)
For further information, contact sap@redhat.com
More information and online resources
RED HAT41
Speaker Contacts
● Ray Ploski, ray@redhat.com
● Kenneth Peeples, kpeeples@redhat.com
● Ted Jones, tejones@redhat.com
RED HAT42
Questions?Questions?
RED HAT43
Wrap Up

Sap webinar-briefing-sep-2013-final

  • 1.
    RED HAT1 SAP BRIEFING: September24, 2013 Ted Jones, Kenny Peeples & Ray Ploski
  • 2.
    RED HAT2 Agenda ● Introductions ●Section 1 - Red Hat JBoss Developer Program ● Section 2 - Red Hat JBoss Fuse 6 Overview DEMO – Integrating SAP NetWeaver Gateway with Red Hat JBoss Fuse and Android ● Section 3 - Red Hat JBoss Data Virtualization 6 Overview DEMO – Integrating SAP NetWeaver Gateway with Red Hat JBoss Data Virtualization and Android ● Section 4 – Developer References
  • 3.
    RED HAT3 Join theRed Hat JBoss Developer Program Today ● Sign up for your account now at JBoss.org ● Download JBoss Developer Studio ● Get productive!
  • 4.
    RED HAT4 Section 1 RedHat JBoss Developer Program
  • 5.
    RED HAT5 Dev Program- Benefits ● Access to Enterprise Binaries ● Build your apps on stable and certified codebase ● No need to migrate your applications from Community ● Access to Enterprise Developer Forums ● Collaborate with Red Hat experts and other enterprise developers. ● Exclusive Enterprise Content ● Quickstarts, tutorials and webinars available only to Developer Program members.
  • 6.
    6 RED HAT Enablesintegration everywhere for a real- time enterprise JBoss Fuse 6.0 A small-footprint, flexible, open source ESB New in 6.0: JBDS + Fuse IDE JON + Fabric Management Console Rebranding, repackaging
  • 7.
    RED HAT7 Section 2 RedHat JBoss Fuse 6.0
  • 8.
    8 RED HAT JBossA-MQ – Value Proposition Value Proposition: – Easier to configure, monitor, manage and maintain: Small IT footprint – Multiple deployment options – centralized, distributed, embedded: Small IT footprint – Proven and robust platform: Based on popular Apache ActiveMQ, Standards-based reliable messaging & High-performance – Multiple connectivity options: Multi- standards and multi-platform support – Real-time and reliable integration: Supports messaging paradigms: Pub/Sub, Point-2-Point, Store and forward New in 6.0: AMQP 1.0 support (Tech Preview) JBoss Developer Studio to include Fuse IDE JBoss Operations Network + Fabric Management Console Rebranding, repackaging
  • 9.
    9 RED HAT JBossFuse 6.0 – Value Proposition Value Proposition: – Easier to configure, monitor, manage and maintain: Small IT footprint – Multiple deployment options – centralized, distributed, embedded: Small IT footprint – Faster time to solution: Apache Camel, excellent integration development platform and tooling – Integrate all enterprise assets: Extensive connectivity options – Lower total cost of ownership – Innovative integration platform: based on popular open source projects with vibrant community New in 6.0 – JBoss Developer Studio to include Fuse IDE – JBoss Operations Network (JON) + Fabric Management Console (FMC) – Rebranding, repackaging
  • 10.
    RED HAT10 JBoss Fuse/A-MQ6.0 ● Fuse ESB, MQ Enterprise, rebranded ● AMQP 1.0 Tech Preview JBoss Fuse/A-MQ 6.1 ● AMQP 1.0 full support ● Component updates ● Additional certifications JBoss Fuse Service Works 6.0 ● Core ESB + SwitchYard ● Repository/Governance ● Integrated Tooling ● EAP 6.1 JBoss Fuse Service Works 6.1 ● Expanded Governance/BAM ● Towards API management ● EAP 6.2
  • 11.
    11 RED HAT ApacheCamel v2.10 ● Intergration framework based on Enterprise Integration Patterns http://camel.apache.org/enterprise-integration-patterns.html ● Routing and Mediation Rules can be defined in Domain- Specific Languages (DSL) including Java-based Fluent API, Spring or Blueprint XML Configuration Files and Scala DSL ● Provides support for Bean Binding and seamless integration with frameworks such as Spring, Blueprint and Guice ● Extensive component implementations via URIs http://camel.apache.org/components.html
  • 12.
    RED HAT JBOSS12 Whatis Camel? Apache Camel uses URIs to work directly with any kind of Transport or messaging model such as HTTP, ActiveMQ, MINA or CXF, as well as pluggable Components and Data Format options. Apache Camel is a small library with minimal dependencies for easy embedding in any Java application. Example below using EIP and components for quick integration.
  • 13.
    RED HAT JBOSS13 Exampleusage of Enterprise Integration Patterns
  • 14.
    14 RED HAT ApacheActiveMQ v5.8 ● Open source messaging and Integration Patterns server ● Full support of EIP via the Apache Camel Library http://activemq.apache.org/enterprise-integration-patterns.html ● Supports JMS 1.1, J2EE 1.4 and JCA 1.5 ● Multiple Language Clients and Protocols Supported http://activemq.apache.org/cross-language-clients.html ● Future AMQP Support
  • 15.
    RED HAT JBOSS15 Whatis A-MQ? JBoss A-MQ is based on Apache ActiveMQ is the powerful open source messaging and Integration Patterns server. A-MQ supports the MQTT protocol and will automatically map between JMS/NMS and MQTT clients.
  • 16.
    RED HAT JBOSS16 Whatis MQTT? MQTT is a machine-to-machine (M2M)/”Internet of Things” publish/subscribe messaging transport. It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.
  • 17.
    RED HAT JBOSS17 Howis MQTT used in A-MQ? Easy to enable MQTT in A-MQ • <transportConnectors><transportConnector name="mqtt" uri="mqtt://localhost:1883 "/></transportConnectors> MQTT uses ActiveMQ Security for Authentication and Authorization • JAAS for Authentication • Authorization policies will be applied when you try to access (read/write) certain destinations • Configurable MessageAuthorizationPolicy to allow you to authorize each message using some content based authorization policy of your choosing
  • 18.
    18 RED HAT ApacheCXF v2.6 ● Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS and JAX-RS. ● These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI
  • 19.
    19 RED HAT ApacheCXF – Standards Support JSR Support ● JAX-WS - Java API for XML-Based Web Services (JAX-WS) 2.0 - JSR-224 ● Web Services Metadata for the Java Platform - JSR-181 ● JAX-RS - The Java API for RESTful Web Services - JSR-311 ● SAAJ - SOAP with Attachments API for Java (SAAJ) – JSR-67 WS-* and related Specifications Support ● Basic support: WS-I Basic Profile 1.1 ● Quality of Service: WS-Reliable Messaging ● Metadata: WS-Policy, WSDL 1.1 - Web Service Definition Language ● Communication Security: WS-Security, WS-SecurityPolicy, WS-SecureConversation, WS- Trust (partial support) ● Messaging Support: WS-Addressing, SOAP 1.1, SOAP 1.2, Message Transmission Optimization Mechanism (MTOM)
  • 20.
    20 RED HAT ApacheCXF – Transports and Bindings ● Transports: HTTP, Servlet, JMS, In-VM and many others via the Camel transport for CXF such as SMTP/POP3, TCP and Jabber ● Protocol Bindings: SOAP, REST/HTTP, pure XML ● Data bindings: JAXB 2.x, Aegis, Apache XMLBeans, Service Data Objects (SDO), JiBX ● Formats: XML Textual, JSON, FastInfoset ● Extensibility API allows additional bindings for CXF, enabling additional message format support such as CORBA/IIOP
  • 21.
    21 RED HAT ApacheKaraf v2.3 ● 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
  • 22.
    22 RED HAT ApacheKaraf Features Include ● Hot deployment ● Dynamic configuration ● Logging System ● Provisioning ● Native OS integration ● Extensible Shell console ● Remote access ● Security framework based on JAAS ● Instance Management
  • 23.
    23 RED HAT JBossFuse Fabric v7.2 ● Fuse Management Console is accessed through a port on the server to which the Fuse Management Console server is deployed. ● The console will provide a view of the fabric to which the Fuse Management Console server is connected. ● Containers are deployed into the fabric and configured using profiles. ● There are several different types of containers that can be deployed. Some are used to manage the fabric while others host applications
  • 24.
    24 RED HAT WhyFuse Fabric? ● 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.
  • 25.
    25 RED HAT FabricKey Features  Support Hybrid deployments – on premise, on cloud, on both  Endpoints can be relocated  Endpoints can be load balanced  Endpoints can be elastic  Endpoints can be highly available  Distributed Configuration  Configuration may be accessed across multiple domains  Configuration is highly available  Distributed Management  Easy elastic scaling of services  Monitoring and control of resources JBoss A-MQ Camel Endpoints Fuse IDE Fuse Management Console JBoss Fuse
  • 26.
    26 RED HAT FuseFabric uses Apache Zookeeper Zookeeper is an Apache Distributed Registry Service Zookeeper Registry Clusters JBoss Fuse JBoss Fuse JBoss Fuse
  • 27.
    27 RED HAT JBossFuse Tooling ● Fuse Fabric Perspective ● Fuse route Editor ● Debugging Tools
  • 28.
    28 RED HAT JBossFuse or JBoss Fuse Service Works Capabilities JBoss Fuse JBoss Fuse Service Works Messaging (ActiveMQ) Integration Framework (Apache Camel, Apache CXF) Services Framework (Lightweight service framework,SOA, SCA) Service Orchestration and business rules processing Service registry and repository Service Governance (Design, control and manage) Activity Monitoring (View, plan, SLA, Operational) Management and Monitoring Container: Apache Karaf Container: JBoss EAP
  • 29.
    RED HAT29 Product Whatis it Used for Scenarios Red Hat JBoss A-MQ Messaging App2App, Device2Device, Device2App connectivity Just need messaging; All end points in customer control; Common message and protocol format Red Hat JBoss Fuse ESB Messaging Integration Distributed environments (retail branches); Custom stacks (investment banking) Red Hat JBoss SOA Platform Service Platform (SwitchYard) BPEL Registry/Repository ESB Messaging EAP Integration; Governance; Application, cloud, mobile service development and deployment (SCA) HQ/Central Hubs (State/Local Govt; Telco; Healthcare; Retail HQ); Red Hat JBoss Integration Product Positioning
  • 30.
    RED HAT30 Multiple Productssolving multiple problems JBoss A-MQ JBoss Fuse (Includes A-MQ) JBoss Fuse Service Works (Includes JBoss Fuse) Additional Capabilities Additional Capabilities Small-footprint messaging platform, eliminating batch delivery “JBoss A-MQ for messaging oriented middleware requirements and use-cases” Integration/ESB platform for integrations that can extend outside the data center “JBoss Fuse for integration/ESB requirements and use-cases” Service design, development and integration platform that enables responsive and innovative enterprise “JBoss Fuse Service Works for integration/ESB+SOA+Orchestration+Governance requirements and use- cases”
  • 31.
  • 32.
    RED HAT32 Section 3 RedHat JBoss Data Virtualization 6.0
  • 33.
    RED HAT33 Data Virtualization– Overview Data Virtualization Process ● Accessing data from disparate systems (databases, files, services, applications, etc.) ● Integrating and transforming the data, creating canonical abstraction ● Exposing information ● as a single-source ● through a variety of data access methods to support different tools and applications ● access is in “real-time” from original sources ● Hide transformation and connectivity details from information consumers
  • 34.
    RED HAT34 Data Virtualization– Benefits Why Data Virtualization? ● Quickly derive value from your data assets ● Present it to your users in the form they want through the tools they use. ● Build a flexible, agile information infrastructure that lets you quickly respond to change ● Complements existing technologies and approaches (SOA, EAI, ETL) ● Gain control of your information sprawl Data Virtualization
  • 35.
    RED HAT35 Usage pattern:Connect and Compose ● Connect to sources, integrate, federate, transform data ● Create foundational data views xml databases warehouses spreadsheets services <sale/> <value/> </ sale > files applications … Existing sources and silos of data Integrated set of standard data views Finance, HR Inventory, Logistics
  • 36.
    RED HAT36 Red HatJBoss Data Services Platform
  • 37.
  • 38.
  • 39.
    RED HAT39 To learnmore • http://www.jboss.org/products • http://www.github.com/FuseByExample • http://camel.apache.org/ • http://camel.apache.org/sap-netweaver.html • http://cxf.apache.org/ • http://karaf.apache.org/ • http://activemq.apache.org/ • https://github.com/kpeeples/jboss-fuse-bitmoney-demo • http://java.dzone.com/articles/android-mqtt-activemq • https://github.com/jsherman1/android-mqtt-demo • https://github.com/fusesource/mqtt-client • http://tools.android.com/recent/dealingwithdependenciesinandroidprojects More information and online resources
  • 40.
    RED HAT40 To learnmore • Visit the “Red Hat JBoss Enterprise Middleware for SAP” page on SCN – http://scn.sap.com/docs/DOC-39134 http://www.redhat.com/products/jbossenterprisemiddleware/data-services/ Download/Install the media tool sets. • http://sapnetweavergatewayonfedora.fedorapeople.org (OS and VM) • http://scn.sap.com/docs/DOC-31221 (SAP NetWeaver Gateway) For further information, contact sap@redhat.com More information and online resources
  • 41.
    RED HAT41 Speaker Contacts ●Ray Ploski, ray@redhat.com ● Kenneth Peeples, kpeeples@redhat.com ● Ted Jones, tejones@redhat.com
  • 42.
  • 43.

Editor's Notes

  • #7 JBoss Fuse, a small-footprint, flexible, open source ESB Supports integration everywhere for a real-time enterprise. The lack of license fees combined with the ability to deploy Fuse ESB Enterprise in any configuration advances intelligent integration to all facets of the business. Small-footprint implies smaller IT footprint, easier to manage and maintain and multiple deployment options (distributed, embedded). Small footprint does not imply any negative performance implications like lower performance. JBoss Fuse is a proven and high-performance messaging platform.
  • #9 JBoss A-MQ, is a small-footprint, high-performance, open source messaging platform Supports real-time integration everywhere The lack of license fees combined with high-performance, reliable messaging that can be used with any development environment provides a solution that supports integration everywhere. Small-footprint implies smaller IT footprint, easier to manage and maintain and multiple deployment options (distributed, embedded). Small footprint does not imply any negative performance implications like lower performance.JBoss A-MQ is a proven and high-performance messaging platform. Value Proposition – Top 3 Take Aways Enterprise-class open source – the best of both worlds – technical innovation, flexibility and cost-savings of open source, and the safety and security of working with a trusted vendor Integrate Everything – the small footprint, flexible architecture and multiple-standards support real-time integration with outlets, mobile devices, and partners High-performance and scalable – High-performance and reliable messaging provides a robust messaging platform and flexible architecture enables scalable deployments
  • #10 JBoss Fuse, a small-footprint, flexible, open source ESB Supports integration everywhere for a real-time enterprise. The lack of license fees combined with the ability to deploy Fuse ESB Enterprise in any configuration advances intelligent integration to all facets of the business. Small-footprint implies smaller IT footprint, easier to manage and maintain and multiple deployment options (distributed, embedded). Small footprint does not imply any negative performance implications like lower performance. JBoss Fuse is a proven and high-performance messaging platform. Value Proposition: Top 3 Take Aways Enterprise-class open source – the best of both worlds – technical innovation, flexibility and cost-savings of open source, and the safety and security of working with a trusted vendor Integrate Everything – the smaller footprint and flexible architecture makes it possible to extend the integration solution to outlets, mobile devices, and partners Faster time to solution – common integration pattern framework, extensive connectivity and excellent tooling provide faster time to solution