Sunday, May 30, 2010

Oracle Mediator Features

Oracle Mediator
  • Oracle Mediator provides a lightweight framework to mediate between various components within a composite application.
  • Mediator converts data to facilitate communication between different interfaces exposed by different components, which are wired together to build a SOA composite application. For example, a Mediator can accept data contained in a text file from an application or service, transform it to a format appropriate for updating a database that serves as a customer repository, and then route and deliver the data to that database.

  • A Mediator component can evaluate routing rules, perform transformations, validate, and either invoke another service or raise another business event. You can use a Mediator component to handle returned responses, callbacks, faults, and timeouts.

Oracle Mediator Features

  1. Content-Based and Header-Based Routing

    Oracle Mediator provides support for setting rules based on message payload or message headers.
    You can select elements or attributes from the message payload or the message header and based on the values, you can specify an action. For example, Mediator receives a file from an application or service containing data about new customers. Based on the country mentioned in the customer’s address,you can route and deliver data to the database storing data for that particular country. Similarly, you can route a message based on the message header.

  2. Synchronous and Asynchronous Interactions

    Oracle Mediator provides support for synchronous as well as asynchronous request response interaction. In a synchronous interaction, the client requests for a service and then waits for a response to the request.
    In an asynchronous interaction, the client invokes the service but does not wait for the response. You can specify a timeout period for an asynchronous interaction, which can be used to perform some action, such as raise an event or start a process.

  3. Sequential and Parallel Routing of Messages

    A routing rule execution type can be either parallel or sequential. You can configure the execution type from Routing Rules panel.

  4. Java Callout

    Oracle Mediator provides support for Java callout. Java callouts enable the use of Java code, together with regular expressions.

  5. Event Handling

    An event is a message data sent as a result of occurrence of an activity in a business environment. Oracle Mediator provides support for subscribing to business events or raising business events. You can subscribe to a business event that is raised when a situation of interest occurs.
    For example, you can subscribe to an event that is raised when a new customer is created and then use this event to start a business process such as sending confirmation email.
    Similarly, you can raise business events when a situation of interest occurs.
    For example, raise a customer created event after completing the customer creation process.

  6. Dynamic Routing

    Dynamic Routing separates the control logic, which determines the path taken by the process, from the execution of the process. You can create a dynamic routing rule from the Mediator Editor.

  7. Mediator Echo Support

    Oracle Mediator supports echoing source messages back to the initial caller after any transforms, validations, assignments, or sequencing are performed.

  8. Error Handling

    Oracle Mediator supports both fault policy-based and manual error handling. A fault policy consists of conditions and actions. Conditions specify the action to be carried out for a particular error condition.

Oracle Service Bus 11g is Out.

Oracle has released the new version of Oracle Service Bus 11g (11.1.1.3.0) which can now be installed as a managed Server does separating it being tightly coupled with a single weblogic server.It has been certified on the new verion of Weblogic Server 10.3.3.With it the following new versions are avaliable.
- Repository Creation Utility 11gR1 (11.1.1.3.0)
- Service Registry 11gR1 (11.1.1.2.0)
- Enterprise Repository 11gR1 (11.1.1.2.0)
- SOA Suite 11gR1 (11.1.1.3.0)
- Oracle JDeveloper 11gR1 (11.1.1.3.0)

The new Oracle Service Bus 11g requires you to upgrade the Repository Creation Utility 11gR1 to 11.1.1.3.0.
Weblogic Server to 11.1.1.3.0
If SOA Suite is also there than the corresponding upgrade 11.1.1.3.0 is also avaliable which is avaliable as patch.