Electronic Business eXtensible Markup Dialect - Business Process Determination Construction (ebXML-BPSS)

1837 days ago, 698 views
PowerPoint PPT Presentation
From the Business-to-Business Frameworks for IDA Networks study distributed in ... Record envelopes convey one and only essential business archive, however may have any ...

Presentation Transcript

Slide 1

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

Slide 2

Outline: Introduction Key Concepts Business Transaction Semantics XML BPSS Example

Slide 3

What is ebXML? An arrangement of details that upgrade e-business exercises by permitting business prepare joint efforts between at least 2 parties. Begun in 1999 as a joint exertion between UN/CEFACT and Oasis – A worldwide consortium that attempts to create and execute e-business models. UN/CEFACT – United Nations Center for Trade Facilitation and Electronic Business Goal: make determinations to permit overall stage free business exchanges.

Slide 4

Why ebXML? Required an approach to bind together an assortment of existing XML particulars. Electronic Data Interchange (EDI) is no longer observed as a suitable technique for conveying e-business. Current particular for e-business exchanges Drawbacks: High startup costs Inconsistent configurations Implementation constrained to substantial associations ebXML's Benefits: Common message structure empowers overall correspondence Provided for nothing out of pocket Scales well to any association estimate

Slide 6

ebXML and W. S. "Web Services and ebXML are not contending structures. They can be seen as serving two diverse B2B models and will keep on being utilized as a part of parallel." -From the Business-to-Business Frameworks for IDA Networks examine distributed in September 2003 by the European Commission's IDA (Interchange of Data between Administrations) [obtained from www.ebxml.org] ebXML characterizes better approaches to utilize the current principles: SOAP – ebXML Messaging Services utilize SOAP message headers and http conventions. UDDI – the ebXML Registry mirrors and functions as a sub-catalog of the UDDI registry. WSDL – ebXML BPSS and CPP give it the usefulness of WSDL in addition to mistake taking care of and disappointment situations.

Slide 7

Diagram: Key ideas Requestor Responder - ebXML BPSS v1.10 p.9

Slide 8

Business Transactions: "a nuclear unit of work in an exchanging course of action between two business accomplices." - ebXML BPSS v1.10 Consists of 2 Roles: Requestor – the initiator of the exchange. Responder – a reaction is important for a "legitimate" exchange to occur. Ex: ask for list, send buy arrange… Binary Collaboration: An arrangement of business exchanges between business accomplices. 2 Types: Binary – Either a business exchange or another Binary joint effort (considers recursion). Multi – packaged parallel coordinated efforts - belittled in ebXML BPSS v1.1 Ex: step 1 = ask for list, step 2 = send list Key Concepts:

Slide 9

Document Flows: Defines the way of a business exchange. 2 Types: One-way = notice Two-way = discussion (considers legally binding understandings) Choreography: Specifies which exchange ought to execute at any given time. Portrays the requesting and moves amongst exchanges and recursive joint effort occasions. Key Concepts II:

Slide 10

Business Transactions An occasion where maybe a couple report streams happen between the accepting and reacting Business Activities. Business Activities ought not be considered as "purchaser" or "dealer" parts, yet kept ambiguous. Case Business Transaction: A "Scratch off Purchase Order" ask for might be conveyed by either part in the business exchange. Affirmations (Business signs) are utilized to control the substance and use of business exchanges.

Slide 11

Business Transaction Syntax <BusinessTransaction name="Catalog Request"> <RequestingBusinessActivity name="requestCatalog" <DocumentEnvelope businessDocument="Catalog Request"/> </RequestingBusinessActivity> <RespondingBusinessActivity name="sendCatalog"> <DocumentEnvelope isPositiveResponse="true" businessDocument="Catalog"/> </RespondingBusinessActivity> </BusinessTransaction>

Slide 12

A More Detailed form: <BusinessTransaction name="Check Credit" nameID="122A3DD33" isGuaranteedDeliveryRequired="true"> <RequestingBusinessActivity name="checkCredit" nameID="122A3E833" isAuthorizationRequired="true" isIntelligibleCheckRequired="true" isNonRepudiationReceiptRequired="true" isNonRepudiationRequired="true" timeToAcknowledgeAcceptance=" PT30S" timeToAcknowledgeReceipt=" PT10S"> <DocumentEnvelope isAuthenticated="persistent" isConfidential="persistent" isTamperDetectable="persistent" businessDocument=" Credit Request" businessDocumentIDREF="122A3F613C"/> </RequestingBusinessActivity>

