Connecting Trading Partners and Marketplaces with Web Services and UDDI

1
Connecting Trading Partners and Marketplaces
withWeb Services and UDDI

• Cafer TosunProduct Strategy Strategic Projects
• SAPMarkets, Inc.

2
Topics

• Business Challenges

• SAPMarkets Solution Vision

• Web Services and UDDI

• SAPMarketsWeb Services Strategy

• Outlook

3
Business challenges
Service Integration
Design consortium
Development partners
Service provider
Customer-driven design
HQ
Plant
Customer
Execution consortium
Dealer
Sub- contractor
Plant
Supplier
Decentralized production and sourcing
Integration
4
... could lead to Application Integration
Spaghetti
Screen scrape
Down- load file
Message queue
Sockets
Screen scrape
Screen scrape
Down- load file
Trans- action file
Trans- action file
CICS gateway
Sockets
RPC
Message
ORB
ORB
Message queue
APPC
Trans- action file
Trans- action file
Message queue
CICS gateway
Screen scrape
RPC
Down- load file
Message
APPC
Source Gartner Group
5
Topics

• Business Challenges

• SAPMarkets Solution Vision

• Web Services and UDDI

• SAPMarketsWeb Services Strategy

• Outlook

6
SAPMarkets Solution Vision
Enterprise using hosted on-ramp

• MarketSet
• Webflow
• Collaboration Engines
• Supply Chain
• Demand Chain
• Life Cycle
• Core
• Add-in Services

Connected Enterprise
Internet Saleson-ramp
Enterprise Buyeron-ramp
7
The next Step Private Exchanges e-Business
Networks
Collaborative Community
Public Exchange
Tendering
Documents
Bulletin Board
Private Exchange
Coll. Procurement
Workspace
B2B Sales
Enterprise Execution
Service Supplier Portal
Firewall
Integration Complexity
Intra
Extra
Inter
8
The way to go!

• Gartner Group There may be a compelling business
  case for c-commerce, but the technological
  foundation is incomplete. Enterprises should
  understand the technology challenges they will
  face when trying to operate in a c-commerce-based
  environment.
• Successful, broad commerce models require
  consistency
• U.S. Railroads in the 1880s
• Internet in the 1990s
• Standardization leads to e-business growth
• Cooperate on standards, compete on
  implementations
• Provide industry proven know-how to standard
  bodies (OASIS, UDDI, ebXML, W3C, rosettanet,
  BPMI)
• Participate actively in standardization efforts

9
Topics

• Business Challenges

• SAPMarkets Solution Vision

• Web Services and UDDI

• SAPMarketsWeb Services Strategy

• Outlook

10
The challenges for collaborative business

• How do I find the right trading partners?
• What products and services do they offer?
• What are the terms and conditions?
• How do I discover my partners e-capabilities?
• How can we conduct collaborative business
  efficiently?

?
?
Yellow Pages, Search engines, Catalogs, Contacts,
...
11
Publication and Discovery
12
What is UDDI?

• Universal Description, Discovery, and Integration
• An industry initiative to speed interoperability
  and adoption for web services
• Standards-based specifications for service
  description and discovery
• Shared operation of a global business registry on
  the Internet
• Partnership among industry and business leaders
  (200)

13
What is a Web Service?

• A Web Service is defined as A self-contained
  and described functionality accessible over the
  internet which serves some specific user need and
  is loosely coupled with other such services via
  (XML) messaging. SAPMarkets definition
• Samples provide stock quotes, process credit
  card transactions, calculating shipping costs,

14
Web Services UDDI
1. Service Registration SOAP
Web Services
3. Service InvocationSOAP, ebXML, BizTalk,
RosettaNet, COM, EJB/RMI, CORBA, ...
2. Service Discovery SOAP
15
Wide-spread usage
16
How UDDI works
4.
SW companies, standards bodies, and programmers
populate the registry with descriptions of
different types of services
1.
Marketplaces, search engines, and business apps
query the registry to discover services at other
companies
2.
UDDI Business Registry
5.
Service Type Registrations
BusinessRegistrations
Businesses populate the registry
with descriptions of the services they support
Business uses this data to facilitate easier
integration with each other over the Web
17
Public Registry Operation

• Peer nodes (websites)
• Companies registerwith any node
• Registrations replicatedon a daily basis
• Complete set ofregistered recordsavailable at
  all nodes
• Common set of SOAP APIs supported by all nodes
• Compliance enforced by business contract

Queries
IBM
Ariba
other
other
Microsoft
18
Types of Registry Data

• Business name
• Textual description
• Contact information
• Identifiers

• Services and product index
• Industry codes
• Geographic index

• Businesses register public information about
  themselves

• Service descriptions
• Application invocation
• Data binding

• Standards bodies, Programmers, Businesses
  register information about their Service Types

19
What does a registry contain?
Technical Specification
Business
identifier
category


1
identifier


1
businessEntity
tModel


category


1
service type
identification


businessService
category
categorization
1

Service type

bindingTemplate
20
tModels

• Usage Example
• Categorize content by
• Industry
• Product and Service Category
• Geographical Region
• ...
• Identify content by
• Business Identifier
• ...
• Specify service types
• Protocol types
• XML vocabularies
• WSDL service descriptions
• ...

43161704
Software suites
93-005-3793
SAPMarkets, Inc.
tModel
21
Business Registration

• XML document Created by end-user company (or on
  their behalf)
• Can have multiple service listings
• Can have multiple taxonomy listings

