September 10, 2010
The Novell Data Synchronizer Connector for GroupWise is the component of Data Synchronizer that connects your GroupWise system with your Synchronizer system.
The Data Synchronizer Mobility Pack includes both the GroupWise Connector and the Mobility Connector for synchronizing GroupWise data to mobile devices.
You can also install Data Synchronizer and the GroupWise Connector without the Mobility Connector for use with the Salesforce.com Connector, the SharePoint Connector, and the SugarCRM Connector.
The general system requirements for the GroupWise Connector are the same as for Data Synchronizer, as listed in Novell Data Synchronizer Mobility Pack Installation Guide.
The GroupWise-specific requirements for the GroupWise Connector are listed in the GroupWise Connector Installation and Configuration Guide.
The GroupWise Connector is automatically installed as part of the Data Synchronizer Mobility Pack, as described in the Novell Data Synchronizer Mobility Pack Installation Guide.
The GroupWise Connector can also be installed without the Mobility Connector for use with the Salesforce.com Connector, the SharePoint Connector, and the SugarCRM Connector, as described in the Novell Data Synchronizer Mobility Pack Installation Guide.
When the GroupWise Connector cannot communicate with the GroupWise POA for some reason, you see the following message in the GroupWise Connector log file:
GroupWise is down, will retry in nn seconds
Occasionally, this messages continues to appear in the GroupWise Connector log file even after the GroupWise POA is running again. To resolve the problem, restart the GroupWise Connector.
By default, GroupWise contact information synchronizes to other applications such as SugarCRM when you add or modify contacts. If you want to get an entire personal address book to synchronize with another application, you can use this workaround:
In the GroupWise client, export the personal address book.
Delete all the contacts from the personal address book, so that the address book is empty.
Import the personal address book back into GroupWise, so that all of the contacts are re-created.
This causes all of the contacts in the personal address book to synchronize with other applications.
On the main Synchronizer Web Admin page, if you click theicon in the column for the GroupWise Connector, no status information is available. Status information is currently provided for the Mobility Connector, but not for the GroupWise Connector.
GroupWise external entities are not currently supported for synchronization. By definition, external entities are represented by GroupWise objects, and they have no corresponding eDirectory objects. Authentication for synchronization is done through LDAP. Therefore, external entities cannot authenticate to the Synchronizer system.
The workaround is to convert external entities into eDirectory users so that they can authenticate to the Synchronizer system.
Under theoptions on the page in Synchronizer Web Admin, leave the option at its default setting of . This setting synchronizes data for the specific users that you select during installation of the Mobility Pack.
Thesetting synchronizes GroupWise data for all users, regardless of whether they have been added to the Mobility Connector. For a Mobility Pack installation, this setting creates unnecessary synchronization traffic and causes the GroupWise Connector to store data that will never be synchronized to mobile devices. However, this setting might be useful if you are using a different connector, such as the Salesforce.com Connector, the SharePoint Connector, or the SugarCRM Connector.
The GroupWise Connector depends on the GroupWise POA to support its functionality. GroupWise 8.0.2 is required for use with the GroupWise Connector. However, GroupWise 8.0.2 was released with some issues that impact GroupWise Connector functionality. Fixes for these GroupWise 8.0.2 issues will be available as hot patches or in the next GroupWise release.
The following issues occur if you are running GroupWise 8.0.2, but they do not occur if you are running a later release of GroupWise:
If you look up a contact in the GroupWise Address Book from your mobile device, the address is retrieved in theformat. This happens even when the address format is set correctly in ConsoleOne. There is no workaround.
Contacts that have notes associated with them take a long time to synchronize to your mobile device. After GroupWise 8.0.2, notes are not synchronized with contacts in order to speed up synchronization.
Under several circumstances, a single appointment or the first instance of a recurring appointment appears multiple times on the mobile device even though it displays correctly in GroupWise. For example, if you modify an appointment on the mobile device, both the original appointment and the modified version appear on the device, but the modification is successfully made in GroupWise.
On some mobile devices, when you modify an existing appointment on your mobile device, duplicate appointments appear on the mobile device and in GroupWise. The duplicates can be cleaned up by retracting the original appointment in the Sent Items folder in GroupWise.
If you create a recurring appointment on your mobile device, the last recurring instance does not appear in GroupWise.
Under certain circumstances, the address in thefield displays incorrectly. This is a cosmetic issue. Replying to the address in the field works correctly.
On some mobile devices, when you send a message, it appears in your own Mailbox folder as well as in your Sent Items folder.
From your mobile device, you cannot mark an itemor if it is in the Trash folder.
Under certain circumstances, POA SOAP threads gradually become unresponsive, and additional SOAP threads start, building up to a total of 80 threads. Occasionally, the POA crashes as a result. If this occurs, restart the POA.
Under certain circumstances, the GroupWise Connector tries to retrieve all items in a user’s mailbox. This erroneous activity causes too many threads to start and consumes a large amount of memory. If this occurs, restart the POA.
Some mobile devices create items encoded for the UTF-8 character set. The encoding used by the mobile devices did not match the UTF-8 encoding expected by the POA. As a result, a duplicate item might be created or the message body is truncated.
Novell Data Synchronizer documentation is available at the Novell Data Synchronizer Documentation Web site:
Novell Data Synchronizer Readmes
Novell Data Synchronizer installation and administration guides
Novell Data Synchronizer connector documentation is available at the Novell Data Synchronizer Connector Documentation Web site
Connector Quick Starts
Connector installation and configuration guides
In addition to the Data Synchronizer product documentation, the following resources provide additional information about Data Synchronizer and connectors:
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2010 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.