Welcome
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.
Monitoring servers
This section describes how to use the tools and features that help you monitor a Domino® system.
Monitoring quality of service
Quality of Service, or QoS, is designed to react to the general operation of a Domino® server in order to keep that server functioning reliably and always available. If QoS detects that a server is not responding or hung, QoS probing can be configured to email an administrator about the problem and/or automatically terminate the server and restart it. QoS log information can also be useful for analysis by Support.
Verifying that QoS is running
If you are the not the administrator who enabled QoS, you can verify the correct setup.

HCL Domino 14.5 Documentation
Welcome to the HCL Domino® 14.5 documentation.
What's new in Domino 14.5?
Learn about all of the new features for administrators in HCL Domino® 14.5.
Overview
Welcome to HCL Domino® Administrator Help.
Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
Planning
Use this topic as an overview of planning task.
Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
Securing
This section describes security features, including execution control lists, IDs, and TLS.
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.
    - Monitoring the Domino® system
      You can monitor system activity and platform use using the Domino® Administrator or the server console.
    - Entitlement tracking
      As of Domino 12.0, a new internal mechanism is provided for collecting the highest entitlement that individual users have across a Domino domain. When a user appears in the ACL of a database with Reader access or above and that person has the right to access the server, the user is said to be an entitled user.
    - Administering Domino licenses with DLA
      The Domino License Administration (DLA) database (dominodla.nsf) automatically collects server and user information for a single Domino domain. It uses this data to classify users by license type.
    - Domino® domain monitoring (DDM)
      Domino® domain monitoring (DDM) provides one location in the Domino Administrator client that you can use to view the overall status of multiple servers across one or more domains, and then use the information provided by DDM to quickly resolve problems.
    - The Domino® SNMP Agent
      The Domino® SNMP Agent enhances the monitoring and control features of Domino by enabling third-party management stations, which use industry standard SNMP, to manage aspects of the Domino server.
    - Overview of server maintenance
      As a Domino® administrator, a major part of your job is maintaining each server that you administer.
    - Tools for mail monitoring
      Domino® provides three tools that you can use to monitor mail. Message tracking allows you to track specific mail messages to determine if the intended recipients received them. Mail usage reports provide the information you need to resolve mail problems and improve the efficiency of your mail network. Mail probes test and gather statistics on mail routes.
    - Monitoring directory assistance
      You can monitor directory assistance by using Show Xdir command to display information about all the directories a server uses for directory services. You can also view directory assistance statistics.
    - Monitoring databases
      You can monitor database activity, replication, and document deletions.
    - Monitoring a cluster
      Domino® provides several ways to find out what is happening in a cluster and make adjustments to keep the cluster running smoothly and efficiently, so that no server is overloaded. You can monitor failover, workload balancing, and cluster replication to see how efficiently the cluster is running.
    - Monitoring slow or unresponsive servers with the Domino® Diagnostic Probe
      Use the Domino® Diagnostic Probe (DDP), a Java™ utility provided by Support, to monitor servers that have been intermittently slow or unresponsive. The probe is a Java process (dbopen.jar) that runs in the background. The utility probes a specific Domino server over time by invoking database open transactions. If the probe detects a slow response, it will invoke Notes® System Diagnostic (NSD) to gather diagnostic data. This data is used by Support to troubleshoot and determine the cause or causes of the performance degradation.
    - Monitoring Smart Server Startup
      With Smart Server Startup, users are prevented from connecting to a Domino server until it is fully up and ready to accept user requests. For example, during startup of the Domino server after a crash, users can connect to the Domino server only after the server has fully recovered.
    - Monitoring quality of service
      Quality of Service, or QoS, is designed to react to the general operation of a Domino® server in order to keep that server functioning reliably and always available. If QoS detects that a server is not responding or hung, QoS probing can be configured to email an administrator about the problem and/or automatically terminate the server and restart it. QoS log information can also be useful for analysis by Support.
      - Enabling QoS when starting Domino®
        You enable QoS at a command prompt.
      - Limiting QoS restarts
        QoS provides the option to limit the QoS restart times during one interval. When the restart times reach the time limitation, the QoS service is deactivated.
      - Pausing and resuming QoS
        QoS provides a mechanism to pause or resume the QoS service at a specific time. Pausing QoS avoids allowing the server to be killed during an option that is expected to take a long time or that is critical to server operation; examples are backups or other maintenance operations. Temporarily disabling QoS allows these operations to complete without being misinterpreted by QoS as a server problem.
      - Running QoS with a no kill option
        You can run QoS with a no kill option. When QoS detects server exceptions, it sends a single email to a specified administrator with notification of the exception instead of killing and restarting the server directly. (You can also set QoS to send mail to an administrator whether or not you enable the no kill option.)
      - Running QoS with other configuration options
        You can run QoS with several additional options to disable probing and manage timeouts.
      - Verifying that QoS is running
        If you are the not the administrator who enabled QoS, you can verify the correct setup.
    - Understanding Quality of Service (QoS) behavior and logging
      This topic covers details of QoS including server and server controller behavior during kill events, failover trigger, and log file content.
  - Managing servers
    Manage Domino® servers by performing any of these tasks.
  - Managing databases
    Topics in this section describe how to set up and manage Domino® databases.
Tuning
Use this information to improve HCL Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, advanced database properties, cluster statistics, and the Server Health Monitor.
Troubleshooting
This section describes how to find and solve problems with HCL Domino® server and Administrator client.
Notices

Verifying that QoS is running

If you are the not the administrator who enabled QoS, you can verify the correct setup.

Procedure

Open and check the notes.ini file for the following setting:
```
QOS_ENABLE=1
```
Open and check the dcontroller.ini file for the following settings (all but the first are optional):
- QOS_ENABLE=1
- QOS_MAIL_TO=email address to send notifications to
  Tip: You can specify multiple email addresses; separate them using commas.
- QOS_MAIL_SMTP_SERVER=name of server to use when sending notifications through SMTP
- QOS_NOKILL=1
  Note: When this is set to 1, it stops QOS from killing the server when an event is triggered.
- QOS_MAIL_ATTACH_LOGS=1
  Note: If a notification is sent, a setting of 1 attaches the NSD logs.