Skip to main content

IBM Domino: How to enable HTTP Request logging in Domino

http://www-01.ibm.com/support/docview.wss?uid=swg21099151

Technote (FAQ)


Question

How do you enable HTTP request logging when using a Lotus® Domino® Web server? You want a record of all requests sent by Web browsers to the Domino server to use for troubleshooting.

Answer

Below is a short guide to turning on request logging that provides the basic logging level. More verbose logging can be enabled by following the instructions in "Overview of HTTP Request Logs" (#7003598).
Important: HTTP request logging should be used only for troubleshooting specific issues, and usually at the direction of and with assistance from IBM Support. Do not use request logging for other purposes, such as administrative reasons. Because these log files grow in size over time, you should not leave this setting enabled for long periods or you will exhaust the available drive space.

To enable logging of HTTP requests for a Domino server for the current HTTP session only, enter the following command on the server console:
    "tell HTTP debug thread on"

When you restart the HTTP task, requests are no longer logged. You can also end request logging by entering the following command on the server console:
    "tell HTTP debug thread off" 
To enable request logging for more than one HTTP session, add the following line to the notes.ini file:
    HTTPEnableThreadDebug=1 (for the default level)

Domino 6 and later servers create htthr*.log files in the IBM_TECHNICAL_SUPPORT directory. (Domino R5 servers write REQ*.LOG files to the Domino program directory for Win32 platforms or to the Domino Data directory on UNIX platforms.)

Supporting Information:

Be aware that Request Log files grow in size. You should periodically move or delete the files, at least once a day. Refer to "How to Manage Size of HTTP Request Log Files" (#1098527) for more information. Also, if you restart the server or HTTP task, you should delete or move the existing log files because new ones will be created.

Related information

Historical Number

186246
Labels:

Popular posts from this blog

[Microsoft Outlook]: Set .pst and .ost files location with ForcePSTPath Registry Key

Set .pst and .ost files location with ForcePSTPath Registry Key The ForcePSTPath registry key is supported by Microsoft Outlook 2003 and later. In Microsoft Outlook 2003 and 2007, it applies to new profiles only. Microsoft Outlook 2013 and Outlook 2016 it applies to new accounts created in a profile. Microsoft Outlook 2013 saves .pst in   %userprofile%\Documents\Outlook Files folder by default. We can change that default setting by adding a new string registry key called ForcePSTPath and set the value to the folder that we want to save those files. Set Microsoft Outlook 2013 always save new .pst and .ost files to D:\Data\Mail folder OST file reached the maximum size The OST File Has Reached The Maximum Size
Read more

Powershell: Test-NetConnection

PS C:\Users\tuyen> get-help Test-NetConnection NAME     Test-NetConnection SYNTAX     Test-NetConnection [[-ComputerName] <string>] [-TraceRoute] [-Hops <int>] [-InformationLevel {Quiet |     Detailed}]  [<CommonParameters>]     Test-NetConnection [[-ComputerName] <string>] [-CommonTCPPort] {HTTP | RDP | SMB | WINRM}     [-InformationLevel {Quiet | Detailed}]  [<CommonParameters>]     Test-NetConnection [[-ComputerName] <string>] -Port <int> [-InformationLevel {Quiet | Detailed}]     [<CommonParameters>]     Test-NetConnection [[-ComputerName] <string>] -DiagnoseRouting [-ConstrainSourceAddress <string>]     [-ConstrainInterface <uint32>] [-InformationLevel {Quiet | Detailed}]  [<CommonParameters>] ALIASES     TNC REMARKS     Get-Help cannot find the Help files fo...
Read more

Powershell: Install IIS

Run Powershell as Administrator, then run the command below to install IIS. Install-WindowsFeature Web-WebServer Check after installing Get-WindowsFeature *Web*
Read more