Resolution:
Description:
============
Need to enable stdout logging.

Environment:
===========
ALL

Symptoms:
========
Not able to see stdout logging.

Cause:
=====

Resolution:
==========
When the BW process is started from TIBCO Admin, it runs as a background process, as a result the stdout and stderr can't be captured.
Admin doesn't redirect the bwengine engine output to any file. In order to redirect the output, you will need to modify the BW engine startup script.
If you go to the directory &ltTIBCO_home>\tra\domain\&ltdomain_name>\application\&ltapplication_name> you'll see your deployed BW engine here.
Ex:
test-Process_Archive.cmd
test-Process_Archive.tra

where test is the instance name.

Open the .cmd (or .sh in Unix) file, you'll see the following:
Ex:
"/Tibco-home/bw/BW-Version/bin/bwengine.exe" --run --propFile "/Tibco-home/tra/domain/&ltdomain_name>/application/&ltprojectName>/test-Process_Archive.tra"

Modify it as follows:
"/Tibco-home/bw/BW-Version/bin/bwengine.exe" --run --propFile "/Tibco-home/tra/domain/&ltdomain_name>/application/&ltprojectName>/test-Process_Archive.tra" > "/Tibco-home/tra/domain/&ltdomain_name>/application/&ltprojectName>/debug.out" 2>&1

What we have done here is to redirect the stdout and stderr to a file called debug.out. Save these changes and restart your BW engine from command line, you'll get the engine output.

For Designer Tester, stderr.log and stdout.log are located at the /Documents and Settings/user-home/.TIBCO/logs directory,. You can change the location of these two files in designer by clicking Edit --> Preferences and specify the new location into User Log Directory text box.

Is there any property to put into the .tra to enable stdout logging?