Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Aphorismen
Applications
Business Economics & Admin.
My Computers
Cooking
Devices
Folders
Food
Hardware
Infos
Software Development
Sports
Operation Instructions
Todos
Test
Help
Glossary
Community portal
adaptions
Sidebar anpassen
Wiki RB4
Search
Search
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
BPM
(section)
Page
Discussion
English
Read
Edit
View history
Toolbox
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Notations== ===Standard Elements=== *Sequence *Parallel split *Synchronization *Exclusive choice *Simple merger (OR-join) *Multiple choice *Multiple merge *Discriminator *N out of M join *Synchronizing merge *Arbitrary circles *... ===BPEL=== The Business Process Execution Language (BPEL, WS-BPEL, BPEL4WS) ist eine XML-basierte Sprache zur Beschreibung von Geschäftsprozessen, deren einzelne Aktivitäten durch Webservices implementiert sind. BPEL Prozesse kommunizieren ausschließlich mit Webservices und nicht direkt mit dem Menschen. Der Standard wurd an [[#OASIS|OASIS]] zur Standardisierung übergeben. Aktuelles Release ist 2.0. ====Historie==== Vorgänger waren: * WSFL by IBM * XLANG by Microsoft * BPEL4WS 1.0 by BEA, IBM und Microsoft * BPEL4WS 1.0 by BEA, IBM, Microsoft, SAP und Siebel * BPEL4People specification by Microsoft, SAP und andere ====Concepts==== BPEL is expressed in XML and defined by XML Schema metadata that is closely aligned with SOA standards. BPEL itself uses WSDL at two levels. First, WSDL defined Web Services are used to interact with capabilities required by the process. Second, every BPEL process is itself a Web Service described using WSDL. ===[[BPMN]]=== ===EPK=== *C:\Uwes\Documents\Software_Development\Modeling\Business Process Modeling\Scheer_Thomas_2005_WISU_EPK.pdf *C:\Uwes\Documents\Software_Development\Modeling\Business Process Modeling\EPK.vsd ===JPDL=== jPDL defined by JBoss and part of [[#JBoss_jBPM| JBoss BPM]] is an extensible XML-based process definition language, and is suitable for a range of problems, from defining web application page flow, to traditional workflow management, all the way up to orchestration of services in a SOA environment. The '''jPDL suite''' is a download that contains all the jBPM components bundled in one easy download. The suite mainly contains: * the '''jBPM core library''': The core workflow and BPM functionality is packaged as a simple java library. This library includes a service to manage and execute processes in the jPDL database. * the '''jPDL process designer''': a eclipse plug-in * '''jBPM console web application''' * '''jBPM identity component''' * '''jBPM Job Executor''' The configuration has the form like the following example: <pageflow-definition name="numberGuess"> <start-page name="displayGuess" view-id="/numberGuess.jsp"> <redirect/> <transition name="guess" to="evaluateGuess"> <action expression="#{numberGuess.guess}" /> </transition> </start-page> <decision name="evaluateGuess" expression="#{numberGuess.correctGuess}"> <transition name="true" to="win"/> <transition name="false" to="evaluateRemainingGuesses"/> </decision> <decision name="evaluateRemainingGuesses" expression="#{numberGuess.lastGuess}"> <transition name="true" to="lose"/> <transition name="false" to="displayGuess"/> </decision> <page name="win" view-id="/win.jsp"> <redirect/> <end-conversation /> </page> <page name="lose" view-id="/lose.jsp"> <redirect/> <end-conversation /> </page> </pageflow-definition> ====Resources==== * [http://docs.jboss.com/jbpm/v4/userguide/html_single/ V4 User Guide] ===Petri Net=== [http://cs.au.dk/CPnets/ Coloured Petri Nets] (CP-nets or CPNs) is a graphical language for constructing models of concurrent systems and analysing their properties. Petri nets provide the foundation of the graphical notation and the basic primitives for modelling concurrency, communication, and synchronisation. CPN models are used to model and specify the behaviour of concurrent and distributed systems. An interactive simulation provides a way to ‘walk through’ a CPN model, investigating different scenarios in detail and checking whether the model works as expected. Automatic simulation is similar to program execution and the purpose is to execute the CPN model as fast and efficiently as possible, without detailed human interaction and inspection. ===XPDL=== XML Process Definition Language is a format standardized by [[#WfMC|WFMC]] to interchange Business Process Definitions between different workflow products like modeling tools or workflow engines.
Summary:
Please note that all contributions to Wiki RB4 may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Uwe Heuer Wiki New:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Toggle limited content width