Comments on: Oracle BPEL Process Manager: Most efficient way to manage dynamic process level (cross instance) data

By: Gita Kaiserman

Gita Kaiserman — Mon, 29 Aug 2011 14:47:19 +0000

I like this post, enjoyed this one appreciate it for posting .

By: Lucas Jellema

Lucas Jellema — Thu, 24 Jan 2008 07:01:46 +0000

Interesting though this story is, it would not be complete without mentioning the Oracle BPEL Deployment Descriptor Properties (Preferences and Configuration Properties). See BPEL Developer's Guide - Appendix C for details on this very useful feature.

By: Lucas Jellema

Lucas Jellema — Sat, 12 Jan 2008 19:32:57 +0000

Umesh
Thanks for your comment. I suppose that in a multi-JVM environment I will not get away with the singleton without having it regularly check in either a file or database table whether or not a refresh is required – by comparing its own latest-refresh-timestamp with the latest-update-timestamp in either file or database table. Depending on how quickly confguration changes should take effect, the singleton has to poll regularly. Altenatively, we could perhaps have each instance (node) initiate the singleton from its own BPEL process instance – and continue to have that process instance around for pushing new configuration settings to the singleton. I do not know at this point however if and how I can create a BPEL Process instance at a specific node in the cluster or instance in OC4J.
Lucas

By: Umesh

Umesh — Sat, 12 Jan 2008 10:20:49 +0000

Quite a nifty technique. Lookups are always important and going to DB or reading from a file etc will always be costly affair. Just out of curiosity, how will this work when you have multiple JVMs for your OC4J or have a clustered installation of SOA suite?