ServiceOriented Architectures at General Motors Mike Vella Web

Service-Oriented Architectures at General Motors Mike Vella Web Service Business Development SMI, Market Development 1 Session # 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 – ● Web Service Business Issues – – ● Resolve IT department bottlenecks Enhance Cost Efficiency with existing infrastructure Web Services Economic model evolves – 1 Open Standards are making progress 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 Session #

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 1 Session #

WS Pilot Value Proposition ● ● ● 1 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-ofbreed technologies and products to our Session #

Presenters Are: ● ● ● 1 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 Web. Services Architect/Strategist for Sybase e-Business division Session #

Service-Oriented Architectures at General Motors Fred Falten Director of Applications Architecture and Integration for IS&S General Motors Corporation 1 Session #

Service-Oriented Architectures at General Motors Understand how GM is using eb. XML to extend SOA and enhance B 2 B for the Automotive Industry 1 Session #

Learning Objectives ● As a result of this presentation, you will be able to: – – 1 Session # Understand the business benefits of SOA Exploit the cumulative features of Web Services and eb. XML to meet very largescale B 2 B Explain the architecture for eb. XML Witness the operation of an eb. XML Reference Implementation

Services-Oriented Architecture Strategy eb. XML Demo. B 2 B Market, Global Multienterprise Big A 2 A Integrated App Families WS Demo Small A 2 A Integrated Apps Homogeneou s Application Typical access via: eb. XML Session # SOAP/HTTP (JAX-M for WS-Routing) Web Services for XML Message Web Services for RPC Reusable Components Tighter Limite d 1 eb. XML SOAP/HTTP (JAX-M for eb. XML) Demo SOAP/HTTP (JAX-RPC) WS Demo ORB (RMI/IIOP) WS Demo Granularity Coupling Security Looser Extensive

SOA Benefits for GM ● Support Business Agility – – ● 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 – 1 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 – Session # Loose coupling improves availability and recovery for global distributed systems Core set of thoroughly tested, highly-available services

SOA Benefits for GM ● IT Cost Savings – Accomplish more with development budget ● ● – 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: ● – 1 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 Session # J 2 EE™ + Web. Services + eb. XML Increased competition among product vendors and software development vendors

Software Factory Enabler Project ● ● ● Purpose: Define GM’s Application Architecture and IT Standards for SOA; Evangelize Deliverables: Reusable Architectural Patterns and RI for Web. Services and eb. XML; 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: – – – 1 Session # Mostly outsourced to Software Factories Buy before build; committed to open standards Legacy is dominant; most new development is for the J 2 EE™ platform

eb. XML Applications at GM ● GM Approved XML Standards (Q 1 2002) – – ● – – 1 XML Business Document Standard B 2 B XML Technical Standard Application categories: – ● OAG BODs: eb. XML: Dealers: Inventory mgmt. , financial data, parts On. Star: Vehicle on-board services Supply Chain: Purchasing and OTD Engineering Suppliers: Global concurrent engineering Finance: Loan/lease collaboration with branches Kicked off GM-Covisint B 2 B XML integration pilot using eb. XML MSH (Q 2 2002); Target completion in Q 3 2002 Session #

eb. XML Architecture @ GM Michael Wheaton Sun Microsystems Inc. 1 Session #

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 J 2 EE—Component Model Basic Web Services (SOAP, WSDL, UDDI)—Services Layer eb. XML—Expose SOA to trading partners

eb. XML 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 eb. XML Registry and Repository—B 2 B Document Management System Complete B 2 B web services framework—A ●Session 1543

eb. XML Architecture at GM Private/Public Collaboration Descriptions Trading Partner Find eb. XML Registry Repository Primarily Design, Develop Time Des/Dev/Dep Time App 1 WS/J 2 E E - Legacy - COTS - Etc. WS App Mapping Converse eb. XML BPML MSH Transport Business Service B 2 B Collaboration Interface BPML Session 1543 Publis h BPSS CPP/A Negotiate CPA Run Time GM BPSS/CPA App - J 2 EE - CORBA - Legacy - COTS - Etc.

XML Document Management eb. XML REGREP ● ● ● 1 Registry XML Registry + Interface Life Cycle Repository Query 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 Extrinsic Registry Organization Objects BPSS, CPA, CC Classification of any type of object Session 1543

eb. XML Architecture Details Apps eb. XML SOAP MSH J 2 EE Web Container CP A 1 Session 1543 EJB Business Services Internal Firewall eb. XML Proces s Server Business Process Collaboratio n BPS S SOA Facade eb. XML BSI DMZ Internet B 2 B— Tradin g Partner EJB Business Services Orchestration Services J 2 EE Application Server Container COTS Apps Legac y Apps DB

