Why would you use the Mediator component in a Service Component Architecture (SCA) application Instead of using Oracle Service Bus?

Why would you use the Mediator component in a Service Component Architecture (SCA)
application Instead of using Oracle Service Bus?

Why would you use the Mediator component in a Service Component Architecture (SCA)
application Instead of using Oracle Service Bus?

A.
Oracle Service Bus runs out side of a SCA application. Therefore, the Mediator is the only
choice for translation and transformation tasks in an SCA application.

B.
The Mediator is much faster than Oracle Service Bus.

C.
The Mediator supports transactions, but Oracle Service Bus does not.

D.
It is always better to use Oracle service Bus Instead of the Mediator.

Explanation:
Whereas Oracle Service Bus provides service virtualization and protocol
transformations for an Oracle SOA Suite application containing multiple composites, Oracle
Mediator is an intra-composite mediation component that is deployed within an application.
Note:
* Analogous to a load balancer routing HTTP traffic, the Oracle Mediator routes data from service
providers to external partners. In addition, it can subscribe to and publish business events.

Using Oracle Mediator, you create routing services and rules for them. A routing service is the key
component for moving a message across the enterprise service bus – from its entry point to its exit
point. The rules determine how a message instance processed by the routing service gets to its
next destination. Using the rules, Oracle Mediator can perform the following actions:
Route: Determines the service component (BPEL process, business rule, human task, and
mediator) to which to send the messages.
Validate: Provides support for validating the incoming message payload by using a schematron or
an XSD file.
Filter: If specified in the rules, applies a filter expression that specifies the contents (payload) of a
message be analyzed before any service is invoked.
Transformation: If specified in the rules, transforms document data from one XML schema to
another, thus enabling data interchange among applications using different schemas.



Leave a Reply 4

Your email address will not be published. Required fields are marked *