Pretty much all logging from WPF is done via log4j and configured via the log4j.properties in WEB-INF/config of your project and deployed WAR.
The Web Service Call builder uses the following two log4j categories to log info and debug messages.
bowstreet.system.debugTracing which is configured with a log4j DebugTracing appender to go to debugTracing.txt
bowstreet.system.webservice.serviceCall which is configured with a log4j ServiceCalls appender to go to serviceCalls.txt
In log4j.properties the debugTracing logger default is set to INFO so if anybody logs to it, it'll get sent to the configured appender for that category.
In log4j.properties the serviceCall logger default is set to WARN so only if you log a warning or error will it get logged, unless you change that to INFO.
These defaults are why if you just turn on logging via the builder input, you only see the logging in debugTracing.txt.
If you changed the WARN to INFO on the log4j.logger.bowstreet.system.webservice.serviceCall property, you would see messages there too, including some messages even if you don't turn on logging in the builder call (this is because some info messages are sent to that logger whether the builder inputs ask to or not, so that an admin can turn on some logging for that builder without even having to change the model). By logging to two appenders based on different criteria (one a builder input and one the logging level in the properties file) you have a way for a developer to turn on logging when necessary, and a way for a non-developer-admin to turn it on later if necessary.
The best way to see the logging information is to get the logs from the deployed WAR, since stdout is often cluttered with other unrelated info, but if for some reason you don't have access to the deployed WAR and can only receive copies of the server's stdout log, then the following info may help you configure logging to also log to stdout.
The appender config (log4j.appender.) in log4j.properties for each log4j category defines where the output for that category goes.
The debug tracing and service calls appenders are configured just to go to their respective properties files. Console is the appender that goes to stdout.
I believe you can change the debug tracing category to log to two appenders by adding an appender after a comma separator like this:
or you could just change it to log only to the console if you have problems with that.
Note, you may have to restart the application or the server to get it to pick up this change to the logging configuration.