Event queue related

akshay.bhagwat@wipro.com akshay.bhagwat at wipro.com
Sun Sep 27 21:25:34 EDT 2009


Hello Seth,
 
Thanks a lot for your inputs. I'll definitely check on these points.
May be based on your previous experience, can you suggest a tentative indication e.g. what might be the permissible no of events per minute beyond which we might need to consider the usage of event queue?
 
Couple of points which I know is: 
1. Workflow will be triggered thru' Interface and triggered Workflow will be doing processing such as sending outbound IDOCs , updating DB tables etc.
2. I'll try to find out the volume and interval relation as you had mentioned in your example.
 
Thanks again,
 
Regards,
Akshay Bhagwat

________________________________

From: sap-wug-bounces at mit.edu on behalf of Stevens, Seth
Sent: Fri 9/25/2009 7:45 PM
To: SAP Workflow Users' Group
Subject: RE: Event queue related


Akshay,
 
There isn't a simple yes/no answer to the question as the event queue is somewhat subjective and depends on your both your environment and your specific workflow.
 
60,000 events per year may or not not need the event queue based on how your system is scaled, how the events are delivered, and what the workflow is doing once it gets triggered.
 
60,000 events spread evenly over a year may or may not require the event queue; however, if they are all concentrated during certain times of the day it probably would.  For example, we process ~2000 vendor invoices per day and use the event queue for this workflow.  An interface loads the data so while we only get 2000 events per day, they are all raised within a 2 minute window which would kill they system if we let them all hit at once.
 
It also depends on what your workflow is doing.  If your workflow is calling code with a lot of overhead the event queue might be needed whereas if it is performing only a couple of simple tasks it may not.  
 
It is not a bad idea to get your basis team involved in the decision; however, in my opinion the event queue is never a bad idea if the business case can handle the delay.  The event queue allows you to adjust on the fly for performance issues, identify event errors, etc.
 
Not a clear cut answer but maybe a few things to help your decision.
 
Thanks,
Seth

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of akshay.bhagwat at wipro.com
Sent: Thursday, September 24, 2009 9:12 PM
To: sap-wug at mit.edu
Subject: Event queue related


Hello Friends,
 
I am a bit new for event queue usage- ie. not used event queue, - but am generally aware about the purpose of event queue.
 
Wanted to know , is there a guideline / pointers which can help in determining in which cases we should use event queue?
 
e.g. if for a particular scenario, no. of events are going to be approx 60,000 per year , will it require using event queue ?
 
Any suggestions are appriciated, thanks in advance.
 
Regards,
Akshay Bhagwat

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com 


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 8136 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20090928/8c9cdc6e/attachment.bin


More information about the SAP-WUG mailing list