I have currently implemented a solution where I am calling a web service on the application server from Oracle stored procedure using Oracle specific DBMS notification packages.
I read in few posts the very need for calling a middle tier component like web service from the database could be a design flaw and need to revisit the design.
The reason I had to resort to this approach is for the following reasons
The web service functionality is only required to be kicked-off after our data loading Oracle stored procedures completes. Once these complete we fire the notification as mentioned above and trigger the web service. In short the Oracle stored procedures task is the pre-process and prepares the data which will subsequently be used by our web service functionality.
What is the alternative to handle this. Can scheduler systems help? The ones I read about like Quartz were good batch handling tools but did not seem to provide auto-scheduling features. Like in our case the stored procedures run once a week and somehow immediately on completion of stored procedures run we want to check the stored procedure status table and kick-off the web service run.
Let me know your thoughts.
Onion rings are vegetable donuts. Taste this tiny ad: