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

GroupWise Coexistence Manager for GroupWise Router | Coexistence Manager for GroupWise Router Service

| Coexistence Manager for GroupWise Router Service

This information applies only if you are connecting to GroupWise 7, or if you have GroupWise 8 and will connect to CMG via the API Gateway (which requires the Coexistence Manager for GroupWise Router).

The first fields in the Management Console screen specify the folders where the Coexistence Manager for GroupWise Router will send or look for various items for its routing functions. In Coexistence Manager for GroupWise’s Management Console you can use Browse buttons to find and select directories.

Novell Account: Novell account login user name.
Password: Password associated with the Novell Account cited above.
Check For New Requests Every ____ Seconds: Polling frequency for F/B queries. The interval (in seconds) the Router will wait between successive checks to see if there is a new query to process.
Request Retry Duration: Number of minutes the Coexistence Manager for GroupWise Router Service will continue trying to move a file (message), if preceding attempt(s) have failed. The service repeats such attempts at intervals specified by the Check For New Requests value above, until successful or until the Request Retry Duration is reached.
Update Performance Counters Every ____ Seconds: Update frequency for the F/B performance counters that feed Windows’ System Monitor feature.
Enable Performance Counters: A checkbox to indicate whether you want the F/B Connector performance counters to run.

Exchange F/B Connector | Bridge

| Bridge

This information applies only for an Exchange-to-GroupWise connector, and only if you are connecting to GroupWise 8 and have chosen the original, shared-address-book configuration. Coexistence Manager for GroupWise uses this information to configure its Bridge web service, for GroupWise queries for Exchange F/B information.

Requests Directory: Specify the folder where F/B requests will be held. In Coexistence Manager for GroupWise’s Management Console you can use a Browse button to find and select a directory.

Results Directory: Specify the folder where F/B results will be held. In Coexistence Manager for GroupWise’s Management Console you can use a Browse button to find and select a directory.

Check For New Requests Every ____ Seconds: Polling frequency. How long the Bridge will wait between successive checks to see if there is a new F/B query to process.

Time Zone for GroupWise API Gateway server: In Coexistence Manager for GroupWise’s Management Console you can use a drop-down list box to select the correct time zone.

Quest Exchange Free/Busy Connector Host Name is prefilled by Coexistence Manager for GroupWise with localhost—the appropriate value for a typical Coexistence Manager for GroupWise configuration. In a typical configuration, the Coexistence Manager for GroupWise Bridge is installed on the same computer as the Coexistence Manager for GroupWise Exchange Free/Busy Connector service, so the generic relative value localhost will suffice in this context. If the Coexistence Manager for GroupWise Bridge is installed on a different computer, then enter the correct Host Name here.

Exchange F/B Connector | Exchange Free/Busy

| Exchange Free/Busy

This information is necessary to configure Coexistence Manager for GroupWise’s Exchange F/B Connector service, for GroupWise queries for Exchange F/B information.

Exchange Server Location: How should F/B queries be routed to the coexisting Exchange environment? By EWS Endpoint, by Autodiscover Endpoint, or by Autodiscover Only?

All queries for Exchange users' F/B information must pass through an Exchange EWS, which facilitates communications between Exchange and the Coexistence Manager for GroupWise Exchange FBC service. In an Exchange environment with a single EWS at a known fixed location (URL), you can point the FBC service directly to the EWS by specifying the EWS URL and host name. If there is no single Exchange EWS with a known fixed location, the FBC service can query the Exchange Autodiscover service, which tracks and reports the current location of an available EWS.

If you will coexist with an Exchange environment where you don't know the location of either the EWS or the Autodiscover endpoint, the Coexistence Manager for GroupWise FBC service will have to search the network for the connection it needs.

Specify your choice by selecting one of these methods:

