Podcasts about bpel

An airhacks.fm conversation with Prof. dr. Matjaz Juric (@matjazbj) about: ZX Spectrum 48k, loading apps from cassettes, playing games, enjoying Space Invaders, switching from Basic to assembly, switching to C-64, implementing application for exams at elementary school, starting to structure programs, getting serious with Schneider PC, creating bookkeeping applications with Borland Turbo Basic, dBASE and clipper were productive, visiting the CEBIT in 1990-ties, daily linear algebra in a bus, C, C++, Pascal, assembly, Vax then Java, studying at the University of Maribor, writing software to assess the value of companies, Ph.D. with ORBIX, Visigenic and RMI in Java, reading JavaReport magazines, writing performance about Java performance, RMI and CORBA, working with IBM Hursley on RMI-IIOP implementation, starting at University of Ljubljana, Java migration projects, Java EE - the enterprise edition was fascinating, Wrox publishing books, contributing performance chapter for Professional EJB book, writing Professional J2EE EAI book for wrox, Service-oriented architecture was a hot topic, orchestration is challenging for non-developers, decomposing application to services is useful, Azure Logic Apps, using JBPM for modelling long-running transactions, BPMN improved BPEL, writing WS-BPEL 2.0 Beginner's Guide about Colaxa, then oracle BPEL suite, the advent of KumuluzEE, attending JavaOne, proposing "the end of application servers" session, applying for Duke Choice Award, KumuluzEE is Java Duke's Choice Award Winner, attending the Java Duke Choice Award ceremony, making KumuluzEE kubernetes-aware, early KumuluzEE started with cloud-native EE extensions before availability of MicroProfile, Prof. dr. Matjaz Juric on twitter: @matjazbj, Prof. dr. Matjaz Juric at University of Ljubljana

Developers identify the pitfalls for businesses and the advantages of Business Process Management. What are the future trends around SOA?

Transcript -- Developers identify the pitfalls for businesses and the advantages of Business Process Management. What are the future trends around SOA?

Developers identify the pitfalls for businesses and the advantages of Business Process Management. What are the future trends around SOA?

Transcript -- Developers identify the pitfalls for businesses and the advantages of Business Process Management. What are the future trends around SOA?

Business processes –the next generation workflows- have attracted considerable research interest in the last fifteen years. More recently, several XML-based languages have been proposed for specifying and orchestrating business processes, resulting in the WS-BPEL language. Even if WS-BPEL has been developed to specify automated business processes that orchestrate activities of multiple Web services, there are many applications and situations requiring that people be considered as additional participants that can influence the execution of a process. Significant omissions from WS-BPEL are the specification of activities that require interactions with humans to be completed, called human activities, and the specification of authorization information associating users with human activities in a WS-BPEL business process and authorization constraints, such as separation of duty, on the execution of human activities. This talk investigates the problem of access control and resiliency for WS-BPEL processes. Access control in the context of business process means checking whether a user claiming the execution of an activity is authorized and the execution does not violate authorization constraints. Resiliency means that even if some users become unavailable, the remaining users can still complete the execution of the process according to the stated authorizations and authorization constraints. We present RBAC-WS-BPEL, an RBAC model for WS-BPEL business processes that supports the specification of resiliency constraints, authorizations and authorization constraints on business process activities. Resiliency constraints are evaluated when a WS-BPEL process is deployed, to check if there is a sufficient number of authorized users to perform the process so that authorization constraints are satisfied and the process terminates even if some users become unavailable. Authorizations and authorization constraints are evaluated whenever a user claims the execution of a business process's activity to determine if the execution of the activity by the user does not violate any authorization constraints and does not prevent some other subsequent activities from completing. About the speaker: From Febraury 2008, Dr. Federica Paci is a post-doctoral research associate at Purdue University.Paci's main research interests include access control for web services and business process, digital identity management and trust negotiations. Currently, she working on digital identity management for business process and mobile devices. Paci earned her Ph.D. in Computer Science from the University of Milan, Italy, in Febraury 2008. In Febraury 2004, she received the equivalent of a combined bachelor's/master's degree in Computer Science, also from the University of Milan.During Spring Semester of 2005 and 2006, Paci was a visiting research scholar at CS Department of Purdue University, West Lafayette, IN. Paci is the author or co-author of more than 10 conference papers and journal articles. Currently, she is co-authoring a book on Web services security. She serves as a program committee member for APWeb 2008 , IEEE Collaborative-Com 2008 and WWW 2009.

Business processes –the next generation workflows- have attracted considerable research interest in the last fifteen years. More recently, several XML-based languages have been proposed for specifying and orchestrating business processes, resulting in the WS-BPEL language. Even if WS-BPEL has been developed to specify automated business processes that orchestrate activities of multiple Web services, there are many applications and situations requiring that people be considered as additional participants that can influence the execution of a process. Significant omissions from WS-BPEL are the specification of activities that require interactions with humans to be completed, called human activities, and the specification of authorization information associating users with human activities in a WS-BPEL business process and authorization constraints, such as separation of duty, on the execution of human activities. This talk investigates the problem of access control and resiliency for WS-BPEL processes. Access control in the context of business process means checking whether a user claiming the execution of an activity is authorized and the execution does not violate authorization constraints. Resiliency means that even if some users become unavailable, the remaining users can still complete the execution of the process according to the stated authorizations and authorization constraints. We present RBAC-WS-BPEL, an RBAC model for WS-BPEL business processes that supports the specification of resiliency constraints, authorizations and authorization constraints on business process activities. Resiliency constraints are evaluated when a WS-BPEL process is deployed, to check if there is a sufficient number of authorized users to perform the process so that authorization constraints are satisfied and the process terminates even if some users become unavailable. Authorizations and authorization constraints are evaluated whenever a user claims the execution of a business process’s activity to determine if the execution of the activity by the user does not violate any authorization constraints and does not prevent some other subsequent activities from completing.