Extensible Enterprise Service Bus

1
Extensible Enterprise Service Bus

• Eric Newcomer
• Chief Technology Officer IONA Technologies

2
at a glance
Solid business with a history of profitable growth
Customers include worlds largest firms

• 80 of Global Telecom
• 70 of Financial Services in Global 100
• Blue Chip System Integrator Partners

• Founded in 1991
• Publicly traded since 1997
• 50 million cash on hand
• No debt

NASDAQIONA
Our Approach Making Software Work Together

• We work within the normal diversity and
  heterogeneity found in enterprise computing
  systems
• We tie together applications from different
  vendors running on different operating systems
  and using different protocols and different
  message formats
• Especially when those applications were never
  designed to be integrated

Worldwide presence

• EMEA HQ in Dublin, Ireland
• US HQ in Massachusetts
• APAC HQ in Tokyo, Japan

3
Eric Newcomer,Chief Technology Officer, IONA
Technologies

• Responsible for directing and communicating
  IONA's technology strategy as it relates to
  standards adoption, product architecture, and
  design
• Joined IONA in November 1999, after 16 years at
  Digital/Compaq, where he achieved a corporate
  level technical position
• Leads IONA's participation in the standardization
  activities around Web services
• Founding member of the XML Protocols Working
  Group at W3C
• Editor of the Web Services Architecture
  specification at the W3C
• Co-author of the recently published Web Services
  Composite Application Framework (WS-CAF) set of
  specifications submitted to OASIS
• Author of the best-selling Understanding Web
  Services (published in May 2002 by
  Addison-Wesley), my new book, Understanding SOA
  with Web Services, is due in December, 2004 from
  Addison-Wesley

4
Topics for this Session

• Enterprise Service Bus -- the Infrastructure for
  SOA
• The Power of Extensibility
• Artix the Extensible ESB
• Artix Examples / Use Cases

5
Enterprise Service Bus The Infrastructure of
Service Oriented Architecture
6
Evolution Towards SOA

• The evolution of a thirty year drive towards
  standards-based, distributed computing and
  component based development
• Driven by the economics of system re-use and
  ubiquity of global high speed network
  connectivity
• Natural progression towards loosely coupled
  interacting systems defined by standard
  interfaces to services

7
SOA Architecture of Interfaces
What is a Service? A business-complete logical
unit of work, accessible programmatically from
independently designed contexts via a direct
openly documented interface
Service Interface
Service Implementation
What is an SOA? Application software design
consisting of services and service consumers
(clients) in loosely coupled 1-to-1 relationships
Service Consumer
Interface
Interface
8

• SOA is not a software product, but instead an
  IT architectural movement

Web Services are the plumbing ..
9
(No Transcript)
10
Summary of SOA Benefits
Enterprise Service Bus
Service Repository
ProcessEngine
Presentation
Business Logic
Business Logic
Business Logic
Data Access
Data Access
Data Access
Retail Banking
InvestmentBanking
MortgageLending
11
What Infrastructure Do Applications Need?

• Support for documented interfaces
• Service or event registration and discovery
• Industry standards (e.g., Web services) - to
  facilitate interoperability
• Qualities of service - for scalability, low
  latency, reliable delivery
• Management - Monitoring, load balancing,
  failover, configuration, security, fault recovery
• Support for common interaction communication
  patterns among services

12
ESBs Combine the Strengths of Previous Middleware
13
Enterprise Service Bus

• IONAs View
• A new architecture for lowering the cost of
  integration
• Draws on the discipline of SOA and Web Services
  technologies
• Radically changes the technology and economics of
  integration projects
• Industry consensus
• Deep native support for all relevant XML and Web
  Services standards
• Transformation capability and routing support
• Support for existing enterprise applications
  platforms and infrastructures

An Enterprise Service Bus (ESB) is a new kind
of middleware that combines features from several
previous types of middleware into one package.
ESBs provide the fabric of services required for
enterprise system interoperability and building
new applications.

• Offer order-of-magnitude better economics than
  enterprise application integration (EAI) or
  customized integration approaches.

14
ESBsDemystified

• ESBs are a collection of distributed,
  interconnected end-points
• ESBs can not be based on a single transport but
  instead must support multiple transports
• ESBs do not use an internal canonical format
  but must support transformation and routing
• End-points must be standards based (WSDL) and
  extensible
• End-Points are distributed therefore ESBs are
  as well
• End-Points must be secure, manageable and
  reliable or the concept wont work!

15
IONA and its CustomersPioneered This Approach
16
Artix and Extensibility
17
Not All ESBs are Created Equal
Class ofProblem
Add Quality of Service Requirements
ExtensibleProblem
Complexity Of Application
18
Extensibility Adapting to Change
Extensibility the ability to change by modifying
or adding features.

• Example XML
• XML is an extensible markup language
• It can be extended to describe very specific
  kinds of data

Can The ESB be Extended to Describe Any End-Point
Through a Standard Description Language?
19
Requirements Drive Extensibility
20
Closing the Gap

• Extensibility bridges the technical gaps between
  modern development and run-time platforms
  (J2EE/.NET) and existing enterprise systems.
• Unique requirements are addressed by
  defining/configuring new capabilities and
  plugging them into an open, pluggable run-time
• Plug-ins keep run-time small enough for
  distributed deployment, while retaining
  zero-latency, embedded performance
• After initial deployment configuration changes
  to extensible endpoints can be made without
  disrupting access to the service

21

• Service-Enable Mission-Critical Enterprise
  Systems
