2. Availability determines that Free/Busy information for this attendee will be in a Public Folder so it queries exchange mailbox servers public folder.

3. Public Folder store sends a ‘notification’ to the ‘Calendar Connector’, and locks the record on using the Transporter Suite tool. Also you can find the CalCon logs into the Public Folders and requests this notification.

5. If the attendee is local to this server, the Domino Server checks in BUSYTIME.NSF (or CLUBUSY.NSF if on a cluster) for a record. Also records are placed in these databases by the Schedule Add-in Task.

6. If data is present for a local attendee it will be returned to the server, otherwise a ‘Not Found’ error is returned to the server. Skip to step 13.

7. If the attendee is not local to this server, the request is passed to the Calendar Connector Add-in Task on the Domino Server. Also the request is routed to the NOTESSCHEDGATEWAY message queue.

8. The Calendar Connector looks in the Name and Address book (or Directory Assistance database) to determine the appropriate server to route the request to. Also the request is sent the same as a Notes client.

9. The remote server follows a similar pattern from step 5. to fetch the Free/Busy data, which will be returned to the Calendar Connector task, otherwise a ‘Not Found’ error is returned.

10. The Calendar Connector task then passes this back to the Notes server process.

11. Free/Busy data is returned via the Notes API to the Calendar Connector Service.

12. The Free/Busy message for the attendee is updated in the Schedule+ Free/Busy Public Folder, and the lock on the record is cleared.

13. Free/Busy data is returned to the Availability Service.

14. Free/Busy data is returned to Outlook 2007 to render

Hope it was informative and possibly the next blog will be on how then Notes client query the free/busy information the Microsoft Exchange mailbox using the Transporter suite tool.