Corporate Services e- business Proof of Concept for Jive-SharePoint Connector

2 MetLife Ryan Bednarz Bruce Galinsky Jerry Ellsworth Kyle Mintz Graham Mingst Steven Perry Three Will Tommy Ryan Eric Bowden Pete Skelly Jive-SharePoint Conector - PoC Team

PoC Activities  Developed and refined PoC requirements  Conducted Deep Dive reviews with Three Will and Jive to clarify requirements  Conducted Deep Dive review of configured Jive- SharePoint connector  Hands on testing of configured Jive-SharePoint connector  Document and summarize PoC findings 3

4 Summary Assessment of Connector Functionality vs. MetLife Requirements Major Connector FunctionSummary Assessment Claims Authentication Socialize SharePoint content in Jive Socialize Jive activity stream to SharePoint Search SharePoint – from Jive Coordinated tag management RIM Compliance Centralized alert management Not supported Partially supported Fully supported

Jive SharePoint Connector – Gap Analysis 5 Jive/SharePoint ConnectorDescriptionFunctionalityGaps Claims AuthenticationPerforming authorization based on SAML claims Use delegation for server to server authentication instead of impersonation  Doesn’t support Claims Authentication now, but can be added to future connector releases Socialize SharePoint content to JiveExpose content from a SharePoint site in a Jive space Link SharePoint site to Jive site such that SharePoint content from the linked site or sites is visible and accessible from the connect Jive site.  Document activity from SharePoint is not security trimmed, thought the document preview is – this is supposed to be available in v 1.6 of the connector  Support document previews for draft and final  Content selection is not granular enough – can socialize a specific content library, but not content type, file extension or individual documents – document level selection is probably not a critical gap.  Would also like to do rules-based socialization – for example PM docs all get socialized to a PM Community doc  List widget does not render all field types properly - Socialize Jive activity stream to SharePoint Expose Jive activity stream in one or more SharePoint team site Add and configure a custom part to expose Jive activity stream in the SharePoint team site  This functionality works, though the use of web parts to accomplish this is a bit clumsy. As is the use of apps to socialize SharePoint documents in Jive  The granularity of the activity stream that can be exposed in SharePoint is not sufficient. (ex. Pull the activity stream for just a single document) Search – from JiveAbility to search SharePoint from Jive.The connector uses a federated SharePoint search to search the SharePoint database from Jive. Our requirement is for this federated search to provide a seamless user experience in comparison with SharePoint searches from SharePoint  SharePoint search results from Jive look very different from ”native:” SharePoint search results – different format, different fields returned. IT does provide the ability to change the look, and the search results format, but still does not get us to a seamless look and feel.  Search results from the federated results do not, but should provide search recommendations from SharePoint and Jive  Jive does not surface tags from SharePoint. A seamless search will require Jive to synchronize and combine the Jive and SharePoint tags.  Search results should clearly delineate content types and content source Tags and Tag managementAbility to recognize and use SharePoint tag values from Jive Need Jive to be able to recognize and use SharePoint tags from SharePoint document  Jive does not recognize tags from SharePoint – so searching by tags from Jive to SharePoint is not using these tags and thus is a potentially ineffective search (when searching SharePoint)  Need some synchronization of SharePoint and Jive term stores. Use SharePoint to manage terms and sync with Jive. RIM policy complianceAll documents used by MetLife are governed by RIM MetLife requires content related to documents in SharePoint be governed by the same policies as that SharePoint document  This functionality is not in the connector at all. We would have to link SharePoint information policies to related conversations (blogs?) and meta data in Jive. Alert managementCentral management of alertsUser can configure a broad range of alerts in SharePoint and can follow users or subjects in Jive – resulting in alerts No central location to manage alerts – to view the list of places and users which are being followed or have established alerts