and Emerging Dynamic eCommerce B2B and M2M …jeffsutherland.org/oopsla2000/xpo/dias/dias.pdf · "Implementation Conventions" (ICs) for Industry Specific Transactions ... Ariba Punchout

Speaker: Daniel M. DiasIBM Research Division, T. J. Watson Research Center

Yorktown Heights, NY 10598USA

Contributors: Asit Dan, Martin Sachs, Shaikh Hidayatullah, Thao Nguyen, Bob Kearney, Linh Lam, Cait Crawford

B2B and M2M Connectivity B2B and M2M Connectivity and Emerging Dynamic eCommerceand Emerging Dynamic eCommerce

© Copyright IBM Corporation 2000, all rights reserved

IBM

Res

earc

h

B2B Protocols: Large number and GrowingB2B Protocols: Large number and Growing

i2

Intelisys/Metiom

Mktplc. 1

ibm,com B2B Supplier 2 Supplier n

AribaPunchout(cxml)

OBI+

Horizontals

Mktplc. nVerticals

mySAP punchout

Standards/Consortia- EDI/ Internet-EDI- OAG- OBI- RosettaNet- ebXML - tpaML- SOAP- UDDI

Proprietary/Company Defined- Ariba Punchout;

cXML- Commerce One round-trip;

CBL- mySAP punchout- Intelisys

OBI+

Fulfillment and Supply Chain Processes

Marketplaces

Business Buyers

Sellers

Ariba

i2CommerceOne

mySAP ...

...

IBM

Res

earc

h

Outline of PresentationOutline of Presentation

Summary of Emerging B2B protocolsStandards / Consortia defined: EDI, OBI, RosettaNet, SOAP, ebXMLProprietary / Company Defined: Ariba punchout, Intelisys/OBI+, mySAP punchout, CommereOne round-trip

B2B Connectivity Requirements implied by ProtocolsSupplier connectivity to marketplaces, marketplace-to-marketplace connectivity, exchanges

Protocol Composition and Meta-Protocols for defining and instantiating protocols

Trading Partner Agreement Markup Language tpaMLEnterprise Business XML standards and tpaML WG

Dynamic eBusinessB2B life-cycle definition and "spontaneous" connectivity

Business 2

BackEndSystems

Buying Selling

B2B EC Suite

comm

Business 3

Business 1

BackEndSystems

IBM

Res

earc

h

BusinessProcess A

BusinessProcess B EDI Messages

-- Message Format/Syntax"Implementation Conventions" (ICs) for Industry Specific TransactionsTrading Partner Agreements on EDI Transactions & ICs

-- EDI is legacy for Business-to-Business electronic commerce-- Open EDI being proposed as paradigm shift

* Shift the focus to Business Processes-- OBI (Open Buying on the Internet), RosettaNet proposed standards

* End-to-end process flow with EDI-equivalent messages=> Move from messaging formats to end-to-end business processes

Move from VANs to Internet

Background and EnvironmentBackground and Environment

IBM

Res

earc

h

Open Buying on the Internet (OBI)Open Buying on the Internet (OBI)

Various Derivatives from OBI- e.g. Ariba Punchout, RosettaNet Puchasing PIP

Requisitioner MerchantServer

OBIServer

OBIServer

1ProcurementSystem

2

34Validation 5

ApprovalProcess 6 7 8

FulfillmentProcess9

EDI

Buying organization

Selling organization

HTTPS, Certificate-based authentication, optional non-repudiation,base 64 encoding, EDI format;not specified -- retries, duplicate detection/idempotency,asynchronous response times, status queries, order confirmation, invoice...

Payment Process

Single Signon

IBM

Res

earc

h

Approver Browser

Intelisys Purchasing System

Supplier Bus. Logic

4. Catalog URL

B2B Gateway

Commerce Server, e.g. WebSphere Commerce Suite

catalog ofgoods and prices

PO Req. generation

HTTP/HTTPs Transport

Order Fulfilment& Payment

internalfirewall

6

12

Intelisys/Metiom OBI (+) Protocol Intelisys/Metiom OBI (+) Protocol for B2B Procurementfor B2B Procurement

Requisitioner Browser

firewall

