Deriving semantics from WS-BPEL specifications of parallel business processes on an example
|
|
- Brice Wilkinson
- 1 years ago
- Views:
Transcription
1 КОМПЬЮТЕРНЫЕ ИССЛЕДОВАНИЯ И МОДЕЛИРОВАНИЕ 2015 Т. 7 3 С ПЛЕНАРНЫЕ ДОКЛАДЫ УДК: Deriving semantics from WS-BPEL specifications of parallel business processes on an example University of Sofia, Faculty of Mathematics and Informatics, Bulgaria, 1164 Sofia, 5 James Bourchier Blvd. Received October 27, 2014 WS-BPEL is a widely accepted standard for specification of business distributed and parallel processes. This standard is a mismatch of algebraic and Petri net paradigms. Following that, it is easy to specify WS-BPEL business process with unwanted features. That is why the verification of WS-BPEL business processes is very important. The intent of this paper is to show some possibilities for conversion of a WS-BPEL processes into more formal specifications that can be verified. CSP and Z-notation are used as formal models. Z-notation is useful for specification of abstract data types. Web services can be viewed as a kind of abstract data types. Keywords: parallel business processes, specification WS-BPEL, semantics Извлечение семантики из спецификаций WS-BPEL обработки параллельных процессов в бизнесе на примере В. Димитров Университет Софии, Факультет Математики и Информатики, Болгария, 1164, г. София, б-р Джеймс Баучера, д. 5 WS-BPEL это широко распространённый стандарт для спецификации распределенных и параллельных бизнес-процессов. Этот стандарт не подходит для алгебраических парадигм и парадигм направленных графов Петри. Исходя из этого, легко определить бизнес-процесс WS-BPEL с нежелательными особенностями. Именно поэтому проверка бизнес-процессов WS-BPEL очень важна. Цель этой статьи состоит в том, чтобы показать некоторые возможности для преобразования процессов WS-BPEL в более формальные спецификации, которые могут быть проверены. CSP и система обозначений Z используются как формальные модели. Система обозначений Z полезна для спецификации абстрактных типов данных. Web-сервисы могут рассматриваться как своего рода абстрактные типы данных. Ключевые слова: параллельные бизнес-процессы, спецификация WS-BPEL, семантика Research in this paper are funded by Bulgarian Science Fund under contract ДФНИ-И01/12 Modern programming languages, environments and technologies, and their application in education of software professionals. Citation: Computer Research and Modeling, 2015, vol. 7, no. 3, pp Vladimir Dimitrov
2 446 Motivation There are two kinds of business processes in WS-BPEL [OASIS, 2007]: executable and abstract ones. The behavioral semantics of executable business processes is well defined in WS-BPEL standard. There is only one problem with WS-BPEL extensions, because they go outside the notation framework; they are open and unpredictable, but without them the framework semantics is consistent. The other category are the abstract business processes. Their intention is to describe Web services interactions without details on Web services internal implementations. The standard defines concretization procedure that can create an executable business process from an abstract one. But it is possible to generate with this procedure an executable business process with behavior different from that of the abstract one. It is possible, the executable business process to contain interactions that change the original ones, i.e. the executable process is not simply specialization of the abstract one. The standard requires for every abstract process to exist at least one executable business process, that is concretized by the procedure defined in the standard, and that is compatible with the abstract one. In such a way, the standard guarantees that above mentioned deviations are not available for at least one executable business process. Abstract business process represents a class of executable business processes compatible with it. It is more productive to verify abstract business processes because: 1. Verification of an abstract business process means a verification of the whole class of executable business processes that it represents. 2. Abstract business process does not contain implementation details that have no impact on Web services interactions. WS-BPEL business process is specified in two parts. First one is the WSDL [W3C, 2001] specification of the Web services involved in the interaction. This specification includes the business process specification as a Web service. The second part is the WS-BPEL business process specification as Web services interactions. These both specifications are complementary because the business process, usually, is a Web service specified in WSDL. On the other hand, the business process as Web service is implemented in WS-BPEL. WSDL standard is extended to capture Web Services participating in the WS-BPEL business process and this is an essential part of WS-BPEL. WSDL specifies only the interfaces and hides implementation details. WSDL specifications could be formalized. Why such a formalization is needed? WSDL is a XML based notation. Authors of XML argue that XML is readable for humans and computers. But XML specifications are verbose and not readable for humans. That is why, it is better, if Web services can be specified in some more compact notation, that is well better accepted by the humans. Such a tool is the Z notation [ISO/IEC 13568:2002]. Specifications in it tend to be very compact. Z-notation is mainly used for specification of abstract data types, but it can be used for specification of algebras. Web services can be viewed as abstract data types. In the example below, the WSDL and WS- BPEL specifications are a specification of abstract business process taken from the standard. Formalization of the WSDL specification First, messages exchanged among Web services are defined (shippingpt.wsdl): <wsdl:definitions targetnamespace="http://example.com/shipping/interfaces/" xmlns:ship="http://example.com/shipping/ship.xsd" xmlns:tns="http://example.com/shipping/interfaces/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/xmlschema"> КОМПЬЮТЕРНЫЕ ИССЛЕДОВАНИЯ И МОДЕЛИРОВАНИЕ
3 Deriving semantics from WS-BPEL specifications 447 <wsdl:types> <xsd:schema> <!-- import ship schema --> </xsd:schema> </wsdl:types> <wsdl:message name="shippingrequestmsg"> <wsdl:part name="shiporder" type="ship:shiporder" /> </wsdl:message> <wsdl:message name="shippingnoticemsg"> <wsdl:part name="shipnotice" type="ship:shipnotice" /> </wsdl:message> <wsdl:porttype name="shippingservicept"> <wsdl:operation name="shippingrequest"> <wsdl:input message="tns:shippingrequestmsg" /> </wsdl:operation> </wsdl:porttype> <wsdl:porttype name="shippingservicecustomerpt"> <wsdl:operation name="shippingnotice"> <wsdl:input message="tns:shippingnoticemsg" /> </wsdl:operation> </wsdl:porttype> </wsdl:definitions> The application data schemas are imported in this part of the WSDL specification. Such a types here are shiporder and shipnotice. They are the application data containers. Only the properties, defined on these messages, have impact on the message exchange among the business process Web services. These data types are modeled as basic types in Z notation: [shiporder, shipnotice] Messages are modelled with Z schemas: shippingrequestmsg shiporder: shiporder shippingnoticemsg shipnotice: shipnotice Every message part in the Z-schemas is specified as a field with the same part name and the same type name. Port types define Web services. They could be represented as abstract data types. In Z-notation, abstract data types are defined with schema type (Z schema) and operations (Z-schemas) applied on it. There is no way in the Z-notation, operations to be defined on the basic types. That is why initially, the basic type WebService is introduced and then it is used in the port types Z-schemas. The field ws is not very elegant approach for introducing the Web services, but it works. All port types are only with one operation. They are represented with the corresponding Z- schema. Operations are one way. Each of them has only one input parameter. 2015, Т. 7, 3, С
4 448 [WebService] shippingservicept [ws: WebService] shippingcustomerpt [ws: WebService] shippingrequest ΔshippingServicePT input?: shippingrequestmsg shippingnotice ΔshippingCustomerPT input?: shippingnoticemsg These specifications of the Web services do not contain any information about the Web services structure or behavior. Properties definition in the WSDL specification is: <wsdl:definitions targetnamespace="http://example.com/shipping/properties/" xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable" xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop" xmlns:ship="http://example.com/shipping/ship.xsd" xmlns:sif="http://example.com/shipping/interfaces/" xmlns:tns="http://example.com/shipping/properties/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/xmlschema"> <wsdl:import location="shippingpt.wsdl" namespace="http://example.com/shipping/interfaces/" /> <!-- types used in Abstract Processes are required to be finite domains. The itemcounttype is restricted by range --> <wsdl:types> <xsd:schema targetnamespace="http://example.com/shipping/ship.xsd"> <xsd:simpletype name="itemcounttype"> <xsd:restriction base="xsd:int"> <xsd:mininclusive value="1" /> <xsd:maxinclusive value="50" /> </xsd:restriction> </xsd:simpletype> </xsd:schema> </wsdl:types> <vprop:property name="shiporderid" type="xsd:int" /> <vprop:property name="shipcomplete" type="xsd:boolean" /> <vprop:property name="itemstotal" type="ship:itemcounttype" /> <vprop:property name="itemscount" type="ship:itemcounttype" /> <vprop:propertyalias propertyname="tns:shiporderid" messagetype="sif:shippingrequestmsg" part="shiporder"> КОМПЬЮТЕРНЫЕ ИССЛЕДОВАНИЯ И МОДЕЛИРОВАНИЕ
5 Deriving semantics from WS-BPEL specifications 449 <vprop:query> ship:shiporderrequestheader/ship:shiporderid </vprop:query> <vprop:propertyalias propertyname="tns:shiporderid" messagetype="sif:shippingnoticemsg" part="shipnotice"> <vprop:query>ship:shipnoticeheader/ship:shiporderid</vprop:query> <vprop:propertyalias propertyname="tns:shipcomplete" messagetype="sif:shippingrequestmsg" part="shiporder"> <vprop:query> ship:shiporderrequestheader/ship:shipcomplete </vprop:query> <vprop:propertyalias propertyname="tns:itemstotal" messagetype="sif:shippingrequestmsg" part="shiporder"> <vprop:query> ship:shiporderrequestheader/ship:itemstotal </vprop:query> <vprop:propertyalias propertyname="tns:itemscount" messagetype="sif:shippingrequestmsg" part="shiporder"> <vprop:query> ship:shiporderrequestheader/ship:itemscount </vprop:query> <vprop:propertyalias propertyname="tns:itemscount" messagetype="sif:shippingnoticemsg" part="shipnotice"> <vprop:query>ship:shipnoticeheader/ship:itemscount</vprop:query> </wsdl:definitions> A new type for the properties is introduced and it Z-schema is: itemcounttype == The properties are then represented as types: shiporderid == N 1 shipcomplete ::= False True itemstotal == itemcounttype itemscount == itemcounttype There are two deviations in the Z-notation schemas from the WSDL specification. The order numbers are positive numbers not simply integers as is defined in the WSDL specification. In Z- notation, there is no Boolean type and it is modelled with two values False and True. The aliases are properties placed on the messages. Here, they are modelled as functions from thr message type to the property type. There is no need to model XPath queries, because they are extensions to WS-BPEL. Queries written in other languages can be modelled in the same way. The aliases specification is more abstract: 2015, Т. 7, 3, С
6 450 shiporderid_shiporder: shippingrequestmsg shiporderid shiporderid_shippingnotice: shippingnoticemsg shiporderid shipcomplete_shiporder: shippingnoticemsg shipcomplete itemstotal_shiporder: shippingrequestmsg itemstotal itemscount_shiporder: shippingrequestmsg itemscount itemscount_shippingnotice: shippingnoticemsg itemscount One property could have many aliases with the same name. In the Z-notation, above defined functions are global ones and their names must be unique. So, alias name is formed by the property name and the part name, in which it is defined. It is mapping from message type to property type. Formalization of partner link type has no sensible interpretation here and they are modeled in the context of the WS-BPEL business process. Finally, as result of the modelling effort, the specification is very compact and very simple. It does not include the business process as a Web service. This specification could be used for Web Services development, but it is very simple without invariants. Formalization of the WS-BPEL specification The specification of the example abstract business process in WS-BPEL is: <process name="shippingservice" targetnamespace="http://example.com/shipping/" xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/abstract" xmlns:plt="http://example.com/shipping/partnerlinktypes/" xmlns:props="http://example.com/shipping/properties/" xmlns:ship="http://example.com/shipping/ship.xsd" xmlns:sif="http://example.com/shipping/interfaces/" abstractprocessprofile= "http://docs.oasis-open.org/wsbpel/2.0/process/abstract/ap11/2006/08"> <import importtype="http://schemas.xmlsoap.org/wsdl/" location="shippinglt.wsdl" namespace="http://example.com/shipping/partnerlinktypes/" /> <import importtype="http://schemas.xmlsoap.org/wsdl/" location="shippingpt.wsdl" namespace="http://example.com/shipping/interfaces/" /> <import importtype="http://schemas.xmlsoap.org/wsdl/" location="shippingproperties.wsdl" namespace="http://example.com/shipping/properties/" /> <partnerlinks> <partnerlink name="customer" partnerlinktype="plt:shippinglt" partnerrole="shippingservicecustomer" myrole="shippingservice" /> </partnerlinks> <variables> <variable name="shiprequest" messagetype="sif:shippingrequestmsg" /> <variable name="shipnotice" messagetype="sif:shippingnoticemsg" /> <variable name="itemsshipped" type="ship:itemcounttype" /> </variables> КОМПЬЮТЕРНЫЕ ИССЛЕДОВАНИЯ И МОДЕЛИРОВАНИЕ
7 Deriving semantics from WS-BPEL specifications 451 <correlationsets> <correlationset name="shiporder" properties="props:shiporderid" /> </correlationsets> <sequence> <receive partnerlink="customer" operation="shippingrequest" variable="shiprequest"> <correlations> <correlation set="shiporder" initiate="yes" /> </correlations> </receive> <if> <condition> bpel:getvariableproperty('shiprequest', 'props:shipcomplete') </condition> <sequence> <assign> <from variable="shiprequest" property="props:shiporderid" /> <to variable="shipnotice" property="props:shiporderid" /> <from variable="shiprequest" property="props:itemscount" /> <to variable="shipnotice" property="props:itemscount" /> </assign> <invoke partnerlink="customer" operation="shippingnotice" inputvariable="shipnotice"> <correlations> <correlation set="shiporder" pattern="request" /> </correlations> </invoke> </sequence> <else> <sequence> <assign> <from>0</from> <to>$itemsshipped</to> </assign> <while> <condition> $itemsshipped < bpel:getvariableproperty('shiprequest', 'props:itemstotal') </condition> <sequence> <assign> <opaquefrom/> <to variable="shipnotice" property="props:shiporderid" /> <opaquefrom/> <to variable="shipnotice" property="props:itemscount" /> 2015, Т. 7, 3, С
8 452 </assign> <invoke partnerlink="customer" operation="shippingnotice" inputvariable="shipnotice"> <correlations> <correlation set="shiporder" pattern="request" /> </correlations> </invoke> <assign> <from> $itemsshipped + bpel:getvariableproperty('shipnotice', 'props:itemscount') </from> <to>$itemsshipped</to> </assign> </sequence> </while> </sequence> </else> </if> </sequence> </process> At the beginning, the partner link, in which the business process participates, is defined. The role of the process in this link is fixed. The partner link is defined with the partner link type taken from the WSDL specification (shippinglt.wsdl): <wsdl:definitions targetnamespace="http://example.com/shipping/partnerlinktypes/" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:sif="http://example.com/shipping/interfaces/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> <wsdl:import location="shippingpt.wsdl" namespace="http://example.com/shipping/interfaces/" /> <plnk:partnerlinktype name="shippinglt"> <plnk:role name="shippingservice" porttype="sif:shippingservicept" /> <plnk:role name="shippingservicecustomer" porttype="sif:shippingservicecustomerpt" /> </plnk:partnerlinktype> </wsdl:definitions> The partner link type shippinglt connects a service (shippingservice) with its consumer (shippingserviceconsumer). In the WS-BPEL specification, the business process role is a fixed service provider. The roles of port types are defined in shippinglt.wsdl and are represented as operations in shippingpt.wsdl. The business process logic written is pseudo code is: receive shiporder if condition shipcomplete send shipnotice else itemsshipped := 0 while itemsshipped < itemstotal КОМПЬЮТЕРНЫЕ ИССЛЕДОВАНИЯ И МОДЕЛИРОВАНИЕ
9 Deriving semantics from WS-BPEL specifications 453 itemscount := opaque // non-deterministic assignment corresponding e.g. to // internal interaction with back-end system send shipnotice itemsshipped = itemsshipped + itemscount The process is instantiated when a shiporder is received. If the received order has been executed then a shipnotice is replied. This situation is checked in the message header property shipcomplete. Otherwise, a cycle is started for the order execution. At every step, part of the items are delivered and a notification is send. The counter is incremented with the number of the sent items. The cycle exits when all items are delivered and only then the process is terminated. In the abstract process, the number of delivered items at every step is non-deterministic. This information is retrieved from the backend system that actually register how many items have been send. From interactions point of view, this process is very simple. Initially, the process waits to receive an order message from a consumer and then replies with one or more messages. There are no error handlers, no compensators, no return values. There is no need for correlation sets coordination: when a new instance of the process is created, the process can be restarted in parallel to wait for new order, and the current instance is executing the received yet order. In CSP, the process is very simple as is shown below: channel customer 0; shippingservice() = customer?shiporder -> (checkorder(shiporder) shippingservice()); checkorder(shiporder) = (shipcomplete -> customer!shiporder -> Skip) [] (shipnotcomplete -> executeorder(shiporder)); executeorder(shiporder) = (itemsshipped -> Skip) [] (itemsnotshipped -> change_itemscount -> customer!shiporder -> executeorder(shiporder)); var count = 10; shippingservicecustomer() = if (count > 0) {customer!count -> {count--} -> receive()} else {Skip}; receive() = customer?shipnotice -> receive(); System() = shippingservicecustomer() shippingservice(); #assert System() deadlockfree; PAT, product for specification and verification of CSP models, is used here. In this specification, there is only one channel between service provider and service consumer. This channel is modelling the partner link from the WS-BPEL specification. The channel could have some capacity, but here only a message can be exchanged through it, like in the classic CSP. The WS-BPEL process is modelled as the CSP process shippingservice. This process, initially, is waiting to receive a shipping order through the channel. When the process receives an order, it starts its execution, but in parallel restarts a new copy to wait for a new order. The subprocess checkorder checks the order. There are two possible events from the check: the order is executed yet or not. With these two events is modelled the check in the WS-BPEL process. The order is received as a parameter by the subprocess checkorder. If the order has been executed yet, the process sends through the channel a notification, which may be is the order message in some format. Otherwise, it starts the subprocess executeorder. In this 2015, Т. 7, 3, С
10 454 process, all manipulations with variables, messages and properties are abstracted to result events. If all order items have been sent then the process terminates. Otherwise, the backend system is initiated. The last one sends information when some delivery is done. This is marked by an occurrence of change_itemscount. Through the channel, the consumer is informed about that delivery. Then follows a recursive execution of the subprocess with the left items. In this specification, instead of shippingnotice is returned shippingorder. The idea is that a document-message, like shippingorder, carries the business process state and no more other messages are needed. It possible, the CSP process to use different message in that case, but this would not change the interaction flow. In the CSP specification, there are consumer and system subprocesses. They are added for verification purposes of the whole system. The abstraction of data manipulations into events is the main approach in this conversion from WS-BPEL to CSP. The representation of a cycle as a recursive subprocess (subprogram) is the other used approach. The conditional statements are modelled as choices among events. The correlation sets are ignored in the model, because they are used only in the consumer part. The process simply returns through the channel data (the order) that contain the dialog identifier. Conclusion Attractive results in WSDL formalization with Z notation have not been achieved, because there are no behavior for the modelled Web Services. The business process WSDL specification is simply an interface to several Web services. On the other hand, the business process WS-BPEL specification specifies a behavior. Its formalization in CSP is maximally abstracted from implementation details saving the original interaction flow. The CSP specification can then be formally verified. The CSP model is very compact and readable. This example of formalization demonstrates an approach to formal verification of business processes. References ISO/IEC 13568:2002, Information technology Z formal specification notation Syntax, type system and semantics, OASIS, Web Services Business Process Execution Language Version 2.0, OASIS Standard, 11 April 2007, W3C, Web Services Description Language (WSDL) 1.1, W3C Note 15 March 2001, КОМПЬЮТЕРНЫЕ ИССЛЕДОВАНИЯ И МОДЕЛИРОВАНИЕ
Business Process Modelling Languages
Agent and Object Technology Lab Dipartimento di Ingegneria dell Informazione Università degli Studi di Parma Business Process Modelling Languages Paola Turci AOT Lab - DII - Università di Parma Business
Storage database in cloud processing
КОМПЬЮТЕРНЫЕ ИССЛЕДОВАНИЯ И МОДЕЛИРОВАНИЕ 2015 Т. 7 3 С. 493 498 СЕКЦИОННЫЕ ДОКЛАДЫ УДК: 004.65 Storage database in cloud processing A. V. Bogdanov a, Thurein Kyaw Lwin b Saint Petersburg State University,
Formalizing state alignment interaction in web service choreography
Lingnan University, Hong Kong From the SelectedWorks of Prof. YEUNG Wing-lok December, 2007 Formalizing state alignment interaction in web service choreography Wing Lok YEUNG, Lingnan University, Hong
Analyzing Service Contract with Model Checking
Analyzing Service Contract with Model Checking Contract-Oriented Software Development for Internet Services Joseph C. Okika, Anders P. Ravn Department of Computer Science Aalborg University, Denmark FLACOS
Distributed dcache-based storage system of UB RAS
КОМПЬЮТЕРНЫЕ ИССЛЕДОВАНИЯ И МОДЕЛИРОВАНИЕ 2015 Т. 7 3 С. 559 563 СЕКЦИОННЫЕ ДОКЛАДЫ УДК: 004.63 Distributed dcache-based storage system of UB RAS E. Yu. Kuklin 1,3,a, A. V. Sozykin 1,3, A. Yu. Bersenev
EVALUATION. WA1844 WebSphere Process Server 7.0 Programming Using WebSphere Integration COPY. Developer
WA1844 WebSphere Process Server 7.0 Programming Using WebSphere Integration Developer Web Age Solutions Inc. USA: 1-877-517-6540 Canada: 1-866-206-4644 Web: http://www.webagesolutions.com Chapter 6 - Introduction
Problem Set 1: Program Verification
Problem Set 1: Program Verification CS 173 Honors Section Assigned: September 7, 2011 Due on: September 14, 2011 One of the applications of logic in computer science is its use in proving programs to be
WebService Security. A guide to set up highly secured client-server communications using WS-Security extensions to the SOAP protocol
WebService Security A guide to set up highly secured client-server communications using WS-Security extensions to the SOAP protocol Jam Hamidi Senior Technical Analyst BCcampus, Victoria, British Columbia,
WebSphere Business Monitor
WebSphere Business Monitor Monitor models 2010 IBM Corporation This presentation should provide an overview of monitor models in WebSphere Business Monitor. WBPM_Monitor_MonitorModels.ppt Page 1 of 25
T-110.5140 Network Application Frameworks and XML Web Services and WSDL 15.2.2010 Tancred Lindholm
T-110.5140 Network Application Frameworks and XML Web Services and WSDL 15.2.2010 Tancred Lindholm Based on slides by Sasu Tarkoma and Pekka Nikander 1 of 20 Contents Short review of XML & related specs
University of Pisa. MSc in Computer Engineering. Business Processes Management. Lectures
University of Pisa MSc in Computer Engineering Business Processes Management Large and complex organizations are a tangible manifestation of advanced technology, more than machinery itself. (J.K. Galbraith)
Tutorial 3: Complex Types, If and ForEach Activities
Tutorial 3: Complex Types, If and ForEach Activities CONTENTS Opening the WSDL Editor Using the Schema Editor, and complex schema types Changing schema types from simple to complex Verifying the type change
Run-time Service Oriented Architecture (SOA) V 0.1
Run-time Service Oriented Architecture (SOA) V 0.1 July 2005 Table of Contents 1.0 INTRODUCTION... 1 2.0 PRINCIPLES... 1 3.0 FERA REFERENCE ARCHITECTURE... 2 4.0 SOA RUN-TIME ARCHITECTURE...4 4.1 FEDERATES...
System modeling. Budapest University of Technology and Economics Department of Measurement and Information Systems
System modeling Business process modeling how to do it right Partially based on Process Anti-Patterns: How to Avoid the Common Traps of Business Process Modeling, J Koehler, J Vanhatalo, IBM Zürich, 2007.
Management and Web service Management
Management and Web service Management This presentation offers work to OASIS completed by IBM with contribution from CA and Talking Blocks The work details a frame of reference for Management Applications,
OBJECT-PROCESS DIAGRAMS AS EXPLICIT GRAPHIC TOOL FOR WEB SERVICE COMPOSITION
2004 Society for Design and Process Science Printed in the United States of America OBJECT-PROCESS DIAGRAMS AS EXPLICIT GRAPHIC TOOL FOR WEB SERVICE COMPOSITION Yin Liu Tongji Center of National Engineering
17 March 2013 NIEM Web Services API Version 1.0 URI: http://reference.niem.gov/niem/specification/web-services-api/1.0/
17 March 2013 NIEM Web Serv vices API Version 1.0 URI: http://reference.niem.gov/niem/specification/web-services-api/1.0/ i Change History No. Date Reference: All, Page, Table, Figure, Paragraph A = Add.
ActiveVOS Fundamentals
Lab #17 Page 1 of 12 - ActiveVOS Fundamentals ActiveVOS Fundamentals Lab #17 Event Sub-processes Lab #17 Page 2 of 12 - ActiveVOS Fundamentals Lab Plan In this lab, we ll use an Event Sub-process to define
ActiveVOS Server Architecture. March 2009
ActiveVOS Server Architecture March 2009 Topics ActiveVOS Server Architecture Core Engine, Managers, Expression Languages BPEL4People People Activity WS HT Human Tasks Other Services JMS, REST, POJO,...
Challenges and Opportunities for formal specifications in Service Oriented Architectures
ACSD ATPN Xi an China June 2008 Challenges and Opportunities for formal specifications in Service Oriented Architectures Gustavo Alonso Systems Group Department of Computer Science Swiss Federal Institute
Relational Algebra The Relational Algebra and Relational Calculus. Relational Query Languages
The Relational Algebra and Relational Calculus Relational Algebra Slide 6-2 Relational Query Languages Query languages Allow manipulation and retrieval of data Not like programming languages Not intend
Syntax Check of Embedded SQL in C++ with Proto
Proceedings of the 8 th International Conference on Applied Informatics Eger, Hungary, January 27 30, 2010. Vol. 2. pp. 383 390. Syntax Check of Embedded SQL in C++ with Proto Zalán Szűgyi, Zoltán Porkoláb
Dynamic Reconfiguration Using Template Based Web Service Composition
Dynamic Reconfiguration Using Template Based Web Service Composition Kristof Geebelen, Sam Michiels and Wouter Joosen IBBT-DistriNet, Dept. Computer Science, K.U.Leuven Celestijnenlaan 200A 3001 Leuven,
SFC A Structured Flow Chart Editor Version 2.3 User s Guide Tia Watts, Ph.D. Sonoma State University
SFC A Structured Flow Chart Editor Version 2.3 User s Guide Tia Watts, Ph.D. Sonoma State University 1 of 35 SFC A Structured Flow Chart Editor Version 2.3 User s Guide Table of Contents 1. Introduction...
BPMN PATTERNS USED IN MANAGEMENT INFORMATION SYSTEMS
BPMN PATTERNS USED IN MANAGEMENT INFORMATION SYSTEMS Gabriel Cozgarea 1 Adrian Cozgarea 2 ABSTRACT: Business Process Modeling Notation (BPMN) is a graphical standard in which controls and activities can
A QoS-aware Method for Web Services Discovery
Journal of Geographic Information System, 2010, 2, 40-44 doi:10.4236/jgis.2010.21008 Published Online January 2010 (http://www.scirp.org/journal/jgis) A QoS-aware Method for Web Services Discovery Bian
Usage of Business Process Choreography
Usage of Business Process Choreography Akira Tanaka, Hitachi, Ltd. tanakaak@soft.hitachi.co.jp Infrastructures and Standard 1 Agenda Introduction Lifecycle! Design phase! Usage phase! Managing phase Remarks
Business Process Execution Language for Web Services
Business Process Execution Language for Web Services Second Edition An architect and developer's guide to orchestrating web services using BPEL4WS Matjaz B. Juric With Benny Mathew and Poornachandra Sarang
NEMSIS v3 Web Services Guide
NEMSIS TAC Whitepaper NEMSIS v3 Web Services Guide Date November 2, 2011 November 14, 2011 (FINAL) April 24, 2012 (Updated) May 09, 2012 (Updated) August 27, 2012 (updated) September 13, 2012 (updated)
GATHERING UNSTRUCTURED WORKFLOW DATA INTO RELATIONAL DATABASE MODEL USING PROCESS DEFINITION LANGUAGE
GATHERING UNSTRUCTURED WORKFLOW DATA INTO RELATIONAL DATABASE MODEL USING PROCESS DEFINITION LANGUAGE Amir Pourabdollah School of Computer Science and IT The University of Nottingham Jubilee Campus, Nottingham
Vertical Integration of Enterprise Industrial Systems Utilizing Web Services
Vertical Integration of Enterprise Industrial Systems Utilizing Web Services A.P. Kalogeras 1, J. Gialelis 2, C. Alexakos 1, M. Georgoudakis 2, and S. Koubias 2 1 Industrial Systems Institute, Building
WebSphere Process Server V6.1 Business Process Choreographer: Concepts and Architecture
WebSphere Process Server V6.1 Business Process Choreographer: Concepts and Architecture Michael Friess, Erich Fussi, Dieter König, Gerhard Pfau, Markus Reichart, Stefan Rüttinger, Claudia Zentner IBM Development
Interaction Choreography Models in BPEL: Choreographies on the Enterprise Service Bus
S BPM ONE 2010 the Subjectoriented BPM Conference http://www.aifb.kit.edu/web/s bpm one/2010 Interaction Choreography Models in BPEL: Choreographies on the Enterprise Service Bus Oliver Kopp, Lasse Engler,
Schematron Validation and Guidance
Schematron Validation and Guidance Schematron Validation and Guidance Version: 1.0 Revision Date: July, 18, 2007 Prepared for: NTG Prepared by: Yunhao Zhang i Schematron Validation and Guidance SCHEMATRON
Extending XACML for Open Web-based Scenarios
Extending XACML for Open Web-based Scenarios Claudio A. Ardagna 1, Sabrina De Capitani di Vimercati 1, Stefano Paraboschi 2, Eros Pedrini 1, Pierangela Samarati 1, Mario Verdicchio 2 1 DTI - Università
10. Service Orchestration Darmstadt University of Applied Sciences, Department of Computer Science Dr. Markus Voß (Accso GmbH)
SOA Service Oriented Architecture 10. Service Orchestration Darmstadt University of Applied Sciences, Department of Computer Science Dr. Markus Voß (Accso GmbH) Today s topic 1. Introduction 2. Business
Specification and Analysis of Contracts Lecture 1 Introduction
Specification and Analysis of Contracts Lecture 1 Introduction Gerardo Schneider gerardo@ifi.uio.no http://folk.uio.no/gerardo/ Department of Informatics, University of Oslo SEFM School, Oct. 27 - Nov.
Web Services Distributed Management: Management of Web Services (WSDM-MOWS) 1.1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 Web Services Distributed Management: Management of Web Services (WSDM-MOWS) 1.1 OASIS Standard, 01 August
02267: Software Development of Web Services
02267: Software Development of Web Services Week 5 Hubert Baumeister huba@dtu.dk Department of Applied Mathematics and Computer Science Technical University of Denmark Fall 2015 1 Recap XML Schema Complex
Service-Oriented Architecture
Erl_FM.qxd 6/30/05 10:53 AM Page v XXXXXXXXXXXXXXXXXXX Sample Chapter 16 from "Service-Oriented Architecture: Concepts, Technology, and Design" by Thomas Erl Service-Oriented Architecture Concepts, Technology,
Presentation / Interface 1.3
W3C Recommendations Mobile Web Best Practices 1.0 Canonical XML Version 1.1 Cascading Style Sheets, level 2 (CSS2) SPARQL Query Results XML Format SPARQL Protocol for RDF SPARQL Query Language for RDF
Abstract Business Process Monitoring
Institut für Architektur von Anwendungssystemen (IAAS) Universität Stuttgart Universitätsstraße 38 D - 70569 Stuttgart Studienarbeit Nr. 2316 Abstract Business Process Monitoring Sumadi Lie Studiengang:
Microsoft.NET Mobile Web
БЪЛГАРСКА АКАДЕМИЯ НА НАУКИТЕ. BULGARIAN ACADEMY OF SCIENCES ПРОБЛЕМИ НА ТЕХНИЧЕСКАТА КИБЕРНЕТИКА И РОБОТИКАТА, 54 PROBLEMS OF ENGINEERING CYBERNETICS AND ROBOTICS, 54 София. 2004. Sofia Microsoft.NET
BPEL. A Step by Step Guide: Model-Driven Generation with. Enterprise Architect. T his document will teach you how to use the Business Process
BPEL A Step by Step Guide: Model-Driven Generation with Enterprise Architect T his document will teach you how to use the Business Process Modeling Notation (BPMN 1.1) as a visual approach to producing
Oracle SOA Suite 12c : Build Composite Applications
Oracle University Contact Us: Local: 1800 103 4775 Intl: +91 80 67863102 Oracle SOA Suite 12c : Build Composite Applications Duration: 5 Days What you will learn This Oracle SOA Suite 12c: Build Composite
The Object Model Overview
The Object Model 3 3.1 Overview The object model provides an organized presentation of object concepts and terminology. It defines a partial model for computation that embodies the key characteristics
Chapter 1: Introduction
Chapter 1: Introduction Database System Concepts, 5th Ed. See www.db book.com for conditions on re use Chapter 1: Introduction Purpose of Database Systems View of Data Database Languages Relational Databases
Web Services Middleware Application: A Solution for SMEs towards B2B Framework Implementation
Web Services Middleware Application: A Solution for SMEs towards B2B Framework Implementation ADRIAN BESIMI, ZAMIR DIKA Contemporary Sciences and Technologies South East European University Ilindenska
BUSINESS-ORIENTED MANAGEMENT OF WEB SERVICES
By Fabio Casati, Eric Shan, Umeshwar Dayal, and Ming-Chien Shan BUSINESS-ORIENTED MANAGEMENT OF WEB SERVICES Using tools and abstractions for monitoring and controlling s. The main research and development
Structure of Presentation. The Role of Programming in Informatics Curricula. Concepts of Informatics 2. Concepts of Informatics 1
The Role of Programming in Informatics Curricula A. J. Cowling Department of Computer Science University of Sheffield Structure of Presentation Introduction The problem, and the key concepts. Dimensions
Chapter 8. Statement-Level Control Structures ISBN
Chapter 8 Statement-Level Control Structures ISBN 0-321-33025-0 Chapter 8 Topics Introduction Selection Statements Iterative Statements Unconditional Branching Guarded Commands Conclusions Copyright 2006
Overview Motivating Examples Interleaving Model Semantics of Correctness Testing, Debugging, and Verification
Introduction Overview Motivating Examples Interleaving Model Semantics of Correctness Testing, Debugging, and Verification Advanced Topics in Software Engineering 1 Concurrent Programs Characterized by
Web Service Facade for PHP5. Andreas Meyer, Sebastian Böttner, Stefan Marr
Web Service Facade for PHP5 Andreas Meyer, Sebastian Böttner, Stefan Marr Agenda Objectives and Status Architecture Framework Features WSD Generator PHP5 eflection API Security Aspects used approach planned
Web Services Technologies
Web Services Technologies XML and SOAP WSDL and UDDI Version 16 1 Web Services Technologies WSTech-2 A collection of XML technology standards that work together to provide Web Services capabilities We
Relational Databases
Relational Databases Jan Chomicki University at Buffalo Jan Chomicki () Relational databases 1 / 18 Relational data model Domain domain: predefined set of atomic values: integers, strings,... every attribute
A Critical Overview of the Web Services Choreography Description Language (WS-CDL)
A Critical Overview of the Web Services Choreography Description Language (WS-CDL) Alistair Barros Marlon Dumas Phillipa Oaks Introduction There is an increasingly widespread acceptance of Service-Oriented
02267: Software Development of Web Services
02267: Software Development of Web Services Week 8 Hubert Baumeister huba@dtu.dk Department of Applied Mathematics and Computer Science Technical University of Denmark Fall 2015 1 Recap I BPEL: I Doing
Comparing and Contrasting an Enterprise Service
Comparing and Contrasting an Enterprise Service Bus with ActiveVOS AN ACTIVE ENDPOINTS PAPER 2011 Active Endpoints, Inc. ActiveVOS is a trademark of Active Endpoints, Inc. All other company and product
Basis Path Test Suite and Testing Process for WS-BPEL
Basis Path Test Suite and Testing Process for WS-BPEL THEERAPONG LERTPHUMPANYA 1, 2 AND TWITTIE SENIVONGSE 1 1 Department of Computer Engineering, Chulalongkorn University Phyathai Road, Pathumwan, Bangkok
Multi-Agent Model for Automation of Business Process Management System Based on Service Oriented Architecture
Multi-Agent Model for Automation of Business Process Management System Based on Service Oriented Architecture Soe Winn, May Thwe Oo Abstract Business process automation is an important task in an enterprise
Business Rule Standards -- Interoperability and Portability
Rule Standards -- Interoperability and Portability April 2005 Mark H. Linehan Senior Technical Staff Member IBM Software Group Emerging Technology mlinehan@us.ibm.com Donald F. Ferguson IBM Fellow Software
Introduction to Business Process Modeling
TDT4250 - Model-driven Development of Information Systems, Autumn 2008 Introduction to Business Process Modeling Michael Havey: Essential Business Process Modeling Chapter 1 1 Business process modeling
Coverability for Parallel Programs
2015 http://excel.fit.vutbr.cz Coverability for Parallel Programs Lenka Turoňová* Abstract We improve existing method for the automatic verification of systems with parallel running processes. The technique
CICS Web Service Security. Anthony Papageorgiou IBM CICS Development March 13, 2012 Session: 10282
Web Service Security Anthony Papageorgiou IBM Development March 13, 2012 Session: 10282 Agenda Web Service Support Overview Security Basics and Terminology Pipeline Security Overview Identity Encryption
Performance Testing Web 2.0
Performance Testing Web 2.0 David Chadwick Rational Testing Evangelist dchadwick@us.ibm.com Dawn Peters Systems Engineer, IBM Rational petersda@us.ibm.com 2009 IBM Corporation WEB 2.0 What is it? 2 Web
Translating to Java. Translation. Input. Many Level Translations. read, get, input, ask, request. Requirements Design Algorithm Java Machine Language
Translation Translating to Java Introduction to Computer Programming The job of a programmer is to translate a problem description into a computer language. You need to be able to convert a problem description
Service-oriented architecture in e-commerce applications
Service-oriented architecture in e-commerce applications What is a Service Oriented Architecture? Depends on who you ask Web Services A technical architecture An evolution of distributed computing and
Software Verification: Infinite-State Model Checking and Static Program
Software Verification: Infinite-State Model Checking and Static Program Analysis Dagstuhl Seminar 06081 February 19 24, 2006 Parosh Abdulla 1, Ahmed Bouajjani 2, and Markus Müller-Olm 3 1 Uppsala Universitet,
Component Approach to Software Development for Distributed Multi-Database System
Informatica Economică vol. 14, no. 2/2010 19 Component Approach to Software Development for Distributed Multi-Database System Madiajagan MUTHAIYAN, Vijayakumar BALAKRISHNAN, Sri Hari Haran.SEENIVASAN,
A standards-based approach to application integration
A standards-based approach to application integration An introduction to IBM s WebSphere ESB product Jim MacNair Senior Consulting IT Specialist Macnair@us.ibm.com Copyright IBM Corporation 2005. All rights
Processes, services and business agility
Processes, services and business agility prof. dr. Wilfried Lemahieu K.U.Leuven Faculty of Business and Economics Department of Decision sciences and Information Management wilfried.lemahieu@econ.kuleuven.be
Web Testing. Main Concepts of Web Testing. Software Quality Assurance Telerik Software Academy http://academy.telerik.com
Web Testing Main Concepts of Web Testing Software Quality Assurance Telerik Software Academy http://academy.telerik.com The Lectors Snejina Lazarova Product Manager Business Services Team Dimo Mitev QA
Developing a Service Oriented Process Management System for University Quality Assurance
Developing a Service Oriented Process Management System for University Quality Assurance PROF. DR. TAHER TAWFEK HAMZA Dept. of computer science, faculty of computer science and informatics, mansoura university,
A CSPm Model for the Procure to Pay Case Study
A CSPm Model for the Procure to Pay Case Study Andreas V. Hense Bonn-Rhein-Sieg University oas, Grantham-Allee 20, 53757 Sankt Augustin, Germany, andreas.hense@brsu.de Abstract. The model presented here
6. SEQUENTIAL AND CONCURRENT STATEMENTS IN THE VHDL LANGUAGE
Structure of Computer Systems Laboratory No. 6 1 6. SEQUENTIAL AND CONCURRENT STATEMENTS IN THE VHDL LANGUAGE A VHDL description has two domains: a sequential domain and a concurrent domain. The sequential
Oracle SOA Suite 11g: Build Composite Applications
Oracle University Contact Us: 1.800.529.0165 Oracle SOA Suite 11g: Build Composite Applications Duration: 0 Days What you will learn This course covers designing and developing SOA composite applications
A Comparison of Database Query Languages: SQL, SPARQL, CQL, DMX
ISSN: 2393-8528 Contents lists available at www.ijicse.in International Journal of Innovative Computer Science & Engineering Volume 3 Issue 2; March-April-2016; Page No. 09-13 A Comparison of Database
Using Database Metadata and its Semantics to Generate Automatic and Dynamic Web Entry Forms
Using Database Metadata and its Semantics to Generate Automatic and Dynamic Web Entry Forms Mohammed M. Elsheh and Mick J. Ridley Abstract Automatic and dynamic generation of Web applications is the future
SOA and ESB. Mark Jeynes IBM Software, Asia Pacific jeynesm@au1.ibm.com
SOA and ESB Mark Jeynes IBM Software, Asia Pacific jeynesm@au1.ibm.com Agenda Service Orientation SCA / SDO Process Choreography WS-BPEL Enterprise Service Bus Demonstration WebSphere Integration Developer
[Refer Slide Time: 05:10]
Principles of Programming Languages Prof: S. Arun Kumar Department of Computer Science and Engineering Indian Institute of Technology Delhi Lecture no 7 Lecture Title: Syntactic Classes Welcome to lecture
1 Introduction: Network Applications
1 Introduction: Network Applications Some Network Apps E-mail Web Instant messaging Remote login P2P file sharing Multi-user network games Streaming stored video clips Internet telephone Real-time video
AN APPROACH TO DEVELOPING BUSINESS PROCESSES WITH WEB SERVICES IN GRID
AN APPROACH TO DEVELOPING BUSINESS PROCESSES WITH WEB SERVICES IN GRID R. D. Goranova 1, V. T. Dimitrov 2 Faculty of Mathematics and Informatics, University of Sofia S. Kliment Ohridski, 1164, Sofia, Bulgaria
The Spi Calculus. CSG 399 Lecture. The Spi Calculus p.1
The Spi Calculus CSG 399 Lecture The Spi Calculus p.1 Recall CSP Model system as a CSP process A specification is a property of traces Often, can be represented as a process Spec Checking a specification:
NGTP in a nutshell. Version 1.0 09/20/2010
NGTP in a nutshell Version 1.0 09/20/2010 Table of contents Page 2 1. About NGTP 2. NGTP Basic-Pattern: Components 3. NGTP Basic-Pattern : Communication concept 4. NGTP Basic-Pattern : Interfaces 5. NGTP
Novell Identity Manager
AUTHORIZED DOCUMENTATION Manual Task Service Driver Implementation Guide Novell Identity Manager 4.0.1 April 15, 2011 www.novell.com Legal Notices Novell, Inc. makes no representations or warranties with
SOA CERTIFIED JAVA DEVELOPER (7 Days)
SOA CERTIFIED JAVA DEVELOPER (7 Days) To achieve this certification, the following exams must be completed with a passing grade: Exam S90.01: Fundamental SOA & Service-Oriented Computing Exam S90.02: SOA
Rigorous Software Development CSCI-GA 3033-009
Rigorous Software Development CSCI-GA 3033-009 Instructor: Thomas Wies Spring 2013 Lecture 11 Semantics of Programming Languages Denotational Semantics Meaning of a program is defined as the mathematical
WebSphere Business Monitor
WebSphere Business Monitor Monitor sub-models 2010 IBM Corporation This presentation should provide an overview of the sub-models in a monitor model in WebSphere Business Monitor. WBPM_Monitor_MonitorModels_Submodels.ppt
The Cassandra System: Distributed Access Control Policies with Tunable Expressiveness 650.650: SPECIAL TOPICS IN MEDICAL
The Cassandra System: Distributed Access Control Policies with Tunable Expressiveness 650.650: SPECIAL TOPICS IN MEDICAL SECURITY AND PRIVACY What is Cassandra Role-based trust management system Policy
Semantic Description of Distributed Business Processes
Semantic Description of Distributed Business Processes Authors: S. Agarwal, S. Rudolph, A. Abecker Presenter: Veli Bicer FZI Forschungszentrum Informatik, Karlsruhe Outline Motivation Formalism for Modeling
On the Integration of Heterogeneous Web Service Partners
On the Integration of Heterogeneous Web Service Partners Francisco Curbera, Ignacio Silva-Lepe and Sanjiva Weerawarana IBM T. J. Watson Research Center {e-mail: curbera, isilval, sanjiva @us.ibm.com }
Search engine ranking
Proceedings of the 7 th International Conference on Applied Informatics Eger, Hungary, January 28 31, 2007. Vol. 2. pp. 417 422. Search engine ranking Mária Princz Faculty of Technical Engineering, University
BPEL to BPMN: The Myth of a Straight-Forward Mapping
BPEL to BPMN: The Myth of a Straight-Forward Mapping Matthias Weidlich, Gero Decker, Alexander Großkopf, and Mathias Weske Hasso Plattner Institute, Potsdam, Germany {matthias.weidlich,gero.decker}@hpi.uni-potsdam.de
Combining SAWSDL, OWL DL and UDDI for Semantically Enhanced Web Service Discovery
Combining SAWSDL, OWL DL and UDDI for Semantically Enhanced Web Service Discovery Dimitrios Kourtesis, Iraklis Paraskakis SEERC South East European Research Centre, Greece Research centre of the University
[MS-SPEMAWS]: SharePoint Email Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SPEMAWS]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
Algorithm & Flowchart & Pseudo code. Staff Incharge: S.Sasirekha
Algorithm & Flowchart & Pseudo code Staff Incharge: S.Sasirekha Computer Programming and Languages Computers work on a set of instructions called computer program, which clearly specify the ways to carry
Umbrella: A New Component-Based Software Development Model
2009 International Conference on Computer Engineering and Applications IPCSIT vol.2 (2011) (2011) IACSIT Press, Singapore Umbrella: A New Component-Based Software Development Model Anurag Dixit and P.C.
REST vs. SOAP: Making the Right Architectural Decision
REST vs. SOAP: Making the Right Architectural Decision Cesare Pautasso Faculty of Informatics University of Lugano (USI), Switzerland http://www.pautasso.info 1 Agenda 1. Motivation: A short history of
Second Workshop for Product Evaluation. My second process. Copyright 2015 Bizagi
Second Workshop for Product Evaluation My second process Second Workshop for Product Evaluation 1 Table of Contents Workshop: Office Supply Request... 3 Description of the Office Supply Request Process...
Efficient Information Retrieval in Network Management Using Web Services
Efficient Information Retrieval in Network Management Using Web Services Aimilios Chourmouziadis 1, George Pavlou 1 1 Center of Communications and Systems Research, Department of Electronic and Physical