ebxml overview cory casanave data access technologies [email protected] (305)...

ebXML Overview

Cory CasanaveData Access Technologies

[email protected]

(305) 234-7077

Copyright © 2001-2002, Data Access Technologies, Inc.

The Internet Computing Model

Collaboration of independent entities

Document exchange over internet technologies Large grain interactions

No required infrastructure * Long lived business

processes Business transactions

BusinessParty

BusinessParty

Portals


Requirements for the “ICM”

Contract of Collaboration Shared business semantics Meta-Model

(EDOC-ECA/BPSS) and representation (I.E. XMI, ebXML-BPSS)

Shared Repository for Contracts (MOF, UDDI, ebXML)

Connectivity (middleware) which meets requirements of the contract

Implementation of each contract role providing connectivity (application server)

BusinessPartner

BusinessPartner

Repository

Contracts(Metadata)

Contract of collaboration can be mapped to the format of various technologies. (ebXML, Soap, .NET)

Instance Data


Two levels of interoperability

Instance data interoperability

Metadata (contract) interoperability

BusinessPartner

BusinessPartner

BPSS

ebXML

Over Soap

CollaborationPartnerProfile

CollaborationPartnerProfile

CollaborationProtocol

AgreementRepository Repository


Parts of ebXML Specification

Requirements (RE)Technical Architecture (TA)Business Process Specification Schema

(BPSS)Collaboration protocol profile & agreement

(CCP)Message Service (MS)Registry Information Model (RI)Glossasry (Gloss)


ebXML Architecture

BPSpecification

Business Process

Core Data Blocks

Business TransactionsContext For Built With

Implement one Partner Role Implement other

Partner Roles

Register

Design time Design time

CPP CPP

Transport

Package

Business Service

Interface

Internal Business App

Internal Business App

Business Service

Interface

Runtime

CPA


Summary of ebXML terms

BPSS Business Process Schema Specification – Meta model in XML (A

Choreographed set of business transactions between partners) UMM

UN/CEFACT Methodology & UML profile for EDI specification Core Components

Common data structures for message interchange in a context CPP

Collaboration Partner Profile – Lists partner processes & technologies CPA

Collaboration Protocol Agreement – Runtime partner binding Reg-Rep

Registry & Repository – Storage for metadata and partners TRP

Transport Routing & Packaging – Wire protocol


Political Split

Oasis CPP CPA Reg-Rep TRP

UN/CEFACT BPSS Core Components UMM

Standards for Global Internet Computing

UML4EDOCUML4EDOCUML4EDOCUML4EDOCSOAP

WSDL

XML

XML-Schema.NET BPML


XML Standards

XML Schema & DTD Description and packaging of data

Soap Basic messaging and packaging Extensions for Soap-RPC with WSDL May be extended to support

collaborative messaging


ebXML Added Value

Specification of business process and data for collaboration

Link between BPSS, Repository and Transport

Choreography of async servicesTiming and security parametersPackaging of complex MIME packagesLong lived process identityWhen web services need to be more than a

simple request/reply


ebXML & EDOC

Transport

Distribution

Repository

Runtime

EnterpriseIntegration

Components

InformationModel

MDA

Collaboration

Process Model

ebXML EDOC


Standards for collaboration

EDOC-ECA ebXML-BPSS

Business Collaborations Yes – Community Process Yes – Multi Party Collaboration

Contract of Interaction Yes – Protocol with Choreography & Object Interface

Yes – Binary Collaboration with Choreography and Business Transactions

Content Model Yes – Document Model Uses external forms, such as XML Schema

Recursive Composition Yes – Recursive Composition into Enterprise

No – Only “B2B”

Detail sufficient to drive communications

No – Requires technology mapping Yes – As ebXML transport. BPSS includes timing and security parameters.

Computing Models Supported

Internet document exchange, entities, business processes, objects and events

Internet document exchange

The model driven architecture for web services and collaborative internet computing


EDOC Solution Triad

Service BasedArchitecture

Standards

Tooling & Infrastructure

Development Process

Components

Model DrivenArchitecture


Two levels of interoperability

Instance data and interoperability

Metadata (contract) interoperability

BusinessPartner

BusinessPartner Bridge

Each can be transformed

PurchasingModel

.NETebXMLBPSS

ebXML Biztalk

Normal Form

Over Soap Over Soap


EDOC as the normal form

EDOC-UML

Web Services(WSDL)

ebXML(BPSS)

J2EE(Java RMI)

Corba(IDL/CDL)

MOM(FCM)

The standard way to model and tool for multiple

technologies

MDAMappings


EDOC and WSDL

Both define document interactions across ports An async EDOC protocol requires a pair of WSDL ports WSDL adds connection and endpoint detail EDOC choreography specifies how multiple WSDL

