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.
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.
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.
• 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) .
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.
9. In the Installing dialog box, allow the installation to complete, then click Next.
10. 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) .
11. 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. 12. 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.
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,Culture=neutral,PublicKeyToken=9df0a1232f502088" / >
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) )
• 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.
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.
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