scholarly journals Approach Based on Web Services for Business Process Adaptation

2015 ◽  
Vol 64 ◽  
pp. 832-837
Author(s):  
Afef Awadid ◽  
Sonia Ayachi Gnannouchi
2021 ◽  
Vol 23 (2) ◽  
pp. 40-44
Author(s):  
Olivia Fragoso-Diaz ◽  
Vitervo Lopez Caballero ◽  
Juan Carlos Rojas-Perez ◽  
Rene Santaolaya-Salgado ◽  
Juan Gabriel Gonzalez-Serna

Author(s):  
W. L. Yeung

Business collaboration is increasingly conducted over the Internet. Trading parties require business-level protocols for enabling their collaborative processes and a number of standardised languages, and approaches have been proposed for specifying business-level protocols. To illustrate the specification of web services based collaborative processes, three inter-related specification languages, namely, the ebXML Business Process Specification Schema (BPSS), the Web Service Business Process Execution Language (WSBPEL), and the Web Services Conversations Language (WSCL) are discussed in this chapter. A contract negotiation protocol is used as an example to illustrate the concepts involved in the specification. The chapter also discusses different strategies for deploying these specification languages.


2010 ◽  
pp. 1627-1638
Author(s):  
Dimitris Folinas ◽  
Tania Pavlou ◽  
Bill Karakostas ◽  
Vicky Manthou

Among different approaches in business processes modelling procedure are those in virtual and dynamic organizational environments. In this paper, a conceptual framework for modelling business processes in Virtual Organizations is suggested, by introducing Web Services technology. Web Services can be the business enabler for the new organizational form, which is particularly well suited to meet the demands arising from today’s turbulent changes in the firms’ environment. The proposed framework consists of several steps in a bottom-up approach, aiming to support the modelling and coordination of the complex and shared business processes in the examined environment.


Author(s):  
Yuhong Yan ◽  
Philippe Dague ◽  
Yannick Pencolé ◽  
Marie-Odile Cordier

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.


Author(s):  
Vincent Yen

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.


Sign in / Sign up

Export Citation Format

Share Document