TriggeredChannel has it's uses

A TriggeredChannel is one that requires an external trigger

I haven’t posted for a while, I can see that my last post was in June; the summer holidays must have been quite exciting (or frenetic); can’t remember now. Anyway, this post is about something that isn’t really used in the adapter; which is TriggeredChannel. It is a channel where the workflows are only started when an external event occurs; hence the name. Once the trigger is received; workflows are started, the channel waits for the workflows to do their thing, and then stops them afterwards and is then ready for the next trigger.

There are some subtle differences between a TriggeredChannel and a normal channel; the consumers inside each workflow should really be based around things that actively poll (i.e. AdaptrisPollingConsumer implementations) rather than consumers that wait for activity (like a JmsConsumer or the like, if you need JMS behaviour, there is JmsPollingConsumer). The polling implementation for each consumer should be a OneTimePoller rather than one of the other implementations. This type of channel also handles errors and events slightly differently. By default, the channel will supply its own message error handling implementation, rather than using the Adapter’s (in this case a com.adaptris.core.triggered.RetryMessageErrorHandler, infinite retries at 30 second intervals); you can change it if you want, but it must still be an instance of com.adaptris.core.triggered.RetryMessageErrorHandler. The trigger itself could be anything you want, it has a consumer/producer/connection element, so you could listen for an HTTP request, or use a JmxChannelTrigger which registers itself as a standard MBean, so you can trigger it remotely via jconsole or the like.


If for instance, an adapter is running on a remote machine, and you don’t have the capability to login to the filesystem and retry failed messages then you could use a TriggeredChannel to copy all the files from the bad directory into a retry directory so that the FailedMessageRetrier is triggered. This is quite a marginal use case; if you have the type of failure where messages can be automatically retried without manual intervention then a normal RetryMessageErrorHandler will probably be a better bet. We’ll make the trigger a message on a JMS Topic; any message received on the topic retry-failed-messages will start the channel, files will be copied from the bad directory to the retry directory and then the channel will stop.

<channel xsi:type="java:com.adaptris.core.triggered.TriggeredChannel">
    <connection xsi:type="java:com.adaptris.core.jms.PasConnection">
       ... config skipped for brevity
    <consumer xsi:type="java:com.adaptris.core.jms.PasConsumer">
      <destination xsi:type="java:com.adaptris.core.ConfiguredConsumeDestination">
        <configured-thread-name>JMS RETRY Trigger</configured-thread-name>
  <consume-connection xsi:type="java:com.adaptris.core.NullConnection" />
  <produce-connection xsi:type="java:com.adaptris.core.NullConnection" />
    <workflow xsi:type="java:com.adaptris.core.StandardWorkflow">
      <consumer xsi:type="java:com.adaptris.core.fs.FsConsumer">
        <destination xsi:type="java:com.adaptris.core.ConfiguredConsumeDestination">
        <poller xsi:type="java:com.adaptris.core.triggered.OneTimePoller">
      <service-collection xsi:type="java:com.adaptris.core.ServiceList"/>
      <producer xsi:type="java:com.adaptris.core.fs.FsProducer">
        <destination xsi:type="java:com.adaptris.core.ConfiguredProduceDestination">

© 2017. All rights reserved.

Powered by Hydejack v6.6.1