Home
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.
The Administration Process
The Administration Process is a program that automates many routine administrative tasks.
Using AdminQ to process web user requests
Use Administration Quick (AdminQ) to expedite the processing of Administration Process (AdminP) requests that affect the user IDs of web users, for example, HCL Verse users. The users must have IDs in an ID vault.
Customizing AdminQ
You can use notes.ini settings to customize AdminQ.

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.
  - The Domino® Administrator
    The Domino® Administrator is the administration client for Notes® and Domino. You can use the Domino Administrator to perform most administration tasks.
  - The Server Controller and the Domino® Console
    The Server Controller is a Java-based program that controls a Domino® server. Starting the Server Controller starts the Domino server it controls. When a server runs under a Server Controller, you can send operating system commands, Controller commands, and Domino server commands to the Server Controller.
  - The Administration Process
    The Administration Process is a program that automates many routine administrative tasks.
    - Specifying the administration server for the Domino® Directory
      Choosing the administration server for the Domino® Directory depends on your network setup, the available equipment, and the anticipated changes that will be made to the Domino Directory via the Administration Process.
    - Setting up the Administration Process
      You complete a set of tasks to set up the Administration Process.
    - Administration Process support of secondary Domino® Directories
      Domino® supports the use of secondary Domino Directories for maintaining user names and groups that you want to store in a directory other than your primary Domino Directory, NAMES.NSF. For example, you may want to maintain Notes® users with Notes IDs in NAMES.NSF, but maintain Web-only users in a secondary Domino Directory.
    - Processing administration requests across domains
      The Administration Process for the Domino® Directory must be set up on a server in each domain.
    - Setting up ACLs for the Administration Process
      Each administrator who uses the Administration Process to perform tasks must have the appropriate access rights and roles in the Domino® Directory (NAMES.NSF), secondary directories -- if applicable, Administration Requests database (ADMIN4.NSF), and the Certification Log database (CERTLOG.NSF).
    - Modifying the Action field in the Access Control List (ACL)
      The Access Control List (ACL) dialog box for Notes® (.NSF) applications contains an Administration Server field and an Action field on the Advanced panel. Use caution when modifying these fields.
    - The Administration Requests database
      Use the views in the Administration Requests database (ADMIN4.NSF) to sort and examine requests in many ways.
    - Managing Administration Process requests
      Managing administration process requests involves approving requests, forcing requests when they must be processed immediately, and checking the Administration Requests database for errors.
    - Customizing the Administration Process
      You can customize the Administration Process.
    - Using AdminQ to process web user requests
      Use Administration Quick (AdminQ) to expedite the processing of Administration Process (AdminP) requests that affect the user IDs of web users, for example, HCL Verse users. The users must have IDs in an ID vault.
      - The Administration Quick Requests database
        AdminP creates the Administration Quick Requests database (adminq.nsf) from the adminq.ntf template. adminq.nsf is used by AdminQ in its request processing.
      - Customizing AdminQ
        You can use notes.ini settings to customize AdminQ.
      - How AdminQ rename requests are processed
        When you rename a web user who has a vaulted ID, for example, an HCL Verse user, the steps to process the request occur automatically.
      - How AdminQ recertify requests are processed
        When AdminQ is enabled on the domain administration server and you recertify the ID of a web user or a Notes user, the following steps to occur to process the request automatically.
      - How AdminQ key rollover requests are processed
        When you initiate a Notes ID key rollover request from an ID vault Security Settings policy, the following steps occur to update the keys in the ID file of web user who has a vaulted ID.
    - Statistics generated during administration request processing
      The Administration Process records statistics to help you monitor the request processing activity of the administration process tasks.
    - Administration request messages
      The response Log documents in the Administration Requests database contain error messages that describe any errors that occur during the processing of an administration request. Error messages also appear on the console of the administration server. Administrators who want to be notified when one of these events occurs on a server, can create an Event Handler document in EVENTS4.NSF to define how they want to be notified.
    - Administration Process requests
      An administration request is created by the administrator performing an action; it represents an administration task and is run by the server task AdminP (Administration Process). When an administration request is generated, it appears in the Administration Requests database.
  - Domino® server commands
    This section describes the Domino® server commands that are available, as well as methods of issuing those commands.
  - Domino® server tasks
    The information in this topic describes Domino® server tasks and their defaults in the NOTES.INI file.
  - IBM® i server commands
    You can use IBM® i server commands to manage Domino® with IBM i.
- 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.
- Managing databases
  Topics in this section describe how to set up and manage Domino® databases.

Customizing AdminQ

You can use notes.ini settings to customize AdminQ.

Procedure

Use any of the following settings:


Setting	Description
ADMINQ_POLLING_SECS=<number>	Changes how frequently in seconds AdminP checks adminq.nsf for "Needs Processing" requests. Default is 3600 seconds (one hour).
ADMINQ_ROLLOVER_CHECK_HOURS=<value>	Early Access only Changes how often AdminQ checks the vault Security Settings policy for rollover requests that need to be scheduled. By default, it does this daily between midnight and 1:00 AM. For testing purposes, use this setting to enable AdminQ to check more frequently. You can specify a value in hours to have AdminQ check every `x` hours after server startup. Or, to use the frequency specified through ADMINQ_POLLING_SECS, specify `0`.
ADMINQ_WEB_ONLY=0	Enables AdminQ rename requests to be used for Notes client users so that these users are not required to authenticate with the Notes client to process the requests. By default, rename requests apply only to Verse and iNotes users.
DEBUG_ADMINQ_RENAME=1.	Enables AdminQ debugging for aid in troubleshooting.
ADMINQ_ENABLE=0	Disables AdminQ on a server. As of Domino 12.0.2, AdminQ is enabled on domain administration servers and vault administration servers by default.
ADMINQ_DISABLE_PROCESSING =<number>	Early Access only Note: The following configuration will not be used when 12.0.2 ships. When AdminQ is enabled, control which of the three supported AdminQ requests are enabled. Specify the sum of the values that represent each type of request to `disable`: internaltest: 16 UserRename: 64 UserRecertify: 128 UserRollover: 256 For example, to enable only UserRecertify requests, specify 336, the sum of 16+64+256. By default, UserRecertify and UserRollover requests are disabled. Note: To enable all requests, specify 16, which disables only an internal request previously used for development testing.