Using Web Administration

Edit online

You can use the instruction provided here to modify the server log settings using the Web Administration Tool.

About this task

  1. Expand Server administration in the navigation area, click Logs, click Modify log settings.
  2. Click Server log.
  3. Enter the path and file name for the error log. Ensure that the path is valid. If the file does not exist, it is created. The error log can also be directed to something other than a file, for example, a line printer. See Default log paths for default log paths.
    Note: If you specify a file that is not an acceptable file name (for example, invalid syntax or if the server does not have the rights to create and/or modify the file), the attempt fails with the following error: LDAP Server is unwilling to perform the operation.
  4. Under Log size threshold (MB), select the first radio button and enter the maximum log size in Megabytes. If you do not want to limit log size, select the Unlimited radio button instead.
  5. Under Maximum log archives, select one of the following options.
    • If you want to specify a maximum number of archived logs, select the radio button with an edit window next to it. Enter the maximum number of archives you want to save. One archived log is an earlier log that reached its size threshold.
    • If you do not want to archive logs, select No archives.
    • If you do not want to limit the number of archived logs, select Unlimited.
  6. Under Log archive path, do one of the following tasks.
    • If you want to specify the path where archives are kept, select the radio button with an edit window next to it and enter the required path.
    • If you want to keep the archives in the directory where the log file is located, select the Same directory as log file radio button.
  7. Under Log Schedule, do the following tasks.
    • Specify the frequency between two cycles of Event by selecting an item from the Select frequency check box.
    • Specify the start date and start time for Event in the Starting on fields. You can also click the calendar icon to specify the start date. The start time must be in the following format: 12:30:00 PM.
  8. Select either Low, Medium, or High for the level of error logging.
    • Low logs the least amount of error information, for example,2023-06-06T16:19:48.243277 GLPSRV009I 11.0.1.<fixlevel> server started.
    • Medium logs a medium amount of error information, for example,
      2023-06-11T14:39:47.323414 GLPCOM024I The extended Operation plug-in is successfully loaded from libloga.dll.
2023-06-11T14:39:47.339285 GLPCOM003I Non-SSL port initialized to 389.
2023-06-06T16:19:48.243277 GLPSRV009I 11.0.1.<fixlevel> server started.
    • High logs the most amount of error information, for example
      2023-06-11T14:39:47.319209 GLPSRV047W Anonymous binds will be allowed.
2023-06-11T14:39:47.323414 GLPCOM024I The extended Operation plug-in is successfully loaded from libloga.dll.
2023-06-11T14:39:47.821234 GLPSRV003I Configuration file successfully read.
O2023-06-11T14:39:47.339285 GLPCOM003I Non-SSL port initialized to 389.
2023-06-06T16:19:48.243277 GLPSRV009I 11.0.1.<fixlevel> server started.
  9. Click Apply to apply your changes and continue working with logs, or click OK to save your changes and to return to the IBM® Verify Directory Web Administration Introduction panel. Click Cancel to return to the IBM Security Directory Server Web Administration Introduction panel without saving any changes.