Web services allow electronic devices to communicate and exchange machine-readable data over the World Wide Web. A web service typically provides an object-oriented interface to a database server that can be accessed by other web servers or mobile applications. Early concepts and technologies for web services were proposed in the late 1990s and 2000s by companies like Hewlett-Packard and Microsoft. Open standards like XML, SOAP, WSDL, and UDDI were developed to define how web services communicate and are discovered. These standards enable modular, inexpensive integration of applications and reduce costs of enterprise integration.

1. Web Services And Its
Significance In IT Domain…
 By Ankur R. Shrivastava IT Executive Bhopal(Bank Project
Team).
 Under Supervision of Mr. Monu Yadav.

2. What is Web Services?
 A Web service is a service offered by an
electronic device to another electronic device,
communicating with each other via the World
Wide Web. In a Web service, Web technology
such as HTTP, originally designed for human-to-
machine communication, is utilized for machine-
to-machine communication, more specifically for
transferring machine readable file formats such as
XML and JSON. In practice, the Web service
typically provides an object-oriented Web-based
interface to a database server, utilized for
example by another Web server, or by a mobile
application, that provides a user interface to the
end user

3. Who Was First?
 What company first proposed the web services
concept?
 Hewlett-Packard's e-Speak in 1999
 was an enabler for e-services
 Microsoft introduced the name "web services" in
June 2000
 now every major vendor is a player

4. Open, Standard
Technologies
 XML – tagging data such that it can be
exchanged between applications and platforms
 SOAP – messaging protocol for transporting
information and instructions between
applications (uses XML)

5. Open, Standard
Technologies
 WSDL – a standard method of describing web
services and their specific capabilities (XML)
 UDDI – defines XML-based rules for building
directories in which companies advertise
themselves and their web services

6. Advantages
 Open, text-based standards
 Modular approach
 Inexpensive to implement (relatively)
 Reduce the cost of enterprise application
integration
 Incremental implementation

7. The Big Picture
Client
UDDI Registry
WSDL
Document
Web Service Code
Client queries registry to locate service
Registry refers client to WSDL document
Client accesses WSDL document
WSDL provides data to interact with web service
Client sends SOAP-message request
Web service returns SOAP-message response

8. XML
 Developed from Standard Generalized Markup
Method (SGML)
 XML widely supported by W3C
 Essential characteristic is the separation of
content from presentation
 XML describes only data
 Any application that understands XML can
exchange data

9. SOAP
 SOAP enables between distributed systems
 SOAP message has three parts
 envelope – wraps entire message and contains
header and body
 header – optional element with additional info such
as security or routing
 body – application-specific data being
commuicated

10. WSDL
 Web services are self-describing
 Description is written in WSDL, an XML-based
language through which a web service conveys
to applications the methods that the service
provides and how those methods are accessed
 WSDL is meant to be read by applications (not
humans)

11. UDDI
 UDDI defines an XML-based format
that describes electronic
capabilities and business processes
 Entries are stored in a UDDI registry

12. SOAP
WS-Security
WS-Policy WS-Trust WS-Privacy
WS-Secure
Conversation WS-Federation WS-Authorization
Web Services Security
Architecture

13. SOAP
WS-Security
WS-Policy WS-Trust WS-Privacy
WS-Secure
Conversation WS-Federation WS-Authorization
WS-Security
Describes how to attach signature and encryption headers to
SOAP messages; how to attach security tokens such as X.509
certificates and Kerberos tickets

14. WS-Policy
SOAP
WS-Security
WS-Policy WS-Trust WS-Privacy
WS-Secure
Conversation WS-Federation WS-Authorization
Describes the capabilities and constraints of the security
and business policies on intermediaries and endpoints

15. WS-Trust
SOAP
WS-Security
WS-Policy WS-Trust WS-Privacy
WS-Secure
Conversation WS-Federation WS-Authorization
Framework for trust models that enables web services to
interoperate securely.

16. WS-Privacy
SOAP
WS-Security
WS-Policy WS-Trust WS-Privacy
WS-Secure
Conversation WS-Federation WS-Authorization
Model for how web services and requesters state privacy
preferences and organizational privacy practice statements

17. WS-SecureConversation
SOAP
WS-Security
WS-Policy WS-Trust WS-Privacy
WS-Secure
Conversation WS-Federation WS-Authorization
Manage and authenticate message exchanges between parties,
including security context exchange and establishing and deriving
session keys

18. WS-Federation
SOAP
WS-Security
WS-Policy WS-Trust WS-Privacy
WS-Secure
Conversation WS-Federation WS-Authorization
Manage and broker trust relationships in a heterogeneous
federated environment, including support for federated identities.

19. WS-Authorization
SOAP
WS-Security
WS-Policy WS-Trust WS-Privacy
WS-Secure
Conversation WS-Federation WS-Authorization
Manage authorization data and authorization policy.

20. Thank You……
GO AHEAD AND BE PREPARED YOUR SELF FOR
INDIA’S BIGGEST RETAIL BANK.