System Center Service Manager includes two types of web parts as follows:
1. End user specific web parts. E.g. Web part for global announcements.
2. Analyst specific web parts. E.g. Web parts for manual and review activities.
One deployment option is to manually deploy the web parts to SharePoint – this can be cumbersome. This option involves copying all the web part assemblies, modifying the site’s web.config file to register the web parts as safe controls, creating a custom security policy file or adding the assemblies to global assembly cache (GAC) and so on.
The other deployment option is to deploy the web parts using a solution package (WSP). A solution package is a cabinet file containing all the web part assemblies, solution, and feature manifests, required web part resources, etc.
Web Parts solution file is attached. For System Center Service Manager 2010 RTM version use this file
SP1 solution file contains both end user and analyst portal web parts.
An advantage of using solution deployment is that all the changes made to web.config file, and the web application are atomic and can be easily undone by retracting the solution using the WSS solution management.
Steps for deploying SM web parts solution to a SharePoint web application:
Install SM portal using the Setup on the SharePoint server. This is required for v1 even if you don’t intend to use the out of the box Service Manager Portal. After you have installed the SM portal and WSS 3.0 it should look like this in IIS -
2. Add the solution package to the solution store. Go to the SharePoint central administration site->Operations->Solution Management. Since there is no way to do this from the UI you need to use the command-line
. You can copy the WSP file to where stsadm is installed for convenience. stsadm ships with WSS 3.0 or Microsoft SharePoint Server 2007 and can be found at “%COMMONPROGRAMFILES%\Microsoft shared\web server extensions\12\bin”. Remember to use the correct WSP file either RTM or SP1 based on your installation. Adjust the stsadm command line to reflect the correct file name.
3. Then deploy the solution to the site from the central administration solution management website or by using stsadm tool. To deploy using the UI go to the SharePoint Site Solution Management UI and click the web parts WSP that we added to the solution store in the last step. Then deploy it by clicking “Deploy Solution” as shown in the picture below.
This will deploy the required web part binaries to the web application bin folder along with their resources. It will also mark the web parts as safe controls by adding the following two SafeControl elements to the SafeControls element web.config file -
Advantage of using solution deployment is that all the changes made to web.config file, and the web application are atomic and can be easily undone by retracting the solution using the WSS solution management.
4. There is one thing you still need to change in the site’s web.config file. Open the site’s web.config and comment out the trust element. If you don’t want to remove the trust element the recommended option is to define a new
policy file and use it. I will provide more details on that in another blog. Another option is to add the web part binaries to GAC.
<trust level="WSS_Minimal" originUrl="" />
5. Go to Site Settings->Site Features and activate the Service Manager web parts feature. This will populate the web part gallery of the site with the SM web parts.
6. Go to IIS and change the application pool identity of the SharePoint services site (where you want to deploy the solution package) to SM SDK service account.
7. In the Features view of the SharePoint site make sure that
8. Change the session state mode of the SharePoint Site to “Use Device Profile”.
9. Create the web part pages using the web parts populated to the web part gallery in the last step.