Electronic Business eXtensible Markup Language Business Process Specification Schema ebXMLBPSS - PowerPoint PPT Presentation

Loading...

PPT – Electronic Business eXtensible Markup Language Business Process Specification Schema ebXMLBPSS PowerPoint presentation | free to download - id: 8493b-ZDc1Z



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

Electronic Business eXtensible Markup Language Business Process Specification Schema ebXMLBPSS

Description:

Binary Either a business transaction or another Binary collaboration (allows for recursion) ... greater flexibility in defining how collaborations take place. ... – PowerPoint PPT presentation

Number of Views:64
Avg rating:3.0/5.0
Slides: 34
Provided by: mikeri2
Learn more at: http://www.cs.ucsb.edu
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: Electronic Business eXtensible Markup Language Business Process Specification Schema ebXMLBPSS


1
Electronic Business eXtensible Markup Language
-Business Process Specification Schema
(ebXML-BPSS)
  • Mike Richmond
  • 11/21/2003

2
Outline
  • Introduction
  • Key Concepts
  • Business Transaction Semantics
  • XML BPSS Example

3
What is ebXML?
  • A set of specifications that enhance e-business
    activities by allowing business process
    collaborations between 2 or more parties.
  • Started in 1999 as a joint effort between
    UN/CEFACT and Oasis
  • Oasis A global consortium that works to develop
    and implement e-business standards.
  • UN/CEFACT United Nations Center for Trade
    Facilitation and Electronic Business
  • Goal create specifications to allow worldwide
    platform independent business transactions.

4
Why ebXML?
  • Needed a way to unify a variety of existing XML
    specifications.
  • Electronic Data Interchange (EDI) is no longer
    seen as a viable method of conducting e-business.
  • Current specification for e-business transactions
  • Drawbacks
  • High startup costs
  • Inconsistent formats
  • Implementation limited to large organizations
  • ebXMLs Benefits
  • Common message structure enables worldwide
    communication
  • Provided free of charge
  • Scales well to any organization size

5
(No Transcript)
6
ebXML and W. S.
  • "Web Services and ebXML are not competing
    frameworks. They can be viewed as serving two
    different B2B models and will continue to be used
    in parallel.
  • - From the Business-to-Business Frameworks for
    IDA Networks study published in September 2003 by
    the European Commission's IDA (Interchange of
    Data between Administrations) obtained from
    www.ebxml.org
  • ebXML defines new ways to use the existing
    standards
  • SOAP ebXML Messaging Services use SOAP message
    headers and http protocols.
  • UDDI the ebXML Registry mimics and works as a
    sub-directory of the UDDI registry.
  • WSDL ebXML BPSS and CPP give it the
    functionality of WSDL plus error handling and
    failure scenarios.

7
Diagram Key concepts
Requestor
Responder
- ebXML BPSS v1.10 p.9
8
Key Concepts
  • Business Transactions
  • an atomic unit of work in a trading arrangement
    between two business partners. - ebXML BPSS
    v1.10
  • Consists of 2 Roles
  • Requestor the initiator of the transaction.
  • Responder a response is necessary for a legal
    transaction to take place.
  • Ex request catalog, send purchase order
  • Binary Collaboration
  • A set of business transactions between business
    partners.
  • 2 Types
  • Binary Either a business transaction or another
    Binary collaboration (allows for recursion).
  • Multi bundled binary collaborations -
    deprecated in ebXML BPSS v1.1
  • Ex step 1 request catalog, step 2 send
    catalog

9
Key Concepts II
  • Document Flows
  • Defines the nature of a business transaction.
  • 2 Types
  • One-way notification
  • Two-way conversation (allows for contractual
    agreements)
  • Choreography
  • Specifies which transaction should be executing
    at any given time.
  • Describes the ordering and transitions between
    transactions and recursive collaboration
    instances.

10
Business Transactions
  • An event where one or two document flows happen
    between the receiving and responding Business
    Activities.
  • Business Activities should not be thought of as
    buyer or seller roles, but kept vague.
  • Example Business Transaction
  • A Cancel Purchase Order request may be sent out
    by either role in the business transaction.
  • Acknowledgements (Business signals) are used to
    control the content and usage of business
    transactions.

11
Business Transaction Syntax
  • ltBusinessTransaction name"Catalog Request"gt
  • ltRequestingBusinessActivity name"requestCatalog"
  • ltDocumentEnvelope
  • businessDocument"Catalog Request"/gt
  • lt/RequestingBusinessActivitygt
  • ltRespondingBusinessActivity name"sendCatalog"gt
  • ltDocumentEnvelope
  • isPositiveResponse"true"
  • businessDocument"Catalog" /gt
  • lt/RespondingBusinessActivitygt
  • lt/BusinessTransactiongt

