Going to SOA and BPEL direction

[Quoted] [Quoted] I work for an IT department of a medium size company where a decision [Quoted] has been made to move to SOA paradigm. Whether or not the company truly needs to get into SOA world is a separate question but the reality is that SOA is an official strategy right now and BPEL (BPEL Process Manager from Oracle) is a tool that will invariably get us there. The pressure is to try to use BPEL every time two or more systems need to talk to each other so that we unify and standardize all integration interfaces. The problem is (at least in my opinion) that overwhelming majority of those "interfaces" fall under "data population" pattern. We have a system as a master of, let's say, employee data, and 10 other systems requiring the same data or a subset of it. So every nigh bunch of scheduled jobs pump data around. One of the drives is to have BPEL do pumping work as well. I know that BPEL Process Manager has all these connectors that can operate with databases and files and theoretically it can do the job. It just seems to me like a gigantic misuse of the tool and technology.

Any one can share similar experiences and how you dealt with them? May be some interesting approaches to the whole "data population" scenario. I was also wondering if any one ran into a decision diagram or decision matrix on whether or not BPEL is a right solution for a particular set of problems.

Thank you for your time. Received on Mon May 01 2006 - 20:08:12 CEST