Chat now with support
Chat mit Support

Coexistence Manager for Notes 3.8.4 - FBC Scenarios Guide

About the CMN Documentation Introduction On-premises Exchange or hybrid O365 using shared (single) namespace On-premises Exchange or hybrid O365 using separate namespaces Non-hybrid O365 using shared (single) namespace Non-hybrid O365 using separate namespaces Appendix: FBC Planning Worksheet Appendix: Troubleshooting the FBC

2-6: Add TCP/IP connection documents

In some environments, free/busy lookups may also require that you add TCP/IP Connection documents in both directions between the Domino servers housing mail databases (mailbox servers) and the Domino server running the QCalCon Domino Server Task.

* 
NOTE: This step may not be necessary if internal TCP/IP communications are already established in the environment. The bottom-line requirement is that the QCalCon server must be able to communicate with other servers.

To add TCP/IP connection documents: In Domino Admin, expand Configuration, expand Messaging and then click Connections. Add a connection, and then:

1
On the Basics tab:
•
Connection type: Local Area Network.
•
Source Server: name of the Domino server (in the Notes / Domino format, e.g. source_Notes_mail_database_server/DOMINODOMAIN).
•
Use the port(s): TCP/IP.
•
Usage priority: Normal.
•
Destination server: the Domino server hosting the QCalCon Domino Server Task (in the Notes / Domino format, e.g. target_Notes_QCalCon_server/DOMINODOMAIN).
•
Destination domain: DOMINODOMAIN of the server running the QCalCon Domino Server Task.
•
Optional network address: IP address of the destination server.
 
* 
IMPORTANT: Remember that a TCP/IP Connection document is required in both directions. The Basics tab settings must be reversed on the other TCP/IP Connection document to define a connection in the other direction. The net result of this configuration with a Domino mail database server and the QCalCon Domino Server Task running on a separate Domino server is that you will have two TCP/IP Connection documents, with one document pair for each Domino mail database server.
2
On the Replication/Routing tab:
•
Replication task: Disabled.
•
Routing task: Mail Routing.
•
Route at once if: 1 messages pending.
3
On the Schedule tab: Modify the settings on this tab to meet sending requirements (24 hours).
4
Click Save and Close.

Step 3: Configure the O365 side

To configure a non-hybrid Office 365 for CMN’s F/B Connector in a single/shared namespace environment:

1
In O365, configure an outbound send connector to point to CMN’s Mail Connector, to facilitate mail flow apart from free/busy.
2
Configure an Autodiscover website for CMN that is not Autodiscover.x.y—since that name is reserved for Outlook use. (In these examples, the "x.y" domain is the SMTP address to the right of the @ symbol.) The CMN website could be, for example, coexist.x.y. The CMN website must also have a matching certificate. (To obtain and install a matching certificate, see 4-2: Obtain and install web services certificates.)
3
Run the O365 Add-AvailabilityAddressSpace cmdlet for the CMN Autodiscover address ("coexist.x.y") configured in step 2 above.
4
In DNS, make sure the coexist domain has an A record pointing to CMN.
5
Test the configuration: Open a web browser and enter the URL ("https://coexist.x.y/autodiscover/autodiscover.xml") to verify that it resolves it correctly and without any certification errors.
To configure O365 for multiple subdomains

CMN’s Free/Busy Connector can facilitate the flow of free/busy information among multiple subdomains supported by both the Exchange and Domino servers. To support this scenario, run the Add-AvailabilityAddress­Space cmdlet on O365 for each Domino SMTP domain supported.

Step 4: Configure CMN's FBC Web Server

Step 4: Configure CMN’s FBC Web Server

To configure CMN’s FBC Web Server:

•
4-1: Physically install the CMN FBC components
•
4-2: Obtain and install web services certificates
•
4-3: Configure trusted sites for computers hosting F/B components
•
4-4 (optional): Configure logging for F/B components
•
4-5 (conditional): Configuring CMN’s FBC for Domino clusters
•
4-6: Run CMN’s Management Console to configure FBC components

4-1: Physically install the CMN FBC components

All CMN FBC components are installed by the AutoRun utility that accompanies the CMN product kit.

The AutoRun installer automatically checks the environment to verify CMN prerequisites, but you can bypass the prerequisites check by running the installer from the command line and appending ignoreprerequisites=1 to the command before executing.

For a typical configuration:

•
On the CMN FBC Web Server: Run AutoRun to install the Autodiscover, EWS and the Domino FBC Service on the CMN FBC Web Server.
•
On either the same CMN FBC Web Server or a separate CMN Exchange FBC Server: Run AutoRun to install the CMN Exchange FBC Service.
To configure CMN’s F/B Connector for multiple Domino servers

For Exchange queries for Domino F/B information, the simplest approach is to dedicate a separate CMN FBC server for each Domino server, with all the CMN servers feeding into the single Exchange server. It is technically possible, but somewhat more complicated, to configure a single instance of the Domino FBC Service, EWS and Autodiscover to process free/busy traffic to and from multiple Domino servers—an approach that requires more elaborate Domino configurations.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen