Introduction to Enterprise Service Bus - ITCourseware › docs › 1-09-00007-000-03-03-09 ›...

SOA: Enterprise Architecture Introduction to Enterprise Service Bus

For information on this course or other many seminar offerings, please contact OnsiteSeminar LLC Direct: (817) 572-9690 email: [email protected]

Introduction to Enterprise Service Bus

© Copyright 2008, OnsiteSeminar LLC All rights reserved, no unauthorized duplication

http://www.onsiteseminar.com

i

TRAIN. LEARN. SUCCEED.



© Copyright 2008 by OnsiteSeminar LLC. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed in any form or by any means including; electronic, mechanical, optical, manual or otherwise without the expressed written consent of this firm. This course, Introduction to Enterprise Service Bus, was developed by the staff of OnsiteSeminar LLC for use in technical seminars. It has been licensed expressly for use by our clients for internal training only.

© Copyright 2008, OnsiteSeminar LLC

All rights reserved, no unauthorized duplication

IMPORTANT NOTICE The sole purpose of this student manual is to serve as a supplement to an instructor-based technical presentation. The combination of information contained in this manual with the detailed insights of the instructor leads to the most positive educational experience for all students. It is not intended to be used solely as a stand alone reference manual. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where these designations appear in this seminar, and OnsiteSeminar LLC is aware of a trademark claim, the designations have been printed in initial capital letters or all capital letters. OnsiteSeminar LLC has taken care in the development of this seminar, but make no expressed or implied warranty of any kind or assume any responsibility for errors or omissions. Java®, Java Development Kit®, J2ME®, J2SE® and J2EE® are a registered trademarks of Sun Microsystems Inc. Rational Application Developer®, WebSphere Application Server®, WebSphere Studio®, WebSphere Studio Application Developer®, MQSeries®, WebSphereMQ®, WebSphere Site Developer®, VisualAge®, VisualAge for Java®, Visual Composition Editor®, VisualAge Debugger® and DB2 are registered trademarks of IBM Corporation. Microsoft® , Microsoft .NET®, MS-DOS®, Windows NT, Windows 2000, Windows 98, Windows ME and SQLServer® are registered trademarks of Microsoft Corporation Oracle, JDeveloper, Oracle BPM Suite, Oracle SOA Suite are registered trademarks of Oracle Corporation.


ii


For information on this course or other many seminar offerings, please contact OnsiteSeminar LLC Direct: (817) 572-9690 email: [email protected] http://www.onsiteseminar.com

iii

Introduction to Enterprise Service Bus Audience Designed for programmers, managers, project leaders, enterprise architects and other

technical individuals that need to understand the modeling of business workflows.

Duration 1 Day

Course Abstract

This course will provide each participant with an introduction to the capabilities, features and abilities of Oracle Enterprise Service Bus for managing and deploying processes. ESB functions and capabilities, Service Component Architecture, communication methods, define the role of SCA components, discuss ESB communication patterns, depict use of business rules, human tasks, state machines and process models, ESB and Message Broker integration and a comparison between the ESB and the Message Broker. All aspects of this class will illustrate the architecture and design of an efficient and effective SOA environment.

Objectives Upon conclusion, each participant will have acquired these skills:

• Illustrate the abilities of the Enterprise Service Bus • Depict architecture of an ESB • Denote the evolution of an ESB • Understand the embedded abilities of ESB components • Illustrate the integration of BAM activities to and ESB • Demonstrate the communication patterns for the ESB • Define the role of SCA components and modules • Illustrate the major components of the ESB • Depict the integration between ESB and Message Broker component • Compare ESB to Message Broker • Discuss mediation processes • Depict the integration of business rules, human tasks, state machines and

business processes • Illustrate the Service Component Architecture implementation • Define the role of business objects and Service Data Objects (SDO)

Class Format Lecture/Lab

Prerequisites Each student should have an understanding of application development and basic design methodologies.



iv

Course Objectives

• Illustrate the abilities of the Enterprise Service Bus

• Depict architecture of an ESB

• Denote the evolution of an ESB

• Understand the embedded abilities of ESB components

• Illustrate the integration of BAM activities to and ESB

• Demonstrate the communication patterns for the ESB

• Illustrate the major components of the ESB

• Depict the integration between ESB and Message Broker component

• Compare ESB to Message Broker

• Discuss mediation processes

• Depict the integration of business rules, human tasks, state machines and business processes

• Define the role of business objects and Service Data Objects (SDO)



Table of Contents


v

I.I. Enterprise Service Bus Enterprise Service Bus

A. Overview Basic SOA Components …. 1-4 Hot Pluggable Components …..1-5 ESB Definition …..1-6 What is an ESB …..1-7 ESB Moves Data …..1-8 Evolution of the Bus …..1-9 ESB Core Features …..1-11 ESB Value Added …..1-12 Primary ESB Patterns …..1-13 ESB Topology …..1-14 Ranking the ESBs …..1-15 ESB Vendors …..1-16

