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.
Monitoring servers
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.
Event-related documents
When an event occurs, an Event Report is generated. Information in the Event Report is obtained from other sources or documents.
Using Modular documents
Modular documents are the reference documents for the Probable Cause, Possible Solution, and Corrective Actions statements.
Creating a Modular document
Use this procedure to create a modular document.

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.
    - 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.
        Using the Server and Addin Task Event document
        You can create a Server and Addin Task Event document that contains event detail such as event type, event subtype, event severity, and suppression time, as well as Probable Cause (PC), Possible Solution (PS), and Corrective Action (CA) statements.
        Merging modified Stock entries into Modular documents
        If you have modified any of the Stock entries provided by HCL, migrate those modifications into Modular documents. During this procedure, you will migrate all of your customized Probable Cause, Possible Solution, and Corrective Action statements from modified Stock entries to Custom entries. You only need to perform this procedure once. Future modifications are protected from being overwritten during an upgrade.
        Using Modular documents
        Modular documents are the reference documents for the Probable Cause, Possible Solution, and Corrective Actions statements.
        Creating a Modular document
        Use this procedure to create a modular document.
        Editing Modular documents
        You can use this procedure to modify a modular document, enable or disable a modular document, and to check the formula syntax used in the Corrective Action statement. When you open the modular document and then click Edit Document, a list of all message documents (event text) that uses this modular document appears at the base of the window. The listed message documents will be updated with the modifications you make after you save your modifications.
        Disabling a modular document
        You can disable a modular document.
      - 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.
      - 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 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.
    - 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.

Creating a Modular document

Use this procedure to create a modular document.

Procedure

From the Domino® Administrator, click the Files tab.
Open the Monitoring Configuration database, EVENTS4.NSF.

In the navigation pane, click Advanced > Modular Documents, and select New Modular Document.

Table 1. Options for a modular document
Field	Action
Type	Choose one: Probable Cause Text - Enter the text to be used as a Probable Cause statement that can be assigned to events. Choose this option, and then enter the Probable Cause text in the Text field. Possible Solution Text - Enter the text to be used as a Possible Solution statement that can be assigned to events. Choose this option, and then enter the Possible Solution text in the Text field. Corrective Action - Formula Code - Choose this option if the Corrective Action runs formula code. Complete the Description, Automatic and Code fields. Corrective Action - LotusScript® Code - Choose this option if the Corrective Action runs LotusScript® Code. Complete the Description, Automatic and Code fields. Corrective Action - Agent -- Choose this option if your Corrective Action runs an agent. Complete the Description, Server Type, Server Name, Agent Database, Agent Name, and Automatic fields.
Text	Specify the Probable Cause or Possible Solution text entry.
Description	Enter a description of the Corrective Action - Formula Code, LotusScript® Code, or Agent that you are defining. This description is used as the Corrective Action text on documents that include the Corrective Action you are defining.
Code	Enter the formula code for the Corrective Action - Formula Code or LotusScript® Code that you are defining.
Server Type	Choose one: Originating - The agent will run on the server on which the event occurred. Target - The agent will run on a target server. For example, if ServerA replicated to ServerB, ServerB is the target server on which the agent would run. Specific - The agent will run on a server that you specify in Server Name field.
Server Name	If Specific Server is selected, specify the name of the server on which the agent will run.
Agent Database	If the agent is to run on a specific database, specify the database name here.
Agent Name	Specify the name of the agent to use in the Corrective Action.

If you want to Enable this modular definition, leave the Enable check box selected; otherwise, deselect the checkbox.
Click Save and Close.