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

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 non-hybrid Office 365) 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:

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.

Step 3: Configure the Office 365 side

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

Configure an Autodiscover website for Coexistence Manager for GroupWise 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 Coexistence Manager for GroupWise website could be, for example, coexist.x.y. The Coexistence Manager for GroupWise website must also have a matching certificate. (To obtain and install a matching certificate, see 4.2: Obtain and install web services certificates.)
Run the O365 Add-AvailabilityAddressSpace cmdlet for the Coexistence Manager for GroupWise Autodiscover address ("coexist.x.y") configured in step 2 above.
In DNS, make sure the coexist domain has an A record pointing to Coexistence Manager for GroupWise.
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.

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

Step 4: Configure Coexistence Manager for GroupWise's FBC Web Server

To configure Coexistence Manager for GroupWise’s FBC Web Server:

Related Documents