Home
Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
Monitoring
This section describes how to use the tools and features that help you monitor a Domino® system.
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.
Maintaining the Domino® Domain Monitor database
You can manage events from the Domino® Domain Monitor database. See the related topics for procedures for managing events from DDM.
Opening DDM.NSF at Domino® Administrator client startup
You can set an administration preference to open DDM.NSF when you start the Domino® Administrator client.

Administering
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.
- Monitoring
  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 one of three tools -- the Domino® Administrator, the Web Administrator, or the server console.
  - Server Health Monitor
    You can monitor and troubleshoot performance issues using a number of different tools.
  - 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.
    - DDM probes
      Domino® has a default set of DDM Probe documents that are shipped with the product.
    - Maintaining DDM Probes
      Use the procedures in this section to view, modify, and delete Probe documents, and to enable and disable probes.
    - DDM server collection hierarchy
      DDM probes run on a server and report events to the Domino® Domain Monitor database (DDM.NSF) that is on that server. Rather than visit every Domino Domain Monitor database on every server to review the probe results, create a DDM server collection hierarchy and have the data aggregated to a few servers.
    - Managing the DDM server collection hierarchy
      You use the Monitoring Configuration database (EVENTS4.NSF) to manage a DDM server collection hierarchy.
    - Domino® Domain Monitor database
      The Domino® Domain Monitor database (DDM.NSF) contains event information that is reported by DDM probes as well as event information reported by other checks that are built into Domino for DDM. Those checks include event generators; new checks that run as part of specific server tasks, such as the router or replicator; and checks that generate events in previous Domino releases and that have now been modified to report into DDM with additional information.
    - Specifying ACL settings and roles in the DDM database
      Several of the actions that you can perform while you maintain the Domino® Domain Monitor database (DDM.NSF) require that an administrator have a specific minimum level of access assigned in the ACL for DDM.NSF. Additionally, some activities require that a specific minimum level of access and a specific role be assigned.
    - Viewing events in the Domino® Domain Monitor database
      Use the Domino® Domain Monitor database (DDM.NSF) to view events sorted by severity, type, server, date or assignment. You can also view open events, recent events or all events simply by clicking a tab in these views.
    - Event-related documents
      When an event occurs, an Event Report is generated. Information in the Event Report is obtained from other sources or documents.
    - Maintaining the Domino® Domain Monitor database
      You can manage events from the Domino® Domain Monitor database. See the related topics for procedures for managing events from DDM.
      - Assigning events in the DDM database to an administrator
        In the DDM database, you can assign one or more selected events to an administrator that you choose. Assigning events enables you to manage Event documents and to delegate issues to be addressed in your domain.
      - Changing the state of an event in DDM
        When you open an event to view detail about the event, the Change State button displays. Use this button to change the state of an event. If you change the state of an Event document that is unassigned, the event is assigned to you. If you change the state of an Event document that is assigned to another administrator, the event owner is not changed.
      - Controlling the content and size of the DDM database
        To prevent the DDM database from becoming too large and using an excessive amount of disk space, you can filter by severity level the messages that are logged to the Domino® Domain Monitor. You can also designate whether both enhanced and simple events are filtered or whether only simple events are filtered.
      - Opening DDM.NSF at Domino® Administrator client startup
        You can set an administration preference to open DDM.NSF when you start the Domino® Administrator client.
      - Viewing correlated events in DDM
        A problem can generate multiple events. For example, when a target server becomes unavailable, the router, replicator, and other components may each generate errors. DDM correlates these events and reports them as one error. In keeping with this example, multiple errors are reported as one error: Server not responding.
      - Reassigning an event in the DDM database to an administrator
        The Domino® Domain Monitor has a Reassign Event feature, accessible from within the Event document, that you use to reassign an event that you have opened.
      - Resolving an event
        When you open an Event document in the Domino® Domain Monitor database, you can review the event's Probable Cause and Possible Solution statements. Many Event documents also contain a Corrective Action statement that can contain a link directly to the document or database that is named in the Corrective Action statement.
    - Using HCL Sametime® in the Domino® domain monitor database
      You can initiate an HCL Sametime® chat with another DDM administrator from the Domino® Domain Monitor (DDM) user interface.
    - Filtering events in DDM
      Create and use DDM filters to control which events are collected and then stored in DDM.
  - 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 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.
  - 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.

Opening DDM.NSF at Domino® Administrator client startup

You can set an administration preference to open DDM.NSF when you start the Domino® Administrator client.

About this task

Procedure

From the Domino® Administrator, click File > Preferences > Administration Preferences.
In the Basics section, locate the Domino® Administrator Startup Settings section.
Click Open specific database(s) and then do one of these:
- To use the default setting to open only DDM.NSF, do not enter anything in this field. DDM.NSF has been entered as the default.
- To add additional databases, enter the database file names, separated by commas.
In the Server field, specify the name of the server on which the specified databases are stored.
Click OK.