Calendar Connector can route queries to partner systems. If the free and busy information does not exist on the partner system's server that Calendar Connector is connected to, the query must be routed to the other connected domains in the partner system. The term calendar domain refers to the connected network within which calendar queries can be processed in a given system. In Exchange, each calendar domain corresponds to an administrative group. In addition, each administrative group contains a unique set of free and busy information for that calendar domain. The servers you configure to transfer free and busy information from one calendar domain to another are called calendar bridgehead servers. The following sections describe how Calendar Connector works with diverse calendar domains.
Lotus Notes servers can route calendar queries to adjacent Lotus Notes domains. So the calendar domain refers to both the domain that hosts the bridgehead server as well as adjacent Lotus Notes domains.
Note Lotus Notes domains that are downstream from the domain that hosts the bridgehead server must have a Foreign Domain document that matches the bridgehead server domain. This allows Calendar Connector to connect to the Lotus Notes domain.
In smaller Lotus Notes networks, or in topologies in which all domains are adjacent to the connected domain, a single Calendar Connector with a direct connection to one Lotus Notes server may prove adequate for the entire network. However, free and busy querying is not supported for Lotus Notes domains that are not adjacent to the domain connected to the Calendar Connector.
Novell GroupWise servers can route calendar queries anywhere within the GroupWise network, so in this scenario the calendar domain refers to the entire GroupWise installation. You can have one calendar connection to a GroupWise installation per administrative group.If you want to connect to the same GroupWise domain from a different administrative group, you must install a second API Gateway in the domain and connect to it. This allows Exchange users from both administrative groups to obtain current free and busy information from GroupWise. However, queries from GroupWise to Exchange must all be made via one API Gateway per domain. This is because the link configuration in GroupWise sends all transactions to one gateway per external domain.
Note Both administrative groups use the same Exchange foreign domain name.
You can distribute the load of queries initiated by GroupWise by installing the other API Gateways in other GroupWise domains. Then you must adjust the link configuration of the other domains to direct all Exchange domain traffic to the local API Gateway.
Related TopicsUsing Multiple Administrative Groups Multiple Free and Busy Public Folder Replicas Implementation Scenarios