How do you relate BPEL dehydration tables

Why I write this?

Well if you want to write some real clever applications on to top your BPEL dehydration database, you need to know some key BPEL tables inside out.

The dehydration database table need to be house kept to clear production data.
What helps you in these scenarios are:

• Understanding of what the key tables are.
• What the key fields are.
• How to relate these table.

What is the key table?

There are a few key tables that can be used across to relate together BPEL tables.

The first table that you should know is CUBE_INSTANCE

What is the key column in CUBE_INSTANCE table?

The most important column that you should know as a BPEL developer is cikey

What is the significance of cikey?

This is the instance ID that you see in your BPEL console.

This gets incremented in a sequence with creation of BPEL instances.

If you don't know what cikey is then here I go. Each BPEL instance is assigned a unique ID.

This ID is visible in the BPEL console. 

And guess what BPEL console does allow you to filter using instance ID.

This is one of the key columns that you should know to do a lot of stuff.

And this key cuts across a lot of tables in the dehydration tables.

The article will continue to grow....

Continuation to cover..

What are the other tables that have cikey

What are the other Key columns in CUBE_INSTANCE