Slide 13

<RespondingBusinessActivity name="confirmCredit" nameID="122A3E863" isAuthorizationRequired="true" isIntelligibleCheckRequired="true" isNonRepudiationReceiptRequired="true" isNonRepudiationRequired="true" timeToAcknowledgeReceipt="PT10S"> <DocumentEnvelope isPositiveResponse="false" isAuthenticated="persistent" isConfidential="persistent" isTamperDetectable="persistent" businessDocument="Credit Denied" businessDocumentIDREF="122A3F8E3"/> <DocumentEnvelope isPositiveResponse="true" isAuthenticated="persistent" isConfidential="persistent" isTamperDetectable="persistent" businessDocument="Credit Approved" businessDocumentIDREF="122A3F6C3"> <Attachment name="Credit Report" mimeType="XML" businessDocument="Credit Rating" businessDocumentIDREF="122A3F8E4" isConfidential="none" isTamperDetectable="none" isAuthenticated="none"> </Attachment> </DocumentEnvelope> </RespondingBusinessActivity> </BusinessTransaction>

Slide 14

Message Flow in a Business Transaction Request receiptAcknowledgement Signal AcceptanceAcknowledgement Signal Requesting Activity Responding Activity Response receiptAcknowledgement Signal AcceptanceAcknowledgement Signal Signals show the present condition of the exchange.

Slide 15

Business Document Flow Conceptually displayed as the death of Document Envelopes between the demand and reaction finishes of a business exchange. Archive envelopes convey stand out essential business report, however may have any number of conceivable records indicated. Case: A buy arrange demand is sent to a merchant (envelope from requestor) and the seller answers with one of three predefined record envelopes: acknowledgment, refusal, or fractional acknowledgment .

Slide 16

Binary Collaborations Defined to be between 2 parts: the initiator and the responder. Two sorts: Business exchange movement Collaboration action – a paired joint effort executed inside another double coordinated effort. isInnerCollaboration : boolean esteem that indicates whether the action might be executed independent from anyone else or just inside another joint effort. Permits more noteworthy adaptability in characterizing how coordinated efforts occur. Joint effort Protocol Agreements (CPA) represent how they occur

Slide 17

<BinaryCollaboration name="Firm Order" nameID="122A38D93" initiatingRoleIDREF="122A38DA3" timeToPerform="P1D"> <Role name="buyer" nameID="122A38DA3"/> <Role name="seller" nameID="122A38DA5"/> <Start toBusinessState="Place Order" toBusinessStateIDREF="122A39C23"/> <BusinessTransactionActivity name="Place Order" nameID="122A39C23" businessTransaction="Create Order" businessTransactionIDREF="122A3DD33" fromRole="buyer" fromRoleIDREF="122A38DA3" toRole="seller" toRoleIDREF="122A38DA5" isConcurrent="true" isLegallyBinding="false" timeToPerform="P2H"/> <Failure fromBusinessState="Place Order" fromBusinessStateIDREF="122A39C23" conditionGuard="AnyProtocolFailure"/> <Success fromBusinessState="Place Order" fromBusinessStateIDREF="122A39C23" conditionGuard="BusinessSuccess | BusinessFailure"/> </BinaryCollaboration>

Slide 18

Choreography Purpose: "to determine which Business Transaction Activity and additionally Collaboration Activity ought to happen anytime." - ebXML BPSS v1.10 How: monitoring the present business state and any moves between business states. Moves are utilized to made the settled exercises specified before. Business State illustrations: begin, finishing, fork, join, choice, business exchange movement, business joint effort action. In the UML demonstrate, every one of the illustrations are speculations of the <<abstract>> business state.

Slide 19

How BPSS fits into the ebXML Framework - ebXML BPSS v1.10 p.14

Slide 20

Business Transaction Semantics Transactions are set up to provide*: Predictability – Roles, time limits of flag passing, and assurance of achievement or disappointment are all unmistakably characterized. Nonrepudiation Security Reliability *Assuming dependable message passing and demand/reaction affirmations are utilized.

Slide 21

Timeouts Timers are utilized to administer to what extent parts ought to hold up when taking part in exchanges. Timeout qualities are determined inside the business exchange XML frames utilizing timetoAcknowledgeAcceptance and timetoAchnowledgeReceipt labels. Values take the frame: P1H – one hour P30S – 30 seconds "All clocks begin when the underlying requ