Difference between revisions of "GVNotificationNode"

From GreenVulcano Wiki
Jump to: navigation, search
(JMXNotification)
Line 127: Line 127:
 
* yes
 
* yes
 
* no
 
* no
 +
|-
 
| objectName || required || This attribute defines the objectName the notification broadcaster.
 
| objectName || required || This attribute defines the objectName the notification broadcaster.
 
|-
 
|-

Revision as of 11:12, 23 February 2012

GVNotificationNode element defines the nodes where GreenVulcano® ESB indicates a notification on execution of the workflow.

Each GVNotificationNode has an associated list of notifications (Notification) that manage the type of message to send and the technology used to make the notification (Log4J, JMX).

The order in which notifications are made is that in which they are defined.

A notification can be defined as 'critical', which is vital for the proper execution of the workflow. If a notification 'critical' throws an exception, the flow fails and the exception is inserted into the buffer specified by the attribute 'output' of GVNotificationNode.

The GVNotificationNode does not read an input buffer, as may be specified a different one for each notification.

The following table shows the GVNotificationNode element's attributes:

Attribute Type Description
type fixed This attribute must assume the value flow-node.
op-type fixed This attribute must assume the value notification.
class fixed This attribute must assume the value it.greenvulcano.gvesb.core.flow.GVNotificationNode.
id required Uniquely identifies the notification node.

Not to be confused with the id of individual notifications.

on-critical-error required A notification can be defined as 'critical', which is vital for the proper execution of the workflow.

The parameter 'on-critical-error' is used to decide whether to stop or not the notifications sequence in the occurrence of exception for a notification defined 'critical' The attribute's admitted values are:

  • break
  • continue
output required This parameter specifies the output buffer where to put a possible exception generated by a 'critical' notification.
next-node-id required Indicates the next node in the workflow to execute when the operation ends.
point-x optional X position of the node in the VulCon workflows editor.

Immutable, used by VulCon®.

point-y optional Y position of the node in the VulCon workflows editor.

Immutable, used by VulCon®.

dump-in-out optional If true enable the dump of the input/output GVBuffer.

Default false.

dump-env-in-out optional If true enable the dump of the input/output Execution Environment.

Default false.

Might contain the following subelements:

Log4JNotification

This element represents GreenVulcanoESB notifications using Log4j. Each element of notification have sub-elements that define the message: • • • StaticMessage A static message that does not provide dynamic parameters and can be associated to any notification GVBufferMessage Defines a notification relating to a GVBuffer found in the execution environment. ExceptionMessage Defines a notification relating to an Exception found in the execution environment. The Log4JNotification Element is used by: GVNotificationNode. The following table shows the Log4JNotification element's attributes:

Attribute Type Description
type fixed This attribute must assume the value notification-node.
class fixed This attribute must assume the value it.greenvulcano.gvesb.notification.Log4JNotification.
id required This attribute defines the id (unique) of the notification.
logger required This attribute defines the logger used to write the notification.
level required This attribute defines the trace level.

The attribute's admitted values are:

  • INFO
  • DEBUG
  • WARN
  • ERROR
  • FATAL
critical required This attribute defines whether or not the notification is critical for the flow.

If a notification 'critical' throws an exception, the flow fails, and the exception is included in the buffer specified by the parameter 'output' of NotificationNode. The attribute's admitted values are:

  • yes
  • no
input optional This attribute defines the input buffer, from which read data for notifications execution.

A different buffer can be specified for each notification.

Might contain the following sub-elements:

JMXNotification

This element represents the GreenVulcano® ESB Notificaions using JMX.

Each Notification element has sub-elements that define the message:

  • StaticMessage: A static message that does not provide dynamic parameters and can be associated to any notification
  • JMXGVBufferNotification: Defines a notification relating to a GVBuffer found in the execution environment.
  • JMXExcNotification: Defines a notification relating to an Exception found in the execution environment.

The following table shows the JMXNotification element's attributes:

Attribute Type Description
type fixed This attribute must assume the value notification-node.
class fixed This attribute must assume the value it.greenvulcano.gvesb.notification.JMXNotification.
id required This attribute defines the id (unique) of the notification.
critical required This attribute defines whether or not the notification is critical for the flow.

If a notification 'critical' throws an exception, the flow fails, and the exception is included in the buffer specified by the parameter 'output' of NotificationNode. The attribute's admitted values are:

  • yes
  • no
objectName required This attribute defines the objectName the notification broadcaster.
notificationType required This attribute defines the notification type
input optional This attribute defines the input buffer, from which read data for notifications execution.

A different buffer can be specified for each notification.

mainInput optional This attribute defines the input buffer, from which read data for notifications execution when the "input" buffer doesn't contain a GVBuffer.

A different buffer can be specified for each notification.

Might contain the following sub-elements: