With the Message Store Mediator (New in version 4.0), you can store messages in a given Message Store.
UI Configuration
...
The Store mediator enqueues messages passing through its mediation sequence in a given message store. It can serve as a dead letter channel if it is included in a fault sequence and if its message store is connected to a message processor that forwards all the messages in the store to an endpoint.
...
Syntax
| Info |
|---|
The Store mediator is a content aware mediator. |
| Code Block | ||
|---|---|---|
| ||
<axis2ns1:store xmlns:axis2ns1="http://ws.apache.org/ns/synapse" messageStore="string" sequence="string"></axis2ns1:store> |
UI Configuration
The parameters available to configure the Store mediator is as follows.
| Parameter Name | Description |
|---|---|
| Message Store | Select the message store where messages will be stored. You |
...
| should add the message store to the ESB before you can select it here. |
| On Store Sequence |
...
| The |
...
| sequence that will be called before the message gets stored. |
...
| This sequence should be pre-defined in the registry before it can be entered here. Click either Configuration Registry or Governance Registry |
...
| to select the required sequence from the resource tree. |
Example
A proxy service can be configured with the Store mediator as follows to save messages in a message store named JMSMS.
| Code Block | ||
|---|---|---|
| ||
<proxy name="SimpleProxy" transports="http https" startonload="true" trace="disable">
<target>
<insequence>
<property name="FORCE_SC_ACCEPTED" value="true" scope="axis2" type="STRING"></property>
<property name="OUT_ONLY" value="true" scope="default" type="STRING"></property>
<store messagestore="JMSMS"></store>
</insequence>
</target>
</proxy> |