probably you can have the entire business logic transferred to the Application Layer i.e EJB's. Create a Message Driven Bean which will invoke the application when ever it receives a message from a client and this client has to be a Java Timer Application or Windows Service or Unix Cron Scripts or any such scheduled client which will just pass on few Standard Messages to MDB such as start, stop etc... and which in turn to these standard message starts the batch application.
As far as the speed of these programs is concerned, it will obviously be high on Database itself, but mind it if the database size is high then this computational overheads which you have there in form of Procedures, when transferred to Application Layer will significantly improve the database performance. One more important criteria in making such decisions would be the No. of Clients that application has to handle. Because if your application has over 100 concurrent clients (roughly) then you can without any doubt find higher performance from having a EJB layer in place instead of procedures and functions written in PL/SQL. *********************** enJoy Life with Technology *********************** pirbhu ;-) "Convince, Confuse, Corrupt" Prabhakar Goel JIL Information Technology Ltd. ph: 91 (120) 4777881 ext # 2392,2387. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
