Scribd
Upload
10 views2 pages

Architecture For Connecting Two Systems Through Web Services

This document describes connecting two systems through web services. It discusses the architecture components including the service provider, service consumer, and web server. It also outlines the communication flow between discovering, requesting, processing, and responding to a web service call.

Uploaded by

Pardhu42
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views2 pages

Architecture For Connecting Two Systems Through Web Services

This document describes connecting two systems through web services. It discusses the architecture components including the service provider, service consumer, and web server. It also outlines the communication flow between discovering, requesting, processing, and responding to a web service call.

Uploaded by

Pardhu42
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Architecture Document: Connecting Two Systems Through Web Services

1. Overview

Web services offer a standardized way for different systems, applications, or software
components to communicate over a network, primarily the internet. They use common protocols
like HTTP (Hypertext Transfer Protocol) and data formats like XML (eXtensible Markup
Language) or JSON (JavaScript Object Notation) to exchange information.

2. Architecture Components

● Service Provider (System A): This system exposes functionalities as web services. It
defines the services it offers, the data it expects (input), and the data it returns (output).
● Service Consumer (System B): This system uses the web services provided by
System A. It knows how to locate and interact with the services.
● Web Server: This server hosts the web services. It handles incoming requests from the
service consumer, processes them, and sends back responses.
● Network: The internet or a private network acts as the communication medium between
the service provider and the service consumer.

3. Communication Flow

1. Service Discovery: The service consumer locates the web service provided by System
A. This is often done through a service registry or directory.
2. Request: The service consumer sends a request to the web service hosted on the web
server. The request typically includes the name of the service to be invoked, input
parameters, and authentication credentials (if required).
3. Processing: The web server receives the request, parses it, and invokes the
corresponding service on System A. System A processes the request and generates a
response.
4. Response: The web server receives the response from System A and sends it back to
the service consumer.
5. Consumption: The service consumer receives the response, parses it, and extracts the
necessary data.

4. Protocols and Technologies

● SOAP (Simple Object Access Protocol): A protocol for exchanging structured


information in web service requests and responses.
● WSDL (Web Services Description Language): An XML-based language for describing
the interface of a web service (i.e., the services it offers, the data it expects, and the data
it returns).
● REST (Representational State Transfer): An architectural style for designing web
services that emphasizes simple, stateless interactions.
● JSON (JavaScript Object Notation): A lightweight data-interchange format often used
with RESTful web services.

5. Security Considerations

● Authentication: Verifying the identity of the service consumer.


● Authorization: Determining if the service consumer is allowed to access the requested
service.
● Encryption: Protecting the confidentiality of the data exchanged between the service
provider and the service consumer.

6. Benefits of Web Services

● Interoperability: Allows systems built on different technologies to communicate


seamlessly.
● Reusability: Web services can be reused by multiple applications.
● Loose coupling: Changes in one system do not necessarily require changes in other
systems that use its web services.
● Scalability: Web services can be easily scaled to handle increased traffic.

You might also like