Part 4 contains these chapters:
- Chapter 12 – Asynchronous Services with SOA composites and Services Bus
- Chapter 13 – Inbound Adapters – Polling Database, Consuming JMS and Receiving Emails
- Chapter 14 – Enterprise Scheduler
- Chapter 15 – Event Delivery Network
- Chapter 16 – Oracle Event Processor for Fast Data and Complex Events
Up to this point, all activities in SOA Suite were started and completed from a synchronous call on a single thread. In Part IV – “Asynchronous Services and Events” –- we discuss the asynchronous side of things. Asynchronous service interfaces that return a response through a call back at a later point in time are both consumed and published using both Service Bus and SOA Composite. Subsequently, the use of inbound technology adapters is discussed. These adapters cause services to be executed as a result of events detected in external components, such as database tables or advanced queues, JMS destinations, an email folder or a file system directory. A time event can be another trigger to execute a service – as the chapter on the Enterprise Scheduling Service (ESS) explains. The ultimate decoupling mechanism in SOA Suite is the Event Delivery Network (EDN) that is introduced next. With EDN, we can implement the extreme decoupling concepts of Event Driven Architecture for business events that are published and consumed from and by Mediator and BPEL inside the SOA Suite, and Java and PL/SQL components outside of it. How Service Bus can be made to interact with EDN is explained as well. The last chapter in this part discusses Oracle Event Processor (OEP), a component that included in the SOA Suite license, integrated with the Event Delivery Network and implement outside of the SOA Suite runtime, in its own container. With OEP, light weight applications can be created that monitor and analyze signals across many run time processes in real time. Using OEP we can automate much of the human responsibility for observation, interpretation and reaction.