• Plug-In Architecture for Transports, Protocols,
  Application Platforms and Value-Added Services
• Proven High Performance Lightweight Run-Time
• Broad Platform Support Including the Mainframe

22

• Plug-In Architecture
• Transports, Protocols, Application Platforms and
  Value-Added Services

• Popular messaging middleware application
  platforms

• Plug-Ins extend existing security, management,
  high availability and transaction capabilities

23
Broad Platform Support
24
Mobile to Mainframe
25
Enterprise Quality of Service
26
Use Cases and Customer Stories
27

• Business Problem
• Acquisition of DHL, Airborne plus existing lines
  of business
• Lots of technologies, disparate systems impedes
  brand and corporate synergies
• Technical Challenges
• Move to a business process flows
• Desire to build a Service Backbone to connect
  all of the disparate businesses
• Extensive requirements for Security, Management,
  Transports, more ..

28

• Trying for 4 years to build ESB selected IONA
  over BEA, Sun, Oracle and others
• Version 1 of custom ESB in production for 18
  months
• Critical Shortage
• Performance and Scalability
• 660 million customercontacts every year
• Extensibility
• Multi-transport
• Multi-platform
• Multi-payload
• Enterprise Qualities of Service (Security /
  Management / H/A)
• Cost of change

29
Approach

• Deutche Post adopting IONAs Artix as the
  integration for its Service Backbone (SBB)
• Enterprise Requirements Drive Demand For
  Extensible ESB Technology
• Plug-In Architecture for Transports, Protocols,
  Application Platforms and Value-Added Services
• Plug-Ins for popular messaging middleware and
  application platforms
• Configurable plug-ins for extending existing
  security, management, high availability and
  transaction capabilities
• Broad platform support including the mainframe

30
Results

• Evolution of home-grown IT landscape to service
  oriented architecture
• About 20 service participants (service provider
  and/or service consumer) already implemented and
  available
• About 15 service participants are candidates for
  2004/2005
• More than 80 service operations available,
  further 40 in development
• Significant costs savings and time savings
  realized, especially for new implementations
• Synergies already identified within Deutsche Post
  World Net Group DHL, Global Mail

31
Major US Telecom Service Provider

• Business Problem
• Due to commoditization of local land line market,
  in 2003 abandons market
• Aggressive business plan to become a leader of
  the VOIP market new emerging platform for
  telephony
• How to repurpose existing OSS and BSS
  applications to fit a new market
• Technical Challenges
• Diversity of OSS/BSS systems
• Desire to move to SOA / WS as core system
  architecture
• Scale for the Web

32
System Architecture
33
Technical Highlights

• End-Points
• Artix embedded at end-point, executing on same
  hardware, managed and secured using the native
  mechanisms of the application, without changing
  applications
• Deployment Flexibility
• Different end-points required different
  deployment models client / server / switch
• Language Independence
• Artix components are deployed using C and Java
• Multiple Protocols and Bindings
• Artix supports multiple transport protocols and
  message format bindings

34
Business Value

• By implementing Artix as the ESB for this
  project, realized significant business value
• Speed to market
• Scaling for the Web
• Leveraged existing systems and hardware
• Leveraged existing internal skill sets

35

• Fortune 100 telecom service provider
• HQ in Atlanta, GA, parent company of Cingular
  Wireless, the nation's largest wireless voice and
  data provider
• Services Offered
• Residential and small business - local and
  long-distance service, dial-up and high-speed DSL
  Internet access, satellite television and
  Cingular Wireless service.
• For businesses, secure, reliable local and
  long-distance voice and data networking
  solutions, online and directory advertising

• Business Problem
• Advance its core capabilities to meet customer
  needs and competitive pressures
• Lost revenue opportunities business complexity
  is generally off-loaded to the sales
  representative and not process oriented
• Increased costs and elongated delivery
  timeframes addition of new business rules and
  products are costly and must be done to multiple
  systems
• Technical Challenges
• Multiple systems perform related functions
• Multiple user interface technologies, desktops,
  and metaphors
• Systems tend to be product-centric, not
  customer-centric
• Little or no integration between applications

36
Retail Ordering System

• Strategic set of applications for managing retail
  orders within the consumer business unit
• Massive scale thousands of users millions of
  transactions
• Legacy client technology (X-Windows Motif)
• Client side - distributed across retail sales
  center
• Server side - datacenter based

37
The Opportunity

• Improve effectiveness of call center agents
• Reduceoperational costs
• Implement multiple channel enablement
• Leverage embedded investments

38
System Decomposition
The re-platforming of ordering applications to a
.NET architecture
Rich Client Presentation
IONAs Artix used to create new integration layer
Web Services
Retail Ordering System
Existing BellSouth ROS platform
Back-End Systems
Systems of record billing, CRM, etc..
39
The Role of Artix

• Integration
• Exposing ROS application as Extensible Web
  Service Endpoint
• Security
• User authorization/authentication
• Security Token Mediation
• Discovery
• Client-side Session ID Leasing (Session Manager)
• Server-side load-balancing (Locator)
• Management
• Integration with BMC Patrol

40
Value

• Business Value
• Improved Sales Center Effectiveness
• Closing the sale
• Product bundling
• Improved Computer Telephony Integration
• Better call routing
• Sales tracking

• Technical Value
• Consolidationand System Renovation
• Eliminated hundreds ofmid-tier servers
• Established new security model for sales center
  workers
• Leveraged existing systems, skills, etc.

41
Questions ?