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 2: Configure the GroupWise side

GroupWise versions 8 and later can connect to Coexistence Manager for GroupWise's Free/Busy Connector via a F/B Internet URL.

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.

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.

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 separate/multiple namespace environment:

1
In DNS, make sure the coexist domain has an A record pointing to Coexistence Manager for GroupWise.
2
Configure an Autodiscover website for Coexistence Manager for GroupWise (for example, Autodiscover.x.y, where the "x.y" domain is the SMTP address to the right of the @ symbol). 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.)
3
Run the O365 Add-AvailabilityAddressSpace cmdlet for the Coexistence Manager for GroupWise Autodiscover address.
4
Test the configuration: Open a web browser and enter the URL ("https://Autodiscover.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:

4.1: Physically install the Coexistence Manager for GroupWise FBC components

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 installation instructions here therefore describe how to install Coexistence Manager for GroupWise’s F/B Connector on two servers.

See the configuration map you made in step 1 above to determine which components should be installed to which servers for this scenario.

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 in step 1 above. All Coexistence Manager for GroupWise Free/BusyConnector subcomponents are installed by the AutoRun utility included in the Coexistence Manager for GroupWise product kit.

IMPORTANT: Before you install, on any computer that will host any Coexistence Manager for GroupWise FBC web subcomponent, remove the IIS DefaultWebSite: In the navigation tree at left, right-click DefaultWebSite, and then select Remove from the pop-up menu. Coexistence Manager for GroupWise requires a dedicated server for its own web subcomponents.

Use the AutoRun utility now to install all the necessary Coexistence Manager for GroupWise F/B Connector subcomponents on the computer(s) where you want them installed.

IMPORTANT: Remember, the Coexistence Manager for GroupWise AutoRun installer must be run on the computer where you want to install a particular subcomponent. If you are deploying the F/B Connector to two different computers, you must run the AutoRun installer twice—once on each computer.

Remember: 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 in step 1 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.

Related Documents