Contents of the logs
BMC Helix Digital Workplace provides logging capabilities to help resolve application issues. For most log files, the format of the content is as follows:
TIME| THREAD| LEVEL| COMPONENT| MESSAGE
BMC Helix Digital Workplace log files
The following log files are available:
| Log file | Location | Description |
|---|---|---|
| ITSMServerConfigureXMLTask.log | installDirectory/DWP/Logs/ | Installer log. Contains information about the import of data to the BMC Remedy ITSM server. |
digital_workplace_patch_install_log.txt |
| Patch installer logs. Check this file for exceptions if the patch installation is:
If any DEF import failure exceptions are logged, check the RIK log files. |
digital_workplace_install_log.txt |
| Installer logs. Check this file for exceptions if the installation is:
If any DEF import failure exceptions are logged, check the RIK log files. |
| RikStatement.html | C:\Program Files\BMC Software\Digital_Workplace_Patch\DWPPatch\Logs (ITSM side) | Remedy component installer logs. Check this file for details if any DEF import failure exceptions are logged in the BMC Helix Digital Workplace installer or patch installer logs. The log is displayed as an HTML report. |
RikStatement.log | C:\Program Files\BMC Software\Digital_Workplace_Patch\DWPPatch\Logs (ITSM side) | Remedy component installer logs. Check this file for details if any DEF import failure exceptions are logged in the BMC Helix Digital Workplace installer or patch installer logs. |
| RikStatement_apps.log | C:\Program Files\BMC Software\Digital_Workplace_Patch\DWPPatch\Logs (ITSM side) | Remedy component installer logs. Check this file for a summary report of the total number of DEF imports that passed, failed, or skipped during the BMC Helix Digital Workplace installation. The details are provided in RikStatement.log and RikStatement.html. |
| SRMServerInitTask.log | ||
| dwp.timeStamp.part.n.log | installDirectory/DWP/Logs/yyyy-mm-weekn | Primary Tomcat log file. Events for BMC Helix Digital Workplace are logged in this file. To download a sample file with all log levels set to debug, see
MyIT Tomcat Logging
This file is saved at regular intervals defined within the logback-dwp.xml file. The dwp.timeStamp.part.n.log file contains data related to backend calls and their duration. When the maximum defined log file size is reached, a new log file is created, and the n counter in the log file name is incremented to n+1. |
| dwp.log | installDirectory/ DWP/Logs/ | This is the current version of dwp.<timeStamp>.part.n.log. The time stamp and part are added when the file is saved, and a new dwp.log is started. |
| dwp-sysinfo.log | Provider startup log. Check this log file for provider failures, such as integration issues. | |
| dwp-userpool.log | Issues encountered while communicating with Remedy. |
BMC Helix Digital Workplace Catalog log files
If you installed BMC Helix Digital Workplace Catalog into a custom folder, then replace all occurrences of the /opt/bmc/digitalworkplace path name with your installation folder.
| Log file name | Information recorded in log file | Log file name and location | Notes |
|---|---|---|---|
Bundle log | The bundle log captures messages related to the application execution, so that you can troubleshoot errors with end user requests, process workflows, and other system errors. | /opt/bmc/digitalworkplace/db/bundle.log | Enabled by default. For information, see Troubleshooting common BMC Digital Workplace Catalog issues by using log files. |
Trace log | The trace log captures messages related to server communication, SSL certificate issues, and API transactions. | /opt/bmc/digitalworkplace/sb/rxscripts/trace.log | Disabled by default. After you install trace logging, the logging feature persists after application and server restarts. For information about enabling this log file, see Configuring logs. |
Installation logs | Two log files record the actions while the application is installing. | /tmp/dwp_install_log.txt /tmp/dwpsystem_install_log.txt | Enabled by default. For information, see Troubleshooting common BMC Digital Workplace Catalog issues by using log files. |
Tenant creation (postinstallation) log | The tenant creation log file records the activity when running the postinstallation script to create the tenant. The restart after tenant creation log records the activity during the system startup process after you run the postinstallation scripts to create the tenant. | /opt/bmc/digitalworkplace/db/post-install.log /opt/bmc/digitalworkplace/post_install_restart.txt | Enabled by default. For information, see Troubleshooting common BMC Digital Workplace Catalog issues by using log files. |
| System startup logs | A series of log files record messages during the system startup process. | /opt/bmc/digitalworkplace/db/sb-start.log /opt/bmc/digitalworkplace/sb/log/dwpcontrollerStart.log /opt/bmc/digitalworkplace/Logs/arStart.log /opt/bmc/digitalworkplace/Logs/arRestart.log | Enabled by default. |
Comments
Log in or register to comment.