Routing rules are mediation logic or execution logic that you define to achieve the requisite mediation. Mediator lets you route data between service consumers and service providers. As the data flows from service to service, it must be transformed. These two tasks, routing and transformation, are the core responsibilities of Mediator. You can use routing rules to specify how a message processed by a Mediator reaches its next destination. Routing rules specify where a Mediator sends the message, how it sends the message, and what changes should be made to the message structure before sending it to the target service.

A routing rule can be triggered either by a service operation or an event subscription. The service operation can be synchronous, asynchronous, or one-way. Routing rules can be of the following two types:

• Static Routing Rules

  Static rules do not change depending on the invocation context and are applied consistently.

• Dynamic Routing Rules

  Dynamic rules let you externalize the routing logic to an Oracle Rules Dictionary, which in turn enables dynamic modification of the routing logic.

For more information about creating routing rules, see How to Create Static Routing Rules and How to Create Dynamic Routing Rules. For information about standard message exchange patterns and how they are handled by Mediator, see Understanding Message Exchange Patterns of an Oracle Mediator.