Conditionally Purge BPEL Instances on 10.1.3.x

Posted on Jan 28, 2008 in Offerings, Technical Tips | 1 comment

Marc Kelderman wrote a helpful article on this topic:

http://orasoa.blogspot.com/2007/03/delete-bpel-instances.html

One of the users there notes:

Note there is a patch to 10.1.3.3 to purge old data (6372741). Its a fairly dumb one that deletes everything older than a given date. Trying to do something more elaborate we have noticed that if you use the script in this article as a basis then rows in xml_document table are not removed.

We have written code to conditionally purge BPEL instances in a sophisticated manner, taking into account custom logic, scheduling, and performance for multiple customers in SOA/BPEL versions 10.1.2 and 10.1.3.x. The fact is that purging should be strategically planned to meet your unique use of Oracle BPEL.

Drop us a note if you would like to discuss your specific needs. We are very responsive and happy to jump onto an initial call for FREE.

Related Information:

1. BPEL

   Following are a few of...

2. BPEL Not Good For Rapid Changes

   I am excited about BPEL’s...

3. BPEL Worklist Application Error

   I wanted to note that...

4. BPMN 2.0 vs BPEL (Oracle BPM VS SOA Suite)

   This post covers Oracle Open...

5. Oracle BPA -> BPEL Manual Configuration Items

   Oracle BPA does a great...

6. Asynchronous vs Synchronous BPEL Processes

   Asynchronous and Synchronous BPEL processes,...

7. Salesforce.com Integration – Oracle Fusion Middleware SOA and BPEL

   Oracle Corporation has recently published...

8. JDeveloper Freezing – Optimize Performance for Large BPEL Flows

   I was running into issues...