SW - Unit 2
SW - Unit 2
1. Application Integration
Web services connect different applications running on various platforms or written in
different programming languages.
Example:
A Java-based inventory system can send data to a .NET-based billing system using web
services.
3. Platform Independence
Web services enable interaction between software programs regardless of the platform
(Windows, Linux, Mac) or language (Python, Java, C#).
Example:
A Python app on Linux can consume a web service created in Java running on Windows.
5. Mobile Applications
Mobile apps (iOS, Android) often use web services to fetch data from a server, like weather
updates, stock prices, or user details.
Example:
Swiggy or Zomato apps use web services to get restaurant listings, menu details, and track
orders.
6. IoT Integration
Web services help IoT devices send or receive data to/from a central server.
Example:
A smart thermostat uses a web service to get weather data or send temperature readings to
the cloud.
Conclusion
Web services are the backbone of modern internet communication, enabling data sharing,
automation, cross-platform integration, and real-time collaboration across applications,
devices, and organizations. Their uses range from daily apps to enterprise-level systems and
even government services.
Feature Description
Standardized
Uses HTTP, XML, SOAP, REST etc.
Protocols
Reusable Web services can be used again and again in different apps.
Protocol Purpose
Example:
A weather app requests today's temperature from a web service. The service fetches the data
and sends it back to the app.
SOAP Web Services Use SOAP protocol and XML. Heavier and more secure.
RESTful Web Use standard HTTP methods. Lightweight, faster, and more popular
Services today.
Real-life Examples
• Login with Google/Facebook – uses web services to verify user identity.
• Online payment – uses web services to communicate between merchant site and
bank.
• Flight booking – combines data from airlines, travel sites using web services.
Summary
Here's a clear and student-friendly explanation of the following Web Services concepts:
• SOAP
• UDDI
• Orchestrating Web Services
• Securing Web Services
Definition:
SOAP is a protocol used for exchanging structured information in web services using
XML over HTTP or other protocols.
Key Features:
• Platform & language independent.
• Uses XML to format messages.
• Supports complex operations like authentication, transactions.
• Can work over HTTP, SMTP, TCP, etc.
Definition:
UDDI is a registry where businesses can list and discover web services. It acts like a
telephone directory for web services.
Key Elements:
• White Pages – Company info (name, address).
• Yellow Pages – Services grouped by category.
• Green Pages – Technical info (WSDL file location, binding info).
Purpose:
• Service providers register their services.
• Service consumers search and find services.
• Enables discovery and integration of services.
Example:
An airline registers its flight availability service. A travel website finds and integrates it using
UDDI.
Definition:
Orchestration is the process of combining multiple web services into a single workflow to
perform a business process.
Example:
Booking a hotel might involve:
1. Search for hotels
2. Check availability
3. Make payment
→ All these are individual web services orchestrated into one process.
Tools/Technologies Used:
• BPEL (Business Process Execution Language) – Describes workflows.
• WS-BPEL – Standard language for web service orchestration.
Use Case:
In an e-commerce system, placing an order can involve inventory check, payment gateway,
and shipment — all orchestrated behind one “Buy Now” button.
Security Mechanisms:
Technique Purpose
Message
Ensures the message content is unreadable to unauthorized users.
Encryption
Example:
When logging into a banking app, the credentials are sent via HTTPS, validated using
authentication tokens, and access is granted based on authorization roles.
Definition:
Grid-enabled web services integrate grid computing with web services to allow sharing of
distributed resources (like CPU, storage, data, etc.) over the web in a standardized way.
Think of it like combining the power of multiple computers across different locations
and making them work together via web services.
Technologies Used:
• OGSA (Open Grid Services Architecture)
• Globus Toolkit – a middleware for building grid-enabled services.
Benefits:
• Access to high computational power
• Scalable and reliable
• Ideal for scientific research, big data, financial modeling
Definition:
The Semantic Web of Web Services refers to enhancing web services with machine-
understandable meaning (semantics) so that they can be automatically discovered,
invoked, composed, and executed by software agents.
It’s like teaching web services to "understand" what they do, so machines can interact
with them intelligently and autonomously.
Core Technologies:
Technology Purpose
Benefits:
• Automation of discovery and execution.
• Interoperability across different domains.
• Dynamic composition of services.
Key
OGSA, Globus Toolkit OWL-S, RDF, SAWSDL
Technologies
Feature Grid-Enabled Web Services Semantic Web of Web Services