What is WID history logging?
History logging is primarily meant to aid debugging during development and also help IBM support people when working on issues. It's a capability that is configurable in WID (turned on by default) whose intent is to gather, at a coarse level, just enough information so that we can have a good idea of the steps that a user took that led to an error. Rotating logs are written in the user's workspace .metadata directory and are named widHistory_n.log. These logs are viewable in the Server Logs view within WID by navigating to the workspace and loading the logfiles from the workspace .metadata directory. To view the configurable properties, open WID | Preferences | Business Integration | Logging and Tracing, as shown in the following screenshot:
There are various aspects that get logged in the history logs and are viewable through the WID Server Logs view. As shown in the following screenshot, when a history log is loaded, the aspects name appears in the content area, and these names can be filtered using the content filter of the Server Logs view. These include:
GeneralUI—shows WID start/end, view, or if editor is opened/activated/closed.
BUILD—shows build-related activities (incremental and clean).
REFACTOR—shows refactoring start/stop and what is being refactored.
SERVER—shows server initialization, state change for server and module on a server start, details about port, connection information, modules deployed to server, and so on.
PUBLISH—shows publish start/stop, publish type, and type of publish (added, changed, removed), and publish time.
INTEGRATED TEST CLIENT—shows server starts, modules added and published to the server, waits for modules to start, and how a server start or publish originated.
MIGRATE—shows files migrated to WID.
FROM_ECLIPSE_ERROR_LOG—shows errors that appear in the Eclipse error log, that is, the Error Log view. These errors indicate the workspace state when the error occurred.
WID Tracing
Tracing in WID is switched off by default. Rotating logs are written in the user's workspace .metadata directory and are named widTrace_n.log. These files are viewable through the WID Server Logs view. You can turn it on and must specify components that should be traced. You must specify the Trace string and example including:
com.ibm.*=finest would trace all.com.ibm.wbit.*=finest: com.ibm.wbit.ui=info
Tracing levels can be one of fine, finer, finest, info, warning, or error. Any changes made are immediate—no need to restart WID.
