Wiki source code of The iXPath BPMN
Version 11.1 by Achraf El Kari on 2021/03/16 15:05
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{box cssClass="floatinginfobox" title="**Contents**"}} |
| 2 | {{toc/}} | ||
| 3 | {{/box}} | ||
| 4 | |||
| |
2.2 | 5 | = Introduction = |
| |
1.1 | 6 | |
| |
2.2 | 7 | **iXPath** uses the BPMN (Business Process Model and Notation) standard for the translation part. |
| 8 | BPMN is a business process modeling method to describe the business activities of an organization in a graphical representation. | ||
| 9 | |||
| |
2.3 | 10 | Below an example of a flow traced by the iXPath BPMN module: |
| |
2.2 | 11 | |
| 12 | [[image:1615831422135-492.png]] | ||
| 13 | |||
| 14 | As we can see, there is 2 main types : Connectors and Gateways | ||
| 15 | |||
| |
1.3 | 16 | = Connectors = |
| |
1.1 | 17 | |
| |
2.4 | 18 | A connector is an algorithm that is executed via a trigger. In iXPath, the trigger is always an input file. |
| 19 | |||
| 20 | In this part, we go through each of the connectors and their particularities: | ||
| 21 | |||
| |
4.1 | 22 | == Listeners == |
| |
2.4 | 23 | |
| |
6.1 | 24 | A listening connector (or listener) is the entry point for a scenario. It allows the event created to be routed through a communication channel (FTP, SFTP, AS2, MAIL, FILE, Webservice). Communication configuration is required to handle those connectors. |
| |
2.4 | 25 | |
| |
6.1 | 26 | **//Note ~://** iXPath detects incoming events in real time. |
| 27 | |||
| 28 | (% style="margin-left:auto; margin-right:auto" %) | ||
| 29 | |=(% style="width: 138px;" %)Listener Name|=(% style="width: 137px;" %)Icon|=(% style="width: 715px;" %)Description | ||
| |
9.1 | 30 | |(% style="width:138px" %)[[FTP Listener>>Documentation.iXPath.The iXPath BPMN.Listeners.FTP Listener.WebHome]]|(% style="width:137px" %)[[image:1615902036864-240.png||height="66" width="69"]]|(% style="width:715px" %)Listen on a **FTP/FTPS** communication, on specific user (created locally) and on specific directory. |
| |
6.1 | 31 | |(% style="width:138px" %)SFTP Listener|(% style="width:137px" %) |(% style="width:715px" %)Listen on a **SFTP** communication, on specific user (created locally) and on specific directory. |
| 32 | |(% style="width:138px" %) |(% style="width:137px" %) |(% style="width:715px" %) | ||
| 33 | |(% style="width:138px" %) |(% style="width:137px" %) |(% style="width:715px" %) | ||
| 34 | |(% style="width:138px" %) |(% style="width:137px" %) |(% style="width:715px" %) | ||
| 35 | |(% style="width:138px" %) |(% style="width:137px" %) |(% style="width:715px" %) | ||
| 36 | |(% style="width:138px" %) |(% style="width:137px" %) |(% style="width:715px" %) | ||
| 37 | |(% style="width:138px" %) |(% style="width:137px" %) |(% style="width:715px" %) | ||
| 38 | |(% style="width:138px" %) |(% style="width:137px" %) |(% style="width:715px" %) | ||
| 39 | |||
| |
4.1 | 40 | == Scenario == |
| |
2.4 | 41 | |
| 42 | |||
| |
4.1 | 43 | == Routing == |
| |
2.4 | 44 | |
| 45 | |||
| |
4.1 | 46 | == Exploitation == |
| |
2.4 | 47 | |
| 48 | |||
| 49 | == E) Timers == | ||
| 50 | |||
| 51 | |||
| |
1.3 | 52 | = Gateways = |
| |
1.1 | 53 | |
| |
1.3 | 54 | == Inclusif gateway == |
| |
1.1 | 55 | |
| |
1.3 | 56 | == Exclusif gateway == |
| |
1.1 | 57 | |
| |
1.3 | 58 | == parallel gateway == |
| 59 | |||
| 60 | = Variables = | ||
| 61 | |||
| 62 | == System variables == | ||
| 63 | |||
| 64 | == Local variables == | ||
| 65 | |||
| 66 | = Conditions = |