Logging categories descriptions
| Logging Category | Value | Description |
|---|---|---|
| LogTrace | 0 | Disabled (default) |
| 1 | Enables the logging of sequence of events Examples: Before Resource Pending <map> |
|
| LogDebug | 0 | Disabled (default) |
| 1 | Enables the logging of information to diagnose Launcher behavior Examples: New audit file name <name> |
|
| LogInfo | 0 | Disabled (default) |
| 1 | Enables the logging of general information about the state
of the Launcher and
maps Examples: Map started |
|
| LogWarning | 0 | Disabled |
| 1 | Enables the logging of issues that are not severe, but might
be important to know. This is the default. Examples: Resource Manager table too small - using default |
|
| LogError | 0 | Disabled |
| 1 | Enables the logging of critical errors that won't cause the Launcher to stop.
This is the default. Examples: Map
failure <map> |
|
| LogFatal | 0 | Disabled |
| 1 | Enables the logging of a fatal error that caused the Launcher to stop.
This is the default. Examples: Corrupted MMC file during initialization <mmc_name> |
If you turn on logging ("Logging Option") from the Management Console or the dtx.ini file, the resulting files are created in the logs subdirectory of the WebSphere® Transformation Extender installation directory.