copyright © 1995 - 2003 open applications group, inc. all rights reserved 1 draft beyond web...
Post on 19-Dec-2015
224 views
TRANSCRIPT
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 1
DRAFT
Beyond Web Services
Using OAGIS as a Standard Business Language for Enterprise Integration
David Connelly, CEO, Open Applications Group, Inc.
www.openapplications.org
OracleWorld 2003
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 2
DRAFT
Agenda
• Open Applications Group Introduction• Trends in Global Business Integration• Open Applications Group Standard• OAGIS as a Canonical Model• A Business Language for Web Services
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 3
DRAFT
Not-For-Profit Industry Consortium to:
Promote interoperability among Business Software Applications and
To create and/or endorse one or more standards for easier business software interoperability
Open Applications GroupWho we are
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 4
DRAFT
Open Applications Group
E2E = B2B + A2A + A2ETMEverywhere to Everywhere Integration
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 5
DRAFT
OAGI Activities
• Technical Activities – 6 XML Work Groups
• Out Reach Activities – Working with Industry
• Interoperability Activities – NIST Test Bed
• Services and Training– OAGIS Help to Users
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 6
DRAFT
Oracle and OAGi
• Oracle is a founding member• Major supporter of OAGi• Building OAGIS into Oracle Applications• What else to say?
– Which applications use OAGIS?– When is Oracle going to Schema?– When is Oracle going to Web Services– Who at Oracle can I contact?
To be completedTo be completed
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 7
DRAFT
Trends in Global Business Integration
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 8
DRAFT
Need for Integration
82% of IT Professionals say that integrating existing systems is theirway to improve business processes
Source: Information Week, Aug. 27, 2001Source: Information Week, Aug. 27, 2001
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 9
DRAFT
Demand for Integration
Customers’ top strategic software platform project over the next year
S ource : M organ S tanley C IO S urvey, M ay 2001N ote : M ultip le responses perm itted
35%
33%
30%
24%
23%
21%
19%
16%
15%
13%
12%
12%
8%
7%
5%
4%
A pp lica tion in te g ra tio ne -b us ine ss
C R MS C M /L og is tics
H RD a ta ba se up g ra de
In trane t im pro vem e n tsF in anc ia l (A cco un ting )
M arke ting app s on W eb s ite
e -p rocu rem en t W eb s iteS ys . m g m t in fras truc tu re
C om m e rce se rve r
B u ild ing In te rne t co m pa nyE ng in ee ring so ftw a re
M an u fac tu rin g so ftw a reO the r
D ereg u la tion
0% 10% 20% 30% 40%
% o f R esp o n d en ts
3%
S ource : M organ S tanley C IO S urvey, M ay 2001N ote : M ultip le responses perm itted
35%
33%
30%
24%
23%
21%
19%
16%
15%
13%
12%
12%
8%
7%
5%
4%
A pp lica tion in te g ra tio ne -b us ine ss
C R MS C M /L og is tics
H RD a ta ba se up g ra de
In trane t im pro vem e n tsF in anc ia l (A cco un ting )
M arke ting app s on W eb s ite
e -p rocu rem en t W eb s iteS ys . m g m t in fras truc tu re
C om m e rce se rve r
B u ild ing In te rne t co m pa nyE ng in ee ring so ftw a re
M an u fac tu rin g so ftw a reO the r
D ereg u la tion
0% 10% 20% 30% 40%
% o f R esp o n d en ts
3%
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 10
DRAFT
The Challenges
• Multiplicity of applications across enterprise fulfilling the same function
• No enterprise wide application and information architecture
• Inflexible architecture• Several versions of “enterprise-
objects” such as Product, Customer, etc
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 11
DRAFT
Business Environment
Integration Back Bone
Business
Unit n
Su
pp
lier
Cu
stom
er
Business
Unit 1
Business
Unit 2
Enterprise
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 12
DRAFT
• Agility
The Focus
• Lower cost of ownership
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 13
DRAFT
• Mostly at the data level• Mostly point to point• Custom program interfaces
or flat file exchange• Grows at exponential rate
Current State of Integration
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 14
DRAFT
• EDI is not disappearing soon• 1st Generation B2B• Suited mainly for big companies• Still largest B2B environment• Organizations generally don’t
remove systems that work
EDI Views
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 15
DRAFT
Connected!
A Vision of Plug and Play
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 16
DRAFT
Semantic Importance
• Interoperability requires interfaces to be standardized. Only 5% of the interface is a function of the middleware. The other 95% is a function of the application semantics. (Gartner Group)
Application Integration Semantics
Messaging and Transport Services
95%
5%
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 17
DRAFT
• XML is a successor to EDI• XML defines the data as it is
being transmitted• XML is technology neutral• More powerful capabilities
for integration• Emerging tools supporting it
XML Emerging
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 18
DRAFT
Why XML?
• XML provides a much richer data capability than other approaches
• XML enables more advanced types of eBusiness connections and application integration
• XML tools provide more options for interoperability
• XML is designed for the web and Web Services• XML is less expensive than EDI
– Brings in your smallest trading partners at a very low entry cost
– EDI for the masses
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 19
DRAFT
• EDI is not disappearing soon• 1st Generation B2B• Suited mainly for big companies• Still largest B2B environment• Organizations generally don’t
remove systems that work
EDI Views
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 20
DRAFT
XML Adoption Curve
• Out of experimental stage
• Fully into early adoption
• Less talk, more action
• It is not too late
We are about here
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 21
DRAFT
What is OAGIS?
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 22
DRAFT
OAGIS is Process Definitions and Payloads
• Scenario is process definition
• Business Object Documents (BODs) are messages within the Collaboration
• Freely downloadable at:
http://www.openapplications.org
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 23
DRAFT
OAGIS Scenarios are Processes
• Scenarios may be large or small– Processes, Activities, Tasks, etc.
• Scenarios are expressed in UML• Scenarios serve as a library of
re-useable processes• Organizations are welcome to
modify to fit their requirements
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 24
DRAFT
Example Scenario– Catalog and Price List
: Order Management
: PDM Systems : Manufacturin...
: Catalog Manageme...
: Purchasing
1: SYNC_CATALOG
2: GET_CATALOG
3: SHOW_CATALOG
5: GET PRICELIST
6: SHOW PRICELIST
8: GET ITEM
9: SHOW ITEM
11: GET_ITEMXREF
12: SHOW_ITEMXREF
14: GET_ITEMCLASS
15: SHOW_ITEMCLASS
17: GET_ITEMSPECS
18: SHOW_ITEMSPECS
21: GET PRODAVAIL
22: SHOW PRODAVAIL
4: SYNC CATALOG
7: SYNC PRICELIST
10: SYNC ITEM
13: SYNC_ITEMXREF
16: SYNC_ITEMCLASS
19: SYNC_ITEMSPECS
20: GET PRODAVAIL
23: SHOW PRODAVAIL
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 25
DRAFT
OAGIS BODs are a Language
• OAGIS BODs use XML to define a common business language for businesses to use.
• This language is used to exchange information between business applications and businesses.
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 26
DRAFT
OAGIS BOD Definition
• The OAGIS Business Object Document (BOD) Architecture defines the common XML structure and behavior definition for all OAGIS Messages.
• The OAGIS BOD Definition defines the layout or structure of a specific message to be used.
• The OAGIS BOD Instance is an occurrence of a live message that contains real data in the format defined in the schema above.
• The term BOD is often used as a generic term used to describe either BOD Definitions or BOD Instances.
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 27
DRAFT
OAGIS BOD Definition
• The OAGIS BOD Architecture is defined in the OAGIS Design Guide – A Word Documentor on web site in HTML.
• The OAGIS BOD Definitions are defined in XML Schema, in a text file such as:– ProcessPurchaseOrder.XSD– Equivalent to 850 definition
• The OAGIS BOD Instances (occurrences) are defined in XML files that are pure text:– ProcessPurchaseOrder.XML– Equivalent to an 850 occurrence
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 28
DRAFT
Sample BOD Definitions
• ProcessPurchaseOrder• CancelPurchaseOrder• AcknowledgePurchaseOrder• ShowShipment• ProcessInvoice• GetInventoryCount• GetCredit• SyncProductionOrder
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 29
DRAFT
The BOD Architecture
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 30
DRAFT
BOD Application Area
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 31
DRAFT
BOD Data Area
Noun
Verb
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 32
DRAFT
Core Components
(each box is a component)
Business View of BOD
POORDERHDR
POTERM
ADDRESS
CONTACT
PARTNER
CHARGE
DISTRIBUTN
Diagram Note: - Required = Solid boxes - Optional = Dashed boxes
POORDERLIN
POSUBLINE
POLINESCHD
PARTNER
ADDRESS
CONTACT
POTERM
DISTRIBUTN
CHARGE
DISTRIBUTN
Business View of BOD Definition
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 33
DRAFT
OAGIS Extensibility
• Scenario Extensibility– Scenario extensibility enables the use of
the Scenarios as a base library of processes.
• BOD Extensibility– UserArea extensions provide for optional
elements within each OAGIS component to carry any necessary additional information.
– Overlay extensions provide the ability to have extensions show up in-line with OAGIS defined fields, compounds, and components. This is not possible with DTDs.
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 34
DRAFT
Extensibility Benefits
• Non-intrusive to the standard• Leverages work of OAGIS base• More customized approach for user• Less re-work for re-application at
next release• Easier to manage
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 35
DRAFT
OAGIS BOD Benefits
• Ensures common look, feel, and behavior of all XML messages in the repository
• Enables common components and common dictionary
• Guarantees a high level of re-use• Enables the extensibility
mechanisms• Provides a faster learning curve
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 36
DRAFT
Current Version
• OAGIS 7.2.1/8.0– 7.2.1 is DTD– 8.0 is XSD– Functional Equivalence– 60 Collaboration Definitions– Support for SOAP, ebXML, RNIF, BizTalk– 201 XML Message Definitions– Actually the 16th Version
• 8+ years in maturing• Available for Free
http://www.openapplications.org/downloads/oagidownloads.htm
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 37
DRAFT
Value Chain CollaborationApplications
EnterpriseManagement Applications
EnterpriseExecution
Applications
OAGIS Content
• eCommerce– e-Catalog– Price Lists– RFQ and Quote – Order Management– Purchasing– Invoice
• Manufacturing– Plant Data Collection – Engineering– Warehouse Management– Enterprise Asset Mgmt.
• Logistics– Shipments
• CRM– Customer– Sales Force Automation
• ERP– Financials– Human Resources– Manufacturing– Credit Management
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 38
DRAFT
OAGi Work Groups
• CRM XML• Logistics XML• RiskML• Location Services• Core Components• Semantic Integration
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 39
DRAFT
Forming Work Groups
• Any Three Members• May be Industry-Based• May be Domain Based• Work Group Types
– Regular– Collaborative– Self-Governing
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 40
DRAFT
Industry Collaborations
• UN/CEFACT – United Nations• ISO- International Standards Organization• MoU MG – Memorandum of Understanding Management Group• KIEC – Korean e-Commerce Consortium• NIST – National Institute of Standards & Technology• AIA – Aerospace North America• AECMA – Aerospace Europe• STAR – Auto Retail North America• AIAG – Auto Supply Chain North America• AAIA – Auto Aftermarket North America• Odette – Auto in Europe• RV Industry – North America• HR-XML – HR Content, world-wide• SP95 – Enterprise Controls• ARTS (Retail)• STEP – Engineering world-wide• IFX – Interactive Financial Exchange• EIDX – Electronics and Computer Industry• IEC TC57 WG14• Footwear Industry
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 41
DRAFT
• Tens of thousands of OAGIS Library Downloads since 1996
• Each Download contains all OAGIS Schemas
• Use includes– B2B, 80%– A2A, 64%– C2B, 15%
• Representing over 60 countries• 5 Continents
OAGIS Adoption
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 42
DRAFT
Some OAGIS Contributors
KildaraKim Liljeborg (Global Brewer)Lars Abrell (Scanova)Lockheed MartinLouis Davis / Earl Miller (GHX)Lucent TechnologiesMarcam=>Wonderware=>InvensysMega.comMenlo WorldwideMicrosoftMike Parks (Georgia Tech)NADA/STARNECNet Commerce Corp.Netfish Technologies=>IONANetonomyNexPrise=>VentroNextSet Software, Inc.NISTObjectSpace, Inc.ObTechOnDisplay=>VignetteOptio Software, Inc.OraclePaperExchange.com=>PaperSpace.comPCS Inc.PeoplesoftPricewaterhouse Coopers=>IBMPSDI=>MRO SoftwareQADQuadremRequisite Technology
Robocom SystemsSAGA SAGA SoftwareSand Hill SystemsSAPScalaSiemensSilverstreamSoftQuad SoftwareSoftware Technologies Corp.=>SeeBeyondSterling CommerceStreamServe, Inc.Sun MicrosystemsSupplierMarket.comSymbolic SystemsSynQuest, Inc.Teklogix=>Psion TeklogixTexas InstrumentsTibcoTilion, Inc.Toyota Motor SalesTradeAccess=>OzroTrilogyTSI=>MercatorU.S. Air ForceUnilever PLCUS DataVesta TechnologiesViewlocityVitria TechnologywebMethodsXML Global TechnologyXML Solutions=Vitria
STAR
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 43
DRAFT
OAGIS Live in 40 Known Countries
• Australia• Austria• Bahrain• Belgium• Canada• Chile• China• Croatia• Czech Republic• Denmark• Ireland• Finland• France• Germany
• Holland• Hungary• India• Israel• Italy• Japan• Korea (South)• Lithuania• Mexico• Netherlands (Holland)• Norway• Papua New Guinea• Poland
• Russia• Saudi Arabia• Singapore• Slovenia• Solvakia• South Africa• Spain• Sweden• Switzerland• Turkey• United Arab Emirates• United Kingdom• United States
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 44
DRAFT
OAGIS Used in over 37 Known Industries
• Aerospace• Agri-Business• Automotive Manufacturing• Automotive Retail• Automotive Aftermarket• Banking• Brewing• CPG • Chemical• Computer Hardware• Computer Software• Consumer Goods – Electronics• Defense• Distributors• Federal Government• Food Manufacturing• Furniture Manufacturing• Medical Device Manufacturing• Insurance
• Industrial Goods Manufacturing• Logistics• Mining• Oil • Natural Gas• Paint• Paper• Publishing• Retail• Shipping• Software• State and Local Government• Telecommunications• Tire Manufacturing• Tobacco• Trucking• Universities• Electric Utilities
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 45
DRAFT
OAGIS as a CANONICAL MODEL
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 46
DRAFT
Business Environment
Integration Back Bone
Business
Unit n
Su
pp
lier
Cu
stom
er
Business
Unit 1
Business
Unit 2
Enterprise
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 47
DRAFT
A Case for a Canonical Model
From <many to many> to <many to one>
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 48
DRAFT
The mathematics of scaling up
For traditional point to point or<many to many> integration:
The number of possible connectionsamong any number of items is n(n-1)for two way connections.
n = 5 5(4) = 20
n = 10 10(9) = 90
n = 15 15(14) = 210
n = 20 20(19) = 380
Number ofcomponentsto integrate
Apply traditionalformula
Cost of traditionalintegration @ 0.1 FTE
2 FTEs
9 FTEs
21 FTEs
38 FTEs
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 49
DRAFT
The mathematics of scaling up
For best practices integration:
The number of possible connections among any number is n * 2.0
Number ofcomponentsto integrate
Best practicesformula
n = 5 5 * 2.0 = 10
n = 10 10 * 2.0 = 20
n = 15 15 * 2.0 = 30
n = 20 20 * 2.0 = 40
1 FTE
2 FTEs
3 FTEs
4 FTEs
Cost of best practicesintegration @ 0.1 FTE
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 50
DRAFT
Side by side comparison
<many to many> growth <many to one> growth
4 FTEs38 FTEs
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 51
DRAFT
• Agilent• Amersham Health• IBM• Oracle• Goodyear• AT&T Wireless• Ford• General Electric Power• Lucent• Weyerhauser
Sample of Customers
SolutionProviderspecificOverlay
VerticalContentOverlay
VerticalContentOverlay
VerticalContentOverlay
CompanySpecificOverlay
OAGIS Canonical Business Language
CRMERP CustomerSupplier
SolutionProviderspecificOverlay
VerticalContentOverlay
VerticalContentOverlay
VerticalContentOverlay
CompanySpecificOverlay
SolutionProviderspecificOverlay
VerticalContentOverlay
VerticalContentOverlay
VerticalContentOverlay
CompanySpecificOverlay
OAGIS Canonical Business Language
CRMERP CustomerSupplier
OAGIS Canonical Business Language
CRMERP CustomerSupplier CRMERP CustomerSupplier
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 52
DRAFT
OAGIS and Web Services
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 53
DRAFT
Core Standards for Web Services
• XML provides platform independent business language definition
• SOAP provides the platform independent envelope
• WSDL provides the platform independent connection
• UDDI provides platform independent definition
TCP/IPTCP/IP
HTTPHTTP
WSDLWSDLSOAPSOAP
XMLXMLUDDIUDDI
TCP/IPTCP/IP
HTTPHTTP
WSDLWSDLSOAPSOAP
XMLXMLUDDIUDDI
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 54
DRAFT
WS-I Basic Profile 1.0
• XML 1.0 (Second Edition) • XML Schema Part 1: Structures • XML Schema Part 2: Datatypes • SOAP 1.1 • WSDL 1.1 • UDDI 2.0 • RFC2246: The Transport Layer Security Protocol
Version 1.0 • RFC2459: Internet X.509 Public Key Infrastructure
Certificate and CRL Profile • RFC2616: HyperText Transfer Protocol 1.1 • RFC2818: HTTP over TLS • RFC2965: HTTP State Management Mechanism • The Secure Sockets Layer Protocol Version 3.0
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 55
DRAFT
WSDL
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 56
DRAFT
OAGIS WSDL
Example
GetPurchaseOrder.wsdl 01 <?xml version="1.0" encoding="utf-8" ?>02 <definitions03 xmlns="http://schemas.xmlsoap.org/wsdl/"04 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"05 xmlns:xs="http://www.w3.org/2001/XMLSchema" 06 xmlns:oagis="http://www.openapplications.org/oagis"07 xmlns:tns="http://www.openapplications.org/oagis/8.0/GetPurchaseOrder.wsdl" 08 targetNamespace="http://www.openapplications.org/oagis/8.0/GetPurchaseOrder.wsdl">0910 <wsdl:types>11 <xs:schema>12 <xs:import 13 namespace="http://www.openapplications.org/oagis"14 schemaLocation="GetPurchaseOrderMessages.xsd"/>15 </xs:schema>16 </wsdl:types>1718 <wsdl:message name="GetPurchaseOrderRequest">20 <wsdl:part 21 name="Document" element="oagis:GetPurchaseOrder"/>22 </wsdl:message>23 <wsdl:message name="GetPurchaseOrderResponse">24 <wsdl:part 25 name="Document" element="oagis:ShowPurchaseOrder"/>26 </wsdl:message>2728 <wsdl:portType name="GetPurchaseOrderPortType">29 <wsdl:operation name="GetPurchaseOrder">30 <wsdl:input message="oagis:GetPurchaseOrderRequest"/>31 <wsdl:output message="oagis:GetPurchaseOrderResponse"/>32 </wsdl:operation>33 </wsdl:portType>3435 <wsdl:binding 36 name="GetPurchaseOrderBinding" 37 type="tns:GetPurchaseOrderPortType">38 <soap:binding 39 transport="http://schemas.xmlsoap.org/soap/http" style="document"/>40 <wsdl:operation name="GetPurchaseOrder">41 <soap:operation soapAction=""/>42 <wsdl:input>43 <soap:body use="literal"/>44 </wsdl:input>45 <wsdl:output>46 <soap:body use="literal"/>47 </wsdl:output>48 </wsdl:operation>49 </wsdl:binding>50 </wsdl:definitions>
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 58
DRAFT
OAGIS and Web Services
• Web Services standardizes– Shape of the plugs (SOAP)– Shape of the outlet (WSDL)– Current over the wire (OAGIS XML)– WS-Security will be the ground
WSDL
SOAP
OAGIS XML
WS -Security
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 59
DRAFT
OAGIS and Web Services
• OAGIS Article in XML Journal• More Resources soon to be published• WS-I Membership• WS-I Compatibility • Defining OAGIS to WSDL• Get/Show Verbs planned for most Nouns
– May charge non-members for WSDL
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 60
DRAFT
Technology Strategy
The technical architecture of the Open
Applications Group is intended to be
technology sensitive . . . but not technology
specific.
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 61
DRAFT
OAGIS is Framework Independent
OAGIS is the payload
SOAP is the envelope
ebXML is the envelope
Your Envelope is the envelope
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 62
DRAFT
Cool New Stuff Coming
• Core Components• Semantic Integration• Schematron• UDEF
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 63
DRAFT
Why OAGIS
• Royalty Free, Open Standard• Oracle Support• Web Services and ebXML Support• Mature and Rich Functionality• Extensible• Investment Protection
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 64
DRAFT
OAGIS is free. Why pay to be an OAGi member?
• Voting rights on all Work Groups• Formally initiate Work Groups• Voice on the OAGi Board to influence
OAGi direction• Outstanding learning and networking
opportunity• Meeting attendance is free• Discounts on services and training
– 25% off services and training
• New deliverables may be free only to members
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 65
DRAFT
OAGIS Services
• Focused on OAGIS users• Phone Support• Training
– OAGIS “Quick Start”– On Site or Classroom
• Services– Implementation Support– BOD Extensions – BOD Development
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 66
DRAFT
Next OAGI Meeting
• San Francisco– October 28 - 30– Hosted by Oracle
Come Join Us!
www.openapplications.org
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 67
DRAFT
AQ&Q U E S T I O N S
A N S W E R S
Copyright © 1995 - 2003 Open Applications Group, Inc. All rights reserved 68
DRAFT
Reminder – please complete the
OracleWorld online session survey
Thank you.