Service-Oriented Architectures
at General Motors
Mike Vella
Web Service Business
Development
SMI, Market Development
Engage the Web
Services Pilot
Team to advance
your business!
Web Services Market Today
• Evolution of Application Integration over the Internet
• Market is not clearly defined
– Open Standards are making progress
• Web Service Business Issues
– Resolve IT department bottlenecks
– Enhance Cost Efficiency with existing infrastructure
• Web Services Economic model evolves
– A few highly skilled leading-edge companies seek to enable
development and integration
– The Big “Platform and Software” Players look to integrate WS into
product line
• Gartner predicts Market size to exceed $1.7
billion by 2002
ASD
1
Session 1543
Web Services Pilot Program
Drive Business Partnerships
With “Marquee” Enterprises
and Best-of-Breed Software
Vendors in Leading-Edge
Web Service Pilot Projects to
Advance Open Standards
ASD
1
Session 1543
WS Pilot Value Proposition
• Alleviate Customer “Pain Points” bottlenecks in
their existing IT infrastructure
• Breakdown silos of information
• Increase scalability and integration of desperate
Networks due to Acquisition and mergers
• Increase cost efficiencies with existing
infrastructure
• Increase access and automation to internal
departments, vendors, and clients
• Increase ISV alliance while bringing best-of-breed
technologies and products to our customers
ASD
1
Session 1543
Presenters Are:
• Fred Falten, Director of Application
Architecture and Integration for IS&S at
General Motors Corporation
• Mike Wheaton is a Java Enterprise Architect
with Sun Microsystems Inc. Professional
Services
• Himagiri (Hima) Mukkamala is WebServices
Architect/Strategist for Sybase e-Business
division
ASD
1
Session 1543
Service-Oriented Architectures
at General Motors
Fred Falten
Director of Applications
Architecture and Integration
for IS&S
General Motors Corporation
Service-Oriented Architectures at
General Motors
Understand how GM is
using ebXML to extend
SOA and enhance B2B
for the Automotive
Industry
ASD
1
Session 1543
Learning Objectives
• As a result of this presentation,
you will be able to:
– Understand the business benefits of SOA
– Exploit the cumulative features of Web
Services and ebXML to meet very largescale B2B
– Explain the architecture for ebXML
– Witness the operation of an ebXML
Reference Implementation
ASD
1
Session 1543
Services-Oriented
Architecture Strategy
ebXML
DemoB2B Market,
Global Multienterprise
Big A2A
Integrated App
Families
WS
Demo
Small A2A
Integrated
Apps
Homogeneou
s Application
Typical access via:
ebXML
Session 1543
SOAP/HTTP
(JAX-M for WS-Routing)
Web Services
for XML Message
Web Services
for RPC
Reusable
Components
Tighte
rLimite
d
1
ebXML
SOAP/HTTP
(JAX-M for ebXML)
Demo
SOAP/HTTP
(JAX-RPC)
WS
Demo
ORB
(RMI/IIOP)
WS
Demo
Granularity
Coupling
Security
Looser
Extensive
ASD
SOA Benefits for GM
• Support Business Agility
– Speed: Faster deployment of new business direction
• Assemble and reassemble applications from
reusable services
• Rapid integration with joint ventures, suppliers,
dealers, branches, …
– Flexibility: Significantly expand the available pool of
trading partners
• Commonize Continually Improving Business Execution
– Act as One Company: Shared services and business behavior
– Use the latest services as they are created (flexible extension)
• Reduced Business Interruptions
– Loose coupling improves availability and recovery for global
distributed systems
– Core set of thoroughly tested, highly-available services ASD
1
Session 1543
SOA Benefits for GM
• IT Cost Savings
– Accomplish more with development budget
• Services reuse is aimed at GM’s outsourced model
• Business process modelers can assemble portions of application
• Faster development of new applications
• Recycle/migrate legacy applications as new services
– Reduction in sustaining costs
• Convert and merge legacy functionality into Web Services
• Reduction in deployment environment diversity
• Market-centric solution
– Component and SOA are the dominant complementary
architectures:
• J2EE™ + WebServices + ebXML
– Increased competition among product vendors and
software development vendors
1
Session 1543
ASD
Software Factory
Enabler Project
• Purpose: Define GM’s Application Architecture and IT
Standards for SOA; Evangelize
• Deliverables: Reusable Architectural Patterns and RI for
WebServices and ebXML; Recommendations
• Approach: Enterprise-level IT provides SOA technology
and methodology leadership
• Funding: Application Solutions Delivery corporate budget
• Key contributors: BEA, IBM, New Era of Networks and Sun
• GM’s development model:
– Mostly outsourced to Software Factories
– Buy before build; committed to open standards
– Legacy is dominant; most new development is
for the J2EE™ platform
1
Session 1543
ASD
ebXML Applications at GM
• GM Approved XML Standards (Q1 2002)
– OAG BODs: XML Business Document Standard
– ebXML:
B2B XML Technical Standard
• Application categories:
–
–
–
–
–
Dealers: Inventory mgmt., financial data, parts
OnStar: Vehicle on-board services
Supply Chain: Purchasing and OTD
Engineering Suppliers: Global concurrent engineering
Finance: Loan/lease collaboration with branches
• Kicked off GM-Covisint B2B XML integration
pilot using ebXML MSH (Q2 2002); Target
completion in Q3 2002
ASD
1
Session 1543
ebXML Architecture @ GM
Michael Wheaton
Sun Microsystems Inc.
GM RI Architectural
Features
●
Reference Architecture based on:
–
–
–
●
Key Aspect—Multi-Tiered Choreography
Engines
–
–
●
Loosely coupled web services applications in back end
Business process collaborations between trading partners
Allows for Declarative Development—XML
document defines
New web services applications
– New Trading Partner Agreements
New Business Process Collaborations
Session–1543
–
1
J2EE—Component Model
Basic Web Services (SOAP, WSDL, UDDI)—Services Layer
ebXML—Expose SOA to trading partners
ebXML Architecture Modules
●
●
●
●
●
1
MSH—Message Service Handler provides reliable
message delivery
CPP/CPA—TP Service Discovery and Agreements
defines protocols, security, timeouts, between
trading partners
BPSS Collaboration—Business Process Specification
Schema for managing collaboration between trading
partners
CC XML Grammers—Core Components/Business
Object Diagrams Industry standard (OAGIS/STAR) XML
grammars
ebXML Registry and Repository—B2B Document
Management System
Complete B2B web services framework—A
●Session 1543
ebXML Architecture at GM
Private/Public
Collaboration
Descriptions
Trading Partner
GM
ebXML
Registry
Repository
Find
Publis
h
BPSS
CPP/A
Primarily Design,
Develop Time
Des/Dev/Dep Time
1
Session 1543
Mapping
Converse
ebXML
ebXML
BPML
MSH Transport
Business Service
Business Service
B2B
Collaboration
Interface
Interface
BPML
WS/J2E
E
- Legacy
- COTS
- Etc.
WS App
CPA
Run Time
App
Negotiate
BPSS/CPA
App
- J2EE
CORBA
- Legacy
- COTS
- Etc.
XML Document
Management
ebXML REGREP
●
●
●
●
●
1
Registry
XML Registry +
Interface Life Cycle
Repository
Query
Manager
Manager
Soap
Life cycle
management
Authentication Security Persistence
features
Manager
Authorization Manager
Query management
engine
Repository
Security features
Database with RIM
includes digital
signatures, user Ids
Registry Organization Extrinsic
Objects
Objects
Classification of any
BPSS, CPA, CC
type of object
Session 1543
ebXML Architecture Details
ebXML ebXML
SOAP
MSH
Apps
J2EE
Web
Container
CP
A
1
Session 1543
EJB
Business
Services
Internal
Firewall
ebXML
Proces
s
Server
Business
Process
Collaboratio
n
BPS
S
SOA Facade
ebXML
BSI
DMZ
Internet
B2B—
Tradin
g
Partne
r
EJB
Business
Services
Orchestration Services
J2EE Application
Server
Container
COTS
Apps
Legac
y
Apps
Legac
y
Apps
DB
Extending SOA With ebXML
Portal
Internal
Firewall
BPSS
Collaboratio
n
ebXML
MSH
Session 1543
Security
Services
ebXML
Proces
s
Server
BPS
S
Web Services
Facade
ebMS
EJB
EJB
Business
Services
Servlet
s
JSPs
J2EE
Web
Container
CP
A
Apps
1
Internet
Browser
B2B—
Tradin
g
Partne
rebXML
BSI
EJ
Web B
Service
Integration Services
GM Architecture
Orchestration Services
J2EE Application
Server
Container
COTS
Apps
Legac
y
Apps
Legac
y
Apps
DB
ebXML Implementation @ GM
Himagiri (Hima)
Mukkamala Sybase
Business Collaboration
(BPSS)
Power Designer Creates BPSS
AvailableVehicle
<<BusinessTransactionActivity>>
Activity
Available Vehicle Activity
The B2B
Collaboration may be
composed of several
business transactions
DealerLocation
<<BusinessTransactionActivity>>
Activity
Dealer Location Activity
VehicleHistory Activity
<<BusinessTransactionActivity>>
VehicleHistory Activity
PurchaseRequest
<<BusinessTransactionActivity>>
Activity
The resulting
sequence is captured
in a BPSS
Vehicle Purchase Request Activity
PurchaseApproval
<<BusinessTransactionActivity>>
Activity
VehiclePurchase Approval Activity
[Business Error]
1
Session 1543
Business Transaction
Definition
Messaging Reliability
AvailableVehicleQuery
Document
Request
Available
Vehicle
ReceiptAck
AcceptanceAck
AvailableVehicleResponse
Document
Respond
Available
Vehicle
ReceiptAck
[Technical Error]
[Business Error]
Technical Error
Business Error
1
Session 1543
Business Transactions define
reliable messaging exchange
between the two trading partners
using acknowledgments, error
handling, logging and roles
Trading Partner Agreement
(CPA)
Power Designer
<<BinaryCollaboration>>
Bulk Buying
Bulk Used
Car Buyers
General Motors
Trading Partner
Specifies
Agreement
(CPA)
Business
Process
Specifications
(BPSS)
Bulk Buying
Business Process
Contains
Business
Transactions
Check Vehicle Availability
Dealer Location
Vehicle History
Submit PO
Contains
XML Messages
DTDs
Grammars
1
Session 1543
Trading Partner Agreement
(CPA)
Web Services Integrator Manager
1
Session 1543
Manage Industry
Standard Payloads
Reg/Rep helps
manage
BPSS, CPP, CPA,
BODs
and their associations
1
Session 1543
STARXML has defined
Automotive Industry specific
BODs—B2B Collaborations and
the associated Payloads;
Adopt/Adapt Industry
Standards when feasible
Map ebXML to SOA
DealerLocator
DealerLocator
Map To
AvailableVehicle Activity
Map To
DealerLocation Activity
DealerLocator
e.g., Map DealerLocation
Activity to the DealerLocator
Web service
Map To
VehicleHistory Activity
PurchaseRequest Activity
Map To
PurchaseApproval Activity
DealerLocator
1
Session 1543
Map To
[Business Error]
Business Analysts
map B2B
Transactions to the
services available in
Back-end Service
Oriented
Architecture (SOA)
When to Consider ebXML
• B2B or large A2A Environments—Extending or integrating
enterprise SOAs, or when loosely coupled messaging is desirable
• Need Reliable Messaging—When enterprise services perform
updates, insert, or deletes to the underlying data model, reliable
messaging becomes critical
• Security is a Concern—When different security profiles and
requirements exist between trading partners
• High scalability requirements—ebXML’s loosely coupled
messaging architecture allows for horizontal scalability, queueing,
and clustering
• Want to Leverage Industry Standards—XML grammars,
business process modeling and trading partner agreements
ASD
1
Session 1543
SOA Demo
Fred Falten, GM
Himagiri (Hima)
Mukkamala
Michael Wheaton,
ebXML RI at GM
Simulated (for conference)
Trading
Partner
GM
Test02
Test01
192.168.100.2
192.168.100.3
(OnLine 2000)
(OnLine 2000)
Router
Sun iForce Site
Digital Labs
GTM Lab on 27th Floor
Internet
Internet
sfepartner2
sfepilot01
•
sfetest01
192.168.100.1
192.168.100.100
(Windows 2000)
(Sun Solaris 8)
sfepartner
sfetest02
192.168.100.200
(IBM AIX 5.1)
192.168.100.52
199.228.84.80
(Sun Solaris 8)
(Sun Solaris 8)
Reference Implementation Overview
– Sale of used vehicles in volume
• Use vehicle selection profile to find matching inventory of offered sales
• Make an offer for each inventory vehicle of interest
• Purchase confirmed after offer evaluated and credit check completed
– Two applications leveraging the WS & J2EE™ components for
back-end services
1
• B2C application using JSP™
Session 1543 • B2B application with automated transactions using CPA & BPSS
ASD
ebXML RI at GM
Web Services Reference Implementation Demonstration
Live Monitoring of Server-side Invocations
ebXML Reference Implementation Demonstration
Business Activity Description
ASD
1
Session 1543
DEMO
Next Steps for SOA at GM
• Path forward for GM:
– 4Q2002:
• Enhance the RI:
– Throughput and performance benchmarks for
WS and ebXML
– Incorporate BODs into RI
• Standardize products and process for SOA:
–
–
–
–
Guidelines for integration (data vs. behavior)
Formalize the use of UDDI and Registry
Mentor WS and ebXML pilot projects
GM standards for choreography and collaboration
management
– Funding model accepted across IT divisions
ASD
1
Session 1543
Next Steps for SOA at GM
• Path forward for GM (Cont.):
– During 2003:
• Standards incorporated:
– Select standards for ‘Business Transaction Management’ for
ebXML and ‘XA’ for WS (WS-Transactions and OASIS BTP)
– Incorporate seamless security (WS-Security and ebXML Security)
– Expedite delivery of AIAG and STAR Core Components
• Modify GM’s development process:
– To optimize ROI of WS and collaborations created by Software Factory
– To leverage SOA reuse, integration, and migration in outsourced model
– To establish a enterprise, SOA team to manage the creation/reuse of:
» WS across each division of IT
» BPSS and CPP across trading partners
• Key Production Projects:
– Complete ebXML application with an existing Trading
partner using STAR BODS
1
Session 1543
ASD
Q&A
Fred Falten
General Motors
Aditya Thadani
General Motors
Hima Mukkamala Sybase
Mike Vella
Sun Microsystems
Mike Wheaton
Sun Microsystems
Service-Oriented Architectures
at General Motors
Mike Vella
Web Service Business
Development
SMI, Market Development
Engage the Web
Services Pilot
Team to advance
your business!