As an administrator, you can define holidays that areparticular to your organization or country.HCLDomino® includesa set of default Holiday documents, which you can modify. Users importthis information directly into their personal calendars.

Thecalendar and scheduling features use the Schedule Manager (Sched task),the Calendar Connector (Calconn task), and the Free Time system (acombination of Sched, Calconn, and nnotes tasks) to operate. Whenyou installDomino® on a server(any server except a directory server), the Sched and Calconn tasksare automatically added to the server'sNOTES.INI file.When you start the server for the first time, the Schedule Managercreates a Free Time database (BUSYTIME.NSF fornon-clustered mail servers andCLUBUSY.NSF forclustered mail servers) and creates an entry in the database for eachuser who has filled out a Calendar Profile and whose mail file ison that server or on one of the clustered servers.

Each usercan keep a personal calendar and create a Calendar Profile that identifieswho may access the user's free time information and specifies whenthe user is available for meetings. When users invite other usersto meetings, the Free Time system performs the free-time lookups.The Free Time system also searches for and returns information onthe availability of resources. If the lookup involves searching inFree Time systems on different servers or scheduling applications,the Calendar Connector sends out the queries. When users scheduleappointments in their calendars and reserve resources, the ScheduleManager task collects and updates that information in the Free Timedatabase.

By default, the Schedule Manager has access to theFree Time database, so you do not have to define the ACL for thisdatabase.

Usingclustered scheduling

For clustered mail servers, the ScheduleManager creates the clustered Free Time database (CLUBUSY.NSF)the first time a server starts. The clustered version of the FreeTime database works the same as the Free Time database (BUSYTIME.NSF).Each clustered server has a replica of the clustered Free Time database,which stores information about users whose mail files exist on serversin the cluster.

If you add a previously non-clustered serverto a cluster, the Schedule Manager deletes theBUSYTIME.NSF databaseon that server and createsCLUBUSY.NSF, whichthen replicates to all cluster members. If you remove a server froma cluster, the opposite occurs: Schedule Manager deletesCLUBUSY.NSF andcreatesBUSYTIME.NSF. Until the Schedule Managervalidates the database by checking to see if the location of users'mail files has changed, the clustered Free Time database containsinformation about users whose mail server you removed from the cluster.This validation also occurs once each day (at 2 AM) to update free-timeinformation for users whose mail files have been added to or removedfrom a mail server. You can update the information at any time byentering theTell Sched Validate command at theconsole.

A benefit of clustered scheduling is that scheduleinformation is always available, even when a user's home server isdown. With non-clustered scheduling, if a home server is not available,its users are unable to access the Free Time database for searching.

Other advantages of using clustered scheduling includeimproved performance and reduced server traffic. Because the FreeTime database is available from other members in a cluster, the serverthat receives a user's query does not have to search another server'sFree Time database for schedule information about a user whose mailserver is in the cluster.

Schedulinga meeting

This section describes the process of schedulinga meeting when users share the same mail server and domain, have differentdomains, and use different scheduling applications.

In the followingexamples, Kathy wants to check the free time of and schedule a meetingwith three users -- Bob, who is in the same domain as Kathy; Robin,who is in a different domain; and Susan, who uses a different schedulingapplication.

Usersin the same domain

1. Kathy creates a meeting invitation and chooses to search for Bob'sfree time.
2. A free time query is sent to Kathy's mail server.
3. The Free Time system looks for Bob's name in the Free Time database(BUSYTIME.NSF orCLUBUSY.NSF)on Kathy's mail server.
   • If Bob and Kathy have the same mail server or if Bob's and Kathy'smail servers are part of a cluster, the Free Time system finds theinformation and returns Bob's free time to Kathy.
   • If the Free Time system does not find any information on Bob,it converts Bob's name into a fully qualified name.
   • If Bob's mail server is unavailable and his Free Time databaseis not clustered, a message appears indicating that the server isunavailable, and the Find Time dialog box indicates that Bob's informationis unavailable.
4. Kathy'sDomino® Directoryis checked for Bob's Person document. When the Person document isfound, the Calendar Connector sends the request to Bob's mail server,the name of which is listed in Bob's Person document.
5. The Free Time system on Bob's mail server looks in its Free Timedatabase and returns the information to Kathy via the Calendar Connector.If the Free Time system doesn't find any information, the query fails,and the Find Time dialog box indicates that Bob's information is unavailable.

Usersin different domains

1. Kathy creates a meeting invitation and chooses to search for Robin'sfree time. In addressing the invitation, Kathy specifies Robin's domain.
2. A query is sent to Kathy's mail server.
3. The Free Time system looks for Robin's name in the Free Time databaseon Kathy's mail server. It determines Robin's mail server is in adifferent domain.
4. Kathy'sDomino® Directoryis searched for a document that matches Robin's domain.
   • If the Free Time system finds an Adjacent Domain document, itlooks at the Calendar server name field of the document for the nameof a server that accepts calendar queries for Robin's domain. TheFree Time system then forwards the query to this server for processing.
   • If the Free Time system finds an Adjacent Domain document withan empty Calendar server name field, it fails; and the Find Time dialogbox indicates that Robin's information is unavailable.
   • If the Free Time system finds a Non-adjacent Domain document,it looks at theRoute requests through Calendar server fieldof the document for the name of the server (which is in a domain adjacentto Kathy's and Robin's) that accepts calendar queries for Robin'sdomain. The Free Time system then forwards the query to this serverfor processing.
   • If the Free Time system finds a Non-adjacent Domain document withan emptyRoute requests through Calendar server field,it fails; and the Find Time dialog box indicates that Robin's informationis unavailable.
   • If the Free Time system doesn't find any domain documents, thequery fails; and the Find Time dialog box indicates that Robin's informationis unavailable.

Usersin other calendar domains

1. Kathy creates a meeting invitation and chooses to search for Susan'sfree time.
2. A query is sent to Kathy's mail server.
3. The Free Time system looks for Susan's name in its Free Time database.It does not find the information, so it converts Susan's name intoa fully qualified one.
4. Kathy'sDomino® Directoryis searched for Susan's Person document.
5. The Free Time system looks in Susan's Person document and locatesthe name of her mail server in the Mail server field and the nameof her calendar domain in the Calendar Domain field.
6. Because Susan is using Organizer as her scheduling application,the Free Time system finds that her calendar domain does not matchher mail server domain. The Free Time system then looks for a Domaindocument for the calendar domain.
7. The Free Time system finds a Foreign Domain document for Susan's calendar domain. The Calendarserver field in the Foreign Domain document identifies the name of the server that accepts queriesfor Susan's domain; theCalendar system field identifies the name of theadd-in program that actually does the free-time lookup on Susan's server. The Free Time systemforwards the query to the appropriate server (the server listed in the Calendar server field) forprocessing.

If the Free Time system doesn't find a Foreign Domain document,the query fails; and the Find Time dialog box indicates that Susan'sinformation is unavailable.