2008 oagis is the missing piece in soa

Copyright © 1995 - 2005 Open Applications Group, Inc. All rights reserved1 Copyright 2008 Open Applications Group

Open Applications Group

OAGIS is the missing piece in SOA

http://www.openapplications.org

David ConnellyCEO, Open Applications Group, Inc.


IBM SOA Definition

• What is an SOA?SOA is the blueprint for IT infrastructure of the future.

SOA extends the Web services value proposition by providing guidance on how enterprise IT infrastructure should be architected using services.

http://www-306.ibm.com/software/solutions/webservices/


IBM Definition of SOA

• Within a service-oriented architecture, applications, information and other IT assets are viewed as services or “building blocks.”

• Each of these services can be mixed and matched to create new, flexible business processes.



Service Bus

CRM

`

ERP

`

SCM

`

PDM SALES

RECEIVING

B2B Portal


Microsoft Definition

• The policies, practices, frameworks that enable application functionality to be provided and consumed as sets of services published at a granularity relevant to the service consumer.

• Services can be invoked, published and discovered, and are abstracted away from the implementation using a single, standards-based form of interface.

http://msdn.microsoft.com/architecture/soa/default.aspx?pull=/library/en-us/dnmaj/html/aj1soa.asp#aj1soa_topic2


Microsoft and SOA

• What's important to recognize is that Web services are part of the wider picture that is SOA.

• The Web service is the programmatic interface to a capability that is in conformance with WSnn protocols.


Microsoft on SOA

• In fact Web services are not a mandatory component of a SOA, although increasingly they will become so.

• SOA is potentially much wider in its scope than simply defining service implementation, addressing the quality of the service from the perspective of the provider and the consumer.


History of SOA

• DCE• Object Orientation• COM/CORBA• Messaging• ebXML• Web Services


Distributed Computing Environment (DCE)

• The OSF Distributed Computing Environment (DCE) is an industry-standard, vendor-neutral set of distributed computing technologies.


History of DCE

• 1987 - The Open Software Foundation (OSF) is formed. Their purpose is to standardize the UNIX operating system and to promote the interoperability amongst computer systems. The organization is vendor neutral.

• 1988 - OSF issues a request for distributed computing technologies amongst its member companies.

• 1989 - After lots of tests, analyses and reviews a core set of technologies for a distributed computing environment (DCE) is finally selected.

• 1991 - DCE 1.0 is released. It has been developed by five companies in USA, Germany, Ireland and members of OSF.


Goals of DCE

• Network transparency • Location transparency • Location independence • User mobility • Fault tolerance • Resource mobility

Copyright © 1995 - 2005 Open Applications Group, Inc. All rights reserved12

Web Services Stack for SOA


The Importance of Content

• What if he is speaking French,• And she is speaking Mandarin?• They are connected,• But they are not communicating.


Typical SOA Depictment

Request

Web ServicesProviderResponse

InternetWeb ServicesProvider

J2EE™AppServer .NET

SOAP Message

s

This is the WRONGPicture for SOA

This is the WRONGPicture for SOA


What is a Service?

General Ledger

OrderManagement

Receiving Inventory

HumanResources

CustomerService

AccountsReceivable

AccountsPayable

Production

SyncPersonnel

Load Receivable

Load Payable

Sync EmployeeWorkSchedule

Add SalesOrder

Sync SalesOrder

Sync Party

Sync I

temMaster

Issue

Inven

toryM

ovem

ent

CreateProductionOrder

Post JournalEntry

Sync ChartOfAccounts

Sync ExchangeRateGet PickList

Update PickList

Show PickList

Update SalesOrder

Sync ItemMaster

Receiv

eInve

ntoryM

ovem

ent

OAGIS 8.0 Scenario 41

This is A

Service


Typical SOA Depictment

Request

Web ServicesProviderResponse

InternetWeb ServicesProvider

J2EE™AppServer .NET

SOAP Message

s


OAGIS® and SOA

• SOAP standardizes the shape of the plugs

• WSDL standardizes the shape of the outlet (WSDL)

• OAGIS® provides the current that powers the service

OAGIS XML

SOAP

WSDL


OAGIS® in the SOA Stack

• Real services are functions for the business

• The technology stack is important,• But the service is the End-in-Mind


The Business Environment

Integration Back Bone

BusinessUnit n

Supp

lier

Cust

omerBusiness

Unit 1

BusinessUnit 2

Enterprise


OAGIS is a Canonical Model

From <many to many> to <many to one>

Addressing the N2 (N-Squared) Issue


A Single Horizontal Language

NeutralMarkup

Language(OAGIS)

S1

std1

Sn...

stdn

S2

std2Service Broker

Internal Systems External Systems

S1

std1

Sn...

stdn

S2

std2


OAGIS® in the SOA Stack

• OAGIS® enables the End-in-Mind for SOA• OAGIS® provides the basis for defining

the services to be deployed • OAGIS® works with your SOA Stack to

give you the Canonical Model that provides the solution to the N-Squared Issue


OAGIS® 9.0 is more than processes and messages


OAGIS® 9.0 is the basis for current and future for business language development


OAGIS® 9.0 is . . .

• Technical Architecture (BOD)– Common Look and Behavior– Extensions Architecture– Extrusions Architecture

• Application Architecture– Common Object Model (Nouns)– Common Component (Class) Libraries

• UN/CEFACT and OAGIS® Components– Artifact Subsets for SOA Service Definitions

• Meta Model– Naming and Design Rules, UN/CEFACT Based– Document Typing– Document inheritance

• Transaction and Context Model– Nouns– Verbs


BODs as Objects

• BODs are comprised of Nouns and Verbs

• Nouns are content• Verbs add “context”

Noun

Verb


OAGIS Component Libraries

• UN/CEFACT

• IST/ISO

• OAGIS


BOD from Class Libraries

OAGIS® BOD

Verb Noun

Component Component Field

Component Field Compound

Field Compound

Field Field

Component Compound

Field Field Compound

Field Field


OAGIS Meta ModelBOD Document Types

• Operational Document– Purchase Order– Production Order

• Financial Document– Journal– Invoice– Payable

• Table Document– Unit of Measure– Party


OAGIS Meta Model

• Document Date Time• Document Status (test/production)• Description and Notes capability• Attachments• Globally Unique Identifier• Digital Signatures• Core Components• Compound Fields


The BOD Architecture


OAGIS® BOD Architecture Benefits

• Common look, feel, and behavior of messages

• Common dictionary across all messages

• Enables common components implementation

• Enables a high level of re-use• Enables the extensibility mechanisms• Provides a faster learning curve for

the user


Simplified OAGIS®

Transactions - Verb Use

VERB Request Verb Response

Process AcknowledgePost AcknowledgeSync ConfirmBODLoad ConfirmBODCancel ConfirmBODChange RespondGet ShowUpdate Respond


Verbs Constrain the Nouns

• Nouns are Consistent as Common Objects• Nouns may need to be different at execution• The Verbs drive these constraints• Example

– SyncPurchaseOrder– CancelPurchaseOrder

• OAGIS constrains the Nouns with XPath portion of XSL (Not XSLT portion)


Verb Constraining the Noun

Application

BOD Instance

Validating Parser

BOD XML Schema

XSL P

rocessor

BOD Constraints


Overlay Extensibility

• Overlay Extensibility enables additions to OAGIS® BODs in a way that:– The overlay content appears in-line with OAGIS

content– The Non-OAGIS® content is distinguishable from

the OAGIS® content– Both are validate-able– The extended schema is managed separately

from OAGIS® Schema


Overlay Example

OAGIS®

Overlay

Your BOD


Lite BODs for Services

OAGIS® CANONICAL BODS

Light Weight BODS• OAGIS® also enables you to

“extrude” Lightweight BODs• Canonical stays in place• Extrude from the class libraries• Maintain at the library level• Use lightweight BODs for

lightweight services


OAGIS® BOD Stack

Lite BOD

Lite BOD

Industry A Overlay

Industry B/Company A Overlay

UN/CEFACT/ISO Core Components

OAGIS® Types &Core Components

OAGIS® Business Object Documents

XML Schema (XSD)

UML Models

IST/ISO20022Core Components

Meta M

odel

Nam

ing andD

esign Rules

BO

D A

rchitecture


OAGIS 9 is . . .

• Technical Architecture (BOD)– Common Look and Behavior– Extensions Architecture– Extrusions Architecture

• Application Architecture– Common Object Model (Nouns)– Common Component (Class) Libraries

• UN/CEFACT and OAGIS® Components– Artifact Subsets for SOA Service Definitions

• Meta Model– Naming and Design Rules, UN/CEFACT Based– Document Typing– Document inheritance

• Transaction and Context Model– Nouns– Verbs



Questions?http://www.openapplications.org