Jive Connects for Microsoft SharePoint

Jive Connects for Microsoft SharePoint

Contents Jive Connects for Microsoft SharePoint...2 ReadMe... 3 Best Practices... 4 Getting Started... 4 Troubleshooting Tips... 5 Generic Troubleshooting...5 Active Directory user account changes not recognized for SharePoint data consumed in Jive... 7 409 Conflict error... 7 "Cannot add the specified assembly to the global assembly cache" error during installation... 7 Cannot add web parts to a SharePoint page...7 Cannot associate Copy To workflow to a library... 7 Error socializing a SharePoint site to Jive...8 Jive Copy workflow is no longer available for manual initiation, or no longer automatically starts...8 Jive installation test fails - SharePoint Administration... 8 Jive user or group avatars not showing up in SharePoint, including web part and user popups... 8 List widget shows broken image icon and/or challenges user for credentials... 9 Search URL for SharePoint items in Jive search results shows internal SharePoint URL... 9 Searching SharePoint from Jive fails...9 SharePoint location test fails - Jive Admin Console... 9 SharePoint Site Admin pages show "Error" and "Unknown Error"... 10 SharePoint user activity not showing in Jive... 10 Users repeatedly prompted for credentials... 10 Jive Doesn't Recognize a SharePoint User After Install/Upgrade...11 SharePoint Activity stream times out or generates an error... 11 Unable to access SharePoint user interface to view or modify socialization settings... 11 Using Jive and SharePoint Together... 14 Viewing SharePoint Content in Jive... 14 Using Web Parts in SharePoint...21 Using the Socialization Features...31 Setting up SharePoint... 36 Installing, Upgrading, and Deploying the SharePoint-Side Plugin...37 Administering the SharePoint-Side Plugin... 48 Configuring Client Browser Settings...58 Configuring Search Results Security Trimming... 61 Tips for Developers... 62 Setting up Jive... 65 Installing and Upgrading the Jive-Side Plugin... 66 Administering the Jive-Side Plugin...69 System Properties for SharePoint Integration...78 Authentication Scenarios... 84 Authentication Through Impersonation...84 Impersonation Restriction Validation... 86

Jive Connects for Microsoft SharePoint Jive Connects for Microsoft SharePoint provides tight integration between SharePoint and Jive. It takes SharePoint s strengths as a content repository with complex workflows and document management and couples them with Jive s social networking capability, intuitive interface, and high adoption rate. This documentation introduces Jive Connects for Microsoft SharePoint, describes initial considerations that should be made when integrating Jive and SharePoint, and directs you to the appropriate documentation for getting up and running with the product. To get started right away, see Getting Started (page 4) ' ' Many enterprises challenged by large content repositories and complex workflows have turned to document management systems like SharePoint. As Social Business Software increasingly transforms business by uniting community, connections and content, traditional content management systems need to find ways to engage with the social workplace and become truly socially enabled. With Jive for SharePoint, enterprises can unite the power of Jive and SharePoint to drive business productivity and innovation. Jive s social networking, collaboration capabilities and highly intuitive interface are highly complementary to SharePoint s content infrastructure. The Connector leverages Sharepoint s strengths in document storage and records management, while providing true collaborative momentum around content creation and business processes. Best of Both Worlds By adding Jive for Microsoft SharePoint, now you can leverage both Jive and Microsoft SharePoint to do what they do best. Use Jive as your hub for socializing and sharing content broadly across the enterprise even if the content lives in SharePoint. Now, when employees post a discussion, author a blog, or collaborate on a document inside Jive, they can easily find and link to SharePoint content searching and navigating any number of SharePoint sites from their Jive interface. Jive Connects for Microsoft SharePoint - 2

Preserve SharePoint as your official workflow and document storage system while infusing it with Jive social features. When employees are working inside SharePoint, they have a direct window and click-through access to people, content, and activities in Jive. Why You'll Love Making SharePoint Jive Socialized synergy Jive for SharePoint seamlessly integrates Jive and SharePoint with unified access, unified search results, unified activity streams, and unified document storage. Bi-directional content push plus corporate governance capabilities further extend the solution. Unified access Gives authorized users transparent, click-through access to both applications while exposing Jive in SharePoint, allowing you to move seamlessly between applications. Unified search results Delivers search results from both Jive and SharePoint in every search, no matter which application you search from to help you find content immediately. Unified activity streams Provides a consolidated view of activities as they happen in both SharePoint and Jive by people you consider important and for projects and initiatives that matter to you, which means that you can act faster and more precisely with full awareness of what s going on. Bi-directional content push Makes it easy to push content in either direction with a one-click push operation that copies a file to a pre-defined location, carrying the specific file metadata with it. Also allows authorized Jive users to push content into SharePoint workflows and to push SharePoint content out into public Jive communities. Corporate governance Gives IT and SharePoint administrators a semantically rich business rule language to help them define what, how, and when SharePoint content gets socialized to protect privacy while enabling powerful socialization at a very granular level from strictly private to completely public. ReadMe Before getting started (page 4) with Jive Connects for Microsoft SharePoint, you should review the following topics to help you ready your environment. You can find release-specific information in the Release Notes. Connections Determine what SharePoint sites and Jive instances you want to connect. SharePoint can connect to multiple Jive installations and Jive can connect to multiple SharePoint sites across multiple SharePoint farms. Policies SharePoint activity can be shown in Jive, but restricted by policies that are enforced by SharePoint farm administrators. Consider what policies you want to put in place to keep your sensitive data secure while still making the most use out of SharePoint by extending it in to the social world of Jive. Authentication We support impersonation using NTLM. If you use impersonation, pay close attention to the Farm Configuration for Jive screen in SharePoint and the System Properties in Jive where you can put in place extra security measures when using impersonation. NTLM (NT Lan Manager) is a Microsoft Windows authentication implementation based on challenge/ response. NTLM can be used to authenticate a user without transmitting a password over the network. A limitation of NTLM is that it cannot "delegate" a user's credentials (token) beyond the server requesting authentication. A benefit of NTLM is that it is relatively simple to configure. Jive Connects for Microsoft SharePoint - 3

Multi-Domain Permissions For environments where users will be logging into SharePoint across multiple domains, the domains must have a two-way trust, so that Jive users can see SharePoint search results. Best Practices Here are some best practices to consider when using SharePoint: Streamline Your Socialized SharePoint Site When a place contains more than 1000 documents, performance may be affected when Jive users try to access SharePoint documents without the appropriate permissions. Here's how you can improve performance in this situation: When you socialize a SharePoint site that many Jive users can't access, you may want to limit access to a private Jive group that contains only members with the appropriate permissions to SharePoint. When you socialize the site, you can select the Jive Security option. Set Activity Stream Polling Limits You may want to set sharepoint.activity.polling.request.initial.timelimitseconds longer than sharepoint.activity.polling.request.timelimitseconds because there should be more Activity Stream items to process in the first request, depending on the start date specified when socializing the SharePoint site to Jive. You should also set both values comfortably below the IIS thread timeout value which defaults to 90 seconds. Getting Started You can use the following steps to get started integrating SharePoint and Jive. 1. Review prerequisites available in the Jive Installation Requirements (page 66) and in the SharePoint Requirements (page 37). 2. Install SharePoint (page 37) and Jive (page 66) plugins. 3. Configure SharePoint location in Jive (page 69) and Jive location in SharePoint (page 50). 4. Test both connections as instructed in the installation topics. 5. Configure user identity mapping (page 71) if required. Determine how Jive users can map to SharePoint users by choosing a mapping set (page 77). Configure identity mapping (page 73) for your SharePoint location. Configure and map user identity values. In Jive, select identity mapping for each SharePoint location. Test Identity Mapping for a user by using diagnostics (page 75) in the Admin Console. 6. Setup SharePoint UI, Web parts, and workflow. Note: Socialization is not required for this step. Perform SharePoint central administration (page 49), which includes configuring the Farm for Jive, managing the Jive installation, and configuring corporate policies. After testing users, add and verify Web Parts (page 21) in SharePoint. Demonstrate the Jive User Popup (page 31) by hovering over a "Modified By" field in a simple list view. For example, Tasks. Demonstrate the Copy to Jive drop down menu action (page 32). Configure and use the Copy To Jive workflow (page 33). 7. At this point, you may want a socialization strategy. For more on this, see Best Practices (page 4). 8. Setup site socialization and activity streams. Jive Connects for Microsoft SharePoint - 4

If this is not a top level site in the site collection, go to the Jive Site Settings (page 55) page and uncheck the Inherit settings from parent site checkbox Socialize a SharePoint site (page 55) to Jive. Set up an activity stream which includes: Select one or more libraries. Configure date from when Jive should pull data for the Activity Stream. Select a permission model. Note: Activity streams may first need to be enabled in Corporate Policies (page 52) by a SharePoint farm administrator. 9. Setup Jive widgets and the Jive UI. Add and verify widgets (page 14) in Jive. Verify document activity is coming from SharePoint into Jive. Demonstrate Migrate to SharePoint (page 19). Demonstrate the SharePoint List Macro in Jive. Troubleshooting Tips This guide can be used by individuals who need to diagnose issues when configuring Jive for SharePoint. Generic Troubleshooting (page 5) Active directory user account changes not recognized for SharePoint data consumed in Jive (page 7) Cannot add web parts to a SharePoint page (page 7) Cannot associate Copy To workflow to a Library (page 7) Error socializing a SharePoint site to Jive (page 8) 409 Conflict (page 7) Installation error message: "Cannot add the specified assembly to the global assembly cache" (page 7) Jive Copy workflow is no longer available for manual initiation (or no longer automatically starts) (page 8) Jive installation test fails - Jive Administration (page 8) Jive user or group avatars not showing up in SharePoint (including web part popups, user popup) (page 8) List widget shows broken image icon and/or challenges user for credentials (page 9) Search URL for SharePoint items in Jive search results shows internal SharePoint URL (page 9) Searching SharePoint from Jive fails (page 9) SharePoint location test fails for SharePoint Administration (page 9) SharePoint Site Admin pages show Error and Unknown Error (page 10) SharePoint user activity not showing in Jive (page 10) Users repeatedly prompted for credentials (page 10) SharePoint Activity stream times out or generates an error (page 11) Unable to access SharePoint user interface to view or modify socialization settings (page 11) Doesn't Recognize a SharePoint User After Install/Upgrade (page 11) Generic Troubleshooting The following tips can be useful for general troubleshooting of the connector within Jive and/or SharePoint. Note: In addition to the log information you can get as described here, you can also get log information from Jive. In the product documentation, see the "Getting Application Logs." SharePoint Logs The SharePoint ULS logs can contain detailed information about SharePoint and the connector itself. The tracing level can be configured from SharePoint Central Administration --> Operations --> Farm Configuration for Jive in the Event Logging section. The log files are stored in a directory which can be determined by going to SharePoint Central Administration --> Operations --> Diagnostic Logging. There you can see the Path for the Trace Log. Jive Connects for Microsoft SharePoint - 5

From this same page you can also specify the logging level for Jive Integration Diagnostics in the Event Throttling section. Only the trace log setting is used (not the event log setting). This is the same setting done from the Farm Configuration for Jive page. After changing the logging level you should perform an IISRESET on every web front end in the farm. When looking at the log files, you can tend to ignore the PSCDiagnostics files. These are post setup configuration files. IIS Logs SharePoint runs under ASP.NET and IIS (Internet Information Server). IIS provides log files that contain all requests. This can be useful in debugging Jive communication to SharePoint. In order to look at the log files, you need to know which IIS web site is used for SharePoint. One way to figure this out is go to SharePoint Central Administration --> Application Management --> Web Application List The names along the left tend to match the IIS web site names and are matched with the URLs used to access SharePoint. Unfortunately, names can be changed. The only way to know for sure is to look at more detailed IIS settings around ports and host headers, but this isn't usually required. Once you know the IIS web site, you can use the information based on your IIS version to find the log files. Note that you may need to look at log files on multiple machines, especially if you have several web front ends (WFEs) in your SharePoint farm. There are two versions of IIS in use: IIS 6.0 and IIS 7.0. Your IIS version may affect where the log files are stored. In IIS 6 Run IIS6 from a SharePoint server (Start --> Administrative Tools --> Internet Information Services (IIS) Manager). Right-click the web site and choose Properties. Go to the Web Site tab and towards the bottom is a logging section. Click on the Properties button to see the log file directory and the log file name (which contains an important subdirectory - the ID noted below). See also: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ IIS/3e27a577-a6e3-4b0b-9379-68efb5d52ee9.mspx?mfr=tru Defaults to %SystemDrive%\WINDOWS\system32\LogFiles\W3SVC<ID> In IIS 7 Run IIS7 from a SharePoint server (Start > Administrative Tools > Internet Information Services (IIS) Manager). Click on the web site. Double-click Logging to see the directory. Click on the web site again. Click Advanced Settings on the right of the page. Note the ID so can find the subdirectory for the log files (see below). Defaults to %SystemDrive%\inetpub\logs\LogFiles\W3SVC<ID> See also: http://technet.microsoft.com/en-us/library/cc732079(ws.10).aspx Advanced Network Monitoring Some more advanced diagnostic options involve using network monitoring tools such as: Client Browser Network Activity Monitoring. You can use a tool such as Fiddler (http:// www.fiddlertool.com/fiddler/version.asp) or Charles (http://www.charlesproxy.com/) to watch activity from your browser. This can be useful to understand client-to-server activity issues. Server Network Activity Monitoring. You can use a tool like TcpMon (https://tcpmon.dev.java.net/) or WireShark (http://www.wireshark.org/download.html). The former is easier to use but requires setting up a proxy. The latter is much more advanced. Jive Connects for Microsoft SharePoint - 6

Active Directory user account changes not recognized for SharePoint data consumed in Jive If you change the login name (samaccountname) of an Active Directory (AD) user after the AD user has logged into SharePoint, then the old login is still used when SharePoint provides Jive user information with the activity stream, copy to action, etc. The end result is that the activity is ignored, or an override account is used (if override accounts are configured). To correct this, the user account must be "migrated" using the stsadm "migrateuser" command to correct the login name in the UserInfo table within the SharePoint content database(s). The following links discuss how to migrate the user: http://technet.microsoft.com/en-us/library/cc262141(office.12).aspx http://www.toddklindt.com/blog/lists/posts/post.aspx?id=75 For more on user overrides, see Adding a SharePoint Location (page 69) or System Properties for SharePoint Integration (page 78). 409 Conflict error You might receive a 409 Conflict error in SharePoint when you attempt to socialize a SharePoint site to a Jive place. This happens when Jive feels it is already part of a socialization. Either the Jive place is already connected to another SharePoint site or there is a disconnect between what Jive and SharePoint think is socialized. That disconnect can happen if a SharePoint site is un-socialized, but SharePoint cannot communicate with Jive at the time. A warning should be shown, but we allow this to occur by design. There are a couple of ways to see if a Jive place is connected to a SharePoint site - from Jive's point of view. As a place owner you can do this from the Jive place using "SharePoint Socialization Settings" link shown in the "Actions" settings typically found on the right side of the page. However, the best way to do this is through Jive Admin console > System > Settings > SharePoint Connector > Diagnostics. Click the green "+" next to each SharePoint Location defined and scroll down to see the "sites" that are connected through each SharePoint Location. If there is truly a disconnect between what SharePoint and Jive think, you can click the red "x" to the right of the site to remove the connection from Jive's point of view. This should only be done if there is a disconnect as it would otherwise cause one "Cannot add the specified assembly to the global assembly cache" error during installation While installing, if you encounter an error such as "Cannot add the specified assembly to the global assembly cache," on each SharePoint Server do the following: 1. Open up a command prompt and enter IISRESET /STOP. 2. Go to Administrative Tools > Services and stop the Windows SharePoint Services Timer service. 3. Open Windows Explorer to C:\Windows\Assembly and look for any Jive.SharePoint.* assembly. 4. Right-click those that you find, then click Uninstall. If you find none, continue to the next step. 5. Go to Administrative Tools > Services and start the Windows SharePoint Services Timer service. 6. Open up a command prompt and enter: IISRESET /START. 7. Re-run the installation. Cannot add web parts to a SharePoint page Make sure you are using IE. Firefox and other browsers are not level 1 browsers within SharePoint 2007 and cannot do all functions. Cannot associate Copy To workflow to a library To use the workflow you must have the "Jive Copy To Workflow" site collection feature activated. This is done by the installer, but must be manually activated on site collections not selected during Jive Connects for Microsoft SharePoint - 7

