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.

About this task

Before AdminQ was available, AdminP requests that affected Notes user IDs required web users to use an HCL Notes client to authenticate with a Domino server to complete the requests. With AdminQ, the Notes client authentication is no longer required for the completion of these requests.

AdminQ is a thread spawned by AdminP. It works in conjunction with existing AdminP requests. As of HCL Domino 12.0.2, AdminQ runs automatically on the domain administration server and vault administration servers. The first time AdminQ runs, AdminP creates the Administration Quick Requests database (adminq.nsf) which is used by AdminQ for request processing.

You can disable AdminQ by adding ADMINQ_ENABLE=0 to the notes.ini setting on the administration server for the domain. For more information, see Customizing AdminQ.

On Domino 12.0.1, AdminQ has to be enabled by adding ADMINQ_ENABLE=1 to the server notes.ini.

AdminQ comes into play when you perform any of the following tasks for users who have IDs in a vault:
  • Rename web users (Available starting with HCL Domino 12.0.1 requiring that the ID vault be on the administration server. As of Domino 12.0.2, the ID vault can be on any server.) Can apply to Notes users if the setting ADMINQ_WEB_ONLY=0 is used.
  • Recertify web users or Notes users (Available starting with Domino 12.0.2. Requires the 12.0.2 or higher adminq.ntf design.)
  • Roll over the public keys in web user ID files. (Available starting with Domino 12.0.2. Requires the 12.0.2 or higher adminq.ntf and idvault.ntf designs.)