Home
Administering
This documentation provides information about the administration tools for HCL Domino.
Administering with Domino Administrator
This documentation provides information about the administration tools for managing and monitoring servers and databases.
Managing servers
Manage Domino® servers by performing any of these tasks.
The Domino® Web server log (DOMLOG.NSF)
You can log your server activity and Web server requests to the Domino® Web server log (DOMLOG.NSF) database. This option may be preferable if you want to create views and view data in different ways.
Domino® Web server logging to text files
When setting up Domino® Web server logging to text files, you must determine the Access file format. The content of the Access log varies depending on which log file format you choose: Extended Common or Common. The most commonly used Access log format is Extended Common, which logs all Web server information into a single text file.

Administering
This documentation provides information about the administration tools for HCL Domino.
- Administering with AdminCentral
  The AdminCentral application (admincentral.nsf) is automatically created by adminP on the Domino administration server. You can open AdminCentral directly from your Notes Standard or Nomad web client, without the need to start Domino Administrator. This application provides a simplified and easy-to-use way of managing fully functional Notes users and groups in a Domino deployment.
- Administering with Domino Administrator
  This documentation provides information about the administration tools for managing and monitoring servers and databases.
  - Administration tools
    Topics in this section describe the tools you can use to administer a Domino® server.
  - Managing users
    The Administration Process helps you manage users by automating many of the associated administrative tasks. For example, if you rename a user, the Administration Process automates changing the name throughout databases in the Notes® domain by generating and carrying out a series of requests, which are posted in the Administration Requests database.
  - Monitoring servers
    This section describes how to use the tools and features that help you monitor a Domino® system.
  - Managing servers
    Manage Domino® servers by performing any of these tasks.
    - Changing the server administrator
      If the name of the former administrator is explicitly listed in the access control list (ACL) for the Domino® Directory, delete the name of the former administrator from the ACL. Add the name of the new administrator and assign the administrator Manager access.
    - Setting and managing passwords for the server console
      Set server console passwords to protect against unauthorized use of the server console.
    - Decommissioning a Domain Search server
      If you want the server that creates full-text indexes of the Domino® domain to resume duty as a regular Domino server, remove it from the appropriate group in the Domino Directory, edit its Server document, and then delete some files from its directory structure.
    - Decommissioning a server
      You use the Decommission Server Analysis tool when you are consolidating existing servers and/or permanently removing a server from service. Whether you are combining two servers into one server or renaming a server, the result is the same -- the old server name is replaced with the new server name.
    - Deleting a server name
      You can use the Administration Process to delete references to a server from the Domino® Directory, and from database ACLs and Extended ACLs. The Administration Process automatically deletes mail-in database documents and cross-certificate documents as necessary during the Delete Server process.
    - Dropping user sessions on a server
      Dropping user sessions from a server may be useful when you need to make a database or server temporarily unavailable to correct a problem; users can reconnect after you are ready. You can drop one user session or all user sessions for the current database, or selected user sessions, from the server.
    - Finding a server name in the domain with the Domino® Administrator
      You can search for a server name in the domain and then view a log that includes document links and directory links to each occurrence of the server name.
    - Recertifying a server ID
      Use the original certifier to recertify a server ID that has a certificate that is about to expire.
    - Uninstalling a Domino® partitioned server
      You can remove all server partitions from a computer or you can remove just one server partition.
    - Reinstalling or moving a Domino® server from one computer to another
      Use this procedure to reinstall a server if an error occurs and the installer does not complete during the install of an incremental installer, or if the Domino® server is crashing and troubleshooting does not reveal the root cause.
    - Transaction logging
      Domino® transaction logging captures changes made to a database and writes them to a transaction log. The logged transactions are then written to disk in a batch, either when resources are available or when scheduled.
    - Installing and running NSD as a Microsoft™ Windows™ service
      Installing and running NSD as a Microsoft Windows service is no longer available as of Domino 10.
    - Setting up a Fault Reports database
      The Notes/Domino Fault Reports database stores data that is collected at the time of a server crash. Data is collected from both the client and the server and can then be used to measure client reliability and determine the areas where problems exist.
    - Client and server diagnostics
      Use these tasks to perform client and server diagnostics to collect diagnostic information after a server or client crash.
    - Collecting diagnostic information after a server or client crash
      The automatic diagnostic collection tool collects diagnostic data after server and client crashes and sends the collected data to a mail-in database when the server or client restarts. You can then use the collected data to determine the cause of the crash.
    - Using the IBM_TECHNICAL_SUPPORT directory
      The IBM_TECHNICAL_SUPPORT database contains data that has been collected using the Domino® Configuration Collector and the Automatic Diagnostic Data Collection tool. It also includes system information files and documents that have been exported from the Domino Directory and saved as .dxl documents using the Save command entered at the Domino server console.
    - The Domino® server log file (LOG.NSF)
      Every Domino® server has a log file (LOG.NSF) that reports all server activity and provides detailed information about databases and users on the server. The log file is created automatically when you start a server for the first time.
    - Controlling the size of the log file
      By default, the log file (LOG.NSF) records information about the Domino® system.
    - The Domino® Web server log (DOMLOG.NSF)
      You can log your server activity and Web server requests to the Domino® Web server log (DOMLOG.NSF) database. This option may be preferable if you want to create views and view data in different ways.
      - Setting up the Domino® Web server log (DOMLOG.NSF)
        To set up the Domino® Web server log, you must enable logging (by default, logging is disabled).
      - Viewing the Domino® Web server log
        You can view the Domino® Web server log (DOMLOG.NSF).
      - Logging Domino® Web server requests
        You can log Domino® Web server requests to a database or to text files. You can also log to both text files and a database.
      - Domino® Web server logging to text files
        When setting up Domino® Web server logging to text files, you must determine the Access file format. The content of the Access log varies depending on which log file format you choose: Extended Common or Common. The most commonly used Access log format is Extended Common, which logs all Web server information into a single text file.
        Setting up Domino® Web server logging to text files
        To set up logging the Domino® Web server to text files, you must enable logging (by default, logging is disabled).
    - Using console log mirroring
      Console log mirroring causes a new server thread to be created which monitors all messages written to the Console Log file and duplicates these messages into another file. When this new file is filled, the thread closes the mirrored file and creates a new file into which subsequent messages are written. You can delete the closed mirrored files at your discretion.
    - Using the Domino® Configuration Tuner to evaluate server settings
      The Domino® Configuration Tuner (DCT) evaluates server settings according to a growing catalog of best practices. All servers in a single domain can be evaluated together. DCT generates reports that explain the issues DCT uncovers, suggests mitigations, and provides references to supporting publications.
    - Activity Logging
      You use activity logging to collect information about the activity in your enterprise. You can use this information to charge users for the amount they use your system, monitor usage, conduct resource planning, and determine if clustering would improve the efficiency of your system.
    - Managing a cluster
      After you have set up a cluster, you can perform tasks to manage it.
  - Managing databases
    Topics in this section describe how to set up and manage Domino® databases.

