FreeKB - Command Line Workstation (CLW) - Debug logging
Introscope - Command Line Workstation (CLW) - Debug logging

By default, Command-Line Workstation will only append events to IntroscopeEnterpriseManager.log that identify when a user connects and disconnects, like this.

Command Line Work Station User "john.doe" connected successfully from host "Node=Workstation_1623, Address=localhost/127.0.0.1:52242, Type=socket"

Command Line Work Station User "" disconnected successfully from host ""

 

To write additional events to IntroscopeEnterpriseManager.log, update <em home>/config/IntroscopeEnterpriseManager.properties to have the following. There is no need to restart the Enterprise Manager as this change will take effect immediately.

log4j.additivity.Manager.CLW=true
log4j.logger.Manager.CLW=DEBUG

 

After the change has been made, IntroscopeEnterpriseManager.log will have additional events, like this.

mm/dd/yy hh:mm:ss [INFO] [Manager.SessionBean] Command Line Work Station User "john.doe" connected successfully from host "Node=Workstation_1623, Address=localhost/127.0.0.1:52242, Type=socket"

mm/dd/yy hh:mm:ss [DEBUG] [Manager.CLW] Execute command: help

 

For even more verbose logging, update <em home>/config/IntroscopeEnterpriseManager.properties to have the following. Restart the Enterprise Manager for this change to take effect.

log4j.logger.Manager=DEBUG

 

Then, issue a CLW command and look for Exceptions in IntroscopeEnterpriseManager.log, like this.

java.io.IOException: An existing connection was forcibly closed by the remote host

 



Add a Comment




We will never share your name or email with anyone. Enter your email if you would like to be notified when we respond to your comment.




Please enter 85202 in the box below so that we can be sure you are a human.




Comments