Deploy the HPC Web Parts Solution and Specify the Head Node

Applies To: Office SharePoint Server 2007, Windows HPC Server 2008

This topic describes how to deploy the HPC Web Parts solution that is included in the HPC Pack 2008 SharePoint Integration Sample. Before completing the steps in this topic, review the Requirements for Installing and Using the HPC Web Parts.

This topic includes the following steps:

• Step 1: Extend the web.config file

• Step 2: Deploy the HPC SharePoint solution

• Step 3: Specify the Windows HPC cluster to use

Step 1: Extend the web.config file

The following procedure includes steps to extend the web.config file on your SharePoint server to support the AJAX features in the HCP Web Parts. To edit an XML file, you can use a program such as Notepad, Visual Studio, or XML Notepad 2007, which can be downloaded from the Microsoft Download Center (https://go.microsoft.com/fwlink/?LinkId=139128).

To extend web.config

1. Log on to the server that has Office SharePoint Server 2007 installed.

2. Open the web.config file in the C:\inetpub\wwwroot\wss\VirtualDirectories\80\ folder.

   Important

   If your site is not using port 80, go to the folder that corresponds to the port number you are using (C:\inetpub\wwwroot\wss\VirtualDirectories&lt;PortNumber></STRONG>). If you are using a different port number, you also need to specify the web URL when you run setup.bat, as described in Step 2: Deploy the HPC SharePoint solution later in this topic.

3. Add the following <sectionGroup> elements within the <configSections> element:

       <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
         <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
           <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
           <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
             <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="Everywhere" />
             <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" />
             <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" />
           </sectionGroup>
         </sectionGroup>
       </sectionGroup>
   

4. Add the following controls declaration within the <pages> element, which is located within the <system.web> element:

     <controls>
       <add tagPrefix="asp" namespace="System.Web.UI"
       assembly="System.Web.Extensions, Version=3.5.0.0,
       Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
     </controls>
   

5. Add the following assembly declaration within the <assemblies> element

     <add assembly="System.Web.Extensions, Version=3.5.0.0,
     Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
   

6. Add the following verb handlers within the <httpHandlers> element

     <add verb="*" path="*.asmx" validate="false"
     type="System.Web.Script.Services.ScriptHandlerFactory,
     System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
     PublicKeyToken=31bf3856ad364e35"/>
   
     <add verb="*" path="*_AppService.axd" validate="false"
     type="System.Web.Script.Services.ScriptHandlerFactory,
     System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
     PublicKeyToken=31bf3856ad364e35"/>
   
     <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"/>
   

7. Add the following script module handler within the <httpModules> element

     <add name="ScriptModule"
     type="System.Web.Handlers.ScriptModule, System.Web.Extensions,
     Version=3.5.0.0, Culture=neutral,
     PublicKeyToken=31bf3856ad364e35"/>
   

8. Add the following safe control entry within the <SafeControls> element, which is located within the <SharePoint> element

     <SafeControl Assembly="System.Web.Extensions,
     Version=3.5.0.0, Culture=neutral,
     PublicKeyToken=31bf3856ad364e35" Namespace="System.Web.UI"
     TypeName="*" Safe="True" />
   

9. Add the following scripting web service handlers within the <configuration> element

     <system.web.extensions>
         <scripting>
           <webServices>
           <!-- Uncomment this line to enable the authentication
           service. Include requireSSL="true" if appropriate. -->
           <!--
             <authenticationService enabled="true"
             requireSSL = "true|false"/>
           -->
           <!-- Uncomment these lines to enable the profile service.
           To allow profile properties to be retrieved and modified in
           ASP.NET AJAX applications, you need to add each property
           name to the readAccessProperties and writeAccessProperties
           attributes. -->
           <!--
             <profileService enabled="true"
             readAccessProperties="propertyname1,propertyname2"
             writeAccessProperties="propertyname1,propertyname2" />
           -->
           </webServices>
           <!--
           <scriptResourceHandler enableCompression="true"
           enableCaching="true" />
           -->
         </scripting>
       </system.web.extensions>
       <system.webServer>
         <validation validateIntegratedModeConfiguration="false"/>
         <modules>
           <add name="ScriptModule" preCondition="integratedMode"
           type="System.Web.Handlers.ScriptModule,
           System.Web.Extensions, Version=3.5.0.0,
           Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
         </modules>
         <handlers>
           <remove name="WebServiceHandlerFactory-Integrated" />
           <add name="ScriptHandlerFactory" verb="*" path="*.asmx"
           preCondition="integratedMode"
           type="System.Web.Script.Services.ScriptHandlerFactory,
           System.Web.Extensions, Version=3.5.0.0,
           Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
   
           <add name="ScriptHandlerFactoryAppServices" verb="*"
           path="*_AppService.axd" preCondition="integratedMode"
           type="System.Web.Script.Services.ScriptHandlerFactory,
           System.Web.Extensions, Version=3.5.0.0,
          Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
   
           <add name="ScriptResource" preCondition="integratedMode"
           verb="GET,HEAD" path="ScriptResource.axd"
           type="System.Web.Handlers.ScriptResourceHandler,
           System.Web.Extensions, Version=3.5.0.0,
           Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
         </handlers>
       </system.webServer>
   

10. Save and close web.config.