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
Business Requirements
Virtual Enterprises
Enterprise Integration (EAI)
Supply-chain automation (B2B)
Customer Integration (B2B)
Web deployment (B2C)
Internet Marketplace (B2C)
Collaboration and Integration
Copyright © 2001, Data Access Technologies, Inc.
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
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
We need to extract
the meat from the
buzzwords
And figure out how
these concepts fit
together
To e-enable the
enterprise
Web Services
Model Driven
Architecture
EAI
Open
Components
Middleware
Collaborative
Enterprise
Repositories
Metadata
Copyright © 2001, Data Access Technologies, Inc.
Messaging
& Events
Shared Data
Workflow
Business & Technology
Coupling
“Open B2B”
Ad-hoc business
“Community B2B” 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
ebXML
Soap
Traditional
EDI
Events &
Messaging Synchronous
(UML)
Transactional
JMS
MQ-Series
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”
 Independent domains
collaborating via open
standards
 No assumption of “the same
The Enterprise”
Enterprise
“The
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
Copyright © 2001, Data Access Technologies, Inc.
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
Copyright © 2001, Data Access Technologies, Inc.
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)
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. (ebXML, Soap,
.NET)
Two levels of
interoperability
Instance data and interoperability
Biztalk
ebXML
Business
Partner
Business
Partner
Bridge
Over Soap
Over Soap
Metadata (contract) interoperability
ebXML
BPSS
Purchasing
Model
Normal Form
Each can be transformed
Copyright © 2001, Data Access Technologies, Inc.
.NET
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
Copyright © 2001, Data Access Technologies, Inc.
Inner Role
Legacy
Inner Role
Domain
Cust
Inner
Role
Collaborative Business
Semantics
 Defined: The processes, information and contracts of
interaction between collaborators within a community
 Collaborative business semantics are a valuable longterm 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)
Copyright © 2001, Data Access Technologies, Inc.
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
Copyright © 2001, Data Access Technologies, Inc.
Standards for Global
Internet Computing
XML
UML4EDOC
.NET
BPML
WSDL
SOAP
XML-Schema
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
Copyright © 2001, Data Access Technologies, Inc.
Vision
 EDOC (a UML Profile)
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
Copyright © 2001, Data Access Technologies, Inc.
ebXML & EDOC
ebXML
EDOC
Enterprise
Integration
Transport
Distribution
Collaboration
Repository
Process Model
Components
Information
Model
Runtime
MDA
Copyright © 2001, Data Access Technologies, Inc.
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
Copyright © 2001, Data Access Technologies, Inc.
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
Copyright © 2001, Data Access Technologies, Inc.
Enterprise Architecture
Supply Chain
Enterprise
Components
EAI Applications &
B2B E-Commerce
Web
Browser
HTTP
Client
Applications
Web Server
Applications
Copyright © 2001, Data Access Technologies, Inc.
XML
Corba
EJB
.NET
Events
SQL DBMS,
Client/Server
& Legacy
Applications
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
Copyright © 2001, Data Access Technologies, Inc.
ebXML 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
 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
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
GetItThere 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
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
Copyright © 2001, Data Access Technologies, Inc.
The Community Process
Identify a “community process”, the roles and
interactions
BuySell CommunityProcess
Buyer
Seller
Buy
Protocol
Sell
Delivery
Ship
Shipper
Delivery
Copyright © 2001, Data Access Technologies, Inc.
Ship
Protocols
Protocol OrderBT
Order
OrderConfirmation
OrderDenied
responderRole
Seller
initiatorRole
Buyer
<<initiates>> Order
<<responds>> OrderDenied
Copyright © 2001, Data Access Technologies, Inc.
Failure
<<responds>> OrderConfirmation
Success
Composition
Copyright © 2001, Data Access Technologies, Inc.
ECA Entity Profile
The model of things
Data Inside a “shared domain”
Adding Entities
<<Entity>>
CompanyManager
 Entities are added to manage
entity data
 Entity Roles are managers that
«Key»
provides a view of the same
CompanyKey
+CompanyId : String
identity in another context
 The Entities have ports for
managing and accessing the
«Key»
AccountKey
+AccountNo : String
entities
 Non-entities which are owned
by (aggregate into) an entity
are managed by the entity
Manage
.
Manages
1
1
-.
-.
1
1
-.
-.
«EntityData»
Account
+Name : String
+Balance : Decimal = 0
+AccountNo : long
1
1
-Manages
-.
<<EntityRole>>
AccountManager
Manage
Copyright © 2001, Data Access Technologies, Inc.
«EntityData»
Company
+Name : String
-CompanyId : String
+Cust +Adr
1
1..*
«EntityData»
Addtress
+Street : String
+City : String
+State : String
+Zip : String
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
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
App
Business
Rules
Business
Rules
Business
Process
Business
Process
Business
Actions
Business
Events
Business
Entity
Business
Entity
Event
Notifications
App
Business
Actions
Business
Events
App
Business
Rules
Business
Rules
Business
Process
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
App
Business
Rules
Business
Rules
Business
Process
Business
Process
Business
Actions
Business
Events
Business
Actions
Business
Events
Business
Entity
Business
Entity
Pub/Sub
App
App
Business
Rules
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
 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
Copyright © 2001, Data Access Technologies, Inc.
OMG Model Driven Architecture (MDA)
High level – platform
independent models
Technology Models
Mapping
Custom
Standard
Standard Models
produce technology
specific standards
artifacts
Copyright © 2001, Data Access Technologies, Inc.
Automated MDA
UML
Design
Profile
(E.G. EDOC)
Infrastructure
Mapping
(E.G. XML)
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
Business
Business
ebXml
Logic
Business
BizTalk
Logic
RosetaNet
Logic
Ejb Component
Logic
Component
Component
Component
Adapters
ebXml
BizTalk
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 Build Build
Build
Release
Build
Deploy
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
Copyright © 2001, Data Access Technologies, Inc.
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
Executable Models
Tooling + Infrastructure
Executable models are source code
aTooling must be technology aware
Infrastructure must support tooling
Model based component architectures
Copyright © 2001, Data Access Technologies, Inc.
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
Copyright © 2001, Data Access Technologies, Inc.
Typical Requirement
Buyer
Web Page
HTML
Seller
B2B
Buyer
Web
Service
Seller
Copyright © 2001, Data Access Technologies, Inc.
Multi-tier implementation
Buyer
Web Page
HTML
B2B
Buyer
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
B2B
Buyer
Buyer
Proxy
Web
Service
Seller
Event Event
Event Cloud
Legacy
Seller
Applications
Copyright © 2001, Data Access Technologies, Inc.
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
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
•ebXml
•RosettaNet
•Legacy
Model to Deployed Artifacts
overrides
Map source
compile
object
package
Process control
parameters
•Configure map
•Select Tools
•Locate Resources
Copyright © 2001, Data Access Technologies, Inc.
•Platform-specific
•Process steps
•artifacts
Supplier-Specific
artifacts
module
assemble
application
deploy
runtime
Generated Artifacts
Implementation Artifacts (EJB Examples)
Class Objects
Jars,Wars,Ears
Java Source
Stubs, Skeletons,
Helpers, Holders,
Interfaces
BeanInfo,Editors.
.
Business Object
Implementation
Logic
Homes,
Managers,
Primary Keys
Serialization,
Persistence
Management
SQL
Descriptors
Documentation
M0/M1 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
Copyright © 2001, Data Access Technologies, Inc.0-20% manual override
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
 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