...
When adding a mediator to a sequence , you can configure the mediator in design view or in source view, which allows you to . Source view provides the XML representation of the configurations done in the UI. When you edit the source XML (different mediators have their own XML configurations). all changes immediately reflect in the design view as well.
Each mediator has its own XML configuration. In the source view of the following mediators, you can comment out required lines if necessary when you edit the XML.
- Aggregate Mediator
- Cache Mediator
- Filter Mediator
- In Mediator
- Iterate Mediator
- Out Mediator
- Sequence Mediator
- Synapse Mediator
- Template Mediator
- Validate Mediator
| Tip |
|---|
It is also possible to comment out required lines in the Synapse definition as well as in the source view of the complete ESB configuration. |
Mediators in a sequence can be one of the following types:
...
The standard mediators in WSO2 ESB are listed in the table below. Click a link for details on that mediator. There are also many samples that demonstrate how to use mediators.
The
...
WSO2 ESB mediator catalog
Category | Name | Description |
|---|---|---|
| Core | Call | Invoke a service in non blocking synchronous manner |
| Enqueue | Uses a priority executor to ensure high-priority messages are not dropped |
Sends a message |
Moves the message from the In flow to the Out flow, skipping all remaining configuration in the In flow |
Inserts a reference to a sequence |
| Respond | Stops processing on the message and sends it back to the client |
| Event | Sends event notifications to an event source, publishes messages to predefined topics |
Drops a message |
| Call Template | Constructs a sequence by passing values into a sequence template |
Enriches a message |
Sets or remove properties associated with the message |
Logs a message | ||
Filter | Filters a message using XPath, if-else kind of logic |
Applies to messages that are in the Out path of the ESB |
Applies to messages that are in the In path of the ESB |
| Validate | Validates XML messages against a specified schema. |
Filters messages using XPath, switch logic |
Routes messages based on XPath filtering |
Implements complex routing rules (Header based routing, content based routing and other rules)
| |||||||
Transform | Performs XSLT transformations on the XML payload |
| FastXSLT | Performs XSLT transformations on the message stream |
Modifies and rewrites URLs or URL fragments |
| XQuery | Performs XQuery transformation |
Sets or removes SOAP headers |
Fault (also called Makefault) | Create SOAP Faults |
| PayloadFactory | Transforms or replaces message content in between the client and the backend server | |
Advanced | Evaluates messages based on whether the same message came to the ESB |
| ForEach | Splits a message into a number of different messages by finding matching elements in an XPath expression of the original message. |
Clones a message |
Stores messages in a predefined message store |
Splits a message |
Combines a message |
Blocks web services calls |
Executes a set of mediators transactionally |
Limits the number of messages |
Writes data to database |
Retrieves information from database |
| EJB | Calls an external Enterprise JavaBean(EJB) and stores the result in the message payload or in a message context property. |
Executes rules | |
| Builder | Builds the actual SOAP message, from a message, which is coming into the ESB through the Binary Relay. |
Evaluates user actions against a XACML policy |
2-legged OAuth support |
| Smooks | Used to apply lightweight transformations on messages in an efficient manner. | |
| Data Mapper | Converts and transforms one data format to another, or changes the structure of the data in a message. | |
| Extension | Bean | Manipulates JavaBeans |
Creates and executes a custom mediator |
Executes a custom command |
Executes a mediator written in Scripting language |
Creates a mediator managed by Spring | ||
| Agent | BAM | Captures data events and sends them to the BAM server |
| Publish Event | Constructs events and publishes them to different systems such as WSO2 BAM/DAS/CEP/SP via event sinks. |