Home

2.0.x

1. If you have Invariant Sections Front Cover Texts and Back Cover Texts replace the with lexts line with this with the Invariant Sections being list their titles with the Front Cover Texts being list and with the Back Cover Texts being list If you have Invariant Sections without Cover Texts or some other combination of the three merge those two alternatives to suit the situation If your document contains nontrivial examples of program code we recommend releasing these examples in parallel under your choice of free software license such as the GNU General Public License to permit their use in free software
2. Secondary Section is a named appendix or a front matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document s overall subject or to related matters and contains nothing that could fall directly within that overall subject Thus if the Document is in part a textbook of mathematics a Secondary Section may not explain any mathematics The relationship could be a matter of historical connection with the subject or with related matters or of legal commercial philosophical ethical or political position regarding them The Invariant Sections are certain Secondary Sections whose titles are designated as being those of Invariant Sections in the notice that says that the Document is released under this License If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant The Document may contain zero Invariant Sections If the Document does not identify any Invariant Sections then there are none The Cover Texts are certain short passages of text that are listed as Front Cover Texts or Back Cover Texts in the notice that says that the Document is released under this License A Front Cover Text may be at most 5 words and a Back Cover Text may be at most 25 words Appendix A GNU Free Documentation License 24 A Transparent copy of the Document means a machine readable copy represented in a for
3. Though the gram mar has to be defined manually the generated parser is very flexible as it allows to process BPEL4WS 1 1 WS BPEL 2 0 and to some extend BPEL4WS 1 0 processes However the parser does not support XML namespaces BPEL20WFN will ignore names pace prefixes and skip all elements that are not explicitly covered by the WS BPEL 2 0 BPEL4WS 1 2 or WSDL 1 1 specification respectively Nevertheless skipping elements are reported as syntax error message cf warning message W00104 As a solution try removing or commenting non standard elements e I validated my process using an XML validator Why does BPEL20WEN still reports syntax errors Well because there are such errors Many BPEL editors generate invalid BPEL Even the official WS BPEL 2 0 specification contains processes with syntax errors Furthermore a lot of syntax errors cannot be covered with XSD XML Schema Definition validation Even if the considered process run on existing engines BPEL20oWFN might reject it as it stubbornly follows the WS BPEL specification e Why LoLA does not accept the generated files and reports parse errors in the first line This problem occurs using a pre compiled windows version of BPEL20WFN The generated files are in Windows format yet LoLA only supports files in Unix format To overcome this limitation of LoLA use a tool like dos2unix or change the file format in an editor like vi 5 2 Known Bugs Though this is
4. in the Document create one stating the title year authors and publisher of the Document as given on its Title Page then add an item describing the Modified Version as stated in the previous sentence Appendix A GNU Free Documentation License 26 J Preserve the network location if any given in the Document for public access to a Transparent copy of the Document and likewise the network locations given in the Document for previous versions it was based on These may be placed in the History section You may omit a network location for a work that was published at least four years before the Document itself or if the original publisher of the version it refers to gives permission K For any section Entitled Acknowledgements or Dedications Preserve the Title of the section and preserve in the section all the substance and tone of each of the contributor acknowledgements and or dedications given therein L Preserve all the Invariant Sections of the Document unaltered in their text and in their titles Section numbers or the equivalent are not considered part of the section titles M Delete any section Entitled Endorsements Such a section may not be included in the Modified Version N Do not retitle any existing section to be Entitled Endorsements or to conflict in title with any Invariant Section O Preserve any Warranty Disclaimers If the Modified Version includes new front matter sections or
5. the value is inherited by the parent activity Chapter 3 Warnings and Error Messages 16 128 129 130 131 132 133 134 135 136 137 138 warning warning warning error error notice warning warning error error notice A WSDL lt operation gt referenced in a BPEL activity was not specified in the input WSDL file A WSDL lt role gt of a partnerLinkType referenced by a lt partnerLink gt was not defined in the specified lt partnerLinkType gt in the input WSDL file A WSDL lt partnerLinkType gt referenced by a lt partnerLink gt was not specified in the input WSDL file An activity has neither a name or id attribute and thus can not be linked with a BPEL4Chor lt messageLink gt An activity has neither could not be linked with a BPEL4Chor lt messageLink gt using the activity s name or id attribute An lt extensionActivity gt is replaced by an lt opaqueActivity gt cf notice 116 A BPEL4Chor lt participantType gt was defined twice The lt participantType gt referenced by a BPEL4Chor lt participant gt was not found The value of a lt forEach gt s attribute id or name does not refer ence a BPEL4Chor lt participant gt or lt participantSet gt Thus the lt forEach gt activity is not grounded to the BPEL4Chor topology In a BPEL4Chor topology no XML namespace was defined for a lt participant gt In a WS BPEL file the attribute targetNamesp
6. we want to create a Fiona open workflow net executing bpel2owfn i example bpel m petrinet p small f owfn o which creates a file example owfn generated by BPEL2oWFN 2 0 1 input file example bpel process exampleprocess invocation ppel2owfn i example bpel m petrinet p small f owfn net size IP 5 P_inl 1 P_outl 1 Tl 2 FI 6 PLACE INTERNAL pi p2 p3 INPUT in PL req MAX_OCCURRENCES 1 OUTPUT out PL ack MAX_OCCURRENCES 1 INITIALMARKING pi 1 initial place FINALMARKING p3 final place TRANSITION t1 input CONSUME in PL req pi PRODUCE p2 TRANSITION t2 output CONSUME p2 PRODUCE out PL ack p3 END OF FILE example owfn This is finally the oWFN model of the BPEL process that can be analyzed by Fiona 1 Fiona is available at http www informatik hu berlin de top tools4bpel Chapter 5 FAQ and Known Bugs 21 5 FAQ and Known Bugs 5 1 Frequently Asked Questions e Why does the parser reject my BPEL file BPEL20WFN uses Flex and Bison to implement the parser We decided do not use an off the shelf XML parser generator as we did not found a suitable platform independent parser generator whose license was compatible to the GNU GPL General Public License Fur thermore we use the term generator Kimwitu to describe and process the AST abstract syntax tree and the trio Flex Bison Kimwitut integrates seamlessly
7. 11 suppressJoinFailure no gt lt compensate gt lt rethrow id 10 gt lt rethrow gt lt sequence gt catchAll lt faultHandlers gt sequence id 7 suppressJoinFailure no gt receive id 8 createInstance yes operation req partnerLink PL suppressJoinFailure no gt lt receive gt lt reply id 9 operation ack partnerLink PL suppressJoinFailure no gt lt reply gt lt sequence gt lt process gt Each activity is printed together with its attributes Note that the standard values of several attributes e g abstractProcess or suppressJoinFailure are added Furthermore an identifier attribute id was added to every activity We now want to create a compact Petri net model of the BPEL process using the petrinet mode and the small parameter fepetzouts i example bpel m petrinet p small l BPEL20WFN now also displays statistics of the generated Petri net model P 5 P_inl 1 P_out 1 IT 2 F 6 The generated Petri net model consists of five places including one input and one output place two transitions and six arcs To create a graphical representation invoke BPEL20WFN with the following options bpel2owfn i example bpel m petrinet p small f dot o This command creates a file example dot containing a Graphviz dot representation of the Petri net and if the dot tool was found in the search path a PNG Portable Netwo
8. appendices that qualify as Secondary Sections and contain no material copied from the Document you may at your option designate some or all of these sections as invariant To do this add their titles to the list of Invariant Sections in the Modified Version s license notice These titles must be distinct from any other section titles You may add a section Entitled Endorsements provided it contains nothing but endorse ments of your Modified Version by various parties for example statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard You may add a passage of up to five words as a Front Cover Text and a passage of up to 25 words as a Back Cover Text to the end of the list of Cover Texts in the Modified Version Only one passage of Front Cover Text and one of Back Cover Text may be added by or through arrangements made by any one entity If the Document already includes a cover text for the same cover previously added by you or by arrangement made by the same entity you are acting on behalf of you may not add another but you may replace the old one on explicit permission from the previous publisher that added the old one The author s and publisher s of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version 5 COMBINING DOCUMENTS You may combine the Document with
9. attribute MUST match the portType value implied by the combination of the specified partnerLink and the role implicitly specified by the activity 1 The descriptions for static analysis messages are taken from Appendix B of the WS BPEL specification Chapter 3 Warnings and Error Messages 10 15 16 17 18 23 24 25 32 35 36 3T 44 static static static static static static static static static static static static static static analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis The lt compensateScope gt activity MUST only be used from within a faultHandler another compensationHandler or a terminationHandler The compensate activity MUST only be used from within a faultHandler another compensationHandler or a terminationHandler To be instantiated an executable business process MUST con tain at least one lt receive gt or lt pick gt activity annotated with a createInstance yes attribute A partnerLink MUST specify the myRole or the partnerRole or both The initializePartnerRole attribute MUST NOT be used on a part nerLink that does not have a partner role The name of a partnerLink MUST be unique among the names of all partnerLinks defined within the same immediately enclosing scope The name of a variable MUST be unique among t
10. copyleft which means that derivative works of the document must themselves be free in the same sense It complements the GNU General Public License which is a copyleft license designed for free software We have designed this License in order to use it for manuals for free software because free software needs free documentation a free program should come with manuals providing the same freedoms that the software does But this License is not limited to software manuals it can be used for any textual work regardless of subject matter or whether it is published as a printed book We recommend this License principally for works whose purpose is instruction or reference 1 APPLICABILITY AND DEFINITIONS This License applies to any manual or other work in any medium that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License Such a notice grants a world wide royalty free license unlimited in duration to use that work under the conditions stated herein The Document below refers to any such manual or work Any member of the public is a licensee and is addressed as you You accept the license if you copy modify or distribute the work in a way requiring permission under copyright law A Modified Version of the Document means any work containing the Document or a portion of it either copied verbatim or with modifications and or translated into another language A
11. other documents released under this License under the terms defined in section 4 above for modified versions provided that you include in the combination all of the Invariant Sections of all of the original documents unmodified and list them all as Invariant Sections of your combined work in its license notice and that you preserve all their Warranty Disclaimers The combined work need only contain one copy of this License and multiple identical Invariant Sections may be replaced with a single copy If there are multiple Invariant Sections with the same name but different contents make the title of each such section unique by adding at the end of it in parentheses the name of the original author or publisher of that section if known or else a unique number Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work In the combination you must combine any sections Entitled History in the various original documents forming one section Entitled History likewise combine any sections Entitled Appendix A GNU Free Documentation License 27 10 Acknowledgements and any sections Entitled Dedications You must delete all sections Entitled Endorsements COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document and other documents released under this License and replace the individual copies of this License in the various doc
12. static static analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis The inputVariable attribute MUST NOT be used on an Invoke ac tivity that contains lt toPart gt elements The outputVariable attribute MUST NOT be used on an Invoke ac tivity that contains lt toPart gt elements For lt receive gt if lt fromPart gt elements are used on a lt receive gt ac tivity then the variable attribute MUST NOT be used on the same activity A start activity is a lt receive gt or lt pick gt activity that is annotated with a createInstance yes attribute Activities other than the fol lowing start activities lt scope gt lt flow gt and lt sequence gt MUST NOT be performed prior to or simultaneously with start activities If a process has multiple start activities with correlation sets then all such activities MUST share at least one common correlationSet and all common correlationSets defined on all the activities MUST have the value of the initiate attribute be set to join For lt reply gt if lt toPart gt elements are used on a lt reply gt activity then the variable attribute MUST NOT be used on the same activity If lt pick gt has a createInstance attribute with a value of yes the events in the lt pick gt MUST all be lt onMessage gt events The semantics of the lt onMessage gt event are identica
13. target gt elements Each lt target gt element associated with a given activity MUST use a link name distinct from all other lt target gt elements at that activity A link MUST NOT cross the boundary of a repeatable construct or the lt compensationHandler gt element This means a link used within a repeatable construct lt while gt lt repeatUntil gt lt forEach gt lt eventHandlers gt or a lt compensationHandler gt MUST be declared in a lt flow gt that is itself nested inside the repeatable construct or lt compensationHandler gt A link that crosses a catch catchAll or lt terminationHandler gt element boundary MUST be outbound only that is it MUST have its source activity within the lt faultHandlers gt or lt terminationHandler gt and its target activity outside of the scope associated with the handler A link declared in a lt flow gt MUST NOT create a control cycle that is the source activity must not have the target activity as a logically preceding activity The expression for a join condition MUST be constructed using only Boolean operators and the activity s incoming links status values The expressions in lt startCounterValue gt and lt finalCounterValue gt MUST return a TII meaning they contain at least one character that can be validated as a xsd unsignedInt Static analysis MAY be used to detect this erroneous situation at design time when possible for example when the expre
14. the second major release version of BPEL20WFN it might still contain poorly tested inefficient code e Problem BPEL20WFN crashes during the translation of an abstract BPEL process Diagnosis The implemented semantics of was mainly created to support executable BPEL processes Therefore the translation of abstract BPEL processes formerly called business protocols might be buggy In particular the allowed absence of implementation details hampers the analysis of the process and the generation of a formal model Solution To avoid errors at least each communicating activity should be defined with partnerlink and operation attribute and invoke activities should be defined with inputVariable and or outputVariable to distinguish the respective asynchronous and synchronous occurrence 5 3 Reporting Bugs If you find bug in BPEL20WFN or have a question please first check that it is not a known bug or a frequently asked question listed in above Otherwise please send us an email to bug bpel2owfn gnu org Include the version number which you can find by run ning bpel2owfn version Also include in your message the input BPEL process and the output that the program produced We will try to answer your mail within a week Chapter 5 FAQ and Known Bugs 22 If you have other questions comments or suggestions about BPEL20WFN contact us via elec tronic mail to nlohmann informatik hu berlin de 5 4 Contact Person Niels Lohman
15. well as lt exit gt lt throw gt lt compensate gt lt compensateScope gt activities is not translated to the Petri net model When combined with reduce this parameter yields the most compact Petri net model fhfaults Confines the standardfaults parameter in the negative control flow in activities in fault handlers no further BPEL standard faults can occur 1 This mode was formally called consinstency This mode was formally called communicationonly Chapter 2 Invoking BP EL20WFEN 6 nointerface reduce When creating a dot file no interface is printed Apply all implemented structural reduction rules This parameter is a shortcut for r5 and overrides any other defined reduction level standardfaults variables Model the occurrence of standard faults When this parameter is om mited only user defined faults that is faults thrown with lt throw gt activities and join failures can occur With the standardfaults pa rameter also the occurrence of other BPEL standard faults is modeled This parameter yields the most detailled and thus biggest Petri net model Add places for the variables of the input BPEL process to the Petri net model As the generated model abstracts from data that is a low level Petri net is generated the variables parameter also does not introduce data aspects Thus this mode is experimental If
16. you want to enable more than one parameter you have to add p parameter to each parameter 2 1 3 Output formats Especially for the Petri net mode a variaty of output formats are supported There are invoked by the following option format fileformat f fileformat Creates a fi le in a given ouput file format Each file format is only available in certain modes If you want to use more than one output file format you have to add f format to each file format Please note that the underlying modes of the given file formats are the same You cannot for example create XML and LoLA files together since XML requires the mode pretty whereas LoLA requires the mode p etrinet Petri net file formats imply mode petrinet or choreography apnn Outputs the inner of the generated open workflow net in APNN Abstract Petri Net Notation When the parameter o is used a file with the suffix apnn is created ina Outputs the inner of the generated open workflow net as untimed low level Petri net in INA Integrated Net Ana lyzer format When the parameter o is used a file with the suffix pnt is created lola Outputs the inner of the generated open workflow net as low level Petri net in LoLA Low Level Analyzer file for mat When the parameter o is used a file with the suffix 1ola is created owfn Outputs the generat
17. BPELZ gt OWFN Translating BPEL Processes into Open Workflow Nets GNU BPEL20WFN Version 2 0 2 15 June 2007 User s Manual Niels Lohmann About this document This manual is for GNU BPEL20WFN version 2 0 2 a tool translating a BPEL process into an open workflow net oWFN last updated 15 June 2007 Copyright 2005 2006 2007 Niels Lohmann Permission is granted to copy distribute and or modify this document under the terms of the GNU Free Documentation License Version 1 2 or any later version published by the Free Software Foundation with no Invariant Sections with the Front Cover Texts being A GNU Manual and with the Back Cover Texts as in a below A copy of the license is included in the section entitled GNU Free Documentation License a The FSF s Back Cover Text is You have freedom to copy and modify this GNU Manual like GNU software This manual does not explain how to setup or install GNU BPEL20WFN For this information please read the nstallation Manual which is part of the distribution or can be downloaded from the website of GNU BPEL20WEN http www gnu org software bpel2owfn S Toots 4 BPEL GNU BPEL20WFEN was developed during the Tools4BPEL project funded by the German Federal Ministry for Education and Research BMBF see http www informatik hu berlin de top tools4bpel for details Table of Contents 1 Introducing BPEL20WEN eeeeeeee eee 1 ll Conce
18. License You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute However you may accept compensation in exchange for copies If you distribute a large enough number of copies you must also follow the conditions in section 3 You may also lend copies under the same conditions stated above and you may publicly display copies 3 COPYING IN QUANTITY If you publish printed copies or copies in media that commonly have printed covers of the Document numbering more than 100 and the Document s license notice requires Cover Texts you must enclose the copies in covers that carry clearly and legibly all these Cover Texts Front Cover Texts on the front cover and Back Cover Texts on the back cover Both covers must also clearly and legibly identify you as the publisher of these copies The front cover must present the full title with all words of the title equally prominent and visible Appendix A GNU Free Documentation License 25 You may add other material on the covers in addition Copying with changes limited to the covers as long as they preserve the title of the Document and satisfy these conditions can be treated as verbatim copying in other respects If the required texts for either cover are too voluminous to fit legibly you should put the first ones listed as many as fit reasonably on the actual cover and continue the rest onto adjacent pages If you publish
19. PEL20WFN supports the following command line options help H Print an overview of the command line options and exit version v Print version information and exit input filename bpel i filename bpel Read a BPEL process from file filename bpel If this parameter is omitted input is read from standard input stdin Wildcards such as process bpel are also allowed wsdl filename wsdl w filename wsdl Read a WSDL file to support the translation topology filename xml t filename xml Read a BPEL4Chor participant topology file to support the translation of BPEL4Chor choreographies Can only be used with the choreography mode output filename 9 The generated output is written to a file called filename If the short form is used or the filename is omitted the input file name is taken and extended by the suffix of the chosen file format s If this parameter is omitted the output is passed to the standard output stdout log filename I All additional information like warnings and processing information are written to a file called filename If the short form is used or the filename is omitted the output file name is taken and extended by the suffix log If this parameter is omitted the information is passed to the standard error output stderr debug 1 4 flex bison d 1 4 flex bison This op
20. ace could not to be grounded to a BPEL4Chor lt participant gt In a BPEL4Chor topology a partner link specified for an activity was not found Instead the name of the specified id is used as a partner link Chapter 4 File Formats 17 4 File Formats In this chapter we show how a BPEL process can be translated to a Petri net model an then exported to several output file formats Consider the following simple BPEL process example bpel lt process name exampleprocess targetNamespace www gnu org software bpel2owfn gt lt partnerLinks gt lt partnerLink name PL partnerLinkType PLT myrole exampleprocess partnerRole exampleuser gt lt partnerLinks gt lt sequence gt lt receive partnerLink PL operation req createInstance yes gt lt reply partnerLink PL operation ack gt lt sequence gt lt process gt This process just waits for a message req on partner link PL and replies to this message with ack on the same partner link To parse this BPEL process BPEL20WFN has to be invoked with bpel2owfn i example bpel i which responds with the output 3 activities 2 basic 1 structured 0 scopes 3 implicit activities O handlers 0 FH O TH O CH O EH 1 implicit handlers O links O variables SYNTAX ANALYSIS No syntax errors found STATIC ANALYSIS No errors found checking 44 statics analysis requirements OTHER ANALYSIS No other errors found This means
21. aphy mode is an extension of the petrinet mode In the choreography mode several BPEL processes can be parsed and a Petri net model of their composition is generated For examples check test bpel4chor directory When combined with LoLA file output an additional task file is generated With the help of this file LoLA can check for weak termination of the composition Note that the choreography mode is only tested with the small mode To support the translation of a BPEL4Chor choreography a participant topology can be additionally parsed using the topology parameter petrinet Generates a Petri net representing the semantics of the given process Other options can be added to simplify or modify that generated Petri net see below pretty Outputs the parsed BPEL file in XML representation This option is mostly used for debugging reasons as it shows the implicit transforma tions and the identifiers of the BPEL constructs At most one mode can be selected If no mode is given BPEL20WFN acts like a plain BPEL parser that is the input file is read but no output is generated 2 1 2 Additional parameters These options control some Petri net related options parameter par Sp par small With the small parameter only the communicational behavior of the input BPEL process is modeled That is the negative control flow fault termination or compensation handlers as
22. ation so you may distribute translations of the Document under the terms of section 4 Replacing Invariant Sections with translations requires special permission from their copyright holders but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections You may include a translation of this License and all the license notices in the Document and any Warranty Disclaimers provided that you also include the original English version of this License and the original versions of those notices and disclaimers In case of a disagreement between the translation and the original version of this License or a notice or disclaimer the original version will prevail If a section in the Document is Entitled Acknowledgements Dedications or History the requirement section 4 to Preserve its Title section 1 will typically require changing the actual title TERMINATION You may not copy modify sublicense or distribute the Document except as expressly provided for under this License Any other attempt to copy modify sublicense or distribute the Document is void and will automatically terminate your rights under this License However parties who have received copies or rights from you under this License will not have their licenses terminated so long as such parties remain in full compliance FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publ
23. composition The result is written to the LoLA file servicel_service2 lola Furthermore an analysis file servicel_service2 task is written that can be processed by LoLA Further examples for invocations of BPEL20WFN can be found in the tests directory of the source distribution Chapter 3 Warnings and Error Messages 9 3 Warnings and Error Messages BPEL20WFN performs several analysis steps on the input BPEL process These messages are displayed during parsing and postprocessing of the process and can be classified as follows e Notices do not report errors but just give information about the translation process e Syntax error messages report problems during the lexical or syntactical analysis of the process See Chapter 5 FAQ and Known Bugs page 21 for information about handling syntax errors e Static analysis messages occur when a test described in the WS BPEL specification detects an error in the process When such an error is found a WS BPEL processor must reject the process If the process is an abstract process the static analysis errors can be considered as warnings as abstract processes are not meant to be executed e Warnings report potential problems in the input process The warned problem should be corrected to assure executability of the input process e Errors report problems that are explicitly mentioned in the WS BPEL specification They should be corrected to avoid runtime errors Furthermore p
24. ct syntax tree is printed in Graphviz dot representation When mode cfg is used the CFG control flow graph is printed in Graphviz dot representation In any case when the tool dot is found in the search path during configuration of BPEL20WFN and the parameter o is used dot is used to generate a PNG Portable Net work Image file In this case two files with the suffixes dot and png are created Note that when the ast mode is used with the dot file format the o parameter has to be used info When mode petrinet is used information about the places and transitions of the generated net in a proprietary ASCII based format For each place and transition all roles that is inscriptions of the Petri net patterns are listed The information can be used to correlate the generated Petri net model with the input BPEL process When the parameter o is used a file with the suffix info is created xml When the mode pretty is used the pretty printed in put BPEL process with the implicit transformation rules applied exported in XML Extensible Markup Lanuage When the parameter o is used a file with the suffix xm1 is created 2 2 Exit Values 0 No error occurred Yasper is available at http www yasper org Chapter 2 Invoking BPEL20oWFN 8 1 A critical error occured that is a fault was detected that makes further processing impossibl
25. d element was parsed when the parser expected a BPEL standard activity Then a syntax error is printed and the whole element is ignored The parse error and this message can usually be ignored as non standard elements would neither we translated to a Petri net model nor are constrained by the WS BPEL specification In the second case a syntactically correct BPEL was skipped because it was misplaced As an example consider two activities embedded in a lt while gt activity without an enclosing sequence activity In this case the second activity triggers this message 4 This fault can only be detected in mode mode cfg 5 All elements that are not explicitly defined in the WS BPEL specification e g elements from other namespaces are considered as non standard Chapter 3 Warnings and Error Messages 14 101 102 103 104 105 106 107 108 109 110 111 112 notice notice notice critical notice warning warning syntax warning warning warning notice The lt partners gt construct only supported by BPEL4WS 1 1 is skipped due to a syntax error The lt to gt or lt from gt construct is skipped due to a syntax error The lt condition gt construct is skipped due to a syntax error When a syntax error occurs BPEL20WFN tries to recover and contin ues parsing the input file after skipping the faulty or unknown element Sometimes however the skipping of acti
26. e 2 An input file could not be opened 3 A syntax error in the input BPEL occurred The input file cannot be further pro cessed 4 Any other error 2 3 Examples In this section we show some examples how BPEL20WFN can be invoked See Chapter 4 File Formats page 17 for more examples ppel2owfn i sample bpel m petrinet f lola f info o p reduce Reads the file sample bpel generates a structural reduced low level Petri net and saves it in a LoLA file sample lola For further information a file sample info is generated ppel2owfn i sample bpel mpetrinet fowfn d3 o Reads the file sample bpel generates a low level open workflow net and saves it in an oWFN file sample owfn For further information a file sample info is generated During the conversion several debug messages are printed to standard output prog bpel2owfn fdot m petrinet dot Tps osample ps Runs the program prog and reads its output as BPEL process generates a Petri net and outputs its Graphviz dot representation This stream is read by dot which layouts the Petri net and creates an output PostScript file sample ps ppel2owfn i sample bpel m ast Reads the file sample bpel and prints the abstract syntax tree AST to standard output ppel2owfn m choreography i service1 bpel i service2 bpel f lola o Reads the files servicei bpel and service2 bpel and creates a Petri net model of their
27. eadlocks or any other Petri net property or e check any temporal logic formula with a variety of model checking tools BPEL20WFN b meta model Petri net model b BPEL process Petri net static analysis pattern selection Furthermore BPEL20WFN can translate a BPEL4Chor choreography to a Petri net model This model can be used to analyze properties of a complete choreography or to synthesize a fitting service for an incomplete choreography BPEL20WFN uses static analysis to make the generated Petri net model as compact as possible to analyze a chosen property This is called flexible model generation Furthermore several design flaws can be detected using control and data flow analysis BPEL20WFN was written by Niels Lohmann Christian Gierds and Martin Znamirowski It is part of the Tools4BPEL project funded by the Bundesministerium fr Bildung und Forschung See http www informatik hu berlin de top tools4bpel for details 1 1 Concepts of BPEL20WFEN Input BPEL Process BPEL20WFN can read BPEL processes compliant to the WS BPEL 2 0 or the BPEL4WS 1 1 specification Abstract Syntax Tree The AST abstract syntax tree is the main data structure of BPEL20WFN The AST is annotated with information gained by static analysis Control Data Flow Graph From the abstract syntax tree a control data flow graph is built This graph is used to apply static analysis algorithms to gain in formation e g dead code abo
28. ed open workflow net in Fiona file for mat Note that the Fiona file format is together with the PNML file format the only Petri net output format that outputs the complete open workflow net that is also Chapter 2 Invoking BPEL20oWFN 7 the interface is exported When the parameter o is used a file with the suffix owfn is created pep Outputs the inner of the generated open workflow net as low level Petri net in low level PEP notation When the parameter o is used a file with the suffix llnet is created pnml Outputs the generated open workflow net in PNML Petri Net Markup Language Note that the PNML file format is together with the Fiona file format the only Petri net output format that outputs the complete open workflow net that is also the interface is exported Currently the interface places are annotated using a type tag which is only supported by Yasper When the parameter o is used a file with the suffix pnm is created spin Outputs the inner of the generated open workflow net as low level Petri net in Promela Process Meta Language for the model checker SPIN When the parameter o is used a file with the suffix spin is created Other file formats note the required mode dot When mode petrinet is used the generated open work flow net is printed in Graphviz dot representation When mode ast is used the AST abstra
29. faultHandlers gt element For the lt catch gt construct to have a defined type associated with the fault variable the faultVariable attribute MUST only be used if ei ther the faultMessageType or faultElement attributes but not both accompany it The faultMessageType and faultElement attributes MUST NOT be used unless accompanied by faultVariable attribute The peer scope dependency relation MUST NOT include cycles In other words WS BPEL forbids a process in which there are peer scopes S1 and 2 such that S1 has a peer scope dependency on 82 and S2 has a peer scope dependency on S1 4 An event handler MUST contain at least one lt onEvent gt or lt onAlarm gt element The partnerLink reference of lt onEvent gt MUST resolve to a partner link declared in the process in the following order the associated scope first and then the ancestor scopes For lt onEvent gt the resolution order of the correlation set s refer enced by correlation MUST be first the associated scope and then the ancestor scopes A scope with the isolated attribute set to yes is called an isolated scope Isolated scopes MUST NOT contain other isolated scopes Within a scope the name of all named immediately enclosed scopes MUST be unique Identical catch constructs MUST NOT exist within a lt faultHandlers gt element Either a non standard element was parsed or a BPEL activity was considered as misplaced In the first case a non standar
30. he names of all vari ables defined within the same immediately enclosing scope Variable names are BPELVariableNames that is NCNames as defined in XML Schema specification but in addition they MUST NOT contain the character The messageType type or element attributes are used to specify the type of a variable Exactly one of these attributes MUST be used For assign the from and to element MUST be one of the spec ified variants In the from spec of the partnerLink variant of assign the value myRole for attribute endpointReference is only permitted when the partnerLink specifies the attribute myRole In the from spec of the partnerLink variant of assign the value partnerRole for attribute endpointReference is only permitted when the partnerLink specifies the attribute partnerRole In the to spec of the partnerLink variant of assign only partnerLinks are permitted which specify the attribute partnerRole The name of a lt correlationSet gt MUST be unique among the names of all lt correlationSet gt defined within the same immediately enclosing scope The specification describes all allowed combinations of elements and attributes in from and to specifications Chapter 3 Warnings and Error Messages 11 51 52 55 56 57 59 62 63 64 65 66 67 68 static static static static static static static static static static static
31. ish new revised versions of the GNU Free Doc umentation License from time to time Such new versions will be similar in spirit to the present version but may differ in detail to address new problems or concerns See http www gnu org copyleft Each version of the License is given a distinguishing version number If the Document specifies that a particular numbered version of this License or any later version applies to it you have the option of following the terms and conditions either of that specified Appendix A GNU Free Documentation License 28 version or of any later version that has been published not as a draft by the Free Software Foundation If the Document does not specify a version number of this License you may choose any version ever published not as a draft by the Free Software Foundation ADDENDUM How to use this License for your documents To use this License in a document you have written include a copy of the License in the document and put the following copyright and license notices just after the title page Copyright C year your name Permission is granted to copy distribute and or modify this document under the terms of the GNU Free Documentation License Version 1 2 or any later version published by the Free Software Foundation with no Invariant Sections no Front Cover Texts and no Back Cover Texts A copy of the license is included in the section entitled GNU Free Documentation License
32. istinct from that of the Document and from those of previous versions which should if there were any be listed in the History section of the Document You may use the same title as a previous version if the original publisher of that version gives permission B List on the Title Page as authors one or more persons or entities responsible for authorship of the modifications in the Modified Version together with at least five of the principal authors of the Document all of its principal authors if it has fewer than five unless they release you from this requirement C State on the Title page the name of the publisher of the Modified Version as the publisher D Preserve all the copyright notices of the Document E Add an appropriate copyright notice for your modifications adjacent to the other copy right notices F Include immediately after the copyright notices a license notice giving the public permission to use the Modified Version under the terms of this License in the form shown in the Addendum below G Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document s license notice H Include an unaltered copy of this License I Preserve the section Entitled History Preserve its Title and add to it an item stating at least the title year new authors and publisher of the Modified Version as given on the Title Page If there is no section Entitled History
33. l to a lt receive gt activity regarding the optional nature of the variable attribute or lt fromPart gt elements if lt fromPart gt elements on an activity then the variable attribute MUST NOT be used on the same activity see SA00055 For lt flow gt a declared link s name MUST be unique among all lt link gt names defined within the same immediately enclosing lt flow gt The value of the linkName attribute of lt source gt or lt target gt MUST be the name of a lt link gt declared in an enclosing lt flow gt activity Every link declared within a lt flow gt activity MUST have exactly one activity within the lt flow gt as its source and exactly one activity within the lt flow gt as its target Two different links MUST NOT share the same source and target ac tivities that is at most one link may be used to connect two activities An activity MAY declare itself to be the source of one or more links by including one or more lt source gt elements Each lt source gt element MUST use a distinct link name Chapter 3 Warnings and Error Messages 12 69 70 71 72 73 74 75 76 77 78 static static static static static static static static static static analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis An activity MAY declare itself to be the target of one or more links by including one or more lt
34. legibly the material this License requires to appear in the title page For works in formats which do not have any title page as such Title Page means the text near the most prominent appearance of the work s title preceding the beginning of the body of the text A section Entitled XYZ means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language Here XYZ stands for a specific section name mentioned below such as Acknowledgements Dedications Endorsements or History To Preserve the Title of such a section when you modify the Document means that it remains a section Entitled XYZ according to this definition The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document These Warranty Disclaimers are considered to be included by reference in this License but only as regards disclaiming warranties any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License 2 VERBATIM COPYING You may copy and distribute the Document in any medium either commercially or noncom mercially provided that this License the copyright notices and the license notice saying this License applies to the Document are reproduced in all copies and that you add no other conditions whatsoever to those of this
35. mat whose specification is available to the general public that is suitable for revising the document straightforwardly with generic text editors or for images composed of pixels generic paint programs or for drawings some widely available drawing editor and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters A copy made in an otherwise Transparent file format whose markup or absence of markup has been arranged to thwart or discourage subsequent modification by readers is not Transparent An image format is not Transparent if used for any substantial amount of text A copy that is not Transparent is called Opaque Examples of suitable formats for Transparent copies include plain ASCII without markup Texinfo input format La TEX input format SGML or XML using a publicly available DTD and standard conforming simple HTML PostScript or PDF designed for human modifica tion Examples of transparent image formats include PNG XCF and JPG Opaque formats include proprietary formats that can be read and edited only by proprietary word proces sors SGML or XML for which the DTD and or processing tools are not generally available and the machine generated HTML PostScript or PDF produced by some word processors for output purposes only The Title Page means for a printed book the title page itself plus such following pages as are needed to hold
36. n Humboldt Universitat zu Berlin Institut f r Informatik Unter den Linden 6 10099 Berlin Germany Homepage http www informatik hu berlin de top mitarbeiter lohmann E mail nlohmann informatik hu berlin de Skype nlohmann Phone 49 30 2093 3070 Fax 49 30 2093 3067 5 5 Help BPELZ0WFN BPEL20WFN is now developed for one and a half year and grown to a quite big program Since November 2006 BPEL20WFN is a GNU package and the development is organized at Savannah https savannah gnu org projects bpel2owfn We are always looking for developers and testers that can help us improving BPEL20WFN Appendix A GNU Free Documentation License 23 Appendix A GNU Free Documentation License Version 1 2 November 2002 Copyright 2000 2001 2002 Free Software Foundation Inc 51 Franklin St Fifth Floor Boston MA 02110 1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document but changing it is not allowed 0 PREAMBLE The purpose of this License is to make a manual textbook or other functional and useful document free in the sense of freedom to assure everyone the effective freedom to copy and redistribute it with or without modifying it either commercially or noncommercially Secondarily this License preserves for the author and publisher a way to get credit for their work while not being considered responsible for modifications made by others This License is a kind of
37. nitial 7 internal initial 8 initial 8 internal initial p2 internal 8 final 8 internal final 9 initial 9 internal initial p3 internal 1 internal final 7 final 7 internal final 9 final 9 internal final in PL req input in PL req out PL ack output out PL ack TRANSITIONS ID ROLES ti 8 internal receive t2 9 internal reply This file has to be read as follows the place p1 has the type internal ie is not connected with an interface place and has the roles 1 internal initial 7 initial Chapter 4 File Formats 20 7 internal initial 8 initial and 8 internal initial While the prefix of each role is the identifier of an activity 1 for the lt process gt 7 for the lt sequence gt and 8 for the lt receive gt the suffix specifies the role inside the respective pattern Without going too much into details 1 internal initial is the role of the initial place of the pattern for the lt process gt whereas for example 7 internal final is the final place of the lt sequence gt s pattern Similarly roles of transitions are specified Multiple roles of a single place arise due to the merging of distinct places during the composition of the several patterns Now that we have convinced ourselves that the generated net reflects the intended behavior of the BPEL process we can export the Petri net model to an output file to process it by analysis tools In this case
38. or distribute Opaque copies of the Document numbering more than 100 you must either include a machine readable Transparent copy along with each Opaque copy or state in or with each Opaque copy a computer network location from which the general network using public has access to download using public standard network protocols a complete Transparent copy of the Document free of added material If you use the latter option you must take reasonably prudent steps when you begin distribution of Opaque copies in quantity to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy directly or through your agents or retailers of that edition to the public It is requested but not required that you contact the authors of the Document well before redistributing any large number of copies to give them a chance to provide you with an updated version of the Document 4 MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above provided that you release the Modified Version under precisely this License with the Modified Version filling the role of the Document thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it In addition you must do these things in the Modified Version A Use in the Title Page and on the covers if any a title d
39. pts ot BPEL20WJBEN a Titri adaa anaa hk etat ute Rd o xL EUER ages 1 2 Invoking BPEL20WEN eee ees 3 2 1 Options nessi ni meeer Ee PEDP Re E RENTRER UE epic ERRORES Ober ve P hanes 3 PE MEO CP T 4 2 1 2 Additional parameters ege eser ek eae RR a ee aeai 5 2 1 8 Output Tormals creer eto Le ERE ee ieee hdd elo Reihe Radeon Ne Pes 6 2 2 Exit Valters du oer RERUM Bex DPRERIV EMPIRE QUEE eh bake FRED ER Rada ns 7 2 9 EXAMPICS 050cseupcageerwcaaesiggasdi peeD4 pU UA RERRIX dee R CDU KERN LE 8 3 Warnings and Error Messages sess 9 4 File Porno ssspsesdu doppi ns Pih et tt beescusd esa d RE 17 5 FAQ and Known Bugs eese 21 5 1 Frequently Asked Questions 0 0 00 cece eee e nett m 21 5 2 Known Bugs 69e eese rok seeded daca retake Ret Ru Ee RR DE e irte e ee GRE e 21 59 Reponn BUGS zu ais qsoeic an E E E OE REE E dare a dub cand sca iE 21 b 4 Contact Person erectie e eerte E EEEE E EE E ade EEG 22 Do Help BPEL20 WEN eee ae Ee adenine een Meade ts 22 Appendix A GNU Free Documentation License 23 Chapter 1 Introducing BPEL20oWFN 1 1 Introducing BPEL20WFEN BPEL20WFN translates a web service expressed in WS BPEL Web Service Business Process Execution Language into an oWFN open Workflow Net This oWFN can be used to e check for controllability or generate the operating guideline using the tool Fiona e check for d
40. ransitions with a dead place in its preset are removed All reduction rules from r1 Additionally unnecessary status places are removed A status place is considered unnecessary if it has no out going arcs All reduction rules from r2 Additionally identical nodes are merged Two nodes are considered identical if their presets and postsets are equal All reduction rules from r3 Additionally remove serial nodes ti P ti t2 p N yox All reduction rules from r4 Additionally remove self loop nodes BPEL20WFN supports different modes for handling input BPEL files modus can be one of the following ast Outputs the AST abstract syntax tree generated while parsing the input file to standard output This option is mostly used for debug Chapter 2 Invoking BPEL20oWFN 5 ging reasons since it shows the implicit transformations and the phylum names used when generating the Petri net cfg For control flow analysis a form of static analysis a CFG Control Flow Graph is generated It can be printed in graphical dot representa tion With the CFG several design flaws of BPEL processes such as cyclic control links or read access to uninitialized variables can be de tected statically Furthermore faulty constellations such as conflicting receiving activities can be found using the cfg mode choreography The choreogr
41. rk Graphics an image file example png The latter looks like this Chapter 4 File Formats 19 in PL req pt out PL ack Petri net generated from example bpel The graphic depicts the generated open workflow net The inner of the net that is all nodes except the interface places are depicted inside the dashed box whereas the interface is depicted outside the frame Input places and all connected transitions are colored orange Similarly output places and connected transitions are colored yellow Gray places belong to the final marking that is the marking p3 is the final marking of the oWFN To reach this final marking the environment has to send a message in PL req followed by receiving a message out PL ack The name of the communication places is composed by the communication direction in or out the partner link s name PL and the operations name req or ack For this very small process it is easy to validate the generated Petri net model that is to compare the intended semantics by the actually modeled semantics Especially the correlation between the nodes of the Petri net and the activities of the input BPEL process is not obvious for larger processes To this end bpel2owfn i example bpel m petrinet p small f info displays an information file consisting of all the Petri net nodes roles PLACES ID TYPE ROLES pi internal 1 internal initial 7 i
42. roblems can arise during the generation of a Petri net model e Critical errors make a further processing of the input process impossible and terminate GNU BPEL20WFN immediately An example for a message is this CubeManagement bpel 566 W00114 variable waitResponse used as variable in from might be uninitialized The first line contains the filename of the input process CubeManagement bpel and the line number 566 of the displayed issue The line number might be imprecise that is it might deviate up or down a few lines After the line number the error code is displayed W00114 stands for a warning with code 114 The detailed description of the messages can be suppressed with option d0 Further details can be taken from the table below Code Type Description 2 static analysis A WS BPEL processor MUST reject any WSDL port Type definition that includes overloaded operation names 3 static analysis If the value of exitOnStandardFault of a scope or process is set to yes then a fault handler that explicitly targets the WS BPEL standard faults MUST NOT be used in that scope 6 static analysis The lt rethrow gt activity MUST only be used within a faultHandler i e catch and lt catchAll gt elements 5 static analysis If the portType attribute is included for readability in a receive reply invoke lt onEvent gt or lt onMessage gt element the value of the portType
43. s found in a parent scope A partner link referenced in an activity was not defined before that is no matching lt partnerLink gt definition was found in the process A correlation set referenced in an activity was not defined before that is no matching lt correlationSet gt definition was found in a parent scope The lt literal gt construct is skipped due to a syntax error This fault can only be detected in mode mode cfg co N Chapter 3 Warnings and Error Messages 15 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 syntax warning notice notice notice notice notice notice notice notice notice notice notice warning warning A UTF 8 character was read in the input file As BPEL20WFN s scan ner does not support Unicode all UTF 8 characters are ignored This message is only displayed when the first UTF 8 character is read CFG analysis detected a read access to a variable that was not initialized before At runtime the standard fault bpel uninitializedVariable would be thrown The process definition defines an abstract process profile and thus al lows several opaque constructs When processing and analyzing an abstract process BPEL20WFN might report error messages that where designed for executable processes for example missing attributes Static analysis errors detected in an abstract process are repor
44. ssion is a constant For the lt forEach gt activity branches is an integer value expression Static analysis MAY be used to detect if the integer value is larger than the number of directly enclosed activities of lt forEach gt at design time when possible for example when the branches expression is a constant For lt forEach gt the enclosed scope MUST NOT declare a variable with the same name as specified in the counterName attribute of lt forEach gt The value of the target attribute on a lt compensateScope gt activity MUST refer to the name of an immediately enclosed scope of the scope containing the FCT handler with the lt compensateScope gt ac tivity This includes immediately enclosed scopes of an event handler lt onEvent gt or lt onAlarm gt associated with the same scope The target attribute of a compensateScope activity MUST refer to 8 Scope or an invoke activity with a fault handler or compensation handler This fault can only be detected in mode mode cfg Chapter 3 Warnings and Error Messages 13 79 static 80 static 81 static 82 static 83 static 84 static 88 static 91 static 92 static 93 static 100 notice analysis analysis analysis analysis analysis analysis analysis analysis analysis analysis The root scope inside a FCT handler MUST not have a compensation handler There MUST be at least one catch or lt catchAll gt element within a lt
45. ted as warnings An lt opaqueActivity gt of an abstract process is modeled by an empty activity When using the parameter small the occurrence of join failures is not modeled Thus any activity is treated as if the attribute suppressJoinFailure is set to yes A user defined transition condition is ignored and modeled as n out of n true instead A user defined transition condition is ignored and modeled as l out of n XOR instead When using the parameter small the FTC fault termination and compensation handlers are not modeled When using the parameter small activities of the negative control flow lt exit gt lt throw gt lt compensate gt and lt compensateScope gt are replaced by an lt empty gt activity A syntax error in the BPEL4Chor chorography file occurred A syntax error in the WSDL input file occurred An XML Schema element nested in a WSDL lt types gt element was ig nored This is usually no problem as WSDL lt types gt are not evaluated in subsequent analysis or translation A variable property element was ignored while parsing the input WSDL file A WSDL lt message gt referenced in a WSDL lt operation gt was not found A WSDL lt portType gt referenced in a WSDL lt role gt was not found This fault can only be detected in mode mode cfg If the attribute suppressJoinFailure is not explicitly defined for an activity
46. the process consists of three activities two basic activities and one structured activities no handlers no links and no variables On the bottom the analysis results are summarized no syntactic static or other error was found Furthermore three implicit activities are counted The WS BPEL specification describes sev eral implicit transformations of the input process as well as standard fault termination and compensation handlers In the considered BPEL process no fault handlers are specified Thus a standard fault handler is added by BPEL20WFN lt faultHandlers gt lt catchAll gt lt sequence gt lt compensate gt lt rethrow gt lt sequence gt lt catchAll gt lt faultHandlers gt To see how the BPEL process looks like after applying the transformation rules and adding the standard handlers BPEL20WFN output the manipulated process using its pretty printer Chapter 4 File Formats 18 bpel2owfn i example bpel m pretty The manipulated process looks like this lt process id 1 abstractProcess no exitOnStandardFault no name exampleprocess suppressJoinFailure no targetNamespace www gnu org software bpel2owfn gt lt partnerLinks gt lt partnerLink id 3 myrole exampleprocess name PL partnerLinkType PLT partnerRole exampleuser gt lt partnerLinks gt lt faultHandlers id 4 gt lt catchAll id 13 gt lt sequence id 12 suppressJoinFailure no gt lt compensate id
47. tion triggers different debug levels and can enable additional information from Flex and Bison about how the input is lexed and parsed Debug level Chapter 2 Invoking BPEL20oWFN 4 eA flex bison reduce 0 5 Apply several structural reduction rules to the generated Petri net model implies mode petrinet or choreography The rules preserve deadlocks livelocks and all deadlock free communicating partners The rules are organized in reduction levels r 0 5 OQ 64 to 2 55 2 1 1 Modes When invoking BPEL20WFN several modes are possible mode modus m modus When errors are found only display the error code and skip additional information No debug information but display warning and error messages Fur thermore detailled information about syntax errors are displayed All messages from d1 Additionally information about the current steps is displayed All messages from d2 Additionally the structure of the process is shown i e when a Petri net is generated All messages from d3 Additionally a message is displayed each time a function is entered or left Displays messages from Flex Can be combined with any other debug level Displays messages from Bison Can be combined with any other debug level No rules are applied standard Structural dead nodes are removed that is unmarked places with empty preset and t
48. uments with a single copy that is included in the collection provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects You may extract a single document from such a collection and distribute it individually under this License provided you insert a copy of this License into the extracted document and follow this License in all other respects regarding verbatim copying of that document AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other separate and independent documents or works in or on a volume of a storage or distribution medium is called an aggregate if the copyright resulting from the compilation is not used to limit the legal rights of the compilation s users beyond what the individual works permit When the Document is included in an aggregate this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document If the Cover Text requirement of section 3 is applicable to these copies of the Document then if the Document is less than one half of the entire aggregate the Document s Cover Texts may be placed on covers that bracket the Document within the aggregate or the electronic equivalent of covers if the Document is in electronic form Otherwise they must appear on printed covers that bracket the whole aggregate TRANSLATION Translation is considered a kind of modific
49. ut the process These algorithms Furthermore design flaws such as cyclic control links or conflicting receiving activities are detected Fiona is available at http www informatik hu berlin de top tools4bpel Chapter 1 Introducing BPEL20oWFN 2 Petri Net API Pattern Repository Output Petri Net The annotated abstract syntax tree is used to generate a Petri net model of the BPEL process All Petri net related functions adding removing and merging of nodes structural reduction are provided by the Petri net API application programming interface For each BPEL construct several patterns with different degrees of abstraction are stored in the pattern repository Using the informa tion gained by static analysis the most abstract pattern applicable is used The generated Petri net model can be exported to many file for mats such as PNML LoLA Fiona oWFN INA APNN or PEP Chapter 2 Invoking BPEL20oWFN 3 2 Invoking BPEL20WFEN The standard invocation of BPEL20WEN is bpel2owfn i service bpel m petrinet f owfn o where service bpel isa BPEL process The option f owfn causes BPEL20WFN to generate an open workflow net option m petrinet This net is written to a file named service owfn because of the option o BPEL20WFN can be called without any parameter In this case it acts as a simple parser for BPEL processes that reads its input from the standard input stdin 2 1 Options B
50. vities yields to situations where a further analysis of the BPEL process is impossible In this case the syntax of the process has to be fixed or non standard elements have to be removed or out commented When a syntax error occurs BPEL20WFN tries to recover and contin ues parsing the input file after skipping the faulty or unknown element If it is possible to continue the analysis results might be faulty In this case the syntax of the process has to be fixed or non standard elements have to be removed or out commented CFG analysis detected two receiving activities ie receive lt onEvent gt lt onMessage gt synchronous lt invoke gt that might be ac tivated concurrently and share the same partner link port type op eration and correlation set When a message is sent to the process these activities are in conflict that is it is not defined which activ ity will receive an inbound message At runtime the standard fault ppel conflictingReceive would be thrown 9 A mandatory attribute of an activity was not defined Especially for communicating activities the absence of partnerLink and operation might hamper the subsequent analysis and Petri net generation An attribute was set to a value that violates the attribute s given type Only the types tBoolean tInitiate tRoles and tPattern are checked A variable referenced in an activity was not defined before that is no matching lt variable gt definition wa

2.0.x

Contents

Download Pdf Manuals

Related Search

Related Contents