Event Queues - Comments on Pros & Cons?

[Rankin, Andrew AJ]

Alan & Stefan,
=20
Thankyou for your replies, I understand the functionality now and like =
it. I think that option 3 ' Do Not Change Linkage' makes the most sense =
for us.
Also it wasn't that I would want to capture the events that failed =
because of a start condition, rather the opposite I was wondering if =
they would be captured uneccessarily
Alan I also checked out your virtual classroom presentation which was =
an excellent way of providing information on new things - thanks!
=20
Regards,
Andrew
 
-----Original Message-----
From: Rickayzen, Alan [mailto:alan.rickayzen at sap.com]
Sent: Thursday, 20 September 2001 17:27
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Event Queues - Comments on Pros & Cons?
 
 
Hi Andrew,
I go into more detail about the recommendations about when to use the =
event queue and when not to in the "what's new to 6.10" virtual =
classroom presentation in SAPNet. I admit this is the last place that =
you'd expect information about older Releases but there you have it.
=20
Only the events that error out within the receiver are added to the =
error queue. E.g. problems starting the flow because the object does =
not yet exist or a table space filled up. The evaluation of the check =
functions including start conditions takes place beforehand so if the =
condition is false (or your check routine returns an exception) the =
event is not added to the queue.=20
=20
I'm not sure why you would want to restart events where they have been =
configured to evaporate without any consequences (via the conditions). =
For debugging purposes you can view such events in the event trace but =
there'd be little point in restarting them.
=20
Kind regards,
Alan Rickayzen=20
WebFlow Product Manager=20
SAP AG=20
 
Techdev=20
Neurottstra=DFe 15=20
69190 Walldorf=20
 
E-mail   alan.rickayzen at sap.com=20
 
http://service.sap.com/webflow <http://service.sap.com/webflow> =20
 
=20
=20
 -----Original Message-----
From: Rankin, Andrew AJ [mailto:Andrew.J.Rankin at BHPBilliton.com]
Sent: Donnerstag, September 20, 2001 4:45 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Event Queues - Comments on Pros & Cons?
 
 
 
Hi all,=20
 
>From what I have read, event queues are available to assist with =
performance where there is a likelihood of a large number of the same =
event being created in a very short space of time. To date, I haven't =
used them and haven't had problems, and I don't expect that to change. =
However the other thing that also interests me is that you can use the =
event queue to manage the case where event linkages end in an error, so =
that with the correct settings in the event linkage, if necessary these =
events can be resubmitted once the problem is fixed.
 
We had the situation a while ago where a small number of event linkage =
instances went into error because a table space was filled. Fortunately =
it was picked up early, and I only had to recreate a small number of =
these events by hand. If the number was large, I don't know how I would =
manage to kick off all the worklfows required without spending many =
tedious hours doing it manually. Perhaps this was a freak occurrence, =
but it makes me think that I should switch on the event queue for =
everything, to cover this risk in the future. So what is the downside =
to using the event queue, if any?
 
The other thing I'm wondering though is if I do switch it on, will it =
see event linkages that end with exception due to a start condition =
killing it (which we want to happen)? What else do I need to consider?
 
I thank you for any expert advice.=20
 
Andrew Rankin.=20
 
 
EOM=20
 
NOTICE - This message and any attached files may contain information =
that is confidential and/or subject of legal privilege intended only =
for use by the intended recipient. If you are not the intended =
recipient or the person responsible for delivering the message to the =
intended recipient, be advised that you have received this message in =
error and that any dissemination, copying or use of this message or =
attachment is strictly forbidden, as is the disclosure of the =
information therein.  If you have received this message in error please =
notify the sender immediately and delete the message.
 
 
EOM=20
 
NOTICE - This message and any attached files may contain information =
that is confidential and/or subject of legal privilege intended only =
for use by the intended recipient. If you are not the intended =
recipient or the person responsible for delivering the message to the =
intended recipient, be advised that you have received this message in =
error and that any dissemination, copying or use of this message or =
attachment is strictly forbidden, as is the disclosure of the =
information therein.  If you have received this message in error please =
notify the sender immediately and delete the message.
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20010927/6dc0e86d/attachment.htm