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

NOTE

<em home>/product/enterprisemanager/plugins/com.wily.introscope.em_<version>.jar is the file that appends the DEBUG events to IntroscopeEnterpriseManager.log

After the change has been made, IntroscopeEnterpriseManager.log will have additional CLW events, like this. This isn’t really that helpful, as all that is included is the command that is invoked. This doesn’t help to determine if the command did or did not produce the expected output.

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

A case can be opened with Broadcom to get what is known as the Desktop Build com.wily.introscope.em_<version>.jar file, such as:

com.wily.introscope.em_10.5.2.jar_DE441405_DesktopBuild20200403

The current <em home>/product/enterprisemanager/plugins/com.wily.introscope.em_<version>.jar file can be backed up and removed. Then, rename the Desktop Build JAR file to have the same name as the JAR file that was backed up and removed, such as com.wily.introscope.em_10.5.2.jar. Upload the new JAR file to the <em home>/product/enterprisemanager/plugins directory, and then restart the Enterprise Manager. Now, additional CLW events will be appended to IntroscopeEnterpriseManager.log, like this. In this example, an invalid CLW command was issued.

mm/dd/yy hh:mm:ss [DEBUG] [Manager.CLW] XXXXX Execute command: some bogus command
mm/dd/yy hh:mm:ss [DEBUG] [Manager.CLW] XXXXX Invalid command: some bogus command
mm/dd/yy hh:mm:ss [DEBUG] [Manager.CLW] XXXXX Done with command: some bogus command

In this example, a valid CLW command was issued. This still isn’t really that helpful, as all the Desktop Build JAR adds is output letting you know if the CLW command was valid or invalid. This doesn’t help to determine if the command did or did not produce the expected output.

mm/dd/yy hh:mm:ss [DEBUG] [Manager.CLW] XXXXX Execute command: list historical agents
mm/dd/yy hh:mm:ss [DEBUG] [Manager.CLW] XXXXX Executed command: list historical agents
mm/dd/yy hh:mm:ss [DEBUG] [Manager.CLW] XXXXX Done with command: list historical agents

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