Semantic Web Services

2009 ◽  
pp. 1293-1298
Author(s):  
Juan Manuel Adán-Coello
Keyword(s):  
Web Services ◽  
Web Service ◽  
Business Processes ◽  
Building Blocks ◽  
Distributed Applications ◽  
Point Of View ◽  
Loosely Coupled ◽  
Service Invocation ◽  
Computing Paradigm ◽  
Computing Platforms

Service-oriented computing (SOC) is a new computing paradigm that uses services as building blocks to accelerate the development of distributed applications in heterogeneous computer environments. SOC promises a world of cooperating services where application components are combined with little effort into a network of loosely coupled services for creating flexible and dynamic business processes that can cover many organizations and computing platforms (Chesbrough & Spohrer, 2006; Papazoglou & Georgakopoulos, 2003). From a technical point of view, the efforts to offer services have focused on the development of standards and the creation of the infrastructure necessary to describe, discover, and access services using the Web. This type of service is usually called a Web service. The availability of an abundant number of Web services defines a platform for distributed computing in which information and services are supplied on demand, and new services can be created (composed) using available services. Nevertheless, the composition of Web services involves three fundamental problems (Sycara, Paolucci, Ankolekar, & Srinivasan, 2003): 1. To elaborate a plan that describes how Web services interact, how the functionally they offer can be integrated to provide a solution to the considered problem. 2. To discover Web services that accomplish the tasks required by the plan. 3. To manage the interaction of the chosen services. Problems 2 and 3 are of responsibility of the infrastructure that supports the composition of services, while the first problem is of responsibility of the (software) agents that use the infrastructure. The discovery and interaction of Web services poses two main challenges to the infrastructure: 1. How to represent Web services capabilities and how to recognize the similarities between service capabilities and the required functionalities. 2. How to specify the information a Web service requires and provides, the interaction protocol, and the low-level mechanisms required to service invocation.

Business Process and Workflow Modeling in Web Services

2011 ◽  
pp. 466-470
Author(s):  
Vincent Yen
Keyword(s):  
Supply Chain ◽  
Web Services ◽  
Web Service ◽  
Business Process ◽  
Business Processes ◽  
Workflow Management ◽  
Heterogeneous Systems ◽  
Application Integration ◽  
Enterprise Application ◽  
Computing Platforms

In large organizations, typical systems portfolios consist of a mix of legacy systems, proprietary applications, databases, off-the-shelf packages, and client-server systems. Software systems integration is always an important issue and yet a very complex and difficult area in practice. Consider the software integration between two organizations on a supply chain; the level of complexity and difficulty multiply quickly. How to make heterogeneous systems work with each other within an enterprise or across the Internet is of paramount interest to businesses and industry. Web services technologies are being developed as the foundation of a new generation of business-to-business (B2B) and enterprise application integration (EAI) architectures, and important parts of components as grid (www.grid.org), wireless, and automatic computing (Kreger, 2003). Early technologies in achieving software application integration use standards such as the common object request broker architecture (CORBA) of the Object Management Group (www.omg.org), the distributed component object model (DCOM) of Microsoft, and Java/RMI, the remote method invocation mechanism. CORBA and DCOM are tightly coupled technologies, while Web services are not. Thus, CORBA and DCOM are more difficult to learn and implement than Web services. It is not surprising that the success of these standards is marginal (Chung, Lin, & Mathieu, 2003). The development and deployment of Web services requires no specific underlying technology platform. This is one of the attractive features of Web services. Other favorable views on the benefits of Web services include: a simple, lowcost EAI supporting the cross-platform sharing of functions and data; and an enabler of reducing integration complexity and time (Miller, 2003). To reach these benefits, however, Web services should meet many technology requirements and capabilities. Some of the requirements include (Zimmermann, Tomlinson & Peuser, 2003): • Automation Through Application Clients: It is required that arbitrary software applications running in different organizations have to directly communicate with each other. • Connectivity for Heterogeneous Worlds: Should be able to connect many different computing platforms. • Information and Process Sharing: Should be able to export and share both data and business processes between companies or business units. • Reuse and Flexibility: Existing application components can be easily integrated regardless of implementation details. • Dynamic Discovery of Services, Interfaces, and Implementations: It should be possible to let application clients dynamically, i.e., at runtime, look for and download service address, service binding, and service interface information. • Business Process Orchestration Without Programming: Allows orchestration of business activities into business processes, and executes such aggregated process automatically. The first five requirements are technology oriented. A solution to these requirements is XML-based Web services, or simply Web services. It employs Web standards of HTTP, URLs, and XML as the lingua franca for information and data encoding for platform independence; therefore it is far more flexible and adaptable than earlier approaches. The last requirement relates to the concept of business workflow and workflow management systems. In supply chain management for example, there is a purchase order process at the buyer’s side and a product fulfillment process at the supplier’s side. Each process represents a business workflow or a Web service if it is automated. These two Web services can be combined into one Web service that represents a new business process. The ability to compose new Web services from existing Web services is a powerful feature of Web services; however, it requires standards to support the composition process. This article will provide a simplified exposition of the underlying basic technologies, key standards, the role of business workflows and processes, and critical issues.

