Overview of SOA For APA
Overview of SOA For APA
July 2012
Haiwei Chen
Agenda
12/3/2017
Application Development 2
Ford Motor Company IT
Agenda
Appendix
SOA definition by OASIS
Key principles of SOA
Web Services characteristics
When to create Web Services?
IBM DataPower and Microsoft BizTalk
Global SOA Program Scorecard (Jan 1st, 2012)
Case studies
References
12/3/2017
Application Development 3
Ford Motor Company IT
Global SOA Program
Established in 2008, with the goal of defining
processes, standards and best practices to identify,
build, and catalog reusable software assets
Is managed under Java Shared Services within AD
Having participants from AD NA, FoE and APA,
across different functional areas
ET Enterprise Architecture, Solution Architecture, Research
Java Center of Excellence
SOA Center of Excellence
Ford Credit
Key areas
Program Management and SOA Governance
Standards and Best Practices (aka Service Architecture)
SOA Infrastructure
12/3/2017
Application Development 4
Ford Motor Company IT
Global SOA Program Scorecard (July 1, 2012)
Savings ($000s)
Memo:
Potential (post-analysis) is measurement against target
since money is removed from projects at SEER estimate.
Agility
Memo:
Dev hours saved is calculated as potential 2012 development hours saved from re-use: 20,708 hrs
post-analysis savings/avg hourly rate ($48)
12/3/2017
Application Development 6
Ford Motor Company IT
Business Capability
Business Capability
defines what a business does or needs to do
to fulfill its objectives and responsibilities
not about how things are done or to be done
examples
Updating vehicle service history
Decoding VINs
Submitting warranty claims
Fulfilling vehicle orders
Note: in this presentation, when we say capability we mean business
capability.
12/3/2017
Application Development 7
Ford Motor Company IT
Service
Service
is an implementation of related capabilities;
exists as physically independent software and
can be used by applications via remote access.
12/3/2017
Application Development 8
Ford Motor Company IT
Web Services
Web Services
are services
are implemented by following Web Services
Interoperability standards
are commonly used to realize SOA
are current recommendation at Ford
12/3/2017
Application Development 9
Ford Motor Company IT
Whats different about SOA?
SOA focuses on Services
Services are building blocks for solutions;
Services are reusable across ownership boundaries.
12/3/2017
Application Development 10
Ford Motor Company IT
Case Study: Consumer Data Refinery
CDR Application in Marketing and Sales
supports inquiries, updates, and management of consumer
information, vehicle ownership, vehicle service history, service offers,
marketing promotion, etc.
capabilities (e.g. register consumer, update vehicle service history, retrieve
consumer contact info ) are implemented as reusable Web Services
LCS
(Consumer)
IP Firewall
IP Firewall
MSS360,
CDR
INRIX(SYNC) DataPower
(Provider)
(Consumer)
Owner Web
(Consumer)
Service Interfaces
DB2
Mainframe
Consumer
12/3/2017
Application Development 14
Ford Motor Company IT
Impact Analysis: VIN Decoder Service
With traditional approach
if VIN decoding and/or VINs are duplicated in multiple applications
adding fragmentation / redundancy to the enterprise yields no business value
integration with ELVIS DB2 SP via DB2 Connect
assuming consumer applications can make DB2 RPC call is a risk
letting ELVIS manage DB2 access control isnt a good design
changes are hard, esp. when the capability is expanded to support new
requirements (e.g. Ford Credit Wholesale Securitization)
tight coupling with use of DB2 leading to more integration effort and cost, esp. when
changes are needed
With SOA / Web Services
encapsulate the capability provided by Mainframe with a web service
the service is standard-compliant & supported by different vendor tools
consumers and provider communicate using XML-based messages
result: consumers and the provider interoperating natively makes integration easier
effort: SOA mindset; up-front collaborations/analysis among stakeholders; service-
oriented analysis and design; build and support the services
12/3/2017
Application Development 15
Ford Motor Company IT
Case Study: B2D Integration
High-level Requirement
Business interaction between Ford internal, dealer-facing
applications (OWS/LDS/) and Dealership/DMS
Need to support
A few thousand dealerships
Disparate systems at dealerships
Need loosely-coupled architecture to support changes
and interoperability
Solution based on SOA / Web Services
follows industry standards, not tying to particular vendor, platform
enables complex message exchange patterns
leverages service intermediary for common functions
12/3/2017
Application Development 16
Ford Motor Company IT
Impact Analysis: B2D Integration
With traditional approach
Huge challenges
Dealership / DMS may not want to take traditional approaches such as EDI, FTP, etc.
to interact with Ford internal systems
Use of VPN / ANX for communications may not be possible
high cost in delivering a viable solution
high risk for failure
SPS
IP Firewall
HTTP/HTTPS Security HTTPS/WSL
Dealer DMS DataPower BizTalk ESB OWS
LDS
Message
Store
12/3/2017
Application Development 18
Ford Motor Company IT
Case Summary: Whats different about SOA?
12/3/2017
Application Development 20
Ford Motor Company IT
Impact Analysis: Bill of Material Foundation
With traditional approach
continue to use various existing systems (AVBOM, PADB, WERS, )
different systems / platforms / interfaces providing same or similar capabilities
point-to-point interaction with different mechanisms
and integrate with the final, grand BOMF when it becomes available
integrating with BOMF means dramatic changes (tear-off) for consuming applications
not acceptable by business
With SOA / Web Services
taking an iterative / incremental approach
defining commonalities, i.e. business capabilities, for particular areas
creating services for those business capabilities
service interfaces are exposed, not the underlying systems, platforms
consumer applications have dependency on the interfaces, not service
implementations
both service consumers and service providers can evolve on their own, yielding
increased business and IT agility
effort: SOA mindset; up-front investment; service-oriented analysis and design;
potential for leveraging ESB functions; build and support services
12/3/2017
Application Development 21
Ford Motor Company IT
Case Study: Bill of Material Foundation
BOMF
Top Hat
user-centric applications focusing on UI, navigation, business process flow,
Platform
back-end providing underlying capabilities / solutions
Demand
/ Use
Interface
Supply
/ Solution
12/3/2017
Application Development 22
Ford Motor Company IT
Case Summary: Whats different about SOA?
App1 App2 AppN
Demands
Interface
Suppliers
12/3/2017
Application Development 28
Ford Motor Company IT
Appendix
12/3/2017
Application Development 29
Ford Motor Company IT
What is SOA?
12/3/2017
Application Development 30
Ford Motor Company IT
Key Principles of SOA
Explicit boundaries
Loosely coupled
Standards-compliant
Metadata-driven
Document-centric
Share interfaces, not implementations
Interface are resilient
Services are autonomous
12/3/2017
Application Development 31
Ford Motor Company IT
Web Services != SOA
Web Services
Standards-based, widely supported
Leading technology for implementing SOA
A in SOA is for Architecture
Characteristics such as Loosely Coupled, Sharing
Contracts not implementations,
Design principles and standards
SOA can be implemented without using Web
Services
Developing Services / Web Services here and there
does not necessarily lead to a successful SOA
12/3/2017
Application Development 32
Ford Motor Company IT
Web Service Characteristics
Has a well-defined service contract.
Service contract is exposed via implementation-independent
interface
Service interface is described in platform-neutral form.
Service interface exists as a physically decoupled architectural element.
More emphasis on service interface - Metadata is a First-
Class Citizen
Is Interoperable and standards based.
Is composable.
Service operations often need to be designed to exchange
document-centric messages, such as entire business
documents.
Messages are usually structured by XML schema.
12/3/2017
Application Development 33
Ford Motor Company IT
When to create Web Services?
Accessing functions across ownership boundaries
Supporting interactions between Ford and external vendors
Functions across line of business within Ford
Accessing functions across platform (technology,
language, implementation boundaries) to support
Interoperability.
Support data sharing without replication
Especially for data that often changes
Complex data model required for the function to operate
Supporting single version of truth
Underlying implementation of a function changes
frequently due to changes in business and / or technology
Functions that support / enable / require service
composition, transformation, orchestration by leveraging
infrastructure capability.
Business function, business process.
12/3/2017
Application Development 34
Ford Motor Company IT
DataPower & BizTalk Best Fit Analysis
Functionality DataPower BizTalk
Security Processing Use DP External for B2B WS security. Not suitable.
Ford Ford
MQ possible but not proven out. MQ common implementation in Ford..
FTP/SFTP possible but not ideal. FTP/SFTP possible but not proven
out.
Service Orchestration Not suitable. Well suited.
Rules Processing Not suitable. Has Rules Engine for lightweight rules
encoding.
Legacy Modernization Well suited but not proven out. Not preferred.
12/3/2017
Application Development 35
Ford Motor Company IT
BizTalk Capabilities
Microsoft BizTalk Server 2010 Capabilities
Protocol bridge
HTTP(S), SOAP, MQ, WCF, SQL, Oracle, DB2,
FTP(S), SharePoint, File, PeopleSoft, others
Message mediation
Message transformation
Message routing
Logic Orchestrations
DB Stored Procedures 23
KPI
% recommended as-is services is 52% (Does not
include non- SOAP items.)
Savings ($000s)
Memo:
Potential (post-analysis) is measurement against target
since money is removed from projects at SEER estimate.
Agility
Memo:
Dev hours saved is calculated as potential 2011 development hours saved from re-use: 56,500 hrs
post-analysis savings/avg hourly rate ($48)
LCS
(Consumer)
IP Firewall
MSS360, HTTP/HTTPS Security HTTPS/WSL
CDR
INRIX(SYNC) DataPower (Provider)
(Consumer) SFTP FTP
-- Transformation
-- Routing Owner Web
-- Protocol bridging (Consumer)
-- Central policy enforcement
-- X509 support
-- XML validation, XML threat protection
-- Message signing, encryption/decryption
12/3/2017
Application Development 42
Ford Motor Company IT
Case Studies
OWS / B2D Integration
High-level Requirement
Business interaction between Ford internal, dealer-
facing applications (OWS/LDS/) and Dealership/DMS
Example Use Case Requirements
DMS interacting with Ford internal apps
DMS invokes Ford internal function asynchronously
Ford invokes DMS function asynchronously
Guaranteed Delivery for messaging between DMS and
Ford
12/3/2017
Application Development 43
Ford Motor Company IT
Case Studies
OWS / B2D Integration
Solution
Exposing/Accessing capabilities via Web Services
Use DataPower as intermediary for
Security checking (AuthN, AuthA, en-/de-cryption, digital
signature, XML validation, )
Broker (X509 Certificate -- WSL Cookie; SFTP -- FTP)
Routing
Use BizTalk as intermediary for
Store/Forward
Routing
Asynchronous messaging
12/3/2017
Application Development 44
Ford Motor Company IT
Inbound Messaging
-- Perform AuthN
and Site-level AuthZ
with SPS (Security
Provisioning
Services)
SPS
IP Firewall
HTTP/HTTPS Security HTTPS/WSL
Dealer DMS DataPower BizTalk ESB OWS
Message
Store
12/3/2017
Application Development 45
Ford Motor Company IT
Outbound Messaging
-- Get DelivPref,
SiteURL, Cert for the
Site Code associated
with the message
SPS
IP Firewall
HTTP/HTTPS Security HTTPS/WSL
Dealer DMS DataPower BizTalk ESB OWS
12/3/2017
Application Development 46
Ford Motor Company IT
Case Studies
SOA Design Patterns Used
Synchronous and Asynchronous Messaging
Service Broker
Intermediate Routing
Async Queuing
Policy Centralization
12/3/2017
Application Development 47
Ford Motor Company IT
Case Studies
BOMF (Bill of Material Foundation)
Requirement
Managing BOM information
Addressing existing BOM fragmentation issues:
Multiple masters of BOM information each with its own interface
Conceptual differences in the data model for each system
Front-end tightly coupled with back-end solution
Performance concerns with some BOM tools
12/3/2017
Application Development 48
Ford Motor Company IT
Case Studies
BOMF - systems involved, integrated, or to be consolidated
PDBC PDBC
BOM Foundation BOM Foundation BOM Foundation BOM Foundation BOM Foundation
3Q
4Q
4Q
1Q
2Q
3Q
4Q
1Q
2Q
3Q
4Q
3Q
1Q
2Q
4Q
1Q
2Q
3Q
1Q
2Q
3Q
4Q
1Q
2Q
12/3/2017
Application Development 49
Ford Motor Company IT
Case Studies
BOMF (Bill of Material Foundation)
Top Hat
user-centric applications focusing on UI, navigation, business process flow,
Platform
back-end providing underlying capabilities / solutions
Demand
/ Use
Interface
Supply
/ Solution
12/3/2017
Application Development 50
Ford Motor Company IT
Case Studies
BOMF (Bill of Material Foundation)
Some of the Web Services (in PROD)
ProductStructurePart
ProductStructurePartUsage
ProductStructureLineOfUsage
ProductStructureLineOfPart
ProductConfigurationProductContext
Program
ProgramProductSystemResponsibility
ProductClassificationBaseConstituent
ProductClassificationCPSC
ProductClassificationCrossReference
12/3/2017
Application Development 51
Ford Motor Company IT
References
ITCN News: Ford IT improving application delivery and reducing complexity
http://www.itcn.ford.com/news/Pages/FordITimprovingapplicationdeliveryandreducingcomplexi
ty.aspx
Global SOA SharePoint site
https://comm.sp.ford.com/sites/soa/Pages/Default.aspx
SOA for Web Services Pattern 2012
https://www.lom.ford.com/launchomatic/download?objectId=0900cad980f06f5a&docbase=ed
msna1
Guide to Interoperability
https://www.lom.ford.com/launchomatic/download?objectId=0900cad980a92863&docbase=ed
msna1
Service Registry and Repository
https://www.sarr.ford.com/ServiceRegistry
DataPower SharePoint site
https://comm.sp.ford.com/sites/datapower/Pages/Default.aspx
BizTalk SharePoint site
https://team.sp.ford.com/sites/ESB/
12/3/2017
Application Development 52
Ford Motor Company IT