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.
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 () 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. All CMG Free/Busy Connector subcomponents are installed by the AutoRun utility included in the CMG product kit, as described in a later step in this chapter.
The typical deployment of FBC components to two computers for this scenario (GW 8 or later via F/B URL, 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 noted 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.
FBC coexistence with any supported GroupWise version requires the GroupWise SOAP web service, enabled on the GroupWise Post Office where the CMG service account resides. To enable and configure SOAP, see , and too.
CMG’s Free/Busy Connector can facilitate the flow of free/busy information among multiple subdomains supported by both the Exchange and GroupWise servers. To support this scenario, run the Add-AvailabilityAddressSpace cmdlet on the Exchange server for each GroupWise SMTP domain supported.
In these scenarios, Exchange queries for GroupWise F/B data (see the right halves of the CMG servers in the diagrams below) are not sent to GroupWise, but rather are routed internally to Exchange’s own public folders, which CMG regularly refreshes by its CMG Public Folder Writer Service. For GroupWise queries to Exchange, however, CMG supports two options (described in the next two subtopics below):
For either Exchange 2003 or 2007, GroupWise queries for Exchange F/B data (the left halves of the CMG servers in the diagrams below) can pass through CMG’s Public Folder Reader Service. The Public Folder Reader Service relays GroupWise F/B queries to Exchange public folders, and then relays the F/B info back to GroupWise.
Outlook users’ queries for GroupWise F/B info (the right halves of the CMG servers in these diagrams) are routed directly to Exchange public folders (internally within the Exchange environment). The public folders reply by transmitting their F/B info directly to the Outlook users. No CMG components are used for that query-reply portion of the F/B process. But the Exchange public folders must regularly be refreshed with GroupWise users’ current F/B info, and that function is performed by CMG’s Public Folder Writer Service.
CMG’s Public Folder Writer Service collects GroupWise users’ current F/B info from GroupWise to refresh the Exchange public folders, and also communicates with Active Directory to get and maintain a current list of GroupWise contacts in the Exchange system.
CMG can connect to Exchange 2007 public folders either via its Public Folder Reader Service (as described above), or via Microsoft’s Autodiscover and EWS, as described here and illustrated in the diagram below. Connecting via the Microsoft services is not an option with Exchange 2003.
This configuration uses CMG’s Exchange Free/Busy Connector Service to relay GroupWise F/B queries to Microsoft’s Autodiscover and EWS on the Exchange server, and relay the F/B info back from MS Autodiscover and EWS to GroupWise. (Microsoft’s Autodiscover and EWS in turn relay GroupWise F/B queries to Exchange public folders, and receive the public folders’ F/B info.)
CMG uses its Public Folder Writer Service to get GroupWise users’ current F/B info from GroupWise and, at regular intervals, to refresh the corresponding F/B info held in the Exchange public folders. The Public Folder Writer Service also communicates with Active Directory to get and maintain a current list of GroupWise contacts in the Exchange system. Outlook users’ queries for GroupWise F/B info are routed directly to Exchange public folders (internally within the Exchange environment), while the public folders transmit the F/B info directly to the Outlook users.