Recurring Process

[JayVal]

Hi Guys :

We have setup a Recurring Process in OTM to occur daily at 22:00 hrs. The process will execute a saved query and transmit the data to an .aspx URL defined by an External System in OTM.

But for some reason, we found that sometimes 2-3 transmissions are happening at this defined time (22:01, 22:02, 22:03) and the data being transmitted are not the same but are valid.

Any ideas why the multiple transmissions are taking place ?

We were wondering if the data out of the Saved query is being split. Any place to check this ?

Thanks in advance.

[james_foran]

Re: Recurring Process

Hi,

Need to have a look in the PROCESS_CONTROL_REQUEST table to see if you have this one duplicated. I have not seen OTM Split in this way. I have had to force it to in several instances for performance reasons, but this is just by modifying the SAVED_QUERY.

1. How many records are returned by the saved_query?

2. How long does the saved_query take to execute (run with same VPD)?

3. Just a quick thought, if the saved query is taking more than 1 minute to run, then perhaps it is getting picked up a second time before it finishes.

4. You should be able to view these tasks running in the GC3/glog.webserver.event.EventDiagServlet servlet. They should execute in the UTILITY Queue.

Hope this helps.

Please let me know how you go.

Regards,

[JayVal]

Re: Recurring Process

Thanks James.

I have answered one of your questions. See if they help. Also I digged into the Transmissions and came out with some statistics for each day. Some of the dates do not have data.

1. How many records are returned by the saved_query?
See Stats below

2. How long does the saved_query take to execute (run with same VPD)?
Will look into next time

3. Just a quick thought, if the saved query is taking more than 1 minute to run, then perhaps it is getting picked up a second time before it finishes.
Can you please explain ?

4. You should be able to view these tasks running in the GC3/glog.webserver.event.EventDiagServlet servlet. They should execute in the UTILITY Queue.
Will look into next time.

Thanks again.

Statistics I generated

Insert DateVoucher CountTransmission Count2/9/200812/13/200814/23/2008714/25/200814/29/200824/30/20085025/1/2008615/2/200815/6/200825/7/200855/8/2008915/9/20085335/10/200845/12/20081115/13/20082315/16/20085335/19/20085835/20/20083825/22/20085335/23/20081916/2/2008916/3/20086736/4/20081216/5/20082416/6/20081316/9/20083636/11/2008616/13/20083126/16/20081316/17/20083226/18/20081116/19/20081916/20/2008616/23/200861

[ianlo]

Re: Recurring Process

Hi JayVal,

It should be ok because apparently, there is a max limit size to the messages sent out under each transmission. My observation is approx 5 MB per transmission (maybe this is a web server setting)

My outbound transmissions sometimes can be as large as 6 - 7 MB. When this happens, OTM will always break it up into 2 separate transmissions, a 5 MB one and a 2 MB one.

If you need all your records to be sent only at that one time a day, then you may not have much choice. However, if you can split up the sending of the records to more than once a day then you can:

a. In your saved query, introduce a ROWCOUNT clause that will limit the number of records retrieved by your query
b. Create another SEND INTEGRATION recurring process to execute it at another time of the day.

You can tweak the ROWCOUNT clause to ensure that you do not hit the 5 MB data size.

This has worked pretty well for me. Hope it helps you as well!

Ian