businessEntity
businessKey name URL description contacts business
Services identifierBag categoryBag
businessService
businessService
serviceKey tModelKey Name Description BindingTempl
ates
Key Name Description BindingTemplates
22
Example of a Registration
23
Contained services and bindings
ltbusinessDetailgt ltbusinessEntity
businessKeyF5E6gt Names, Descriptions,
Contacts ltbusinessServicesgt
ltbusinessService serviceKey3D21
businessKeyF5E6gt Names, Descriptions
ltbindingTemplatesgt
ltbindingTemplate bindingKeyA28C
serviceKey3D21gt Descriptions
ltaccessPoint URLTypehttpgthttp//www...lt/
accessPointgt lttModelInstanceDetailsgt
lttModelInstanceInfogt
lttModelKeygtC33Alt/tModelKeygt
Descriptions ltinstanceDetailsgt
Descriptions, Overview URLs
lt/instanceDetailsgt
lt/tModelInstanceInfogt
lt/tModelInstanceDetailsgt
lt/bindingTemplategt ...
lt/bindingTemplatesgt ltcategoryBaggt...lttMode
lKeygtA442lt/tModelKeygt...lt/categoryBaggt
lt/businessServicegt ...
lt/businessServicesgt ltidentifierBaggt...lttModelK
eygtC33Alt/tModelKeygt...lt/identifierBaggt
ltcategoryBaggt...lttModelKeygtA442lt/tModelKeygt...lt/c
ategoryBaggt lt/businessEntitygt
... lt/businessDetailgt
Business entity
Business service
Binding template
24
UDDI and SOAP
UDDI RegistryNode
User
UDDISOAP Request
HTTPServer
SOAPProcessor
UDDISOAP Response
UDDIRegistry Service
B2B Directory
Create, View, Update, and Deleteregistrations
Implementation-neutral
25
Registry APIs (SOAP Messages)

• Publishers API
• Save things
• save_business
• save_service
• save_binding
• save_tModel
• Delete things
• delete_business
• delete_service
• delete_binding
• delete_tModel
• security
• get_authToken
• discard_authToken

• Inquiry API
• Find things
• find_business
• find_service
• find_binding
• find_tModel
• Get Details about things
• get_businessDetail
• get_serviceDetail
• get_bindingDetail
• get_tModelDetail

26
The project
UDDI Project announced, spec v1 available
UDDI Business Registry goes live with beta
Public UDDI Business Registries live
UDDI spec v2 available
UDDI spec v3 available
We are here
UDDI turns over to a standards organization
09/2000 11/2000 05/01 06/01 12/2001
Q1/2002
27
UDDI Version 2

• Validation
• Validated taxonomies and ID systems
• Data structure
• Business relationships
• Service projections
• Structured address
• Internationalization
• Language-specific names
• Data replication
• Customizable replication process

28
Topics

• Business Challenges

• SAPMarkets Solution Vision

• Web Services and UDDI

• SAPMarketsWeb Services Strategy

• Outlook

29
SAP Markets Web Service Strategy

• SAPMarkets the Web Services Solutions provider
• Applications are developed as Web Services
• SAPMarkets solutions UDDI compliant
• built in publish, discover and invoke features,
  self describing
• SAPMarkets Service types are published in UDDI
• SAPMarkets the Web Services Framework provider
  for c-business
• SAPMarkets MarketSet Services Framework
• SAPMarkets A2A-Technology
• SAPMarkets Product offering on top of UDDI
• Information enrichment, attribute based
  enhancements for supplier, vendor evaluations,
• Analytical features

30
SAPMarkets the Web Services Solutions provider
3. Interoperate with a just discovered Business
2. Discover
1. Publish their Services
Enterprise Buyer
Internet Sales
SAP Service Types
UDDI Business Registry
0. Publish SAPMarkets Service types
31
Technical interaction example with UDDI
Partner registers Customers in UDDI
Enterprise Buyer
UDDI
Internet Sales
32
SAPMarkets the Web Services Framework provider
for c-business
Commercial Technical
Buyer
MarketSet Services Framework
Seller
public/private exchange

• Value Added Services
• Transport
• Import/Export
• Legal Services
• Payment
• Insurance
• ...

UDDI Business Registry
Local Carrier 1
Local Carrier 2
33
Private/Public Exchange with SAPMarkets
A2A-Technology reduce complexity
public/private exchange
Logistics Exchange
Transportation Company
Manufacturer Company
UDDI Business Registry
34
Transport Exchange
Selecting find service, if a new carrier should
be found
Here, the user can chose one of the already
selected carriers, originally selected from his
white-list
35
Inbox
36
SAPMarkets Product offering on top of UDDI
- Additional information - enhanced search
capabilities - Questionnaire
public/private exchange
private UDDI Business Registry
Logistics Exchange
Synchronise
Public UDDI Business Registry
37
Topics

• Business Challenges

• SAPMarkets Solution Vision

• Web Services and UDDI

• SAPMarketsWeb Services Strategy

• Outlook

38
What does interoperability need?
Inspection
Routing
Security
What Schemas?
My WebService
Your Web Service
XML
What Address?
Discovery
What Pattern?
Reliability
Attachments
Compare to slides from W3C Webservices Workshop
April 2001
39
Web Services Framework
Negotiation
Future
Reliability
In Proc
Security
Existing
Orchestration
Routing
Attachments
XML Protocol Envelope and Extensibility(SOAP)
Service Description(WSDL,)
Directory (UDDI)
Inspection
Structure (XML Schemas)
Syntax (XML)
Description
Wire
Discovery
Compare to slides from W3C Webservices Workshop
April 2001
40
Questions