Home | Table of Contents | Send a JMS Message | CloverETL 4.6.1
--- | --- | ---
Prev | Tasks | Next

## 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 name | A 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 name | A JNDI name of a connection factory. It depends on a JMS provider.
Destination JNDI name | JNDI name of a message queue/topic on the server
Username | Username for connection to a JMS message broker
Password | Password for connection to a JMS message broker
URL | URL of a JMS message broker
JMS pattern | This 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.
Text | Body of a JMS message. It is also possible to use placeholders. See Placeholders of send e-mail task for details.

Figure 20.8. Web GUI - Task JMS message editor

Table 20.14. Parameters of "Send a JMS Message"

event | Event that has triggered the task.
now | Current date-time
task | The 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_USERNAME | Username of the user who caused the event
EVENT_USER_ID | Numeric ID of the user who caused the event.
EVENT_SCHEDULE_DESCRIPTION | Description of the schedule
EVENT_SCHEDULE_EVENT_TYPE | Type of the schedule - SCHEDULE_ONETIME or SCHEDULE_PERIODIC.
EVENT_SCHEDULE_ID | Numeric ID of the schedule.
EVENT_SCHEDULE_LAST_EVENT | Date-time of the latest schedule triggering (in java.util.Date.toString() format).

Prev | Up | Next
Archive Records | Home | Table of Contents | Execute Groovy Code