OASIS Adoption Forum

1
OASIS Adoption Forum

• Tim Mortimer Red Wahoo

Wednesday Oct 6, 2004
2
Overview

• Current adoption hurdles
• Understanding interoperability components
• Whats going to change
• The real world

3
Current adoption barriers

• Cost
• Reinvented wheel each every integration
• Expensive enabling (middleware) solutions
• Complexity
• Building for integration has not been simple
• Medium Small size business
• Cost simplicity lead to lack of widespread
  adoption

4
Transaction vs Q/A integration

• Transactional
• end to end data exchange, ie. invoice
• Question / Answer service
• simply web service, ie. daily currency rate
• Why the distinction is important

5
Web Services ebXML

• web Services Mile wide / Inch deep
• ebXML Inch wide / Mile deep

Profile Contract
Process
Information
Complex
B2B e-commerce
Security
Messaging
Web Services
6
The Alignment Domain
Company A
Company B
Interface
Interface
Goal
Desire, Intent
Choreography
Process
Format, understanding
Information / Payload
Security
Messaging
Securely reliably
Authentication Non-repudiation
7
Whats really different

• Automating adoption
• significantly reduces cost
• True scalability
• makes interoperability growth exponential
• Guaranteeing meaning
• implicit semantic understanding

8
Public / Private Processes

• Public
• Community standard abstract what not how
• Actors, roles, QOS, collaboration sequence,
  payload
• Private
• Map community standard into your backend
• Spread compliance cost over community
• How this subtle distinction matters

ERP
ERP
Middleware
Middleware
Public Process
Private Process
Private Process
9
Creating an integration
CPP
CPP
Registry
Repository
Company A
Company B
CPA
Xi middleware
BizTalk
Invoice BPSS / WSDL
SAP Invoice - BPEL
Quicken Invoice - BPEL
10
Company 2
The N2 problem
12 / 24
12 / 36
PO
Inv
ASN
9
7
8
1
10
PO
PO
2
Company 3
Company 1
11
3
ASN
ASN
12
INV
Inv
5
6
N2 x p 10 x 3 300 100 x 3 30,000 1000 x 3
300,000 N2 is actually n(n-1) p
4
ASN
PO
Inv
Company 4
11
Scalability The Challenge
12
Scalability

• Discovery
• Human Machine readable schema
• Do not maintain CPAs at every end point
• Packaged / plug play integration is simple

13
The registry

• ebXML reg vs UDDI
• A single one or multiple registries (federation)
• Version differences
• uuid or key generated

14
(No Transcript)
15
(No Transcript)
16
The repository

• Storing
• public process schema (invoice 1 2, po, asn)
• private process schema (translators)
• Community standards development
• Critical Re-use, extension

17
Agreements to Trade (CPAs)

• Represents the binding to trade
• is sent/shared with the middleware
• prevents massive duplication of trading partner
  data

18
(No Transcript)
19
(No Transcript)
20
(No Transcript)
21
Message level integration

• Authentication
• Reliability
• Non-repudiation
• Failure / retry / error
• Payload vs Message

A
B
22
Security

• How is it achieved?
• Registry Connector level
• Fear of exposing services
• registry can control access to services on trust
  basis

23
BizDex

• What is it
• Standards Australia, Industry Government
• PPP infrastructure (roads network analogy)
• Our learnings and understanding
• www.bizdex.com.au

24
GovDex

• What is it?
• Project AGIMO (Aust Govt Info Mgt Office)
• Critical Governance Framework

25
Takeaway

• Cost
• Simplicity
• Scalability

26
further information

• Tim Mortimer Red Wahoo
• tim.mortimer_at_redwahoo.com
• www.redwahoo.com

27
Back up slides
28
Simple choreography
29
Private Process Workings
30
The Interoperability Stack

• Messaging reliably securely
• Security authentication non-repudiation
• Information/ Semantic format structure
• Business Process message exchange sequence
• Profile Contract agreements between partners
  
• Registry/Repository discovery, re-use

31
Standard type
Profile Contract
Process
B2B e-commerce
Information
Complex
Security
Web Services
Messaging
Simple
Simple (eg currency converter)
Complex, long running processes