Message Processors

A message processor is used to deliver messages that have been temporarily stored in a message store. This approach is useful for serving traffic to back-end services that can only accept messages at a given rate, whereas incoming traffic to the ESB arrives at different rates. You use the Store mediator to store messages in the message store, and then you use a message processor to deliver messages from the message store to the back-end service at a given rate. Using message processors and message stores allows you to implement different messaging and integration patterns.

You can implement your own message processor by implementing the MessageProcessor interface and adding the message processor to the configuration. The ESB ships with the following message processor implementations:

• Message Forwarding Processor
• Message Sampling Processor

Message Processor Configuration

<messageProcessor name="string" messageStore="classname" >
                <parameter name="string" > "string" </parameter>*
</messageProcessor>

You enable a message processor in the ESB configuration by adding the <messageProcessor> element. This element is a top-level entry in the configuration and must have a unique name. The class attribute value is the fully qualified class name of the underlying message processor implementation, and the parameters section is used to configure the parameters that are needed by that implementation.

You can add, edit, delete, and activate/deactivate message processors and perform scheduled message processor operations in the Management Console.