Workflows getting inactive in Prod frequently

Thu Jun 24 04:17:06 EDT 2010

Jocelyn,

I'm intimately familiar with SWEQADM, have no fear. My point was that  
the behaviour setting upon feedback is more appreciable using SWETYPV.

MGT

Sent from my iPhone

On 24 Jun 2010, at 09:04, "Dart, Jocelyn" <jocelyn.dart at sap.com> wrote:

> Hi MGT
>
> Really not trying to have an argument here, but just to clarify the  
> best practice position further for the sake of everyone else on the  
> list:
>
>
>
>  …. most of what you are saying is correct but …. BOTH SWETYPV  
> and SWEQADM look at event linkages … SWEQADM specifically looks at
>
> a)      Event linkages in error
>
> b)      Volume event linkages
>
> Whereas SWETYPV just contains the transported settings for all event  
> linkages.  You can see if the event linkage has been marked in error  
> but it’s not exactly obvious.
>
>
>
> In a runtime environment any errors in behaviour are therefore far  
> more evident in SWEQADM which focuses on those errors in the  
> Linkages in Error tab. It links directly to the event linkage  
> container and event log entries to help diagnose why the event  
> linkage failed.  Plus it has traffic light icons to highlight events  
> with new and continuing problems.
>
>
>
> I agree SWETYPV is useful background information and you might still  
> need to use SWETYPV to fix the problem of course… but SWEQADM should 
>  still be the starting point for event linkage behavioural problems.
>
>
>
> Especially as there are plenty of workflow administrators out there  
> who are not workflow developers… and SWETYPV wouldn’t help those  
> people at all.  Even for a workflow developer it’s far easier to fig 
> ure out what’s going wrong when you can look at a specific instance  
> of the event linkage and its container.
>
>
>
> Also SWEQADM  notifies the workflow administrator of any problems  
> via email (provided you entered a real user id with an email address  
> on the Basic Data tab)  … so the workflow administrator is able to c 
> atch any errors quicker.
>
>
>
> Perhaps you haven’t had a chance to play around in SWEQADM a lot so  
> far?  Developers often don’t particularly if they’ve been working  
> with workflow for some years… but as a workflow administrator  
> it’s an invaluable tool, and well worth familiarizing yourself with  
> it.
>
>
>
> Again not wanting an argument but, given that there are quite a few  
> workflow administrators on the WUG list, I think it’s important to c 
> larify the best practice here as using the correct tool goes directl 
> y to speed of problem resolution.
>
> Regards,
>
> Jocelyn
>
>
>
>
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On  
> Behalf Of Madgambler
> Sent: Thursday, 24 June 2010 5:06 PM
> To: SAP Workflow Users' Group
> Cc: SAP Workflow Users' Group
> Subject: Re: Workflows getting inactive in Prod frequently
>
>
>
> Hi back Jocelyn,
>
>
>
> You!re right to point out how essential SWEQADM is of course.
>
>
>
> In this case the cause for concern seems to be the behaviour of the  
> event linkages, which is more evident using SWETYPV.
>
>
>
> Any self-respecting WF Admin should be watching both or at least be  
> aware of them.
>
>
>
> Like you, though, my instinct here would be to investigate why  
> errors are causing feedback to trip the linkage rather than rush off  
> to adjust the setting, which is not what I'd advocate at all. Quite  
> the contrary. In this case the setting behaviour could well be  
> justified to prevent further damage.
>
>
>
> And of course SWEQADM would be invaluable to help diagnose and re- 
> issue 'stuck' events.
>
>
>
> MGT
>
> Sent from my iPhone
>
>
> On 24 Jun 2010, at 00:38, "Dart, Jocelyn" <jocelyn.dart at sap.com>  
> wrote:
>
> Hi MGT,
>
> Sorry but for the benefit of all I have to disagree with you there…
>
>
>
> As the whole point of SWEQADM is
>
> a)      to manage the event behaviour over and above the settings  
> transported via SWETYPV
>
> b)      to help you diagnose what is wrong if an event linkage has  
> failed  - especially an occasional problem such as this which might  
> be data related
>
>
>
> I’m still seeing too many sites not remembering to set up SWEQADM an 
> d suffering as a result.
>
>
>
> Please folks you really need to think of activating your workflow  
> environment as at least a 2 step process these days i.e. SWU3  
> ***AND*** SWEQADM.
>
>
>
> Regards,
>
> Jocelyn
>
>
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On  
> Behalf Of Madgambler
> Sent: Wednesday, 23 June 2010 8:05 PM
> To: SAP Workflow Users' Group
> Cc: SAP Workflow Users' Group
> Subject: Re: Workflows getting inactive in Prod frequently
>
>
>
> And SWETYPV is probably more useful for that...
>
>
>
> But, rather than changing the settings to prevent the linkage from  
> blowing it would be a better idea to find a recent instance of your  
> WF (no doubt you have an errored one lying around) and work out the  
> problem is.
>
>
>
> You might, for example, have an intermittent issue that is data  
> related, e.g. A binding error like ObjectA.ObjectB.Attribute where  
> ObjectB is null.
>
>
>
> MGT
>
>
> Sent from my iPhone
>
>
> On 23 Jun 2010, at 09:08, "Dart, Jocelyn" <jocelyn.dart at sap.com>  
> wrote:
>
> Just check the settings on the basic data tab.  Karl has already  
> indicated that the critical field is the Behavior on Error Feedback
>
>
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On  
> Behalf Of Patil, Priyank
> Sent: Wednesday, 23 June 2010 5:54 PM
> To: SAP Workflow Users' Group
> Subject: RE: Workflows getting inactive in Prod frequently
>
>
>
> Could you please explain me in detail regarding the settings in the  
> Queue Administration (SWEQADM) for workflows. As Iam not much aware  
> in that. Please let me know the settings that should be done.
>
>
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On  
> Behalf Of Dart, Jocelyn
> Sent: Wednesday, June 23, 2010 1:14 PM
> To: SAP Workflow Users' Group
> Subject: RE: Workflows getting inactive in Prod frequently
>
>
>
> Yes – that’s exactly the sort of behaviour that suggests you are  
> getting failed linkages that are being deactivated by the Event Queu 
> e Administration settings.
>
>
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On  
> Behalf Of Patil, Priyank
> Sent: Wednesday, 23 June 2010 5:18 PM
> To: SAP Workflow Users' Group
> Subject: RE: Workflows getting inactive in Prod frequently
>
>
>
> Once I login into Prod and activate, it starts to work perfectly.  
> But after some days it will get inactive automatically, even for  
> standard workflows. Again I need to login and activate it. Its like  
> an extra rework for us.
>
>
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On  
> Behalf Of Karl Nietz
> Sent: Wednesday, June 23, 2010 11:57 AM
> To: SAP Workflow Users' Group
> Subject: Workflows getting inactive in Prod frequently
>
>
>
>
> It is likely that you have the type linkage setting for your  
> triggering event set to 'Deactivation of Linkage' when an error  
> occurs (parameter 'Behaviour Upon Error Feedback').  You should  
> change this to something more benign.  Also check the report of  
> workflows in error (SWI2_DIAG) to see if you have workflows in  
> error, and review and clear them.
>
> Karl Nietz
> Senior Consultant
> CSC Australia
> Ph: 61 3 8695 1157
> Mob: 61 434 181303
>
> Please consider the environment before printing this e-mail. <br>  
> <br>CSC - This is a private message. If you are not the intended  
> recipient, please delete without copying and kindly advise us by e- 
> mail of the mistake in delivery. Note: Regardless of content, this e- 
> mail shall not operate to bind CSC to any order or other contract  
> unless pursuant to explicit written agreement or government  
> initiative expressly permitting the use of e-mail for such purpose • 
>  CSC Australia Pty Limited; Registered Office: 5B/26 Talavera Road,  
> Macquarie Park NSW 2113 Australia; Incorporated in Australia. ACN: 008 476 944
>
> From:
>
> "Patil, Priyank" <Priyank.Patil at keane.com>
>
> To:
>
> "SAP Workflow Users' Group" <sap-wug at mit.edu>
>
> Date:
>
> 23/06/2010 04:08 PM
>
> Subject:
>
> Workflows getting inactive in Prod frequently
>
>
>
>
>
>
>
> Hi,
>      We are facing serious a problem in production. The workflows  
> which are existing in Prod are automatically getting inactive. The  
> event link in SWDD are getting inactive frequently and the mail/ 
> workitems are not getting triggered. Since every time we need to  
> login to Prod and activate the event linkage in the workflow  
> builder. Is there any permanent solution for this??.We are into Ecc6.
> ______________________
> Thanks and Regards,
> Priyank Dev Patil.
>
>
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole  
> use of the intended recipient(s) and may contain information that is  
> confidential, legally privileged or otherwise exempt from disclosure  
> under applicable law. If you are not the intended recipient(s) or  
> have received this message in error, you are instructed to  
> immediately notify the sender by return email and required to delete  
> this message from your computer system. This communication does not  
> form any contractual obligation on behalf of the sender, the  
> sender's employer or such employer's parent company, affiliates or  
> subsidiaries._______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole  
> use of the intended recipient(s) and may contain information that is  
> confidential, legally privileged or otherwise exempt from disclosure  
> under applicable law. If you are not the intended recipient(s) or  
> have received this message in error, you are instructed to  
> immediately notify the sender by return email and required to delete  
> this message from your computer system. This communication does not  
> form any contractual obligation on behalf of the sender, the  
> sender's employer or such employer's parent company, affiliates or  
> subsidiaries.
>
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole  
> use of the intended recipient(s) and may contain information that is  
> confidential, legally privileged or otherwise exempt from disclosure  
> under applicable law. If you are not the intended recipient(s) or  
> have received this message in error, you are instructed to  
> immediately notify the sender by return email and required to delete  
> this message from your computer system. This communication does not  
> form any contractual obligation on behalf of the sender, the  
> sender's employer or such employer's parent company, affiliates or  
> subsidiaries.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100624/32c7981f/attachment.htm