Domino contains an asynchronous mechanism for processing various internal tasks. For example, if the name of a user account changes, this mechanism ensures that the access control list from the Notes database is also modified.
The request is processed by the Notes server task AdminP that runs on every Notes server. This task checks at set intervals whether there are new requests pending that require handling. These are placed in the Notes database admin4.nsf in the form of request documents and then replicated on every Notes server. After a request has been processed, the running Notes server creates a response document and if necessary a follow-up request.
AdminP requests are queued by certain changes in One Identity Manager, for example, to change parts of a users name, exchanging certificates, or when restoring a user ID.
Several factors are involved in determining when these will be processed:
- When was the request replicated on the running Notes server?
- How often does the AdminP server task run on the running Notes server?
- Which type of request is it?
Related topics
Certain AdminP requests have to be confirmed first by the administrator before they can be run. It is possible to confirm them automatically with One Identity Manager. Prerequisite for this is regular synchronization of the Admin4 database.
To confirm pending AdminP requests regularly
-
In the Designer, configure and enable the Automatically confirm Domino request from AdminP schedule.
For more information about editing schedules, see the One Identity Manager Operational Guide.
Confirmation of the following requests has currently been implemented:
- Approve MailfileDeletion
- Approve MovedReplicaDeletion
- Approve ReplicaDeletion
Related topics
Properties of synchronized AdminP requests are displayed in the Manager.
To display the main data of a request document
Table 25: Main data of an AdminP request document
|
Action |
Action to be run by the AdminP request. |
|
Executing server |
Server to run the request. |
|
Object |
Name of the object to which the action will be applied. |
|
Author |
Name of the AdminP request author. |
|
Database file |
File name of the database to be processed. |
|
Approval code |
Specifies whether the AdminP request has been approved by an administrator. |
|
Change label |
Specifies whether the AdminP request was changed. |
To display the main data of a response document
-
In the Manager, select the HCL Domino > Hierarchical view > <domain> > Administration requests > <filter> > <object> > <action> category.
-
Select the response document in the result list.
Table 26: Main data of an AdminP response document
|
Action |
Action that was run by the AdminP request. |
|
Request document |
Unique ID for the associated request document |
|
Target |
Name of the object that was processed. |
|
Author |
Name of the AdminP request author. |
|
Executing server |
Server that run the request. |
|
Request initiated on |
Creation date of the request. |
|
Database file |
File name of the database processed. |
|
Error code |
Specifies whether errors occurred while processing AdminP requests. |
Related topics
You use One Identity Manager to manage all objects of the Domino that are required for the optimization of access control in the target system. These objects are imported into the One Identity Manager database during synchronization. You cannot display or edit their properties in the Manager.
Detailed information about this topic
