OMG - EDOC Enterprise Distributed Object Computing Bringing together business goals, standards, processes and technologies for the e-enabled enterprise

Integrating Enterprises, People & Systems - Worldwide Enabling e Using Internet Technologies

Integrating Enterprises, People & Systems - Worldwide Business Requirements Virtual Enterprises Enterprise Integration (EAI) Supply-chain automation (B2B) Customer Integration (B2B) Web deployment (B2C) Internet Marketplace (B2C) Collaboration and Integration

The dynamic reality The information system must facilitate; Rapid realization of business goals Integration of independent processes and systems Multiple and Changing business requirements business processes technologies standards enterprise boundaries partners

The e-enabled enterprise Has a competitive advantage in its capability to embrace collaboration and change

Embracing collaboration and change We need to extract the meat from the buzzwords And figure out how these concepts fit together To e-enable the enterprise Web Services Messaging & Events Model Driven Architecture EAI Open Collaborative Enterprise Components Middleware Repositories Shared Data Metadata Workflow

Business & Technology Coupling “Open B2B” Ad-hoc business Collaborative Components EDOC Model (UML) Internet Computing Model ebXML Soap “Community B2B” - Business Partners & Independent Divisions Traditional EDI Events & Messaging JMS MQ-Series Synchronous Transactional RPC Corba EJB Integration within a managed domain Shared Data SQL IMS-DB Integration or production of an application

The role of open systems in the enterprise Supporting open distributed computing while meeting local requirements

Enterprise boundaries are not static! The “open domain” “The Enterprise” Independent domains collaborating via open standards No assumption of “the same thing” on both sides! Appropriate inside and outside the enterprise (EI & B2B) Requires business (process collaboration and information) and technical (middleware) standards The open domain needs a point of ownership in the enterprise The Enterprise Enterprise boundaries are not static!

The Internet Computing Model Portals Business Party Business Party Collaboration of independent entities Document exchange over internet technologies Large grain interactions No required infrastructure * Long lived business processes Business transactions

Requirements for the “ICM” Contract of Collaboration Shared business semantics Meta-Model (EDOC-ECA) 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) Business Partner Business Partner Instance Data Repository Contracts (Metadata) Contract of collaboration can be mapped to the format of various technologies. (ebXML, Soap, .NET)

Two levels of interoperability Instance data and interoperability Business Partner Business Partner Biztalk ebXML Bridge Over Soap Over Soap Metadata (contract) interoperability .NET ebXML BPSS Purchasing Model Normal Form Each can be transformed

Drilling down – inside a role The open domain should make no assumptions about the “inside” of a role. Inside one role you frequently find more collaborating “parts” of the enterprise - the same model may be used Until you get to system inside a managed domain Shared resources (DBMS) Common Management Frequently a legacy system Inner Role Legacy Inner Role Domain Inner Role Cust

Collaborative Business Semantics Defined: The processes, information and contracts of interaction between collaborators within a community Collaborative business semantics are a valuable long-term asset Captures information and process Requires ownership and support in the open domain Do not put this valuable asset in a (transient - one size fits all) technology specific form Use technology independent models (MDA) Map to the technology of the day (E.G. DTD)

Required support for the open domain Connectivity standards and infrastructure Providing the enterprise “bus” (Intranet) http, Soap, ebXML Common processes and lexicon What goes on the bus - the real business value! Facilitating communities of practice Meta-model standards (UML, ebXML-BPSS, EDOC...) How to represent shared processes and information Repositories Finding services, models and components for design time and runtime integration

Standards for Global Internet Computing XML WSDL UML4EDOC SOAP .NET BPML XML-Schema

XML Standards XML Schema & DTD Soap Description and packaging of data Basic messaging and packaging Extensions for Soap-RPC with WSDL May be extended to support collaborative messaging

Vision EDOC (a UML Profile) ebXML Provide an architecture for open collaborative computing Simplify the development of component based distributed systems by means of a modelling framework, based on UML 1.4 Provide a platform independent, recursive collaboration based modelling approach supporting multiple technologies. Embrace Model Driven Architectures (MDA) – Provide design and infrastructure models and mapping ebXML Creating a single global electronic market Includes process specification, transport and repositories

ebXML & EDOC ebXML EDOC Collaboration Process Model Enterprise Integration Components Information Model MDA Transport Distribution Repository Runtime Collaboration Process Model

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

Parts of EDOC Enterprise Collaboration Architecture (PIM) Component Collaboration Architecture Business Process Specification Entities Business Events Patterns Technology Mapping (PSM – in progress) Flow Composition Model (Messaging) EJB & Corba Components ebXML .NET Others… MAPPING – Precise models are are source code

Enterprise Architecture Supply Chain Enterprise Components EAI Applications & B2B E-Commerce SQL DBMS, Client/Server & Legacy Applications XML Corba EJB .NET Events Web Browser Client Applications HTTP Web Server Applications 15

Parts of ebXML Business Process Specification (Like EDOC-CCA) XML Representation of business process Core Components Business Data Types & documents based on context Collaboration Protocol Profile What business partners implement what business processes using what technologies One-One agreement for doing business Transport Routing & Packaging Messaging Built on Soap Registry & Repository Finding business partners, document and process specifications

ebXML Architecture Designtime Runtime BP Specification Business Process Core Data Blocks Business Messages CPA Context For Built With Implement one Partner Role Implement other Partner Roles Register Designtime CPP Business Service Interface Business Service Interface Transport Package Internal Business App Internal Business App Runtime

