Workflows getting inactive in Prod frequently

Wed Jun 23 20:26:17 EDT 2010

Wuggers,

 I'll second that emotion.

I used to think that SWEQADM was only for managing high volumes of events,
but in fact it is vital for catching and diagnosing event / linkage errors.

Consider this:

If you have no SWEQADM and an event error occurs:
 - the linkage is deactivated by default
- any subsequent events are lost forever (!!)
- if SWEL is turned off, you have no record of the event that caused the
problem
- a transport may be required to reactivate the linkage

Whereas if SWEQADM is turned on:
- the linkage is only marked as 'having an error'
- subsequent events are automatically saved in a queue
- you can examine the guilty event (and look into its container!)
- you can re-deliver all events once the issue is fixed
- the linkage can be turned back on with a mouseclick.

Definitely 'best practice'..

cheers
Paul

             "Dart, Jocelyn"                                               
             <jocelyn.dart at sap                                             
             .com>                                                      To 
             Sent by:                  "SAP Workflow Users' Group"         
             sap-wug-bounces at m         <sap-wug at mit.edu>                   
             it.edu                                                     cc 

                                                                   Subject 
             24/06/2010 09:38          RE: Workflows getting inactive in   
             AM                        Prod frequently                     

             Please respond to                                             
               "SAP Workflow                                               
               Users' Group"                                               
             <sap-wug at mit.edu>                                             

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 and
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 Queue
      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

******************************************************************************************************************************************************

Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments.  Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.

The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright.  If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments.  Queensland Treasury uses virus scanning software.  However, it is not liable for viruses present in this e-mail or in any attachment.  

******************************************************************************************************************************************************