MEN ARE FROM MARS, WOMEN ARE FROM VENUS, WEB SERVICES ARE FROM BETELGEUSE - PowerPoint PPT Presentation

1 / 55
About This Presentation
Title:

MEN ARE FROM MARS, WOMEN ARE FROM VENUS, WEB SERVICES ARE FROM BETELGEUSE

Description:

Solutions from the Past. Web Services and SOA The Future. Real ... what TCP/IP did for networks' Andy Astor, WebMethods. Non-SAP. Application. or. Business ... – PowerPoint PPT presentation

Number of Views:276
Avg rating:3.0/5.0
Slides: 56
Provided by: natha49
Category:
Tags: are | betelgeuse | from | mars | men | services | venus | web | women | astor

less

Transcript and Presenter's Notes

Title: MEN ARE FROM MARS, WOMEN ARE FROM VENUS, WEB SERVICES ARE FROM BETELGEUSE


1
MEN ARE FROM MARS, WOMEN ARE FROM VENUS, WEB
SERVICES ARE FROM BETELGEUSE
  • Denise P. Kalm,
  • Annie Shum,
  • BMC Software, Inc.

2
Agenda
  • The Problem
  • Solutions from the Past
  • Web Services and SOA The Future
  • Real Life Success Stories
  • Challenges
  • Summary

3
  • The Problem

4
How (most) Men Women See the World

Source Deborah Tannen
5
(No Transcript)
6
How Do You Make This Work?

7
The wish list
  • To link to any organization, anywhere in the
    world but with standard connection interfaces to
    the network
  • To communicate with all business partners with
    just one set of protocols, documents and business
    processes
  • To communicate responsively, reliably, securely,
    and without concern for scalability 24x7
  • To use the same technology to communicate within
    the organization as is used externally
  • To loosely couple organizations so that they
    dont need to know the internals of one anothers
    business processes or technologies
  • To be able to reuse data and services/processes
    to reduce cost
  • To be able to change services components or
    swap out one for another without breaking
    anything
  • Last But Not least To make money by providing
    data and services to others over the network.

Doug Kaye, IT Strategy, 2003
8
  • Solutions From the Past

9
History Flashback
  • 83 EDI complex, requires private networks
  • RPC developed for interoperability
  • 84-00 COM, DCOM, CORBA/IIOP, Java RMI,
    ORB vie for industry seal of approval
  • All fell short of boundary-less interoperability
    platform and language specific, typically
    tightly coupled and fine grained

10
New Beginnings
  • 91 CERN created HTML (from GML) next up ?
    XML
  • 98 MS put XML-tagged RPCs into documents,
    using http (SOAP)
  • 00 IBM, MS others defined WSDL and UDDI
    standards
  • the standards based underpinnings of Web Services
  • XML
  • SOAP
  • WSDL
  • UDDI

11
Distributed Computing At a Glance
12
(No Transcript)
13
WS
WS
WS Hub
WS
WS
WS
WS
14
  • Web Services and SOA
  • The Future

15
Web Services Executive Summary
  • Web Services is an emerging technology driven by
    the will to securely expose business logic beyond
    the firewall.
  • Through Web services companies can encapsulate
    existing business processes, publish them as
    services, search for and subscribe to other
    services, and exchange information throughout and
    beyond the enterprise.
  • Web services will enable application-to-applicatio
    n e-marketplace interaction, reducing the
    inefficiencies of human intervention.

16
Web Services Key Benefits
  • Software as a Service
  • Dynamic Business Interoperability
  • Accessibility
  • Efficiencies
  • Universally Agreed Specifications
  • New Market Opportunities
  • Legacy Integration
  • exposing mainframe functionality as ready-to-use
    enterprise Web services

17
A new generation of Legacy applications
  • In today's world of modern computing, there are
    more transactions processed by IBM CICS and IMS
    than by the Internet in its entirety.
  • Enterprise organizations leverage CICS and IMS
    to process more than 80 billion transactions or
    3.5 trillion worth of business every day

18
(No Transcript)
19
The 3 basic conceptual roles operations of
SOA Service Oriented Architecture
Discovery Agency
Service Broker
Publish/ Register
Find
Loosely Coupled
Service Description
Service Consumer
Service Provider
Bind/Interact
Service
Client
application software topology in loosely-coupled
one-to-one relationships
20
The SOA conceptual architecture of Web Services
with XML, SOAP, WSDL UDDI
UDDI for Discovery
Service Broker
UDDI Inquiry Find (xyz)
UDDI Publish Save (xyz)
WSDL
WSDL for description
Service Consumer
Service Provider
XML
Service
Client
SOAP
SOAP for Messaging
21
Source Computerworld
22
Alien Communication