12
A More Detailed version
  • ltBusinessTransaction
  • name"Check Credit"
  • nameID"122A3DD33"
  • isGuaranteedDeliveryRequired"true"gt
  • ltRequestingBusinessActivity
  • name"checkCredit"
  • nameID"122A3E833"
  • isAuthorizationRequired"true"
  • isIntelligibleCheckRequired"true"
  • isNonRepudiationReceiptRequired"true"
  • isNonRepudiationRequired"true"
  • timeToAcknowledgeAcceptance" PT30S"
  • timeToAcknowledgeReceipt" PT10S"gt
  • ltDocumentEnvelope
  • isAuthenticated"persistent"
  • isConfidential"persistent"
  • isTamperDetectable"persistent"
  • businessDocument" Credit Request"
  • businessDocumentIDREF"122A3F613C"/gt

13
  • ltRespondingBusinessActivity
  • name"confirmCredit"
  • nameID"122A3E863"
  • isAuthorizationRequired"true"
  • isIntelligibleCheckRequired"true"
  • isNonRepudiationReceiptRequired"true"
  • isNonRepudiationRequired"true"
  • timeToAcknowledgeReceipt"PT10S"gt
  • ltDocumentEnvelope
  • isPositiveResponse"false" isAuthenticated"pe
    rsistent"
  • isConfidential"persistent" isTamperDetectable
    "persistent"
  • businessDocument"Credit Denied"
    businessDocumentIDREF"122A3F8E3"/gt
  • ltDocumentEnvelope
  • isPositiveResponse"true" isAuthenticated"per
    sistent"
  • isConfidential"persistent" isTamperDetectable
    "persistent"
  • businessDocument"Credit Approved"
  • businessDocumentIDREF"122A3F6C3"gt
  • ltAttachment nameCredit Report mimeTypeXML
  • businessDocumentCredit Rating

14
Message Flow in a Business Transaction
Request
receiptAcknowledgement Signal
AcceptanceAcknowledgement Signal
Requesting Activity
Responding Activity
Response
receiptAcknowledgement Signal
AcceptanceAcknowledgement Signal
Signals indicate the current state of the
transaction.
15
Business Document Flow
  • Conceptually modeled as the passing of Document
    Envelopes between the request and response ends
    of a business transaction.
  • Document envelopes carry only one primary
    business document, but may have any number of
    possible documents specified.
  • Example A purchase order request is sent to a
    vendor (envelope from requestor) and the vendor
    replies with one of three predefined document
    envelopes acceptance, denial, or partial
    acceptance .

16
Binary Collaborations
  • Defined to be between 2 roles the initiator and
    the responder.
  • Two types
  • Business transaction activity
  • Collaboration activity a binary collaboration
    executed within another binary collaboration.
  • isInnerCollaboration boolean value that
    specifies whether the activity may be executed by
    itself or only within another collaboration.
  • Allows greater flexibility in defining how
    collaborations take place.
  • Collaboration Protocol Agreements (CPA) govern
    how they take place

17
  • ltBinaryCollaboration
  • name"Firm Order"
  • nameID"122A38D93"
  • initiatingRoleIDREF122A38DA3
  • timeToPerform"P1D"gt
  • ltRole name"buyer" nameID"122A38DA3"/gt
  • ltRole name"seller" nameID"122A38DA5"/gt
  • ltStart
  • toBusinessStatePlace Order
  • toBusinessStateIDREF122A39C23 /gt
  • ltBusinessTransactionActivity
  • name"Place Order" nameID"122A39C23"
  • businessTransaction"Create Order"
    businessTransactionIDREF"122A3DD33"
  • fromRole"buyer fromRoleIDREF"122A38DA3"
  • toRole"seller toRoleIDREF"122A38DA5"
  • isConcurrent"true" isLegallyBinding"false"
  • timeToPerform"P2H"/gt
  • ltFailure
  • fromBusinessState"Place Order"

18
Choreography
  • Purpose to specify which Business Transaction
    Activity and/or Collaboration Activity should
    happen at any point in time. - ebXML BPSS
    v1.10
  • How keeping track of the current business state
    and any transitions between business states.
  • Transitions are used to created the nested
    activities mentioned earlier.
  • Business State examples start, completion, fork,
    join, decision, business transaction activity,
    business collaboration activity.
  • In the UML model, all the examples are
    generalizations of the ltltabstractgtgt business
    state.

19
How BPSS fits into the ebXML Framework
- ebXML BPSS v1.10 p.14
20
Business Transaction Semantics
  • Transactions are set up to provide
  • Predictability Roles, time bounds of signal
    passing, and determination of success or failure
    are all clearly defined.
  • Nonrepudiation
  • Security
  • Reliability
  • Assuming reliable message passing and
    request/response acknowledgements are used.

