In order for the GroupWise Sync Agent to interact successfully with a GroupWise POA, your GroupWise system must meet the following requirements:
In post offices that have mobile device users:
GroupWise 2014 Support Pack 1 or later
GroupWise 2012 Support Pack 3 or later
For best synchronization performance, the latest version of GroupWise is strongly recommended.
IMPORTANT:When you are ready to upgrade from GroupWise 2012 to GroupWise 2014, update your Mobility system to Mobility Service 2.1 before you upgrade your GroupWise system.
You must have at least a basic GroupWise system (one domain and one post office) set up and running. For more information, see the documentation for your version of GroupWise:
The GroupWise Post Office Agent (POA) that the GroupWise Sync Agent communicates with must have SOAP enabled. For more information, see the documentation for your version of GroupWise:
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 for post offices that have mobile device users must have SOAP enabled.
A GroupWise trusted application key is required so that the GroupWise Sync Agent can authenticate to GroupWise mailboxes without needing GroupWise users’ mailbox passwords. For more information, see the documentation for your version of GroupWise:
IMPORTANT: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.