Jive Connects for Microsoft SharePoint

(1)

Jive Connects for Microsoft

SharePoint

(2)

(3)

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.

(5)

• 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

(6)

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)

• 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 -->

(8)

• 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/)

(9)

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.

(10)

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:

(11)

• 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.

(12)

• 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

(13)

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>")

(14)

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 : http://jive.com/sharepoint/administration i : http://www.w3.org/2001/XMLSchema-instance InheritParentSettings : false

DefaultJiveInstanceId : 1 SocializationEnabled : true

SocialTargets : SocialTargets StreamingEnabled : true

SocializedSite : http://jive.redlinkmobile.local/rpc/rest/spintegration/sites/1000

PS C:\Users\Administrator> $ssxml.jiveSiteSettings.SocialTargets.SocialTarget

AccessControl : AllowMetaData JiveGroupType : 0

JivePlaceId : 1001 JivePlaceName : Marketing JivePlaceType : 700

UserAccountForAccess : 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:

(15)

$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 : http://jive.com/sharepoint/administration i : http://www.w3.org/2001/XMLSchema-instance InheritParentSettings : false

DefaultJiveInstanceId : 1 SocializationEnabled : true

SocialTargets : SocialTargets StreamingEnabled : true

SocializedSite : http://jive.redlinkmobile.local/rpc/rest/spintegration/sites/1000

PS C:\Users\Administrator> $ssxml.jiveSiteSettings.SocialTargets.SocialTarget

AccessControl : AllowMetaData JiveGroupType : 0

JivePlaceId : 1001 JivePlaceName : Marketing

(16)

$web.properties["jive.sitesettings"] = ""

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

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

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.

(17)

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. Navigate to the group, space, or site. 2. Click Customize in the Overview tab.

3. When the widget layout canvas opens, select Other, and then select the SharePoint widget. 4. Drag the Drag to Add button to where the widget should show up.

5. 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.

(18)

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:

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.

(19)

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:

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.

(20)

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.

(21)

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.

(22)

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

(23)

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.

(24)

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.

(25)

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

(26)

Your Places Spaces Projects

The "Your Places" panel shows all the Spaces, Projects, Groups that you have

selected to "Follow" from Jive. It will also list the SharePoint sites that you have selected to "Follow" from SharePoint.

The "Spaces" panel shows a complete list of Jive Spaces available to "Follow"

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"

(27)

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

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.

(28)

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

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.

(29)

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

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.

(30)

• 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.

(31)

• 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

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.

(32)

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

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).

(33)

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.

(34)

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.)

(35)

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

Jive Connects for Microsoft SharePoint

Jive Connects for Microsoft

SharePoint

Contents

Jive Connects for Microsoft SharePoint

ReadMe

Best Practices

Getting Started

Troubleshooting Tips

Generic Troubleshooting

Active Directory user account changes not recognized for SharePoint

data consumed in Jive

409 Conflict error

"Cannot add the specified assembly to the global assembly cache"

error during installation

Cannot add web parts to a SharePoint page

Error socializing a SharePoint site to Jive

Jive Copy workflow is no longer available for manual initiation, or no

longer automatically starts

Jive installation test fails - SharePoint Administration

List widget shows broken image icon and/or challenges user for

credentials

Search URL for SharePoint items in Jive search results shows

internal SharePoint URL

Searching SharePoint from Jive fails

SharePoint location test fails - Jive Admin Console

SharePoint Site Admin pages show "Error" and "Unknown Error"

SharePoint user activity not showing in Jive

Users repeatedly prompted for credentials

Jive Doesn't Recognize a SharePoint User After Install/Upgrade

SharePoint Activity stream times out or generates an error

Unable to access SharePoint user interface to view or modify

socialization settings

Using Jive and SharePoint Together

Viewing SharePoint Content in Jive

Adding a SharePoint Widget:

SharePoint Sites Widget:

Adding a SharePoint Widget:

Configuring the List Widget:

Adding a SharePoint Widget:

Configuring the Calendar Widget:

Viewing the Calendar Widget:

Using Web Parts in SharePoint

Adding Jive Web Parts:

Activating and Deactivating Jive Web Parts:

Editing a Jive Web Part:

Using the Socialization Features

Workflow Association

Manual Workflow Initiation

Populate Metadata Fields

Copy Document