OBI B2B Protocol

IEC Link

OBI Messaging

9. Approve PO

1. LOGIN

3

5. SHOPPING

2

8. OBI POR

14. EDI 855

10. OBI PO

7

11.HTTP 200OK

13.Poll EDI 855

Selling OrganizationBuying Organization

externalfirewall

Approval Process

Ariba ORMS Purchasing System

SellerBus. Logic

4. Catalog URL

B2B Gateway

Commerce Server e.g. WebSphere Commerce Suite

catalog ofgoods and prices

PO Req. generation

HTTP/HTTPs Transport

Order Fulfilment& Payment

internalfirewall

12

Ariba Punchout Process Ariba Punchout Process for B2B Procurementfor B2B Procurement

Requisitioner Browser

firewall

Ariba B2B Protocol

CXML Messaging

9. Approve PO

1. LOGIN

3

5. SHOPPING

2

7. PO to Appr

10. PO (CXML)

6 PO

11.Sync. PO Ack

8. Sync. Ack.

Selling OrganizationBuying Organization

Arib

a N

etw

ork

externalfirewall

IBM

Res

earc

h

RosettaNetRosettaNet

RosettaNet Consortium is Defining Partner Interface Processes (PIPs) originally for IT Supply ChainDefined as Clusters -> Segments -> PIPs

Cluster 0: Support; Segment A Admin.; PIP01A (failure)Cluster 1: Partner, Product and Service Review

Segment A: Partner Review; PIP1A1,2 Acct. setup, maintainSeg. B: Product and Service Review

Cluster 2: Product IntroductionSeg. A: Prep. for Distrib.; PIP2A1-8, distrib., querySeg. B: Prod. Change; PIP2B1-5, change prod., mkt., sales, tech.

Cluster 3: Order ManagementSeg. A: Quote & Order entry; PIP3A1-7, req. quote, query price and avail., transfer shopping cart, PO, order status, PO acc.Seg. B Transp. & Distrib; seg. C returns & finance; seg. D Config.

Clus. 4: Inventory mgmt; Clus. 5 Mkt. info; Clus. 6 Service & Support

IBM

Res

earc

h

RosettaNet Manage Purchase Orders PIPRosettaNet Manage Purchase Orders PIP

Principal messages in PIPOrder CreateOrder ChangeOrder CancelSimilar flow for each message

Buyer Seller

Order Create Message POSync. Ack. -- HTTP 200 OK

Order ResponseSync. Ack. -- HTTP 200 OK

Browser

Publisher Subscriber

Notification Service

GenRegForm

BPF

SubRegForm

RedRegForm

ViewNewItems

NotificationDaemon

RetSubConf

HTTPSRec

HTTPSSender

BPF Manager

Doc Exchange

TPAO

SI

Scenario: Catalog Update PIP: Catalog Subscription 1B1

Subs DB

1

2

3

4

5

6

7

8

9 10

11

814

814

Logi

n Fo

rm

814

Cont

ents

id RMsg NewSub

"Pending"

814

824

Update Status

Hidayatullah Shaikh

RosettaNet Catalog Subscription PIP

IBM

Res

earc

h

Simple Object Access Protocol - SOAPSimple Object Access Protocol - SOAP

SOAP proposal submitted to W3C by Microsoft, IBM, othersXML-based lightweight protocol for distributed info. exch.Defines envelope for describing what is in msg., encoding rules for app. defined data types, and RPC conventionsSOAP is stateless; no bi-di communications specifiedNeeds Security and other extensions for use in B2B env.

Client Server

HTTP Post <envelope>[hdr]<body>

Sync. Ack. -- HTTP 200/500

<body> either arbitrary messageor RPC; convention for RPC callsand responses

IBM

Res

earc

h





Trading Partner Agreement Markup Language tpaMLBusiness-to-Business Protocol Framework


Business 2

BackEndSystems

Buying Selling

B2B EC Suite

comm

Business 3

Business 1

BackEndSystems

IBM

Res

earc

h

B2B Connectivity to Marketplaces: B2B Connectivity to Marketplaces: The ProblemThe Problem- Many Buyers have selected a horizontal /procurement network- Different protocols for each network- Need to support a growing number of B2B protocols

