Driving Standards
for Enterprise 2.0
The Fast Track to SAP Knowledge
David Keene
david.keene@sap.com
Vice President Platform Technologies
SAP EMEA
AGENDA
The Business Case for Standards
Role of Enterprise SOA
Technology Standards
Business Standards
Standards Development
Conclusion
 SAP
AG 2007,to
OASIS
Conference
/2
The Fast
Track
SAP
Knowledge
When Should A Vendor Embrace A Standard?
A Specification
+
An acknowledgement
+
Wide acceptance
 SAP AG 2007, OASIS Conference / 3
In Return What Do We Get?
Turn Innovation Into Industry Best
Practice
Focus On Value-Add
EcoSystem To Innovate
 SAP AG 2007, OASIS Conference / 4
Where Is The Differentiation?
Invest in differentiating
competitive features
Efficiency and automation
 Buy standard software
Innovate and differentiate
 Better support customers
 Provide complete solutions
and services
 Extend business networks
 Decrease time-to-value
– Best practices, compliance
– Conformance to standards
 Lower TCO
– Ensure data accuracy
– Increase level of automation &
productivity
– Leverage open source
software in commodity areas
 Leverage business process
flexibility
De-invest in
non-differentiating features
 SAP AG 2007, OASIS Conference / 5
The SAP View Of Standards
Interoperability is achieved by standards, supports the
seamless exchange and use of business information and
significantly lowers cost-of-integration
Semantic Interoperability
Applications understand and correctly
use the information being exchanged
Process
Component
Process
Component
Service
Infrastructure
Service
Infrastructure
Technical Interoperability
Systems are connected and can
exchange information
 SAP AG 2007, OASIS Conference / 6
Driving A Reference Architecture for Enterprise Software
Degree of differentiation
Software layer
Business value
Composite
Applications
Industry Next Practices, Business Process
Flexibility, Customer Innovation, Monitoring
Process
Components
Industry Best Practices, Business Process
Integrity, Compliance
Service
Infrastructure
Connectivity, Distribution, Productivity,
Interoperability
Database
Operating
System
 SAP AG 2007, OASIS Conference / 7
Data Integrity, Reliability, Security,
Scalability, Performance
AGENDA
The Business Case for Standards
Role of Enterprise SOA
Technology Standards
Business Standards
Standards Development
Conclusion
 SAP
AG 2007,to
OASIS
Conference
/8
The Fast
Track
SAP
Knowledge
Role Of Standards in Enterprise SOA
Business
Standards
Web
Services
Standards
Enterprise
Services
Community Definition
Group for Banking
Product Standards
 SAP AG 2007, OASIS Conference / 9
Productising Interoperability Across All Layers
Enterprise Services
 Are implemented by means of an open, standards-based technology
(Web services standards)
 Provide standardized business connectivity
 Are used for virtually all types of application integration scenarios
Supplier
Customer
Composite
Application
A2X
Process
Component
Service
Infrastructure
Enterprise Service
A2A
Process
Component
Service
Infrastructure
A2X Composite-to-Application
 SAP AG 2007, OASIS Conference / 10
B2B
A2A Application-to-Application
Process
Component
Service
Infrastructure
B2B Business-to-Business
AGENDA
The Business Case for Standards
Role of Enterprise SOA
Technology Standards
Business Standards
Standards Development
Conclusion
 SAP
AG 2007,to
OASIS
Conference
/ 11
The Fast
Track
SAP
Knowledge
Technology Standards Are A Key Foundation
Interoperability
 enables separately-designed
artifacts to be plugged together
Component
Platform A
Component
Platform B
Common
Interface
designed artifacts as part of a
larger suite of components or
services
Common
Interface
 enables easy use of separately
Common
Interface
Integration
Component
Platform B
Platform A
Sending
Component
Receiving
Component
Portability
 enables to write components
once and run them everywhere
Platform B
Platform A
Component
Component
 increases developer
productivity through a reduced
learning curve
 SAP AG 2007, OASIS Conference / 12
Component
Role of Web Services Standards
Basic Interoperability Requirements
 Exchange messages reliably
– Guaranteed message delivery (at least once)
– Duplicate elimination (at most once)
– Message sequence (ordering)
 Exchange messages securely
– Confidentiality (encryption)
– Integrity, non-repudiation (digital signatures)
Sending
Component
Receiving
Component
Send
Deliver
Source
Infrastructure
 SAP AG 2007, OASIS Conference / 13
Acknowledge
Destination
Infrastructure
BPM – Where Is The Process?
 SAP contributes to, defines and embraces BPM industry standards in several areas
 BPM standards aim to achieve:
– Interoperability (seamless integration, eliminate point-to-point integration)
– Portability of process definitions
 SAP embraces and supports BPMN since it enables business process modeling, agnostic
from the execution language, elevating modeling into the business domain
Business Process
Management Standards
 Human Centric Processes
 BPMN 1.1 for composite business processes
 BPMN-to-execute
 Drive further evolution (BPMN 2.0)
 WS-HumanTask planned
 System Centric Process
 BPEL4WS 1.1
 WS-BPEL 2.0 preview and implementation
 BPEL4People planned
 SAP AG 2007, OASIS Conference / 14
