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 Copyright © 2001, Data Access Technologies, Inc.
Integrating Enterprises, People & Systems - Worldwide z Business Requirements y. Virtual Enterprises y. Enterprise Integration (EAI) y. Supply-chain automation (B 2 B) y. Customer Integration (B 2 B) y. Web deployment (B 2 C) y. Internet Marketplace (B 2 C) z Collaboration and Integration Copyright © 2001, Data Access Technologies, Inc.
The dynamic reality z The information system must facilitate; y. Rapid realization of business goals y. Integration of independent processes and systems y. Multiple and Changing xbusiness requirements xbusiness processes xtechnologies xstandards xenterprise boundaries xpartners Copyright © 2001, Data Access Technologies, Inc.
The e-enabled enterprise Has a competitive advantage in its capability to embrace collaboration and change
Embracing collaboration and change z We need to extract the meat from the buzzwords z And figure out how these concepts fit together z To e-enable the enterprise Copyright © 2001, Data Access Technologies, Inc. Web Services Messaging & Events Model Driven Architecture EAI Open Components Middleware Collaborative Enterprise Repositories Metadata Shared Data Workflow
Business & Technology Coupling “Open B 2 B” Ad-hoc business “Community B 2 B” Business Partners & Independent Divisions Internet Collaborative Computing Components Model Integration within a managed domain Integration or production of an application Copyright © 2001, Data Access Technologies, Inc. EDOC Model (UML) eb. XML Soap Traditional EDI Events & Messaging Synchronous JMS MQ-Series Transactional RPC Corba EJB Shared Data SQL IMS-DB
The role of open systems in the enterprise Supporting open distributed computing while meeting local requirements
The “open domain” z Independent domains collaborating via open standards z No assumption of “the same thing” on both sides! z Appropriate inside and outside the enterprise (EI & B 2 B) z Requires business (process collaboration and information) and technical (middleware) standards z The open domain needs a point of ownership in the enterprise Copyright © 2001, Data Access Technologies, Inc. The Enterprise “The Enterprise” Enterprise boundaries are not static!
The Internet Computing Model Portals Business Party z Collaboration of independent entities z Document exchange over internet technologies y Large grain interactions z No required infrastructure * z Long lived business processes z Business transactions Copyright © 2001, Data Access Technologies, Inc.
Requirements for the “ICM” z Contract of Collaboration y Shared business semantics y Meta-Model (EDOC-ECA) and representation (I. E. XMI, eb. XML-BPSS) y Shared Repository for Contracts (MOF, UDDI, eb. XML) z Connectivity (middleware) which meets requirements of the contract z Implementation of each contract role providing connectivity (application server) Copyright © 2001, Data Access Technologies, Inc. Business Partner Instance Data Business Partner Repository Contracts (Metadata) Contract of collaboration can be mapped to the format of various technologies. (eb. XML, Soap, . NET)
Two levels of interoperability Instance data and interoperability Biztalk eb. XML Business Partner Over Soap Bridge Business Partner Over Soap Metadata (contract) interoperability eb. XML BPSS Purchasing Model Normal Form Each can be transformed Copyright © 2001, Data Access Technologies, Inc. . NET
Drilling down – inside a role z The open domain should make no assumptions about the “inside” of a role. z Inside one role you frequently find more collaborating “parts” of the enterprise - the same model may be used z Until you get to system inside a managed domain y Shared resources (DBMS) y Common Management y Frequently a legacy system Copyright © 2001, Data Access Technologies, Inc. Inner Role Legacy Inner Role Domain Cust Inner Role
Collaborative Business Semantics z Defined: The processes, information and contracts of interaction between collaborators within a community z Collaborative business semantics are a valuable longterm asset z Captures information and process z Requires ownership and support in the open domain z Do not put this valuable asset in a (transient - one size fits all) technology specific form y Use technology independent models (MDA) y Map to the technology of the day (E. G. DTD) Copyright © 2001, Data Access Technologies, Inc.
Required support for the open domain z Connectivity standards and infrastructure y Providing the enterprise “bus” (Intranet) y http, Soap, eb. XML z Common processes and lexicon y What goes on the bus - the real business value! y Facilitating communities of practice z Meta-model standards (UML, eb. XML-BPSS, EDOC. . . ) y How to represent shared processes and information z Repositories y Finding services, models and components for design time and runtime integration Copyright © 2001, Data Access Technologies, Inc.
Standards for Global Internet Computing XML UML 4 EDOC. NET BPML WSDL SOAP XML-Schema
XML Standards z. XML Schema & DTD y. Description and packaging of data z. Soap y. Basic messaging and packaging y. Extensions for Soap-RPC with WSDL y. May be extended to support collaborative messaging Copyright © 2001, Data Access Technologies, Inc.
Vision z EDOC (a UML Profile) y Provide an architecture for open collaborative computing y Simplify the development of component based distributed systems by means of a modelling framework, based on UML 1. 4 y Provide a platform independent, recursive collaboration based modelling approach supporting multiple technologies. y Embrace Model Driven Architectures (MDA) – Provide design and infrastructure models and mapping z eb. XML y Creating a single global electronic market x. Includes process specification, transport and repositories Copyright © 2001, Data Access Technologies, Inc.
eb. XML & EDOC eb. XML EDOC Enterprise Integration Transport Distribution Collaboration Repository Process Model Runtime Components Information Model MDA Copyright © 2001, Data Access Technologies, Inc.
Standards for collaboration EDOC-ECA eb. XML-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 “B 2 B” Detail sufficient to drive communications No – Requires technology mapping Yes – As eb. XML transport. BPSS includes timing and security parameters. Computing Models Supported Internet document exchange, entities, business processes, objects and events Internet document exchange Copyright © 2001, Data Access Technologies, Inc.
Parts of EDOC z Enterprise Collaboration Architecture (PIM) y Component Collaboration Architecture y Business Process Specification y Entities y Business Events y Patterns z Technology Mapping (PSM – in progress) y Flow Composition Model (Messaging) y EJB & Corba Components y eb. XML y. NET y Others… z MAPPING – Precise models are source code Copyright © 2001, Data Access Technologies, Inc.
Enterprise Architecture Supply Chain Web Browser HTTP Enterprise Components EAI Applications & B 2 B E-Commerce Client Applications Web Server Applications Copyright © 2001, Data Access Technologies, Inc. XML Corba EJB. NET Events SQL DBMS, Client/Server & Legacy Applications
Parts of eb. XML z Business Process Specification (Like EDOC-CCA) y XML Representation of business process z Core Components y Business Data Types & documents based on context z Collaboration Protocol Profile y What business partners implement what business processes using what technologies y One-One agreement for doing business z Transport Routing & Packaging y Messaging Built on Soap z Registry & Repository y Finding business partners, document and process specifications Copyright © 2001, Data Access Technologies, Inc.
eb. XML Architecture Business Process Context For Business Messages Built With Core Data Blocks Register Implement one Designtime Partner Role CPP Business Service Interface Internal Business App Copyright © 2001, Data Access Technologies, Inc. BP Specification Designtime Implement other Partner Roles CPA CPP Transport Business Service Interface Package Runtime Internal Business App
Summary of points thus far z We must enable the emerging Internet Computing Model y Loosely coupled roles exchanging documents based on a contract of collaboration z Web need interoperability at two levels y Messaging for the data y Metadata for the contract of collaboration, stored in repositories z This model of collaborating roles is recursive, extending into the enterprise, into managed domains and into applications y Inside the enterprise we want to include resources entities, business events and business processes z Supporting the open domain has some required parts and can be augmented with a “treasure chest” of tools and infrastructure z Between EDOC & eb. XML we are covering B 2 B and intra enterprise Copyright © 2001, Data Access Technologies, Inc.
EDOC Component Collaboration Architecture The model of collaborative work
The Marketplace Example Order Conformation Shipped Mechanics Are Us Buyer Process Complete Status Acme Industries Seller Ship Req Shipped Physical Delivery Delivered Get. It. There Freight Shipper Copyright © 2001, Data Access Technologies, Inc.
The Seller’s Detail Order Conformation Order Processing Shipped Shipping Ship Req Shipped Delivered Copyright © 2001, Data Access Technologies, Inc. Event Receivables
Parts of a CCA Specification z Structure of process components and protocols y. Process components, ports, protocols and documents x. Class Diagram or CCA Notation z Composition of process components y. How components are used to specify components x. Collaboration diagram or CCA Notation z Choreography y. Ordering of flows and protocols in and between process components x. Activity Diagram Copyright © 2001, Data Access Technologies, Inc.
The Community Process z Identify a “community process”, the roles and interactions Protocol Copyright © 2001, Data Access Technologies, Inc.
Protocols Copyright © 2001, Data Access Technologies, Inc.
Composition Copyright © 2001, Data Access Technologies, Inc.
ECA Entity Profile The model of things Data Inside a “shared domain”
Adding Entities z Entities are added to manage entity data z Entity Roles are managers that provides a view of the same identity in another context z The Entities have ports for managing and accessing the entities z Non-entities which are owned by (aggregate into) an entity are managed by the entity Copyright © 2001, Data Access Technologies, Inc.
ECA Business Events The model of when… Loosely coupled integration within the enterprise and with “aligned” business partners
Event Based Business Processes Business Rules Business Process Business Actions Business Events Business Entity Copyright © 2001, Data Access Technologies, Inc. Event Notification Business Process Business Events Business Actions Business Entity
Point to point Event Notification App Business Rules Business Process Business Actions Business Events Business Entity App Business Entity Event Notifications Business Rules App Business Rules Business Process Business Events Business Actions Business Events Business Process Business Actions Business Entity Copyright © 2001, Data Access Technologies, Inc. Business Actions Business Events Business Entity
Pub/Sub Event Notification App Business Rules Business Process Business Actions Business Events Business Entity Pub/Sub App Business Rules Business Process Business Events Business Process Business Actions Business Entity Copyright © 2001, Data Access Technologies, Inc. Business Actions Business Events Business Entity
Event Example Copyright © 2001, Data Access Technologies, Inc.
Vision Building and adapting systems for collaboration, reuse and change
Business Component Marketplace z The business component marketplace is projected to be a 10 b market in 5 years z Consider the value of XML components that wrap popular legacy z New application functionality built from components z Components for integration and transformation z XML and web services makes an excellent basis for such components z Technology components, such as for repositories and DBMS z Marketplace my be inside the enterprise or commercial Copyright © 2001, Data Access Technologies, Inc.
OMG Model Driven Architecture (MDA) z High level – platform independent models z Technology Models z Mapping y. Custom y. Standard z Standard Models produce technology specific standards artifacts Copyright © 2001, Data Access Technologies, Inc.
Automated MDA Profile (E. G. EDOC) Infrastructure Mapping (E. G. XML) UML Design Tools Produce & Integrate Enterprise Components Framework & Infrastructure Mapping is tuned to the infrastructure Copyright © 2001, Data Access Technologies, Inc. (E. G. XML)
Technology Independence Business Logic eb. Xml Business Logic Biz. Talk Roseta. Net Logic Ejb Component Logic Component Adapters eb. Xml Biz. Talk Rosetanet EJB Copyright © 2001, Data Access Technologies, Inc. Adapters EJB Business Logic Component MQ Corba CICS
Iterative Development Business Model Design Automation Infrastructure Development Copyright © 2001, Data Access Technologies, Inc. Build Build Release Build Deploy
High level tooling & infrastructure z MUST BE SIMPLE! y. We must be able to create better applications faster y. We must separate the technology and business concerns, enable the user z Tooling + Infrastructure y. Executable models are source code y. Tooling must be technology aware y. Infrastructure must support tooling, not manual techniques z Model based component architectures Copyright © 2001, Data Access Technologies, Inc.
High level tooling & infrastructure z MUST BE SIMPLE! y. We must be able to create better applications faster y. We must separate the technology and business concerns, enable the user Executable Models z Tooling + Infrastructure y. Executable models are source code ya. Tooling must be technology aware y. Infrastructure must support tooling z Model based component architectures Copyright © 2001, Data Access Technologies, Inc.
Net effect z Using these open standards and automated techniques we can; y. Achieve the strategic advantage of an open and flexible enterpise y. Produce and/or integrate these systems FASTER and CHEAPER than could be done with legacy techniques y. Provide a lasting asset that will outlive the technology of the day Copyright © 2001, Data Access Technologies, Inc.
Typical Requirement Buyer Web Page HTML Seller B 2 B Buyer Web Service Seller Copyright © 2001, Data Access Technologies, Inc.
Multi-tier implementation Buyer Web Page HTML B 2 B Buyer Proxy Could have multiple implementations using different technologies Copyright © 2001, Data Access Technologies, Inc. Web Service Seller Could have multiple implementations using different technologies
Multi-tier implementation Buyer Web Page HTML B 2 B Buyer Proxy Web Service Seller Event Legacy Seller Applications Copyright © 2001, Data Access Technologies, Inc. Event Cloud Implementing seller using events
Model Driven Architecture Automating Design To execution
MDA Overview z. Use high level UML models made precise with profiles z. With technology specific mappings z. To produce substantial parts of the executable system Copyright © 2001, Data Access Technologies, Inc.
Models and mapping Platform Independent Model Business Model map Versioned repository Copyright © 2001, Data Access Technologies, Inc. Management Over Time Platform-specific artifacts (IDL/DTD) • UML/CORBA • UML/EJB • XML • OAG • SOAP • eb. Xml • Rosetta. Net • Legacy
Model to Deployed Artifacts Map source overrides • Platform-specific • Process steps • artifacts Au to compile object m at ed pla tfo package module rm -s pe cif ic pr assemble application Process control oc es parameters s • Configure map • Select Tools deploy • Locate Resources Copyright © 2001, Data Access Technologies, Inc. Supplier-Specific artifacts runtime
Generated Artifacts Implementation Artifacts (EJB Examples) Class Objects Java Source Stubs, Skeletons, Helpers, Holders, Interfaces Bean. Info , Editors. . Business Object Implementation Logic Homes, Managers, Primary Keys Serialization, Persistence Management Jars, Wars, Ears SQL Descriptors Documentation M 0/M 1 XMI/DTD 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 Copyright © 2001, Data Access Technologies, Inc.
Reverse Engineering 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 Copyright © 2001, Data Access Technologies, Inc.
MDA and Components Platform Independent Model Business Model Direct Execution Copyright © 2001, Data Access Technologies, Inc. Components
Summary of MDA benefits z Isolates domain specifications from platform details y Reduces complexity y Preserves domain model semantics y Increases stability and lifetime y Generates to platform/legacy of choice z Decreased development time y fast iterative development y separation between the engineering and business requirements z Increased quality. z Builds on industry directions Users Domain Specifications MDA
Скачать презентацию OMG — EDOC Enterprise Distributed Object Computing Bringing
a92ac3a7e1e79c6e79c2e6f7d3d2bb8e.ppt