Asset Suite / PassPortGeek

The Ventyx developers put in a lot of System.out.println's in the Java code used by BuyDemand. It can be non intuitive finding the output and the messages are critical to understanding and debugging the Java services because WebMethods cannot "debug" them, i.e., step through the code.


For WebMethods running on Windows the following is suggested. Start WebMethods as a Windows Started Task or from a Command Prompt window. It does not appear to be possible to start WebMethods as a Windows Service and see standard output (console output).


Log onto the Windows box running WebMethods with a user ID with administration authority on the box.

Open a Command Prompt window.

Go to the directory containing the ..\IntegrationServer\bin\server.bat file.
Example: cd W:\webMethods\region\IntegrationServer\bin\

Start WebMethods.
Bad example: W:\webMethods\region\IntegrationServer\bin\server.bat -log w:\webmethods\region\console.log -debug 5

The bad example seems to indicate that standard output will be written to file console.log. It is not and scrolls on the Command Prompt window. The "-debug 5" seems to be necessary to get the standard output.

Reference:

http://www.jroller.com/nathan/entry/crash_course_on_webmethods_integration