Additional SOA Patterns –Supporting Composition Controllers - Applied SOA Patterns on the Oracle Platform - page 569

<wlevs:listener ref="cargoBookingChannel" />
<wlevs:instance-property name="keyProperties"
value="cargoID"/>
<wlevs:instance-property name="timeProperty"
value="bookingTime" />
</wlevs:adapter>
With many parameters to correlate, you can assign an entire class as an instance
property. The outbound adapter is configured in a similar way; for more details,
please see the Oracle EPN documentation. For brevity, we also skipped configur-
ation details for channels and listeners.
Compared to JMS's configuration routines, the DB intermediate store will require
at least one more in addition to the inbound event's source adapter; however, the
data source and store provider must be configured first:
<data-source>
<name>VoyBookEvt</name>
<connection-pool-params>
<initial-capacity>30</initial-capacity>
<max-capacity>80</max-capacity>
</connection-pool-params>
<driver-params>
<url>jdbc:derby:bookingevents;create=true</url>
<driver-name>org.apache.derby.jdbc.EmbeddedDriver</driver-name>
</driver-params>
</data-source>
<rdbms-event-store-provider>
<name>event-rdbms-provider</name>
<data-source-name> VoyBookEvt </data-source-name>
</rdbms-event-store-provider>
To record the events in DB, we need to specify what type of events we want to re-
cord for the adapter. Please note that in addition to the adapter, we can use the
processor stream and event beans for event recording: