A Formal Model of Business Application Integration from Web Services (Position Paper)

2009 ◽  
pp. 656-667 ◽  
Author(s):  
Kaiyu Wan ◽  
Mubarak Muhammad ◽  
Vasu Alagar
Keyword(s):  
Web Services ◽  
Formal Model ◽  
Position Paper ◽  
Application Integration ◽  
Business Application

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.

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.

Design of an Integrated Web Services Brokering System

2009 ◽  
Vol 4 (3) ◽  
pp. 58-77 ◽  
Author(s):  
Frederick Petry ◽  
Roy Ladner ◽  
Kalyan Moy Gupta ◽  
Philip Moore ◽  
David W. Aha
Keyword(s):  
Web Services ◽  
Web Service ◽  
Application Integration ◽  
Specific Context ◽  
Specific Domain ◽  
Specific Data ◽  
Multiple Data ◽  
Standard Interface ◽  
Automated Discovery ◽  
Community Standard

This article describes an Integrated Web Services Brokering System (IWB) to support the automated discovery and application integration of Web Services. In contrast to more static broker approaches that deal with specific data servers, our approach creates a dynamic knowledge base from Web Service interface specifications. This assists with brokering of requests to multiple data providers even when those providers have not implemented a community standard interface or have implemented different versions of a community standard interface. A specific context we illustrate here is the domain of meteorological and oceanographic (MetOc) Web Services. Our approach includes the use of specific domain ontologies and has evaluated the use of case-based classification in the IWB to support automated Web Services discovery. It was also demonstrated that the mediation approach could be extended to OGC Web Coverage Services.

Lowering Coupling in Distributed Applications With Compliance and Conformance

2020 ◽  
pp. 35-77
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Web Services ◽  
Distributed System ◽  
Fundamental Problem ◽  
Distributed Applications ◽  
Application Integration ◽  
Architectural Style ◽  
Normal Case ◽  
Data Schema ◽  
Share Data ◽  
Integration Problem

The interaction of applications in distributed system raises an integration problem that application-developing methods need to solve, even if the initial specifications change, which is actually the normal case. Current integration technologies, such as Web Services and RESTful APIs, solve the interoperability problem but usually entail more coupling than required by the interacting applications, since they share data schemas between applications, even if they do not actually exercise all the features of those schemas. The fundamental problem of application integration is therefore how to provide at most the minimum coupling possible while ensuring at least the minimum interoperability requirements. This chapter proposes compliance and conformance as the concepts to achieve this goal by sharing only the subset of the features of the data schema that applications actually use, with the goal of supporting a new architectural style, structural services, which seeks to combine the advantages of both SOA and REST.

RDTA

2014 ◽  
Vol 5 (3) ◽  
pp. 42-67
Author(s):  
Fateh Latreche ◽  
Faiza Belala
Keyword(s):  
Web Services ◽  
Real Time ◽  
Formal Model ◽  
Timed Automata ◽  
Web Services Composition ◽  
Composite Service ◽  
The Real ◽  
Services Composition ◽  
Dynamic Web ◽  
Natural Way

Web services are very dynamic, they are all around us and we use them every day without even knowing it. In this paper, the authors define a formal model for dynamic Web services composition and they investigate how it can be used to specify and analyse backward recovery procedures, updating partner services in case of failure. First, they propose Recursive and Dynamic Timed Automata (RDTA) model, interpreted over composite service configurations, which provide a natural way to design stateful and dynamic Web services. Then, the authors define the concurrent semantics of this timed automata extension in terms of real-time rewrite theories. Analysis of the model is carried out in the Real-Time Maude system, based on checking relevant properties.

A model for application integration using Web services

2005 ◽  
Author(s):  
A.K. Harikumar ◽  
R. Lee ◽  
Hae Sool Yang ◽  
Haeng-Kon Kim ◽  
Byeongdo Kang
Keyword(s):  
Web Services ◽  
Application Integration

An Adaptable Formal Model for Web Services Protocols

2007 ◽  
Author(s):  
Pemadeep Ramsokul ◽  
Arcot Sowmya
Keyword(s):  
Web Services ◽  
Formal Model

scholarly journals The Semantic Side of Service-Oriented Architectures

2010 ◽  
pp. 644-659
Author(s):  
Catarina Ferreira da Silva ◽  
Paulo Rupino da Cunha ◽  
Parisa Ghodous ◽  
Paulo Melo
Keyword(s):  
Web Services ◽  
Semantic Web ◽  
Enterprise Application Integration ◽  
Semantic Web Services ◽  
Semantic Matching ◽  
Application Integration ◽  
Service Oriented Architectures ◽  
Enterprise Application ◽  
Consumer Services ◽  
Service Oriented

In Service-Oriented Architectures (SOA), service descriptions are fundamental elements. In order to automatically execute SOA tasks, such as services discovery, it is necessary to capture and process the semantics of services. We review several Semantic Web Services frameworks that intend to bring semantics to Web Services. This chapter depicts some ideas from SOA and Semantic Web services and their application to enterprise application integration. We illustrate an example of logic-based semantic matching between consumer services and provided services, which are described in ontologies.

Sign in / Sign up

Export Citation Format

Share Document