Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7.1 - FBC Configuration Guide

About the Coexistence Manager for GroupWise 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

FBC Scenario #1

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

Follow these steps, in order as presented here, to install and configure Coexistence Manager for GroupWise’s F/B Connector for scenario #1:

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 Coexistence Manager for GroupWise and documented separately by Microsoft. Configuring Coexistence Manager for GroupWise’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 Coexistence Manager for GroupWise 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 Coexistence Manager for GroupWise 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 Coexistence Manager for GroupWise’s F/B Connector on two servers. If you prefer that all subcomponents reside on a single server, simply combine the components of Coexistence Manager for GroupWise Server 1 and Coexistence Manager for GroupWise Server 2 as they are listed below. All Coexistence Manager for GroupWise Free/Busy Connector subcomponents are installed by the AutoRun utility included in the Coexistence Manager for GroupWise 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 Coexistence Manager for GroupWise FBC Server 2 (as noted just above, for Exchange queries to GroupWise, and GroupWise replies) for each GroupWise server, with all the Coexistence Manager for GroupWise 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 Coexistence Manager for GroupWise’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 Coexistence Manager for GroupWise 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 Coexistence Manager for GroupWise 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:

1
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].
2
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.)
4
Change the API agent Idle Sleep Duration to 5 seconds.
5
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.

Step 3: Configure the Exchange side

Other than an accommodation for multiple subdomains (see next subtopic below), no additional Exchange configuration is necessary for the FBC to work with an Exchange environment whose Outlook clients are all version 2007 or later, and where Exchange will connect with the FBC by Microsoft’s Autodiscover and EWS (without Exchange public folders). This Exchange-side scenario is illustrated here:

If you are configuring FBC for a hybrid Office 365: 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 configured apart from Coexistence Manager for GroupWise (and documented separately by Microsoft). Configuration of Coexistence Manager for GroupWise’s FBC for a hybrid O365 is therefore the same as configuring for a local on-premises Exchange—as described here.

Coexistence Manager for GroupWise’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-AvailabilityAddress­Space cmdlet on the Exchange server or Office 365 for each GroupWise SMTP domain supported.

Related Documents