21
Timeouts
  • Timers are used to govern how long roles should
    wait when engaging in transactions.
  • Timeout values are specified within the business
    transaction XML forms using timetoAcknowledgeAccep
    tance and timetoAchnowledgeReceipt tags.
  • Values take the form
  • P1H one hour
  • P30S 30 seconds
  • All timers start when the initial requesting
    business document is sent. - ebXML BPSS v1.10
  • Problem initial document transport latency will
    cause the timers to start at different times.

22
Business Service Interface (BSI)
  • Responsibilities
  • Detect start of transactions
  • Detect transfer of control within transactions
  • Detect successful transaction completion
  • Detect unsuccessful transactions
  • Timeouts
  • Exceptions to protocol rules
  • Handle negative receipt/authorization signals

23
States of the Business Transaction Protocol
From message flow in a business transaction
diagram
Requesting Activity
Protocol Failure
Protocol Success
Busn. Success
Busn. Failure
Success
Failure
- ebXML v1.1 Figure 16 p.43
24
Show diagram on p. 54 gt 62
25
Nonrepudiation
  • Receipt acknowledgement ensures that both parties
    involved can legally enforce the agreement (the
    legally binding aspect of it has been
    deprecated).
  • Takes two forms
  • 1 (unenforceable)
  • Each party (requestor/responder) is asked to save
    copies of all documents and envelopes involved in
    a transaction.
  • 2 (enforceable)
  • The isNonRepudiationOfReceiptRequired parameter
    is used in every message to make sure the
    receiver (either the requestor or responder)
    acknowledges the message.
  • A lack of response from the receiver will make
    the transaction null.

26
SecurityAuthorization and document integrity may
be enforced through ebXML.
  • Authorization
  • Activated when the following parameter is
    included in a document.
  • isAuthorizationRequired
  • Receiving side of the activity must authorize the
    document by comparing it to a previously supplied
    set of values (by sender).
  • Deprecated in version ebXML BPSS v1.1
  • Document
  • Uses 3 messages with null, transient, or
    persistent values
  • isConfidential
  • isTamperDetectable
  • isAuthenticated
  • Transient security provided through the
    communication channel tests ensure that it was
    not tampered with during transfer.
  • Persistent ensures the information remains
    confidential through the use of encryption.

27
Reliability
  • Documents and signals can be trusted to reach
    their destinations.
  • Parameter isGuaranteedDeliveryRequired forces the
    responding party to choose a communication
    channel where there is a delivery guarantee.
  • Instructs the CPP and CPA on the level of service
    required for this transaction.

28
XML BPSS Example Document Specifications
  • lt?xml version"1.0" encoding"UTF-8"?gt
  • ltProcessSpecification name"Simple" version"1.1"
    nameID"Simple-2434134"
  • xmlns"http//www.untmg.org/downloads/General/appr
    oved/BPSS-v1pt10.xsd"
  • xmlnsxsi"http//www.w3.org/2001/XMLSchema-instan
    ce"
  • xsischemaLocation"http//www.untmg.org/downloads
    /General/approved/BPSS-v1pt10.xsd
  • C\projects\bpss\bpss_1.1\ebBPSS1.08b.xsd"gt
  • lt!-- Business Documents --gt
  • ltBusinessDocument name"CatalogRequestspecificati
    onLocation"http//www.xyx.com/CatalogReq.xsd"/gt
  • ltBusinessDocument name"Catalog"
    specificationLocation"http//www.xyx.com/Catalog.
    xsd"/gt
  • ltBusinessDocument name"Purchase Order"
    specificationLocation"http//www.xyx.com/PO.xsd"/
    gt
  • ltBusinessDocument name"PO Acknowledgement"
  • specificationLocation"http//www.xyx.com/POAck.x
    sd"/gt
  • ltBusinessDocument name"Credit Request"
    specificationLocation"http//www.xyx.com/CreditRe
    q.xsd"/gt
  • ltBusinessDocument name"Credit Confirm"
    specificationLocation"http//www.xyx.com/CreditCo
    n.xsd"/gt
  • ltBusinessDocument name"ASN" specificationLocation
    "http//www.xyx.com/CatalogASN.xsd"/gt
  • ltBusinessDocument name"CreditAdvice"
  • specificationLocation"http//www.xyx.com/CreditA
    dvice.xsd"/gt
  • ltBusinessDocument name"DebitAdvice"
    specificationLocation"http//www.xyx.com/DebitAdv
    ice.xsd"/gt
  • ltBusinessDocument name"Invoice"
    specificationLocation"http//www.xyx.com/Invoice.
    xsd"/gt

