Step by Step procedures to Deploy SharePoint 3rd party Solutions in SharePoint

Step by Step procedures to Deploy SharePoint 3rd party Solutions in SharePoint:
Blog software installation steps in Share Point 2010

Steps:

Step1: Deploying the solution by using STSADM command
• Add Solution
• Deploy Solution

Step2: Enable the Blog features site Level in the Central Admin

Example: http://sp2010dev:10000/_layouts/settings.aspx (Central Admin)

Step3: Enable the Blog features at Site Collection Level.

Example:http://sp2010dev:15000/_layouts/ManageFeatures.aspx(Blog)

Step4: Enable OOB CKS themes on Blog Site (Modifying the Web.config File)
Note: We need to login with the Farm administrator Credentials in the server

Add CKS:EBE Solution:
1. Open the command line for the server.
2. If stsadm.exe is not on the path, change directory to the SharePoint BIN directory:
cd %PROGRAMFILES%\Common Files\Microsoft Shared\web server extensions\14\BIN
3. Add the solution to the farm by running the addsolution command:
Stsadm -o addsolution –filename c:\cks\cks.ebe.wsp
Note: Either copy the wsp file to the directory “C:\cks” or change the –filename value to the location of the wsp file
Deploy CKS: EBE Solution
1. Continuing from the command line above, run the command:
stsadm -o deploysolution -name cks.ebe.wsp -immediate -allowgacdeployment
Activate the Web Application feature
You can activate the web application feature of CKS: EBE using Central Administration
Central Administration Activation:
1. From SharePoint Central Administration browse to Application Management.
2. In the SharePoint Web Application Management section choose Manage Web application features.
3. If necessary, change the Web Application selector to your blog site Web application.


4. Click the Activate button next to CKS: EBE Web Application Feature.
or Browse directly this link and enable
(http://sp2010dev:10000/_layouts/ManageFeatures.aspx)

Activate the Site Feature
Site Administration Activation
1. Browse to your Blog site.
2. Choose Site Actions | Site Settings.
3. In the Site Administration section choose Site features.(http://sp2010dev:15000/_layouts/ManageFeatures.aspx)
4. On the Site Features page choose the Activate button next to CKS:EBE Extensions.
Note: If we enable the above two features in the Central Admin and Blog Site then only we will able to see the following Tag in the Web.config file
< add name="CksEbeModule" type="CKS.EBE.BlogHttpModule, CKS.EBE,Version=0.1.0.0,Culture=neutral,PublicKeyToken=3e8b700c069fb747" / >

We can see the changes on our SharePoint web server(s) after deploying the solution :
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES: Contains
CKS EBE
CKS EBE Themes
CKS EBE Webapp
C:\Windows\assembly: contains
CKS.EBE
CKS.EBE.SEARCH
C:\Program Files\Common Files\Microsoft Shared\Web Server extensions\14\TEMPLATE\LAYOUTS\cks\ebe:
Contains the utility pages like
Settings.aspx
TRACKBACK.ASPX

Enable OOB CKS themes on Blog Site:
Open web.config for Blog site and find the following line under section
< add name="CksEbeModule" type="CKS.EBE.BlogHttpModule, CKS.EBE,Version=0.1.0.0,Culture=neutral,PublicKeyToken=3e8b700c069fb747" / >
.
Go ahead and CUT that line above (we'll be pasting it somewhere else in a minute).
Next find the section simply labeled . In this section you will probably find 5 tags and 4 tags. Paste the "add" tag that you cut above so that it's after all the removes, but before the add's in the modules section. Also, you need to add a preCondition="integratedMode" attribute to this element. So, your whole section will look something like this (with your additions bolded below):



< modules runallmanagedmodulesforallrequests="true" >
< remove name="AnonymousIdentification" >
< remove name="FileAuthorization" >
< remove name="Profile" >
< remove name="WebDAVModule" >
< remove name="Session" >
< add name="CksEbeModule" precondition="integratedMode" type="CKS.EBE.BlogHttpModule, CKS.EBE, Version=0.1.0.0, Culture=neutral, PublicKeyToken=3e8b700c069fb747" >
< add name="SPRequestModule" precondition="integratedMode" type="Microsoft.SharePoint.ApplicationRuntime.SPRequestModule, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" >
< add name="ScriptModule" precondition="integratedMode" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" >
< add name="SharePoint14Module" precondition="integratedMode" >
< add name="StateServiceModule" type="Microsoft.Office.Server.Administration.StateModule, Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" >
< add name="RSRedirectModule" type="Microsoft.ReportingServices.SharePoint.Soap.RSRedirectModule, RSSharePointSoapProxy, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" >
< add name="PublishingHttpModule" type="Microsoft.SharePoint.Publishing.PublishingHttpModule, Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" >
< /add > < /add > < /add > < /add > < /add > < /add > < /add > < /remove > < /remove > < /remove > < /remove > < /remove > < /modules >

Save and Close the Web.config file

After that open the url : http://server:port No/home.aspx

References :

http://cks.codeplex.com/releases/view/28520#DownloadId=130561
http://cks.codeplex.com/releases/view/28520#DownloadId=130559
http://www.thekickboard.com/archive/2010/07/24/running-cksebe-3-0-on-sharepoint-foundation-2010.aspx