B. BAM Overview Who Needs BAM …. 1-18 Business Activity Monitoring …..1-19 Window of Opportunity …..1-20 BAM/User Experience …..1-21

II.II. ESB Components and Capabilities ESB Components and Capabilities

A. Overview Enterprise Service Bus …. 2-4 What is an ESB? …. 2-5 Basic ESB Pattern …. 2-6 Elements of Basic ESB Pattern …. 2-7 ESB Architecture …. 2-8 Using ESB Functionality …. 2-9 Enterprise Service Bus …. 2-10 Added Value to Application Server …. 2-11 Multiple Interaction Patterns …. 2-12 ESB Communication …. 2-13 ESB Capabilities …. 2-14 ESB Components …..2-17 ESB Product Relationships …. 2-18 Major ESB Components …. 2-19 Service Component Mediations …..2-20 ESB and Message Broker …..2-21 Message Broker as ESB …..2-22



B. ESB Patterns ESB Patterns …. 2-24

Interaction Patterns …. 2-25


vi

III.III. Development with ESB Development with ESB

A. ESB Components ESB Suite Components …. 3-4 ESB Integration Features …..3-5 ESB Connectivity …..3-6 Document Transformation …..3-8 Content & Header=Based Routing …..3-9 Creating, Configuring and Managing …..3-11 Oracle ESB Control …..3-14 Sun ESB Control …..3-15 WebSphere ESB Control …..3-16 Basic ESB Architecture …..3-17 Sample ESB Scenario …..3-18

B. Developer IDE Developer IDE …..3-21 Introduction to Oracle Developer …..3-22 IDE Application Components …..3-23 Design Tab and Component Palette …..3-24 Service Definitions and Routing Rules …..3-25

IV.IV. ESB and Message Broker ESB and Message Broker

A. Overview What is an ESB? …. 4-4

SOA with an ESB …..4-5 Functions of an ESB …..4-6 Different Kinds of ESB …..4-7

B. Building an Advanced ESB with MQ and MB The Advanced ESB …. 4-9 Building SOA Enabled Applications …..4-10 Adding Message Broker …..4-11 ESB Function: Protocol Support …..4-12 Protocols – Input and Output Nodes …..4-13 Protocol Support …..4-14 ESB Function – Routing …..4-15 Message Broker Routing Nodes …..4-16 Building a Routing Flow …..4-17 Routing Concepts …..4-18



vii

ESB Function – Transformation …..4-19 Transformation – Graphical Mapping …..4-20 Transformation – ESQL and XSLT …..4-21 Transformation …..4-22 ESB Function – Event Handling …..4-23 Message Broker Event Nodes …..4-24 Complex Event Processing …..4-25 Complex Event Processing Nodes …..4-26 Security Considerations for an ESB …..4-27 ESB Performance Considerations …..4-28

C. MQ, MB and SOA Lifecycle SOA Lifecycle and ESB …. 4-30 SOA Lifecycle – Model and Compose …..4-31 SOA Lifecycle Model …..4-32 SOA Lifecycle – Compose …..4-33 SOA Loose Coupling …..4-34 SOA Lifecycle – Deploy …..4-35 SOA Lifecycle – Monitor …..4-36 SOA Lifecycle – Monitor ESB …..4-37 Monitoring – The Wider Picture …..4-38 Managing and ESB …..4-39 Manage Service Relationships …..4-40

Introduction to Enterprise Service Bus Section I: Enterprise Service Bus

© Copyright 2008, OnsiteSeminar LLC Introduction to Enterprise Service Bus All rights reserved, no unauthorized duplication Unit 1. Enterprise Service Bus 1-1 Revision: December 15, 2007

Section I: Enterprise Service Bus



Section I. Enterprise Service Bus Unit Description

In this unit, the student will be introduced to the capabilities, features and abilities of an Enterprise Service Bus for managing and deploying processes. ESB functions and capabilities, Service Component Architecture, communication methods, ESB and Message Broker integration and a comparison between the ESB and the Message Broker. The instructor-led lecture is supplemented with a series of hands-on exercises to reinforce all of the ESB concepts discussed in this section.

Unit Objectives

After successfully completing this section, you should be able to:

Illustrate the abilities of the an Enterprise Service Bus Depict architecture of the ESB Denote the evolution of an ESB Understand the embedded abilities of ESB components Illustrate the integration of BAM activities




Overview



Basic SOA Components

______________________________________________________________________ Student Notes:



Hot Pluggable Components

______________________________________________________________________ Student Notes:

• Eclipse IDE-based toolsets provide a comprehensive, easy to use design time graphical interface for building end-to-end message flows and registering ESB service metadata. It also includes a WSDL editor, integrated XSLT mapper, XSD schema editor for standard J2EE application development.



