Web services are self-contained, modular applications that can be described, published, located, and invoked over a network.
Web services are becoming the standard for basic SOA implementation by taking advantage of existing open-standard Web technologies such as XML, URL, and HTTP. These comprise a set of standards that facilitate open system-to-system communication. By adhering to Web services, applications that are based on different platforms and technologies can cooperate through well defined interfaces. Web services follow the SOA philosophy of loose coupling between service requesters and providers.
The formal definition of a Web service, provided by the World Wide Web consortium (W3C) Services Architecture Working Group is as follows:
“A web service is a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the Web services in a manner prescribed by it’s description using SOAP messages, typically conveyed using HTTP with and XML serialization inconjunction with other Web-related standards.”
1.Properties of a Web service
While this is widely documented, it can be summarized that all Web services share the following properties:
2.Web service standards
Web services standards and specifications change rapidly to keep up with emerging technologies.
Then, within each standard there are a number of specifications that we will outline.
Core standards of Web Services
Figure outlines the eight standards of Web service, which we discuss further in the following list.
a. Business processes
A business process specifies the potential execution order of operations from a collection of Web services, the data shared between these Web services, which partners are involved, and how they are involved in the business process. It also includes joint exception handling for collections of Web services and other issues involving how multiple services and organizations participate. BPEL (Business Process Execution Language) specifies business processes and how they relate to Web services.
Web services manageability is defined as a set of capabilities for discovering the existence, availability, health, performance, usage, as well as the control and configuration of a Web service within the Web services architecture. As Web services become pervasive and critical to business operations, the task of managing and implementing them is imperative to the success of business operations.
It is not possible to solve business issues if the participants are unable to be sure of the completion of message exchanges. Reliable messaging, which allows messages to be delivered reliably between distributed applications in the presence of software component, system, or network failures, is therefore critical to Web services.
Transactions are a fundamental concept in building reliable distributed applications. A Web service environment requires coordination behavior provided by a traditional transaction mechanism to control the operations and outcome of an application. The specifications include the following:
There are a number of specifications that applications can engage in secure communication that are designed to work with the general Web services framework. Following are some of these specifications:
f. Description and discovery
Web services are meaningful only if potential users may find information sufficient to permit their execution. The focus of these specifications and standards is the definition of a set of services supporting the description and discovery of businesses, organizations, and other Web services providers, the Web services they make available, and the technical interfaces which may be used to access those services.
Amongst others, some of these specifications are discussed in a following section and pertain to the CICS implementation of Web services:
These messaging standards and specifications are intended to give a framework for exchanging information in a decentralized, distributed environment. CICS TS provides support for the SOAP specifications.
BEEP, the Blocks Extensible Exchange Protocol (formerly referred to as BXXP), is a framework for building application protocols. It was standardized by IETF and does for Internet protocols what XML does for data.
3.WS standards in CICS TS
Certainly CICS TS adheres to many of the specifications outlined in the previous section, and the following are of particular interest to the development of Web services in CICS:
Following is additional terminology that describes some key specifications that are useful within the scope of this publication:
Extensible Markup Language or XML is the foundation of Web services. However, since much information is already written about XML, we do not describe it here.
SOAP provides an XML, text-based platform and language neutral message format. Originally proposed by Microsoft®, SOAP was designed to be a simple and extensible specification for the exchange of structured XML-based information in a decentralized, distributed environment. As such, it represents the main means of communication between the three functional components in an SOA: the service provider, the service requester, and the service registry.
There are currently two versions of SOAP: Version 1.1 and Version 1.2.
The SOAP specification consists of the following three parts:
A SOAP message is, in principle, independent of the transport protocol that is used: HTTP, JMS, SMTP, or FTP. The most common way of exchanging SOAP messages is through HTTP.
Web services Description Language (WSDL) uses XML to specify the characteristics of a Web service, what the Web service can do, where it resides, and how it is invoked. WSDL can be extended to allow descriptions of different bindings, regardless of what message formats or network protocols are used to communicate.
WSDL enables a service provider to specify the following characteristics of a Web service:
WSDL is not bound to any protocol or network service. It can be extended to support many different message formats and network protocols. However, because Web services are mainly implemented using SOAP and HTTP, the corresponding bindings are part of this standard.
The Universal Description, Discovery, and Integration standard defines a means to publish and to discover Web services. The current release is UDDI Version 3.0.
4. Implementing Web services
Web services invocation model
Following is a description of the interaction in above Figure
Web service Usage Models
Basic Web services support provides the following three simple usage models:
Other Web service standards are built upon these basic standards and invocation models to provide higher level functions and qualities of service.
IBM-CICS Related Interview Questions
|VSAM Interview Questions||IBM - VSAM Interview Questions|
|IBM-REXX Interview Questions||JCL Interview Questions|
|IBM DB2 Interview Questions||COBOL Interview Questions|
|IBM-JCL Interview Questions||DB2 Using SQL Interview Questions|
|IBM-JCL&VSAM Interview Questions||IBM Mainframe Interview Questions|
|Mainframe DB2 Interview Questions|
Service-oriented Architecture And Cics
Cics As A Service Provider And Requester
Modern Web Services Development Tools
Development Of The Change Of Address Cics Application
Exposing Our Application As A Web Service
Developing Web Service Clients
Tracing The Change Of Address Scenario
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.