2.4 GroupWise Requirements

In order for Mobility to interact successfully with a GroupWise POA, your GroupWise system must meet the following requirements:

  • GroupWise 2014 or later for post offices that have Mobility users.

    For best synchronization performance, the latest version of GroupWise is strongly recommended.

  • You must have at least a basic GroupWise system (one domain and one post office) set up and running. For more information, see GroupWise System Creation in the GroupWise 2014 R2 Installation Guide.

  • The GroupWise Post Office Agent (POA) that the GroupWise Sync Agent communicates with must have SOAP enabled.

    The POA must also be configured with an HTTP user name and password on the Agent Settings property page of the POA object in the GroupWise Admin console (or in ConsoleOne in older GroupWise systems). This enables you to monitor SOAP threads in the POA web console.

    The initial POA uses the native GroupWise redirection process to inform the GroupWise Sync Agent how to communicate with the additional POAs throughout your GroupWise system. Thereafter, the GroupWise Sync Agent communicates directly with each POA where mobile device users’ mailboxes are located.

    IMPORTANT:All POAs must have the same SSL setting--ether all enabled for SSL or all disabled for SSL. A tool has been created to help you test these settings. For information on this tool, see GMSsslCheck in the GroupWise Mobility Service 2014 R2 Security Enhancements Quick Start.

  • A GroupWise trusted application key is required so that the GroupWise Sync Agent canauthenticate to GroupWise mailboxes without needing GroupWise users’ mailbox passwords. For more information, see Creating a Trusted Application and Key in the GroupWise 2014 R2 Administration Guide.

  • A Mobility server can be configured to communicate with one GroupWise system. If you have multiple GroupWise systems, you must set up a Mobility server for each GroupWise system.