Changes to web.config on Installation

When you install the connector (activate the Jive Infrastructure web application feature), the entries described in this topic are added to the web.config files associated with the appropriate web applications. When you uninstall the connector (deactivate the Jive Infrastructure web application feature), all web.config entries should be removed unless other third-party tools have added the same web.config entries for their purposes.

Note: This topic is provided for informational purposes, describing how web.config is altered during installation so that you're aware of the changes. In most cases, you shouldn't need to take any action because of these changes.

ScriptResource HttpHandler

This is an HTTP handler for processing requests for script files that are embedded as resources in an assembly. It is basic AJAX capability used in ASP.NET but not embraced by SharePoint 2007. Note that other third-party tools may do this as well, so removing this by hand could affect other tools.

<system.web> 
    <httpHandlers> 
        <add verb="GET,HEAD" path="ScriptResource.axd"
            type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0,
            Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false" /> 
    </httpHandlers>
</system.web>

Binding Redirects

This is an assembly binding redirect so that ASP.NET 3.5 versions of System.Web.Extensions.dll and System.Web.Extensions.Design.dll can be used. It is basic AJAX capability used in ASP.NET but not embraced by SharePoint 2007. Note that other 3rd party tools may do this as well, so removing this by hand could affect other tools.

<runtime> 
    <dependentAssembly> 
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" /> 
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" /> 
    </dependentAssembly> 
    <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" /> 
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" /> 
    </dependentAssembly> 
</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