Alan H. Karp

Hewlett-Packard Laboratories

E-nabling

the

E-conomy

E-conomy Components

BuyerSeller

Buyer

Seller

StandardsLegacy Business

Market MakerMatch Maker

The Essential Difference

Hardware + Software

Tell the computer how to do the job

Services

Tell the computer what job you want done

Technology Need

Do for services what the browser has done for data

Make it as simple, in fact simpler and safer to create, compose, deploy, manage, personalize, and access services as it is to publish and access data on the Web.

Outline

• Why

• What• How• Some geeky stuffA technology transfer story

Why

B2B Procurement

Supplier discovery

Policy-based searchbrowse

Transmit purchase order

Sale order & confirmation receipt

Check status

Desktop delivery update

Invoice payment

Dynamic lookup, scalability

Transparency, seamless distribution

Virtualization, cross-device, securityData heterogeneity

Cross-device, security,Data heterogeneityGranting authorization, delegationcross-enterprise

Scan-device(?), security,cross-enterprise, delegation

Automated remittance, security

Current status:1. Static/ preferred supplier

2. Hard-coded, not easily extensible

3. Integrated with ERP

4. EDI, cross-device not automated, security(?)

5. OK with VPN, and with real-time integration 6. Not fully automated

7. OK for centralized, else some user intervention

8. Not automated

Obtain approval/ERPIntegration with ERP systems

Clicks and clicks away … Maybe

Locate merchant sitesCompareCross-optimize

Itinerary change?

Check another site for deal?

E-services Today(User’s Perspective)

Isn’t Your Best Value Just a Click Away?

StandardsStatic, custom solutionLocate and compare

Complex, slow, costly

E-services Today(Merchant’s Perspective)

Connections and connections away … Maybe Isn’t Creating an E-service Just a Connection Away?

Internet Challenges

• Today’s e-business web sites are proprietary, massive and costly to develop.

• Companies are forced to build out their entire offerings from the ground up.

• Even though they are connected to the Net, getting e-businesses and e-commerce sites to talk to one another in a meaningful way is difficult, special-case work.

The volume of business is limited by the bandwidth of eyeballs.

What

P2P, Grid, E-conomy

• P2P

Get the stuff I need to do my job

• Grid

Do my job using that stuff

• E-conomy

Do my job, and I don’t care what stuff you use

E-Commerce, E-Business, E-Services

Storefront

Customer Care

Supply Chain

IT

.

.

.

Business

Storefront

Customer Care

Supply Chain

IT

.

.

.

E-Commerce

Storefront

Customer Care

Supply Chain

IT

.

.

.

E-Business

Storefront

Supply Chain

IT

Storefront

Customer Care

IT

Supply Chain

Customer Care

E-Services

Int**net

E-conomyDiscover

Distribute

MonitorBill

Verify

Manage

Meter

Convert

QoS

Locate

Negotiate

Mirror

Isolate

Cache

E-conomy Marketplace

New services and service compositions,

New service providers

New customers

Services Framework

Service Specification

WorkflowRequirementsAccess control (security, billing, ...)

Int**net

Int**net

E-conomy

Service Advertisement

Int**net

E-conomy

Service Discovery

Int**net

E-conomy

Service Execution

How

Monolithic, proprietary systems

Open systems2-tier client-server systems

Open data (Web)3-tier, 4-tier, … systemsProprietary, one-off services (Amazon.com, Expedia, eBay, …)

E-conomy Dynamic n-tier systemsBrokered service composition (active personalization)

Systems Evolution

Assumptions and Implications

• Large number of machines– No centralized anything, forget consistency

• Dynamic– Deal with failures, new services

• Heterogeneous– Different hardware, OS, capability

• Hostile environment– Security is critical

• Different fiefdoms– Never look inside another machine

Architectural Principles

• Design for seamless, flexible, dynamic evolution

• Current and future

• Scalable, manageable, securable, extensible

• Simple abstractions and mechanisms

• No special cases

• No homogeneity requirements

• Uniform abstractions

• Based on widely accepted standards

Requirements

• Discovery

• Can’t rely on names or interfaces

• Extensible ontologies

• Service discovery within and across enterprises

• Security

• Support for dynamic roles

