Service-Oriented Architectures

at General Motors

Mike Vella
Web Service Business Engage the Web
Development Services Pilot
Team to
advance your
SMI, Market business!

Development
 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
 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 large-
scale B2B
– Explain the architecture for ebXML
– Witness the operation of an ebXML
Reference Implementation

ASD

1 Session 1543
 Services-Oriented
Architecture Strategy
ebXML Typical access via:
Demo
B2B Market,
Global Multi- SOAP/HTTP ebXML
enterprise ebXML Demo
(JAX-M for ebXML)
SOAP/HTTP
Big A2A Web Services (JAX-M for WS-Routing)
Integrated App for XML Message
Families SOAP/HTTP WS
Web Services
(JAX-RPC) Demo
Small A2A for RPC
Integrated ORB WS
WS Apps (RMI/IIOP) Demo
Demo Reusable
Homogeneo Components
us Granularity
Application
Tight Looser
er
Coupling
Limit Extensiv
ed
Security e ASD

1 Session 1543
 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 ASD
software development vendors
1 Session 1543
 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 ASD

1 Session 1543
 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:
– J2EE—Component Model
– Basic Web Services (SOAP, WSDL, UDDI)—Services Layer
– ebXML—Expose SOA to trading partners
● 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

1 Session 1543
 ebXML Architecture
Modules
● 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 complete
specification with available implementations to extend
an SOA to trading partners

1 Session 1543
 ebXML Architecture at
GM
Trading Partner
Private/Public
Collaboration GM
Descriptions
ebXML
Registry
Repository
Find Publis
h
Primarily Design, BPSS
Develop Time CPP/A
Negotiate
Des/Dev/Dep Time WSApp
Run Time CPA Mapping

Converse
BPML ebXML MSH Transport ebXML BPML
App Business Service Business Service App
Interface B2B Collaboration Interface
BPSS/CPA
- - J2EE
WS/J2E -
E CORBA
- -
Legacy Legacy
- COTS - COTS
1 - Etc.
Session 1543 - Etc.
 XML Document
Management
ebXML REGREP
Registry
●
XML Registry +
Repository Interface Life Cycle Query
●
Life cycle Soap Manager Manager
management
features AuthenticationSecurity Persistence
●
Query management Authorization Manager Manager
engine
●
Security features Repository
includes digital
signatures, user Ids Database with RIM
Extrinsic
●
Classification of any Registry
Objects
Organization Objects
type of object BPSS, CPA, CC

1 Session 1543
 ebXML Architecture
Details
DMZ Lega
B2B—
Tradin EJB cy
Internet

Interna Business Apps

g l
Partne Firewal Services
r l
EJB
Business DB
ebXM Services
ebXM ebXML ebXM

SOA Facade
L
L SOAP L Proce
BSI MSH ss Orchestration
Serve Services
r J2EE
Business Application
Process Server
J2EE Collaborati COTSContainer
Apps Lega
Web on
cy
Apps

Containe Apps
r

CP BPS
A S
1 Session 1543
 Extending SOA With
ebXML GM
Portal Architecture

Integration Services
EJ Lega
Web B cy
Interna Service Apps
l
Browse Firewal EJB
r l
EJB
Servle Business DB
Internet

ts Services

Web Services
JSPs

Facade
Security
B2B— BPSS Services Orchestration
Tradin Collaborati Services
g on J2EE
Partne Application
r ebXM ebMS ebXM Server
ebXM L COTSContainer
L L Proce Apps Lega
BSI MSH ss cy
J2EE Apps
Serve
Apps

Web
Containe r
r
CP BPS
A S
1 Session 1543
ebXML Implementation @ GM

Himagiri (Hima)
Mukkamala Sybase
 Business Collaboration
(BPSS)
Power Designer Creates BPSS

AvailableVehicle
Activity
<<BusinessTransactionActivity>>
Available Vehicle Activity
The B2B
DealerLocation Collaboration may
Activity
<<BusinessTransactionActivity>>
be composed of
Dealer Location Activity
several business
transactions
VehicleHistory
Activity
<<BusinessTransactionActivity>>
The resulting
VehicleHistory Activity
PurchaseRequest sequence is
Activity
<<BusinessTransactionActivity>> captured in a BPSS
Vehicle Purchase Request Activity
PurchaseApproval
Activity
<<BusinessTransactionActivity>>
VehiclePurchase Approval Activity

[Business Error]

1 Session 1543
 Business Transaction
Definition
Messaging Reliability

AvailableVehicleQuery
Document

Request ReceiptAck Respond

Available AcceptanceAc Available
Vehicle k
AvailableVehicleResponse
Document Vehicle
ReceiptAck
[Technical Error]
[Business Error]

Technical Error
Business Error Business Transactions define
reliable messaging exchange
between the two trading
partners using
acknowledgments, error
handling, logging and roles
1 Session 1543
 Trading Partner
Agreement
Power Designer
(CPA)
<<BinaryCollaboration>>
Bulk Buying

Bulk Used General Motors

Car Buyers
Trading Partner BusinessBulk Buying
Agreement Specifies ProcessBusiness Process
(CPA) Specifications
(BPSS)
Contains
Check Vehicle Availability
Business Dealer Location
TransactionsVehicle History
Submit PO
Contains

XML
DTDs
Messages
Grammars

1 Session 1543
 Trading Partner
Agreement (CPA)
Web Services Integrator Manager

1 Session 1543
 Manage Industry
Standard Payloads
STARXML has defined
Automotive Industry
specific BODs—B2B
Collaborations and the
associated Payloads;
Adopt/Adapt Industry
Reg/Rep helps
Standards when feasible
manage
BPSS, CPP, CPA,
BODs
and their
associations

1 Session 1543
 Map ebXML to SOA
DealerLocator

DealerLocator
Map To

AvailableVehicle
Map To
Activity
DealerLocation Activity
DealerLocator
e.g., Map DealerLocation
Activity to the
DealerLocator Map To
Web service Business Analysts
VehicleHistory Activity
PurchaseRequest Activity map B2B
Transactions to
Map To the services
PurchaseApproval Activity available in Back-
end Service
Map To [Business Error] Oriented
DealerLocator
Architecture
(SOA)

1 Session 1543
 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
GM Partner

Test01 Test02
192.168.100.2 192.168.100.3
(OnLine 2000) (OnLine 2000)
Sun iForce Site
Router GTM Lab on 27th Floor Digital Labs

Internet Internet
sfepartner2
199.228.84.80
sfepilot01 sfetest01 sfetest02 sfepartner
192.168.100.1 192.168.100.100 192.168.100.200 192.168.100.52 (Sun Solaris 8)
(Windows 2000) (Sun Solaris 8) (IBM AIX 5.1) (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 ASD
• B2C application using JSP™
1 Session 1543 • B2B application with automated transactions using CPA & BPSS
 ebXML RI at GM
Web Services Reference Implementation Demonstration ebXML Reference Implementation Demonstration
Live Monitoring of Server-side Invocations 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 ASD
partner using STAR BODS
1 Session 1543
 Q&A
Fred Falten General Motors
Aditya Thadani General Motors
Hima Mukkamala Sybase
Mike Vella Sun
Microsystems
Service-Oriented Architectures
at General Motors

Mike Vella
Web Service Business Engage the Web
Development Services Pilot
Team to
advance your
SMI, Market business!

Development