interactions will work together EDOC provides a way to model the component behind

a set of services EDOC shows how service components can be

composed of other service components EDOC integrates with the information model, events

and workflow WSDL is appropriate as an EDOC technology mapping


EDOC and J2EE – JSR 159

Title: Java Process Component API (JPC) . The goal of [JSR 159] is to provide J2EE developers with the ability to

compose an application out of service level components (where service in this context means a loosely coupled, event based process). Today, J2EE developers build applications that implement a service; however, there is no formal way to describe the full semantics of a service to the J2EE container. There is no formal concept of a service as a J2EE component nor is there a formal concept of service composition.

For some time, the computing industry has struggled to find a component abstraction that balanced the need for type safety with the need for loosely coupled, event based composition. The most recent and most promising solution to this problem is the EDOC Component Collaboration Architecture. In addition to standing alone as a service component architecture, CCA is closely related to the WSDL model for web services. Both are loosely coupled, port based models of service integration; however, the CCA goes much further to explicitly define a rich collaboration model. Their similarities make it practical to view WSDL as a web service

adjunct to CCA rather than a different, competing technology.

From the enterprise to technology viewpoints

EDOC collaborations as the basis of multiple viewpoints


The Connected EnterpriseContent and Communication

AerialPhotos

DigitalMap

CensusData

HouseDrawings

PoliceRecords

PoliceDispatcher

Role


Multiple roles in a collaboration


Implementation

Net

Hardware

OperatingSystem

Framework,Middleware& Container

Roles to Systems

WEB SERVICE!

Component in Role

Interaction(With Information)

Role

Collaboration

Vision

Building and adapting systems for collaboration, reuse and change


Loosely coupled enterprise architecture

OpenStandards

OpenStandards

Ope

n

Stand

ards

Independent enterprise components

Representing business concepts

Link via open standards


OMG Model Driven Architecture (MDA)

High level – platform independent models

Technology Models Mapping

Custom Standard

Standard Models produce technology specific standards artifacts


What some infrastructurevendors would

have you do

Technology Independence

BusinessLogic

ComponentebXml

BusinessLogic

Component.NET

BusinessLogic

ComponentRosetaNet

BusinessLogic

ComponentEjb

Adapters

EJB

BusinessLogic

Component

ebXml

BizTalk

Rosetanet

Adapters

CICS

EJB

MQ

Corba


Automated MDA

ProfileProfile(E.G. EDOC)(E.G. EDOC)

Framework &Framework &InfrastructureInfrastructure

(E.G. XML)(E.G. XML)

InfrastructureInfrastructureMappingMapping

(E.G. XML)(E.G. XML)

Mapping is tunedMapping is tunedto the infrastructureto the infrastructure

ToolsToolsProduce &Produce &IntegrateIntegrate

EnterpriseEnterpriseComponentsComponents

UMLUMLDesignDesign


High level tooling & infrastructure

MUST BE SIMPLE! We must be able to create better applications

faster We must separate the technology and business

concerns, enable the userTooling + Infrastructure

Executable models are source code Tooling must be technology aware Infrastructure must support tooling, not manual

techniquesModel based component architectures


High level tooling & infrastructure

MUST BE SIMPLE! We must be able to create better applications

faster We must separate the technology and business

concerns, enable the user

Tooling + Infrastructure Executable models are source code aTooling must be technology aware Infrastructure must support tooling

Model based component architectures

Executable Models


Iterative Development

Build Build Build Build BuildRelease

Build Deploy

BusinessModelDesign

InfrastructureDevelopment

Automation


Business Component Marketplace

The business component marketplace is projected to be a 10b market in 5 years

Consider the value of XML components that wrap popular legacy

New application functionality built from components Components for integration and transformation XML and web services makes an excellent basis for

such components Technology components, such as for repositories and

DBMS Marketplace my be inside the enterprise or

commercial


Net effect

Using these open standards and automated techniques we can; Achieve the strategic advantage of an open

and flexible enterprise Produce and/or integrate these systems

FASTER and CHEAPER than could be done with legacy techniques

Provide a lasting asset that will outlive the technology of the day


Role of the OMG

While web services have huge potential but the enterprise needs to see how to bring these technologies together to solve business problems

The OMG can bring business focus and unification to web services by applying Model Driven Architecture (MDA); Bridging technologies Unifying tools Automating the development process

We have just adopted EDOC for this vary purpose


Discussion


Contact

Cory Casanave

Data Access Technologies

www.enterprise-component.com

[email protected]

(305) 234-7077

ebxml overview cory casanave data access technologies [email protected] (305)...

Documents

net instance data slide

partner roles

bpml slide

format of various technologies

collaborative messaging

ebxmlbpss yshared repository

ebxml zconnectivity

contract role