DPT 6302 INTEGRATIVE PROGRAMMING & TECHNOLOGIES

1
[WEB SERVICES]

Module 3<Week 3>< WEB SERVICES>

Course Learning Outcomes:

1. To be able to know the different web services use in system integration.
2. To be able learn the different compents use in accessing web services.

< CS 6100 – DEFINITION >

A web service is any piece of software made accessible on the internet using a structured
XML messaging framework. XML is used to format all Web Service communications. For
example , a client uses an XML message to invoke a web service, then waits for a
corresponding XML response.
Web services are self-contained, scalable, distributed, interactive apps that can be defined,
written, found, or invoked over the network to build goods, processes, and supply chains.
Local, distributed or web-based applications may be such. Online services are developed on
top of open standards like TCP / IP, HTTP, Java, HTML , XML and others.
Web services are information exchange systems based on XML which use the Internet for
direct interaction between applications. These systems can comprise programs, artifacts,
messages, or documents.
A web service is a set of open protocols and standards that are used to share data between
apps or systems. Software applications written in different programming languages and
running on different platforms that use web services to exchange data over computer
networks such as the Internet in a manner similar to communication between processes on
a single machine.

Components of Web Services

The basic web services platform is XML + HTTP. All the standard web services work using
the following components −

• SOAP (Simple Object Access Protocol)

• UDDI (Universal Description, Discovery and Integration)
• WSDL (Web Services Description Language)

WEB SERVICES AND MIDDLEWARE

It is an application integration technology that allows applications to be integrated more
rapidly, easily and less expensively. It is also a program-to- program interactions whereas

Course Module
web for program-to-user interactions allowing companies to reduce the cost of doing e-
business, to deploy solutions faster and to open up new opportunities.

Web services model built on emerging standards such as

• HTTP
• XML
• Simple Object Access Protocol (SOAP)
• Web Services Description Language (WSDL)
• Universal Description, Discovery and Integration (UDDI)

You can build on Solaris a Java-based web service that's accessible from your Windows
running Visual Basic software.
You can also use C # to build new web services under Windows that can be invoked from
your JavaServer Pages (JSP)-based web application and run on Linux.

Example
Find a basic program for account-managing and order processing. A client application built
with Visual Basic or JSP is used by accounting personnel to create new accounts and to enter
new customer orders.
The processing logic for this system is written in Java, and resides on a Solaris machine,
which also interacts to store information with a database.
The steps to perform this operation are as follows:
• The client program bundles the account registration information into a SOAP
message.
• This SOAP message is sent to the web service as the body of an HTTP POST request.
• The web service unpacks the SOAP request and converts it into a command that the
application can understand.
• The application processes the information as required and responds with a new
unique account number for that customer.
• Next, the web service packages the response into another SOAP message, which it
sends back to the client program in response to its HTTP request.
• The client program unpacks the SOAP message to obtain the results of the account
registration process.

WEB SERVICE ARCHITECTURE

1. A client that wants to be serviced should first find the supported services from the pre-
existing registry before compiling a code.
2. After finding its services through searching, the client gains the Web Service Description
Language (WSDL) that a server previously registers. From the WSDL, the client knows the
service provider location and the parameters to the found method.
3. After the client binds the described service during the compile time, it calls the local agent
whenever the client invokes a method call, and the local agent delivers it to the server side
 DPT 6302 INTEGRATIVE PROGRAMMING & TECHNOLOGIES
3
[WEB SERVICES]

agent through Simple Object Access Protocol (SOAP) over HTTP, FTP, SMTP, and TCP during
the runtime.
4. The server side agent activates the appropriate object, and delivers the calls to the object.

Simple Object Access Protocol: SOAP

• Microsoft proposed the SOAP standard
• SOAP is essentially XML and HTTP
-Intent is to introduce no new technology for distributed computing beyond what is
being used
-SOAP adds some headers to HTTP; no other changes
• Key element of SOAP:
-New MIME type: text/xml
-Agreed definitions of data types, mandatory values, etc.
-SOAP can send binary files, objects, etc. in its message
• SOAP implements the key features of legacy middleware (COM and CORBA) at a fraction of
the complexity
• SOAP is the key component in Web services, or Service Oriented Architectures (SOA)

Web Services and SOAP

