Kaleidoscope 2011 - Overview of Eventing in Oracle SOA Suite 11g

Overview of Eventing in Oracle SOA Suite 11g Ronald van Luttikhuizen Vennster

Abstract
Services and events are highly complementary instead of competing paradigms in the ICT landscape. Oracle SOA Suite 11g emphasizes the importance of events by introducing the Event Delivery Network (or EDN) into the SCA infrastructure. This session provides an introduction of eventing in SOA Suite 11g. It will start by explaining the basics of events [also with respect to services], introduce several messaging patterns such as fire-and-forget and publish/subscribe, and explain some real life examples of using events in an SOA landscape. It will then dive into the underlying eventing infrastructure of Oracle WebLogic Server 11g and Oracle SOA Suite 11g that is based on JMS and AQ, and demo their use both inside and outside SCA composites using resource adapters, PL/SQL, and Java. The session will finish with the introduction of Oracle SOA Suite 11g’s EDN and the use of (composite) sensors in SCA composites.

Agenda
What is eventing and why use it?
Scenario
Patterns, implementation & demos
Summary and Best Practices

What are events?
Event is the occurrence of something relevant that usually requires action
Business: customer has moved, new employee
Technology: server down, response time above threshold
Producer, consumer
Contract, interface, and implementation

Why use events in SOA?
Case Organization modeling notifications in processes.
Mistake Dependencies between processes modeled directly in the processes itself.
Explanation Process flow sometimes is influenced by other processes. This was modeled into every process: this makes processes tightly coupled to each other and hard to change. It resulted in deadlocks.

Case: Explanation

Case: Best Practice

Why eventing?
Business
Businesses are about events
Better communication with business stakeholders
Technology
Decoupling
Different rates of processing speed
Different up-times
Easier release management

Agenda
Scenario
Patterns, implementation & demo
Summary and Best Practices

Scenario “Order2Cash” Order2Cash Webshop CRM Billing Dunning payment evt order evt billing evt dunning evt Chat order evt

Implementation/channel
AQ
JMS
EDN
Sensors
Others: Oracle CEP, 3rd party MOM, mail, file, Twitter, polling, custom-built, Java Action Listeners, and so on …

Messaging patterns
Queueing
Publish-subscribe
Complex-event processing
Fire-and-forget
Consumer Producer

Advanced Queuing (AQ)
Oracle Database
Payload
PL/SQL interface, AQ Resource Adapter
Single vs. multi-consumer
Transactionality
Filtering
Correlation

Creation of AQ schema and objects
CREATE USER jmsuser IDENTIFIED BY jmsuser;
GRANT CONNECT, RESOURCE, AQ_ADMINISTRATOR_ROLE, AQ_USER_ROLE to jmsuser;
GRANT EXECUTE ON DBMS_AQADM TO jmsuser;
GRANT EXECUTE ON DBMS_AQ TO jmsuser;
DBMS_AQADM.CREATE_QUEUE_TABLE(
Queue_table => ‘JMSUSER.NEW_CUST_ADDRESS_QT’,
Queue_payload_type => ‘SYS.XMLTYPE’,
Sort_list => ‘PRIORITY, ENQ_TIME’,
Multiple_consumers => ‘TRUE’);
DBMS_AQADM.CREATE_QUEUE(
Queue_name => 'JMSUSER.NEW_CUST_ADDRESS_QUEUE',
Queue_table => 'JMSUSER.NEW_CUST_ADDRESS_QT',
Max_retries => 5,
Retention_time => 10512000,
Retry_delay => 5);
DBMS_AQADM.START_QUEUE(Queue_name => 'JMSUSER.NEW_CUST_ADDRESS_QUEUE');

Demo AQ
New order request inserted in Webshop Database with trigger that publishes event
Start of SOA Composite Order2Cash instance through AQ Adapter
Stopping SOA Composite and insert new order
Webshop Database SOA Composite Order2Cash AQ queue New Order Chat

Messaging patterns
Queueing
Publish/subscribe
Fire-and-forget
Consumer Producer Consumer Consumer

Java Message Service (JMS)
Application server such as WebLogic Server
In-memory and file-based
Queues and topics
Java, MDB, JMS Resource Adapter
Transactionality
Filtering
Correlation
Hybrid: JMS over AQ

Demo JMS
SOA Composite Order2Cash publishes new billing event through JMS Topic
SOA Composite Billing generates invoice
Java CRM Application stores billing info with customer records
SOA Composite Order2Cash JMS topic SOA Composite BillingService Java CRM Application

Event Delivery Network (EDN)
SOA Suite 11g
Light-weight framework on top of AQ or JMS; EDN-DB and EDN-JMS
Technology-neutral and declarative
XML Payload (Event Definition Language)
Publish/subscribe
Filtering
ADF BC, PL/SQL API and Java API

Demo EDN
SOA Composite Order2Cash publishes dunning event through EDN; SOA Composite DunningService is subscribed and started
Publication of payment event through EM correlated to Order2Cash
SOA Composite Order2Cash SOA Composite DunningService EDN

Messaging patterns
Queueing
Publish/subscribe
Fire-and-forget
Producer Producer Producer Engine

Messaging patterns
Queueing
Publish/subscribe
Fire-and-forget
Producer ?

Eventing and synchronicity
Asynchronocity can also be achieved without eventing; eventing is often more decoupled

Eventing and synchronicity (II)
Eventing usually is asynchronous; but not necessarily
Product DB Request Q Response Q ProductWS

Sensors
Publish relevant process data in SOA Suite 11g
BAM
JMS, Database, Custom
Also: Composite Sensors

Demo sensors and composite sensors
Composite sensor to capture relevant data
Sensor to notify other systems that human task is started and completed

Agenda
Scenario
Patterns, implementation & demos
Summary and Best practices

Summary & best practices
SOA is not only about (synchronous) services; also events
Model events in BPM/SOA efforts, use events to notify running processes
Use events for decoupling
Not just queuing, also pub/sub
Expand service registry to include events
Not a single best technology

Overview of Eventing in Oracle SOA Suite 11g Please Fill Out Your Evaluations Ronald van Luttikhuizen Managing Partner @ Vennster, Oracle ACE Director for FMW & SOA Vennster, Netherland

http://blog.vennster.nl	393
http://www.slideshare.net	1
http://translate.googleusercontent.com	1

Kaleidoscope 2011 - Overview of Eventing in Oracle SOA Suite 11g

by Ronald van Luttikhuizen

Accessibility

Categories

Upload Details

Usage Rights

3 Embeds 395

Statistics