<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Helvetica Neue";}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
mso-fareast-language:EN-GB;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Rick,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Speaking from experience I have seen this take systems down on quite a few occasions so it can go horribly wrong. If you have someone who can monitor it and
delete trace data when needed then I guess it is workable. Also use the trace restrictions when switching it on so only monitor a select number of events.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Also with note
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">1905199 a syslog entry (SM21) is written when an event linkage is deactivated so this can be used to check when the event linkage deactivation occurs. Then use the event
trace to get specific information about the deactivation itself.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Eddie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]
<b>On Behalf Of </b>Rick Bakker<br>
<b>Sent:</b> 05 March 2014 22:17<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Re: Workflow Event Trace Leave On or Turn Off<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi David,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I like to leave the event trace turned on. I have found this to be the case at most sites. Also, most workflow people I have worked with agree with this approach. The overhead is minuscule compared to the information it adds.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Rick Bakker<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Mar 6, 2014 at 3:29 AM, Edward Diehl <<a href="mailto:edwarddiehl@hotmail.com" target="_blank">edwarddiehl@hotmail.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:16.0pt;font-family:"Garamond","serif";color:black">It's not whether or not the trace is running, it's how often you delete "old" entries and reorg it. Having said that, we have stopped
using it to test for duplicate events and now check for duplicate workflows in a check function.<br>
</span><br>
<br>
<strong><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Ed Diehl</span></strong><b><span style="font-size:16.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
</span></b><em><span style="font-family:"Tahoma","sans-serif"">"Success consists of going from failure to failure without loss of enthusiasm."</span></em><span style="font-family:"Tahoma","sans-serif"">
<br>
<br>
<br>
</span><o:p></o:p></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal">To: <a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a><br>
From: <a href="mailto:davidcooper06@icloud.com" target="_blank">davidcooper06@icloud.com</a><br>
Subject: Workflow Event Trace Leave On or Turn Off<br>
Date: Wed, 5 Mar 2014 06:55:50 +0000<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi All,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The following is more a discussion item!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I have read in various texts and heard from several workflow administrators that it is recommended to turn the workflow trace off in production.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Reasons:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">1) The trace adds an overhead to the application and database servers, and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">2) The trace fills up the event table(s) with data that is not needed over time.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My argument for leaving the trace running, is more for diagnostic reasons when problems occur in production. It becomes another source for tracking down what happened. Yes the overhead is a given, but I feel this is justified to capture
the diagnostic information. As for the database table being filled, implement a deletion strategy which purges the data from the table after a period of say 3 ,6, 9, or 12 months.<o:p></o:p></p>
</div>
<div>
<pre style="white-space:pre-wrap;word-wrap:break-word"><span style="font-size:11.5pt;font-family:"Helvetica Neue"">Kind Regards<o:p></o:p></span></pre>
<pre><span style="font-size:11.5pt;font-family:"Helvetica Neue"">David Cooper<o:p></o:p></span></pre>
<pre><span style="font-size:11.5pt;font-family:"Helvetica Neue"">Linked-In: <a href="http://www.linkedin.com/pub/david-cooper/47/616/36a" target="_blank">http://www.linkedin.com/pub/david-cooper/47/616/36a</a><o:p></o:p></span></pre>
<pre><span style="font-size:11.5pt;font-family:"Helvetica Neue""><o:p> </o:p></span></pre>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________ SAP-WUG mailing list
<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>