 |
CalConn task does not return Free Time for adjacent domain in Hub-Spoke; Free Time is grayed out
|
| | | Problem | A customer has a Hub and Spoke Topology between two Lotus® Domino® domains (Domain A and Domain B). In this topology only the Hub servers (MailHub1/DomainA and MailHub2/DomainB) are cross certified to connect to each other to allow for mail routing or replication via a Server Connection record. The spoke servers, or mail servers do not have a Server Connection record to DomainB because the Hub server takes care of routing the mail and replication to the other domain.
In addition, the spoke servers may not have access to the other domain's Hub server. The Calendar Server field in the Adjacent Domain documents of each domain's Domino Directory references the Hub server of the other domain. So for Domain A, the Adjacent Domain document named DomainB states that the Calendar Server is MailHub2/DomainB.
When a user in Domain A tries to view the free time information of another user in Domain B, the free time information is grayed out. | | | | Solution | In the scenario above, the Calendar Connector (CalConn) task does not follow the same Connection documents that are used for mail routing or replication.
The Connection documents for mail routing and replication are used to control the flow of mail routing or replication from one server to another. CalConn uses the Calendar Server field in the Adjacent Domain document in the Domino Directory (Public Name & Address Book) to determine which server to connect to. The mail server's Calendar Connector will try to connect directly to the server that is listed as the Calendar Server in the Adjacent Domain document. The Calendar Connector does only one hop per server. Although DomainA's Adjacent Domain document named DomainB may state that MailHub2/DomainB is the Calendar Server, the connections for Free Time do not come from MailHub1/DomainA. The connections for Free Time come from Mail1/DomainA.
In the scenario above, Mail1/DomainA may not be able to find MailHub2/DomainB over the network because it cannot resolve MailHub2 to a valid network address or it is not authorized to access MailHub2/DomainB. Even though the Adjacent Domain document for Domain A lists the MailHub2/DomainB as the Calendar Server, CalConn will not connect to MailHub1/DomainA and then connect to MailHub2/DomainB.
In order for the mail servers to connect to the other domain, the following must happen:
1. The mail servers must be able to resolve the Calendar Server listed in the Adjacent Domain document by its network address (host name, ip address, etc.).
2. The mail servers must be cross certified with the Calendar Server listed in the Adjacent Domain document.
3. The mail servers must be allowed access to the Calendar Server listed in the Adjacent Domain document.
It is possible to configure the Domino Directories so that all the Mail servers in, for example, Domain A, talk to the Mail Hub in Domain A, and then route the request on.
Here is how:
1. Set the Calendar Server for Domain B to be "MailHub1/DomainA" in all Domino Directories in Domain A except for the one on MailHub1.
2. Set the Calendar Server for Domain B to be "MailHub2/DomainB" in the Domino Directory on MailHub1.
This will make all Mail servers in Domain A connect to MailHub1/DomainA when looking for busytime data for users in Domain B. MailHub1 will see the list belongs to Domain B, look up the Calendar Server for Domain B in its Domino Directory (MailHub2) and send the request there.
Repeat this configuration change in Domain B to allow servers in Domain B to get data from Domain A. Be sure that the Adjacent Domain documents in the Domino Directory on MailHub1 and the rest of the domain do not intermix so that all servers except the hub will try to use the hub; and the hub will be the sole server connecting to the hub in the other domain.
Note: The key is to not replicate the domain documents from the mail server and the hub server.
Workarounds:
- Cross certify and allow access each domain's Mail server with one adjacent domain's Mail server and list that adjacent domain mail server as the Calendar Server. This method still restricts the mail servers from accessing the adjacent domain's Hub server.
- Add another server on each domain. Cross certify the 2 additional servers by certifier. List the additional server in the adjacent domain as the Calendar Server in the Adjacent Domain document. This method alleviates cross certifying hundreds of mail servers with one server.
- Use a wildcard connection document from DomainA to the Calendar Server that is listed in the Adjacent Domain document.
- Cross certify and allow access each domain's Mail server with the adjacent domain's Hub server (not recommended).
Supporting Information:
Free Time lookup is a server to server process and only makes one connection per server. The Calendar Connector task is the server task that makes the connection for free time lookup. It makes a direct connection to the server that is listed in the Public Address Book/Domino Directory. When the Calendar Connector task makes a Free Time connection it will try to find the Domino server name and match it to a network address. When found, the requesting server needs to be able to access the destination server. This means cross certificates need to exist as well as Access Server is granted in the Server document.
| | | | | | | Cross Reference information | | Segment | Product | Component | Platform | Version | Edition | | Messaging Applications | Lotus Notes | Lotus Notes | Mac OS, Windows | 7.0, 6.5, 6.0, 5.0, 4.6, 4.5 | |
| Product Alias/Synonym | | Lotus Notes Client | | |
| | |
|
|
|
| IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. |
|
|
|
|
| Please take a moment to complete this form to help us better serve you. |
|
 |
|
|
|
|
|
|
| Product categories: |
|
| | Software | |
| | Messaging Applications | |
| | Advanced Messaging | |
| | Lotus Domino | |
| | Lotus Domino Server | |
|
| Operating system(s): |
| |
AIX, Linux, OS/400, Solaris, Windows, i5/OS, z/OS
|
|
| Software version: |
| |
4.5, 4.6, 5.0, 6.0, 6.5, 7.0
|
|
| Reference #: |
| |
1091658
|
|
| IBM Group: |
| | Software Group |
|
| Modified date: |
| | 2007-04-29 |
|
|
