Ramkumar Menon's Blog

My colleague provided me an extremely useful script that will replace a source string with a target string in all files in the current directory and its subdirectories.

find . -type f | xargs perl -pi~ -e 's/oldtext/newtext/g;'

Replace "oldtext" with the source string, and "newtext" with the target string.

During the replacement, all original files are backed up with a  "~" suffix.

There are different properties that you could actually update in your process descriptor. They are a) The Configuration properties b) The preference properties c) The partnerlink properties. These properties are illustrated below.

To update these properties dynamically within the BPEL Process, you can use a Java embedding within the process, as shown below.

Click here to download the Sample BPEL Process project.

Here is a simple BPEL Query that will get you the statistics of execution times of all BPEL Process instances over a period of time. The stats include the number of invocations, minimum, maximum and average time of execution.

SELECT process_id,count(*) as num_invocations, max(((EXTRACT(HOUR FROM MODIFY_DATE) - extract(hour from creation_date)) *3600 + (EXTRACT(MINUTE FROM MODIFY_DATE) - extract(MINUTE from creation_date)) *60 + (EXTRACT(SECOND FROM MODIFY_DATE) - extract(SECOND from creation_date))) *1000) as Max_Time , min(((EXTRACT(HOUR FROM MODIFY_DATE) - extract(hour from creation_date)) *3600 + (EXTRACT(MINUTE FROM MODIFY_DATE) - extract(MINUTE from creation_date)) *60 + (EXTRACT(SECOND FROM MODIFY_DATE) - extract(SECOND from creation_date))) *1000) as Min_Time , avg(((EXTRACT(HOUR FROM MODIFY_DATE) - extract(hour from creation_date)) *3600 + (EXTRACT(MINUTE FROM MODIFY_DATE) - extract(MINUTE from creation_date)) *60 + (EXTRACT(SECOND FROM MODIFY_DATE) - extract(SECOND from creation_date))) *1000) as Avg_Time FROM CUBE_INSTANCE WHERE state <> 9 and creation_date > '09-APR-08 09.00.00.000000000 AM' and creation_date < '09-APR-08 01.00.00.000000000 PM' group by process_id order by process_id asc 

In this query, you need to replace the sample date and time values with the values that you wish to use and report. Here is another query that gives the execution times of all BPEL instances over the given time period.

select bpel_process_name as process_id, instance_key as cikey, trunc(creation_date), eval_time as exec_time from bpel_process_instances where state <> 9 and creation_date > '11-APR-08 09.00.00.000000000 AM' and creation_date < '11-APR-08 05.00.00.420000000 PM' order by process_id asc, exec_time desc 

In this query, you need to replace the sample date and time values with the values that you wish to use and report. Note that the above query shall give you the execution times for a particular day. Take a look at the comments on this blog entry to see a modified example that uses the "day" as well to obtain stats that span across multiple days.

Here is one simple but useful thing that I've been too lazy to make use of, and had overlooked.

JDeveloper's component palette has a page named "Code Snippets". You could actually add frequently re-used code snippets and save them into the "code snippets" section.

Once you click on "Add component", you can give the snippet a name, for e.g. "Assign WS-Addressing Headers" and copy the snippet from your source code  to the given text area.

You can now re-use the code snippet by dragging and dropping the component from the code snippet palette onto the source view of any file that you open in JDeveloper.

Similarly, you can also add your own Pages to the Component palette, to capture Snippets for diferent cateogies of code [for instnace, BPEL,XML, XSD, XSLT etc].

Now you can specify the Page Name and specify the type  - "snippet", "java" etc.

Now you can add new code snippets to the new Palette Page that you created.

Wondering what to do if you wished to view the audit trail for stale instances?

Well, you could make use of the View Raw XML feature in the BPEL Console.