Routing between components in an SCA assembly.

Validation of incoming messages into an SCA assembly.

Transformation of data from one format to another within an SCA assembly.

Filtering to allow the selection of components to invoke based on the message content.

Oracle Mediator supports static and dynamic routing rules.

XSL transforms can be used in Mediator to provide mappings between one data format and another.

Validation of input data to Mediator can be done using the Schematron file. Input data can also be validated against an XSD using the validate syntax option in the Mediator option.

Mediator has a feature to create events on target types for static or dynamic rules.

Dynamic routing of messages is possible through the asynchronous interface in Mediator.

Dynamic routing of rules in the Oracle Mediator component allows the externalizing of the routing logic to an Oracle Rules Dictionary.

EDN uses JMS to deliver events from subscribers to publishers, but the configuration of JMS queues and topics and any associated filters is hidden from users of the EDN service.

Business events are defined using the Event Definition Language (EDL) in Oracle SOA Suite 11g.

Header properties are not propagated to the target service automatically. If the pass through property is enabled, it is propagated automatically.

When the underlying WSDL is changed, the Mediator need not be rebuilt; it can be refreshed to obtain the changes in the WSDL.

Switch case is the first action in Mediator, followed by transformation, assignment, and invoking of the required service/event.

Oracle Mediator initiates a new transaction for processing each parallel run.

The callout class must implement the oracle.tip.mediator.common.api.IjavaCallout interface.

Callouts are available for both static and dynamic routings.

Oracle Mediator provides support for setting rules based on message payload or message headers.

Oracle Mediator provides support for synchronous and asynchronous request and response interactions.

A routing rule can be either executed in parallel or sequentially.

Oracle Mediator supports data transformation from one XML schema to another using XSL.

Oracle Mediator provides support for validating the incoming message payload using a Schematron or an XSD file.

Oracle Mediator supports subscribing to business events and raising business events.

Oracle Mediator can process messages consisting of multiple parts.

Oracle Mediator supports both manual error handling and error handling based on a fault policy.

Oracle Mediator WSDLs can be modified by adding or deleting operations. After modifying the WSDL file, use the refresh WSDL dialog to synchronize the changes.

The echo option is available for synchronous operations like request/reply and request/reply/fault.

The echo option is not available for Oracle Mediator interfaces having request/reply/fault/callback WSDL files or for one-way WSDL files.

The echo option is only available for synchronous operations when the routing rule is sequential.

The priority property is applicable only to parallel routing rules.

You cannot route an Oracle Mediator response to a two-way service. If you want to route a response to a two-way service, you should use a one-way Oracle Mediator between the first Oracle Mediator and the two-way service. The response should first be forwarded to the one-way Oracle Mediator, which in turn should call the two-way service.

All the fault policies for a composite are loaded when the first error occurs. At runtime, Oracle Mediator checks whether there is any policy defined for the current error. If a fault policy is defined, then Oracle Mediator performs the action according to the configuration in the fault policies file. If there is no fault policy defined, then the default action of human intervention is performed.

Error groups in Oracle Mediator are:

TYPE_DATA, TYPE_METADATA, TYPE_FATAL, TYPE_TRANSIENT, TYPE_INTERNAL.

Schematron files are not compiled or validated by the Oracle SCA compiler.