ESB Definition

______________________________________________________________________ Student Notes:

• An ESB generally provides an abstraction layer on top of an implementation of an enterprise messaging system, which allows integration architects to exploit the value of messaging without writing code. Contrary to the more classical enterprise application integration (EAI) approach of a monolithic stack in a hub and spoke architecture, the foundation of an enterprise service bus is built of base functions broken up into their constituent parts, with distributed deployment where needed, working in harmony as necessary.

• An ESB does not implement a service-oriented architecture (SOA) but provides the features with

which one may be implemented. Although it is a common belief, an ESB is not necessarily web-services based. An ESB should be standards-based and flexible, supporting many transport mediums. Based on EAI rather than SOA patterns, it tries to remove the coupling between the service called and the transport medium.



What is an ESB

Depends On Who You Ask • Service architecture built on top of

messaging • Web service management • J2EE Application Server • Suite or Standalone Product?

An ESB Is All of the Above • Key Component of a vendor SOA Suite • Delivers Data and Application Integration

Functionality • Supports Multiple Protocols • Based on Open standards and is 3rd Party

Interoperable ______________________________________________________________________ Student Notes:

• An Enterprise Service Bus provides everything you need for seamless integration of data and enterprise applications within your organization and with trading partners. The Enterprise Service Bus is a key component of a Service-Oriented Architecture, providing low-cost, standards-based integration between systems for greater IT flexibility and responsiveness. SOA allows organizations to more easily manage the complexity of their heterogeneous environment, without vendor lock-in to proprietary technologies.



ESB Moves Data

______________________________________________________________________ Student Notes:

• An ESB is the foundation for delivering services utilizing an SOA and EDA. At its core, it is a loosely coupled application framework that provides businesses with increased flexibility, reusability and overall responsiveness in a distributed, heterogeneous, message-oriented environment.

• Business Integration consists of four important solution components: (i) ESB, (ii) BPEL PM, (iii) OWSM

and (iv) B2B. Most vendor products provide the total one-stop platform for enterprise integration. They are fully integrated with an application server, a RDBMS, Eclipse-based integrated DVE and basic integration tools. They leverage various vendor infrastructure and GRID features such as security, high availability and scalability.



Evolution of the Bus

ERP

CRM

Proprietary M

essage B

us

Legacy

______________________________________________________________________ Student Notes:

• Distributed ESB services are centrally managed with vendor enterprise management and ESB Administrative control. The ESB Administrative control provides a service dependency viewer that enables visualization of fan-in and fan-out relationships for impact analysis of proposed changes to your systems. The console allows administrators to dynamically configure routing rules, transformations; domain value maps and other externally defined services.

WSDWSD

WSD

B2B

.NETPortal

WSD WSD

WSD

JMS and SOAP



Evolution of the Bus

______________________________________________________________________ Student Notes:

• In such a complex architecture, the ESB is the piece of software that lies between the business applications and enables communication among them. Ideally, the ESB should be able to replace all direct contact with the applications on the bus, so that all communication takes place via the bus. In order to achieve this objective, the bus must encapsulate the functionality offered by its component applications in a meaningful way. This is typically accomplished through the use of an enterprise message model. The message model defines a standard set of messages that the ESB will both transmit and receive.

• When the ESB receives a message, it routes the message to the appropriate application. Often, because the application was not built with the message model in mind, the ESB will have to transform the message into a legacy format that is understandable by the application. The software responsible for effecting these transformations is referred to as an adapter (analogous to a physical adapter).



ESB Core Features Deliver Information to the Right Place, at the Right Time in the Right Format

______________________________________________________________________ Student Notes:

• Purpose-built for flexible integration of distributed services and applications within an SOA, the Oracle ESB distributed architecture combines independently scalable integration services, intelligent routing, and an enterprise messaging backbone. The result maximizes flexible service re-use and efficient, scalable processing and delivers seamless integration across LAN boundaries and firewalls.



ESB Value Added

______________________________________________________________________ Student Notes:

• Supports distributed, high-throughput parallel processing of event streams. Services asynchronously place messages on and draw messages off enterprise messaging backbone. Integration services and enterprise messaging brokers scale independently, allowing efficient allocation of resources for computing and communication-intensive processing when and where needed.

• Facilitates integration with a wide range of protocols and business system interactions. Supports full

spectrum of integration scenarios: service invocation, data access, aggregation and dissemination, and notification and routing of events.

• Supports flexible, configured interaction. Fully isolates application or service from considerations of

deployment location, communication protocol, quality of service,message format, message destination(s), service orchestration sequence, and error recovery.



Primary ESB Pattern Summary

Point To Point • Adapter -> Transformation -> Adapter • Quick and Easy Integration • File to DB, Topic to Queue

