You may be a pro at administering a Domino server, but that doesn't mean you understand everything under the hood. Learn the no-fuss, no-frills, simple explanations of the most common Domino concepts and find out exactly how they work, and how to apply this knowledge to help avoid problems and improve performance. You'll learn how reader fields work, how replication and cluster replication works, mail routing including SMTP, the secrets of ACLs, ID file details, Adminp, busytime, cross-certification, recertifying, Domino domains, transaction logging, view indexes, and more. Learning the entire concept behind the "stuff" that's in Domino will make you a better troubleshooter, a faster problem-solver, and an all-around great admin!
9. This presentation is modeled after the brilliant example of HowStuffWorks.com From HowStuffWorks.com: "Our premise is simple: Demystify the world and do it in a simple, clear-cut way that anyone can understand."
11. Agenda How Notes Named Networks work How Replication works How Cross-Certifying works How Connection Documents work How Clustering works How View Indexes work How Mail Routing works How Busytime works How Transaction Logging works How Domino Domains work How Agent Manager works How Program Documents work How SMTP works How AdminP works How Smart Upgrade works How Access Control Lists work How ID Files work How Readers fields work How Recertifying works
19. While other uses are possible, the primary usage for having Notes Named Networks is for mail routing scenarios.
20.
21.
22.
23. When users find a replica of a database, it will automatically “find” replicas of databases also based on servers in the same NNN as the user's home server.
24.
25. In the Server doc, go to the Ports-->Notes Network Ports tab.
26. Enter the port name. Domino will automatically set the protocol.
110. The Router picks up the incoming message and deposits it into Domino's mail.box
111. The Router looks up the incoming address against the $Users view in the Domino Directory.
112. If it finds a match (and there are no restrictions against the address in the Configuration document) it looks up the user's home server in their Person document.
113. The routing tables finds the least-cost path to deposit the message in the mail.box of the user's home server.
114. Finally, the home server's Router task looks up their mail file in their Person document, and if the server has sufficient access in the ACL, deposits the message into the database.
127. A user can never be granted more rights in a database than what's been given to them in the ACL, no matter how the database is designed or what the Domino Directory says about them.
128. There are switches to fine-tune each access level, also called privileges .
129.
130. You can read documents that you are listed in an “Author”'s field.
137. These are so Domino knows what ID file type it should be expecting to go along with a name/Certifier combination.
138. Leaving a user or group as “Unspecified” in the ACL will make it possible for a user to create a local group titled as a person's name to gain higher access.
139.
140.
141. This allows you to cover your bases, and not leave an entry as “Unspecified”.
152. Setting it to “Reader” will allow anyone who access it to read the contents, rather than putting in an entire organization's group membership in the ACL.
202. Table of server access levels for replication: (from Notes Help) Access level Allows a server to push these changes Assign to Manager ACL settings Database encryption settings Replication settings All elements allowed by lower access levels Servers you want to use as a source for ACL changes. For tight database security, give this access to as few servers as possible. In a hub-and-spoke server configuration, you typically give the hub server Manager access. Designer Design elements All elements allowed by lower access levels Servers you want to use as the source for design changes. Use Manager access instead if you want one server to control ACL and design changes. Editor All new documents All changes to documents Servers that users use only to add and modify documents. In a hub-and-spoke configuration, you typically give the spoke servers Editor access. Author New documents No servers. You don't typically use this access for servers. Reader No changes; server can only pull changes Servers that should never make changes. Servers in the OtherDomainServers group are often given Reader access. Depositor New documents. Also prevents the server from pulling changes. No servers. You don't typically use this access for servers. No Access No changes. Also prevents the server from pulling changes. Servers to which you want to deny access. Servers in the OtherDomainServers group are sometimes given No Access.
571. 6. (Optional) Create a Desktop policy to upgrade their mail file at the same time.
572.
573.
574. However, as Smart Upgrade tracking is pushed down via policy, the tracking uses DCC
575.
576.
577.
578.
579. If a user is downloading the kit instead of installing across a network share, they will not receive notification to upgrade until the kit has completed downloading and the installation is ready to execute!
To deliver a message, the thread performs a DatabaseOpen call to the mail file, uses a NoteUpdate to deliver all messages pending delivery to that mail file, and closes the session The main thread creates a queue in matrix form for each mail file. One axis of the matrix shows messages for delivery, and the other axis shows the local mail files on the server A delivery thread handles delivery to each mail file. After the delivery thread delivers a message to a recipient’s mail file, it marks that recipient Complete and deletes the message from the delivery queue. The Router updates the main message queue with this state information and removes that recipient and that message as work items.
![Who are Jess and Susan? ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)