Configuring Run-Time Logging Preferences
InstallAnywhere 2024 R2
InstallAnywhere includes support for generating run-time log files that you or your end users can use to troubleshoot issues with installers. Your installers can generate log files during installation, during uninstallation, when features are added, when the product is repaired, or when features are removed. By default, installers do not generate log files.
To enable logging and configure logging preferences:
1. | In the Advanced Designer, on the Project page, click General Settings. The General Settings view opens. |
2. | In the Log Settings area of the view, modify the values of the settings as needed. |
For information about all of the log-related settings that you can configure, see General Settings View.
Log File Locations
The default target system path for log files is:
$USER_INSTALL_DIR$$\$_$PRODUCT_NAME$_installation$\$Logs$/$
When you are specifying the path for a log file, you can use an absolute path. If the path is invalid at run time, the installer saves the log file in the default location.
If you edit one or more log file paths and then want to revert back to the default values for all of the enabled log files, click the Restore Default Paths button in the Log Settings setting.
The default log location is resolved by the InstallAnywhere variable $INSTALL_LOG_DESTINATION$.
The default file name for the install log is:
$PRODUCT_NAME$_<Mode>_<MM_DD_YYYY_HH_MM_SS>.log
For example:
• | My_Product_Install_08_13_2010_11_48_46.log |
• | My_Product_Add_08_13_2010_11_48_46.log |
Logging Installers that Include Merge Modules
For this merged logging functionality to work properly, it is mandatory that logging is enabled for both the parent and the merge module.The same applies for appending the stderr and stdout entries to the log.
To append the merge module logs to the parent log, you must select Plain text format in the Log Format setting, which is available in the General Properties view of the Project page. Adding the merge module log to the parent log is not available for the XML log format.
See Also