Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7 - FBC Configuration Guide

About the CMG Documentation Determine your FBC scenario FBC Scenario #1 FBC Scenario #2 FBC Scenario #3 FBC Scenario #4 FBC Scenario #5 FBC Scenario #6 FBC Scenario #7 FBC Scenario #8 FBC Scenario #9 FBC Scenario #10 FBC Scenario #11 FBC Scenario #12 Appendix: FBC Planning Worksheet Appendix: Configuring and troubleshooting the FBC with PowerShell Appendix: Troubleshooting the FBC

5.2: Configure Exchange server connections

Configure and verify the link from the Exchange server to the domains/subdomains supported by the GroupWise server. This procedure tests whether the certificate on the CMG Web Server is trusted by the Exchange server.

Add-AvailabilityAddressSpace -ForestName <smtpdomain> -AccessMethod OrgWideFB
... where <smtpdomain> is the name of the GroupWise domain.
2
Open a web browser and enter the URL http://autodiscover.<domain>/autodiscover/autodiscover.xml to ensure that the Exchange server resolves it to the CMG FBC EWS without any certification errors.
1
Click the SSL button in the Web browser, then click View Certificates.
2
4
Click Import, then Finish.

If you requested a certificate from a public CA, the certificate is already trusted by Exchange.

For F/B coexistence with an Exchange 2013 in a single-namespace environment: On all servers running a mailbox role, modify the hostfile to add the IP address and host name of the CMG Autodiscover.

To enable shared SMTP namespace F/B lookups in the Exchange-to-GroupWise direction, add the CMG F/B Web Services IP address to the host file on the Exchange CAS server.

5.3: Configure DNS

You can use Network Load Balancing to permit multiple web servers to handle Autodiscover requests. This is optional, not required to deploy CMG. For more information, see

this Microsoft article.

Configure DNS to point autodiscover.<smtpdomain.com> to the computer where CMG’s Autodiscover service is installed. For each domain, Exchange connects to predefined Autodiscover URLs using DNS host entries.

For Exchange to get free/busy information from the domain supported by a GroupWise server, through the CMG Free/Busy Connector, you must make the CMG Autodiscover Web Service resolvable to this URL:

FBC Scenario #3

This procedure begins with the assumption that you have already reviewed the introductory chapter of this FBC Configuration Guide to Determine your FBC scenario. This chapter explains how to configure the FBC and the coexisting environments for F/B scenario #3, specified above.

Follow these steps, in order as presented here, to install and configure CMG’s F/B Connector for scenario #3:

Step 1: Plan your FBC installation and configuration

Review the System Requirements (in the CMG Release Notes), and verify either that your environment conforms to the requirements, or that you will have the necessary hardware and software to meet the requirements.

Scan through the installation and configuration procedures in this chapter, and think through what this process will entail in your own environment, to accommodate your own needs and preferences. Identify any special circumstances or issues, and determine how these will be addressed.

Then sketch out a configuration map to show which FBC components will reside on which computers, and how they will connect to the GroupWise and Exchange environments.

For any given scenario and configuration, it is possible to install all CMG F/B Connector components on a single server, as shown in the illustrations in the introductory chapter (Determine your FBC scenario) of this Guide. However, many production environments experience sufficient query volume to warrant separate servers to ensure optimal performance. The instructions here therefore describe how to install CMG’s F/B Connector on two servers. If you prefer that all subcomponents reside on a single server, simply combine the components of CMG Server 1 and CMG Server 2 as they are listed below.

The typical deployment of FBC components to two computers for this scenario (GW 7 or later via API Gateway, and connections to Outlook 2003 via Exchange public folders) depends on how the public folders will connect to the CMG components for GroupWise queries to Exchange. With Exchange 2003, that half of the process must be routed through CMG’s Public Folder Reader Service, and the typical deployment is:

With Exchange 2007, GroupWise queries to Exchange may be routed through CMG’s Public Folder Reader Service, by the same deployment as shown above, or may instead be routed through Microsoft’s Autodiscover and EWS. In the latter case, the typical deployment for CMG Server 2 is the same as shown above, but CMG Server 1 (for GroupWise queries to Exchange, and Exchange replies) contains:

For Exchange queries for GroupWise F/B information, the simplest approach is to dedicate a separate CMG FBC Server 2 (as listed just above, for Exchange queries to GroupWise, and GroupWise replies) for each GroupWise server, with all the CMG servers feeding into the single Exchange server.

It is technically possible, but somewhat more complicated, to configure a single instance of the GroupWise FBC Service, EWS and Autodiscover to process free/busy traffic to and from multiple GroupWise servers—an approach that requires more elaborate GroupWise configurations.

Use the worksheet in Appendix A of this FBC Configuration Guide to gather and organize the information you will need to enter into CMG’s Management Console application when configuring the Free/Busy Connector. You can print the worksheet to paper, and use a pen or pencil to write the information into the wide right margins.

The actual data-entry work will occur later in this procedure, in step 4.

Related Documents