Chat now with support
Chat with Support

Integration for Notes 20.13 - User Guide - FreeBusy

Section 1. Introduction Section 2. Scope Section 3. Recommended Installer Prerequisites Section 4. Pre-installation Requirements Section 5. Configure the Domino environment Section 6. Configure Integration for Notes FreeBusy in Exchange or Office 365 Section 7. Install FreeBusy On the Domino Coex Server Section 8. Create and Configure the Domino Databases Section 9. Modify the Notes.ini File Section 10. Start FreeBusy on Domino Coex Server Section 11. Install FreeBusy for Windows Section 12. Verification Section 13. Ongoing Administration Appendix A. Adding a Root Trusted Signed Certificate to the FreeBusy Operating System(s) Appendix B. SetFBCred Utility Appendix C: Enable Modern Authentication Appendix D. Notes.ini File Parameters

1.4 Coexistence Environment

1.4    Coexistence Environment

A coexistence environment consists of three servers, which are specifically configured so that Integration for Notes can be utilized optimally. These servers are:

  1. Domino Coexistence Server

  2. Windows Coexistence Server (for Free/Busy only)

  3. SQL Coexistence Server (for Directory Sync Pro)

     

    In the illustration above, one of the components is the Domino Coexistence Server, which is responsible for supporting coexistence server tasks at the Domino end of the environment. These server tasks include:

  1. Messaging/calendaring/application coexistence

  2. Free/Busy lookup

    The Windows Coexistence Server, on the other hand, is designed to support coexistence on the Exchange side with Free/Busy lookup.

The SQL Coexistence Server can be a dedicated or shared SQL Server (in the middle of the illustration) and contains a dedicated transitional SQL database, which is utilized for directory synchronization between Domino and Exchange.

Messaging

The coexistence environment is configured to enable mail flow between Domino and Exchange. It is also configured to determine how the e-mail addressing will be handled between the two platforms. Similarly, the system is configured such that there is transitional calendar workflow between Domino users and Exchange users to enable them to schedule/update/reschedule/cancel single occurrences and recurring meetings irrespective of their migration status.

For migrated items with Migrator for Notes, this will not be true until a full post-migration workflow has been implemented. 

Directory Synchronization Using Directory Sync Pro

Directory Synchronization is accomplished by reading data from source directories, Active Directory and the Domino Directory, and writing it into an SQL database. In turn, information in SQL is written into target directories, Active Directory and the Domino Directory. The SQL database allows for the customization of data from one directory to another directory. Some of the basic mapping is already completed; however, there are several changes that must be made to accommodate environments ranging from the small business to enterprise deployments. The Domino BTDirSync task handles all the interaction with SQL for reading and writing to Domino. The Windows BTDirSync (full name BinaryTree.Coexistence.DirSync.Exchange.exe) service handles the reading and writing to Active Directory. The Client UI component is used to configure the base settings for connectivity.

Free/Busy

The way a Domino environment implements its calendar Free/Busy queries is different from the way Exchange does. One environment cannot see the availability of users in the other environment. Integration for Notes FreeBusy is designed to enable reliable Free/Busy schedule lookups between Microsoft Exchange and Lotus Domino users by providing the proper address resolution. In other words, to make the two environments communicate with each other, Integration for Notes configures the system such that one environment can determine the Free/Busy status of users within the other environment.

The Binary Tree FreeBusy application is designed to allow for calendar scheduling look ups for meeting bookings. It does not allow for direct calendar access between Notes and Outlook.

 

 

Section 2. Scope

Before installing FreeBusy, it is important to know what specific functionality is covered in this document and what is not. For items not included in this document but covered elsewhere, references to the appropriate documentation are provided in the Out of Scope section.

Section 2. Scope

1.4    Coexistence Environment

A coexistence environment consists of three servers, which are specifically configured so that Integration for Notes can be utilized optimally. These servers are:

  1. Domino Coexistence Server

  2. Windows Coexistence Server (for Free/Busy only)

  3. SQL Coexistence Server (for Directory Sync Pro)

     

    In the illustration above, one of the components is the Domino Coexistence Server, which is responsible for supporting coexistence server tasks at the Domino end of the environment. These server tasks include:

  1. Messaging/calendaring/application coexistence

  2. Free/Busy lookup

    The Windows Coexistence Server, on the other hand, is designed to support coexistence on the Exchange side with Free/Busy lookup.

The SQL Coexistence Server can be a dedicated or shared SQL Server (in the middle of the illustration) and contains a dedicated transitional SQL database, which is utilized for directory synchronization between Domino and Exchange.

Messaging

The coexistence environment is configured to enable mail flow between Domino and Exchange. It is also configured to determine how the e-mail addressing will be handled between the two platforms. Similarly, the system is configured such that there is transitional calendar workflow between Domino users and Exchange users to enable them to schedule/update/reschedule/cancel single occurrences and recurring meetings irrespective of their migration status.

For migrated items with Migrator for Notes, this will not be true until a full post-migration workflow has been implemented. 

Directory Synchronization Using Directory Sync Pro

Directory Synchronization is accomplished by reading data from source directories, Active Directory and the Domino Directory, and writing it into an SQL database. In turn, information in SQL is written into target directories, Active Directory and the Domino Directory. The SQL database allows for the customization of data from one directory to another directory. Some of the basic mapping is already completed; however, there are several changes that must be made to accommodate environments ranging from the small business to enterprise deployments. The Domino BTDirSync task handles all the interaction with SQL for reading and writing to Domino. The Windows BTDirSync (full name BinaryTree.Coexistence.DirSync.Exchange.exe) service handles the reading and writing to Active Directory. The Client UI component is used to configure the base settings for connectivity.

Free/Busy

The way a Domino environment implements its calendar Free/Busy queries is different from the way Exchange does. One environment cannot see the availability of users in the other environment. Integration for Notes FreeBusy is designed to enable reliable Free/Busy schedule lookups between Microsoft Exchange and Lotus Domino users by providing the proper address resolution. In other words, to make the two environments communicate with each other, Integration for Notes configures the system such that one environment can determine the Free/Busy status of users within the other environment.

The Binary Tree FreeBusy application is designed to allow for calendar scheduling look ups for meeting bookings. It does not allow for direct calendar access between Notes and Outlook.

 

 

Section 2. Scope

Before installing FreeBusy, it is important to know what specific functionality is covered in this document and what is not. For items not included in this document but covered elsewhere, references to the appropriate documentation are provided in the Out of Scope section.

2.1 In Scope

2.1    In Scope

This document covers the installation of a single FreeBusy pair.  The following topics are also covered:

Configuration of the Domino and Exchange/Office 365 infrastructure to support FreeBusy

2.2 Out of Scope

2.2    Out of Scope

This document does not cover the items listed below. If documentation exists elsewhere, the corresponding references are provided.

DirSync configuration (see DirSync user guide)

Active Directory (AD) schema changes

Project methodology

Creation of an Office 365 tenant and security model

Proxies and firewall changes

Network Load Balancers

Section 3. Recommended Installer Prerequisites

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating