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

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.

Step 3: Configure the Exchange side

Configure domains, permissions and other server parameters and attributes so they will be able to work with CMG’s Free/Busy Connector.

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-AvailabilityAddress­Space 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.

Step 4: Configure CMG's FBC Web Server

To configure CMG’s FBC Web Server:

4.1: Physically install the CMG FBC components

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 installation 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 in step 1 above. All CMG Free/Busy Connector subcomponents are installed by the AutoRun utility included in the CMG product kit.

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

IMPORTANT: Before you install, on any computer that will host any CMG 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. CMG requires a dedicated server for its own web subcomponents.

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

IMPORTANT: Remember, the CMG 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.
NOTE: CMG’s Public Folder Writer Service and Public Folder Reader Service are available only via the Custom Setup option of CMG’s F/B Connector Setup utility.
NOTE: If you are configuring F/B for Exchange 2003: Exchange 2003 does not support CMG's F/B Bridge subcomponent or PowerShell. The AutoRun installer installs these subcomponents anyway, because it doesn't know how you intend to configure your F/B services, but the CMG F/B Bridge and PowerShell will not be used in your configuration.

Remember: For Exchange queries for GroupWise F/B information, the simplest approach is to dedicate a separate CMG FBC Server 2 (as noted in step 1 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.

Related Documents