Domino® Web server logging to text files

When setting up Domino® Web server logging to text files, you must determine the Access file format. The content of the Access log varies depending on which log file format you choose: Extended Common or Common. The most commonly used Access log format is Extended Common, which logs all Web server information into a single text file.

Optionally, you can choose Common for the Access log file format; however, the Common format is an older log file format and is available primarily for legacy information. If you choose the Common format for your Access file, it contains a subset of the server request information, with the requesting agent and referer information stored in separate Agent and Referer log files. It is difficult to match the entries in these different log files because a referer is not always sent with every request, so the number of referer entries may not match the number of requests.

When you log to a text file, the following information is recorded.

Table 1. Log information
Text file	Records
Access	The Access log records different information depending on whether the format in the Server document is set to Common or Extended Common. In Common format, the Access log records the following information: Client DNS name or IP address if DNS name is not available Host header from request, or server IP address if Host header is not available Remote user if available Request time stamp Http request line Http response status code In Extended Common format, the Access log records the following information: Client DNS name or IP address if DNS name is not available Host header from request, or server IP address if Host header is not available Remote user if available Request time stamp Http request line Http response status code Request content length if available, otherwise shows "-" Referring URL if available, otherwise shows "-" User agent if available, otherwise shows "-" Amount of time, in milliseconds, to process the request Value of the cookie header Translated URL, (the full path of the actual server resource, if available)
Agent	User agent if available, otherwise shows "-"
Referer	URL the user visited to gain access to a page on this site