Difference between revisions of "Main nodes"
(Created page with "==Start== Add img Nodo start Represents the node of a flow started. ==Check== Add img Nodo Check Is the node where {{GVESB}} makes decisions and determines what the next nod...") |
|||
| Line 1: | Line 1: | ||
| − | + | The main nodes in order to draw a flow are: | |
| − | + | *Start Node: Represents the node of a flow started. | |
| − | + | *Check Node: Is the node where {{GVESB}} makes decisions and determines what the next node to execute. Each Check node has a basic routing mechanism that chooses | |
| − | Represents the node of a flow started. | + | the next node only of the presence or absence of errors indicated by exceptions. |
| − | + | *Wait Node: Allows you to insert delays in the execution of a stream. | |
| − | + | *Notification Node: It allows a notification to signal on the process flow.For each 'NotificationNode' is associated with a list of notifications (Notification) | |
| − | + | that handle the type of message to send and the medium on which to write the notification. ES: log4j, JMX. The order in which notifications are | |
| − | + | performed is the insertion order. A notification can be described as 'critical', which is vital for the proper execution of the flow. If | |
| − | + | a notification 'critical' throws an exception, the flow fails, and the exception is inserted into the buffer specified by the 'output' of | |
| − | Is the node where {{GVESB}} makes decisions and determines what the next node to execute. Each Check node has a basic routing mechanism that chooses the next node only of the presence or absence of errors indicated by exceptions. | + | NotificationNode. The NotificationNode not read an input buffer, as may be specified a different one for each notification. |
| − | + | *ChangeGVBuffer Node: It lets you make a change in the data buffer. You can perform manipulations on the data buffer, set new properties or modify existing ones | |
| − | + | using scripting languages such as JavaScript or OGNL. | |
| − | + | *SavePoint Node: DB allows you to save the state of execution of the workflow. They can also be stored business information in the form of name-value pairs. | |
| − | + | *End Node: End the flow execution. | |
| − | |||
| − | Allows you to insert delays in the execution of a stream. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | It allows a notification to signal on the process flow.For each 'NotificationNode' is associated with a list of notifications (Notification) that handle the type of message to send and the medium on which to write the notification. | ||
| − | ES: log4j, JMX | ||
| − | The order in which notifications are performed is the insertion order. | ||
| − | A notification can be described as 'critical', which is vital for the proper execution of the flow. | ||
| − | |||
| − | The NotificationNode not read an input buffer, as may be specified a different one for each notification. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | It lets you make a change in the data buffer. | ||
| − | You can perform manipulations on the data buffer, set new properties or modify existing ones using scripting languages such as JavaScript or OGNL. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | DB allows you to save the state of execution of the workflow. They can also be stored business information in the form of name-value pairs. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | End the flow execution. | ||
Revision as of 15:16, 23 January 2012
The main nodes in order to draw a flow are:
- Start Node: Represents the node of a flow started.
- Check Node: Is the node where GreenVulcano® ESB makes decisions and determines what the next node to execute. Each Check node has a basic routing mechanism that chooses
the next node only of the presence or absence of errors indicated by exceptions.
- Wait Node: Allows you to insert delays in the execution of a stream.
- Notification Node: It allows a notification to signal on the process flow.For each 'NotificationNode' is associated with a list of notifications (Notification)
that handle the type of message to send and the medium on which to write the notification. ES: log4j, JMX. The order in which notifications are
performed is the insertion order. A notification can be described as 'critical', which is vital for the proper execution of the flow. If
a notification 'critical' throws an exception, the flow fails, and the exception is inserted into the buffer specified by the 'output' of
NotificationNode. The NotificationNode not read an input buffer, as may be specified a different one for each notification.
- ChangeGVBuffer Node: It lets you make a change in the data buffer. You can perform manipulations on the data buffer, set new properties or modify existing ones
using scripting languages such as JavaScript or OGNL.
- SavePoint Node: DB allows you to save the state of execution of the workflow. They can also be stored business information in the form of name-value pairs.
- End Node: End the flow execution.
