Harikrishna,
Can you be more specific about the ‘time’? Is this a static time for any message that gets into the queue, or different messages could have different time?
As you said, JMS Trigger would immediately pick and process the message. But if you don’t want that to happen, you can write a service that uses pub.jms:createConsumer & pub.jms:receive services which will PULL the message from the JMS queue/topic… In order to let this execute at specified interval, you can schedule this service to run at certain interval using IS schedulers.
If the time varies message to message, then in the publisher side during runtime, one time scheduled services need to be created which would do this job. But don’t think it is a good approach as if you have lot of messages coming in, there could be that many schedulers.
I am still trying to understand, what is the business use case behind it? Do you want to throttle and send to backend as you don’t want to let backend down due to heavy push from webMethods? Can you explain more on the business context?
Regards
Senthil
#webMethods#Adapters-and-E-Standards#Integration-Server-and-ESB