CData values showing up in servled_out.log

ijh

We have a default_config.xml file similar to the following:
With the following tags in it.
The CDATA ivalues are showing up in our servlet_out.log causing it to fill up
Does anyone know why it would be printed out to the servletd_out.log or am I missing something

Servletd_out.log example:
false
000001
true


----------------

[html]



- <Script id="scriptIndexDisplayNo">
-
- <br>if("$IW_CV(displayIndexOption)" == "false")<br>{<br>true;<br>}<br>else<br>{<br>false;<br>}<br><br>

Immediate Deployment
Global Variables
ModelProperties
</Script>



- <Script id="EndTaskTimeout">
-
- v="+000001"<br>

Flow252
Timeout Duration
Flow
</Script>
- <Script id="scriptIndexDisplayYes">
-
- <br>if("$IW_CV(displayIndexOption)" == "true")<br>{<br>true;<br>}<br>else<br>{<br>false;<br>}<br><br>

Immediate Deployment
Global Variables
ModelProperties
</Script>




[/html]

Adam Stoller

We have a default_config.xml file similar to the following: With the following tags in it. The CDATA ivalues are showing up in our servlet_out.log causing it to fill up Does anyone know why it would be printed out to the servletd_out.log or am I missing something Servletd_out.log example: false 000001 true ...

You should not be putting customizations into the default_config.xml - read the WFM manual and learn how to create custom instantiaton configuration files - which is where your custom code should go.

[update] I just thought about this a bit - and if that CDATA code is being put in by the system when you save your model - because you have SCRIPT variables - then yes, this is a known issue (at least I knew about it and reported it once:[indent]*** | May 20, 2010 @ 05:43:17 PDT | ***[indent]Is there anyway to eliminate the output from WFM Script variables from going
into servletd_out.log?

I have a script like:
------
if ("$IW_BRANCH".match(/iwconfig/)) true;
else false;
------

And every time the workflow is initiated I see either 'true' or 'false' (no quotes)
appear within the servletd_out.log.

With lots of script variables in lots of workflows and lots of workflows being
instantiated during the course of a day - this adds up to a lot of "noise" in
that log file.

While it's a nice way to verify scripts are working the way you want during
development / debugging - it's not something that I want to continue to
happen once the workflow development is completed and being used on a
production system.

Build #: 70033[/indent]...
*** | Jun 21, 2010 @ 13:19:46 PDT | With Engineering *** [indent]I have heard back from engineering. Would you like to implement the following solution?

"This is a known issue, unfortunatly there is no way to make this go way.
How ever if we identify which log4j file is being used, we can add an appender in log4j.xml to make this go to some other file or make everything except this go to some other file."[/indent]*** | Jun 21, 2010 @ 13:24:12 PDT | With Engineering *** [indent]I like the idea of sending it to another file - iwjoberrors.log is a possibility, though they aren't errors - perhaps
something like iwwfm.log ?

So - yes, please file the enhancement request and provide the ID (and actual description of the request) for it here (in
the case notes) - then, as is the mandate of AIWOV Support, you can close the case and I can look forward to it
eventually showing up in a future release.[/indent]...
*** | Jul 01, 2010 @ 07:41:07 PDT | With Engineering *** [indent]As it turns out there are plans for adding an option to remove these items in a version planned for Dec; I don't have anything concrete on that. I'm still chasing engineering regarding the log4j settings.[/indent]...
*** | Sep 17, 2010 @ 11:37:19 PDT | With Engineering *** I don't think that engineering is going to create any patches for this so I have created a defect for this (TS-12811) and will close this case. You can look for the defect reference in the release notes of TeamSite to see if this change has been implemented.[/color][/indent]