In order for Mobility to interact successfully with GroupWise, your GroupWise system must meet the following requirements:
GroupWise 18 or later domain.
For best synchronization performance, the latest version of GroupWise is strongly recommended.
NOTE:While GroupWise 18 domains are required, your POAs do not have to be updated to 18 to work with Mobility 18.
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 that have Mobility users must have the same SSL setting--ether all enabled for SSL or all disabled for SSL. If you need to check the SSL settings of your POAs, use the SSL Check option in MCheck.
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 Creating a Trusted Application and Key in the GroupWise 18 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.