web services @ sap peter mcnulty, sap labs, llc sam tingleff, sap labs, llc sinisa zimek, sap labs,...

Web Services @ SAP

Peter McNulty, SAP Labs, LLCSam Tingleff, SAP Labs, LLC Sinisa Zimek, SAP Labs, LLC

Agenda

Introduction to WS-I

Approaching Web Services Interoperability

Overview and Deliverables

Technical Activities

2002 SAP Labs, LLC, Session ID, Speaker Name 4

The Context

Businesses need to innovate at an ever increasing pace

Success requires broad interoperability Within an enterprise Between business partners Across a heterogeneous set of platforms, applications, and

programming languages

Internet technologies are assumed, interoperability is required


The Situation

The shift to Web services is underway An Internet-native distributed computing model based on

XML standards has emerged Early implementations are solving problems today and

generating new requirements The Web services standards stack is increasing in size and

complexity to meet these requirements

The fundamental characteristic of Web services is interoperability


The Challenge

“[the] Architecture of Web services is not fully crystallized.Without guidance, standards may fragment”

Gartner Group, March 12, 2001

“Inevitably, companies involved with Web services will definethem in their own way. The term Web services will be a messycatchall phrase.”

Intelligent Enterprise, June 29, 2001

“standards…allow Web services to overcome the barriers ofdifferent programming languages, operating systems, andvendor platforms so multiple applications can interact.”

eWeek, August 13, 2001


The Opportunity

?

Interoperability will accelerate Web services adoption


What’s Needed?

Guidance A common definition for Web services Implementation guidance and support for Web services

adoption

Interoperability Across platforms, applications, and languages Consistent, reliable interoperability between Web services

technologies from multiple vendors A Standards Integrator to help Web services advance in a

structured, coherent manner

Agenda






Achieve Web services interoperability Across platforms, applications and languages

Encourage Web services adoption Among customers, industries and end users

Accelerate Web services deployment

WS-I Goals


WS-I Approach

Businesses Industry Consortia Developers End Users

Standards Bodies

Implementation Guidance, Best Practices

Specifications, Standards, Protocols Requirements, Feedback, Input

Requirements, Feedback, Input


Where WS-I Fits

Standards bodies produced standards

Implementers and Others consume them

Vendors interpreted and selected standards to implement

Often vendors in the same space selected different standards or implemented the same standards differently

The result was lack of interoperability

Prior WS-IPrior WS-I


Where WS-I Fits

Standards bodies (still) produce standards

Others (still) consume them

The Web Services community works within WS-I selecting, interpreting and implementing standards (= profiles)

Community members select the same standards and implement them the same way

The result will be improved interoperability

With WS-IWith WS-I

Agenda






Use CasesUsage

Scenarios

Scenariosand SampleApplications

ProfilesImplementationGuidance

TestingTools andMaterials

SampleApplications

Other TestMaterials

TestingTools

WS-I OverviewWS-I Overview


WS-I Deliverables

Application scenarios Solution scenarios based on customer requirements

Profiles Named groups of specifications at given version levels with

conventions about how they work together Implementation guidelines constrain how specifications are

used to achieve interoperability

Test suites and supporting materials Conformance testing tools Supporting documentation and white papers

Sample code from sample applications


Schedule for 2002

February 6 – WS-I Launch

March 5 – First WS-I Board Meeting (monthly meetings through 2002)

April 17 – First WS-I Community Meeting

4Q/02 –Basic Profile 1.0 Released

July 24 – Second WS-I Community Meeting

Nov 5 – Third WS-I Community Meeting

Today approx. 133 Members

Agenda






WS-I Working Groups

WS Basic Profile Working Group

WS Basic Sample Apps Working Group

Testing Working Group

Charters available on WS-I web site http://www.ws-i.org/documents.aspx

Technical Coordinating Group (TCG) Board Committee Cross Working Group Forum


Basic ProfilesWorking Group

• Usage of Public Specification, e.g. SOAP, WSDL, UDDI etc.

• Implementation Guidelines

• Initial Test Conditions

• Sample ScenariosSample ApplicationsWorking Group

• Functioning Applications

• Support Documentation

• Application Test Cases

Test Materials & ToolsWorking Group

• Test Tools• Testing

Methodology• Technical Test

Cases

Basic profiles,Scenario definitions,Implementation guidelines

Public specifications,Implementation guidelines,Initial test conditions

Test ToolsTechnical Test Cases

Lead:Lead:

Lead:

Working Groups & Relationship


Sample Applications Working Group

Identify and Validate usage scenarios

Architect a real world application Develop business use cases Define the application Model Architect the application

Co-Develop test plan and scripts

Implement sample applications Different plat forms, programming languages Using scenarios and use cases


Usage Scenarios

Usage Scenario descriptions Actors & Roles Scenarios Constraints

Validation of Basic Profiles Test Tools Application Architecture

Best Practice for Profiles usage

WS-I White Paper


Basic Profiles Working Group

Develop the Basic Profile specification

Identify and resolveIssues and Ambiguities Interoperability issues due to the extensibility and optional

features of underlying specs

Make methodically Choices remove optional features by making decisions onoptions E.g., SOAP action, use of cookies,

document vs RPC, literal vs encod., etc.


A list of specifications SOAP 1.1 HTTP XML 1.0 WSDL 1.1 XSD 1.0 UDDI 2.0

Subsets and guidance materials based upon those specifications

What is the Basic Profile?


Test Working Group

Identified Testing requirements for the underlying specifications and protocols E.g., HTTP, SOAP, WSDL, etc.

Define an initial set of Test Cases

Develop initial designs for the tools Monitor Logger Analyzer

Implement prototypes for these three tools


UserApplication

Or WS

Web Service

Logfile

MONITOR

ANALYZER Report

Test Tools Overview (Simplified)


Conformance with WS-I Profile Requires exhaustive testing of operations, under various

conditions (e.g. errors, etc.) Normally requires a Test Driver

Conformance does not guarantee Interoperability (!) It is a pre-requisite Allows Certifying separately a WS and its deployment platform,

prior to actual use

Conformance Testing


Interoperability Testing will be a Routine Operation As Business Partners independently upgrade their

systems and Web services Must be easy to use and deploy

Context of Testing Logistics more complex to coordinate and organize Failure may originate on either side

Interoperability Testing


Call to Action

Join Community of 140+ industry leaders and visionaries in

sharing a vision for Web services interoperability Foster commitment across the community

Participate Encourage customer participation and buy-in Commit to an aggressive delivering schedule to aid

Web services implementations

Comply Ensure conformance with WS-I profiles Promote adoption to customers and partners


Q&A

Questions?

web services @ sap peter mcnulty, sap labs, llc sam tingleff, sap labs, llc sinisa zimek, sap labs,...

Documents

web services technologies

web services adoption

web services advance

standardsallow web services

architecture of web

term web services

web services standards

sap labs