Intelisys/Metiom

Mktplc. 1

ibm,com B2B

Supplier 2 Supplier n

AribaPunchout(cxml) OBI+

Horizontals

Mktplc. nVerticals

mySAP punchout

Marketplaces

Buyers

Sellers

i2CommerceOne

Ariba mySAP ...

...

IBM

Res

earc

h

Supplier Connectivity Requirements Supplier Connectivity Requirements

Intelisys

Marketplc.

Supplier1 ibm.com Supplier n


Connectivity to key marketplaces

Horizontals

Verticals

Buyers

Sellers

Marketplaces

i2CommerceOne

......

Ariba mySAP

IBM

Res

earc

h

Marketplace Connectivity RequirementsMarketplace Connectivity Requirements

Intelisys

Mktplc. 1

ibm.comB2B hub

Supplier 2


Connectivity to key horizontals

B-B Protocols for VentroIntegration ofexternal suppliers

AribaPunchout(cxml)

OBI+

Supplier n

Supplier connectivity to Mktplc.

Mktplc. n

Inte

r-Mkt

plc.

conn

ectiv

itypa

ckag

e New M2M Protocols needed

i2 CommerceOne ...

...

Ariba mySAP

IBM

Res

earc

h

B2B Protocol Exchange RequirementB2B Protocol Exchange Requirement

Intelisys

B2B Protocol Exchange

ibm.comB2B

Supplier 2 Supplier n

Mktplc. n

HorizontalsAribaPunchout(cxml)

OBI+

Supplierchosenprotocol

i2CommerceOne

......

RoundTrip

mySAPpunchout

Mktplc.chosenprotocol

Ariba mySAP

IBM

Res

earc

h







Business 2

BackEndSystems

Buying Selling

B2B EC Suite

comm

Business 3

Business 1

BackEndSystems

IBM

Res

earc

h

Inter-enterprise IntegrationInter-enterprise Integration

Workflow

BPBP

BPBP

Trading Partner Trading Partner

Application

Application

Business Process

Application

Application

Business Process

TPAs

NO Shared MiddlewareLoose CouplingNo 2-phase commits

Long-Running Conversations

Back-end IntegrationWorkflow

Back-end Integration

Application

Application

XML

B2Bi

Untrusted Access Hide internal process

IBM

Res

earc

h

Local Business Process

TPA

TP

A

TPA

TP

A

TPA

T

PATP

A

TPA

TPA

T

PATP

A

TPA

SupplierMarketplaceService ProviderAgencyWarehouseConsolidator ...

Sub-contractorSupplierService providerPayment process ...

Long runningdistributed processesand trasactions onthe Internet

B2B ArchitectureB2B Architecture

// Authentication, non-repudiation

Examples

IdentificationOverall properties

Comm. properties

Actions

Sequencing rules

Recourse actions

Roles

Error handling Legal text

Security properties

Constraints

Responsiveness

// Business partner info.

// Contract duration

// HTTP, SMTP, etc.

// Reserve, modify, etc.

// Refund, etc.

// Buyer, seller, broker, etc.

// Retries, actions invoked

// Penalty if unreachable

// Modify before 6 p.m

// Modify after reserve

// Timeout

TPA/ Service Contract

SMTP HTTP VAN

XML/EDI

PO RFQ

Trad

ing

Partn

er A

gree

men

t (T

PA)

PO

Local Business Process

MQ

POstatus

POcancel

OBI Plus

EDI XML

DOCUMENTEXCHANGE

Reliable msging.Logging, audit trail,

time stampsecurity, query

Parsing, generation,

doc repository

Negotiation

Business protocols/ processes

Transport

B2B B2B LayeringLayering

General B2B Process Flow

Requisitioner MerchantServer

OBIServer

OBIServer

1WebServer

2

3

4Validation 5

ApprovalProcess 6 7

Payment Process (SET)

89

EDI

WCS

OBIOBI

Buyer organization

FulfillmentProcess

Doc.Exch.

Change after PO

PO, PO change

Time-out

Buyer, seller, broker

Authentication, non-repudiation

Key TPA Elements To Be SpecifiedKey TPA Elements To Be Specified