scholarly journals The EasySOC Project: A Rich Catalog of Best Practices for Developing Web Service Applications∗

2011 ◽  
Vol 14 (3) ◽  
Author(s):  
Juan Manuel Rodriguez ◽  
Marco Crasso ◽  
Cristian Mateos ◽  
Alejandro Zunino ◽  
Marcelo Campo
Keyword(s):  
Web Service ◽  
Service Discovery ◽  
Technical Specification ◽  
Building Blocks ◽  
Distributed Applications ◽  
Point Of View ◽  
Service Oriented ◽  
Development Support ◽  
Software Practitioners ◽  
Practical Nature

The Service-Oriented Computing (SOC) paradigm has gained a lot of attention in the software in- dustry since SOC represents a novel way of architecting distributed applications. SOC is mostly materialized via Web Services, which allow developers to expose their application as building blocks for other applications by defining a clear and public interface. Although conceptually and technologically mature, SOC still lacks adequate development support from a methodological point of view. We present the EasySOC project: a catalog of guidelines to build service-oriented applications and services. This catalog synthesizes best SOC development practices that arise as a result of several years of research in fundamental SOC-related topics, namely WSDL-based technical specification, Web Service discovery and Web Service outsourcing. In addition, we describe a plug-in for the Eclipse IDE that has been implemented to simplify the utilization of the guidelines. We believe that the practical nature of the guidelines, the empirical evidence that supports them, and the availability of IDE-integrated tools that enforces them will help software practitioners to rapidly exploit our ideas for building real SOC applications.

scholarly journals Http Relay Binding (webHttpRelayBinding) and Crud Contract

2019 ◽  
pp. 51-54
Author(s):  
Dr. Manish L Jivtode
Keyword(s):  
World Wide Web ◽  
Web Services ◽  
Web Service ◽  
World Wide ◽  
Distributed Applications ◽  
Configuration File ◽  
Representational State Transfer ◽  
State Transfer ◽  
Representational State ◽  
Http Protocol

The Broker Architecture became popular involving client and server. Representational State Transfer(REST) architecture is the architecture of World Wide Web. REST uses HTTP protocol based on Servlet and ASMX technology is replaced by WCF web service technology. SOAP and REST are two kinds of WCF web services. REST is lightweight compared to SOAP and hence emerged as the popular technology for building distributed applications in the cloud. In this paper, conducted by exposing a HTTP endpoint address, HTTP relay binding (webHttpRelayBinding) and CRUD contract through interface. The interface is decorated using WebGet and WebInvoke attributes. WCF configuration file created using XML tags for use with REST web service.

The Enabling Technologies for Cloud Computing

2014 ◽  
pp. 29-48
Keyword(s):  
Cloud Computing ◽  
Web Services ◽  
Multicore Processors ◽  
Network Virtualization ◽  
Building Blocks ◽  
Virtual Private Network ◽  
Point Of View ◽  
Private Network ◽  
Security Network ◽  
Networking Security

