Sharepoint solution deployment and configuration guide

Introduction
This guide will walk you through the steps to deploy and configure “Number Research” sharepoint solution into a new server.

Pre requisite

• New Sharepoint site collection must have been created with defined URL.
  
• Application portal must have been restored from Development server into new server.
  
• Site navigation must have been restored to the new site collection.

Web parts and class library DLL list
Below listed DLLs are deployed in sharepoint server’s BIN folder when we install the sharepoint solution.
Web part DLL files (Naming convention is NOT required)
1) ABCTopHeader.DLL : To display filter controls
2) ABCReportViewer.DLL : To display SSRS reports.
3) ABCContentWF.DLL : To display WF Content
4) ABCReportMDM.DLL : To show all Business groups
5) MDMReportMDMBrands.DLL : To maintain brands
6) ABCReportMDMSiteDomains.DLL : To maintain Site domains
7) ABCETLDataManagement.DLL : To maintain data mapping
8) ABCETLMonitoring.DLL : To monitor data sufficiency
9) ABCArchivedReportsLink.DLL : To display Archive PDF list.
10) ABCReportMDMDataInput.dll : To insert / update traffic data
11) ABC_RDLCaching.DLL : To reset the SSRS RDL caching minutes
12) AchiveReportByForce.DLL : To create / update archive PDF file

Class library DLL files (with naming convention)
13) ADS.NumberResearch.Workflow.DLL : Custom workflow engine.
14) ADS.NumberResearch.PollingAgentClassLibrary.DLL : Polling agent objects.
15) ADS.NumberResearch.INABCReports.DLL : Report viewer class objects
16) ADS.NumberResearch.DBAccess.dll : Database access objects
17) ADS.NumberResearch.ArchiveReport.DLL : Archive report class objects

Sharepoint Solution deployment
Deployment is done in 7 steps.
1) Install Sharepoint solution in the already created SharePoint site collection.
2) Activate Sharepoint solution in site collection.
3) Create user groups in site collection
4) Update configuration files.
5) Restart IIS.
6) Assign site access permission to admin user.
7) Assigning permission to “Executive summary content list”

Step 1: Installing SharePoint solution (.WSP)

Installing Sharepoint solution file name: ABCSol.wsp
Ø This is a navigation configuration file.
Ø This solution contains web part files and class library DLL files also.
Installer EXE file name: STSADM.EXE
Ø This file can be found at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN Path on Server machine.
Installation command syntax: STSADM.EXE -o addsolution -filename %SOL_FILE%
Installation command: STSADM.EXE -o addsolution -filename ABCSol.wsp

Step 2: Activating SharePoint solution (.WSP) in portal

Installer EXE file name: STSADM.EXE
Ø This file can be found at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN Path on Server machine.
Installation command syntax: STSADM.EXE -o addsolution -name %SOL_NAME% -url
%PORTAL_URL% -immediate –allowcaspolicies –force
NOTE:
%PORTAL_URL% : Site Collection URL Ex: http://Number-Research:9999
%SOL_NAME% : ABCSol.wsp (Name of solution file)
Installation command: STSADM.EXE -o deploysolution -name ABCSol.wsp
-url http://Number-Research:9999 -immediate –allowcaspolicies –force

Step 3: Creating user groups in site collection

Installer EXE file name: STSADM.EXE
Ø This file can be found at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN Path on Server machine.
Note: We need the following Groups in site Collection.

Admin Owner : User in this group can access Admin Site
Admin User : User can Updated any Content
APPROVERS : User can approve workflow
EDITOR : Users can edit/write contents for reports/workflow
ABC OWNERS : Users are administrator of complete Site Collection (by Default)
VIEWERS : Normal User (by Default Created in Site Collection)
Installation command syntax: STSADM.EXE -o createGroup –URL %PORTAL_URL% -name
%Group_NAME% -ownerlogin %OWN_NAME% -type member
NOTE:

%PORTAL_URL% : Site Collection URL Ex: http://Number-Research:9999
%Group_NAME% : Name of new group Ex: EDITOR / APPROVERS / Admin Owner
%OWN_NAME% : Name of parent group which can manage users in this group

Installation command: (Replace the URL with actual value)
STSADM.EXE -o createGroup –URL http://Number-Research:9999 -name “Admin Owner”
-ownerlogin “Admin Owner” -type member
STSADM.EXE -o createGroup –URL http://Number-Research:9999 -name “AdminUser”
-ownerlogin “Admin Owner” -type visitor
STSADM.EXE -o createGroup –URL http://Number-Research:9999 -name Editor
-ownerlogin “Admin Owner” -type visitor
STSADM.EXE -o createGroup –URL http://Number-Research:9999 -name Approvers
-ownerlogin “Admin Owner” -type visitor

Step 4: Updating configuration files

Configuration files to update: 2 files

1) App.config
o Contains all the key elements required for Database Connection, User Names and SSRS configurations.

Note: This file must me checked/changed element by element as per new deployment environment.

2) Web.config
o Contains security configurations for site collection and other required key elements.
4.1) Update app.config

i) Change the following important key element values as per the new server configuration.
SharePointUserName => User name which has access to
Sharepoint web services
SharePointPassword => Password of the user name
SharePointDomain => Sharepoint domain name
SharePointHost => Sharepoint site URL.
SiteLinkUrl => Sharepoint site URL
ConnectionString => Database connection string
AdminUsers => List of admin. users’ email.
ReportRDLServerPath => URL of “ReportViewer.aspx”
ReportRDLServerWebServiceUrl => URL of “ReportService.asmx”
ReportRDLDeployedPath => RDL deployed path will normally be
“/Number/”
ii) Copy this file to the same location as web.config file
(Please see the Web.config file section below, to know about the location of it)
This configuration file will be referred in web.config file.
4.2) Update web.config
Location:
C:\Inetpub\wwwroot\wss\VirtualDirectories\%SITE_COL_PORT%
EX: For http://Number-Research:9999, web.config will be in C:\Inetpub\wwwroot\wss\VirtualDirectories\9999\
Update <appSettings> and <trust> elements
i) Point the <appSettings> element to app.config as shown below.

ii) Assign the trust level value to the newly created “Trust Level”.

Now portal is ready for operation.

Step 5: Restart IIS

Since solution is deployed and configuration files are changed, we must restart IIS.

Step 6: Assign site access permission to admin Owner at ADMIN Site

Remove the permissions of all user groups except from admin owner.
6.1) Open the portal in browser, and go to Admin Site.
6.2) Click the Site ActionàSite SettingsàPeople and Groups


6.3) Click the link Site Permissions

6.4) At Permissions Page, Click the ActionàEdit Permission


It popup a confirmation box, click on OK button

6.5) Now select all the permission, except ‘Admin Owner’

6.6) Click ActionàRemove User Permission


It popup a confirmation box, click on OK button.
Now Site is accessible ONLY to admin owner user.

Step 7: Assign permission to “Executive summary content List”

7.1) Open the portal in browser.
7.2) Navigate to [Site Action]à[View All Site Contents]


7.3) Open the List named ‘Executive Summary Content List’


7.4) Click [Settings]à[List Settings]


7.5) Click the link ‘Permissions for this list’

7.6) Click [Action]à[Edit Permissions]


7.7) Confirm the editing by clicking OK button



Here we need to provide the Contribute Permissions to all Groups which can View/Edit/Approve the workflow contents. Ex: see the Viewer Group


It has “View Only” Permission and hence we need to assign Contribute Permission.

7.8) Click the Viewer Group.


Select the ‘Contribute’ Permission and Press OK button


Repeat step 7.8 to assign “Contribute permissions” to below listed user groups.
APPROVERS
EDITOR
VIEWERS


Now Site is ready for operation.