IdentificationOverall properties

Communication properties

Actions

Sequencing rules

Recourse actions

Roles

Error handling

Comments

Security properties

Constraints

Responsiveness

Business partner info.TPA duration, Business protocol

HTTPs, FTP, SMTP, Messaging

Refund

Retries, actions invoked

ID of accompanying paper contract

Change within 24 hours

Examples

Formal Specification of TPA Avoids MisinterpretationExisting protocols specified as special cases

IBM

Res

earc

h

ebXML: Enterprise Business XMLebXML: Enterprise Business XML

Broad-based industry consortium for electronic commerce standards (approx. 120 companies)Open XML-based infrastructure for global e-business informationLower e-business entry barrier for small/medium enterprises and developing nationsProject teams related to electronic TPA

Business Process methodologyMessage Structure and RoutingTrading Partner Profiles and TPARegistry and Repository

IBM

Res

earc

h

Standardizing the TPAStandardizing the TPA

Interoperability is essential to wide-spread B2B e-commerce

Avoid vendor-dependent solutionsPartners with different implementations must be able to do business

Create a vendor-neutral standard TPA languageebXML has begun a standardization activity on electronic TPAs based on the IBM proposalDraft tpaML proposal available from http://xml.org/xmlorg-resources/b2bxml.shtml

IBM

Res

earc

h

ebXML Trading-Partner Project TeamebXML Trading-Partner Project Team

MissionDefine a specification for creating the IT part of a partner profile and a TPA, which is a combination of two partner profilesEnable automated configuration generation from TPA

TPAIT configuration file, specifies only things that TRP messaging service can manage and enforceNo business informationNo business semantics except message names/schemas and sequencing rules

Derive from BP metamodel

IBM

Res

earc

h

XML based TPA StructureXML based TPA Structure<TPA><TPAInfo>

</TPAInfo>

<Transport></Transport>

<DocExchange></DocExchange>

<BusinessProtocol></BusinessProtocol>

</TPA>

IBM

Res

earc

h

Key Document-Exchange ElementsKey Document-Exchange Elements

Message encodingOption to check for duplicate messagesMessage RetriesMessage security

Nonrepudiationcertificates

Digital envelopecertificates

IBM

Res

earc

h

Key Transport ElementsKey Transport Elements

CommunicationProtocol

HTTP, SMTP, FTP, VAN-EDIAddresses

Transport SecurityEncryption definitionAuthentication definitionCertificates

Each party's certificate URLCertificate authorities' certificate URLsKey length

IBM

Res

earc

h

RolesRolesTPA may be in terms of actual parties or roles

Example of roles: buyer, seller

Roles used to build prototype TPAsAuthoring tool or registration tool resolves roles

Replace roles by specific parties everywhere in TPAFill in party-specific information such as addresses

<Role><RoleDefn> <RoleName>rosettanetseller</RoleName><RolePlayer>IBM</RolePlayer></RoleDefn>

</Role>

IBM

Res

earc

h

Action ExamplesAction Examples

Actions in a procurement TPAProcess purchase orderModify purchase orderCancel purchase order

Actions in an airline reservation TPAReservation requestModify reservationCancel reservationConfirm reservation

Actions in a TPA are defined by the business application, not mandated by the TPA standard.

IBM

Res

earc

h

Elements of Action DefinitionElements of Action Definition

Request nameRequest message (schema)Delivery channelReply nameException reply nameMaximum allowed service timeSequencing rules

IBM

Res

earc

h

Action DefinitionAction Definition<Action><Request><RequestName>processOBIPOR</RequestName><RequestMessage>OBIPOR</RequestMessage><Channel ChannelID="name" /> </Request>

<Response><ResponseName>name</ResponseName></Response>

<ExceptionResponse><ExceptionResponseName>name</ExceptionResonseName>...

<ResponseServiceTime><ServiceTime>time</ServiceTime></ResponseServiceTime>

<Sequencing>...

</Action>

IBM

Res

earc

h

Sequencing RulesSequencing Rules

<StartEnabled><RequestName>action_name</RequestName>

</StartEnabled>

<Sequencing><Enable> 

<RequestName>name_of_action</RequestName>

