Administration Process

2
What is Administration Process?

The Administration Process (AdminP) is a Domino task that runs on the
server to execute housekeeping, maintenance, and administrative
tasks.

For example, if you delete a user, the Administration Process locates that
user's name in the Domino Directory and removes it, locates and
removes the user's name from ACLs, and makes any other necessary
deletions for that user. If you want to delete all replicas of a database,
the Administration Process finds the replicas on servers in the domain
and provides an interface for deleting them.
3
Administrative Tasks
Name management tasks: Rename person, rename group, delete
person, delete group, delete server name, recertify users, and store
Internet certificate.

Mail file management tasks: Delete mail file and move mail file.

Server document-management tasks: Store CPU count, store
platform, and place network protocol information in Server document.

Roaming user management: Roaming user setup, move roaming
users to other servers, upgrade a non-roaming user to roaming status,
and downgrade roaming user to non-roaming status.
4
Administrative Tasks
User mail file management tasks: Performing Access Control List
(ACL) changes and enabling agents. For example, the "Out of Office"
agent is enabled and disabled by IBM Lotus Notes client users.

Person document management tasks: Storing the user's Notes
version and client platform information.

Replica management tasks: Create replica, move replica, or delete
all replicas of a database

5
Components Involved in Administration Process
AdminP server task

Administrator client (Domino and/or Web)

Notes client

Domino Directory (names.nsf)

Certification log database (certlog.nsf)

Administration Request database (admin4.nsf)

Administration server (assigned to each database in the domain)
6
AdminP server task

The AdminP server task runs on all Domino servers. This task loads
when the Domino server is first started

AdminP is controlled through :

Notes.ini variable




Server Tasks in Server Document

7
AdminP server task
Server Document Setting
8
AdminP server task
Notes.ini variables that controls Administration Process:


AdminPInterval
AdminPModifyPersonDocumentsAt
Adminp_Daily_Override
Adminp_Delayed_Override
AdminP_Disable_move_Mail_Connectivity
Adminp_Dont_Attempt_Direct_Deposit
Adminp_Exchange_All_Unread_Marks
AdminP_Immediate_Override
Adminp_Interval_Override
Adminp_Manage_Folder_On_Delegate_Disable
Adminp_Manage_Folder_On_Web_Delegate_Disable
Adminp_RestrictTime_Begin
Adminp_RestrictTime_End
9
AdminP server task
The AdminP server task wakes up on periodic time intervals and
executes commands waiting in the Administration Request database.
Each command placed in the Administration Request database has an
assigned proxy action. These proxy actions are essentially the Op-code
that runs the Administration Process.

Each command placed in the Administration Request database is
represented by a document. Each document has a number of fields,
including one called ProxyAction.

After each action has completed on a server, a response document is
Created to indicate the status of that request.


10
Administrator client
The Administrator client has all of the tools needed to initiate the
AdminP commands. These include renaming and deleting users, deleting
a replica, moving a database, and moving a user from one hierarchy to
another.
11
Notes client

Notes client can initiate and complete different administration
Processes

Accept user name changes and x509v3 certificates into the Notes.id file.

Initiate calendar ACL delegation.

Involved with the process to move a user to another server.

It can issue a request to change the user's password and/or synchronize his
Notes.id and Web password

Client can automatically accepts ID recovery information without user prompts

12
Domino Directory
The Domino Directory provides part of the instructions used with
AdminP. For instance, when a user is renamed, the certificate information
Is changed. This is stored in a Person document in the Domino
Directory. When the renaming process is in progress, this is indicated in
the Person document under the Change Request field. Each person's
name is stored in various fields in the Person document. When a user is
renamed, both the old name and new name are stored.

Every server has a Server document that controls how the server is
managed. Every Server document has a section on AdminP parameters.
13
Domino Directory
AdminP commands affect Domino Directory information, including:

Resource names

Clusters

Person documents, including client information

HTTP password synchronization

Group updates and deletions

Server information (protocol and version)

Policies

Certificate Authority (CA) configuration

License tracking

14
Certification log
The Certification log database (certlog.nsf) is created when you install
The first server in a domain. The Certification log records certification-
Related activities from Domino, including new user and server
registration, user recertification's and renames, and user moves from one
Organization level certifier to another

AdminP requires a Certification log on each server to initiate
administration requests.
15
Administration server

Every database must have an Administration server assigned to it,
listed in the database's ACL. This includes the Domino Directory. The
Administration server setting tells AdminP where to process each
database. The Administration server appears in the ACL with a key icon
next to its name. In each domain, there is a single Primary Administration
server. The Primary Administration server is determined by the value in
the ACL of the Domino Directory (names.nsf).
16
Administration Request database
This database contains all requests for a single domain. Every
request (via a proxy action) placed in the Administration Request
database replicates to every server in the domain.

Each Administration Request database in a domain has the same
replica ID and must replicate to all other servers in the domain that run
AdminP. This allows one server to post a request and another to respond
to it.

When an additional server in a domain is set up, the Administration
Request database is copied from the registration server to the new
server.


17
Administration Request database
For example: The command to recertify a user in the Domino
Directory (proxy action 10) can be issued to any server in the
domain. The command replicates to the Primary Administration
server, where it executes. The process is started in the
Administrator client when you request that a user be recertified.
18
Proxy Action
Every documents in the Admin request database is controlled
by set of commands called Proxy action.

Each Proxy action has a unique number assigned to it.

Version R5 has 82 different proxy actions, Version 6 retained
all the proxy actions available in previous releases and In
addition, to it 83 new proxy actions were introduced in R6, and
two additional proxy action where introduced in R6.5 all these
proxy action are available in R7.






19
Proxy Action
Each AdminP request can create a response document called
the Process Log. The response document shows if an AdminP
request completed successfully or failed with an error message.

Most proxy actions are created on the Primary Administration
server. Some can be initiated on a spoke Administration server

For example, if you rename a user, the primary request is issued by
AdminP at the Primary Administration server. In this example, a proxy
action 6 (move person's name in hierarchy) is created on the Primary
Administration server. You approve the name change and the Primary
Administration server creates a proxy action 8 (initiate a rename in the
Domino Directory). AdminP updates the public key and also updates the
Certificate Request field in the Person document.