Friday, 23 November 2012

What is Dehydration store in soa 11g? What are the Tables for that?

BPEL dehydration store :
1.Oracle BPEL PM utilizes a database to store metadata and instance data during runtime.
  The process of updating process state in the database is called Dehydration.
  This data is stored in what is known as the Dehydration store, which is simply a database schema
  The Dehydration Store database is used to store process status data, especially for asynchronous      BPEL processes,   like BPEL’s metadata and instance data. This exists in x_SOAINFRA schema created by running RCU.
2. The Dehydration Store database is used to store process status data, especially for asynchronous BPEL processes.
3.A very important to remember if a BPEL process fails without reaching a
dehydration point then the instance will not show up on the BPEL console.
This instance never gets stored to the database.
Below are the main Dehydration tables for BPEL:
1.CUBE_INSTANCE
2.CUBE_SCOPE
3.AUDIT_TRAIL
4.AUDIT_DETAILS
5.DLV_MESSAGE
6.DLV_MESSAGE_BIN
7.INVOKE_MESSAGE
8.INVOKE_MESSAGE_BIN
9.DLV_SUBSCRIPTION
10.TASK
11.WORK_ITEM
Following are processes state codes and their meaning
State                          Code
Closed and Aborted 8
Closed and Cancelled 7
Closed and Completed 5
Closed and Faulted 6
Closed and (Pending or Cancel) 4
Closed and Stale 9
Initiated 0
Open and Faulted 3
Open and Running 1
Open and Suspended 2

No comments:

Post a Comment