1. Developing SOA Applications with Oracle SOA Suite
  2. Sharing Functionality Across Service Components
  3. Using Business Events and the Event Delivery Network
  4. Subscribing to or Publishing a Business Event from an Oracle Mediator Service Component
  5. What You May Need to Know About Subscribing to a Business Event

What You May Need to Know About Subscribing to a Business Event

Only subscribers in default revisions of the SOA composite applications can receive business events. For example, note the following behavior.

To subscribe to a business event:

  1. Create a composite application with an initial Oracle Mediator service component named M1 that publishes an event and a second Oracle Mediator service component named M2 that subscribes to the event. The output is written to a directory.
  2. Deploy the composite application as revision 1.
  3. Modify the composite application by adding a third Oracle Mediator service component named M3 that subscribes to the same event and writes the output to a different directory.
  4. Deploy the composite application as revision 2 (the default).
  5. Invoke revision 2 of the composite application.

    Oracle Mediator M2 writes the output to one file in the directory. As expected, Oracle Mediator M3 picks up the event and writes the output successfully to another directory. However, Oracle Mediator M2 (from revision 1) is not picking up the published event from revision 2 of the composite application.