Summary of points thus far We must enable the emerging Internet Computing Model Loosely coupled roles exchanging documents based on a contract of collaboration Web need interoperability at two levels Messaging for the data Metadata for the contract of collaboration, stored in repositories This model of collaborating roles is recursive, extending into the enterprise, into managed domains and into applications Inside the enterprise we want to include resources entities, business events and business processes Supporting the open domain has some required parts and can be augmented with a “treasure chest” of tools and infrastructure Between EDOC & ebXML we are covering B2B and intra enterprise

EDOC Component Collaboration Architecture The model of collaborative work CCA

The Marketplace Example Order Conformation Shipped Process Complete Mechanics Are Us Buyer Acme Industries Seller Status Ship Req Physical Delivery Shipped Delivered GetItThere Freight Shipper

The Seller’s Detail Event Order Processing Shipping Receivables Order Conformation Shipped Shipping Event Ship Req Receivables Shipped Delivered

Parts of a CCA Specification Structure of process components and protocols Process components, ports, protocols and documents Class Diagram or CCA Notation Composition of process components How components are used to specify components Collaboration diagram or CCA Notation Choreography Ordering of flows and protocols in and between process components Activity Diagram

The Community Process Identify a “community process”, the roles and interactions Protocol

Protocols

Composition

The model of things Data Inside a “shared domain” ECA Entity Profile The model of things Data Inside a “shared domain”

Adding Entities Entities are added to manage entity data Entity Roles are managers that provides a view of the same identity in another context The Entities have ports for managing and accessing the entities Non-entities which are owned by (aggregate into) an entity are managed by the entity

ECA Business Events The model of when… Loosely coupled integration within the enterprise and with “aligned” business partners

Event Based Business Processes Rules Business Rules Event Notification Business Process Business Process Business Actions Business Events Business Events Business Actions Business Entity Business Entity

Point to point Event Notification App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions Event Notifications App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions

Pub/Sub Event Notification App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions Pub/Sub App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions

Event Example

Building and adapting systems for collaboration, reuse and change Vision Building and adapting systems for collaboration, reuse and change

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

OMG Model Driven Architecture (MDA) High level – platform independent models Technology Models Mapping Custom Standard Standard Models produce technology specific standards artifacts

Automated MDA Manual Coding Enterprise Components UML Design Tools Profile (E.G. EDOC) UML Design Manual Coding Enterprise Components Infrastructure Mapping (E.G. XML) Tools Produce & Integrate Framework & Infrastructure (E.G. XML) Mapping is tuned to the infrastructure

Technology Independence Business Logic Component ebXml Business Logic Component BizTalk Business Logic Component RosetaNet Business Logic Component Ejb Adapters EJB Business Logic Component ebXml BizTalk Rosetanet CICS MQ Corba

Iterative Development Business Model Design Deploy Release Build Automation Build Build Build Build Build Infrastructure Development

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 Tooling must be technology aware Infrastructure must support tooling, not manual techniques Model 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

Net effect Using these open standards and automated techniques we can; Achieve the strategic advantage of an open and flexible enterpise 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

Typical Requirement Buyer Seller Web Page B2B Seller Buyer HTML Web Service Seller

Multi-tier implementation Web Service B2B Buyer Seller Buyer Web Page HTML Proxy Could have multiple implementations using different technologies Could have multiple implementations using different technologies

Multi-tier implementation Web Service B2B Buyer Seller Buyer Web Page HTML Proxy Event Cloud Event Event Legacy Seller Applications Implementing seller using events

Model Driven Architecture Automating Design To execution

MDA Overview Use high level UML models made precise with profiles With technology specific mappings To produce substantial parts of the executable system

Models and mapping Specification Implementation Solution Provisioning BXS Business Model Platform Independent Model Platform-specific artifacts (IDL/DTD) map UML/CORBA UML/EJB XML OAG SOAP ebXml RosettaNet Legacy Versioned repository Management Over Time

Model to Deployed Artifacts overrides source Platform-specific Process steps artifacts Map object compile module Supplier-Specific artifacts package Automated platform-specific process application Process control parameters assemble Configure map Select Tools Locate Resources runtime deploy

Generated Artifacts Artifact generation involves multiple tools Implementation Artifacts (EJB Examples) Class Objects Jars,Wars,Ears Java Source Homes, SQL Stubs, Skeletons, Managers, Helpers, Holders, Primary Keys Interfaces Descriptors BeanInfo ,Editors. Documentation Serialization, . Persistence Management M0/M1 XMI/DTD Business Object Implementation Logic Artifact generation involves multiple tools EJB Container provider;Deployment tools;Packagers; java development tools(IDE);persistence provider;… Typical 10-20 per PIM Classifier 0-20% manual override

Reverse Engineering model disposition navigation algorithms PIM Native artifacts model navigation Production rule engine disposition process Native meta-model is platform-specific XML DTD/Schema; java introspection; SQL tables; legacy model; etc. Map navigates the native meta-model, populates PIM Limited semantic recovery Information and middleware models work best

MDA and Components Specification Implementation Solution Provisioning BXS Business Model Platform Independent Model Components Direct Execution

Summary of MDA benefits Isolates domain specifications from platform details Reduces complexity Preserves domain model semantics Increases stability and lifetime Generates to platform/legacy of choice Decreased development time fast iterative development separation between the engineering and business requirements Increased quality. Builds on industry directions Users Domain Specifications MDA