URLs (URIs) replace the repositories and registries of COM and CORBA, its predecessors A
search engine can be used to dynamically locate remote objects unknown to the client
application when designed.

Course Module
HTTP POST and response replace application programming (in legacy CORBA and COM
interface definition languages, or IDLs) SOAP (HTTP and XML) is in text rather than binary,
so it’s much easier to interoperate across machines and debug it.
-Binary transmissions are not humanreadable
-SOAP can send binary objects like pictures (that are human readable) SOAP is
sufficiently efficient for most machinemachine communication
– Don’t use it on a single machine: use native COM or Java mechanisms

Web Services Description Language: WSDL

Contains:
▪ Description and format of messages that can be passed in <types> and <message>
tags.

▪ Direction of message passing in <portType>:

• Requestonly, requestresponse, responseonly

▪ Message encoding in <binding> element (literal, etc.)

▪ Location where service is offered in <service> element.

XML Summary
▪ Databases can read and write XML documents
▪ Web (HTTP) servers can send and receive XML documents
• XML can be displayed in browsers, via XSL
• XML can be translated between organizations, via XSL
▪ XML documents are small parts of a database
• XSD (or DTD) defines business rules and a schema:
o Entities, attributes, relationships, cardinality, and keys.
• XML documents can contain validation data, conditional data, objects
(graphics, other binary data)
• Applications are being designed to use XML heavily
▪ XML documents are generally not read into the core part of a database
• Placed in a staging area, then checked and processed, before being placed in
core part of database
▪ Many XML extensions: RDF, semantic Web, and UDDI.
• You’re able to read about them with basic XML background

EDI (Electronic Data Interchange)

• EDI is an old, mainframebased standard for electronic exchange of information
EDI is expensive, complex and has limited usage, but enough that new technologies
must interoperate with it
 DPT 6302 INTEGRATIVE PROGRAMMING & TECHNOLOGIES
5
[WEB SERVICES]

Very large companies use EDI and force it on their smaller partners/vendors
• XML documents follow EDI standards in many cases
EDI documents are called Transaction Sets (TS)
EDI to XML mapping established using DTDs
• New users of Internet ecommerce may skip EDI and use XML
Less than 80,000 of 6.2 million US businesses use EDI 125,000 businesses worldwide
use EDI EDI cost and complexity are large obstacle for medium size businesses
• Microsoft, by making XML the markup language for MS Office, may be hoping to take over
ecommerce through disruptive, lowcost technology.
EDI communications:
▪ Binary, not text (difficult to change or troubleshoot) EDI transaction sets are static
(that’s not all bad) EDI designed for expensive and scarce communications

▪ Much optimization of message size, etc.

▪ Intended to replace letters, phone calls, faxes.

▪ Not selfdescribing, cannot be validated, can’t be extended.

▪ Done through third party valueadded networks (VANs).

▪ Companies generally use file transfer to send file to VAN VAN handles EDI exchange
with trading partners Geared to onceaday, batch exchanges of data.

Example (over a period of days):

• Buyer sends EDI 840 document (Request for Quote)
• Receives EDI 843 (Quote) Sends EDI 850 (Purchase Order)
• Receives EDI 856 (Shipment Notice)
• Receives EDI 810 (Invoice)
• Sends EDI 820 (Payment)

Course Module
References and Supplementary Materials
Books and Journals
1. <Hubert Baumeister>; <2018>; <System Integration>; <Denmark>
2. <Len Bass, Paul clements, Rick Kazman>; <2012>; <Software Architecture in Practice>;
<USA>; <Addison-Wesley >
3. < Sathish Kumar Konga><Basic Integrative Programming Technologies: Data
Integration Technology/Architectures>; <2012>; <System Integration>; <LAP Lambert
Academic>

Online Supplementary Reading Materials

1. <System Integration>; <https://en.wikipedia.org/wiki/System_integration>; <May 2,
2020>
2. <Software Architecture>; <https://en.wikipedia.org/wiki/Software_architecture>;
<May 2, 2020>
3. <Integrative Coding>; <https://uomustansiriyah.edu.iq/media/lectures>; <May 2,
2020>
4. <Integrative Programming and Technology>;
<https://www.slideshare.net/vijipriyacse/ipt-chapter-3-data-mapping-and-
exchange-dr-j-vijipriya>; <May 2, 2020>