Database Reference
In-Depth Information
Monitoring
the
Event
Delivery
Network (EDN)
Oracle SOA Suite 11g has an out-of-the-box
Event Delivery Network (EDN)
that
allows you to publish and subscribe to business events. The EDN framework cre-
ates the messaging plumbing out of the box, that is, you will not have to create
any backend queues to support event delivery and consumption in the infrastruc-
ture. The default EDN is configured on the database, and this uses
Oracle Ad-
vanced Queuing (AQ)
behind the scenes. You can also have EDN based on
JMS that uses the JMS API. In the development and testing stage, access to the
EDN logs is of great help to identify and troubleshoot issues with your EDN im-
plementation. EDN logging level can be changed by following the next steps:
1.
Log in to Oracle Manager Fusion Middleware Control.
2.
Right-click on
soa-infra
, then navigate to
Logs
|
Log Configuration
.
3.
Expand the logger nodes to
oracle.integration.platform.blocks.event
or
enter
blocks.event
in the search box and click on the
Search
button to
filter the view.
4.
Change log level of
oracle.integration.platform.blocks.event.saq
to
TRACE: 32
. Configuring the logging at this level will ensure that the body of
the event message is available in the EDN trace.
5.
Check the
Persist log level state across component restarts
box and click
on the
Apply
button. This will let the log level survive managed server re-
starts.
In addition to configuring the EDN runtime java loggers as discussed earlier,
you can also enable the debug flag when using the default EDN implementation
based on the database. The value of the
ENABLED
column in the
EDN_LOG_ENABLED
table in the dehydration store can be set to
1
for making
the EDN logs available for review and configuration in a browser console at
ht-
tp://<host>:<soaport>/soa-infra/events/edn-db-log
.
The following screenshot shows a sample EDN log output wherein the screen
displays the event payload and status (
Enqueing Event, Enqueing Complete,