29
Business Transaction Specification
  • ltPackage name"Ordering"gt
  • lt!-- Here are some of the Business Transactions
    needed --gt
  • ltBusinessTransaction name"Catalog Request"gt
  • ltRequestingBusinessActivity name"RequestCatalog
    "gt
  • ltDocumentEnvelope businessDocument"Catalog
    Request"/gt
  • lt/RequestingBusinessActivitygt
  • ltRespondingBusinessActivity name"SendCatalog"gt
  • ltDocumentEnvelope isPositiveResponse"true"
    businessDocument"Catalog"/gt
  • lt/RespondingBusinessActivitygt
  • lt/BusinessTransactiongt
  • ltBusinessTransaction name"Create Order"gt
  • ltRequestingBusinessActivity name"SendOrder"
    isNonRepudiationRequired"true"
  • timeToAcknowledgeReceipt"P2D"
    timeToAcknowledgeAcceptance"P3D"gt
  • ltDocumentEnvelope businessDocument"Purchase
    Order"/gt
  • lt/RequestingBusinessActivitygt
  • ltRespondingBusinessActivity name"SendPOAcknowle
    dgement"
  • isNonRepudiationRequired"true"
    timeToAcknowledgeReceipt"P5D"gt
  • ltDocumentEnvelope isPositiveResponse"true"
  • businessDocument"PO Acknowledgement"/gt

30
Binary Collaboration Specification
  • lt!-- Now one of the Binary Collaborations --gt
  • ltBinaryCollaboration name"Request Catalog"
    initiatingRoleID"1122B1"gt
  • ltRole name"requestor" nameID"1122B1"/gt
  • ltRole name"provider" nameID"2211A1"/gt
  • ltStart toBusinessState"Catalog Request"/gt
  • ltBusinessTransactionActivity name"Catalog
    Request" businessTransaction"Catalog Request"
  • fromRole"requestor" toRole"provider"/gt
  • ltSuccess fromBusinessState"Catalog Request"
    conditionGuard"Success"/gt
  • ltFailure fromBusinessState"Catalog Request"
    conditionGuard"Failure"/gt
  • lt/BinaryCollaborationgt

31
Compound Binary Collaboration
  • lt!-- A compound Binary Collaboration for
    illustration purposes--gt
  • ltBinaryCollaboration name"Credit Charge"
    initiatingRoleID"8132B1"gt
  • ltRole name"charger" nameID"8132B1"/gt
  • ltRole name"credit service" nameID"8122B1"/gt
  • ltRole namepayor" nameID"7122B1"/gt
  • ltStart toBusinessState"Credit Inquiry"/gt
  • ltCollaborationActivity name"Credit Inquiry"
    binaryCollaboration"Credit Inquiry"
  • fromRole"charger" toRole"credit service"/gt
  • ltCollaborationActivity name"Credit Payment"
    binaryCollaboration"Credit Payment"
  • fromRole"charger" toRole"payor"/gt
  • ltSuccess fromBusinessState"Credit Payment"
    conditionGuard"Success"/gt
  • ltFailure fromBusinessState"Credit Payment"
    conditionGuard"Failure"/gt
  • ltTransition fromBusinessState"Credit Inquiry"
    toBusinessState"Credit Payment"/gt
  • lt/BinaryCollaborationgt

32
Multiparty Collaboration (deprecated)
  • lt!-- First the overall MultiParty Collaboration
    --gt
  • ltMultiPartyCollaboration name"DropShip"gt
  • ltBusinessPartnerRole name"Customer"gt
  • ltPerforms role"requestor" roleIDREF"1122B1"/gt
  • ltPerforms role"buyer" roleIDREF"1122B2"/gt
  • ltTransition fromBusinessState"Catalog Request"
    toBusinessState"Create Order"/gt
  • lt/BusinessPartnerRolegt
  • ltBusinessPartnerRole name"Retailer"gt
  • ltPerforms role"provider" roleIDREF"2211A1"/gt
  • ltPerforms role"seller" roleIDREF"1122B3"/gt
  • ltPerforms role"creditor" roleIDREF"9122B1"/gt
  • ltPerforms role"buyer" roleIDREF"1122B2"/gt
  • ltPerforms role"payee" roleIDREF"6122B1"/gt
  • ltPerforms role"payor" roleIDREF"7122B1"/gt
  • ltPerforms role"requestor" roleIDREF"1122B1"/gt
  • ltTransition fromBusinessState"Create Order"
    toBusinessState"Check Credit"/gt
  • ltTransition fromBusinessState"Check Credit"
    toBusinessState"Credit Payment"/gt
  • lt/BusinessPartnerRolegt
  • ltBusinessPartnerRole name"DropShip Vendor"gt

33
Sources
  • EbXML committee
  • www.ebxml.org
  • Oasis
  • www.oasis-open.org
  • UN/CEFACT
  • www.unece.org/cefact
About PowerShow.com