• Fine grained access control

• Secure firewall traversal

• Manageability

• Generation of management and billing events

• Ability to monitor state and control activities

• Integration with leading management platforms

Discovery(UDDI)

Paper (HTTP)

Alphabet (XML)

Web Services Stack

Infrastructureand otherServices

MatchMaker

Words (SOAP)

Sentences (WSDL)

Conversations (WSFL/WSCL/XLANG)

MarketMaker

. . Native Hardware

Host OS

Network

Web Services Layer

Dynamic Federation

A distributed system is one in which a machine I never heard of can render my machine useless.

-- Leslie Lamport

A Technology Transfer Story

Origins

• Global Computer - 1990

• Two talks to Labs – 1992, 1994

• Command performance – Joel Birnbaum, 1995

• Future Systems Department – Rajiv Gupta

• Client Utility Prototype with Bill Rozas - 1996

• Re-architected by Gang of 4 - Arindam Banerji

• Sales job

• Gave demo 157 times in 18 months

• Distributed 500+ copies of video

Birth, Infancy, Demise• E-speak Operation – November 1998 with 6 people

• $10M for first year from Unix box division

• “I’ll sell $500M more stuff in the first 6 months after we announce this stuff.” – He did!

• Alpha release May 1999 – E-services Conference

• 30 developers, 30 marketing/training

• Beta 2.2 December 1999 (first usable version)

• Retargeted as B2B platform

• Release 1.0 June 2000

• 150 people, $25M annual budget

• Shut down in May 2001

Customers

• Helsinki Telecom (April 1999)• Used e-speak broker, not full architecture

• Hi-Tel (Korea Telecom) (January 2000)• Game platform

• HP GSL (June 2000) (decommissioned 1/2003)• Procurement

• Spin Circuit (August 2000)• Electronic design documentation

• Slovenia (May 2002)• mTicka

Innovations

• First “web services” platform

• First open source (GPL) by a major company

• Completely integrated platform

• Security, manageability, discovery, naming

• First complete XML services infrastructure

• E-services Village (UDDI with rich query)

• Dynamic community formation

Named “Computerworld Smithsonian Laureate” for “Visionary Use of Information Technology” in April 2000

Theories on Demise

• Cute puppy, ugly dog

• No industry buy-in

• Too far from HP’s mainstream

• OpenView only software success

• Dot bomb

• Lost interest in B2B

• Lack of patience

• No clear path to $1B

• Purchase of Bluestone

• Appserver = middleware

Keys to Technology Transfer

• Luck

• Timing

• Compelling Vision

• Compelling Demo

• Executive Champion

• Internal and External Validation

• Innovative technology

Opinions

Key Issues

• Discovery

• Trust

• Naming

Discovery• AltaVista effect/Googlewacking

• Need context for search

• Global ontologies evolve too slowly

• UDDI Discovery

• Search by name of business

• Search by standard classification

• Search by interface (tModel)

• Problems

• No rich query

• No standard for tModel description

• Needs dynamically extensible ontology

Trust

• Trust based on identity not scalable

• Need “vouch for” mechanism

• Trusted party as risk taker

• Must reflect contractural relationships

• Often forgotten points

• Privileges granted to people

• Access rights enforced on processes

• People need to limit rights of their processes

Naming• Naming interacts with security

• Can’t protect what you can’t name• Reusing names a problem

• Location based global name spaces unworkable• Domain names and IP addresses change• Firewalls create private name spaces

• Opaque names require locator service• Hash of contents – changing content?• Random number – hijacking of name?• PKI solutions – lifetime of private key?

• Path dependent names reflect trust relationships

The Big Problem

Where’s the architecture?A SOAP name is a URLA WSDL name is a URL and portA UDDI name is a GUID

So what’s a web services name?How will we define a transaction?What about event driven services?An architecture provides the answers

Summary

• Now• Apps-on-tap• B2B portals

• Soon• Outsource computing and storage• Ubiquitous web services • Modular building blocks• Easy access from and to appliances, PCs, servers

• Longer term• Dynamic brokering• Web services advertise, discover, and compose• Web services negotiate, bill, manage, monitor

The Big Shifts Coming

Success Factors

Technology

Business ModelPartnerships

You