Canonical Model • Integrate n+ Enterprise Applications • Domain Value Mapping • Dynamically Add New Subscribers

Routing Service • Decoupled Flexible Routing • Configurable in Rich Client • Services Visible to BPEL, BAM, Web

Services Gateway _____________________________________________________________________ Student Notes:

• In an ESB, data is passed between endpoints using messages. The coordination of the message passing is done using an ESB concept known as itinerary-based routing. A message itinerary is metadata that gets carried with a message that provides a list of forwarding addresses. The itinerary is a set of instructions telling the ESB invocation framework which endpoints the message needs to be delivered to as it travels from endpoint to endpoint across the bus. Itineraries contribute to the distributed nature of the ESB architecture by eliminating the dependency on a centralized routing engine, which could potentially be a single point of failure.



ESB Topology

______________________________________________________________________ Student Notes:

• An ESB is a highly distributed, event-driven, enterprise SOA that is geared toward integration. It is a standards-based integration platform that combines messaging, Web services, data transformation, and intelligent routing to reliably connect and coordinate the interaction of significant numbers of diverse applications across extended enterprises with transactional integrity.

• Adds routing-slip state ("ESB itinerary") to business data such that they flow together across network for distributed processing. Executes across multiple servers, clusters, and security domains, yet can be deployed and debugged from anywhere on the network. Scales with underlying communications infrastructure to deliver highly reliable and continuously available processing of large numbers of concurrent active routes--obviating performance bottleneck of hub-and-spoke orchestration models.



Ranking the ESBs

______________________________________________________________________ Student Notes:

• The market has two segments, with different leaders in each. The ESB suites segment is led by Cape Clear Software, Fiorano Software, BEA Systems, and Sonic Software, whereas the comprehensive ESB suites segment is led by Oracle, TIBCO, and Sun Microsystems. Included in this report is an interactive vendor comparison tool that provides detailed product evaluations and customizable rankings.



ESB Vendors

______________________________________________________________________ Student Notes:

• BEA, like IBM and Oracle, is starting to be able to leverage other components within it software portfolio. ALSB uses a lightweight version of WebLogic Portal for administration and operation. This is probably a plus for BEA, which in the past tended to put too much functionality in its application server, other enterprise grade vendors tend to have a more distributed approach to software engineering.

• The next-generation, Eclipse-based tool is specifically designed to build and deploy business

processes based on SOA. IBM states the tools are easy to use and require minimal programming skills.




BAM Overview



Who Needs BAM ______________________________________________________________________ Student Notes:

• One of the key issues when considering BAM is being non-invasive. A BAM should be able to collect the data it needs to present a real-time dashboard of business state and Key Performance Indicators (KPIs), without you having to engineer that into your applications.

• Another key issue is correlation. Lots of bits of data and process state go into creating a holistic picture of a business process. A BAM needs to be able to tie all those bits together. Different systems often use different keys to identify a particular instance of a process.

• Sometimes the interaction between systems is terse e.g. in a synchronous request/response

scenario the response message might not even have a process identifier. This can make it difficult for the BAM to create that holistic view and show you everything you want to see.



Business Activity Monitoring

______________________________________________________________________ Student Notes:

• The term 'Business Activity Monitoring' was originally coined by analysts Gartner, Inc and refers to the aggregation, analysis, and presentation of real time information about activities inside organizations and involving customers and partners.

• A Business Activity can either be a business process that is orchestrated by Business Process Management (BPM) software, or a business process that is a series of activities spanning multiple systems and applications. BAM is an enterprise solution primarily intended to provide a real-time summary of business activities to operations managers and upper management.



Window of Opportunity

______________________________________________________________________ Student Notes:



BAM/User Experience

______________________________________________________________________ Student Notes:

• The final result is that we develop a BAM dashboard reporting directly from ESB metrics. in most cases it is likely that the BAM async calls have some degradation on the overall process performance, given that the call to the BAM web service and the associated transform are happening before the actual process execution in some cases.

• Also, BAM dashboard will not effectively handle having many event sensors like BPEL does (ie. one

on the send, one on the response, one on the transform), we think a good design principle would be to limit your sensors to one per ESB system (just reporting that a significant event occurred), any more complex event reporting should be carried out from a higher level orchestrating process. Given the use cases for ESB as a transport medium, virtual interface or wrapper to create an autonomous service this fits well anyway.



Section I. Enterprise Service Bus Unit Summary

After successfully completing this section, you should be able to:

Illustrate the abilities of the Oracle Enterprise Service Bus Depict architecture of Oracle ESB Denote the evolution of an ESB Understand the embedded abilities of ESB components Illustrate the integration of BAM activities

Date post:	28-May-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

Introduction to Enterprise Service Bus - ITCourseware › docs › 1-09-00007-000-03-03-09 ›...

Documents