What Happens When You Create an Oracle Mediator with a Synchronous Interface Definition

18-20 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite Figure 18–18 Asynchronous Oracle Mediator in the Mediator Editor

18.4.6 Creating an Oracle Mediator for an Event Subscription

You can create an Oracle Mediator for subscribing to a business event that is generated when a situation of interest occurs. A business event consists of message data sent as the result of an occurrence in a business environment. For information about business events, see Chapter 38, Using Business Events and the Event Delivery Network.

18.4.6.1 How to Create an Oracle Mediator for an Event Subscription

The Subscribe to Events template in the Create Mediator dialog creates an Oracle Mediator that subscribes to events. To subscribe to events, the events must be defined in an Event Definition EDL file. To create an Oracle Mediator for an event subscription: 1. Create an Oracle Mediator as described in Section 18.3, Creating an Oracle Mediator . The Create Mediator dialog appears.

2. In the Name field, enter a name for the Oracle Mediator service component.

3. From the Template list, select Subscribe to Events, as shown in

Figure 18–19 . Getting Started with Oracle Mediator 18-21 Figure 18–19 Subscribe to Events Template Selection in Create Mediator Dialog

4. Click Add.

The Event Chooser dialog appears.

5. To the right of the Event Definition field, click Search.

The SOA Resource Browser dialog appears.

6. Select an event definition file .edl and click OK.

The Event field is populated with the events described in the.edl file that you selected. For more information about creating.edl files, see Chapter 38, Using Business Events and the Event Delivery Network.

7. Select one or more events in the Event field, as shown in

Figure 18–20 , and click OK . Figure 18–20 Event Chooser Dialog 8. Select a level of delivery consistency for the event. ■ one and only one : A global JTA transaction is used for event delivery. If the event call fails, the transaction is rolled back and the call is retried a configurable number of times. ■ guaranteed : A local transaction is used to guarantee delivery. There are no retries upon failure.