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.
> 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.
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.
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 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.
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.
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" />
</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,Culture=neutral,PublicKeyToken=9df0a1232f502088" / > </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,Culture=neutral,PublicKeyToken=9df0a1232f502088" 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
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 Field Description
Impersonation • Allowed: The preferred choice. Required for out-of- the-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:
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.
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 Jive- specific 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