Changes for page 4. The iXPath BPMN
Last modified by Achraf El Kari on 2022/06/13 13:18
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 6 removed)
Details
- Page properties
-
- Content
-
... ... @@ -7,7 +7,7 @@ 7 7 **iXPath** uses the BPMN (Business Process Model and Notation) standard for the translation part. 8 8 BPMN is a business process modeling method to describe the business activities of an organization in a graphical representation. 9 9 10 -Below an example of aflow traced by the iXPath BPMN module:10 +Below an example of flow traced by the iXPath BPMN module: 11 11 12 12 [[image:1615831422135-492.png]] 13 13 ... ... @@ -15,40 +15,6 @@ 15 15 16 16 = Connectors = 17 17 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 - 22 -== Listeners == 23 - 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. 25 - 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 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. 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 - 40 -== Scenario == 41 - 42 - 43 -== Routing == 44 - 45 - 46 -== Exploitation == 47 - 48 - 49 -== E) Timers == 50 - 51 - 52 52 = Gateways = 53 53 54 54 == Inclusif gateway ==
- 1615902036864-240.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.aelkari - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.3 KB - Content
- 1615903474893-102.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.aelkari - Size
-
... ... @@ -1,1 +1,0 @@ 1 -10.1 KB - Content
- 1615903500591-246.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.aelkari - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.4 KB - Content
- 1615903536880-750.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.aelkari - Size
-
... ... @@ -1,1 +1,0 @@ 1 -8.4 KB - Content
- 1615903600906-895.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.aelkari - Size
-
... ... @@ -1,1 +1,0 @@ 1 -10.2 KB - Content
- 1615903620708-998.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.aelkari - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.5 KB - Content