training-lotus
- 1. Introduction to Lotus Domino Adnan Hasan
- 2. 2 What is Lotus Notes? Lotus Notes is a groupware solution. It is a powerful software that helps people work together effectively. What is Groupware? Groupware is a relatively new type of information technology that allows individuals and groups to work together with a high degree of collaboration and coordination. The term "groupware" covers several types of technology, including e-mail, bulletin boards, group meeting software, discussion group support, group calendaring and scheduling, document management, and workflow. Groupware systems also can act as platforms for development of databases and applications by multiple users. - E-mail - Calendar - To do lists - Address Book - Internet address lookups - Web browsing - Internet e-mail (IMAP or POP) client software - Internet newsgroup messaging - Secure certificates
- 3. 3 Notes consists of two primary programs: - Domino server - Notes client – The Notes client runs on a computer running Windows or Macintosh software. It communicates with Domino servers and Internet servers so you can use, among other things, shared databases, read and send mail, find people and databases, and browse the Web. – The Domino server run on a computer running Windows, Linux or UNIX - provides services to Notes client users and other Domino servers including storage of shared databases and Notes mail routing.
- 4. 4 What's new in Release 5? New Domino server features Security - X.509 certificates - You can issue X.509 certificates to users. - Password recovery - If users forget their password, an administrator can recover their ID file. - File protection for Web files - Domino R5 lets you set access control for Web files such as images and HTML documents.
- 5. 5 Mail Native SMTP - The Domino router can transfer and deliver messages over SMTP as well as Notes RPC, allowing any R5 Domino server to act as an Internet mail server. Directory Directory Catalog (Compressed enterprise directory) - The Directory Catalog compresses one or more Domino Directories for fast, easy lookups of addresses. A 1 GB Domino Directory can be compressed into a 12 MB Directory Catalog. The Directory Catalog is an excellent tool for mobile users. Router performance Multiple MAIL.BOX databases Administration Message Tracking - R5 lets you track messages en route, including routing path & whether the message has been delivered.
- 6. 6 Applications Transaction logging - Transaction logging keeps a sequential record of every operation that occurs to data. If a database becomes corrupted, you can "roll back" the database to a point before it was corrupted and replay the changes from the transaction log. Online, in-place database compaction - With R5, you can compact databases while they are open. Compaction takes place without the need for extra disk space, where R4 required free disk space equal to the size of the database being compacted. Domino Enterprise Connection Services (DECS) - DECS lets you connect in real-time to backend data, such as relational databases and Enterprise Resource Planning (ERP) systems. Internet Internet clustering (fail over and load-balancing) - Web clients fail over to another server in a cluster when one server goes down, and Domino balances the load from Web clients across servers. Integration with Microsoft Internet Information Server (IIS) as HTTP stack - You can use Microsoft IIS as the HTTP services for Domino.
- 7. 7 New Domino application features Performance The Release 5 database format (On-Disk Structure, or ODS) and templates offer much improved performance, especially for databases such as the Domino Directory and MAIL.BOX. Database operations require less I/O, and memory and disk space allocation are improved. Transaction logging Transaction logging writes all changes to a database sequentially to a log file and does not physically alter the database until those changes are safely stored on disk. This allows you to recover data lost through database corruption or other problems by "rolling back" the database to a given point and replaying the changes to the database through the log. This also allows greatly improved backup of databases. R5 databases with transaction logging enabled do not need to have Fixup run on them. Be sure to use a separate, single-purpose, high-volume drive for the log files. Faster rebuilds View rebuilds are as much as five times faster in Release 5 if you designate a separate drive for the temporary files for the rebuilds. The greater the space on the drive you dedicate to view rebuilds, the greater the increase in rebuild speed. Multiple MAIL.BOX databases allow you to spread the mail load over several databases. Better compaction Compaction of Release 5 databases occurs online and "in place" and does not require additional disk space. Users can read and modify the database while compaction occurs. R5 compaction is significantly faster than R4 compaction -- up to 10 times faster. Database Size can be as large as 64 GB.
- 8. 8 Notes Client Preferences Basic settings - Change icon and bookmark color and size - Find unread documents - Turn on scheduled agents - Choose your location - Change the default fonts - Change the local database folder - Lock user ID when inactive - Change how you empty trash - Make Internet URLs into clickable hotspots - Close windows with right double-click - Make Notes my default Web browser
- 9. 9 Mail and News settings - Use a different Personal Address Book - Change how often Notes checks for new mail - Change how you save your sent mail - Specify how you want to be notified when you get mail Port settings - Configure ports - Delete a port - Reorder a port - Trace a port connection - Enable or disable a port Security settings - Create Safe copy - Merge Safe copy
- 10. 10 Domino Databases What is Domino Database Domino stores information in databases which contains objects known as documents. A document is an object containing text, graphics, video, audio, or other kinds of rich text. Database Elements Documents - Contain data Forms - Used to create documents Views - Used to display documents Agents - Program statement that run at certain times Navigators - Contains buttons, hotspot, links that perform action Database Format The database elements are stored in a database known as Notes Storage Facility (NSF). For eg, users mail file USERNAME.NSF & domino directory is a database NAMES.NSF *The maximum size of database in Notes R5 is 64 GB as compared to 4GB in R4.
- 11. 11 Working with Databases - Create a database - Open an existing database - Create new copy of database Database properties There are seven tabs in database properties: - Basics - Information - Printing - Design - Launch - Search - Advanced settings. Replacing/Refreshing the design of a database -Replace design to reflect new changes in database template -Refresh existing design to correct view corruption problem
- 12. 12 REPLICATION What is replication? Notes lets you keep multiple copies of a single file, called replicas, on multiple servers or workstations. This lets users on various networks in a variety of locations share the same information. A replica differs from a copy of a file, in that the original file and its replica have the same replica ID number. Replication is the process of sharing changes between replicas. When you replicate, Notes updates the replicas, copying changes from one to the other. Notes eventually makes all replicas identical. You can choose to replicate between replica copies, where both replicas send and receive updates, or only from one to the other. You can also regularly schedule replication, or do it manually as needed. You can replicate between two servers or between a workstation, such as a laptop, and a server.
- 13. 13 Client to server replication Notes lets you create copies of server databases on your workstation/server, called local replicas. Local replicas are useful because you can work with them when you're not connected to a server over a network. To perform client to server replication, you must first create a local replica. Then you can work in it locally and replicate changes between it and the database on the server. Replica IDs Replicating databases in the foreground Replicating databases in the background Customizing database entries Setting options on the Replicator Schedule replication
- 14. 14 Setting up Notes for a remote location Step 1: Set up a modem - Enable COM Port - Edit COM port options Step 2: Create location documents - Create location document (Notes Direct Dial-up) - Configure all other setting Step 3: Create connection document - Create Connection document
- 15. 15 Personal Address Book Notes looks in your address book to find information it uses when you send mail. For example, when you address a message to a person, Notes looks in your address book for the person's mail address. If Notes doesn't find the information it needs there, it checks in the Domino directory on your mail server. You can save information about contacts and mailing lists in your address book to address mail more easily. Personal Address Book saves information about: - Locations where you use Notes - Connection to Servers you connect to using Notes - Certificates - Personal Contacts - Personal Groups
- 16. 16
- 17. 17 Mailbox - Changing mail preferences Tools > Preferences - Create Out Of Office Agent when you are on leave Tools > Out of office - Add address of sender to Personal Address Book Tools > Add sender to Address Book - Changing Delivery Options - Encrypt mail - Prevent copying/printing of mail - Return receipt - Delivery Report - Mood Stamp - Importance - Delivery Priority - Auto Spell check
- 18. 18 NOTES ID - Domino uses ID files to identify users and to control access to servers. Every Domino server and Notes user must have an ID. When you register users and servers, Domino automatically creates their IDs. An ID file contains: - Name & licence information - Licence information - Private & Public keys - Certificates - Recovery Information (Optional) How Authentication Works Whenever a Notes client (or Domino server) attempts to communicate with a Domino server for replication, mail routing, or database access, two security procedures use information on the client's ID to verify that the client is legitimate. - Validation, the first procedure, establishes trust of the client's public key. - If validation occurs successfully, authentication, the second procedure, begins. Authentication verifies the identity of the user. - Authentication uses the public and private keys of the client and the server in a challenge/response interaction.
- 19. 19 Domino Server Installation License Type: - Domino Mail Server Domino & Internet mailing (POP3, IMAP, LDAP, HTTP) Calendaring & Scheduling - Domino Application Server All the functionality of Domino Mail server Custom Domino databases for Notes & Web clients Database Transaction Logging - Domino Enterprise server All the functionality of Domino Application Server Domino Clusters Internet Cluster Manager for Web servers Server Partitioning
- 20. 20 Domino Directory The Domino Directory, which previous releases referred to as the Public Address Book or Name and Address Book, is a database that Domino automatically creates/replicates on every server. The Domino Directory serves two purposes: - It is directory of information about users, servers, groups, and other objects that you might include in the directory yourself. - It is also a tool that administrators use to manage the Domino system. For example, administrators create documents in the Domino Directory to connect servers for replication or mail routing, to register users and servers, to schedule server tasks, and so on. When you set up the first server in a Notes domain, Domino automatically creates the Domino Directory database and gives it the file name NAMES.NSF. When you add a new server to the domain, Domino automatically creates a replica of the Domino Directory on the new server. Typically, a Domino Directory is associated with a Notes domain. When you register users and servers in the domain, you create Person documents and Server documents in the Domino Directory. These documents contain detailed information about each user and server.
- 21. 21 Mail Routing Mail routing components - Mail file - Mail server - Mailer - Domino Directory - Mail.box - Router How Mail is routed 1. Client creates & sends a mail message from the workstation/notes client. 2. Client Mailer program checks names in Directory (no check if address contains @). 3. Client Mailer puts mail in Mail.box on Home Server specified in user’s current location document. 4. Router task on server Polls Mail.box for new messages. 5. Router checks Directory for routing information & for address on the message & determines the message route. 6. Router transfers message to Mail.box on next destination server. 7. Router task on destination server polls Mail.box for new messages. 8. Router checks Directory for routing information for address on the message. 9. Router deliver message to recipient’s mail file. * Mail routing happens automatically in same DNN.
- 22. 22
- 23. 23 Mail Monitoring/Troubleshooting Tools Log Files Notes log (Log.nsf) records all console messages, both success & failure. Mail status - Pending mail: Mail awating delivery. Often referred to a the outbound queue. - Dead mail: Mail that cannot be delivered to receiver & receiver. Mail Quota - Limits the max size of a database. Mail Tracking Collector Why track a message? A user reports a message was sent but not received. The message is not: - A Non-delivery - In the pending queue of your server - On the hub server MTC requirements - Message Tracking is enabled on each server in route - There is Message Tracking Store database (MTCSTORE.nsf) - The appropriate tasks are running on server: - Router & Message Tracking Collector (MTC)
- 24. 24 How to check Mail queue on server? - Open Mail.box from the server & check the queue. How to route all messages to a particular server? - On the server console type Route <destination server>. All mail to the destination server will be routed immediately. Where can I change the Router settings? - Sever Configuration document > Router/SMTP tab. Messages are not getting delivered to Servers mailbox - User is working on local copy of mail file & mail setting are not proper in current location doc There are lots of messages in queue (servers mailbox) & Router is Idle (not delivering messages) - Unload Router Tell router quit - Load Router Load router How to handle Dead mails? - Dead mails are mails which can not be delivered to recipient & non-delivery report can not be delivered to Sender due to some problems (server down, link problem etc.)
- 25. 25 Type of Mail Clients accessing the Domino server Domino supports Notes, IMAP, POP3, NNTP, and Web clients. Notes clients Notes clients access the server via Notes protocols, POP3, IMAP, and NNTP. If your organization uses Notes clients, select any of these protocols for server access (though NNTP does not provide mail functionality). Enable the protocol on the server that clients use for access. IMAP clients IMAP clients access mail on the server via IMAP and send mail to the server via SMTP. Enable the IMAP service and use the Router for IMAP clients to use the Domino server for mail. POP3 clients POP3 clients access mail on the server via POP3 and send mail to the server via SMTP. Enable the POP3 service and use the Router for POP3 clients to use the Domino server for mail. NNTP clients NNTP clients access news groups and discussion databases on the server via the Domino NNTP service. The NNTP protocol does not provide mail functionality, though many NNTP clients also include IMAP and POP3 functionality. Enable the NNTP service for NNTP clients to use the Domino server for news and discussions. Web clients Web clients access mail on the server via the Domino HTTP service and send mail via SMTP using the Domino HTTP service and the Router. Enable the HTTP service and use the Router for Web clients to use the Domino server for mail. The SMTP listener must be enabled on the Domino server.
- 26. 26 Domino Named Network (DNN) What Is a Domino Named Network? Servers that meet the following criteria can be members of the same Domino Named Network : - Are in same domain - Share a common LAN protocol - Can maintain a constant connection on the same LAN or bridged/routed WAN Mail routing within a DNN - Mail routing occurs automatically between servers in the same DNN Why to Separate servers into different DNN? - To control when mail routes between servers - To reduce the network traffic Determine current DNN - Server document > Ports tab
- 27. 27 Hierarchical Naming A system of naming associated with Notes IDs that reflects the relationship of names to the certifiers in an organization. Hierarchical naming helps distinguish users. Domino uses hierarchical naming to guarantee unique user & server names across a large network. Hierarchical names are also known as Distinguished Names. An example of a hierarchical name that uses all the components is as follows: Julia Herli/Sales/East/Acme/US Typically, names are entered and displayed in their abbreviated format (see above) and stored internally in canonical format, which is a format that contains the name and its associated components: CN=Julia Herli/OU=Sales/OU=East/O=Acme/C=US.
- 28. 28 Component Description Characters Required Common Name (CN) The person’s Full first & Last name, or server name 80 max Yes Organizational Unit (OU) Typically a department or location name 32 per OU No Organization Name (O) Company Name 3 to 64 Yes Country 2 letter abbreviation for country & top-level location 0 or 2 No
- 29. 29 Server Topology Planning a topology for server connections To determine how to configure Connection documents, you must plan a server topology. The topology is a plan for how servers connect to each other. When planning a server topology, keep in mind that you want to keep the number of Connection documents to a minimum and that you want to keep the number of "hops" -- that is, stops along the way to a destination -- to a minimum. These factors influence server topology: - Number of servers in the company, and whether all the servers are in the same or different Notes named networks - Location of servers -- that is, whether they are in the same domain or in a foreign domain - Tasks running on the server -- replication, mail - Function of the server in the topology -- passthru, dial-in, network dial-up (remote access service) Type of topologies - Hub-and-spoke - peer-to-peer - Ring - Binary Tree
- 30. 30 Hub-and-Spoke In Hub and Spoke topology there is one Hub server & all other servers are spoke servers for any kind of information. A hub-and-spoke topology establishes one central server as the hub and other servers as the spokes. The spokes update the hub server by replication and mail routing, and the hub in turn updates each spoke. In organizations with more than one hub, hub servers replicate with each other or with master hub servers. Hub-and-spoke topology works best in large organizations; it minimizes network traffic and is the most efficient topology for replication/mail routing. If you use hub-and-spoke, keep in mind that your topology is vulnerable to a single point of failure if the hub is not working (cluster your Hub server). Hub-and-spoke topology is most commonly used topology.
- 31. 31 Peer-to-peer A peer-to-peer topology connects every server in your organization to every other server. This topology works best in companies that have only a few servers to connect.
- 32. 32 Access Control List (ACL) What is database ACL? Every Domino database has an Access Control List, commonly named as ACL, is used to determine who can access database , and the type of access they are allowed. For each user, group, or server listed in the ACL, you select the basic access level and user type, and then further refine the access level by selecting a series of access privileges. If the application designer creates a role for the application, then assign the role in the database ACL for the appropriate person, group, or server. To access a database on a particular server, a Notes user must have both the appropriate level of access to the database, as well as the appropriate access in the Server Access section of the Server document. Default entries in the ACL A new database, by default, contains these entries in the ACL: -Default- Database creator name LocalDomainServers OtherDomainServers
- 33. 33 Access Level Privileges When to assign... Manager Can modify ACL settings, encrypt a database for local security, modify replication settings, and delete a database -- tasks permitted by no other access level. Managers can also perform all tasks allowed by other access levels. Notes requires each database to have at least one Manager. It's best to assign two people with Manager access to a database in case one manager is absent. Designer Can modify all database design elements (fields, forms, views, public agents, the database icon, Using This Database document and About This Database document), can modify replication formulas, and can create a full text index. Designers can also perform Assign to the original designer of a database or to a user responsible for updating the design after a database is in use. Editor Can create documents and edit all documents, including those created by others. Assign to a user responsible for maintaining all data in a database. Author Can create documents and edit documents they create. Assign when you want to allow users to contribute to a database but not edit documents created by others. When possible, use Author access rather than Editor access to reduce Replication or Save Conflicts. Reader Can read documents in a database but cannot create or edit documents. Assign to users who must be able to read the contents of a reference database such as a company policies database. Depositor Can create documents but can't see any documents in the database views, even the documents they create. Assign to allow users to contribute to a mail-in database or to a database used as a ballot box. No access Cannot access the database. Assign as the default access to prevent most users from accessing a confidential database. ACL Levels
- 34. 34 User types in the ACL A user type identifies whether a name in the ACL is for a person, server, or group. When you assign a user type to a name, you are specifying the type of ID required for accessing the database with that name. The user types are Person, Server, Mixed Group, Person Group, Server Group, and Unspecified. User types provide additional security for a database. For example, assigning the Person user type to a name prevents an unauthorized user from creating a Group document with the same person name, adding his or her name to the group, and then accessing the database through the group name. User type: Person - Individual Users Server - Individual Servers Mixed Group - Group of users & server Person Group - Group of persons Server Group - Group of servers
- 35. 35 Database Roles Although ACL is the first level of security, additional security is available using Roles to control create & edit documents. A role is similar to a group, but is created in the database ACL, while a group is defined in the Domino Directory. A role only applies to the database in which it was created. You must create a role before you assign it to a name or group in the ACL. You must have Manager access to create roles in the database ACL. Roles in Domino Directory Role Allows GroupCreator Users with "Create documents" privilege to use the Create menu to create new Group documents GroupModifier Users with Author access to edit Group documents* NetCreator Users with "Create documents" privilege to use the Create menu to create all documents except Person, Group, and Server documents NetModifier Users with Author access to edit all documents except Person, Group, and Server documents* ServerCreator Users with the"Create documents" privilege to use the Create menu to create new Server documents ServerModifier Users with Author access to edit Server documents* UserCreator Users with the "Create documents" privilege to use the Create menu to create Person documents UserModifier Users with Author access to edit Person documents * * To delete documents in the Domino Directory, users must have the "Delete documents" privilege in the
- 36. 36 The Administration Process The Administration Process is a program that automates many routine 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. The Administration Process automates these tasks: - Name-management tasks, such as rename person, rename group, delete person, delete group, delete server name, recertify users, and store Internet certificate Mail-file-management tasks, such as delete mail file, and move a mail file. - Server-document-management tasks, such as store CPU count, platform, and place network protocol information in Server document Administration servers Administration servers control how the Administration Process does its work. You specify an administration server for the Domino Directory and for each database. By default, the first Domino server you set up in a domain is the administration server for the Domino Directory. The administration server for the Domino Directory maintains the Domino Directory's ACL, performs deletion and name change operations, and replicates these changes to other replicas of the Domino Directory in the domain.
- 37. 37 Administration Requests database The Administration Process primarily interacts with the Administration Requests database, which is created on the administration server for the Domino Directory when that server starts for the first time. To complete tasks, the Administration Process posts and responds to requests in the Administration Requests database. Domino servers use replicas of this database to distribute requests made on one server to other servers in the domain. When other servers start, if the Administration Requests database does not exist, the server creates a replica stub of the Administration Requests database and waits for it to be initialized from another server in the domain. Every server in the domain stores a replica of the Administration Requests database and the Domino Directory. Certification Log To use the Administration Process to perform name changes and recertifications, you must set up the Certification Log (CERTLOG.NSF) on the server that stores the Domino Directory in which you will initiate the name change or recertification. If the Certification Log exists on another sever, move the Certification Log to the server containing the Domino Directory on which you are initiating the name change or recertification. This log contains a permanent record of how you register servers and users, including information about the certifier ID. The Certification Log also contains messages that describe the results of recertification requests that the Administration Process is processing.
- 38. 38 How ADMINP works 1. The Administration process task requests a change, such as deleting a group from the Domino Directory. 2. The request is posted to the Administration Request database. 3. The Administration Request Database is replicated throughout the domain 4. The Administration Server for the Domino Directory starts the process of deleting the group and posts its status back to Administration Request database. 5. The Administration Process database is replicated throughout the domain. 6. All servers named as administration servers in any database complete necessary steps to change ACL & field. 7. Administration server posts their status back to the Administration Request database. * For Administration Process to work, ADMINP task should be running on al the servers (Load ADMINP)
- 39. 39 Groups Groups are list of users, groups, and servers that have something in common. Groups are useful for creating mailing lists and ACL for databases. Types of Group Select a group type from the Group type field. The Group type specifies the purpose of the group and determines the views in the Domino Directory where the group name appears. For example, mailing list groups appear in the Mail Users view, and access control groups appear in the Access Control view. Using specific group types improves performance by reducing the size of view indexes in the Domino Directory. Group type Purpose Multi-purpose Use for a group that has multiple purposes -- for example, mail, ACLs, and do on Access Control List onlyUse for adding to ACLs Mail only Use for mailing list groups Servers only Use for server groups Deny List only Use to add terminated users or other users. The Administration Process cannot delete any member of the group.
- 40. 40 Recertification About ID Expiration ID’s contain certificates & for security reasons ID’s are given an expiration date. ID expiration dates are dependent on certificate dates. When a certificate expires, a user can no longer use it to communicate with servers & clients. If the certificate is not renewed by the expiration date, the ID is invalid. Notes prompts the user when the ID is about to expire. How to determine when a Certificate expires? - Choose File > Tools > User ID. - Click Certificates. How to renew the Certificate? By Recertifying an ID file certificates are renewed (assigned new expiration date) * Certifier ID’s are used to recertify certifiers below them in the hierarchy & to recertify servers & users within their branch of hierarchy.
- 41. 41 Cross-Certification Cross-certification allows a server or user in one hierarchy to authenticate with a server in another hierarchy. Cross-certification is required if two entries, servers or users, do not share a certificate in common. Agents What is an Agent? An Agent is a program that performs series of automated tasks according to a set schedule, at users request, or in response to the occurrence of an event. What is an Agent Manager? The Agent Manager controls when an agent runs on a server. Every time an agent runs, it uses server resources.
- 42. 42 Replicas and replication To make a database available to users in different locations, on different networks, or in different time zones, you create replicas. All replicas share a replica ID which is assigned when the database is first created. The file names of two replicas can be different, and each replica can contain different documents or have a different database design; however, if their replica IDs are identical, replication can occur between them. As users add, edit, and delete documents in different replicas of a database, the content in the replicas is no longer identical. To ensure that the content in all replicas remains synchronized, you use Connection documents to schedule replication between the servers that store the replicas. Then multiple sites, teams, and users can make changes to a database and share those changes with everyone else who has access to that database. In addition, using replicas and scheduling replication reduces network traffic. Users never need to connect to a single central server that stores the only replica of a particular database; instead, they can access a replica of that database on one or more local servers. A replica of a database isn't the same as a copy of a database that you make by choosing File - Database - Copy. Although a copy of a database may look the same as the original database, a copy doesn't share a replica ID with the original database and so it can't replicate with it.
- 43. 43 Server to Server Replication How server-to-server replication works For server-to-server replication, the Replicator on one server calls another Domino server at scheduled times. By default, the Replicator is loaded at server startup. To schedule replication between servers, you create Connection documents that describe when servers connect to update replicas. As users add, edit, and delete documents in a database, the replicas contain slightly different information until the next time the servers replicate. Because replication transfers only changes to a database, the network traffic, server time, and connection costs are kept to a minimum. During scheduled replication, by default, the initiating server first pulls changes from the destination server and then pushes changes to the destination server. As an alternative, you can schedule replication so that the initiating server and destination server each pull changes or so that the initiating server pulls changes only or pushes changes only. You can also use the server commands initiate replication between servers. Replication, step-by-step 1. The Replicator remains idle until Server A initiates replication to Server B. 2. As a security precaution before replication, the two servers authenticate their identities in an exchange involving their public and private keys. First, the two servers find a certificate in common. Next, they test each other's certificate to ensure it is authentic. 3. The two servers compare lists of databases to identify databases with identical replica IDs.
- 44. 44 4. The servers check the time when each database was last modified to see if that time is more recent than the date of the last successful replication event recorded in the replication history. This step enables servers to determine that a database needs to be replicated. 5. For each modified database, both servers build a list of the document, design element, and ACL changes that occurred since the last replication with the other server. 6. For each modified database, Server A checks the database ACL to determine what changes Server B can make to its replica, and Server B checks the ACL to determine what changes Server A can make to its replica. 7. The transfer of document, design, and ACL changes takes place. For documents, the servers replicate only the fields that have changed, rather than replicating the entire documents. For documents that were deleted, deletion stubs remain, enabling the replicator to replicate the deletions. To save disk space, Domino removes these deletion stubs according to the purge interval that is set in the database replication settings.
- 45. 45 Type of Replication By default, Domino uses Pull-Push as the replication direction. However, you can specify a different replication direction. Pull-Push The default replication direction, is a two-way process in which the calling server pulls updates from the answering server and then pushes its own updates to the answering server. Using Pull-Push, the replicator task on the calling server performs all the work. Pull-Pull is a two-way process in which two servers exchange updates. Using Pull-Pull, two replicators -- one on the calling server and one on the answering server -- share the work of replication. Push-only is a one-way process in which the calling server pushes updates to the answering server. One-way replication always takes less time than two-way replication. Pull-only is a one-way process in which the calling server pulls updates from the answering server. One-way replication always takes less time than two-way replication. To change the replication direction, open the Connection document and then, in the "Replication Type" field, edit the calling server's replication direction. You can also specify replication direction when you force replication.
- 46. 46 Command Result Replicate Replicates changes to databases in both directions; Domino performs Pull-Push replication. Pull Replicates changes to databases in one direction where the initiating server pulls changes from the other server Push Replicates changes to databases in one direction where the initiating server pushes database changes to the other server. Mannual Replication
- 47. 47 Domino server tasks Task Command to run task Description Default in NOTES.INI file Administration Process AdminP Automates a variety of administrative tasks. ServerTasks Agent manager AMgr Runs agents on one or more databases. ServerTasks Billing Billing Collects all generated billing information. ServerTasks Calendar Connector Calconn Processes requests for free-time information from another server. ServerTasks Cataloger Catalog Updates the database catalog. ServerTasksAt1 Chronos Chronos Updates full-text indexes that are marked to be updated hourly, daily, or weekly. None Cluster Administration Process Cladmin Oversees the correct operation of all components of a cluster. None Cluster Database Directory Manager Cldbdir Updates the cluster database directory and manages databases with cluster- specific attributes. ServerTasks Cluster Replicator Clrepl Performs database replication in a cluster. ServerTasks Database compactor Compact Compacts all databases on the server to free up disk space. None Database fixup Fixup Locates and fixes corrupted databases. None Designer Design Updates all databases to reflect changes to templates. ServerTasksAt1 DIIOP DIIOP Allows Domino and the browser client to use the Domino Object Request Broker (ORB) server program. ServerTasks
- 48. 48 Task Command to run task Description Default in NOTES.INI file Directory Cataloger Dircat Populates directory catalogs and keeps the catalogs up-to-date. None Event Monitor Event Monitors events on a server. None HTTP Server HTTP Enables a Domino server to act as a Web server so browser clients can access databases on the server. None IMAP Server IMAP Enables a Domino server to act as a maildrop for IMAP clients. None Indexer Updall Updates all changed views and/or full-text indexes for all databases. ServerTasksAt2 ISpy RunJava ISpy Sends server and mail probes and stores the statistics. ServerTasks LDAP Server LDAP Enables a Domino server to provide LDAP directory services to LDAP clients. None MTC MTC Reads log files produced by the router and writes summary data about message traffic to a database for message tracking purposes. ServerTasks NNTP Server NNTP Enables a Domino server to act as a news server for NNTP clients. None Object store manager Object Performs maintenance activities on databases and mail files that use shared mail. ServerTasksAt2= Object Collect mailobj.nsf POP3 Server POP3 Enables a Domino server to act as a maildrop for POP3 clients. None Replicator Replica Replicates databases with other servers. ServerTasks Reporter Report Reports statistics for a server. None Router Router Routes mail to other servers. ServerTasks Schedule manager Sched Returns meeting times and dates and available invitees. ServerTasks Statistic Collector Collect Collects statistics for multiple servers. None Statistics Statlog Records database activity in the log file. ServerTasksAt5 Stats Stats Generates statistics for a remote server on demand. ServerTasks Web Retriever Web Implements the HTTP protocol to retrieve Web pages and convert them into Notes documents. None
- 49. 49 Questions?
- 50. 50
- 51. 51