Roadmap of Administration Process Requests: Deleting a person's name [return to the Roadmap Administration Process Requests main article]

You can use the Administration Process to delete a person's name throughout the databases in a domain. The Delete Person action automatically deletes the Person document in the Public Address Book. When you do this, you can also choose to delete the person's mail file and, optionally, any replicas of the mail file. The following sequence of requests occurs:



Details on deleting a person's name
Here are details on the "how, why, where, and when" of each request involved with deleting a person's name.

Delete in Address Book
• Triggered by: Choosing "Actions - Delete Person" in the Public Address Book (or clicking the "Delete Person" button) and choosing to delay deletion of the name from the Public Address Book.
• Posted on: The server from which you choose the delete action.
• Carried out on: The administration server for the Public Address Book.
• Carried out: According to the Interval setting for the Administration Process in the Server document.
• Result: The Administration Process removes the name from the Public Address Book except from other people's Person documents.

Delete in Person Documents
• Triggered by: Completion of a "Delete in Address Book" request.
• Posted on: The administration server for the Public Address Book.
• Carried out on: The administration server for the Public Address Book.
• Carried out: According to the "Execute once a day requests at" setting for the Administration Process in the Server document.
• Result: The Administration Process removes the name from other people's Person documents in the Public Address Book.

Delete in Access Control List
• Triggered by: Choosing to immediately delete all occurrences of the name from the Public Address Book when initiating the delete action or the completion of a "Delete in Address Book" request (if you chose to delay deletion of the name from the Public Address Book.)
• Posted on: The server from which you choose the delete action (if you chose to immediately delete all occurrences of the name from the Public Address Book) or on the administration server for the Public Address Book (if you chose to delay deletion of the name from the Public Address Book).
• Carried out on: Each server in the domain.
• Carried out: According to the Interval setting for the Administration Process in the Server document.
• Result: Each server in the domain deletes the name from the ACLs of databases for which it is an administration server.

Delete in Reader/Author Fields
• Triggered by: Completion of a "Delete in Access Control List" request on the administration server for the Public Address Book (if you chose to immediately delete occurrences of the name from the Public Address Book) or completion of a "Delete in Person Documents" request (if you chose to delay deletion of the name from the Public Address Book).
• Posted on: The administration server for the Public Address Book.
• Carried out on: Each server in the domain.
• Carried out: According to the "Delayed Request" settings for the Administration Process in the Server document.
• Result: Each server in the domain deletes the name from Reader and Author fields of databases for which it is an administration server and that have the advanced ACL option "Modify all Reader and Author fields" selected.

Get Information for Deletion
• Triggered by: Completion of the "Delete in Access Control List" request on the administration server for the Public Address Book (if you chose to immediately delete all occurrences of the name) or completion of the "Delete in Address Book" request (if you chose to delay deletion of the name from the Public Address Book). You must also must have specified to delete the mail file in when you chose to delete the person.
• Posted on: The administration server for the Public Address Book.
• Carried out on: The deleted person's home server.
• Carried out: Immediately.
• Result: Person's home server creates an "Approve File Deletion" request which provides information about the mail file. This appears in the "Pending Administrator Approval" view of the Administration Requests database.

Approve File Deletion
• Triggered by: Completion of the "Get Information for Deletion" request.
• Posted on: The deleted person's home server.
• Carried out on: The server on which you approve the request.
• Carried out: When you manually approve or reject the request.
• Result: If you approve the request, the Administration Process creates a "Request File Deletion" request.

Request File Deletion
• Triggered by: When you approve an "Approve File Deletion" request.
• Posted on: The same server on which the approval was made.
• Carried out on: The administration server for the Public Address Book.
• Carried out: Immediately.
• Result: Creation of a "Delete Mail File" request.

Delete Mail File
• Triggered by: Completion of a "Request File Deletion" request.
• Posted on: The administration server for the Public Address Book.
• Carried out on: The deleted person's home server.
• Carried out: According to the Interval setting for the Administration Process in the Server document.
• Result: The Administration Process verifies that the administrator who approved the deletion has at least Author (with Delete documents) access to the Public Address Book. Then, if the mail file doesn't use shared mail, the Administration Process deletes the file. If the file does use shared mail, then the Administration Process purges the links to the shared mail database, disables replication, and creates a "Delete Unlinked Mail File" request.

Delete Unlinked Mail File
• Triggered by: Completion of a "Delete Mail File" request for a mail file that uses shared mail.
• Posted on: The deleted person's home server.
• Carried out on: The deleted person's home server.
• Carried out: According to the "Interval between purging mail file and deleting when using object store" setting for the Administration Process in the Server document.
• Result: The Administration Process deletes the mail file after waiting a period of time. This delay provides time for the Object Collect task to purge any obsolete messages.
• Note: If the person requesting the delete action chose to delete all replicas of a mail file, then a "Get Information for Deletion" request is created and processed by all servers in the domain. This request is posted after completion of the "Delete Mail File" request or the "Delete Unlinked Mail File" request. For each replica of the mail file found on servers in the domain, the "Approve File Deletion," "Request File Deletion," and "Delete Mail File" request sequence occurs again.

[go to the Deleting servers and groups task]
[return to the Roadmap Administration Process Requests main article]

Copyright 1997 Iris Associates, Inc. All rights reserved.