EWS Endpoint: Select this option if you have an on-premises Exchange with a single Exchange EWS whose location (URL) is fixed relative to Coexistence Manager for GroupWise’s Exchange FBC service. This approach typically yields the best performance of the three options, but is the least flexible since the connection will fail if the Exchange EWS is not at the specified URL. If you select this option, you must also specify:
Exchange EWS Host Name: Name of the Exchange server where EWS requests should be sent.
EWS URL: Location of Microsoft EWS web service on the Exchange server.
Autodiscover Endpoint: Select this option if you have an on-premises Exchange environment with multiple Exchange EWS endpoints (for example, in a load-balanced environment) and you have an Exchange Autodiscover service that can determine which EWS endpoint to use. This can also be the best choice if you want to coexist with Microsoft's hosted Office 365 (see the Office 365 notes below). Performance will be slower than if you direct the FBC service to a fixed-location EWS (above), but will still be faster than if neither the EWS nor the Autodiscover value is specified (below). For this option, you must also specify:
Exchange Autodiscover URL: Location of the Autodiscover service on the Exchange server (or, for Office 365, of Microsoft's Autodiscover URL, as noted below).
 
NOTE: If coexisting with Microsoft’s Office 365: Select the Autodiscover Endpoint option and set the Exchange Autodiscover URL to Microsoft’s Autodiscover URL:

Note, however, that this is a Microsoft URL that is subject to change, in which case this connection would fail and the Free/Busy Connector would fail. Remember this if you set the Exchange Autodiscover URL to the Microsoft URL, and Coexistence Manager for GroupWise’s F/B Connector works fine for a time but then suddenly and consistently fails. The most likely cause is a change in Microsoft’s Autodiscover URL. Contact Microsoft to get the new URL, or select the Autodiscover Only option (below) instead.

Autodiscover Only: Select this option if you will coexist with an Exchange environment where you don't know the location of either the EWS or Autodiscover. In this case, the FBC service will search the network for the connection it needs, so this is the most flexible option, but it is also much slower than either alternative above.

Regardless of your selection for Exchange Server Location, Coexistence Manager for GroupWise’s Management Console will ask for all of the information listed below.

Exchange Online: Mark this checkbox only if you are configuring coexistence with Microsoft’s Office 365 hosted Exchange services. If you are configuring coexistence with a local, on-premises Exchange server, make sure this checkbox is unmarked.

Exchange Username (only if the Coexistence Manager for GroupWise admin computer and the Exchange environment are in different domains): The Username for the administrator account the F/B Connector will use to access data and features in Exchange.

IMPORTANT: Leave these Exchange Username and Exchange Password fields empty unless you are coexisting with a hosted Exchange (such as Office 365), or with a local on-premises Exchange that isn't in the same domain as the Coexistence Manager for GroupWise admin server. But if Coexistence Manager for GroupWise resides in a different domain from Exchange, then entries here are mandatory.

Exchange Password (only if the Coexistence Manager for GroupWise admin computer and the Exchange environment are in different domains): The Password associated with the Exchange Username cited above.

Show Tentative As Busy: Select Yes or No to determine whether Tentative F/B status in Outlook should appear as Busy in GroupWise.

GroupWise F/B Connector | GroupWise Free/Busy

| GroupWise Free/Busy

This information is necessary to configure Coexistence Manager for GroupWise’s GroupWise F/B Connector service, for Exchange queries for GroupWise F/B information.

GroupWise Soap Service Host Name: IP address or full DNS hostname for the GroupWise server.

GroupWise Soap Service Port Number: The SOAP port for the GroupWise server. Coexistence Manager for GroupWise prefills this field with the GroupWise default, 7191, but be sure to change it if your SOAP service is assigned to a different port.

GroupWise Request Retry Delay: Number of seconds to wait between retrying Free/Busy requests to the GroupWise system. This number should be significantly less than the GroupWise Request Timeout value (below).

GroupWise Request Timeout: Number of seconds the GroupWise Free/Busy Connector should run before timing out and returning the results it has obtained up until the timeout. Note that Outlook Free/Busy requests timeout at about 25 seconds so this number should be a few seconds less than that.

GroupWise User Name: User name for the GroupWise SOAP logon process.

GroupWise Trusted Application Name: Name of the trusted application (for example, QuestFreeBusy) by which the GroupWise User Name specified above will access the GroupWise Post Office.

GroupWise Trusted Application Key: An authentication code that permits access to GroupWise data and features by the GroupWise User Name specified above. This Key is associated with a particular Trusted Application Name, specified in the field above. You can create the key with ConsoleOne (in GroupWise 8.01 SP1 or later), or simply run a command from the Windows command prompt:

SMTP Domain Mappings: Used when the domain specified in GroupWise for a user's email address is different from the domain specified for the same GroupWise user on an Exchange system. For example, if the user’s email address in GroupWise is JohnSmith@ gwsitraka.com, and his email address in Exchange is JohnSmith@exsitraka.com, then an SMTP domain mapping would be created for exsitraka.com=gwsitraka.com. Then when Outlook does a F/B search for JohnSmith@exsitraka.com, the Coexistence Manager for GroupWise F/B Connector translates it as a request to GroupWise for JohnSmith@gwsitraka.com. SMTP Domain Mappings are used only for Exchange-to-GroupWise F/B queries.

Related Documents