GRAY-LISH
EVIL ALIEN
ESPERANTO
23
RCA Jack Web Services for Your Stereo

24
The Telephone Book of Web Services
  • UDDI each entry is an XML file

White Pages describe the company offering the
service
Yellow Pages Describe the categories
Card authorization scan lost/stolen cards and
authorize Credit approval calls Equifax and
verifies credit
Green Pages describe the service itself
25
Web Services Goal
  • To start a car, you dont need to know how an
    internal combustion engine works or even how the
    starter motor works. You only need to know how to
    use the interface that the car supplies to start
    it Turn the key
  • - Anne Thomas Manes

26
Web Services and SOA
  • A web-services-based SOA is both a process and a
    set of protocols designed to connect disparate
    applications.

27
Coupling Options
28
Web services are about interoperability a
subset of integration. They will do for
application connectivitywhat TCP/IP did for
networks Andy Astor, WebMethods
Web Services
Insulation Layer
29
(No Transcript)
30
(No Transcript)
31
Web Services - Inside the numbers
  • According to BusinessWeek, IBM has over 1,000
    employees working on technologies related to Web
    services.
  • IDC expects the total IT opportunity around Web
    services in, including hardware, software and
    services, to grow from
  • Western Europe 108 million in 2002 to 7.8
    billion in 2007, a compounded annual growth rate
    (CAGR) of 135.
  • North America to 21.0 billion by 2007 with an
    average annual CAGR of 94 among all segments.
  • By 2004, 40 of financial services transactions
    will leverage Web services models, with 35 of
    online government services delivered as Web
    services. (Gartner)

32
  • The Real-Life Success Stories

33
Mainframe Web Services A new generation of
legacy app
  • In todays world of modern computing, there are
    more transactions processed by IBM CICS and IMS
    than by the Internet in its entirety.
  • Enterprise organizations leverage CICS and IMS to
    process more than 80 billion transactions or 3.5
    trillion worth of business every day
  • Quickly expose mainframe functionality as
    ready-to-use enterprise Web services
  • Example Merrill Lynchs X4ML

34
X4ML Merrill Lynch Example
Legacy App
NAINTER
Online App for Merrill Lynch brokers
Legacy CICS
  • Name and Address Interface (NAINTER)
  • z/OS CICS app for managing account information
  • Key business rules/functions are embedded in the
    code
  • X4ML exposes these rules processes as Web
    Services
  • Provides SOAP support for NAINTER
  • No need to change legacy code in NAINTER
  • Developed to facilitate EAI project
  • Cost saving estimate 800K actual cost 30K

35
Dollar Rent A Car - Challenge
  • Expose mainframe-based reservation system (Quick
    Keys) for access by other business partners
  • Solutions that didnt work
  • direct connection to mainframe (EDI) didnt
    work
  • CORBA/IIOP cost security issues, lack of
    experience
  • Java RMI didnt know Java complex
  • DCOM Windows-based not all partners run
    Windows
  • Socket programming long development cycle no
    potential for re-use

36
Dollar Rent A Car - Solution
  • Dollar

SOAP Processor
Quick Keys
Partner
Dollar
Dollar
ACMS
XML Web Services
Win 2K
VMS
37
Dollar Rent A Car - Success
  • Cost effective links to new partners, gaining
    millions of rate requests and thousands of new
    reservations
  • Reduced dependency on for-fee referrals
  • Reuse of interface (four times so far) minimal
    effort required

38
Legacy Design

39
Adaptor Model
40
Gateway Model
41
What do these disparate companies have in
common?
42
  • The Challenges

43
Web Services Lessons Learned 1
  • Wells Fargo
  • "We make the technology and the business people
    sit together so they understand one another
    before we begin," he says. "That's the most
    important thing you can do. You need the business
    people to 'get' IT, and the IT people to 'get'
    business." Steve Ellis, exec VP
  • The National Student Clearinghouse (NSC)
  • "What surprised me the most is that there really
    haven't been technical issues -- the technology
    itself is almost trivial. Most important is to
    make sure that the business model is right --
    make clear why you should do this with a trading
    partner, and calculate your ROI ahead of time. -
    Mark Jones, VP