</Enable><Disable>

<RequestName>name_of_action</RequestName>



</Disable>

</Sequencing>

Directly under Service Interface tag

Inside Action Definition

IBM

Res

earc

h

Rules Code

Transport

Interface Code

'Inbound' Request/Replies 'Outbound' Request/Replies

Network

Sub Contractors

ERP Packages

Business Applications

Workflow

Set Up and Generation

Run Time

Document Respository

Runtime Services

Logging

Local Business Processes

BPF Manager

XMLTPAs

Application Interfaces

ParsersSecurity HandlersEncoders

Executable Files

Registration Database

'Helpers'

Network

HTTPSSMTP

MQSeriesEDI

Registration Tools

Generation Tool

Authoring Tool

(a)

(b)

(c)

Document Exchange

B2B Integration Framework and TPAs B2B Integration Framework and TPAs

IBM

Res

earc

h







Business 2

BackEndSystems

Buying Selling

B2B EC Suite

comm

Business 3

Business 1

BackEndSystems

Vision of Spontaneous e-Commerce Vision of Spontaneous e-Commerce

Service Broker

Service provider

Service consumer

PublishFind

Bind / Service invocation

Locate services provided by other businesses, create agreement and invoke services

Quick and easy business-to-business integrationDynamic business processes

partner discovery and selection, negotiation of terms & conditions, contracts, connectivity set-up, order/message flow, fulfillment...

IBM

Res

earc

h

Universal Description, Discovery, and Universal Description, Discovery, and Integration: UDDIIntegration: UDDI

UDDI spec. released Sept. 6/00 by Ariba, IBM and MicrosoftUDDI provides Web-based registries for business description, discovery and interfaces

White Pages: Business name, text description, contact info. (names, phone #, Web sites, etc.), identifiers (e.g. DUNS number)Yellow Pages: Business categories; 3 taxonomies in V1,

Industry: NAICS (US Govt.), Prod./Svc.: UN/SPSC (ECMA), Location

Green Pages: Business services, service descriptions, binding info.tModel provides reference to info. on spec. of interface

tpaML template could be a tModel for B2B serviceUDDI API provides functions for registering and finding information

SOAP messaging over HTTP used to access UDDI service

IBM

Res

earc

h

Automatic Contract Enabling System(ACES)Automatic Contract Enabling System(ACES)

ACES ObjectivesDefinition of automated contractsRegistration and discovery of partner profiles

Could be done using UDDINegotiation of contract

Protocols, business parametersTools/infrastructure

Automate contract setup process

IBM

Res

earc

h

TPA/Service Negotiation Prototype: TPA/Service Negotiation Prototype: Remote partner registrationRemote partner registration

1. TPA/service template creation/setup2. Service advertisement/discovery3. TPA/service negotiation4. TPA/service agreement submission/approval/registration/instantiation 5. Execution of B2B process

procurement administrator

SellerPortal

TPATemplate

SellerB2B

Server

Negotiate TPAElements

3

1

Instantiate TPA

Execute TPA-basedBusiness Process

5

Negotiation

4

3

BuyerB2B

Server

seller administratorTPA publish and

setupDiscovery

2 UDDI Server

Buyer

Mktplc.

IBM

Res

earc

h

Summary and ConclusionsSummary and Conclusions

A large number of B2B conn. protocols emergingEDI, OBI, RosettaNet, SOAP, ebXML, UDDI, Ariba punchout, Intelisys/OBI+, mySAP punchout, etc.

Connectivity becomes complex to implementSupplier connectivity to marketplaces, marketplace-to-marketplace connectivity, exchanges

These Protocols can be composed, specified and quickly implemented using tpaML

tpaML is being standardized under ebXML Dynamic eBusiness is emerging as a new paradigm

B2B specification, discovery, negotiation, and set-up for "spontaneous" connectivity

Business 2

BackEndSystems

Buying Selling

B2B EC Suite

comm

Business 3

Business 1

BackEndSystems

Documents

and Emerging Dynamic eCommerce B2B and M2M …jeffsutherland.org/oopsla2000/xpo/dias/dias.pdf · "Implementation Conventions" (ICs) for Industry Specific Transactions ... Ariba Punchout