SCA = Future Neutral Reference
 SCA – Service Component Architecture
 Language-neutral programming model for SOA applications
 Not meant to replace or compete with any existing programming model
 SCA defines syntax and semantics for
 service component construction
 service component assembly
 deployment
 Service components can be bound to whichever technology specifc
implementation you choose
 Started as the Open SOA industry initiative in 2005 (BEA, IBM, Oracle &
SAP)
 Submitted to OASIS in 2007 for standardization within the Open
Composite Services Architecture (CSA) Member Section
 SAP AG 2007, OASIS Conference / 15
Key SAP Technology Standards Adoption
WS-BPEL, BPEL4People
Platformspecific
Platform-independent
Business Process Management
SCA, SDO
Componentization
CIM, WS-Management
Management
SOAP, WSDL, UDDI, WS-ReliableMessaging,
WS-Security, SAML, WS-Policy, WS-I Profiles,
etc.
Web Services
Java EE
Java
platform
 SAP AG 2007, OASIS Conference / 16
Java EE, ABAP
SAP NetWeaver
.NET
Microsoft
Web Services Standards Stack (WS-I View)
Additional
Capabilities
Management
Business
Process
Orchestration
Composable
Service
Elements
Portals
Composition/Orchestration
Security
(WS-Security,
WS-SecureConversation,
WS-SecurityPolicy)
Reliable
Messaging
(WS-ReliableMessaging,
WS-RM Policy)
Transactionality
Messaging
Endpoint Identification (WS-Addressing), Publish/Subscribe
Description
XML Schema, WSDL, UDDI, WS-Policy
Invocation
XML, SOAP
Transports
HTTP, HTTPS, Others
 SAP AG 2007, OASIS Conference / 17
The SOA Security Standards Stack
Security
Services
SPML
WS-Trust
WS-Policy
Interoperability
WS-Security
Message
Security
WS-Security
Policy
SOAP Message
Security
WS-Secure
Conversation
RELToken
Token
REL
Security
Token
Profile
Profile
Profiles
Document
Security
Transport
Layer
Security
 SAP AG 2007, OASIS Conference / 18
XML
Signature
XML
Encryption
SSL/TLS
WS-Policy
Attachment
Security
Metadata
WS-I
Basic
Security
Profile
Java EE 5 in the SAP NetWeaver Application Server
SAP NetWeaver Application Server 7.1 Java EE 5
Common annotations for the Java platform
Database Access
Business Logic
EJB 3.0
Java Persistence API 1.0
Web Services & XML
User Interface
JAX-WS 2.0
JAXB 2.0
StAX 1.0
SAAJ 1.3
 SAP AG 2007, OASIS Conference / 19
Web Service
Metadata
for the Java
Platform
JSP 2.1
JSTL 1.2
Servlet 2.5
JSF 1.2
AGENDA
The Business Case for Standards
Role of Enterprise SOA
Technology Standards
Business Standards
Standards Development
Conclusion
 SAP
AG 2007,to
OASIS
Conference
/ 20
The Fast
Track
SAP
Knowledge
Business Standards = Enterprise Services B2B Interoperability
SAP is a leader in defining business standards in over 24 vertical
industries – these standards are a key part of SAP business
solution maps
 SAP, partners and customers are
actively engaged in many B2B
industry consortia
 Industry Value Networks of
partners and customers are
defining industry best practices
 ES Community Definition Groups
are driving precise standards
requirements into new enterprise
services
 Knowledge from Business Process
Expert Community leverages
business standards
 SAP AG 2007, OASIS Conference / 21
Role of Business Standards
Interoperability Requirements
 Data
– The message content can be correctly interpreted
 Process
– The business context is accurately understood
– Business transactions have a common definition
– Choreography of messages supports the business needs
 Organization
– Workflow mechanisms are established so that necessary approval steps and
error resolutions can be triggered seamlessly
Sending
Component
 SAP AG 2007, OASIS Conference / 22
Receiving
Component
Value Of Business Standards
Business Standards
 Represent the necessary business contracts between process
components
 Allow the individual development and provisioning of process
components and composite applications
 Guarantee process integrity and flexibility as long as contractual
obligations are adhered to
 SAP AG 2007, OASIS Conference / 23
Standards Alignment Enhances Cross-Industry Collaboration
Customers
Participate in
Considers
Communities
Co-specify
Content
(Message and
Data Types)
A2X A2A B2B
Is mappable
A2A
B2B
Conforms to
Conformance
 SAP AG 2007, OASIS Conference / 24
Core Component Type Specification (CCTS)
The Three Areas That Need Further Standardization
Key requirements
Approach
“Service-orientedness”
Are there the services I
need? Can they be
reused?
Governance
 Co-innovation
 Portfolio management
 Rules for identifying and
