I am using RAD 7.5 with Websphere 6.1 server in Windows 7 OS. I deployed my EAR application to websphere server through RAD. I was sucessful with all these. However, during debugging my application, I introduced few "System.out.println()" between my java code. Although I know its not a best practice to do this, I tried for now. But for my surprise, I did not find this message in RAD server console. To understand more on this behaviour, I placed the one more sys out in constructor of my java class and executed the application. Still did not find the message in console.
Can anyone please let me know if i missed out to check any settings in RAD to overcome this behaviour. While I tried simple java application with main method and few sys outs every thing is going good.
Eshwar Prasad wrote:Can anyone please let me know if i missed out to check any settings in RAD to overcome this behaviour.
Well, no, there aren't. It's Websphere you are asking about, not RAD. So you should have been looking for the Websphere settings.
So once you have the Websphere server started from RAD, start the administration application. (Right-click the server in RAD, that's one of the options.) Select Servers, then Application Servers, then your server (probably server1), then Logging and Tracing, then JVM Logs. Here you'll see some places where you configure the name of the files where System.out and System.err get diverted to. Click on the Runtime tab and you call see the full path to those files. You can even view those files from here.
Or... you could just change your servlet code to use the log() method. That's what it's for. It's even shorter to type than "System.out.println".
Joined: Mar 21, 2008
Thanks paul for your thoughts.
As suggested, I checked in admin server runtime tab and view the logs. The logs here display only the server log information like
So no sys outs are getting diverted.
I configured RAD and server in windows XP and tried..The sys outs I inserted are getting evaluated and displaying in the server console.
As said, using servlet log() function than using system.out.println is more easier...however, just surprised why sys outs are not coming in server console