Integrating Novell Collaboration Products with SugarCRM, and SharePoint


Published on

Third-party application support for products like Novell GroupWise and Novell Teaming is among the top customer enhancement requests—and critical to user productivity. In this session, we'll show you how we've done it with our upcoming data synchronization product, Novell Data Synchronizer. We'll introduce you to the product and take a detailed look at the way it enables integration between Novell collaboration products and SugarCRM, and Microsoft SharePoint.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Integrating Novell Collaboration Products with SugarCRM, and SharePoint

  1. 1. Integrating Novell ® Collaboration Products with SugarCRM, and SharePoint Ian Butler Islam Morsi Developer, Novacoast Developer, Novacoast
  2. 2. Engine and Connector Overview GroupWise ® Interwoven Teaming Sugar CRM Mobility Novell Data Synchronizer SDK SharePoint SAP 2 © Novell, Inc. All rights reserved.
  3. 3. Connector Architecture Review • Hub and spoke model • Filters and the application interface SYNC ENGINE CONNECTOR APPLICATION • GroupWise OUTPUT NODE SOURCE FILTERS FILTERS SINK • SharePoint • SugarCRM • SalesForce CACHE APPLICATION INTERFACE • Documentum INPUT • Teaming SINK FILTERS FILTERS SOURCE • And Others... NODE = Incoming Event = Outgoing Event 3 © Novell, Inc. All rights reserved.
  4. 4. User Mapping Review • Especially important with cloud services – Often use email address as user identifier • Application username vs engine username (DN) – DN is globally unique and authoritative • Simple case: Add by hand, set application names • Getting fancy: Add a group, application names automatically filled in • Large-scale enterprise guru: All automatic • App1 username → engine DN → App2 username 4 © Novell, Inc. All rights reserved.
  5. 5. Contact Use Case Contact is synchronized Contact is added to all connected to application applications Mobile Device Novell Data Synchronizer Novell GroupWise 5 © Novell, Inc. All rights reserved.
  6. 6. Salesforce and SugarCRM Connector Overview • The connectors facilitate streamlined business practices by combining sales and work group data – Contact and calendar synchronization with mobile access – Migrations, mergers, acquisitions and strategic partnerships • Supported items – Contacts – Appointments > Add vs. send > Multiple invited users supported – Tasks – Mail (legacy SugarCRM module) 6 © Novell, Inc. All rights reserved.
  7. 7. Salesforce Connector Configuration • Salesforce prerequisites – Admin proxy user – Salesforce account type • User mapping – User name options for automatic mapping • User settings • Filters – Schema mapping – User-based filtering 7 © Novell, Inc. All rights reserved.
  8. 8. SugarCRM Connector Configuration • SugarCRM prerequisites – Service user with permissions – Connectivity from server hosting the connector • User mapping • User settings • Filters – Schema mapping – User-based filtering 8 © Novell, Inc. All rights reserved.
  9. 9. Example Advanced Connector Uses • Filter contacts at certain companies • Filter low priority tasks • Transform task and appointment properties • Many more possibilities to meet business needs • How to accomplish? – Data, event and user based transformations in the filters 9 © Novell, Inc. All rights reserved.
  10. 10. Demo SugarCRM and GroupWise ®
  11. 11. Demo SugarCRM, Groupwise , and Salesforce ®
  12. 12. SharePoint Connector Overview • Allows for SharePoint synchronization with individual and group based applications • Supported items – Calendar items > Sync from SharePoint – one (list item) to many (site members) > Sync to SharePoint – one,many to one (list item) – Tasks > Sync from SharePoint - one (list item) to one (assignee) > Sync to SharePoint – one,many to one (list item) – Sync to SharePoint requires either: > Concept of a 'resource' (eDirectory , GroupWise ), or ™ ® > Subject field with name of SharePoint site included 12 © Novell, Inc. All rights reserved.
  13. 13. SharePoint Connector Usage • Configuration – NTLM/non-NTLM authentication supported – Users > Identified by login name (e.g. 'DOMAINusername') » Default policy that creates properly formated username based on CN > Select events to sync, direction to sync – Per-site custom mappings > Map non-default list names, field names • SharePoint site awareness – Changes in site name – New sites, deleted sites 13 © Novell, Inc. All rights reserved.
  14. 14. SharePoint Connector Usage • Event handling details – Connector identifies identical events > e.g. An appointment in GroupWise is sent to a resource identifying a ® SharePoint site and two users who are members of the same site » Duplicate item protection: ~ Only one calendar item is created » Across the board syncing ~ Item modification/deletion in SharePoint or by either user using GroupWise synced to all end points > e.g. Calendar item created in SharePoint list generates event per site user » Common identifier in all events for other connectors to check – Attachments supported – SharePoint list permissions respected 14 © Novell, Inc. All rights reserved.
  15. 15. SharePoint Connector Feature Details • Data and event transformations – By default, only accepts received events – HTLM in body stays intact – Special fields for transformation: > Task status > Task percent complete > Task priority > Recurring calendar items > Resource type recipient 15 © Novell, Inc. All rights reserved.
  16. 16. Demo SugarCRM and SharePoint Integration with Advanced Features
  17. 17. Salesforce, SugarCRM, SharePoint Connector Review • Enable efficient collaborative customer relationship management • Allow for faster access to business data, improving business awareness • Advanced event and data transformations can fit desired business processes and enable the creation of new streamlined processes 17 © Novell, Inc. All rights reserved.
  18. 18. Questions and Answers
  19. 19. Unpublished Work of Novell, Inc. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.