developing the right services
Integration by design
How can the services be
orchestrated? Do they
use the same data types?
Resilience to changes
How can I increase
business process
flexibility while retaining
business process
integrity?
 SAP AG 2007, OASIS Conference / 25
Process
Component
Service design patterns
 Interactions, e.g., request-confirmation
 Operations, e.g., standard query signature
 Data types, e.g., core data types (ID vs.
Name)
Change management
 Compatibility
 Rules for provisioning of and
adapting to changes
Process
Component
Composite
Application
Process
Component
Service V2
Service V1
Rel. N Rel. N+1
AGENDA
The Business Case for Standards
Role of Enterprise SOA
Technology Standards
Business Standards
Standards Development
Conclusion
 SAP
AG 2007,to
OASIS
Conference
/ 26
The Fast
Track
SAP
Knowledge
SAP Works Across All Standards-Setting Organizations
World-Wide Web Consortium (W3C)
 Founded in 1994 - more than 400 members
 Mission: To lead the World Wide Web to its full potential by
developing protocols and guidelines that ensure long-term growth
for the Web
 Important standards: HTTP, MTOM, SOAP, WSDL, WS-Addressing,
WS-Policy, XML, XML Encryption, XML Schema, XML Signature
Organization for the Advancement of
Structured Information Standards (OASIS)
 Founded in 1993 (as SGML Open) – more than 500 members
 Mission: to drive the development, convergence, and adoption of
open standards for the global information society
 Important standards: SAML, SPML, UDDI, WS-BPEL, WSReliableMessaging, WS-SecureConversation, WS-Security, WS-Trust
Web Services Interoperability Organization (WS-I)
 Founded in 2002 – more than 130 members
 Charter: to promote Web services interoperability across platforms,
operating systems and programming languages
 Important standards: Basic Profile, Basic Security Profile
 SAP AG 2007, OASIS Conference / 27
Actors in Standardization
Specifications
Test cases
IPR declarations
Standards Body
Technical
contributions
(may contain IPR)
IPR
declaration
Agree on common
denominator
Implementation
feedback
Implementers
Developers
Product/Services
Sales
IP licensing
Prototypes
 SAP AG 2007, OASIS Conference / 28
Requirements
Products
Conformance
Claims
Conformance /
Interoperability
issues
Users
And Sponsors The Enterprise Services Community
Collaborative Process
Roadmap-Driven Track
SAP’s plans to service-enable
mySAP Business Suite
DECIDE
Necessary
but not obvious
Confirmation
of SAP plans
Prioritize,
considering
dependencies
Long
List
Select
Short
List
use cases
Stakeholder-Driven Track
quarterly
Customers / partners
deciding how SOA drives
business value
Breakthrough
innovations
Committed Outcome
DEFINE
collaboratively
DEVELOP
DELIVER
DEPLOY
semi-annually
on mySAP ERP 2005
SAP
Architects
ES bundles
Community Definition Groups
 SAP AG 2007, OASIS Conference / 29
DECLARE
AGENDA
The Business Case for Standards
Role of Enterprise SOA
Technology Standards
Business Standards
Standards Development
Conclusion
 SAP
AG 2007,to
OASIS
Conference
/ 30
The Fast
Track
SAP
Knowledge
Standards Leadership
SAP holds governance roles in important
standards organizations
 OASIS (Board), WS-I (Founder, Chair and Board)
 JCP (Board), Eclipse (Founder, Board)
SAP leads the standards development for
key technologies
 OASIS UDDI, WS-BPEL, WS-ReliableMessaging,
SCA/SDO
 W3C WS-Addressing and WS-Policy
 WS-I Sample Application
 OMG BPMN
 UN/CEFACT CCTS & XML Naming and Design Rules
 BPEL4People
SAP runs the ES Community to co-innovate
enterprise services with customers and
partners
 200+ members
 35+ community definition and advisory groups
The Fast Track to SAP Knowledge
 SAP AG 2007, OASIS Conference / 31
Standards Compliance
SAP supports key technology standards as
building blocks for enterprise SOA adoption
 SOAP, WSDL, UDDI
 WS-Security, SAML, WS-ReliableMessaging, WSSecureConversation, WS-Addressing, WS-Policy
 WS-I Profiles and Sample Apps
 WS-BPEL and BPEL4People
 Java EE 5, EJB 3.0
 Eclipse IDE
 SCA, SDO
 MOF, XMI, JMI, CWM
 OSGi Service Platform
The Fast Track to SAP Knowledge
 SAP AG 2007, OASIS Conference / 32
SAP takes a holistic view of standards where
business value is the primary driver
SAP is fully committed to and drives technical and
business standards that
 Provide for increased technical and semantic interoperability
 Streamline the implementation of enterprise SOA
SAP runs on and integrates mature open source
software, which enables customers to
 Leverage community innovation
 Reduce costs by capitalizing on mature commodity
infrastructure
and use these savings to re-invest in innovation
 Increase flexibility with regard to IT infrastructure choices
 SAP AG 2007, OASIS Conference / 33