44
Web Services Lessons Learned 2
  • Things Remembered Inc., the largest personalized
    gift retailer in the U.S ( about 760 retail
    stores)
  • The key to developing a Web services application
    is to make whatever you build reusable, so that
    you can plug it in for other purposes. We built
    ours with that mind-set, and it's paying off." -
    Mark Fodor, director of e-business

45
The major missing pieces
  • Business Semantics
  • Security/Identity
  • Transactional Integrity
  • Reliable Asynchronous Message Handling
  • Orchestration Choreography
  • Single Sign On
  • OoS
  • Contracts and Negotiations
  • Billing Accounting Services Metering
    Chargeback
  • Standardization of Business Models
  • Intermediaries and Transformation Services
  • Operational Infrastructure

46
Mind the SOAP Overhead
The reality another layer on top of the
infrastructure that already exists. Particularly
true in the Java environment, where there are so
many layer mappings - from UML, to relational,
from XML to objects and back again, and XML to
code.
47
Strategic Tips for service design
  • Design services to be shared
  • Services have a clear purpose
  • Services are discoverable and support
    introspection.
  • Services plug into a SOA.
  • Services can be loosely orchestrated and use
    other services whenever possible for common
    tasks.
  • A service has a well-defined use policy/contract.
  • Services accept well-defined input and deliver
    well-defined output.
  • Services do not have hidden side effects (play
    well with others).
  • Services are interfaces to or from processes.
  • Services must provide visibility and an SLA.

48
Major roadblocks to full-scale Adoption
  • First roadblocks
  • Identity/Security
  • Web services management
  • Next roadblocks
  • Transactions/Rollback
  • Registry solutions
  • Web Services orchestration and workflow solutions
  • SLAs, QoS, QoB, Contracts, Metering/Chargeback
  • For large scale B2B and collaborative commerce
  • Web Services standards and infrastructure must be
    supplemented with trading agreements and
    non-repudiation

49
SOM Service Oriented Management
  • New management challenges for Web Services based
    SOA
  • A catalyst for a paradigm change from tightly
    coupled to loosely coupled app
  • From Point-to-point integration All tiers are
    well known and defined in advance
  • To Services can be dynamically discovered and
    different for each transaction
  • SOM for Web Services solutions
  • Bridge the gap between the underlying systems and
    the Services that run on top of them

50
Just the Tip of the Iceberg
Two things are clear - first Web Services are
far from mature by any measure, and second we
have a long way to run before we reach anything
like maturity. David Sprott, May 2003
Management
Security
  • Todays View Falls Short of Whats Required for
    Mission-Critical Business

Business Process Modeling
Data Transformation
Transactional Integrity
Orchestration/Workflow
Source WebMethods
51
Industry Co-opetition(Hope for the Future?)
  • Microsoft and IBM joined forces on Web Services
  • Jointly developed specifications were
    demonstrated (9/17/03) with an EDI-like
    application. The 2 companies linked
  • a manufacturer (using Linux),
  • a car dealer (using Websphere)
  • and a 3rd party supplied (using Linux-based
    wireless).
  • Complex, secure transactions between multiple
    business partners
  • Co-opetition combination of cooperation and
    competition

52
  • Behind the scenes was a high-tech cocktail of
    IBM's DB2 and WebSphere and Microsoft's SQL
    Server and .Net.
  • The auto dealer was notified upon logging on of a
    windshield wiper shortage. The crowd followed as
    the dealer proceeded to place an order with the
    supplier, who in turn placed an order with the
    manufacturer.
  • The underpinnings of the demonstration were
    actual Web services applications, developed with
    specs such as WS-Coordination (Web Services
    Coordination) and WS-AtomicTransactions,
    WS-Federation and WS-Reliable Messaging

53
  • Bill Gates left no room for doubt
  • "Web services are important to the foundation
    of the Internet, enabling e-commerce to become a
    reality."
  • Steve Mills, IBM Software Groups senior vice
    president and general manager
  • We're not declaring victory, but were showing
    people the goal line.

54
Web Services An Unstoppable Force

THE GLASS HOUSE
55
Questions?
  • Denise P. Kalm
  • Denise_Kalm_at_bmc.com
  • Annie Shum
  • Annie_Shum_at_bmc.com
Write a Comment
User Comments (0)
About PowerShow.com