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.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.<> 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 #2

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 #2, specified above.

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

Remember that the FBC for a hybrid O365 is configured only between GroupWise and the local on-premises Exchange, while synchronization of the local Exchange to O365 is a connection apart from CMG and documented separately by Microsoft. Configuring CMG’s FBC for a hybrid O365 is therefore the same as configuring for a local on-premises Exchange.

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. 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 7 or later via API Gateway, with Exchange 2007 or later and Outlook 2007 or later) is:

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.

Step 2: Configure the GroupWise side

Free/busy coexistence with GroupWise 7 requires the GroupWise API Gateway, GroupWise Proxy GWIA, and the GroupWise SOAP web service, as described in the subtopics below.

The API Gateway is also supported (though not recommended) for GroupWise 8 and later. GroupWise 8 admins may choose between the router/postoffice configuration and the original shared-address-book configuration.

A later step of this FBC configuration procedure describes how to configure and test connections among CMG FBC components and the GroupWise and Exchange environments.

These components must be installed to support the newer router/postoffice configuration option, required for connection to GroupWise 7. This configuration requires:

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 this Novell article, and this one too.

FBC coexistence with GroupWise version 7 requires a proxy GWIA. In ConsoleOne:

Manually create an empty gateway folder called GWIAFB (e.g., ..\WPGATE\GWIAFB).
Copy the entire GWIA folder (the “real” GWIA) to a new proxy GWIA directory, and then delete the \wpcsout\gwiaXXXX subfolder (where XXXX is the gateway unique ID), and delete the \wpcsin subfolder. Do not start/enable the proxy GWIA, since the FBC must process the files in the proxy GWIA folders.
Account rights with a minimum of Read, Write and Delete rights for all folders in the proxy GWIA. These rights may vary depending on the OS to which the proxy GWIA is installed. For example, the equivalent rights on Netware are Read, Write, Create, Modify, Erase and Filescan [RWCEMF].
Create a GroupWise Internet Agent called GWIAFB, and point it to the GWIAFB directory that was just created. (This new GroupWise Internet Agent will need to have a Gateway Type of Internet Agent.)
Change the API agent Idle Sleep Duration to 5 seconds.
Reconfigure the GW domain to use GWIAFB as the default. To do this: Select the Non-GroupWise domain in ConsoleOne and then, on the Tools menu: Select GroupWise System Options | Internet Addressing to open the Internet Addressing dialog box. Then select GWIAFB from the Internet Agent for outbound SMTP/MIME messages drop-down list. Click OK to save the changes.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating