Deploy and retract a WSP in SharePoint 2007 using Central Admin

I once had an engineering professor that said ‘It is easy once you know how to do it.’  Obviously, but first you have to know how to do it.
This is pretty basic but if you are learning SharePoint administration but I figured I would throw it up here in case someone needed to learn it. 
Deploying and retracting a WSP in SharePoint 2007 is makes managing customized SharePoint sites much easier to maintain and manage.  Instead of dropping DLL’s in the GAC or bin, and adding features to the site manually, the WSP or solution package wraps customizations up into a nice portable package.
There are three steps to deploying a WSP in a Farm
1.       Add the Solution to the Farm (this is the only step that must be done with the stsadm command line tool, all others can be done via the GUI in central admin)
Go to a command prompt and type: stsadm –o addsolution –filename “C:\yourWSPpath\yourWSPname.wsp”

2.       Deploy the Solution to the Farm or Web app depending on how it is scoped.
This is done by going into Central admin select Operations->Solution Management (under Global Configurations section) -> Name of your WSP you added -> Deploy Solution.

At this point, if your Solution is scoped not scoped at the farm level you will get an option of what applications you want to deploy the solution to, if it is at the farm level you will have to deploy globally.

That’s it, you have deployed your solution.  Depending on how the code is written you may have to go in and activiate features, but the code is now there.

To remove a solution from a Farm:
1.       Retract your solution.
This is done by going into Central admin select Operations->Solution Management (under Global Configurations section) -> Name of your WSP to retract->  Retract Solution.
In order to remove the solution it must be retracted form all web applications that it was deployed to.
2.       Delete the solution
This is done by going into Central admin select Operations->Solution Managemen
(under Global Configurations section) -> Name of your WSP to retract->  Retract Solution.

Comments

Post a Comment

Popular posts from this blog

Metastorm - Open form in an action from a list or link

Below is the SQL underneath the custom list with the link to open an action.  If you are opening from outside of a Metastorm client, you may need to add the ‘SessionID’ parameter containing a valid session ID 9.  I haven’t tried this with the current 9.1 SSO, it may be unnecessary.   If the session id parameter is still necessary, usually we write a wrapper aspx page to authenticate to user, grab the session id and redirect them to the action. The syntax is http://<servername/Metastorm/eForm.aspx?Map=<process map name>&Action=<action name>&Folder=<folder name>&FolderID=<folderid>&Service=<BPM Service Name>&Client=External&FolderLaunchURL=&FolderCancelURL=&IsFolderAction=True SELECT eFolder . eFolderID , eFolder . eFolderName , eFolder . eStageName ,   eFolder . eUpdated , eFolder . eSubject , ITProjectInitiation . txtProjectName ,   CASE       WHEN LEN ( ITProjectInitiation . txtNextAction ) > 1          
Read more

Corporate Intranet Information Architecture – a Publishing Site

Image
There have been several occasions in my consulting career where I have discussed what a corporate intranet should look like.   There are several aspects to this question, branding, custom web parts or other bells and whistles, but I believe that the fundamental structure or information architecture is one of if not the most important aspect of a solid, useful corporate intranet. Clearly, each individual company will have a unique look and feel and information architecture.   This will depend on the underlying business as well as the relative size, geographical locations and languages of the company. However, I have noticed certain commonalities across companies and have started to develop a template of how I can help an organization visualize there corporate intranet.   This could be used as a target to reorganize an existing intranet or as a template to stand up a new one.   In either case, changes will have to be made to suit the individual company’s needs.   Most companie
Read more

No Search Results in SharePoint Contextual Search OSSSearchResults.aspx

This is another one for me so I never have to figure this out again.   All the other posts I found when looking into this talked about how to set up a search center and redirect people over there.   That is pretty well documented at this point, but the problem I had was that people were trying to search the local site, being direct to the out of the box _layouts/OSSSearchResults.aspx page and getting no results.   The fix was frustratingly simple, check your alternate access mappings.   If you have extended the web app and users are using the new AAM then that could be the reason that the OOTB search results are not working.   In my case I had the short name as the default, and the FQDN as the custom, I switched them and now everything works.
Read more