Web Service Interoperability

Harcharan Jit Singh

ME CSE
820932001

1
 Agenda

 Why is Web services interoperability important?

 The evolution of the Web services “stack”
 An introduction to WS-I
 What does WS-I do?

2
The Web Services Context

• Complex, heterogeneous infrastructures

• If these systems can’t communicate with each
other, a great deal of the potential value is lost
• Enterprises must also communicate with
customers and partners outside of the firewall
• Yet, these environments are incompatible with
those within the enterprise

3
 The Web Services Context

X
X X X
X
X
• Various communication paths among
systems; many are blocked X
X
• Systems are brittle and difficult to maintain
since each point-to-point
X solution is written
X
separately

X
X
• Web services define standards for secure,
X reliable delivery
X
of messages (not the XML
business documents)
• They help enable communications across
X X
X X
X
heterogeneous environments, both inside and
across firewalls

4
 The Web Services Context

X
X X X

• Result: communication paths are improved,

X
however there is still a problem

X
X
• Vendors and end-users implement Web
servicesXdifferently and they may not be
compatible
• Technical guidance and implementation
X X
X
examples are needed to ensure Web services
are implemented consistently

5
The Web Services Context

• With the help of WS-I, developers can

create Web services that are
interoperable at the messaging level
• WS-I helps enterprises lower the cost and
risk of implementing Web services

6
 What is WS-I?

 An open industry effort chartered to promote Web Services

interoperability across platforms, applications and programming
languages.
 A standards integrator to help Web services advance in a
structured, coherent manner
 Hundreds of companies and organizations involved

7
WS-I, Standards and Industry

8
 WS-I Goals

• Achieve Web services interoperability

Integrate web services specifications
Promote consistent implementations
Provide a visible representation of conformance
• Accelerate Web services deployment
Offer implementation guidance and best practices
Deliver tools and sample applications
Provide a implementer’s forum where developers can collaborate
• Encourage Web services adoption
Build industry consensus to reduce early adopter risks
Provide a forum for end users to communicate requirements
Raise awareness of customer business requirements

9
 Deliverables

 Profiles
Guidelines and conventions for using Web service and other
specifications together in ways that ensure interoperability
 Sample applications
Use cases and usage scenarios based on customer requirements
Sample code and applications built on multiple vendor environments
Demonstrate solutions from multiple vendors can interoperate
 Test tools and supporting materials
Tools that test profile implementations for conformance with the
profiles
Supporting documentation and white papers

10
 Current Working Groups

 Basic Profile Working Group

Core set of specifications that provide the foundation for Web
services: SOAP, WSDL and UDDI
 Basic Security Profile Working Group
How to digitally sign and encrypt SOAP messages
 XML Schema Work Plan Working Group
Plan appropriate solutions for XML Schema interoperability issues

11
 SAP Implementation Example

Sample Application

UI
SA Core
Interop Web Dynpro Container Business
SA Testing Logic
SA
J2EE Container
WS-I Authentication
Sample App & Authorization
Applications based User Management Engine Data
on other vendors‘ Dictionary
platforms SAP NetWeaver 04s Web AS Specifi-
cation

12
 The Web Services Standards Stack

Additional
Management Portals
Capabilities

Business
Process Composition/Orchestration
Orchestration

Composable
Reliable
Service Security Transactionality
Messaging
Elements

Messaging Endpoint Identification, Publish/Subscribe

Description XML Schema, WSDL, UDDI, SOAP with Attachments

Invocation XML, SOAP

Transports HTTP, HTTPS,Others

13
 WS-I’s Work to Date

Additional
Management Portals
Capabilities

Business
Process Composition/Orchestration
Orchestration

Composable
Reliable
Service Security Transactionality
Messaging
Elements

Messaging Endpoint Identification, Publish/Subscribe

Description XML Schema, WSDL, UDDI, SOAP with Attachments

Invocation XML, SOAP

Transports HTTP, HTTPS, Others

14
 Delivered to Date

 Final Material
 Basic Profile 1.0 and 1.1, Simple SOAP Binding Profile 1.0 and
Attachments Profile 1.0
 Profiles that define how Web service standards should be used
together
 Sample Application Implementations 1.0
 Demonstrate interoperability between multiple vendors
 Testing Tools 1.0
 Used to check that messages conform to Basic Profile
 Security Challenges, Threats and Countermeasures
 Provides guidance on what to consider when securing Web
services

15
 Delivered to Date

 Draft Material
 Basic Security Profile 1.0
 How to secure messages
 REL and SAML Token Profiles
 Additional security features
 Testing Tools for the Basic Security Profile
 Used to check that SOAP messages conform to the Basic Security
Profile

16
 What’s Next

 Ongoing work
 Finalize the Basic Security Profile
 Align Sample Applications and Testing Tools with the Basic Security
Profile
 Determine scope of XML Schema interoperability work
 Gather business and technical requirements through the
Requirements Gathering Working Group to determine future
profile work
 Likely future candidates
 Update Basic Profile to include SOAP v1.2, WSDL v2.0, UDDI v3.0
 Other profile candidates include reliable messaging, addressing,
transactionality, orchestration, etc.

17
 Business Value of WS-I Conformance

 Reduce cost, complexity and risk

Provides confidence in interoperability
Common implementation guidelines
 Improve productivity and accelerate time to market
Facilitates collaboration, both internally and with business partners
Allows companies to focus on added value, not basic plumbing
 Simplify Web services buying decisions
The WS-I logo identifies conformance

18
THANKS
Q&A

19