scholarly journals UML activity diagram transformation into BPEL integration flow

2018 ◽  
Vol 67 (3) ◽  
pp. 15-45 ◽  
Author(s):  
Tomasz Górski ◽  
Grzegorz Ziemski

The growing interest of companies in integration and interoperability between information systems has caused increase in significance of Service-Oriented Architecture which provides tools for Enterprise Application Integration. In that architecture, Enterprise Service Bus provides technical possibilities of communication between IT systems. A key element in the communication are integration flows. Objective: The aim of this article is to present a new transformation Integration2BPEL, which automates the development of executable integration flow expressed in the Web Services Business Process Execution Language (WS-BPEL) based on the model of the integration flow presented in the Unified Modelling Language (UML) activity diagram. Method: The author proposes a transformation of the type of model-to-code type which generates integration flow expressed in WS-BPEL, which can be executed in any BPEL-compliant process engine. The integration flow is modelled using UML activity diagram with stereotypes from ‘UML Profile for Integration Flows’ profile in an IBM Rational Software Architect (RSA). Using Integration2BPEL transformation a complete, executable integration flow is generated, which is composed of many mediation mechanisms. Generated integration flows have been executed on OpenESB. Results: The ability to generate a complete integration flow in BPEL, which without any additions can be run on enterprise service bus. Implementation phase of an integration flow construction was automated. Each of integration flows is implemented according to the same rules. In addition, it allows to avoid mistakes made by designers and programmers. Conclusions: Model-Driven Development is an approach that leads to the automation of the design and programming phases. Integration2BPEL transformation is a uniform mechanism to design integration flow. Potentially, it also allows to avoid implementation errors. Keywords: Web Services Business Process Execution Language (BPEL), Enterprise Service Bus (ESB), Unified Modelling Language (UML), UML activity diagram, Model-Driven Development (MDD), Transformation. null

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.


2005 ◽  
pp. 317-342 ◽  
Author(s):  
Rania Khalaf ◽  
Nirmal Mukhi ◽  
Francisco Curbera ◽  
Sanjiva Weerawarana

2019 ◽  
Author(s):  
Ricko Aulia

Pemodelan proses bisnis merupakan cara untuk memahami, mendesain dan menganalisa suatu proses bisnis. Manfaat pemodelan proses bisnis adalah untuk membantu perusahaan memahami proses bisnisnya dengan baik, mengidentifikasi permasalahan seperti critical path atau bottleneck yang mungkin terjadi, mengembangkan, mendokumentasikan serta mengkomunikasikannya pada semua pemangku kepentingan bisnis. Sehingga perusahaan dapat meningkatkan performance dari pengelolaan proses bisnisnya. Pemodelan proses bisnis dapat dilakukan dengan beberapa cara atau standar, antara lain dengan BPMN (Business Process Modelling Notation) dan Activity Diagram UML (Unified Modelling Language). Kedua standar pemodelan tersebut yang akan dibandingkan dengan studi kasus pemodelan proses bisnis perwalian secara online atau dikenal dengan nama FRS Online (Formulir Rencana Studi). Secara umum BPMN cenderung menggambarkan proses dari pandangan seorang analisis bisnis. BPMN tidak dibuat dengan tujuan untuk dibuat programnya. BPMN perlu disempurnakan (misalnya ke proses BPEL) sebelum bisa dibuat pedoman pemrograman. Alasan inilah, BPMN digunakan oleh analisis bisnis dengan tujuan bukan untuk implementasi tapi lebih ke arah penyajian kebutuhan yang akan diberikan kepada analisis IT dan software development. Umumnya, BPMN dipakai untuk menghasilkan “BPEL code” yang akan diperbaiki oleh developer sehingga dapat dibuat implementasinya.


2011 ◽  
pp. 155-190 ◽  
Author(s):  
C. Ouyang ◽  
W. Van der Aalst ◽  
M. Dumas

The Business Process Execution Language for Web Services (BPEL) is an emerging standard for specifying the behaviour of Web services at different levels of details using business process modeling constructs. It represents a convergence between Web services and business process technology. This chapter introduces the main concepts and constructs of BPEL and illustrates them by means of a comprehensive example. In addition, the chapter reviews some perceived limitations of BPEL and discusses proposals to address these limitations. The chapter also considers the possibility of applying formal methods and Semantic Web technology to support the rigorous development of service-oriented processes using BPEL.


Author(s):  
Carlos Pedrinaci ◽  
Dong Liu ◽  
Guillermo Álvaro ◽  
Stefan Dietze ◽  
John Domingue

Over the years a large number of technologies have been devised in order to describe service interfaces, e.g., WSDL (Booth & Liu, 2007), combine services in a process-oriented way, e.g., WS-BPEL (OASIS Web Services Business Process Execution Language (WSBPEL) TC, 2007), provide support for transactions, e.g., WS-Transaction, and cover non-functional properties (NFP) of services such as security aspects and the like, see for instance WS-Security and WS-Policy to name just a few (Erl, 2007). There is in an overwhelming stack of technologies and specifications dubbed WS-*, covering most aspects researchers have faced thus far. There remain nonetheless a number of outstanding issues (Papazoglou, Traverso, Dustdar, & Leymann, 2007) some of which are of a general technical nature, and some, indeed, are specifically related to NFPs. The latter will be dealt with in more detail in the next section.


Sign in / Sign up

Export Citation Format

Share Document