AdminP operates with various configurations of the IBM
® Sametime server and IBM Domino
Sametime and the Domino Directory are hosted on the same machine
® and Domino
directory are on the same server. When a rename is made the AdminP add-in is notified and the callback updates the relevant databases. After the Name Change Utility is run all users can see each other's updated names.
Two or more Domino servers, each hosting Sametime and a Domino Directory
directories are replicated between all servers. Names.nsf and admin4.nsf are replicated on all servers. A name change executed on either one of these servers will trigger the AdminP process on both servers. Each AdminP process updates only the database that their administration server matches. This setting avoids replication conflicts.
Domino Directory hosted remotely from Sametime but within the same Domino domain
One or more Sametime servers and Domino
directory are in the same domain. Each Sametime server accesses the Domino
Directory through the directory assistance feature. Since all are in the same domain and the remote directory is accessed through da.nsf, updates are done on the remote directory and are received on the Sametime server. The Sametime server triggers the update of the databases that set their administration server to be the local server and activate the callback in the AddIns.
Domino Directory hosted remotely from Sametime, in a different Domino domain
This time, the Sametime servers and the Domino
directory are in different domains. For rename updates to go from the Domino
directory on Domain A to the Sametime servers on Domain B, a cross domain configuration should be applied on these domains. When a name is updated on the directory in domain B, a mail message is sent to domain A (assuming cross domain configuration is applied). This mail message is treated as a request for the AdminP and is added to the admin4.nsf which logs the request for the AdminP process.
Refer to the Domino
Administration guide for additional information on cross-domain configuration.
Domino Directory hosted remotely from Sametime, in a different Domino domain, and not serving as primary directory
servers and Domino
directory are in different domains, and the Domino
directory is not the primary directory for the deployment.
As In the previous configuration, the Cross Domain Configuration should be applied and the da.nsf on the Sametime
servers should point to the required NAB in the remote Domino
server (instead of names.nsf).
Two or more Domino Directories on remote servers, replicated with one or more Sametime servers
The Sametime servers and the Domino
directories are in different domains. A Cross Domain Configuration should be applied and the da.nsf on each Sametime server should point to the required NAB in the remote Domino
cluster. One server in the Domino
environment (domain B) should be defined as the Administration server of the Primary address book for the Domino
Domain. The da.nsf of each Sametime server should point to the NAB on this server.
Parent topic: Enabling AdminP integration