Review the following for information about working with Reflection Gateway log files:
Log files for the Reflection Gateway Administrator, the Reflection Hub, and the Reflection Transfer Server are created in the logs folders:
<install path>\GatewayAdministrator\logs
<install path>\Hub\logs
<install path>\TransferServer\logs
NOTE:By default, the server log files and debug log files (when debug logging is enabled) roll over daily and are deleted after three days. This helps ensure that disk space is not used up by large, accumulating log files. If you alter the configuration to keep these files for a longer period, you should monitor the files and/or move them to another server to ensure that sufficient disk space is always available.
The following log files are available for the Reflection Gateway Administrator, the Reflection Hub, and the Reflection Transfer Server:
server.log server.yyyymmdd.log |
This is the principal log file . It rolls over daily. The file called server.log captures log information for the current day. By default, rolled-over log files include the date in year-month-day format, and logs are deleted after three days. For additional troubleshooting information, you can add debug logging to the Gateway Administrator server.log file. |
debug.log |
Debug logging is not enabled by default. A debug.log file is created in the logs folder, but remains empty unless you enable debug logging. To enable debug logging, see Add Debug Logging to the Server Log File. |
The following additional log is available for the Gateway Administrator:
directory.log |
This log is not frequently used. It may be useful for troubleshooting LDAP server access.. |
For additional information troubleshooting Jobs, you can log debug information to the Gateway Administrator server.log file.
To enable debug logging in the server log file
As an administrator of the computer running Gateway Administrator, navigate to GatewayAdministrator\conf in the Reflection Gateway installation folder. The default location is:
C:\Program Files\Micro Focus\ReflectionGateway\GatewayAdministrator\conf
Open logback.xml file in a text editor.
Find the “Package level configuration” section:
<!-- Package level configurations -->
Add the following line to this section:
<logger name="com.attachmate.mft" level="DEBUG" />
Save thelogback.xml file.
NOTE:Edits you make to logback.xml need to be repeated each time you apply a hotfix or upgrade Reflection Gateway.
The Reflection Secure Shell Proxy supports two methods of logging: to the Windows Event Viewer and/or to a text log file. To configure logging, use the Reflection Secure Shell Proxy console (Micro Focus Reflection for Secure IT Gateway > Reflection Secure Shell Proxy).
Windows Event Viewer |
Logging to the Event Viewer is enabled by default. To view the Event Viewer log from the Reflection Secure Shell Proxy console, click the toolbar button, or go to View > Event Viewer. To modify the Event Viewer log level, go to Configuration > Logging > Event logging. |
Debug (text) logging |
Debug logging to text files is not enabled by default. To enable logging to a text file, set the log level, specify a log file directory, and configure rollover, go to Configuration > Logging > Debug logging. To view the log file from the Reflection Secure Shell Proxy console, click the toolbar button, or go to View > Latest Debug Log File. |