This documentation is for WSO2 Enterprise Service Bus version 5.0.0. For the latest ESB, view the latest WSO2 Enterprise Integrator documentation.

All docs This doc

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


titleTask handling in a clustered environment

In a clustered environment, tasks are distributed among server nodes according to the round-robin method , by default. If required, you can change this default task handling behavior so that tasks are distributed randomly, or according to a specific rule. This is a server-level setting that is configured in the tasks-config.xml file.

  • See Configuring the Task Scheduling Component for instructions on configuring the task handling behavior at server-level.
  • You can also configure the task handling behavior at task-level , by specifying the Pinned Servers for a task. Note that this setting overrides the server-level configuration.

Also, note that a scheduled task will only run on one of the nodes (at a given time) in a clustered environment. The task will failover to another node, only if the first node fails.


Follow the instructions below to add and schedule a task in ESB Management Console.

  1. Sign in. Enter youruser nameand your user name and password to log in to the ESB Management Console.
  2. Click Main in the left menu to access the Manage menu.
  3. In the Manage menu, click Scheduled Tasks under Service Bus.
  4. The Scheduled Tasks page appears, where you can add, edit, and delete tasks.
  5. Click Add Task.
  6. The New Scheduled Task page appears. Enter the required details into the fields.
    1. Task Name - Name of a scheduled task.
    2. Task Group - The group name to grouping tasks. The group name synapse.simple.quartz belongs to ESB - Synapse. All available groups are displayed as a drop-down menu. If there are tasks belong belonging to some other domains, for example WSO2 Mashups tasks, then those will be shown here as a as separate group names.
    3. Task Implementation - The implementation class of the task. To use the default task implementation that is available with the ESB (and therefore can be used without downloading any third-party libraries or custom JARs), specify  org.apache.synapse.startup.tasks.MessageInjector. This class simply injects a specified message into the Synapse environment at ESB startup. For more information on writing custom task implementations, see Writing Tasks.
    4. Trigger Type- Trigger type for the task. This can be selected as either "Simple" or "Cron."
      • Simple Trigger - Defined by specifying a count and an interval, implying that the task will run a count number of times at specified intervals.
        • Count - The number of times the task will be executed.
        • Interval - The interval between consecutive executions of a task.
      • Cron Trigger - Defined using a cron expression.
    5. Anchor
      Pinned Servers - The list of ESB server nodes that will run the task. You can specify the IP addresses of the required nodes. 


      This setting can be used if you want the task to run on a selected set of nodes in an ESB cluster. Note that the task will only run on one of the nodes at a time. It will failover to another node, only if the first node fails.

      As explained above, pinned servers will override the default task handling behavior defined at server-level (for this particular task). However, if rule-based task handling is specified at server-level, you need to ensure that the same server nodes you specify as pinned servers for the task are also specified for the task handling rule at server-level.

  7. Click Load Task Properties to see the instance properties of the task implementation.
  8. Use the instance properties fields as follows:
    • Property Name - The unique name of the task property.
    • Property Type- The type of property, either Literal or XML.
    • Property Value - The value of the property.
    • Action - Allows you to delete a property.

    For more information on setting the properties for the default task implementation, see Examples and Injecting the message to a named sequence or proxy service below.

    The org.apache.synapse.startup.tasks.MessageInjector implementation takes the following properties: 
    • format - defines the format of the message similar to Address Endpoint formats: soap11, soap12, pox, get
    • message  - you can provide an XML or literal value depending on message format.


      When you add a scheduled task, it is mandatory to provide a value for the message property. Therefore, even If you do not want to send a message body, you have to provide an empty payload as the value to avoid an exception being thrown.

    • soapAction - specify the SOAP Action to use when sending the message to the endpoint. 
    • to - specify the endpoint address. 
    • injectTo - specify whether to inject a message to a proxy service or sequence. This field takes values 'sequence' or 'proxy' and 'main' to inject to main sequence. 
    • proxyName - if injectTo contains 'proxy' then the name of the proxy to inject the message to is specified here. 
    • sequenceName - if injectTo contains 'sequence' then the name of the sequence to inject the message to is specified here. 
  9. Click Schedule to apply the settings.