JMS queue will have primary key (order id) of the order message. once I dequeue message from JMS queue, I'll fire stored procedure and extract Order XML message by passing order id using SQLX function from Siebel database tables
Once I extract order XML message I'll again enqueue the XML message in weblogic server queue.
I ask you again.
Why it is so critital for you to submit event immediately after new record in inserted in JMS queue and then in wake up job process it.
When you create job that run every minute then delay is 1 minite maximaly.
How many records per minute is inserted to JMS ?
I want to post message to weblogic server as soon as possible. The stored procedure would be executed as soon as Order is submitted. There could be more ~20-25 order submitted within a minute.
Actually Sales rep who is submitting the order is waiting for successful completion of the order. Our middleware (AIA and weblogic) would route it to fulfillment and billing systems immediately and Siebel would gets the response immediately (with in few sec). So after order submission, rep will see the Order status within few seconds
If we wait for a min it's not good user experience.
I want to use parallel_instances = True so that we can spawn multiple actions at the same time for each JMS event.