rss
SOATUBE
Oracle
Custom Search SOABYTE here

Wednesday, July 14, 2010

Tables in BPEL dehydration store




















The Dehydration Store database is used to store process status data, especially for asynchronous BPEL processes.

Key BPEL tables
Table
Contents
CUBE_INSTANCE
Stores the instance header information: domain, creation date, state (completed, running, stale, canceled), priority, title, and so on
CUBE_SCOPE
Stores the state of the instance, (variable values and so on)
AUDIT_TRAIL
Audit trail information for an instance. This information can be viewed from BPEL Console.
AUDIT_DETAILS
Large detailed audit information about a process instance
DLV_MESSAGE
Callback message metadata
DLV_MESSAGE_BIN
Payload of callback messages
INVOKE_MESSAGE
Invocation messages metadata
INVOKE_MESSAGE_BIN
Payload of invocation messages
DLV_SUBSCRIPTION
Delivery subscriptions for an instance
TASK
Tasks created for an instance (i.e. title, assignee, status, expiration)
WORK_ITEM
Stores activities created by an instance All BPEL activities in
a flow will have a work_item created for it.

1 comments:

Anonymous said...

Hello, I ´ve a question for u, do u know if the routing flow is stored in the WFROUTINGSLIP table?, and if it´s so, how can I change a route of an activity?.
Thanks.
Nik

Post a Comment

 
Blogger Profile