This chapter explores emerging technologies centered around cloud computing. From the technological point of view, cloud computing was born as a result of the emergence and the convergence of contemporary technologies. This chapter regards technological aspects of cloud. In the software area, Virtualization Technology and Web Services; in the hardware area, shared compute components (i.e., multicore processors); in networking, security, network virtualization, Virtual Private Network (VPN), virtual firewalls, and network overlay are the promising technologies for the future complex computing infrastructures. In this chapter, the authors review these technologies and describe how they contribute to the anatomy and the characteristics of cloud computing. These technologies constitute the building blocks of cloud computing technologies and infrastructures.

Ensuring Customised Transactional Reliability of Composite Services

2013 ◽  
pp. 203-232 ◽  
Author(s):  
Sami Bhiri ◽  
Walid Gaaloul ◽  
Claude Godart ◽  
Olivier Perrin ◽  
Maciej Zaremba ◽  
...  
Keyword(s):  
Web Services ◽  
Web Service ◽  
Control Structure ◽  
Point Of View ◽  
Workflow Patterns ◽  
Composite Services ◽  
Transactional Models ◽  
Transactional Approach

Web services are defined independently of any execution context. Due to their inherent autonomy and heterogeneity, it is difficult to examine the behaviour of composite services, especially in case of failures. This paper is interested in ensuring composite services reliability. Reliable composition is defined as a composition where all instance executions are correct from a transactional and business point of view. In this paper, the authors propose a transactional approach for ensuring reliable Web service compositions. The approach integrates the expressivity power of workflow models and the reliability of Advanced Transactional Models (ATM). This method offers flexibility for designers to specify their requirements in terms of control structure, using workflow patterns, and execution correctness. Contrary to ATM, the authors start from the designers’ specifications to define the appropriate transactional mechanisms that ensure correct executions according to their requirements.

Application of the FUSION Approach for Tool Assisted Composition of Web Services in Cross Organisational Environments

2010 ◽  
pp. 628-643
Author(s):  
Spiros Alexakis ◽  
Markus Bauer ◽  
András Balogh ◽  
Akos Kiss
Keyword(s):  
Web Services ◽  
System Architecture ◽  
Business Processes ◽  
Building Blocks ◽  
Enterprise Application Integration ◽  
Enterprise Application ◽  
Business Applications ◽  
Service Oriented ◽  
Heterogeneous Service ◽  
Fusion Approach

The research project FUSION aims at supporting collaboration and interconnection between enterprises with technologies that allow for the semantic fusion of heterogeneous service-oriented business applications. The resulting FUSION approach is an enterprise application integration (EAI) conceptual framework proposing a system architecture that supports the composition of business processes using semantically annotated Web services as building blocks. The approach has been validated in the frame of three collaborative commercial proof-of-concept pilots. The chapter provides an overview on the FUSION approach and summarises our integration experiences with the application of the FUSION approach and tools during the implementation of transnational career and human resource management services.

Service Composition Verification and Validation

2013 ◽  
pp. 200-219
Author(s):  
Manuel Palomo-Duarte
Keyword(s):  
Web Services ◽  
Software Development ◽  
Web Service ◽  
Service Composition ◽  
Web Service Composition ◽  
Verification And Validation ◽  
Loosely Coupled ◽  
Program Testing ◽  
Traditional Program ◽  
Programming Systems

Web services are changing software development thanks to their loosely coupled nature and simple adoption. They can be easily composed to create new more powerful services, allowing for large programming systems. Verification and validation techniques try to find defects in a program to minimize losses that its malfunction could cause. Although many different approaches have been developed for “traditional” program testing, none of them have proven definitive. The problem is even more challenging for new paradigms like web services and web service compositions, because of their dynamic nature and uncommon web service-specific instructions. This chapter surveys the different approaches to web service and web service composition verification and validation, paying special attention to automation. When no tools are available for a given technique, academic efforts are discussed, and challenges are presented.

Service-Oriented Computing

2013 ◽  
pp. 1-20 ◽  
Author(s):  
Stéphanie Chollet ◽  
Philippe Lalanda ◽  
Jonathan Bardin
Keyword(s):  
Web Services ◽  
Service Oriented Architecture ◽  
Application Integration ◽  
New Paradigm ◽  
Loosely Coupled ◽  
Service Oriented Computing ◽  
Service Oriented ◽  
Scale Network ◽  
Computing Platforms ◽  
Multiple Domains

The visionary promise of Service-Oriented Computing (SOC) is a world-scale network of loosely coupled services that can be assembled with little effort in agile applications that may span organizations and computing platforms. In practice, services are assembled in a Service-Oriented Architecture (SOA) that provides mechanisms and rules to specify, publish, discover and compose available services. The aim of this chapter is to present the different technologies implementing the new paradigm of SOA: Web Services, UPnP, DPWS, and service-oriented component OSGi and iPOJO. These technologies have been developed and adapted to multiple domains: application integration, pervasive computing and dynamic application integration.

A Model-based Approach for Diagnosing Fault in Web Service Processes

2013 ◽  
pp. 92-116
Author(s):  
Yuhong Yan ◽  
Philippe Dague ◽  
Yannick Pencolé ◽  
Marie-Odile Cordier
Keyword(s):  
Web Services ◽  
Web Service ◽  
Business Process ◽  
Business Processes ◽  
Formal Model ◽  
Service Orchestration ◽  
Model Based ◽  
Architecture Framework ◽  
Web Service Orchestration ◽  
Business Process Execution

Web services based on a service-oriented architecture framework provide a suitable technical foundation for business process management and integration. A business process can be composed of a set of Web services that belong to different companies and interact with each other by sending messages. Web service orchestration languages are defined by standard organizations to describe business processes composed of Web services. A business process can fail for many reasons, such as faulty Web services or mismatching messages. It is important to find out which Web services are responsible for a failed business process because we could penalize these Web services and exclude them from the business process in the future. In this paper, we propose a model-based approach to diagnose the faults in a Web service-composed business process. We convert a Web service orchestration language, more specifically BPEL4WS, into synchronized automata, so that we have a formal description of the topology and variable dependency of the business process. After an exception is thrown, the diagnoser can calculate the business process execution trajectory based on the formal model and the observed evolution of the business process. The faulty Web services are deduced from the variable dependency on the execution trajectory. We demonstrate our diagnosis technique with an example.

Distributed Geospatial Processing Services

2011 ◽  
pp. 1186-1193 ◽  
Author(s):  
Carlos Granell ◽  
Laura Díaz ◽  
Michael Gould
Keyword(s):  
Web Services ◽  
Web Service ◽  
Spatial Data ◽  
Geospatial Data ◽  
Service Description ◽  
Service Oriented Architectures ◽  
Data Infrastructure ◽  
Loosely Coupled ◽  
Tightly Coupled ◽  
Geospatial Services

The development of geographic information systems (GISs) has been highly influenced by the overall progress of information technology (IT). These systems evolved from monolithic systems to become personal desktop GISs, with all or most data held locally, and then evolved to the Internet GIS paradigm in the form of Web services (Peng & Tsou, 2001). The highly distributed Web services model is such that geospatial data are loosely coupled with the underlying systems used to create and handle them, and geospatial processing functionalities are made available as remote, interoperable, discoverable geospatial services. In recent years the software industry has moved from tightly coupled application architectures such as CORBA (Common Object Request Broker Architecture?Vinoski, 1997) toward service-oriented architectures (SOAs) based on a network of interoperable, well-described services accessible via Web protocols. This has led to de facto standards for delivery of services such as Web Service Description Language (WSDL) to describe the functionality of a service, Simple Object Access Protocol (SOAP) to encapsulate Web service messages, and Universal Description, Discovery, and Integration (UDDI) to register and provide access to service offerings. Adoption of this Web services technology as an option to monolithic GISs is an emerging trend to provide distributed geospatial access, visualization, and processing. The GIS approach to SOA-based applications is perhaps best represented by the spatial data infrastructure (SDI) paradigm, in which standardized interfaces are the key to allowing geographic services to communicate with each other in an interoperable manner. This article focuses on standard interfaces and also on current implementations of geospatial data processing over the Web, commonly used in SDI environments. We also mention several challenges yet to be met, such as those concerned with semantics, discovery, and chaining of geospatial processing services and also with the extension of geospatial processing capabilities to the SOA world.

Sign in / Sign up

Export Citation Format

Share Document