the installation. To activate, log in as a site collection administrator and go to Site Settings > Site Collection features on the root site in your site collection. Then activate the "Jive Copy To Workflow" feature. Note that this can only be used on SharePoint libraries, not on regular SharePoint lists. Error socializing a SharePoint site to Jive If you see an error containing "Unable to register new activity feed with Jive due to Server returned HTTP response code: 400", then verify that the SharePoint service account (defined within the JiveAdmin Console:Settings --> SharePoint Connector --> SharePoint Locations has access to the SharePoint site you are trying to socialize. If you see an error saying "Error registering WebDeleting event receiver," Jive has added the unified feed, but if this SharePoint site is deleted, Jive will not be notified and the feed will not be removed from Jive. Validate that the SharePoint service account use by Jive (specified in SharePoint Locations within Jive) has access to the SharePoint site being socialized. Jive Copy workflow is no longer available for manual initiation, or no longer automatically starts All configured Jive Copy Workflow associations to any document libraries are disabled across your entire farm and prevent new instances from running when you perform an upgrade of Jive for SharePoint. This also happens across an entire site collection if you disable and re-enable the Jive Copy To Workflow feature in a site collection. To correct this, SharePoint site administrators need to set their Jive Copy workflows to allow new instances. For detailed instructions, see Allowing New Instances for Jive Copy Workflow (page 36) Jive installation test fails - SharePoint Administration This describes how to diagnose the issue where you cannot successfully test a Jive installation defined within SharePoint Central Administration --> Operations --> Manage Jive Installations. Ensure that Jive has the plugin installed. Ensure that the Jive service account has access to Jive (try to log into Jive with that service account). Check Jive web service settings (Jive Admin Console:System --> Settings --> Web Services) Ensure that "REST Web Services" are enabled. Check the User Access section. Recommend that "All Registered Users" is used initially. If you are using "Only Specified Users" or "Specific Groups" make sure the Jive service account is addressed. If you make a change you need to restart Jive for this to take effect. Make sure you have the SharePoint web front end (WFE) IPv4 and/or IPv6 addresses in the Jive admin System Property sharepoint.ip.restrictions. Note that if you have several WFEs, you need to add IP addresses for each. Consider adding 127.0.0.1 if all else fails. Try navigating to the following URL with your browser to see the response. Recommend using IE because it nicely formats XML results, but any browser should do. <jive_internal_url>/rpc/rest/spintegration/server For example: http://jive.mycompany.com/rpc/rest/spintegration/server Jive user or group avatars not showing up in SharePoint, including web part and user popups Jive Connects for Microsoft SharePoint - 8

Go to JiveJive Admin Console:System --> Management --> System Properties and make sure the "jiveurl" property is the same as the Jive External URL defined in the Jive Installation within SharePoint (SharePoint Central Administration --> Operations --> Manage Jive Installations) (Advanced) Using a tool like Fiddler can help here. List widget shows broken image icon and/or challenges user for credentials When the list widget shows images from SharePoint, the image may show up as a broken icon or may challenge the user for SharePoint credentials. This can be fixed by selecting a list view that does not show the image or by configuring the client browser settings to automatically login to SharePoint. See Configuring Client Browser Settings (page 58) for more details. Note that Jive users that do not have access to SharePoint will not be able to see the image. Search URL for SharePoint items in Jive search results shows internal SharePoint URL If you perform a search in Jive and see SharePoint search results that have the first part of the URL incorrect, it may be due to a configuration issue. This can occur when you use different URLs for the internal and external URLs for a SharePoint Location defined within Jive. The search results should begin with the external URL, but may begin with the internal URL. In SharePoint Central Administration, both URLs should be defined through Alternate Access Mappings. The external URL should be defined using the Alternate Access Mapping for the Default zone. Searching SharePoint from Jive fails In a browser, go to the SharePoint site associated for the SharePoint Location. Log in as account specified in Jive for the SharePoint Location and go to Site Actions --> Site Settings. Then click the Diagnostics link under Jive group (<sharepoint_site>/_layouts/jive/pages/diagnostics.aspx). Follow the instructions on the page for the Search Impersonation Test. Take careful note of the requirements for search impersonation. If possible run the browser from the Jive server to validate that the Jive server can access a SharePoint server. SharePoint location test fails - Jive Admin Console This describes how to diagnose the issue where you cannot successfully test a SharePoint Location defined within the Jive Admin Console. Perform the diagnostic test, Testing User Connectivity and Search Across Sites in a SharePoint Location in the Diagnosing Integration Issues (page 75) help topic. Ensure that SharePoint has the bits installed. Ensure that the SharePoint service account has access to the location (try to log into that SharePoint location with that service account). The SharePoint service account should have read access to the site defined by the external/internal location URL and for sites within that location that are socialized to Jive. Check the impersonation settings (Central Admin --> Operations --> Farm Configuration for Jive) Set Impersonation = Allowed. Recommend that Valid Incoming IP Addresses is blank initially. When setting this, realize that you may need IPv4 and IPv6 addresses of all Jive servers. In addition, you may need to enter the IP addresses of load balancers immediately in front of SharePoint web front ends. Recommend that Valid Incoming Service Accounts is blank initially. When setting this simply enter all SharePoint service accounts specified in the Jive console under SharePoint locations. Use the user check icon to validate the entry. Jive Connects for Microsoft SharePoint - 9

In a browser, go to the SharePoint site associated for the SharePoint Location. Log in as account specified in Jive for the SharePoint Location and go to Site Actions > Site Settings. Then click the Diagnostics link under the Jive group (<sharepoint_site>/_layouts/jive/pages/diagnostics.aspx). Follow the instructions on the page for the Web Service Test If possible run the browser from the Jive server to validate that the Jive server can access a SharePoint server. SharePoint Site Admin pages show "Error" and "Unknown Error" If the SharePoint site administration pages (including Jive Site Settings, Jive Socialization Settings, View Jive Activity Streams, Diagnostics) show "Error" and "Unknown Error," it is likely because the web application feature was not properly activated. To fix this go to SharePoint Central Administration > Application Management > Manage Web Application Features and use the drop down near the top right of the page to select the web application where the problem occurs. Activate the Jive Infrastructure feature. If it is already active, deactivate it and then activate it. The Jive Infrastructure feature copies resource files to the App_GlobalResources directory for the web application. Each SharePoint web application has a web site directory (for example, C:\Inetpub\wwwroot \VirtualDirectories\80) that has an "App_GlobalResources" subdirectory. If the following files are not in this subdirectory, the administrative pages will fail to load: JiveGlobalResources.de-de.resx JiveGlobalResources.es-es.resx JiveGlobalResources.fr-fr.resx JiveGlobalResources.it-it.resx JiveGlobalResources.ja-jp.resx JiveGlobalResources.resx JiveGlobalResources.zh-cn.resx. These files are copied from the Resources directory under the SharePoint root (for example, C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\resources). If these files are not in place for your web application, you can copy them there manually, but this is not recommended because it is likely the other updates by the Jive Infrastructure feature were not performed, and this does not handle every web front end. The recommended fix is to deactivate and re-activate the Jive Infrastructure feature on your web application. SharePoint user activity not showing in Jive If a SharePoint site is socialized to a Jive place you will only see activity (document updates) from SharePoint users who are also Jive users. If you see activity in Jive for most users but not from a particular user, then it is likely that the user whose activity is not showing up in Jive is not a user in Jive. However, activity for particular users can also be turned off from Corporate Policies (page 52). It could be that the user simply needs to log into Jive once for the account to be recognized in Jive or that you need to set up a LDAP synchronization process to ensure that new LDAP users are regularly added to Jive without them having to physically log into Jive. Not that SharePoint activity from service accounts that don't have access to Jive are not supported. The workaround is to use other accounts for the activity or to give those accounts access to Jive. Users repeatedly prompted for credentials Anonymous users are not supported with the connector. If you allow anonymous access to a SharePoint site where the Jive Web Parts feature is activated, any page in the site will can cause anonymous users to be prompted for a username and password multiple times. A partial workaround is to turn off all global features ( SharePoint Central Administration --> Operations --> Farm Configuration for Jive) and to not show any of the Jive web parts on pages accessed by anonymous users. Jive Connects for Microsoft SharePoint - 10

Jive Doesn't Recognize a SharePoint User After Install/Upgrade If you are setting the sp-external-id profile property in Jive when the user logs in, SharePoint users will not be able to access SharePoint resources after a plugin install or upgrade until they have logged into. We now have an override in place to set the user name to some common account, but it cannot be set to the real Jive user account if there is no Jive user record with the sp-external-id profile property set (in the multi-domain case). You should prompt your users to log in to Jive before using Jive Connects for SharePoint each time you install or upgrade the plugin. Users who haven't logged in yet, and whose accounts have not been synchronized through a batch process, may experience some of the following problems: Documents aren't displayed in the Activity Stream Copying to Jive fails The List Widget doesn't function correctly SharePoint web parts show "access denied" Site socialization is not possible You can't associate the Jive Copy workflow to a document library SharePoint Activity stream times out or generates an error You may be encountering a high volume of activity, and you can resolve this by limiting the time Jive spends polling for SharePoint activity by reducing the time limit set by the sharepoint.activity.polling.request.initial.timelimitseconds and sharepoint.activity.polling.request.timelimitseconds system properties. For more on this, see System Properties for SharePoint Integration (page 78) Unable to access SharePoint user interface to view or modify socialization settings In SharePoint 2007 or 2010, if you cannot access the SharePoint user interface, you can still use PowerShell to view and modify the site settings, including the socialization settings, for a specific SharePoint site. Note: This approach should be done as a last resort when the screens are not working properly for some reason. Using this approach does not perform a handshake with Jive so it can cause SharePoint and Jive to not be in sync. SharePoint 2007 Download and install PowerShell from Microsoft Support. Once installed, launch PowerShell by going to Start > All Programs > Accessories > Windows PowerShell > Windows PowerShell. When PowerShell opens, you'll need to load the SharePoint libraries for PowerShell. Do this by copying/ pasting the following lines into the PowerShell command window: [System.Reflection.Assembly]::Load("Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c") [System.Reflection.Assembly]::Load("Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c") To view the settings: $spsite = [Microsoft.SharePoint.SPSite] ("<root_web_url>") $web = $spsite.openweb("<relative_site_url>") $ss = $web.properties["jive.sitesettings"] $ss For example: Jive Connects for Microsoft SharePoint - 11

PS C:\Users\Administrator> $spsite = [Microsoft.SharePoint.SPSite]("http:// sharepoint.redlinkmobile.local/") PS C:\Users\Administrator> $web = $spsite.openweb("/marketing/") PS C:\Users\Administrator> $ss = $web.properties["jive.sitesettings"] PS C:\Users\Administrator> $ss <jivesitesettings xmlns="http://jive.com/sharepoint/administration" xmlns:i="http:// www.w3.org/2001/xmlschema-instance" ><InheritParentSettings>false</InheritParentSettings><DefaultJiveInstanceId>1</ DefaultJiveInstanceId><SocializationEnab led>true</socializationenabled><socialtargets xmlns:a="http://schemas.datacontract.org/2004/07/ Jive.SharePoint.Common.A dministration"><a:socialtarget><a:accesscontrol>allowmetadata</ a:accesscontrol><a:jivegrouptype>0</a:jivegrouptype><a:j iveplaceid>1001</a:jiveplaceid><a:jiveplacename>marketing</ a:jiveplacename><a:jiveplacetype>700</a:jiveplacetype><a:use raccountforaccess>sp2007\kliemohn</a:useraccountforaccess></a:socialtarget></ SocialTargets><StreamingEnabled>true</Stre amingenabled><socializedsite>http://jive.redlinkmobile.local/rpc/rest/spintegration/ sites/1000</socializedsite></jivesi tesettings> If you want to see the XML a little nicer you can copy the text out of the output and paste it in notepad and then format it. Or, you can do the following: $ssxml = [xml]$ss $ssxml.jivesitesettings $ssxml.jivesitesettings.socialtargets.socialtarget For example: PS C:\Users\Administrator> $ssxml = [xml]$ss PS C:\Users\Administrator> $ssxml.jivesitesettings xmlns i InheritParentSettings DefaultJiveInstanceId SocializationEnabled SocialTargets StreamingEnabled SocializedSite : : : : : : : : http://jive.com/sharepoint/administration http://www.w3.org/2001/xmlschema-instance false 1 true SocialTargets true http://jive.redlinkmobile.local/rpc/rest/spintegration/sites/1000 PS C:\Users\Administrator> $ssxml.jivesitesettings.socialtargets.socialtarget AccessControl JiveGroupType JivePlaceId JivePlaceName JivePlaceType UserAccountForAccess : : : : : : AllowMetaData 0 1001 Marketing 700 SP2007\kliemohn To clear out the settings simply do the following. Make sure you have saved your site settings into a local variable ($ss) first in case you want to set them back! $web.properties["jive.sitesettings"] = "" $web.properties.update() If you go to your site socialization page you should see a notice in red that "This site is inheriting Jive Socialization Settings from its parent site." In addition, the rest of the screen should be disabled with the "No Socialization" option selected. To change your site settings back simply do the following: $web.properties["jive.sitesettings"] = $ss $web.properties.update() Now if you go to your site socialization page you should see it back the way it was before. If you want to modify just pieces of the settings you can do something like the following: Jive Connects for Microsoft SharePoint - 12

$ssxml.jivesitesettings.streamingenabled = "false" $web.properties["jive.sitesettings"] = $ssxml.outerxml $web.properties.update() SharePoint 2010 Open the PowerShell command prompt on the SharePoint server by navigating to Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell. To view the settings: $web = Get-SPWeb <site_url> $ss = $web.properties["jive.sitesettings"] $ss For example: PS C:\Users\Administrator> $web = Get-SPWeb http://sharepoint.redlinkmobile.local/marketing PS C:\Users\Administrator> $ss = $web.properties["jive.sitesettings"] PS C:\Users\Administrator> $ss <jivesitesettings xmlns="http://jive.com/sharepoint/administration" xmlns:i="http:// www.w3.org/2001/xmlschema-instance" ><InheritParentSettings>false</InheritParentSettings><DefaultJiveInstanceId>1</ DefaultJiveInstanceId><SocializationEnab led>true</socializationenabled><socialtargets xmlns:a="http://schemas.datacontract.org/2004/07/ Jive.SharePoint.Common.A dministration"><a:socialtarget><a:accesscontrol>allowmetadata</ a:accesscontrol><a:jivegrouptype>0</a:jivegrouptype><a:j iveplaceid>1001</a:jiveplaceid><a:jiveplacename>marketing</ a:jiveplacename><a:jiveplacetype>700</a:jiveplacetype><a:use raccountforaccess>sp2010\kliemohn</a:useraccountforaccess></a:socialtarget></ SocialTargets><StreamingEnabled>true</Stre amingenabled><socializedsite>http://jive.redlinkmobile.local/rpc/rest/spintegration/ sites/1000</socializedsite></jivesi tesettings> If you want to see the XML a little nicer you can copy the text out of the output and paste it in notepad and then format it. Or, you can do the following: $ssxml = [xml]$ss $ssxml.jivesitesettings $ssxml.jivesitesettings.socialtargets.socialtarget For example: PS C:\Users\Administrator> $ssxml = [xml]$ss PS C:\Users\Administrator> $ssxml.jivesitesettings xmlns i InheritParentSettings DefaultJiveInstanceId SocializationEnabled SocialTargets StreamingEnabled SocializedSite : : : : : : : : http://jive.com/sharepoint/administration http://www.w3.org/2001/xmlschema-instance false 1 true SocialTargets true http://jive.redlinkmobile.local/rpc/rest/spintegration/sites/1000 PS C:\Users\Administrator> $ssxml.jivesitesettings.socialtargets.socialtarget AccessControl JiveGroupType JivePlaceId JivePlaceName JivePlaceType UserAccountForAccess : : : : : : AllowMetaData 0 1001 Marketing 700 SP2010\kliemohn To clear out the settings simply do the following. Make sure you have saved your site settings into a local variable ($ss) first in case you want to set them back! Jive Connects for Microsoft SharePoint - 13

$web.properties["jive.sitesettings"] = "" $web.properties.update() If you go to your site socialization page you should see a notice in red that "This site is inheriting Jive Socialization Settings from its parent site." In addition, the rest of the screen should be disabled with the "No Socialization" option selected. To change your site settings back simply do the following: $web.properties["jive.sitesettings"] = $ss $web.properties.update() Now if you go to your site socialization page you should see it back the way it was before. If you want to modify just pieces of the settings you can do something like the following: $ssxml.jivesitesettings.streamingenabled = "false" $web.properties["jive.sitesettings"] = $ssxml.outerxml $web.properties.update() Using Jive and SharePoint Together This section helps you use Jive with SharePoint. It also enables you to make the most of the Jive web parts and socialization features now available in SharePoint. Note: Before you start using Jive Connects for SharePoint, we recommend logging into the Jive interface. Logging into Jive synchronizes your identity between the Jive community and your SharePoint site, ensuring that all the parts of the system can talk to one another and you have access to all the information your permissions support. Viewing SharePoint Content in Jive Learn how to use Jive to display SharePoint content and migrate content to SharePoint. From Jive, you can search SharePoint (page 20), view SharePoint lists (page 19), and use widgets that display SharePoint information. Find out more about the four SharePoint-centric widgets: Recent Activity (page 14), SharePoint Sites (page 15), SharePoint List (page 16), and SharePoint Calendar (page 17). You can also migrate content that you created (page 19) in Jive to live in SharePoint. Note: The SharePoint-centric widgets are only available within a Jive place and they are not available within a Jive place until a SharePoint site has been socialized to it by a SharePoint site administrator. Using Recent Activity Widgets You can add a SharePoint Recent Activity widget to a place (group, space, or project) that has been socialized with a SharePoint site. Only place administrators have the ability to customize and add widgets to their places. For more on socializing places see Configuring Socialization for a Site (page 55). The Recent Activity widget is part of the Jive core product and is not distributed with the SharePoint Connector plugin. Within the context of SharePoint integration, the Recent Activity widget is designed to surface SharePoint "activities" (activity stream). The Recent Activity widget will show a preview of the content and present the contributing user along with when the activity was performed. Jive Connects for Microsoft SharePoint - 14

Note: The preview of SharePoint content is shown or not shown depending on socialization settings specified within SharePoint. They are only shown if all members of the Jive place are allowed to see socialized content regardless of their ability to access SharePoint. Recent Activity Widget Configuration The configuration for the Recent Activity widget (within the context of SharePoint) is driven by the socialization settings established in SharePoint. There are no additional configuration options to set in Jive. Using SharePoint Sites Widgets You can add a SharePoint Sites widget to a place (group, space, or project) that has been socialized with a SharePoint site. Only place administrators have the ability to customize and add widgets to their places. For more on socializing places see Configuring Socialization for a Site (page 55). The SharePoint Sites widget is designed to surface the hierarchy of SharePoint site(s) based on how socialization is established or "mapped" in SharePoint. The SharePoint sites widget shows the SharePoint site names, last modified time, and provides a link to directly take a Jive user into the respective SharePoint site. Adding a SharePoint Widget: To add the SharePoint widget to a place: 1. 2. 3. 4. 5. Navigate to the group, space, or site. Click Customize in the Overview tab. When the widget layout canvas opens, select Other, and then select the SharePoint widget. Drag the Drag to Add button to where the widget should show up. Click Publish Layout when you're done. SharePoint Sites Widget: SharePoint Sites Widget Configuration The configuration for the SharePoint Sites widget is controlled by how the Jive space, project, or group is "mapped" in the Jive Socialization Settings configuration for a designated SharePoint site. No additional configuration is required and/or available in Jive. Note: The SharePoint Site widget will not appear as an option unless the specific Jive space, project, or group has been "mapped" for socialization in SharePoint. Jive Connects for Microsoft SharePoint - 15

Image Description The SharePoint Site widget only shows the site that is mapped for socialization along with the SharePoint sites one level below the "mapped" SharePoint site. Using SharePoint List Widgets You can add a SharePoint List widget to a place (group, space, or project) that has been socialized with a SharePoint site. Only place administrators have the ability to customize and add widgets to their places. For more on socializing places see Configuring Socialization for a Site (page 55). The SharePoint List widget is designed to surface SharePoint list content (including Edit item action) availability within Jive. SharePoint lists represent core functionality within SharePoint to structure, store, and make collaborative content available to users. SharePoint layers on the concept of views (shared or specific to a user) to further refine how list content is presented. The SharePoint list widget takes advantage of the power of SharePoint lists and views and allows a Jive user to view and interact with the list content. Note: In viewing SharePoint images within a list widget, you might be prompted for your name and password, or see a broken image icon. To prevent this consider choosing a view from the list that does not show an image field. Adding a SharePoint Widget: To add the SharePoint widget to a place: 1. 2. 3. 4. 5. Navigate to the group, space, or site. Click Customize in the Overview tab. When the widget layout canvas opens, select Other, and then select the SharePoint widget. Drag the Drag to Add button to where the widget should show up. Click Publish Layout when you're done. Configuring the List Widget: To configure the SharePoint List widget, click the down-arrow in the top right corner to open the edit view as seen in the following image. Jive Connects for Microsoft SharePoint - 16

The configuration for the SharePoint List widget requires several pieces of information to find and surface a SharePoint list (and optional "custom" view). 1. Custom Title (Optional): Type the value to display above the SharePoint List widget. 2. Site Name: Keep this blank for a list in the site associated directly with this Jive place. Enter the name of a sub-site if the list is located in a sub-site to the associated SharePoint site. 3. List Name: Type name of the list in SharePoint for the socialized site. Note: The List Name field is case sensitive. Please ensure the value you provide matches SharePoint. 4. View Name (Optional): If left blank, the default view from SharePoint will be used; If specified, the SharePoint List widget will attempt to find and use the view name. Note: If you leave the View Name blank and notice the list shows in Jive with unwanted fields, please review (or create) the available views in SharePoint to refine what is displayed in Jive. When you click Save Properties and publish the layout, the SharePoint List widget should display on the space Overview pages as shown in the following image. Using SharePoint Calendar Widgets You can add a SharePoint Calendar widget to a place (group, space, or project) that has been socialized with a SharePoint site. Only place administrators have the ability to customize and add widgets to their places. For more on socializing places see Configuring Socialization for a Site (page 55). Adding a SharePoint Widget: To add the SharePoint widget to a place: 1. 2. 3. 4. 5. Navigate to the group, space, or site. Click Customize in the Overview tab. When the widget layout canvas opens, select Other, and then select the SharePoint widget. Drag the Drag to Add button to where the widget should show up. Click Publish Layout when you're done. Configuring the Calendar Widget: To configure the SharePoint Calendar widget, click the down-arrow in the top right corner to open the edit view as seen in the following image. Jive Connects for Microsoft SharePoint - 17

The configuration for the SharePoint Calendar widget requires the following information to find and surface a SharePoint calendar. Custom Title (Optional) - Type the value to display above the SharePoint Calendar widget. Site Name: Keep this blank for a calendar in the site associated directly with this Jive place. Enter the name of a sub-site if the calendar is located in a sub-site to the associated SharePoint site. Name of Calendar: Type the name of the Calendar List or Custom List (if it uses a calendar view) exactly as used in SharePoint for the socialized site. For example, "Calendar." Note: The Name of Calendar field is case sensitive. Please ensure the value you provide matches the one used in SharePoint. View Name: Keep this blank unless you want to filter the contents of the calendar to contain a subset of the calendar entries in which case you would enter the name of the SharePoint view configured on the calendar that filters the contents. Viewing the Calendar Widget: The following images shows the SharePoint calendar in a wide column view. The SharePoint Calendar widget is designed to present a specific SharePoint calendar in Jive. The SharePoint Calendar widget can display a month view, week view, or day view. It will also show individual event title and timeframe, along with a link back to the physical appointment/calendar item in SharePoint. The following images shows the SharePoint calendar in a wide column view. The SharePoint Calendar widget will dynamically change to a day view to conserve space on the screen. This happens Jive Connects for Microsoft SharePoint - 18

automatically based on available screen space for the current Jive page layout and does not require user configuration. Adding SharePoint Lists to Jive Content If you want to surface SharePoint lists in Jive, you can add them to Jive content. You can enhance Jive content by inserting snapshots of SharePoint lists. These lists can be viewed, but not edited, in Jive. However, the view you see in Jive preserves certain links so when you click them, you are redirected to the source and the SharePoint site. You must have the proper SharePoint permissions to actually open the links. To add a sharepoint list: 1. Create or edit a document, discussion, or blog post in Jive. 2. Click the Add SharePoint List icon in the toolbar of the content editor. 3. Select the SharePoint list you want to see in your Jive content. 4. Click Publish to post your Jive content. Migrating to SharePoint The "Migrate to SharePoint" action appears when a new Jive document is uploaded to a Jive space, project, or group that has been configured for socialization with SharePoint. Note: This feature is only available for documents uploaded to Jive. It is not available for document written using Jive's editor. When a user clicks the action to "Migrate to SharePoint", a screen similar to the one below will be presented to user to select the target SharePoint document library. Jive Connects for Microsoft SharePoint - 19

Migrate to SharePoint Configuration The configuration for the "Migrate to SharePoint" feature is added automatically when the SharePoint Connector plugin is installed and the containing Jive space, project, or group is configured for socialization to SharePoint. Searching SharePoint From Jive The results should appear in a tabbed format similar to what's shown below. Example Jive Search Results Example SharePoint Search Results Jive Connects for Microsoft SharePoint - 20

Using Web Parts in SharePoint This section presents each of the Jive web parts that can be used in SharePoint. This includes an example of what each web part looks like, followed by the specific SharePoint web part editor options. Note: Remember that SharePoint 2007 is fully supported only on Internet Explorer. For more information about Microsoft's browser support for SharePoint, see Plan browser support (Office SharePoint Server) and Plan browser support (SharePoint Server 2010). Managing Jive Web Parts The Jive for SharePoint web parts provide access to Jive functionality from within SharePoint. The following section describes how to add one or more of the Jive web parts to a SharePoint page. Adding Jive Web Parts: 1. In SharePoint (assuming you have access to Edit Page content), click Site Actions > Edit Page. The page should change to expose one or more web part zones. Each zone represents an area on the page that can accept web parts. 2. To add a web part, click Add a Web Part in the desired zone. 3. Select check boxes for the Jive web parts you want, then click the Add button. If the web parts do not show in the list of available web parts, make sure the Jive Web Parts feature is activated. See Activating and Deactivating Jive Web Parts for more information. Jive Connects for Microsoft SharePoint - 21

4. Depending on the web part, you may need to access the "editor" part (configuration panel) for each web part to select the Jive installation (see Managing Jive Installations (page 50) ) and update the unique web part configuration settings. 5. Once you are done adding/configuring web part, click on Exit Edit Mode (near top right of the screen). Activating and Deactivating Jive Web Parts: You can activate or deactivate Jive Web Parts. To get to the Jive Web Parts feature, log in as a Site Collection Administrator, then click Site Actions > Site Collection Features. If the feature is not activated, you can activate it by clicking its Activate button next to the Jive Web Parts feature. Note: Deactivating the Jive Web Parts feature removes the Jive Settings link from the Site Settings page, but it does not remove or hide already configured web parts. Also, if you deactivate and then reactivate, none of your settings are lost. However, if you delete the web parts from a page, you'll lose the placement of the web part and settings it has. Note that running the installer to uninstall the connector from SharePoint deactivates the features. So, it has similar behavior in that the web parts are not removed from the page, but if you re-install they will be functional again without losing their settings. Editing a Jive Web Part: A web part's editor contains a single configuration item specific to Jive. This is a drop down item you can use to select a Jive installation. Note: SharePoint provides an option to provide specific dimension settings (height and width) for each web part. While you'll get best results if you keep the defaults, if you decide to set the height and width, please experiment with your desired settings to ensure full access to the web part user interface. Jive Connects for Microsoft SharePoint - 22

Using the Places Web Part The Places web part is used in SharePoint to allow a user to "Follow" and browse Jive places (spaces, projects, and groups). As you place your mouse over (or hover) each space, project, or group, a Jive popup is shown to provide more details about the respective Jive content. There also an option at the bottom of each popup dialog to "Follow" the space, project, or group. Please see Managing Jive Web Parts (page 21) for more information on how to add a Places web part to a SharePoint page. Sample Places Web Part Panels Places Web Part Panels Jive Connects for Microsoft SharePoint - 23

Your Places Spaces Projects The "Your Places" panel shows The "Spaces" panel shows a all the Spaces, Projects, complete list of Jive Spaces Groups that you have available to "Follow" selected to "Follow" from Jive. It will also list the SharePoint sites that you have selected to "Follow" from SharePoint. The "Projects" panel shows a complete list of Jive Spaces available to "Follow" Places Web Part Panels (continued) Groups SharePoint Sites The "Groups" panel shows a complete list of Jive Spaces available to "Follow" The "SharePoint Sites" panel shows a complete list of SharePoint Sites available to "Follow" Example of Places Web Part Popup Dialog Jive Connects for Microsoft SharePoint - 24

Note: Please see Example of the Web Part Editor on Managing Jive Web Parts (page 21) for an example of the Places web part editor. Using the Recent Content Web Part Please see Managing Jive Web Parts (page 21) for more information on how to add a Recent Content web part to a SharePoint page. Sample Recent Content Web Part Image Description The Recent Content web part is designed to display content from a selected Jive space, project, or group. The type of content is presented along with when it was created/modified, who created the content, and a link to access the content directly in Jive. Sample Recent Content Web Part - User Profile Jive Connects for Microsoft SharePoint - 25

Image Description The Recent Content web part also presents a popup dialog describing the user profile that created/modified the content. This popup shows basic profile details, additional content the user has worked on, and provides a SharePoint user with the ability to "Follow" the user in Jive. Recent Content Web Part Editor Image Description The editor for the Recent Content web part contains configuration options in addition to the Jive instance as shown on Managing Jive Web Parts (page 21). 1. Number of Results - This item must be a numeric value to limit the number of items to display at once on the page. 2. Jive Place - This item determines which Jive place (space, project, or group) for which the recent content is shown. Note: SharePoint provides an option "out of the box" to provide specific dimension settings (Height and Width) for each web part. For this web part, the recommendation is to keep the default Height and Width settings. If you decide to set the Height and Width, please experiment with your desired settings to ensure full access to the web part user interface. Using the Watch a Tag Web Part Please see Managing Jive Web Parts (page 21) for more information on how to add a "Watch a Tag" web part to a SharePoint page. "Watch a Tag" Web Part Jive Connects for Microsoft SharePoint - 26

Image Description The "Watch a Tag" web part is designed to surface Jive content that has been "tagged" with one or more specified Jive metadata tags. In the case of the example to the left, the web part has been configured to surface/show Jive content that has been tagged with the terms "netbook" and "news". "Watch a Tag" Web Part Editor Settings Image Description The editor for the "Watch a Tag" web part contains configuration options in addition to the Jive Instance as shown on Managing Jive Web Parts (page 21). 1. Tags - This can consist of one or more terms/tags separated by spaces or commas. 2. Number of Results: Limits the number of results to surface; the default is 25 items. 3. Show Videos - Yes or No; Allow Jive video content to show or not to show. 4. Show Documents - Yes or No; Allow Jive document content to show or not to show. 5. Show Discussions - Yes or No; Allow Jive discussion content to show or not to show. 6. Show Bookmarks - Yes or No; Allow Jive bookmark content to show or not to show. 7. Show Blog Posts - Yes or No; Allow Jive blog post content to show or not to show. Note: SharePoint provides an option "out of the box" to provide specific dimension settings (Height and Width) for each web part. For this web part, the recommendation is to keep the default Height and Width settings. If you decide to set the Height and Width, please experiment with your desired settings to ensure full access to the web part user interface. Using the Federated Search Web Part The Federated Search web part is designed to enable searching for community content from within SharePoint. The web part can be configured in two ways. Please see Managing Jive Web Parts (page 21) for more information on how to add a Federated Search web part to a SharePoint page. Default Configuration In the Default Configuration simply place the web part on any web part page and choose to keep the "Display Search Box" checkbox enabled. The user will be able to enter search terms and click the magnifying glass to see results. Jive Connects for Microsoft SharePoint - 27

Targeted for Windows SharePoint Services (WSS 3.0/SharePoint Foundation; also can be used this way in MOSS 2007/SharePoint Server 2010). Provides standalone search functionality. Can be used on any web part page. Federated Configuration In the Federated Configuration place the web part on a Microsoft Office SharePoint Server (MOSS) 2007 / SharePoint Server 2010 search results page (e.g., "/SearchCenter/Pages/Results.aspx") and choose to uncheck the "Display Search Box" checkbox. When a search is done from SharePoint, the search results page will show SharePoint search in one web part and community search results in another web part. Note: Removing the search box makes the Federated Search web part useless in some contexts. In other contexts, such as the MOSS search page, it might be a desired option to make use of the?k= query string, for example. Jive Connects for Microsoft SharePoint - 28

Typically configured with Microsoft Office SharePoint Server (MOSS) 2007 / SharePoint Server 2010. Used to show results from the community and to reside on the same search results page as other search result web parts. Must be configured on a "search results" page to show next to SharePoint search results (as shown above). Note: The web part editor (see Federated Search Web Part Editor Settings below) allows a SharePoint user to define the default usage settings (sorting, filter, result limit). Federated Search Web Part - User Profile Image Description The Federated Search web part also presents a popup dialog describing the user profile that created/modified the content. This popup shows basic profile details, additional content the user has worked on, and provides a SharePoint user with the ability to "Follow" the user in Jive. Federated Search Web Part Editor Settings Jive Connects for Microsoft SharePoint - 29

Image Description The editor for the Federated Search web part contains configuration options in addition to the Jive Instance as shown on Managing Jive Web Parts (page 21). 1. Jive Search: Display Search Box - This checkbox toggles the display of the search text box. Note: The option to toggle this item off is useful when the Federated search web part is used in a MOSS 2007/SharePoint Server 2010 search results page. Typically, in a search results page, another search text box would drive the search criteria, and this Federated search web part would return results alongside other search result web parts. 2. Jive Search: Display Search Options - This checkbox toggles the toolbar that provides additional search result filters (Sort, Content Type, Last Modified) 3. Sort by - This sets the default sort to be by Relevance, Date, or Subject (The web part interface has an option to override this configuration for each set of search results. 4. Show content types - This sets the default content type (All, Documents, Discussions, etc.) for the search results. (The web part interface has an option to override this configuration for each set of search results) 5. Show if modified - This sets the default last modified filter (anytime, in the past day, etc.) for the search results. (The web part interface has an option to override this configuration for each set of search results) 6. Number of Results - This item must be a numeric value to limit the number of search results to display at once on the page. Note: SharePoint provides an option "out of the box" to provide specific dimension settings (Height and Width) for each web part. For this web part, the recommendation is to keep the default Height and Width settings. If you decide to set the Height and Width, please experiment with your desired settings to ensure full access to the web part user interface. Using the Freedom Web Part The Freedom web part provides links that pull SharePoint users into the Jive community. Please see Managing Jive Web Parts (page 21) for more information on how to add a Freedom web part to a SharePoint page. Freedom Web Part - Default/Closed Image Description The Freedom web part is designed to take a portion of the screen to provide access for a SharePoint user to launch Jive-specific actions (in Jive). Freedom Web Part - Expanded Jive Connects for Microsoft SharePoint - 30

Image Description The Freedom web part will toggle between collapsed and expanded view to show/hide Jive-specific actions. These actions include the ability to start a discussion, create a document, create a blog post, create a video, and create a task. Note: Please see Example of the Web Part Editor on Managing Jive Web Parts (page 21) for an example of the Places web part editor. This is the same as the editor for the Freedom web part. Using the Socialization Features This section presents the socialization features beyond the included web parts and activity stream integration. User and Jive Container Pop-up Profiles The following image shows an example of a User Profile Popup. This Popup appears in SharePoint to mimic the related User Profile Popup from Jive. Notice the user avatar, email address, participation level, and last five most recent documents are shown. There is also a link to Follow (or Stop Following) a specific user in Jive. The Follow/Stop Following functionality is available from within Jive search results and the Jive web parts. The following image shows how a Jive group is summarized in SharePoint when a user hovers over a link to the group. A similar popup is available for Jive spaces and projects. The popup also allows a user to join or leave the respective group. Jive Connects for Microsoft SharePoint - 31

Using the Document Menu Items and Item Status The Document Menu Item integration and Item Status provides the "List Item" or third layer (four layers total) of socialization administration. The List Item layer is designed to be controlled by individual contributors of the SharePoint site. This layer is used to control the socialization Activity Stream for each document item. The context menu for each individual document will contain the available actions (Disable Jive Activity Streams, Enable Jive Activity Streams, "Copy To" Jive Space, Project, or Group) Note: Notice the initial icons to the left of each document. The green Jive icon represents that the Activity Stream is active and enabled for the item. The grayed out Jive icon represents that the Activity Stream has been disabled for the item (could be that a user clicked the "Disable Jive Activity Streams" as shown in the image above). The Jive icon with the red line crossed through it represents that the Activity Stream has been blocked for the item. This is facilitated through the Administrative level as a Corporate Policy. For the "blocked" items above, the documents were created with a SOX SharePoint content type. Policy has been configured to "block" all documents based on this content type. Here is another example of an item context menu. Since Activity Streams have been disabled, notice how the option to "Enable Jive Activity Streams" is presented. There is also an option to "Copy to Jive" (Space, Projects, or Groups). The "Copy To Jive" functionality ties into the fourth layer of socialization. There is a "Copy to Jive" workflow available as well (see Using the "Copy to Jive" Workflow (page 33) for more details.) Note: You can perform a Copy To Jive action as long as you have write access in the Jive place you're choosing as the destination. In other words, read access in SharePoint is all that's needed to perform a Copy To. Jive Connects for Microsoft SharePoint - 32

Using the "Jive Copy Document" Workflow The "Jive Copy Document" workflow can be controlled by SharePoint site contributors. This layer is used to specify the Jive place where you can copy documents. You can perform a Copy To Jive action as long as you have write access in the Jive place you're choosing as the destination and read access in SharePoint. Note: To use the workflow you must have the "Jive Copy To Workflow" site collection feature activated. You can activate this feature for a site collection during installation, but if you don't, then you can manually activate it later. To activate the "Jive Copy To Workflow" site collection feature, log in as a site collection administrator and go to Site Settings > Site Collection features on the root site in your site collection. Here you can activate the "Jive Copy To Workflow" feature. Note that this feature can only be used on SharePoint libraries, not on regular SharePoint lists. The following list explains the Jive Copy Document workflow and how it depends on the access a Sharepoint user has in Jive. Workflow Association Workflow association requires that the list manager (the user making the workflow association) has access to Jive because this user must select a default Jive place for the destination of the copy operation. Selecting the place requires that the user navigate the Jive places and therefore the user must have access to Jive. Manual Workflow Initiation Manual workflow initiation involves the screen where the user may potentially override the Jive place chosen at association time. Even if the configuration does not allow an override, this operation currently requires that the user starting the workflow have access to Jive. If users may not have access to Jive and you want them to be able to run the workflow, consider having the workflow start automatically on add and/or update and turn off manual initiation. Populate Metadata Fields This operation occurs automatically when the workflow is run. If checked, the users who initiate the workflow (either through manual initiation or automatic initiation) must have access to Jive. If the users may not have access to Jive, leave this option unchecked. Copy Document Physically copying the document from SharePoint to Jive when the workflow runs requires that the user initiating the workflow (either through manual initiation or automatic initiation) has write access to the destination Jive place. This is true except for the following conditions: If there is a SharePoint Location defined within Jive that would handle this SharePoint site, then the "Content Copied from SharePoint" setting for that SharePoint Location determines how/if the document is copied based on the SharePoint user's privilege within Jive. For more on this, see Adding a SharePoint Location (page 69). If there is no SharePoint Location defined within Jive that would handle this SharePoint site, then the "sharepoint.default.copytojive.username" Jive system property must be set to a valid Jive user if the user does not have write access and the copy is to succeed. For more on this, see System Properties for SharePoint (page 78). Jive Connects for Microsoft SharePoint - 33

Associating the Jive Copy Document Workflow to a SharePoint Document Library: Before the Jive Copy Document workflow can be used within a SharePoint document library, it must be associated to the document library by a manager of that library. To associate the Jive Copy Workflow to the SharePoint document library: 1. Select the document library where you want to associate the workflow. 2. Navigate to the workflow settings page using the following instructions for the appropriate version of SharePoint. SP 2007: Choose Settings --> Document Library Settings and then click Workflow settings --> Add a Workflow. SP 2010: From the ribbon, select Library --> Workflow Settings --> Add a Workflow. 3. When the Add a Workflow page opens, select Jive Copy Document from the list of workflow templates as shown in the following image. Note: If the Jive Copy Document workflow template is not shown in this list, you either need to activate the "Jive Copy To Workflow" feature as noted in the beginning of this topic, or if you have recently upgraded, see Allowing New Instances for Jive Copy Workflow (page 36). 4. Enter the name of the workflow and either use the default information for the remaining Task List, Workflow History List, or Start Options fields or change them In the Start Options field, you can specify whether you want the workflow started manually and/or automatically when a document is created or updated. 5. Click Next. 6. Complete the Jive Copy Document Workflow form using the following information to help you. The previous list (page 33) provides more on SharePoint user access to Jive. Field Description Jive Instance Select a Jive Instance that you can access. If you want to give users the opportunity to change the Jive Instance when they manually run the workflow, select the Allow users to override box. Jive Place Name Click Browse to select a place where documents can live when you run this workflow and it copies the documents to Jive. If you want to give users the opportunity to change the Jive Place Name when they manually run the workflow, select the Allow users to override box. Populate Metadata Fields Select this option to populate additional metadata fields in this document library when the workflow runs. When selected, Jive saves the information about when the document was last copied to a specific Jive place and who last copied the document to a specific Jive place. If some users running this workflow do not have access to Jive, you need to uncheck Create SharePoint metadata fields and make sure the workflow is not allowed to run manually. Instead, the workflow should run automatically on adding and updating documents as specified in Start Jive Connects for Microsoft SharePoint - 34

Field Description Options field described previously in Step 4. Metadata should not be popluated. Jive Tags Select one or more fields to be translated as tags in Jive when you run this workflow on a document. Create these fields by adding columns in the document library before you create this workflow. You can use Single Line of Text, Choice, Lookup, and Calculated fields to create tags in Jive. These fields may be multi-value choice fields (check boxes) and multi-value lookup fields, which transfer multiple tags. One tag is transferred to Jive for each value chosen. For example, if the choices are blue, green, and red, and the user selects blue and green, then both a blue and a green tag are associated with the document in Jive. Regardless of whether it is a single- or multi-value field, each value is considered an entire tag, but some special characters may be changed: Spaces become underscores (_) Double quotes (") and single quotes (') are removed Commas (,) become semicolons (;) Backslash (\) becomes a front slash (/) Less than and greater than signs (< >) when put together in that order become underscore (_) Note: If you are running this workflow automatically on document updates, you should make at least one field in your library a required field in addition to the Name field. This ensures that tag values are available when the workflow runs. 7. Click OK. Launching the Jive Copy Document Workflow: After you configure the Jive Copy Workflow to a document library, you can manually launch the workflow by performing the following steps. 1. In the document library, click the down-arrow next to the desired document and select Workflows as shown in the following image. 2. Click the workflow you want to run. This example uses "Jive Copy Document" as shown in the following image. Jive Connects for Microsoft SharePoint - 35

Note: If your workflow used to show in this list, and you have recently upgraded, see Allowing New Instances for Jive Copy Workflow (page 36) 3. If set for user override, you can select new Jive Instance and Jive Place Name choices. 4. Click OK. Allowing New Instances for Jive Copy Workflow When attempting to launch a Jive Copy workflow, if your workflow no longer shows in the list if available workflows, the workflow may have been changed to no longer allow new instances. This happens when the SharePoint Connector is upgraded or if you disable and re-enable the Jive Copy To Workflow feature in a site collection. To allow new instances for your Jive Copy workflow: 1. Navigate to the document library as a list manager, for example as a site owner. 2. Navigate to workflow settings using the following instructions for the appropriate version of SharePoint. SP 2007: Choose Settings > Document Library Settings > Workflow settings. SP 2010: From the ribbon choose Library > Workflow > Workflow Settings. 3. Click Remove a workflow. We are not actually removing a workflow even though the text seems to suggest it. 4. For any Jive Copy workflows, change from "No New Instances" to "Allow" and click OK. The Jive Copy Workflow name is determined at the time the workflow is associated. Setting up SharePoint Jive Connects for Microsoft SharePoint provides tight integration between SharePoint and Jive. It takes SharePoint s strengths as a content repository with complex workflows and document management and couples them with Jive s social networking capability, intuitive interface, and high adoption rate. This section covers the features within SharePoint and is intended for SharePoint IT administrators. It includes technical installation and configuration of the SharePoint features, followed by more technical concepts around the SharePoint features. To learn more about the features within Jive, see Managing the Features (page 65). > Important: Before you begin, refer to the Read Me (page 3), which helps you prepare for configuring Jive and SharePoint. Authentication Scenarios (page 84) describes two authentication scenarios used to demonstrate the integration between SharePoint and Jive. These scenarios provide some extra guidance and may help relate to your requirements. Note: Remember that SharePoint 2007 is fully supported only on Internet Explorer. For more information about Microsoft's browser support for SharePoint, see Plan browser support (Office SharePoint Server) and Plan browser support (SharePoint Server 2010). Jive Connects for Microsoft SharePoint - 36

Installing, Upgrading, and Deploying the SharePoint-Side Plugin This section describes the SharePoint prerequisites and basic SharePoint-side plugin installation steps. The Special Cases (page 45) section describes how to overcome some common issues encountered when installing the Jive for SharePoint. SharePoint Plugin Installation Requirements The Jive for SharePoint requires the following items to be configured prior to installation. Note: Anonymous access to SharePoint should not be allowed for any site collection where the Jive Web Parts feature is activated. Anonymous users will be prompted to log in as they use pages in the site collection. Microsoft Office SharePoint Server (MOSS) 2010, Microsoft Office SharePoint Foundation 2010, Microsoft Office SharePoint Server (MOSS) 2007, Windows SharePoint Services (WSS) 3.0 The value added with MOSS 2007 regarding Jive Connects for Microsoft SharePoint is that the Jive Federated Search web part can be placed on a MOSS search results page so that SharePoint search results can be shown side-by-side with Jive search results. Note: These results are not intermixed/inline. Microsoft.NET Framework 3.5 SharePoint 2010 SharePoint 2010 requires Microsoft.NET Framework 3.5. SharePoint 2007 This comes with Windows Server 2008 R2 and is required for any web server with Windows Server 2008 R1 (it is a prerequisite for the server when turning the web feature on within the operating system). This does not come with earlier versions of Windows Server 2008 or any version of Windows Server 2003 (and will need to be installed for Jive integration). Available for download here (http://www.microsoft.com/downloads/details.aspx? FamilyID=333325fd-ae52-4e35-b531-508d977d32a6&DisplayLang=en) Version 3.5 of the.net Framework is supported with SharePoint 2007 as indicated here (http://technet.microsoft.com/en-us/library/cc288751(office.12).aspx) To search SharePoint content from Jive: Windows Domain Controller (separate server) and SharePoint configured to be a member of the respective domain. To perform credential delegation calls from Jive to SharePoint (using the search.svc), you must use the appropriate search configuration (see Configuring Search Results Security Trimming (page 61) ) and you must use domain accounts for both the SharePoint application pool owner accounts (the account authenticating to the web service) and the impersonation account (the SharePoint user). Installing the SharePoint-Side Plugin Use the instructions in this topic to install the SharePoint-side plugin. You must be logged directly into a SharePoint server using a SharePoint Administrator user account. This only needs to be performed on one server in the SharePoint farm (it will be disseminated to the others). See Special Cases (page 45) for additional installation/configuration scenarios. Note: If you use the installer to uninstall the features and subsequently install the features to only a subset of the site collections, it will activate the features on site collections not chosen the second time around if they were chosen the first time and the web application for the feature was also chosen. If you manually deactivate the features before uninstalling with the installer, they will not be activated the next time the installer runs unless chosen during the install. Overview The following section walks through the general procedure for installing the Jive plugin in the SharePoint environment. The procedure will install the following items in SharePoint. Jive Connects for Microsoft SharePoint - 37

Jive-specific Central Administration screens (see SharePoint Central Administration (page 49) ) Jive-specific Site Administration (Site Settings) screens (see SharePoint Site Settings (page 55) ) Jive Places web part (see Using the Places Web Part (page 23) ) Jive Recent Content web part (see Using the Recent Content Web Part (page 25) ) Jive "Watch a Tag" web part (see Using the "Watch a Tag" Web Part (page 26) ) Jive Federated Search web part (see Using the Federated Search Web Part (page 27) ) Jive Freedom web part (see Using the Freedom Web Part (page 30) ) "Copy To Jive" Functionality (page 33) (Workflow, SharePoint Designer Activity, Context Menu) Socialization Features (Status, enable/disable Context Menu, User Popup) Back end services used by both the SharePoint web parts and Jive widgets Installation Steps Note: Note that when installing, each target web application for the install will experience a web application restart as part of the installation process. 1. Save the provided Sharepoint connector.zip file to the desired location on your Sharepoint server. 2. Unzip the installation zip, then locate a file named Jive_SP_Connector_NetApplication_xxx.zip within it (where "xxx" is the version number). Unzip this file into a new folder. 3. Open the new folder from the previous step and click Setup_Jive.SharePoint.exe. 4. If you are running Windows Server 2008, if you're prompted with the Open File - Security Warning dialog box, click Run. 5. In the Jive SharePoint Connector welcome dialog box, click Next. 6. In the System Check dialog box, if all prerequisites pass, click Next (otherwise see Special Cases (page 45) ). 7. In the End-User License Agreement dialog box, read the license agreement, then select the I accept the terms in the License Agreement check box and click Next. 8. In the Site Collection Deployment Targets dialog box, choose the web application(s) and site collection(s) where you would like to deploy Jive for SharePoint (see following 2 screens). Click Next. Note: The SharePoint web parts are typically not installed to the Central Administration web application. The web.config associated with each targeted SharePoint web application will be modified as discussed in Changes to web.config On Installation (page 47). Jive Connects for Microsoft SharePoint - 38

9. 10. 11. 12. Note: See Deploying to New Web Applications and Site Collections (page 44) if you want to deploy to new web applications or site collections sometime later after the install process has completed. In the Installing dialog box, allow the installation to complete, then click Next. In the Installation Successfully Completed dialog box, review the status of the installation, then click Close. Note: If you get errors on activating site collection features, it might be because the current account running the installer (a farm administrator) is not a site collection administrator for those site collections. For each of these site collections you will need to log into them as a site collection administrator and go to Site Settings > Site Collection Features and activate the "Jive Web Parts" and "Jive Copy To Workflow" features. See also Deploying to New Web Applications and Site Collections (page 44). Please see Managing Jive Installations (page 50) for details on configuring Jive installations to use in SharePoint. > Important: Please ensure the Jive components have been installed in Jive before continuing. After installing please restart the Central Administration application pool to see the Jive-related links within Central Administration. This can be done by running IISRESET from a command line on each web front end, but that will also restart all application pools and not just the Central Adminstration application pool. Note: If you have SharePoint configured such that you have a server with Central Administration and no other web applications, then you won't be able to use the central administration screens provided with the connector. To remedy this, you can manually deploy the components to the web application and copy resource files to the App_GlobalResources directory. To do that, deploy the Jive.Sharepoint.wsp solution to the central admin web application (see Manually Installing the SharePoint-side Plugin (page 40) for more information). After you deploy, manually copy all JiveGlobalResources.* files from <12 Hive> \Resources to <central admin virtual directory>\app_globalresources. For example, copy C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\resources\jiveglobalresources.* to C: \Inetpub\wwwroot\wss\VirtualDirectories\12345\App_GlobalResources. Jive Connects for Microsoft SharePoint - 39

Uninstalling the SharePoint-Side Plugin The following procedure will not remove your existing SharePoint web parts and related settings. However, it will render the web parts unusable. If you subsequently install the connector, the prior settings are retained. If you use the installer to uninstall the features and subsequently install the features to only a subset of the site collections, it will activate the features on site collections not chosen the second time around if they were chosen the first time and the web application for the feature was also chosen. If you manually deactivate the features before uninstalling with the installer, they will not be activated the next time the installer runs unless chosen during the install. To uninstall the SharePoint-side Plugin: 1. Download the Jive-side plugin and extract the package to a desired location on your environment (such as a new folder on the Desktop of the SharePoint server). 2. Open the new folder from step 1 and click Setup_Jive.SharePoint.exe. 3. If you are running Windows Server 2008 and you're prompted by the Open File - Security Warning dialog box, click Run. 4. In the Jive SharePoint Connector dialog box, click Next. 5. In the System Check dialog box, if all prerequisites pass, click Next (otherwise see Special Cases (page 45) ). 6. In the Repair or Remove dialog box, click Remove to retract the current solution, then click Next. 7. In the Uninstalling dialog box, allow the removal to complete, then click Next. 8. Review the status of the uninstall and click Close. 9. Clean up Jive web parts. For more on this, see Cleaning up after Uninstalling (page 43). Troubleshooting Uninstallation: If you get an error message If you get an error during the uninstall, remove the following line of code from the C:\Inetpub\wwwroot \wss\virtualdirectories\<port>\web.config SharePoint file where "<port>" is the port that web site runs under on the server. <add name="jivepagecontroller" type="jive.sharepoint.services.httpmodules.jivesharepointhttpmodule,jive.sharepoint.services,version=1.0.0.0, > Note: Look for the previous line of within <system.web> and <httpmodules>. If you find this line in the web.config file, and you can't find the Jive.SharePoint.Services.dll in the Global Assembly Cache (C:\Windows\Assembly), SharePoint will be unaccessible for that web application Manually Installing the SharePoint-Side Plugin This topic walks through the general procedure for manually installing Jive for SharePoint in the SharePoint environment. This process can be used in place of the automated install discussed in Installing the SharePoint-side Plugin (page 37). Note: See Special Cases (page 45) for additional installation/configuration scenarios. The procedure will install the following items in SharePoint. Jive-specific Central Administration screens (see SharePoint Central Administration (page 49) ) Jive-specific Site Administration (Site Settings) screens (see SharePoint Site Settings (page 55) ) Jive Places web part (see Using the Places Web Part (page 23) ) Jive Recent Content web part (see Using the Recent Content Web Part (page 25) ) Jive "Watch a Tag" web part (see Using the "Watch a Tag" Web Part (page 26) ) Jive Federated Search web part (see Using the Federated Search Web Part (page 27) ) Jive Freedom web part (see Using the Freedom Web Part (page 30) ) "Copy To Jive" Functionality (page 33) (Workflow, SharePoint Designer Activity, Context Menu) Socialization Features (Status, enable/disable Context Menu, User Popup) Jive Connects for Microsoft SharePoint - 40

Back end services used by both the SharePoint web parts and Jive widgets Manual Installation Steps: To manually install Jive for SharePoint, you need to upload the solutions package, deploy the solution, and then activate the features. The following procedures describe how to complete the manual installation. Uploading the Solutions Package 1. Log into SharePoint's web application front end server using an account with Farm Administrator privileges in order to upload and deploy the.wsp 2. Open a command prompt and make sure your path is set with the SharePoint bin directory. Note: The following bin directory paths provide access to SharePoint 2007 and 2010: SharePoint 2007: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN SharePoint 2010: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN 3. Run stsadm -o addsolution -filename Jive.SharePoint.wsp in the directory containing the extraction of Jive_SP_Connector_NetApplication_102.zip Deploying the Solution 1. Open the SharePoint Central Administration in a browser. 2. Manage application features: In SharePoint 2007 a. Go to Central Admin > Operations > Solution Management. b. Select the Jive.SharePoint.wsp package and deploy it to the target web application(s). c. Select Central Admin > Application Management > Manage Web application features, and select the appropriate web application in the top right drop-down list. In SharePoint 2010 a. Go to Central Administration > Manage web applications. b. Select the Jive.SharePoint.wsp package and deploy it to the target web application(s). c. Select Manage Features. Note: If the deployment in the above steps fails, you can correct it by performing the following steps. a. Open a command prompt and set your path to the SharePoint bin directory as described above (page 41) in the Uploading the Solutions Package procedure. b. Type the following command stsadm -o deploysolution -name Jive.SharePoint.wsp -url http://sharepoint.mycompany.com -immediate -allowgacdeployment -force c. Run the command for each web application URL. You can replace "-url" with "-allcontenturls" to run for all URLs at once. To clear the Global Assembly Cache (GAC) for every web front-end, see "Upgrade Deployment Error: Cannot deploy solution Jive.SharePoint.wsp" in Special Cases Related to Jive for SharePoint Installation (page 45). d. Navigate to manage features. In SharePoint 2007: Select Central Admin > Application Management > Manage Web application features, and select the appropriate web application in the top right drop-down list. In SharePoint 2010: Select Manage Features. 3. Activate the Jive Infrastructure feature. If the "Jive Infrastructure" feature is already active you need to deactivate it and then re-activate it. 4. Select other web applications, and activate as appropriate. 5. Please see Managing Jive Installations (page 50) for details on configuring Jive installations to use in SharePoint. > Important: Please ensure the Jive components for Jive for SharePoint have been installed in Jive before continuing. Jive Connects for Microsoft SharePoint - 41

6. Restart the Central Administration application pool to view the Jive-related links within Central Administration. To do this, run IISRESET from a command line for each web front-end. This restarts all application pools, not just the Central Adminstration application pool. Activating the Features 1. Open the target site collection(s) in a browser. 2. Log in as a site collection administrator for that site. 3. Go to Site Actions > Site Settings > Site Collection Features. 4. Activate the Jive Web Parts feature and the Jive Copy To Workflow feature. Manually Uninstalling SharePoint-Side Plugin This topic walks through the general procedure for manually uninstalling the SharePoint-side plugin. This process can be used in place of the automated uninstall discussed in Uninstalling the SharePoint-side Plugin (page 40). Uninstallation Steps To manually uninstall the SharePoint-side plugin, you need to deactivate the site collection features, deactivate the web application feature, retract the solution, and delete the solution. The following procedure shows you how to complete the manual uninstall. 1. Deactivate the site collection features: a. Open each target site collection in a browser. b. Log in as site collection administrator. c. Go to Site Actions > Site Settings > Site Collection Features. d. Deactivate the Jive Web Parts and Jive Copy To Workflow features for each site collection. 2. Deactivate the web application feature: a. Open the SharePoint Central Administration in a browser b. Go to Central Admin > Application Management > Manage Web Application features c. Select the appropriate web application in the Web Application drop-down menu to the top right, and then deactivate the Jive Infrastructure feature. Repeat for each web application. 3. Retract the solution: a. Open the SharePoint Central Administration in a browser. b. Navigate to the path appropriate for your version of SharePoint. SharePoint 2007: Central Admin > System Settings > Manage Application features. SharePoint 2010: Central Admin > Operations > Manage farm solutions. c. Select jive.sharepoint.wsp d. After waiting for a minute or so, refresh your browser until you see "Not Deployed" as the status for jive.sharepoint.wsp. e. Select jive.sharepoint.wsp f. Click Remove Solution. 4. Clean up Jive web parts. For more on this, see Cleaning up after Uninstalling (page 43). Troubleshooting Uninstallation: If you get an error message If you get an error during web application feature deactivation, remove the following line of code from the C:\Inetpub\wwwroot\wss\VirtualDirectories\<port>\web.config SharePoint file where "<port>" is the port that web site runs under on the server. <add name="jivepagecontroller" type="jive.sharepoint.services.httpmodules.jivesharepointhttpmodule,jive.sharepoint.services,version=1.0.0.0, > Note: Look for the previous line of within <system.web> and <httpmodules>. Jive Connects for Microsoft SharePoint - 42

If you find this line in the web.config file, and you can't find the Jive.SharePoint.Services.dll in the Global Assembly Cache (C:\Windows\Assembly), SharePoint will be unaccessible for that web application Cleaning up After an Uninstall When you uninstall Jive for SharePoint, SharePoint does not remove the Jive web parts. This is the default behavior because some pages may still contain Jive web parts. However, once Jive for SharePoint is uninstalled, the Jive web parts no longer function. To clean up the non-functioning Jive web parts, log in as a site collection administrator for each site collection that has the Jive Web Parts feature activated and complete the following steps: 1. Go to Site Actions > Site Settings > Web Parts (under the Galleries group). 2. Click the Group heading and filter to "Jive." You should see the following web part files: FederatedSearchWebPart.webpart PlacesWebPart.webpart RecentContentWebPart.webpart SocializeContentLinksWebPart.webpart WatchATagWebPart.webpart 3. Click the Edit icon for each webpart file and then click the Delete button. You may have to re-filter the Group to "Jive" after deleting each one. Upgrading the SharePoint-Side Plugin This topic describes how to upgrade the SharePoint-side plugin. The upgrade process involves removing the old plugin, and then installing the new version. To upgrade, you must be logged directly into the SharePoint server using a SharePoint Administrator user account. See Special Cases (page 45) for additional installation/configuration scenarios. Note: If you'd rather upgrade manually, you can use our manual uninstallation and installation instructions instead of using the automatic installer (Setup_Jive.SharePoint.exe). For more on this, see Manually Uninstalling SharePoint-side Plugin (page 42) and then Manually Installing the SharePointside Plugin (page 40) Removing the Existing Version of the Connector (Part 1 of 3): The following procedure will not remove your existing SharePoint web parts and related settings. However, it will render the web parts unusable. If you subsequently install the connector, the prior settings are retained. If you use the installer to uninstall the features and subsequently install the features to only a subset of the site collections, it will activate the features on site collections not chosen the second time around if they were chosen the first time and the web application for the feature was also chosen. If you manually deactivate the features before uninstalling with the installer, they will not be activated the next time the installer runs unless chosen during the install. To uninstall the SharePoint-side plugin: 1. Download the Jive-side plugin and extract the package to a desired location on your environment (such as a new folder on the Desktop of the SharePoint server). 2. Open the new folder from step 1 and click Setup_Jive.SharePoint.exe. 3. If you are running Windows Server 2008 and you're prompted by the Open File - Security Warning dialog box, click Run. 4. In the Jive SharePoint Connector dialog box, click Next. 5. In the System Check dialog box, if all prerequisites pass, click Next (otherwise see Special Cases (page 45) ). 6. In the Repair or Remove dialog box, click Remove to retract the current solution, then click Next. 7. In the Uninstalling dialog box, allow the removal to complete, then click Next. 8. Review the status of the uninstall and click Close. 9. Clean up Jive web parts. For more on this, see Cleaning up after Uninstalling (page 43). Installing the New Version of the Connector (Part 2 of 3): After you've removed the old version of the connector, you can install the new version. Jive Connects for Microsoft SharePoint - 43

> Important: If Jive features are active on any site collection, you must either have the site collection admin deactivate features before the farm admin upgrades the.wsp or make the farm admin a site collection admin on the site collections where the features are active. 1. From the Jive SharePoint Connector package you downloaded and extracted, click Setup_Jive.SharePoint.exe. 2. If you are running Windows Server 2008 and you're prompted by the Open File - Security Warning, click Run. 3. In the Jive SharePoint Connector dialog box, click Next. 4. In the System Check dialog box, if all prerequisites pass, click Next (otherwise see Special Cases (page 45) ). 5. In the End-User License Agreement dialog box, read the license agreement, then select the I accept the terms in the License Agreement check box and click Next. 6. In the Site Collection Deployment Targets dialog box, choose the web application(s) and site collection(s) where you would like to deploy the SharePoint web parts (see following 2 screens). Click Next. Note: See Deploying to New Web Applications and Site Collections (page 44) if you want to deploy to new web applications or site collections sometime later after the install process has completed. 7. In the Installing dialog box, allow the installation to complete, then click Next. 8. In the Installation Successfully Completed dialog box, review the status of the installation and click Close. 9. Restart the Central Administration application pool to view the Jive-related links within Central Administration. To do this, run IISRESET from a command line for each web front-end. This restarts all application pools, not just the Central Adminstration application pool. Enabling Jive Copy Workflows (Part 3 of 3): When you perform an upgrade of the SharePoint-side plugin, all configured Jive Copy Workflow associations to any document libraries are disabled across your entire farm, preventing new instances from running. This also happens across an entire site collection if you simply disable and re-enable the Jive Copy To Workflow feature in a site collection. To correct this, SharePoint site administrators need to set their Jive Copy workflows to allow new instances. For detailed instructions, see Allowing New Instances for Jive Copy Workflow (page 36). Deploying to New Web Applications and Site Collections Deploying to New Web Applications If you create a new web application after SharePoint-side plugin has been installed and you want to make the Jive features available in this new web application you can use the Solution Management link from SharePoint Central Administration to deploy the solution to more web applications. Then activate the features as described below. To deploy the solution: 1. Open the SharePoint Central Administration in a browser. 2. Manage application features: In SharePoint 2007 a. Go to Central Admin > Operations > Solution Management. b. Select the Jive.SharePoint.wsp package and deploy it to the target web application(s). c. Select Central Admin > Application Management > Manage Web application features, and select the appropriate web application in the top right drop-down list. In SharePoint 2010 a. Go to Central Administration > Manage web applications. b. Select the Jive.SharePoint.wsp package and deploy it to the target web application(s). c. Select Manage Features. Note: If the deployment in the above steps fails, you can correct it by performing the following steps. Jive Connects for Microsoft SharePoint - 44

3. 4. 5. 6. a. Open a command prompt and set your path to the SharePoint bin directory as described above (page 41) in the Uploading the Solutions Package procedure. b. Type the following command stsadm -o deploysolution -name Jive.SharePoint.wsp -url http://sharepoint.mycompany.com -immediate -allowgacdeployment -force c. Run the command for each web application URL. You can replace "-url" with "-allcontenturls" to run for all URLs at once. To clear the Global Assembly Cache (GAC) for every web front-end, see "Upgrade Deployment Error: Cannot deploy solution Jive.SharePoint.wsp" in Special Cases Related to Jive for SharePoint Installation (page 45). d. Navigate to manage features. In SharePoint 2007: Select Central Admin > Application Management > Manage Web application features, and select the appropriate web application in the top right drop-down list. In SharePoint 2010: Select Manage Features. Activate the Jive Infrastructure feature. If the "Jive Infrastructure" feature is already active you need to deactivate it and then re-activate it. Select other web applications, and activate as appropriate. Please see Managing Jive Installations (page 50) for details on configuring Jive installations to use in SharePoint. > Important: Please ensure the Jive components for Jive for SharePoint have been installed in Jive before continuing. Restart the Central Administration application pool to view the Jive-related links within Central Administration. To do this, run IISRESET from a command line for each web front-end. This restarts all application pools, not just the Central Adminstration application pool. Activating Features in New Site Collections If you create a new Site Collection after Jive for SharePoint has been installed and want to use the Jive web parts or Copy to Jive workflow in the Site Collection, you need to navigate to the Site Collection "features" and click the Activate button for "Jive Web Parts" and "Copy To Jive Workflow". To activate the features: 1. Open the target site collection(s) in a browser. 2. Log in as a site collection administrator for that site. 3. Go to Site Actions > Site Settings > Site Collection Features. 4. Activate the Jive Web Parts feature and the Jive Copy To Workflow feature. Special Cases Related to SharePoint-Side Plugin Installation System Check: Administration Service Not Started You may encounter a problem with the check for the Administration Service (see red X below) while attempting to install the SharePoint-side plugin. Jive Connects for Microsoft SharePoint - 45

Please ensure you are logged into the SharePoint server as an Administrative account and execute the following steps. 1. Click the Abort button to stop the current installation. 2. Navigate to Services (For Microsoft Windows Server 2008, Click Start > Administrative Tools > Services). 3. Click the Name column to sort the list of services. 4. Find the service named Windows SharePoint Services Administration. 5. Right-click Windows SharePoint Service Administration, then click Start. 6. Try installing the plugin again (see Installing the SharePoint-side Plugin (page 37) ). System Check: You do NOT have permission to install and deploy SharePoint solutions! You may encounter a problem (red X) indicating "You do NOT have permission to install and deploy SharePoint solutions!" This appears to happen on systems running Microsoft Windows Server 2008. If you encounter this problem, please abort the current installation. Next, run the installation again by right-clicking Setup_Jive.SharePoint.exe, then clicking Run as Administrator. Upgrade Deployment Error: Cannot deploy solution Jive.SharePoint.wsp Jive Connects for Microsoft SharePoint - 46

When performing an upgrade of the SharePoint-side plugin, you need to uninstall the old version then install the new version. However, the uninstall may not completely remove all components, causing the subsequent install to fail with the error, "Upgrade Deployment Error: Cannot deploy solution Jive.SharePoint.wsp." To remove the remaining components and install properly: 1. Log into each web front end on the SharePoint farm as an administrator and complete the following steps: a. Go tot a command prompt and type IISSRESET /stop. b. Open up Windows Explorer to the Global Assembly Cache (GAC). This is typically C:\windows \assembly. Remove all files that begn with "Jive.SharePoint" by highlighting the file and pressing Delete. Refresh Windows Explorer and ensure that there are no more files that start with "Jive.SharePoint" in the GAC. c. From a command prompt, type IISRESET /start 2. Perform the manual installation as discussed in Manually Installing the SharePoint-side Plugin (page 40). You may have to perform the deployment steps using stsadm as discussed in the documentation. Changes to web.config on Installation When you install the connector (activate the Jive Infrastructure web application feature), the entries described in this topic are added to the web.config files associated with the appropriate web applications. When you uninstall the connector (deactivate the Jive Infrastructure web application feature), all web.config entries should be removed unless other third-party tools have added the same web.config entries for their purposes. Note: This topic is provided for informational purposes, describing how web.config is altered during installation so that you're aware of the changes. In most cases, you shouldn't need to take any action because of these changes. ScriptResource HttpHandler This is an HTTP handler for processing requests for script files that are embedded as resources in an assembly. It is basic AJAX capability used in ASP.NET but not embraced by SharePoint 2007. Note that other third-party tools may do this as well, so removing this by hand could affect other tools. <system.web> <httphandlers> <add verb="get,head" path="scriptresource.axd" type="system.web.handlers.scriptresourcehandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false" /> </httphandlers> </system.web> Binding Redirects This is an assembly binding redirect so that ASP.NET 3.5 versions of System.Web.Extensions.dll and System.Web.Extensions.Design.dll can be used. It is basic AJAX capability used in ASP.NET but not embraced by SharePoint 2007. Note that other 3rd party tools may do this as well, so removing this by hand could affect other tools. <runtime> <dependentassembly> <assemblyidentity name="system.web.extensions" publickeytoken="31bf3856ad364e35" /> <bindingredirect oldversion="1.0.0.0-1.1.0.0" newversion="3.5.0.0" /> </dependentassembly> <dependentassembly> <assemblyidentity name="system.web.extensions.design" publickeytoken="31bf3856ad364e35" /> <bindingredirect oldversion="1.0.0.0-1.1.0.0" newversion="3.5.0.0" /> </dependentassembly> Jive Connects for Microsoft SharePoint - 47

</runtime> JivePageController HTTP Module This is a HTTP module that runs on every page in SharePoint within the web application to which the components were deployed. It is used to potentially show any of the global features (user popup, socialization status icon, or drop down menu items such as Copy To). This code immediately stops processing if all of the global features are turned off (done in Central Administration > Operations > Farm Configuration for Jive) or if the Jive Web Parts feature is not activated for the current site collection. SharePoint 2007 <system.web> <httpmodules> <add name="jivepagecontroller" type="jive.sharepoint.services.httpmodules.jivesharepointhttpmodule,jive.sharepoint.services,version=1.0.0.0, > </httpmodules> </system.web> SharePoint 2010 <system.web> <httpmodules> <add name="jivepagecontroller" type="jive.sharepoint.services.httpmodules.jivesharepointhttpmodule,jive.sharepoint.services,version=1.0.0.0, precondition="integratedmode"/> </httpmodules> </system.web> Copy To Workflow Authorized Type This adds the Copy To workflow activity as an authorized type which is required for the Copy To workflow to run or for the Copy To workflow activity to be used in either a custom Visual Studio workflow or a SharePoint Designer workflow. <System.Workflow.ComponentModel.WorkflowCompiler> <authorizedtypes> <authorizedtype Assembly="Jive.SharePoint.Workflow, Version=1.0.0.0,Culture=neutral, PublicKeyToken=06322024e9df4f4e"Namespace="Jive.SharePoint.Workflow" TypeName="*" Authorized="True" /> </authorizedtypes> </System.Workflow.ComponentModel.WorkflowCompiler> Troubleshooting If you find that entries are appearing in web.config files that should not be, you can make a backup of the web.config file and manually remove them from there. If you find that they re-appear when reinstalling Jive for SharePoint, then you likely have web.config modification entries that have not been properly removed from SharePoint. You can use a tool found at either of the two links below to fix this issue (the links basically provide the same tool): http://blog.thekid.me.uk/archive/2007/03/24/web-config-modification-manager-for-sharepoint.aspx http://www.dynasign.nl/blog/?p=14 Administering the SharePoint-Side Plugin Jive Connects for Microsoft SharePoint - 48

This section tells you how to configure SharePoint once Jive for SharePoint has been installed. In order to begin using the Jive web parts, please configure at least one Jive installation (see Manage Jive Installations (page 50) ). Note: Note: Before your users begin using Jive Connects for SharePoint, or each time you upgrade them to a new version, you should encourage them to log into the Jive interface. Logging into Jive synchronizes your identity between the Jive community and your SharePoint site, ensuring that all the parts of the system can talk to one another and you have access to all the information your permissions support. SharePoint Central Administration You'll find the entry point to Jive for SharePoint administration in the SharePoint Central Administration section. 1. Locate the Jive Administration section: In SharePoint 2007 Central Administration > Operations > Jive Administration. In SharePoint 2010 Central Administration > Application Management > Jive Administration. Under Jive Administration, you'll find links for to other sections for administering the Jive for SharePoint. Use the following topics for more information. Farm Configuration for Jive (page 49) Manage Jive Installations (page 50) Corporate Policies for Jive (page 52) Configuring the Farm For Jive: You can use the Farm Configuration for Jive page in Central Administration to configure settings that impact the entire Farm as it is integrated with Jive. To Configure the Farm for Jive 1. Open SharePoint Central Administration. 2. Locate the Jive Administration section: In SharePoint 2007 Central Administration > Operations > Jive Administration. In SharePoint 2010 Central Administration > Application Management > Jive Administration. 3. Click Farm Configuration for Jive. 4. On the Farm Configuration for Jive page, you can configure the following Jive fields. Farm Configuration for Jive Fields Field Name Impersonation Field Description Allowed: The preferred choice. Required for out-ofthe-box communication from Jive to SharePoint. Prevented Except for Activity Streams: Prevents all impersonation requests except for activity streams. This is currently reserved for custom integrations. Prevented: Prevents any impersonation requests. Useful only if Jive is not accessing SharePoint. This will limit the SharePoint Connector features to: SharePoint Web Parts (page 21) User Popups (page 31) Copy to Jive (either through the Document Menu Item (page 32) or the Workflow (page 33) ) Jive Connects for Microsoft SharePoint - 49

Field Name Field Description Valid Incoming IP Addresses for Impersonation Limit communication from Jive servers originating from one or more IP addresses. Applicable to non-kerberos authentication only. Note: If load balancers are used in front of SharePoint web front ends, restricting the incoming IP addresses is not beneficial because the load balancer IP addresses must be entered into this field. Use the Valid Incoming Service Accounts for Impersonation field (below) to help prevent unauthorized impersonation. Valid Incoming Service Accounts for Impersonation Limit communication from Jive servers using the listed service user accounts. Browser Caching Improves the user experience by limiting the need to retrieve content from SharePoint that rarely changes. User Popup Individual toggle used to turn On/Off User Popups (outside of the Jive web parts) for the entire SharePoint Farm. This feature is only available if this option is checked and the Jive Web Parts feature is activated within the current site collection. Document Menu Items Individual toggle used to turn On/Off Jive-specific document context menus (enable/disable socialization, copy to Jive) for the entire SharePoint Farm. This feature is only available if this option is checked and the Jive Web Parts feature is activated within the current site collection. Jive Status Individual toggle used to turn On/Off Jive socialization status for document libraries in the entire SharePoint Farm. This feature is only available if this option is checked and the Jive Web Parts feature is activated within the current site collection. Event Logging Used to log error and other trace messages to the SharePoint ULS logs. Version Information Version details for the individual components of the Jive for SharePoint 5. When you've finished configuring, click OK. Managing Jive Installations: This topic walks through the general procedure for configuring one or more Jive instances for the Jive for SharePoint web parts to use. When you add one of the Jive for SharePoint web parts to a page or use the other social features, you will need to choose a Jive installation (or rely on the default installation). For each web part that is added to a page, a configuration panel (web part editor) will present a list of Jive installations. In addition, each site has a default Jive installation (defined in "Site Settings" -- see Specifying a Default Jive Instance (page 55) for more information) used by site socialization, user popup, and the Copy To drop down menu. Note: You must configure at least one Jive installation before using the Jive for SharePoint web parts. The Jive-side plugin (represented in Managing the Features (page 65) ) will need to be installed before you can successfully configure a Jive installation. To Manage Jive Installations 1. Open SharePoint Central Administration. 2. Locate the Jive Administration section: In SharePoint 2007 Central Administration > Operations > Jive Administration. Jive Connects for Microsoft SharePoint - 50

In SharePoint 2010 Central Administration > Application Management > Jive Administration. 3. Under Jive Administration, click Manage Jive Installations. 4. On the Manage Jive Installations page, click on New Jive Installation. 5. Provide values for at least the following fields: Name Jive Internal URL Jive External URL Jive Service User Password You'll find example values below. See the table below for more information about each of the fields. Add Jive Installation Fields Field Name Field Description/Details Example Name A name of the respective Jive installation; to be used during web part configuration, workflow configuration, and site settings. Jive Installation 1 Jive Internal URL URL path that is used for communication from the SharePoint server to Jive (this may be same value as used for the Jive External URL). http://jive.jivekrb5.local Jive External URL URL path that is handed to the client (the user's browser) to resolve Jivespecific resources (this may be the same value as used for the Jive Internal URL). http://jive.jivekrb5.local SharePoint Domain (Optional) This is used if there is more than one domain; it helps distinguish between the same user name that may exist in separate domains. Jive only allows for a single domain. If provided, it limits access to Jive functionality to only those users in the specified domain. Jive Service User User account (may be a normal Jive account) used to access Jive services on behalf of SharePoint users. This account simply needs to have normal access to Jive. No overrides are required. ' jiveaccess Jive Connects for Microsoft SharePoint - 51

Field Name Field Description/Details Example Jive Service User Password Password that is associated <password> to the Authentication user above. Note: The password is case sensitive. Jive Domain The Jive Domain/Realm is optional and is typically left blank. Custom Jive SSO configurations may require this to be set. jivecustom 6. Click the Test Connection button to confirm that SharePoint is able to successfully connect to Jive. 7. Click OK, and review the Valid field to confirm the entry was added correctly and that SharePoint can successfully communicate with Jive. See also Jive Installation Test Fails in Troubleshooting Tips: SharePoint Administration (page 5). If the connection to Jive was successful, on the Manage Jive Installations page, under New Jive Installation, you will see the "Valid" column with a "True" value. If the connection was NOT successful, please take a look at the User name and Password for case sensitivity. Note: Now that at least one installation of Jive is configured in SharePoint, you can begin configuring and using the Jive web parts (see Managing Jive Web Parts (page 21) and the Socialization Features (page 14). Configuring Corporate Policies for Jive: Content from SharePoint can be configured to be "surfaced" (or shown) in Jive by configuring socialization Activity Streams. An Activity Stream is an RSS-style feed that can be established as a link between SharePoint and Jive. The Activity Stream provides awareness to the consumer (in this case the Jive application) of new or modified content. This content is generally in the form of documents from SharePoint that can be previewed, reviewed, and rated by an established (or new) Jive community. Note: Corporate policies only apply for streams from SharePoint to Jive. Content requested through the widgets, or the list macro are not subject to the corporate policies. There are four layers of control regarding socialization of content between SharePoint and Jive. This section will describe the top-most Administrative layer. The others layers are represented by the following bullet points and referenced document sections. Administrative Level. See information about corporate policies for Jive below. Site Level. For more information, see Jive Socialization Settings (page 55) List Item Level. For more, see Using the Document Menu Items (page 32) "Copy To Jive" Workflow. For more, see Using the Copy To Jive Workflow (page 33) The Administrative Level allows a SharePoint administrator the ability to turn on/off socialization and to control how Activity Streams can be used (or not used). Note: People will be able to perform a Copy To Jive action -- regardless of the Corporate Policy settings -- as long as they have write access in the Jive place they're choosing as the destination. In other words, read access in SharePoint is all that's needed to perform a Copy To. To Configure Corporate Policies for Jive 1. Open SharePoint Central Administration. 2. Locate the Jive Administration section: In SharePoint 2007 Central Administration > Operations > Jive Administration. In SharePoint 2010 Central Administration > Application Management > Jive Administration. 3. Under Jive Administration, click Corporate Policies for Jive. 4. Review the following screen shot and details below the screen shot to learn more about the available policy options. Jive Connects for Microsoft SharePoint - 52

Corporate Policy for Jive Fields Field Name Field Description Allow Jive Activity Streams from SharePoint? Primary checkbox "toggle" used to turn Activity Streams On or Off at a global level. Jive Places Specific types of Jive places that can be targeted for socialization of SharePoint content. Activities Specify whether to "surface" new SharePoint items, updated SharePoint items, or both in Jive. Jive Connects for Microsoft SharePoint - 53

Field Name Field Description SharePoint Sites Filter for SharePoint sites that can (or cannot) be used to stream or "surface" content to Jive. File Extensions Filter for document file extensions that can (or cannot) be used to stream or "surface" content to Jive. Content Types Filter for SharePoint "content types" that can (or cannot) be used to stream or "surface" content to Jive (see screen shot below). User Settings Filter for specific SharePoint users that cannot stream or "surface" content to Jive. Note: Site Content Types are a powerful concept in SharePoint for organizing metadata/content. The following screen is an example of a custom Jive content type. The screen below "Site Content Type Gallery" shows the effect of applying the Corporate Policy with the "SOX" Site Content Type. Example of a SharePoint document library in a SharePoint site configured for socialization with Jive. Note: Notice the initial icons to the left of each document. The green Jive icon represents that the Activity Stream is active and enabled for the item. The grayed out Jive icon represents that the Activity Stream has been disabled for the item (changed via the drop down menu for each item). The Jive icon with the red line crossed through it represents that the Activity Stream has been blocked for the item. This is facilitated through the Administrative level as a Corporate Jive Connects for Microsoft SharePoint - 54

Policy. For the "blocked" items above, the documents were created with a SOX SharePoint content type. Policy has been configured to "block" all documents based on this content type. 5. Click OK. Configuring Site-Level Connector Settings You'll find site-level configuration for Jive for SharePoint on the Site Settings page, under Site Actions > Site Settings for the SharePoint site. Locate the Jive site settings section: Site Actions menu > Site Settings > Jive. Note: You must have appropriate access on the site to be able to see or access the Site Actions menu. Jive Site Settings: You can change Jive Site Settings to specify a default Jive instance and Jive inheritence settings. To Specify a Default Jive Instance 1. Locate the Jive site settings section: Site Actions menu > Site Settings > Jive. Note: You must have appropriate access on the site to be able to see or access the Site Actions menu. 2. Under Jive, click General Jive Settings. 3. Under Default Jive Instance, choose the desired Jive Instance (same as a Jive Installation). This Jive Installation will be used by the Jive Socialization Settings (page 55), the Jive User Popup (page 31), and the Copy to Jive (page 32) drop down menu for SharePoint documents. 4. To have SharePoint subsites follow the same socialization configuration, select the Inherit settings from parent sitecheck box. This specifies that the current SharePoint site "inherits" the Jive Installation details from its parent SharePoint site. If you select Inherit settings from parent site you can also select Allow parent socialized site to override settings. Having both checked is the default value. When you select Allow the parent socialized site to override the settings, the inheritance is dependent upon the selection in the Jive Socialization Settings (page 55) page of the parent (ancestor) site. Note: If you access "General Jive Settings" for a SharePoint root-level site, the "Inherit settings from parent site" and "Allow parent socialized site to override settings" checkboxes are not shown. 5. Click OK. Socialize a SharePoint Site: The Jive Socialization Settings screen provides the "Site" or second layer (four layers total) of socialization administration. After you socialize a site, its libraries become visible within Jive. If you don't want certain SharePoint libraries to be visible, you can disable the streams for those libraries. To disable streaming, go to Libraries > Site Pages, and then select Disable Jive Activity Stream from the drop-down list next to both libraries. For more information on activity streams or details regarding the socialization administration layers, see Configuring Corporate Policies for Jive. (page 52) The Site layer is designed to be controlled by a specific SharePoint site owner. This layer is used to establish a "mapping" between a SharePoint site and a Jive Space, Project, or Group. Streaming creates mirrors of the SharePoint documents in Jive, so Jive users can see them in Jive and then open them in SharePoint. Once this type of "mapping" is established, the Corporate Policy (Administrative layer) is used to determine what content can be socialized into Jive as a valid Activity Stream. This "mapping" in SharePoint also enables the use of the SharePoint widgets in the "mapped" Jive container (Space, Project, or Group). Note: When you disable socialization for a site, you will have the option to delete any documents you have already streamed from the Jive target place, or to convert them to ordinary Jive documents with no link to SharePoint. However, any documents streamed with a previous version of Jive Connects for SharePoint (before version 1.6) will be retained. Jive Connects for Microsoft SharePoint - 55

To Configure Jive Socialization Settings for a Site When you socialize a SharePoint site to Jive, Jive accesses it by using a service account that has read access to this SharePoint site. If you receive an error socializing the site, please contact your administrator. 1. Locate the Jive site settings section: Site Actions menu > Site Settings > Jive. Note: You must have appropriate access on the site to be able to see or access the Site Actions menu. 2. Under Jive, click Jive Socialization Settings. The Jive Socialization Settings page opens.you can use this page to configure how the current site is socialized with Jive. Note: If the entire Jive Socialization Settings page appears to be disabled, please navigate to the General Jive Settings screen (under Site Actions > Site Settings) and clear the Inherit settings from parent site check box. 3. Under Select a Jive Place, choose a Jive place (space, project, or group) to begin socializing content; you can also click New Social Group to create a new group in Jive where your site can be socialized. Socializing to a place makes Jive Web parts visible in SharePoint as well as enabling SharePoint widgets in Jive. 4. In the Subsite Behavior field, select the checkbox if you want all subsites for the current site to inherit the socialization behavior. You should also select Allow the parent socialized site to override the settings for the subsite in Jive Site Settings (page 55). If you want to specify inheritance for only some subsites, then do not select the checkbox in this field, but do select the Inherit settings from parent site for each subsite that should inherit the settings in Jive Site Settings (page 55). 5. If you want information about documents from all or part of the SharePoint site to flow into a place in Jive, select the Enabled check box under Activity Streams. You can optionally include sub-sites and Document Libraries. You can socialize your site without enabling the activity stream if you want make features such as widgets and the list macro available in Jive. Note: Libraries with asterisks (in SharePoint 2010 only) do not have the Modified field indexed. Indexing the field is recommended, but not required unless there are a large number of documents in the library (for example, over 5000). 6. To limit the number of documents streamed to Jive, type the beginning date for document streaming in the Include activity on or after field. You can socialize your site without enabling the activity stream if you want make features such as widgets and the list macro available in Jive. Note: When you enable socialization and click OK to establish the mapping to Jive, make sure you are logged in with the correct account. This account will be used to pull activity stream updates from SharePoint. Libraries from subsites are only shown if the the Include Subsites checkbox is checked and the subsite inherits its site settings. The subsite inheritance is specified on the subsite's Jive Site Settings (page 55) page and potentially influenced by the Inherit by Default checkbox previously mentioned. 7. For Access Control, you can select either Jive security or SharePoint security to determine who can access the content in the target Jive container. Jive Security SharePoint documents are visible (including preview) within Jive to users with access to the target Jive place where the documents are streamed. However, only users who also have access to the documents through SharePoint can download and edit them. You then control access to the documents based on Jive places, for example, you could create a secret or members-only group with limited access and stream your documents to that location where only selected users can see them. Because of performance considerations, we recommend using Jive Security rather than SharePoint Security. SharePoint Security Jive Connects for Microsoft SharePoint - 56

SharePoint documents are visible (including preview) within Jive only to users who have access to the target Jive place where the documents are streamed and have read access to the individual documents in SharePoint. 8. Click OK. Viewing Log Information for the Activity Stream To see information about documents streamed from your site, click Site Settings --> View Jive Activity Streams. Viewing Activity Streams for a Site: Viewing Activity Streams for a Site 1. Locate the Jive site settings section: Site Actions menu > Site Settings > Jive. Note: You must have appropriate access on the site to be able to see or access the Site Actions menu. 2. Under Jive, click View Activity Streams. 3. In the list of activity feed types, locate one you want to test. 4. To test the feed, click the Test link to launch a new browser window that displays the feed. Here is a sample of an activity stream (RSS feed). Note: Depending on the currently logged-in user and the impersonation restrictions specified in Configuring the Farm For Jive (page 49), you may not be able to view the activity stream. If you are logged in as the account used by the activity stream (see Configuring Socialization for a Site (page 55) ), then you should not have a problem. If you are using another account and the farm impersonation settings restrict by IP address or service account, the link will likely fail indicating the restriction in the response. Accessing the Diagnostics Page: The Diagnostics page is intended for troubleshooting issues with the connector including issues creating a SharePoint Location within Jive and searching SharePoint from within Jive. To Access the Diagnostics Page 1. Locate the Jive site settings section: Site Actions menu > Site Settings > Jive. Note: You must have appropriate access on the site to be able to see or access the Site Actions menu. 2. Under Jive, click Diagnostics. 3. Follow the on-screen instructions for diagnosing your configuration. Jive Connects for Microsoft SharePoint - 57

Configuring Client Browser Settings The following browser settings are recommended to allow the browser to automatically log in to SharePoint and potentially Jive, relieving the user of having to ever enter a username or password for SharePoint or Jive. These settings are not required, but they do help users with SharePoint web applications or Jive installations that use Windows Integrated Authentication (for example, NTLM or Kerberos) for authenticating to SharePoint or Jive. Jive does not require Windows Integrated Authentication, but if it does use it, then these settings can reduce the steps it takes for a user to log in. Note: Instead of performing these operations manually, you can use policy management software to have the browser settings propagated to users' machines. For example, Active Directory can use group policies to configure the settings for IE browsers for everyone in the organization. To Configure Microsoft Internet Explorer versions 6, 7, and 8 1. Open Internet Explorer 2. Click Tools > Internet Options > Security. 3. Choose the Local Intranet zone, then click the Sites button. 4. Click the Advanced button. Jive Connects for Microsoft SharePoint - 58

5. Enter the URLs for both the SharePoint site and the Jive site (click the Add button for each). 6. Click Close, then click OK. 7. Click the Custom level... button. Jive Connects for Microsoft SharePoint - 59

8. If it is not already set, set the Logon setting to Automatic logon only in Intranet zone. 9. Click OK, then click OK To Configure Firefox version 3.5 Jive Connects for Microsoft SharePoint - 60

1. Open Firefox. 2. Navigate to "about:config". 3. Enter network.neg in the filters section. 4. Add the Kerberos domain to network.negotiate-auth.delegation-uris and network.negotiateauth.trusted-uris. Note: The value.jivekrb5.local, shown above, is only an example of a domain. Please supply your specific domain. Configuring Search Results Security Trimming Configuration of delegation is necessary in order for the SharePoint search service provided to Jive to perform security trimming using the account supplied to the search method. Attention: This is required when SharePoint and Jive use NTLM to communicate. Requirements Windows Server 2003 (or later) Active Directory controller. The application pool accounts must use a domain account. If used, the IP address restriction lists in both Jive and SharePoint must include all the required IP addresses. For environments where users will be logging into SharePoint across multiple domains, the domains must have a two-way trust, so that Jive users can see SharePoint search results. Using the Trust tab of Active Directory Domains and Trusts, Configuration Scenario On every SharePoint web front end use the Local Security Policy snap-in (Start > All Programs > Administration Tools > Local Security Policy) to confirm that the SharePoint application pool accounts have the following privileges on each SharePoint web front end: 1. Act as part of the operating system privilege. 2. Impersonate a client after authentication. Note: If the two changes above for the application pool account are not acceptable for the the application pool account used by regular users, consider extending the SharePoint web application and using a separate application pool account for the extended web application. Then when Adding a SharePoint Location (page 69), use the original web application for the External SharePoint Location URL and the extended web application URL as the Internal SharePoint Location URL. It is the Internal SharePoint Location URL that must use an application pool account with the specified settings. On the domain controller, use the Active Directory Users and Computers snap-in to confirm the correct domain functional level. 1. View the properties for the domain. 2. Verify that the domain functional level is set to Windows 2003 or later. 3. If the domain is not set to at least Windows 2003, right-click the domain and select "Raise domain functional level". Beware, this command is not reversible. Jive Connects for Microsoft SharePoint - 61

If any configuration changes were made, you will need to execute IISRESET on your SharePoint instances to make them take effect. Tips for Developers This section describes topics that may interest Developers and/or SharePoint Administrators. Integrating Workflow with SharePoint Designer The steps described here show how to use SharePoint Designer and the "Copy Document to Jive" workflow activity to create a custom workflow. Once you've done this, you should be able to execute the workflow as designed to copy documents into a Jive space, project, or group. The steps differ between SharePoint 2007 and SharePoint 2010. Integrating Workflow with SharePoint 2007: 1. Launch the SharePoint Designer application (this is typically installed as a separate application, but grouped with Microsoft Office). 2. Open the SharePoint site where you want to create the custom workflow. 3. Click File > New > Workflow. 4. In the Workflow Designer, under Define your new workflow, enter a new for your workflow and choose a SharePoint document library that you want to associate to the workflow. 5. Click Next. 6. On the next screen, enter a step name, configure the workflow step conditions, click the Actions dropdown. 7. In the Workflow Actions dialog box, under Select a Category, select Jive Actions, the select the Copy Document to Jive workflow action (activity). 8. Click Add. 9. Configure the Copy Document to Jive action parameters (this document, Jive Instance Name, Jive Place Type, and Jive Place Name). Jive Connects for Microsoft SharePoint - 62

10. Click Finish. Integrating Workflow with SharePoint 2010: 1. Launch the SharePoint Designer application (this is typically installed as a separate application, but grouped with Microsoft Office). 2. Open the SharePoint site where you want to create the custom workflow. 3. Click File > New > Workflow. 4. Decide whether your workflow is going to be associated to a single SharePoint document library, or whether it can be reused and associated to multiple document libraries or a content type. The sections below describe each option. Creating a Workflow that is Associated to a Single SharePoint Document Library a. Click List Workflow, then choose a document library in your site to associate your workflow to the document library. b. Under Add a new workflow to your list, enter the name for the workflow. You can optionally enter a description. c. Build the workflow with as many steps as you like. In one step, add the Copy Document to Jive Action. 1. Click Action > Copy Document to Jive. 2. Specify the action properties. You will need to change the Jive Instance Name to what is defined in central administration (an administrator may need to help you or you can use one of the web parts to show you the instance name in the web part properties). You also must select the Jive Place Type (space, project, group) and type the name of the Jive place to copy the document. d. Click Publish to save your workflow and publish it to the chosen SharePoint document library. Creating a Reusable Workflow a. Click Reusable Workflow. Jive Connects for Microsoft SharePoint - 63

b. In the Create Reusable Workflow dialog box, under Add a new reusable workflow to your site, enter a name for your workflow and choose a content type (you can optionally add a description). The content type should be Document or some content type that inherits from Document (the Copy to Jive action does not work for list items). c. Build the workflow with as many steps as you like. In one step, add the Copy Document to Jive Action. 1. Click Action > Copy Document to Jive. 2. Specify the action properties. You will need to change the Jive Instance Name to what is defined in central administration (an administrator may need to help you or you can use one of the web parts to show you the instance name in the web part properties). You also must select the Jive Place Type (space, project, group) and type the name of the Jive place to copy the document. d. Click Publish to save your workflow and publish it to SharePoint. e. Associate your workflow to a content type or a list. This will take you into the SharePoint UI and let you perform the association. Working Around Browser Caching Jive for SharePoint uses the following file types: XSL, XML, HTM, and CSS. Files of these types are cached by client browsers unless browser caching is disabled (see Farm Configuration for Jive (page 49) ). Browser caching generally improves performance because the client need not submit a request or download files which do not frequently change. However, it can be a nuisance when you're changing files on the SharePoint file system such as CSS, XSL, or XML files. In this case it will be necessary to clear the browser cache and issue a full refresh (CTRL-F5). Steps required to successfully clear the browser cache sufficient to force download of these files varies by browser and version. Enabling and Viewing SharePoint Tracing Enabling Tracing on the Client Browser Some basic client browser level tracing is available from the SharePoint application. To enable, append the following to your current browser location (URL) query string.?jivedebug=true Example: http://sharepointurl?jivedebug=true Note: Please note the uppercase "J" and "D" in JiveDebug. The value for JiveDebug is case sensitive. The following screen shot shows a sample of the client tracing output. Jive Connects for Microsoft SharePoint - 64

Note: You will not immediately see the trace output on the screen. Make sure to scroll beyond the normal screen presentation and you will see the trace output. Enabling Tracing on the SharePoint Server To enable tracing on the SharePoint server see the Farm Configuration for Jive (page 49). You must perform an IISRESET on SharePoint after changing this setting for the setting to take effect. In addition, this must be done on every SharePoint web front end to enable tracing for all SharePoint activity within the connector. Viewing Trace Output There are two techniques to view tracing output: Looking in the SharePoint ULS logs Using DebugView Viewing Output in the SharePoint ULS Logs The SharePoint ULS logs are, by default, in a directory such as "C:\Program Files\Common Files\microsoft shared\web Server Extensions\12\LOGS" on the SharePoint server, but this is defined in Central Administration (Operations -> Diagnostics Logging). Go to that directory and find the file with the latest update timestamp. You may need to wait a few seconds for the latest updates to show up. Open the file with the latest changes, go to the bottom, and start looking for anything with "[Jive.SharePoint.Tracing]" in it. Viewing Output with DebugView DebugView is a tool that will let you watch real-time tracing. You can download DebugView, run it on the SharePoint server, and simply watch for trace messages to appear. You may want to set a filter (Edit -> Filter/Highlight) to "[Jive.SharePoint.Tracing]" to only get Jive SharePoint trace messages. You may also need to capture Win32 message (Capture -> Win32 and/or Capture -> Global Win32). Note: DebugView has been known to not work in Windows Server 2008 under some configurations. Setting up Jive Jive Connects for Microsoft SharePoint provides tight integration between SharePoint and Jive. It takes SharePoint s strengths as a content repository with complex workflows and document management and couples it with Jive s social networking capability, intuitive interface, and high adoption rate. Jive Connects for Microsoft SharePoint - 65

This section covers the features within Jive and is intended for Jive IT administrators. It begins with the technical installation and configuration of the Jive features, followed by more technical concepts around the Jive features. To learn more about the features within SharePoint, see Managing the SharePoint Features (page 36). > Important: Before you begin, refer to the Read Me (page 3), which helps you prepare for configuring Jive and SharePoint. Authentication Scenarios (page 84) describes two authentication scenarios used to demonstrate the integration between SharePoint and Jive. These scenarios provide some extra guidance and may help relate to your requirements. Installing and Upgrading the Jive-Side Plugin This section provides prerequisites and basic steps for installing or upgrading the Jive-side plugin for SharePoint. Jive-Side Plugin Installation Requirements SharePoint Connector 1.6 requires Jive versions 4.5.4, 4.5.5, 4.5.5.2, 4.5.6, 4.5.6.1, 4.5.6.2, 4.5.6.3, or 4.5.7.0. Using a common user repository is highly recommended, but the connector can function with different repositories for Jive and SharePoint as long as the account names are identical and you are not using Kerberos authentication. Ensure that REST web services are enabled in Jive. You can enable them in the Jive admin console at System > Settings > Web Services. Installing the Jive-Side Plugin 1. Download the Jive-side Plugin for SharePoint and extract the package to a desired location on your environment (such as a new folder on the Desktop). 2. Navigate to Admin Console:System --> Plugins --> Add Plugin. 3. Click the Browse button, then locate the spintegration.jar that you extracted in Step 1. 4. Click the Upload button. Jive Connects for Microsoft SharePoint - 66

5. Once you've installed the SharePoint plugin, you should see a screen similar to the following: Note: You will likely need to restart Jive before attempting to use the Jive SharePoint External Storage Provider Plugin. 6. Please see Adding a SharePoint Location (page 69) for details on configuring a connection from Jive to SharePoint. Note: Please ensure the SharePoint-side plugin has been installed in SharePoint before continuing. Upgrading the Jive-Side Plugin 1. Download the Jive-side Plugin and extract the package to a desired location on your environment (such as a new folder on the Desktop). 2. Log into Jive as an Administrator and navigate to the Admin Console. 3. Go to System > Management > Plugins. Jive Connects for Microsoft SharePoint - 67

4. Locate the existing Jive SharePoint-side plugin in the list, then click the red X to remove it. Note: Click OK if you receive the following message. You will be asked to restart Jive at the end of the upgrade steps. 5. On the Plugins page, click Add Plugin. 6. Click the Browse button, then locate the spintegration.jar that you extracted in Step 1 above. 7. Click the Upload button. 8. Once you've installed the SharePoint plugin, you should see a screen similar to the following. Jive Connects for Microsoft SharePoint - 68

9. Restart Jive. Note: The following command will restart Jive running in a Linux environment. /etc/init.d/jive-application restart 10. Edit each SharePoint Location and update the External Search URL and Query Test Term as discussed further below in Adding a SharePoint Location (page 69). Administering the Jive-Side Plugin This section presents the configuration options available in Jive once the SharePoint-side plugin has been installed. In order to begin using the new SharePoint-based Jive widgets, please configure at least one SharePoint Location (see Adding a SharePoint Location to Jive (page 69) ). Adding a SharePoint Location When you add a SharePoint Location, you make Jive aware of a SharePoint site and all of its sub-sites. Once you have installed the Jive-side and SharePoint-side plugins, then you can add and configure SharePoint Locations in Jive. For more on installing the plugins, see Installing the Jive-side Plugin (page 66) and Installing the SharePoint-side Plugin (page 37) Note: The SharePoint Location also allows Jive to be aware of any site collections that share the same initial URL path. For example, if there is a SharePoint site collection at http://sharepoint, and other site collections at http://sharepoint/sites/projecta and http://sharepoint/sites/projectb, only one SharePoint Location needs to be defined pointing to http://sharepoint. However, to use this approach, there must be a site collection at the shared portion of the URL (http://sharepoint). When you add or update a SharePoint Location, the plugin adds or updates a corresponding OpenSearch Engine item, which is used to implement the SharePoint Search functionality. Perform any changes to the SharePoint Location itself to automatically copy the change to the OpenSearch Engine item for you. Once you complete the following steps, a SharePoint Site administrator can socialize a site (page 55) to Jive, which produces SharePoint activity in Jive and makes the SharePoint widgets (page 14) available within Jive: Add a SharePoint location as described in this topic. Configure installation (page 50) in SharePoint. Enable socialization in corporate policies (page 52). Note: The URL for the SharePoint site being socialized must start with the SharePoint Location External URL discussed below. In the UI: Admin Console: System > Settings > SharePoint Connector > SharePoint Locations 1. Click Add SharePoint Location. Alternatively, you can click the Edit button next to an existing SharePoint Location to update it. Note: You can add as many SharePoint locations as you like, but one external/internal URL cannot start with the entire contents of another. For example, you can have http://sharepoint/sites/ projecta and http://sharepoint/sites/projectb as two SharePoint Locations, but you cannot have http://sharepoint and http://sharepoint/sites/projectb as two SharePoint Locations. In the latter case the http://sharepoint/sites/projectb started with the entire contents of http://sharepoint. For this case you can just have one SharePoint Location (http://sharepoint) to handle all of the sites. 2. Complete the required fields, which are red. Use the following field descriptions to help you complete the form. Note: For the fields that require URL items, please ensure each URL resolves through DNS. If DNS does not resolve the URL, update the hosts file on the Jive server(s) instead of using an IP address. Jive Connects for Microsoft SharePoint - 69

Using an IP address for SharePoint it is not optimal and may cause issues related to Alternate Access Mappings on the SharePoint server. This will show up in the SharePoint trace log and System event log and may prevent some features of the connector from working properly. SharePoint Location Name: Enter free form name to use as a reference for the specified SharePoint location. SharePoint User Identity Mapping: After deciding whether you need to change the default user identity mapping, select the corresponding identity mapping: SharePoint External ID (Simple Profile field settings) or SharePoint External Username and Domain (Composite Profile field settings). For more on this, see Configuring User Identity Mapping (page 71) and Configuring Identity Mapping for SharePoint Locations (page 73). Enabled: Select to enable SharePoint. SharePoint Location External URL: Enter URL to a SharePoint site as accessed by users. This is used for links referencing SharePoint provided in the browser to Jive users. This URL must resolve to a page accessible by users. This will allow any SharePoint sites under the referenced site to be accessible by Jive. SharePoint Location Internal URL: Enter URL to a SharePoint site as accessed by Jive. In most cases, this will be identical to the external URL above. However, this allows serverto-server communications to occur through a different handler on the SharePoint server(s) (a different IIS web site through the use of extended web applications). This allows for more flexibility in how security is handled for end users vs. Jive web service requests. Service Account: Account used to access SharePoint services on behalf of Jive users. This account requires read access to the SharePoint Location External URL, and it requires read access to any site socialized from SharePoint. The permission for read access can be set manually, but because SharePoint security is set up at the site collection level, it can be overridden at any site.therefore, you can ensure that the service account always has read access by creating a User Policy for the associated SharePoint web application and giving the service account Full Read permissions on the web application. External Search URL: Enter URL to a SharePoint search results page. The easiest way to determine the correct value: Log on to your SharePoint site. Find the search box (typically at the top right corner of the page). Type in a search term and press Enter. Cut and paste the URL from the Search Results page into this field. Manually remove everything from a question mark ("?") character to the end of this value. Append?k={searchTerms} to the URL, to ensure that the search terms you are using will be forwarded to SharePoint. Search Scope: Enables you to create a scope that narrows SharePoint searches to only Names, Sites, or List, if desired. Note: An advanced option allows you to set multiple Search Scopes. To do this, go to Admin Console: System > Settings >OpenSearch Engines and select Add Engine from Form. Use the Admin Console help for more information about this form. In the Search URL field, you need to enter the search URL that includes the type and value of the scope. The following list provides examples for each type of search scope. Scope by Name: http://<jive-instance-url>/spi-search.jspa? searchterms={searchterms}&count={count}&locationid=1118&scope=<name> Scope by Site (URL): http://<jive-instance-url>/spi-search.jspa? searchterms={searchterms}&count={count}&locationid=1118&site=<siteurl> Scope by List (URL): http://<jive-instance-url>/spi-search.jspa? searchterms={searchterms}&count={count}&locationid=1118&list=<listurl> Query Test Term: Enter a test phrase that returns results from SharePoint when a search is performed. Username: Type the username for the SharePoint service account. Typically this username is in the format of <domain>\<user>. Note: The service account must be a valid account that has read access to any SharePoint site (or sub-site) that connects to this SharePoint location. When a SharePoint site is socialized Jive Connects for Microsoft SharePoint - 70

to a Jive place, the URL of the SharePoint site needs to match the external or internal URL for one of the SharePoint locations. The matching SharePoint Location's service account needs to have read access to the corresponding site(s). A single SharePoint Location may map to multiple site collections as discussed previously. If the service account does not have read access to a particular SharePoint site, socializing that SharePoint site to Jive will fail. Content from SharePoint activity stream: Use this option to manage content that you maintain in SharePoint, but view in Jive. You can select one of the three options. The first option excludes content that has not been generated by a registered Jive user. The second option enables you to specify an override user to claim that content. The third option enables you to associate all content that is maintained in SharePoint with a specific Jive user that you type into the Override User field. For example, you can associate all SharePoint content with one user so you can see at a glance which content is maintained in SharePoint. Note: When you need to specify an Override User, make sure to use a valid Jive user. Content Copied from SharePoint: Use this option to manage content copied from SharePoint that will be maintained in Jive. You can select one of the three options. The first option excludes content that has not been generated by a registered Jive user. The second option enables you to specify an override user to claim that content. The third option enables you to associate all content that is maintained in SharePoint with a specific Jive user that you type into the Override User field. For example, you can associate all SharePoint content with one user so you can see at a glance which content is maintained in SharePoint. Note: When you need to specify an Override User, make sure to use a valid Jive user. 3. Click Update and then click Test next to your new SharePoint location before using the new SharePoint-centric widgets and socialization features. Configuring User Identity Mapping Jive supports external identity mapping by enabling you to map user identities using LDAP, SSO, or environments managed from within Jive. You only need to configure identity mapping if SharePoint users are from multiple domains or if SharePoint User IDs are different from Jive User IDs. You can configure user identity mapping to support two or more SharePoint domains that communicate with Jive. The following steps provide instructions for user identity mapping according to how your environment retrieves user information, which can be LDAP, SSO, or internally managed (page 78). Note: External identity mapping support for SharePoint Connector can only be enabled once the required identity attribute values are made available to Jive. For more on this, see Required Attribute Settings (page 78) LDAP 1. Determine which mapping set (page 77) is the best fit for the required identity attributes. 2. If Jive already has a profile field with this information, then you can override it using the sharepoint.identity.fieldname.override.sp-external-id property: a. Set the sharepoint.identity.fieldname.override.sp-external-id (page ) property to the name of the new custom profile field. When you create this custom profile field, see the rules for creating it (page 78). b. Check and verify external identity mapping configuration System --> Settings --> SharePoint Connector --> Multiple Domain. c. Click Synchronization. d. Proceed to Configuring Identity Mapping for SharePoint Locations (page 73). 3. Set sharepoint.identity.simple.fields.enabled and/or sharepoint.identity.composite.fields.enabled to true (restart is required). The SPC custom profile fields by default will be externally managed so ACTION IS REQUIRED for sharepoint.identity.profilefield.externallymanaged.* system properties. They must be all be set to false, which requires a restart. Jive Connects for Microsoft SharePoint - 71

4. Navigate to Admin Console: People --> Settings --> Profile and Homepage --> Custom Profile fields. 5. Click Edit Mapping for applicable fields, depending on the mapping set, which can be simple or composite configuration (page 77). 6. Enter the LDAP attribute name(s). 7. Run Synchronize LDAP or login as Jive user. This imports the LDAP required attributes values into either the simple or composite set of profile fields. Jive for SharePoint now has the correct SharePoint identifier(s) in its external identity store. 8. Configure SharePoint Location in Jive. For more info, see Configuring Identity Mapping for SharePoint Locations (page 73) SSO 1. Determine which mapping set (page 77) is the best fit for the required identity attributes. 2. If Jive already has a profile field with this information, then you can override it using the sharepoint.identity.fieldname.override.sp-external-id property: a. Set the sharepoint.identity.fieldname.override.sp-external-id (page ) property to the name of the new custom profile field. When you create this custom profile field, see the rules for creating it (page 78). b. Check and verify external identity mapping configuration System --> Settings --> SharePoint Connector --> Multiple Domain. c. Click Synchronization. d. Proceed to Configuring Identity Mapping for SharePoint Locations (page 73). 3. Set sharepoint.identity.simple.fields.enabled and/or sharepoint.identity.composite.fields.enabled to true (restart is required).the SharePoint Connector custom profile fields by default will be externally managed so ACTION IS REQUIRED for sharepoint.identity.profilefield.externallymanaged.* system properties. They must be all be set to false, which requires a restart. 4. Create Mapping. Depending on the SSO plugin implementation, you need to set identity attributes into the user's profile field(s) programmatically or by declarative means. For example, configuration - Spring mapping. 5. Run Synchronization. Log in as jive user or run bulk synchronize (if available). This will bring in the required attributes values into either the simple or composite set of profile fields. Jive for SharePoint now has the correct SharePoint identifier(s) in its external identity store. 6. Configure SharePoint Location in Jive. For more info, see Configuring Identity Mapping for SharePoint Locations (page 73) Internally Managed 1. Determine which mapping set (page 77) is the best fit for the required identity attributes. 2. If Jive already has a profile field with this information, then you can override it using the sharepoint.identity.fieldname.override.sp-external-id property: a. Set the sharepoint.identity.fieldname.override.sp-external-id (page ) property to the name of the new custom profile field. When you create this custom profile field, see the rules for creating it (page 78). b. Check and verify external identity mapping configuration System --> Settings --> SharePoint Connector --> Multiple Domain. c. Click Synchronization. d. Proceed to Configuring Identity Mapping for SharePoint Locations (page 73). 3. Set sharepoint.identity.simple.fields.enabled and/or sharepoint.identity.composite.fields.enabled to true (restart is required. The SPC custom profile fields by default will be externally managed so ACTION IS REQUIRED for sharepoint.identity.profilefield.externallymanaged.* system properties. They must be all be set to false, which requires a restart. 4. Navigate to Admin Console: People --> Settings --> Edit/Add user. 5. Add or edit the identity value directly into the stock profile fields for either the simple of composite set. Upon save, Jive for SharePoint propagates the values into SharePoint external identity store. Jive Connects for Microsoft SharePoint - 72

6. Configure the SharePoint Location in Jive. For more info, see Configuring Identity Mapping for SharePoint Locations (page 73) Configuring Identity Mapping for SharePoint Locations This topic helps you configure your SharePoint Locations if you want to provide user identity mapping for multiple SharePoint domains. The following steps should be performed after you configure user identity mapping, which enables external identity mapping support. 1. From the Admin Console, navigate to System --> Settings --> SharePoint Connector --> SharePoint Locations. 2. Click Edit next to the location you want to edit. If you are adding a location for the first time, see Add a SharePoint location (page 69) to help you complete this page. 3. Use the following criteria to select the appropriate SharePoint User Identity Mapping. For more on this, see Configuring User Identity Mapping (page 71). When the the Jive username and the SharePoint external identity (SharePoint login) are the same and SharePoint users are all from a single domain (if using Windows authentication), select the following profile field setting. Default (Jive username) When the the Jive username and the SharePoint external identity are NOT the same or the SharePoint users are from more than one domain (if using Windows authentication), select one of the following profile field settings. Simple when the fully qualified SharePoint external identity can be set into a single Jive user custom profile field: SharePoint External ID or [override field name]. For examples, see Mapping Sets for Custom Profile Fields (page 77) and Settings for Custom Profile Fields (page 78). Composite when the fully qualified SharePoint external identity cannot be set into a single Jive user custom profile field. The SharePoint external identity will span two Jive custom profile fields: SharePoint External Username and SharePoint Domain Name. For examples, see Mapping Sets for Custom Profile Fields (page 77) and Settings for Custom Profile Fields (page 78) 4. Click Update to save your changes. 5. Verify SharePoint identity and connectivity by navigating to System --> Settings --> SharePoint Connector --> Diagnostics and clicking Diagnose next to the appropriate SharePoint location. Check user by entering user's Jive username and clicking Check Account. How to Extract Attribute Values Complex attribute values are ones that are buried in attribute strings and need to be parsed in order to use them. This topic shows you how you can extract complex attribute values from SharePoint and map them to Jive. This profile field mapping allows Jive to become aware of values that are buried in attribute strings by pulling out the significant pieces and mapping them to their counterparts in Jive. The following advanced regex properties are available to extract the target values from a string. You need to define the regex properties so they grab the right target value. Note: If you make a change to any of the following transformation scenarios, then you'll need to run SharePoint Identity Synchronization (page 78). The following Simple Extraction table shows default values for the simple extraction. These settings extract a value so it can be mapped to the SharePoint External ID or Simple override profile fields. System Property Setting (Default) Definition sharepoint.identity.simple.formatprovider.regex.pattern (.+) Match 1 or more of anything sharepoint.identity.simple.formatprovider.regex.group 1 Group 1 is the value to be extracted Jive Connects for Microsoft SharePoint - 73

The following Composite Extraction table provides extraction of default values and maps them to the SharePoint Username and SharePoint Domain Name profile fields. System Property Setting (Default) Definition sharepoint.identity.composite.formatprovider.username.regex.pattern (.+) Match 1 or more of anything sharepoint.identity.composite.formatprovider.username.regex.group 1 Group 1 is the value to be extracted sharepoint.identity.composite.formatprovider.domain.regex.pattern (.+) Match 1 or more of anything sharepoint.identity.composite.formatprovider.domain.regex.group 1 Group 1 is the value to be extracted sharepoint.identity.composite.formatprovider.domain.regex.extract.lookupmap Provides a JSON { (advanced) representation of a lookup "lookup": { "key1": "value1", associative array and a "key2": "value2" default value. Property string }, "defaultvalue": must be a valid JSON string. "default" The following string is the } default value. The lowercase value of the raw profile field or, in this case, the extracted value based on the regex, will be looked up against the lookup map property. 1. If a value is found in the lookup map then it will be used. 2. If no value is found in the lookup map and the "defaultvalue" property is defined that value will be used. 3. Otherwise the raw profile field or the extracted value will be used. Note: Lookup functionality is only available for the SharePoint Domain Name profile field. An ERROR log entry will result if Jive cannot interpret JSON as a lookup associative array and a default value. Examples Check out the following examples of different ways to parse out the NETBIOS Domain name from the dn (Distinguished Name) LDAP attribute and transform it using a lookup table. This effectively maps the attribute name, dn (Distinguished Name) to SharePoint Domain Name. Jive Connects for Microsoft SharePoint - 74

System Property Setting Definition sharepoint.identity.composite.formatprovider.domain.regex.pattern (?i)((?:\s*dc\s*=\s*([0-9.az_-]+)\s*(, $)){1}) parses out the 1st domain (first DC key=value pair) or the string "JIVELAND" caseinsensitive. Domain Name can consist of the following chars: 0-9a-z_-. sharepoint.identity.composite.formatprovider.domain.regex.group 2 Group 2 is the value to be extracted The examples in this section use the following setting for sharepoint.identity.composite.formatprovider.domain.regex.extract.lookupmap, which defines the defaultvalue property, but does not define "JAF". { "lookup": { "jiveland": "JIVESOFTWARE", "pdx": "PORTLAND" }, "defaultvalue": "JIVERS" } If the exact value for the NetBIOS domain name cannot be easily made available to Jive, but the NetBIOS domain name already exists in the LDAP attribute you can use *.formatprovider.regex.pattern and *.formatprovider.regex.group and define these properties to parse out the target value. In this example, the target value is "JIVELAND", which is the value of the 1st DC key value pair. Note: Before resorting to transformation of something like distinguished name, check to see if the LDAP attribute msds-principalname is available for each user. If so, this has the NetBIOSDomain\username value. Example #1 Attribute value: CN=Karen Berge,CN=admin,DC=JIVELAND,DC=Fabrikam,DC=COM Result: SharePoint Domain Name = JIVESOFTWARE Example #2 Attribute value: CN=Karen Berge,CN=admin,DC=PDX,DC=Fabrikam,DC=COM Result: SharePoint Domain Name = PORTLAND Example #3 In the following example defines neither a lookup for "jaf" nor does it define a defaultvalue, so the raw extracted values are used. Attribute value: CN=Karen Berge,CN=admin,DC=JAF,DC=Fabrikam,DC=COM Result: SharePoint Domain Name = JAF Example #4 Attribute value: CN=Karen Berge,CN=admin,DC=JAF,DC=Fabrikam,DC=COM Result: SharePoint Domain Name = JIVERS Diagnosing Integration Issues You can diagnose issues with user connectivity from Jive to SharePoint locations and sites. In the UI: Admin Console: System > Settings > SharePoint Connector > Diagnostics Viewing Defined System Properties Jive Connects for Microsoft SharePoint - 75

Look for the list of system properties in Admin Console: SharePoint Diagnotsics > SharePoint Properties. These system properties are defined, supported by Jive and closely related to SharePoint. For example, if you've set the sharepoint.document.migratetosharepointoption property to disable the Migrate to SharePoint feature, you'd see it listed. There are a few Jive System Properties you might see listed, such as jiveurl or jive.usernames.case.insensitive. Note: For Jive systems that integrate with SharePoint, the Jive system property jive.usernames.case.insensitive must be set to true or not be specified, which defaults to true. For a list of system properties related to SharePoint integration, see System Properties for SharePoint (page 78). Testing User Connectivity and Search Across Sites in a SharePoint Location You can discover which SharePoint sites in a location a user has access to, and how search in those sites will respond for the user. To test user access to SharePoint locations: 1. Navigate to Admin Console:System --> Settings --> SharePoint Connector --> SharePoint Locations and then find the name of the SharePoint location you want to test. 2. To the right end of the location's row in the list, click Diagnose. 3. In the Diagnose Location dialog box, in the Location dropdown, ensure that the location you want to test is selected. 4. In the Test a user box, enter the username for the user whose connectivity you want to test. 5. Test with that username: To verify that the user has an account on sites in the location, click Check account. A message will indicate whether a account for the user was found. To see if a search as that user will return results from sites in the location: a. Click Search as user. b. In the Searching as box, enter a phrase to search for. c. Click Search. A message will indicate how many results were returned by the search. Testing User Visibility Into Sub-Sites You can check to see what a Jive user can see in a SharePoint site and their sub-sites. To test user visibility into a site: 1. Navigate to Admin Console:System --> Settings --> SharePoint Connector --> SharePoint Locations and then find the name of the SharePoint location with sites you want to test. 2. At the left end of the location's row in the list, click the location's name. 3. Under the location's name, in the location details box that appears, locate the name of the site you want to test. If the site list is a long one, you can shorten the list by entering part of the site's name in the Filter Sites box. 4. Click the site's name. 5. In the Diagnose dialog box, in the User name box, enter the username of the user whose access you want to test, then click Get sites. A message will indicate whether that user has access to sites in the location. If the user has access to sites in the location, the sites will be listed in the dialog box. 6. If the user has access to sites, under Select a site click the name of the site you want to test. Note that if the site has sub-sites, you'll be able to access those by clicking the >> symbol next to the site's name. Click << to navigate back upward through the site hierarchy. 7. In the Lists box, note the lists for which the user has access. 8. In the Lists box, click a list name to get a list of the views for which the user has access. 9. Click Test to view a message indicating the number of items in the view for which the user has access. Jive Connects for Microsoft SharePoint - 76

What Happens When SharePoint is Unavailable This topic provides more information about the time-out behavior you see in Jive when SharePoint cannot be reached. When Jive can't reach SharePoint, it activates a monitoring thread. Once this thread is activated, Jive will poll the connection for a designated interval using the sharepoint.monitor.check.delay and sharepoint.monitor.check.interval system properties until SharePoint becomes available once again. The following SharePoint system properties (page 78) can be adjusted to regulate this monitoring and time out behavior. Click a property to find out more about it. sharepoint.connection.monitor.timeout (page ) sharepoint.socket.monitor.timeout (page ) sharepoint.monitor.check.delay (page ) sharepoint.monitor.check.interval (page ) sharepoint.monitor.check.skip (page ) When SharePoint cannot be reached, users will be able to access places that have been socialized, but SharePoint widgets and macros will not load and SharePoint documents with SharePoint permissions will not be visible, except to the Jive administrator. Once connection is re-established, users will once again see SharePoint documents and widgets. Note: When you create a socialization, documents can be streamed using Jive or SharePoint permissions. If they use Jive permissions, then the documents will still be visible when SharePoint is unavailable. Mapping Sets for Custom Profile Fields You can use the following table to see examples of how Jive maps the simple and composite sets of data to custom profile fields for SharePoint. The identity mapping you use depends on whether the Jive user name and the SharePoint external identity are the same or different. The second case is only applicable to multi-domain implementations. Use the SharePoint Locations dialog (page 73) to specify identity mappings. Note that for multidomain implementations, it's possible for different SharePoint Locations to use different identity mappings. When the Jive user name and the SharePoint external identity and SharePoint login are the same, select Default in the Sharepoint Location dialog of the Jive Admin Console. When the Jive user name and the SharePoint external identity are NOT the same: Select Simple in the Sharepoint Location dialog when the fully qualified SharePoint external identity can be set into a single Jive user custom profile field. You can use either use the predefined custom profile field, SharePoint External ID, or you can override SharePoint External ID with a custom profile field containing the SharePoint external identity. See the rules for creating custom profile fields (page 78). Select Composite in the Sharepoint Location dialog when the fully qualified SharePoint external identity cannot be set into a single Jive user custom profile field. In this case, the SharePoint external identity spans two Jive custom profile fields: SharePoint External Username and SharePoint Domain Name. Custom Profile Field Name Simple Set SharePoint External ID Composite Set Expected Field Content ' Example Values ' user@netbiosdomain or joe.strummer@jiveland NetBIOSDomain\username or claimsuser@claimsidentityprovider ' ' SharePoint External Username username joe.strummer SharePoint Domain Name NetBIOSDomain JIVELAND Jive Connects for Microsoft SharePoint - 77

Rules for creating custom profile fields To create valid cusotm profile fields for identity mapping, you must make sure new fields include the following configuration. In the UI: Admin Console: People > Settings > Profile Settings Field Type: Select Text Field. Attributes: uncheck Editable. Required Attribute Settings The required attribute settings help you make the required identity attribute values available to Jive. LDAP Advanced LDAP topology is needed: Global catalog, LDAP tree, etc. Required identity attributes are mapped to Jive SPC profile field(s). SSO Plug-in Custom configuration to map required identity attributes values into Jive. For example, user properties, user profile field(s). Internally Managed Jive Admin edits user profiles and enters required identity attribute values. Bulk update requires identity attribute values are imported per user. Settings for Custom Profile Fields Simple SharePoint External ID field represents the complete SharePoint identity. Composite Together SharePoint username and user NetBIOS Domain name fields represent the complete SharePoint identity and are individually made available as SharePoint External Username and SharePoint Domain Name. This approach only applies if SharePoint users are authenticated via classic mode, which is Windows Integrated Authentication, for example, NTLM and Kerberos. SharePoint Identity Synchronization Jive for SharePoint watches all multi-domain related profile fields even when overridden, and automatically keeps SharePoint identities in sync. When users are added, updated, or deleted, Jive for SharePoint marshalls profile fields and transforms them into a distinct Jive for SharePoint external identity data store for optimization. When you initially use stock Jive for SharePoint multi-domain fields, the fields are all new so Jive for SharePoint automatically becomes aware of any changes and synchronizes the changes to the Jive for SharePoint external identity data store automatically. But, when you use the system property, system property sharepoint.identity.fieldname.override.sp-external-id, to override multiple domain fields, there may be pre-existing profile values because the Jive for SharePoint external identity data store will not have been built so a manual synchronization is needed. You may also need to synchronize identities if you change the transformation scenario (page 73). To synchronize SharePoint Identities: 1. Make the changes to the transformation scenario or profile values as described int his topic. 2. Run SharePoint Identity Synchronization System --> Settings --> SharePoint Connector --> Multiple Domain. 3. Click Synchronization System Properties for SharePoint Integration System properties provide a way to do additional configuration. To use system properties, you need to log into the Jive Admin Console and navigate to System > Management > System Properties. Keep in mind that both property names and values are case sensitive. Jive Connects for Microsoft SharePoint - 78

Jive for SharePoint uses several system properties that are used to configure global settings of the connector. For example, jiveurl, sharepoint.ip.restrictions, and sharepoint.serviceaccount.restrictions. Some of these settings are shared with other Jive functionality and others are exclusively used by the SharePoint Connector. If the property does not exist in Jive, you can scroll to the bottom of the page to add a new system property, otherwise you can edit the existing property. Note: You should make changes to system settings only under the guidance of Jive support or professional services teams. The following is a list of system properties that can be used to fine-tune configuration. In the examples shown below, assume that the configured service account is FooBar and the domain is EXAMPLE.LOCAL -- note that capitalization is very important! Property Description jiveurl A string used to construct absolute URLs for various resources. Must match the URL set in SharePoint Central Administration for this Jive instance. The jiveurl property is used as the base URL in communication with Jive for SharePoint. It is the URL users need to use to access Jive. Make sure this is a valid URL accessible by all Jive users. For example, http://jive.mycompany.com. jive.usernames.case.insensitive Setting to false makes case sensitive comparisons when users register or log in, for example, bbrag is a different user than BBragg. When set to true, there is no disctinction between bbragg and BBragg. Default is true. Note: For Jive systems that integrate with SharePoint, the Jive system property jive.usernames.case.insensitive must be set to true or not be specified, which defaults to true. search.results.groupbythread true to have search results from Jive back to SharePoint collapsed into single result items. Default is true. sharepoint.activity.polling.delay Delay in seconds before initial execution of the Activity Polling background task. Default is 60. sharepoint.activity.polling.interval Delay in seconds between each subsequent execution of the Activity Polling background task. Default is 15. sharepoint.activity.polling.request.initial.items Sets the number of items that can come across in the Activity Stream for new account activity feed requests. Default is 5000. sharepoint.activity.polling.request.initial.timelimitseconds For the initial request, limits in seconds how long Jive can query SharePoint for items that will be shown in the Jive Activity stream. When you set this limit, it only applies to querying list items and processing the results. To ensure that more so more list items reach the Activity Stream, Jive does not query changes, such as deletes and permission changes, on the initial activity feed request. By setting an "abridged" flag in SharePoint's View Jive Activity Streams page, Jive uses subsequent queries to pick up items missed because of the time limit. Default is 60. See Best Practices (page 4) for more on this. sharepoint.activity.polling.request.items Sets the number of subsequent items that can come across in the Activity stream for subsequent activity feed requests. Default is 5000. sharepoint.activity.polling.request.timelimitseconds Sets the limit in seconds for how long Jive continues to query SharePoint for items that will be shown in the Jive Activity stream. This property allows requests for changes, such as deletes and permission changes. By setting an "abridged" flag in SharePoint's View Jive Activity Streams page, Jive uses subsequent queries to pick up items missed because of Jive Connects for Microsoft SharePoint - 79

Property Description the time limit. Default is 20. See Best Practices (page 4) for more on this. sharepoint.activity.polling.suspend true to globally suspend the Activity Polling background task; intended for temporary use. Default is false. sharepoint.activity.processing.delay Delay (in seconds) before initial execution of the Activity Processing background task. Default is 65. sharepoint.activity.processing.documentcontenttypeonly true sets this Boolean property so only files of contenttype Document can stream to Jive. Default is false. sharepoint.activity.processing.interval Delay (in seconds) between each execution of the Activity Processing background task. Default is 60. sharepoint.activity.processing.perdocumentmaxretries Sets the maximum number of retries, on a per document basis, that Jive will try to process a document in the stream. Default is 10. sharepoint.activity.processing.perdocumentmaxretries.delete When maximum number of retries is reach delete activity. Default is true. sharepoint.activity.processing.per_cycle Maximum number of activities to process on each execution of the Activity Processing background task. Default is 30. sharepoint.activity.processing.suspend true to globally suspend the Activity Processing background task; intended for temporary use. Default is false. sharepoint.calendar.maxeventspermonth Maximum number of events per month available in the SharePoint calendar widget. Default is 1000. sharepoint.calendar.monthswindow Maximum number of months containing events available in the SharePoint Calendar widget. Default is 12. sharepoint.calendar.monthsprevious Number of previous months containing events available in the SharePoint Calendar widget. Default is 3. This number is used to determined the number of future events you can see in the calendar by subtracting it from sharepoint.calendar.monthswindow. sharepoint.connection.monitor.timeout Sets the connection timeout in milliseconds for SharePoint monitor polling service. Default is 10000. sharepoint.connection.timeout.millis Sets the connection timeout in milliseconds Default is 90000. sharepoint.document.migratetosharepointoption true to enable the "Migrate to SharePoint" feature; false to disable it. Default is true. sharepoint.document.converttojive.removesporigins When and if SharePoint streamed documents are converted to Jive documents, setting to true removes all remnants of the document's' SharePoint origins. Default is false. sharepoint.groupmembershipchange.check.delay Identifies the delay (in seconds) before initial execution of the SharePoint group membership changed background task. Default is 180. sharepoint.groupmembershipchange.check.interval Identifies the delay (in seconds) between each execution of the SharePoint group membership changed background task. Default is 300. sharepoint.groupmembershipchange.check.skip true specifies that the SharePoint group membership changed background task should should be skipped. Default is false. sharepoint.identity.composite.formatprovider.username.regex.pattern Default is (.+), which means match 1 or more of anything. sharepoint.identity.composite.formatprovider.username.regex.group Default is 1, which means group 1 is the value. sharepoint.identity.composite.formatprovider.domain.regex.extract.lookupmap Provides a JSON representation of a lookup associative array and a default value. Property string must be a valid JSON string. The following string is the default value. Jive Connects for Microsoft SharePoint - 80

Property Description { "lookup": { "key1": "value1", "key2": "value2" }, "defaultvalue": "default" } The lowercase value of the raw profile field or, in this case, the extracted value based on the regex, will be looked up against the lookup map property. 1. If a value is found in the lookup map then it will be used. 2. If no value is found in the lookup map and the "defaultvalue" property is defined that value will be used. 3. Otherwise the raw profile field or the extracted value will be used. Note: Lookup functionality is only available for the SharePoint Domain Name profile field. An ERROR log entry will result if Jive cannot interpret JSON as a lookup associative array and a default value. sharepoint.identity.composite.formatprovider.domain.regex.group Default is 1, which means group 1 is the value. sharepoint.identity.composite.formatprovider.domain.regex.pattern Default is (.+), which means match 1 or more of anything. sharepoint.identity.fieldname.override.spuse to override the Simple Set - SharePoint External ID profile external-id with an existing profile field containing the same expected values: user@netbiosdomain or NetBIOSDomain\username or claimsuser@claimsidentityprovider. No default and no restart is required. Because this is an existing field, you'll need to run SharePoint Identity Synchronization (page 78) once. sharepoint.identity.formatprovider.restart.required false allows Jive administrator to change the regex and group definitions without a system restart because it forces the Jive plugin to recompile the regex each time before the transformation is applied. Default is true. In production environment, compile should only happen at startup; therefore, set this property to true in production environments or remove the property completely since default is true. sharepoint.identity.simple.fields.enabled true to activate the external identity mapping field, "SharePoint External ID" in a Jive profile (identity simple) if you have multi-domain requirements or if the SharePoint username is different from the Jive username ; false to disable it. Governs whether or not the fields are active and created. The default for this property is false. An application restart is required for changes to this property to take effect. Note: If this property was switched from true to false, you should manually delete the custom profile field(s) that were created when set to true. To delete these fields, navigate to: Admin Console: People --> Setting --> Profile and Homepage --> Custom Profile fields and delete the following fields. SharePoint External ID sharepoint.identity.composite.fields.enabled true to activate the external identity mapping fields, "SharePoint External Username" and "SharePoint External Domain" in a Jive profile (identity composite) if you have multi-domain requirements or if the SharePoint username is different from the Jive username; false to disable it. Governs whether or not the fields are active and created. Set this to true if you have multi-domain requirements or if the SharePoint Jive Connects for Microsoft SharePoint - 81

Property Description username is different from the jive username. The default for this property is false. An application restart is required for changes to this property to take effect. Note: If this property was switched from true to false, you should manually delete the custom profile field(s) that were created when set to true. To delete these fields, navigate to: Admin Console: People --> Setting --> Profile and Homepage --> Custom Profile fields and delete the following fields. SharePoint Username SharePoint Domain Name sharepoint.identity.profilefield.externallymanaged.domainname true to enable whether or not the SharePoint Connector Domain Name custom identity field is Externally Managed. Set to true (which is default) when the field is populated by LDAP or SSO. Default is true. An application restart is required for changes to this property to take effect. Set to false when the Jive admin will be setting the domain name value in the Admin Console. Setting this value to false is only meant for UAT and POC testing. In general, this profile values should be set by an external mechanism. Note: If the SharePoint Domain Name field is mapped to an attribute and then this externally managed option is set to false, any preexisting mapping to attribute will be cleared out. Navigate to Admin Console: People --> Settings --> Profile and Homepage --> Custom Profile fields --> Mapping to see mapping for a field. sharepoint.identity.profilefield.externallymanaged.externalid true to enable whether or not the SharePoint Connector External ID custom identity field is Externally Managed. Set to true (which is default) when the field is populated by LDAP or SSO. Default is true. An application restart is required for changes to this property to take effect. Set to false when the Jive admin will be setting the external ID value in the Admin Console. Setting this value to false is only meant for UAT and POC testing. In general, this profile values should be set by an external mechanism. Note: If the SharePoint External ID field is mapped to an attribute and then this externally managed option is set to false, any preexisting mapping to attribute will be cleared out. Navigate to Admin Console: People --> Setting --> Profile and Homepage --> Custom Profile fields --> Mapping to see mapping for a field. sharepoint.identity.profilefield.externallymanaged.externalusername true to enable whether or not the SharePoint Connector Username custom identity field is Externally Managed. Set to true (which is default) when the field is populated by LDAP or SSO. Default is true. An application restart is required for changes to this property to take effect. Set to false when the Jive admin will be setting the username value in the Admin Console. Setting this value to false is only meant for UAT and POC testing. In general, this profile values should be set by an external mechanism. Note: If the SharePoint External Username field is mapped to an attribute and then this externally managed option is set to false, any preexisting mapping to attribute will be cleared out. Navigate to Admin Console: People --> Setting --> Profile and Homepage --> Custom Profile fields --> Mapping to see mapping for a field. sharepoint.identity.simple.formatprovider.regex.pattern Default is (.+), which means match 1 or more of anything. Jive Connects for Microsoft SharePoint - 82

Property Description sharepoint.identity.simple.formatprovider.regex.group Default is 1, which means group 1 is the value. sharepoint.ip.restrictions Comma-delimited list of IP addresses for SharePoint servers. If configured, only accepts web service calls from IP addresses on this list, or for IP addresses reported by DNS resolution of the hostname of a SharePoint Location external URL. If this property isn't in place, no restrictions are enforced. Make sure you are using the correct IPv4 and/ or IPv6 addresses of the SharePoint web front end (WFE). For debugging purposes, the IP filter will log what the currently configured list of IP addresses if it rejects a request. It will also log the address that the request came in from. If the request is supposed to be legitimate, add that address to the list in the property's value. For example, 192.168.1.11, 192.168.1.12,3ffe:1900:4545:3:200:f8ff:fe21:67cf. Note: If load balancers are used in front of Jive, restricting the incoming IP addresses is not as beneficial because the load balancer IP addresses may have to be entered into this field. For more information, see Impersonation Restriction Validation (page 86) sharepoint.list.macro.showviewnames Boolean property that controls how the document list macro displays lists. Set to true and individual views can be selected instead of just getting the default view for a list. Default is false. sharepoint.list.timezone.option Calendar Widget time zone option. Default is jive_timezone. sharepoint.monitor.check.delay Sets the delay (in seconds) before initial execution of the SharePoint monitor background task. Default is 60. sharepoint.monitor.check.interval Sets the delay (in seconds) between each execution of the SharePoint monitor background task. Default is 5. sharepoint.monitor.check.skip Determines whether or not the SharePoint monitor background task should be skipped. Default is false. sharepoint.macro.list.errors.show Show macro errors when Jive for SharePoint List macro is unable to render SharePoint content. Default is false. sharepoint.macro.list.render.calendaraslist Within the context of Jive for SharePoint List macros, render SharePoint calendars as lists. Default is true. sharepoint.page.size Number of items returned for paged web service requests. Default is 30. sharepoint.place.document.count.threshold.enabled Enables accurate counting of documents in socialized Jive places. Default true. sharepoint.project.document.count.threshold Identifies threshold to accurately count documents in socialized projects. Default 30. sharepoint.remoteentitlement.visibilitycheck.enabled true to specify that Jive should perform a SharePoint permission check to determine document visibility in Jive. Default is true. sharepoint.remoteentitlement.hideallstreamed Globally hides all SharePoint streamed documents. Default is false. sharepoint.serviceaccount.restrictions Accepts a comma-delimited list of Jive user accounts. If configured, Jive for SharePoint only accepts web service calls from Jive accounts in this list. The service accounts used by SharePoint to access Jive as defined in Managing Jive Installations. This is used to limit the accounts that can authenticate to Jive for SharePoint custom web services for impersonation. Separate multiple accounts with commas and do not Jive Connects for Microsoft SharePoint - 83

Property Description enter a domain name. If this property isn't in place, no restrictions are enforced. For example, jivesvcacct. For more information, see Impersonation Restriction Validation (page 86) sharepoint.socket.monitor.timeout Sets the socket timeout in milliseconds for SharePoint monitor polling service. Default is 10000. sharepoint.socket.timeout.millissets the socket timeout in milliseconds. Default is 90000. sharepoint.socialgroup.document.count.threshold Identifies threshold to accurately count documents in socialized groups. Default 30. sharepoint.space.document.count.threshold Identifies threshold to accurately count documents in socialized spaces. Default 30. sharepoint.synchronize.blocksize Sets the number for the blocks of users to be processed during the SharePoint identity synchronization task. Default is 1000. sharepoint.synchronize.yield true indicates that the background SharePoint identity synchronization task should yield CPU between processing blocks of users. Default is true. sharepoint.viewdocuments.filter.spmanaged.option true to enable users to filter documents by files managed in SharePoint. This filter shows documents that live in SharePoint, but can be viewed in Jive. When users select Files Managed by SharePoint as the filter in the Documents tab of a group, space, or projects, they see all documents managed by SharePoint. Default is true. sharepoint.viewdocuments.filter.spcopied.option true to enable users to filter documents by files copied from SharePoint into Jive. This filter shows documents now live in Jive, but they started in SharePoint. When users select Files Copied from SharePoint as the filter in the Documents tab of a group, space, or projects, they see all documents copied from SharePoint. Default is true. sharepoint.widget.list.render.calendaraslist Renders SharePoint calendars as lists within the context of the SJive for SharePoint list widget. Default is true. sharepoint.widget.list.refreshonvalidate When set to true, Jive requests a complete refresh of the SharePoint taxonomy when SharePoint list widgets are saved. Default is true. Authentication Scenarios Jive Connects for Microsoft SharePoint provides tight integration between SharePoint and Jive. It takes SharePoint s strengths as a content repository with complex workflows and document management and couples it with Jive s social networking capability, intuitive interface, and high adoption rate. One of the major integration components is the ability to seamlessly authenticate a user's credentials and to properly authorize access based on each product's security "trimming" capability. Security "trimming" means to only show a user what they have the abiltity to see and/or interact with. This section focuses on authentication scenarios between Jive and SharePoint. Each scenario represents a real configuration used to demonstrate or test Jive and SharePoint integration. Authentication Through Impersonation The following configuration describes a demonstration environment configured to use NTLM authentication and Impersonation for web service communication between SharePoint and Jive. This is the simplest authentication configuration between Jive and SharePoint. Individual Server Machines: JS-DC-02.jivedemo.local (Domain Controller) Jive Connects for Microsoft SharePoint - 84

JS-J3-02.jivedemo.local (Jive Server) JS-M7-02.jivedemo.local (MOSS/SharePoint Server) Setting the Authentication Provider in SharePoint Registering a Jive Installation in SharePoint Registering a SharePoint Location in Jive Jive Connects for Microsoft SharePoint - 85

Impersonation Restriction Validation Because Jive for SharePoint uses impersonation, steps must be taken to restrict impersonation requests such that only authorized requests are performed. The configuration for these restrictions are discussed in: Configuring the Farm For Jive (page 49) System Properties for SharePoint Integration (page 78) There are basically two ways to restrict impersonation: by service account and by originating IP address. Restricting by service account is recommended. Restricting by originating IP address can also be done, but if load balancers are used in front of SharePoint or Jive then this can be less useful without extra network configuration. SharePoint Restriction Validation 1. (Optional) Test with validation turned off. a. Validate that no restrictions are set. Review the settings on Configuring the Farm For Jive (page 49) and verify that: Impersonation is allowed Valid Incoming IP Addresses for Impersonation is blank Valid Incoming Service Accounts for Impersonation is blank b. Test hitting the custom SharePoint web services. 1. Log into SharePoint as a regular user (not a service account). IE or Firefox are ideal browsers for this because the results are easier to see (Chrome does not show results very well). 2. Determine a user you want to impersonate (not the account used above). 3. Change the URL in your browser to the following. Change <user> to the login of the user chosen in the step above (do not include the domain). <site_url>/_layouts/jive/webs.svc/rest/getwebs/<user> For example, http://sharepoint.mycompany.com/_layouts/jive/webs.svc/rest/ getwebs/john.doe 4. You should see results in your browser showing a <webcollection> with more details. If this were to fail due to impersonation restrictions you should see something like: Invalid service account of '<domain>\<user>' for impersonation. Request denied. Invalid user host address of '<ip address>' for impersonation. Request denied. 2. Restrict the service account. a. Update SharePoint configuration to restrict the service account. 1. Navigate to Configuring the Farm For Jive (page 49). Jive Connects for Microsoft SharePoint - 86

2. Add each SharePoint Service account(s) specified in Adding a SharePoint Location (page 69) to the Valid Incoming Service Accounts field. Hit the check icon to validate that the user is found. 3. Save your changes. 4. Perform an IISRESET (do for all web front ends). b. Test hitting the SharePoint web services with service accounts restricted. 1. Perform all steps under Step 1.2: Test hitting the custom SharePoint web services above. This should fail. 2. Perform all steps under Step 1.2: Test hitting the custom SharePoint web services above, but log into SharePoint using one of the service accounts. This should succeed. 3. (Optional) Restrict the incoming IP address. a. Update SharePoint configuration to restrict the IP address. 1. Navigate to Configuring the Farm For Jive (page 49). 2. Add each Jive server IP address to the Valid Incoming IP Addresses for Impersonation field. Separate each IP address with a newline/return. Note: You may need to add both IPv4 and IPv6 addresses. If you have load balancers in front of SharePoint, this setting should be left blank unless you can setup your network such that Jive->SharePoint requests bypass the load balancers and go direct to a SharePoint server. Otherwise you would need to enter the load balancer IP address here and that would defeat the purpose of this restriction. 3. Save your changes. 4. Perform an IISRESET (do for all web front ends). 4. Test hitting the SharePoint web services with incoming IP addresses restricted. a. Perform all steps under Step 1.2: Test hitting the custom SharePoint web services above, but log into SharePoint using one of the service accounts and make sure your browser is not running from a Jive server. This should fail. b. Perform all steps under Step 1.2: Test hitting the custom SharePoint web services above, but log into SharePoint using one of the service accounts and make sure your browser is running from a Jive server. This should succeed. Jive Restriction Validation 1. (Optional) Test with validation turned off. a. Validate that no restrictions are set. Review the settings on System Properties for SharePoint Integration (page 78) and verify that: The system property sharepoint.ip.restrictions is blank or non-existent. The system property sharepoint.serviceaccount.restrictions is blank or non-existent. b. Test hitting the custom Jive web services. 1. Log into Jive as a regular user (not a service account and not a Jive admin account). IE or Firefox are ideal browsers for this because the results are easier to see (Chrome does not show results very well). 2. Determine a user you want to impersonate (not the account used above). 3. Change the URL in your browser to the following. Change <user> to the login of the user chosen in the step above (do not include the domain). <jive_url>/rpc/rest/spintegration/places?username=<user> Example: http://jive.mycompany.com/rpc/rest/spintegration/places? username=john.doe 4. You should see results in your browser showing a <places> with more details. If this were to fail due to impersonation restrictions you should see something like: User not authorized for this type of request. User was not found in 'sharepoint.serviceaccount.restrictions' and/or requesting IP was not found in 'sharepoint.ip.restrictions'. 2. Restrict the service account. a. Update Jive configuration to restrict the service account. Jive Connects for Microsoft SharePoint - 87

1. Review configuration settings on System Properties for SharePoint Integration (page 78). 2. Create (or update) a property called sharepoint.serviceaccount.restrictions to have the Jive Service account(s) specified in each SharePoint Service account(s) specified in Manage Jive Installations. Separate multiple names with a comma. Do not include domain names. 3. Save your changes. b. Test hitting the Jive web services with service accounts restricted. 1. Perform all steps under Step 1.2: Test hitting the custom Jive web services above. This should fail. 2. Perform all steps under Step 1.2: Test hitting the custom Jive web services above, but log into Jive using one of the service accounts. This should succeed. 3. (Optional) Restrict the incoming IP address. a. Update Jive configuration to restrict the IP address. 1. Review configuration settings on System Properties for SharePoint Integration (page 78). 2. Create (or update) a property called "sharepoint.ip.restrictions" to have each SharePoint server IP address. Separate each IP address with a comma. Note: You may need to add both IPv4 and IPv6 addresses. If you have load balancers in front of Jive, this setting may not work as well and you may want to go without setting this property. If you can setup your network such that SharePoint->Jive requests bypass the load balancers and go direct to a Jive server it should work fine. Otherwise it may require that you enter the load balancer IP address here and that would defeat the purpose of this restriction. 3. Save your changes. b. Test hitting the Jive web services with incoming IP addresses restricted. Perform all steps under Step 1.2: Test hitting the custom Jive web services above, but log into Jive using one of the service accounts and make sure your browser is not running from a SharePoint server. This should fail. Perform all steps under Step 1.2: Test hitting the custom Jive web services above, but log into Jive using one of the service accounts and make sure your browser is running from a SharePoint server. This should succeed. Jive Connects for Microsoft SharePoint - 88