Extending SOA With eb. XML Portal Apps 1 Session 1543 Internet eb. MS Servlet s JSPs BPSS Collaboratio n eb. XML MSH J 2 EE Web Container CP A Security Services eb. XML Proces s Server BPS S Web Services Facade Internal Firewall Browser B 2 B— Tradin g Partner eb. XML BSI EJ Web B Service EJB Business Services Integration Services GM Architecture Orchestration Services J 2 EE Application Server Container COTS Apps Legac y Apps DB

eb. XML Implementation @ GM Himagiri (Hima) Mukkamala Sybase 1 Session #

Business Collaboration (BPSS) Power Designer Creates BPSS Available. Vehicle <<Business. Transaction. Activity>> Activity Available Vehicle Activity Dealer. Location <<Business. Transaction. Activity>> Activity Dealer Location Activity Vehicle. History Activity <<Business. Transaction. Activity>> Vehicle. History Activity Purchase. Request <<Business. Transaction. Activity>> Activity The B 2 B Collaboration may be composed of several business transactions The resulting sequence is captured in a BPSS Vehicle Purchase Request Activity Purchase. Approval <<Business. Transaction. Activity>> Activity Vehicle. Purchase Approval Activity [Business Error] 1 Session 1543

Business Transaction Definition Messaging Reliability Available. Vehicle. Query Document Request Available Vehicle Receipt. Ack Acceptance. Ack Available. Vehicle. Response Document Respond Available Vehicle Receipt. Ack [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 <<Binary. Collaboration>> Bulk Buying Bulk Used Car Buyers General Motors Trading Partner Specifies Agreement (CPA) Business Process Specifications (BPSS) Contains Business Transactions Bulk Buying Business Process 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—B 2 B Collaborations and the associated Payloads; Adopt/Adapt Industry Standards when feasible

Map eb. XML to SOA Dealer. Locator Map To Available. Vehicle Activity Map To Dealer. Location Activity Dealer. Locator e. g. , Map Dealer. Location Activity to the Dealer. Locator Web service Map To Vehicle. History Activity Purchase. Request Activity Map To Purchase. Approval Activity Dealer. Locator 1 Session 1543 Map To [Business Error] Business Analysts map B 2 B Transactions to the services available in Back-end Service Oriented Architecture (SOA)

When to Consider eb. XML ● ● ● 1 B 2 B or large A 2 A 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—eb. XML’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 Session #

SOA Demo Fred Falten, GM Himagiri (Hima) Mukkamala Michael Wheaton, 1 Session #

eb. XML RI at GM Simulated (for conference) Trading Partner GM Test 02 Test 01 192. 168. 100. 2 (On. Line 2000) Router 192. 168. 100. 3 (On. Line 2000) Sun i. Force Site Digital Labs GTM Lab on 27 th Floor Internet sfepartner 2 sfepilot 01 192. 168. 100. 1 (Windows 2000) ● 192. 168. 100 (Sun Solaris 8) sfetest 02 192. 168. 100. 200 (IBM AIX 5. 1) sfepartner 192. 168. 100. 52 199. 228. 84. 80 (Sun Solaris 8) Reference Implementation Overview – Sale of used vehicles in volume ● ● ● – ● Session # 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 & J 2 EE™ components for back-end services ● 1 sfetest 01 B 2 C application using JSP™ B 2 B application with automated transactions using CPA & BPSS

eb. XML RI at GM Web Services Reference Implementation Demonstration Live Monitoring of Server-side Invocations 1 Session # eb. XML Reference Implementation Demonstration Business Activity Description

DEMO 1 Session #

Next Steps for SOA at GM ● Path forward for GM: – 4 Q 2002: ● Enhance the RI: – – ● Standardize products and process for SOA: – – – 1 Session # Throughput and performance benchmarks for WS and eb. XML Incorporate BODs into RI Guidelines for integration (data vs. behavior) Formalize the use of UDDI and Registry Mentor WS and eb. XML pilot projects GM standards for choreography and collaboration management Funding model accepted across IT divisions

Next Steps for SOA at GM ● Path forward for GM (Cont. ): – During 2003: ● Standards incorporated: – – – ● Select standards for ‘Business Transaction Management’ for eb. XML and ‘XA’ for WS (WS-Transactions and OASIS BTP) Incorporate seamless security (WS-Security and eb. XML 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: ● ● 1 Session # ● WS across each division of IT BPSS and CPP across trading partners Key Production Projects:

Q&A Fred Falten General Motors Aditya Thadani General Motors Hima Mukkamala Sybase 1 Mike Vella Sun Microsystems Mike Wheaton Sun Microsystems Session #

Service-Oriented Architectures at General Motors Mike Vella Web Service Business Development SMI, Market Development 1 Session # Engage the Web Services Pilot Team to advance your business!