Send a JMS Message

This type of task is useful for notifications about result of graph execution. E.g. you can create a graph event listener with this task type to be notified about each failure in a specific sandbox or failure of a particular graph.

JMS messaging requires JMS API (jms.jar) and third-party libraries. All these libraries must be available on application server classpath. Some application servers contain these libraries by default, some do not, thus the libraries must be added explicitly.

Table 20.13. Attributes of JMS message task

Task type"JMS message"
Initial context Choose between default and custom initial context.
Initial context class nameA full class name of javax.naming.InitialContext implementation. Each JMS provider has its own implementation. E.g., for Apache MQ it is "org.apache.activemq.jndi.ActiveMQInitialContextFactory". If it is empty, server uses the default initial context.
Broker URL 
Connection factory JNDI nameA JNDI name of a connection factory. It depends on a JMS provider.
Destination JNDI nameJNDI name of a message queue/topic on the server
UsernameUsername for connection to a JMS message broker
PasswordPassword for connection to a JMS message broker
URLURL of a JMS message broker
JMS patternThis select box is available only when user is creating a new record. It contains all predefined JMS message patterns. If user chooses any of them, text field below is automatically filled with value from pattern.
TextBody of a JMS message. It is also possible to use placeholders. See Placeholders of send e-mail task for details.

Web GUI - Task JMS message editor

Figure 20.8. Web GUI - Task JMS message editor


Table 20.14. Parameters of "Send a JMS Message"

eventEvent that has triggered the task.
nowCurrent date-time
taskThe triggered task.
user Object representing owner of the schedule. It contains sub-properties that are accessible using dot notation (i.e. ${user.email}) e-mail, username, firstName, lastName, groups (list of values).
schedule Object representing the schedule that triggered this task. It contains sub-properties that are accessible using dot notation (i.e. ${schedule.description}) description, startTime, endTime, lastEvent, nextEvent, fireMisfired.
EVENT_USERNAMEUsername of the user who caused the event
EVENT_USER_IDNumeric ID of the user who caused the event.
EVENT_SCHEDULE_DESCRIPTIONDescription of the schedule
EVENT_SCHEDULE_EVENT_TYPEType of the schedule - SCHEDULE_ONETIME or SCHEDULE_PERIODIC.
EVENT_SCHEDULE_IDNumeric ID of the schedule.
EVENT_SCHEDULE_LAST_EVENTDate-time of the latest schedule triggering (in java.util.Date.toString() format).