The deployment manifest <soultion> tag has an attribute "DeploymentServerType" , which takes either WebFrontEnd and ApplicationServer(not sure whats the default value though)
DeploymentServerType = "WebFrontEnd/ApplicationServer"
ResetWebServer = "TRUE"
SolutionId = "GUID">
For all my server farm, I have done MOSS installation of type "complete" for all my servers. Then as per requirement I have enabled different services(WEF, search, index, CA) on different servers. In this case, how does the deplyment solution knows which servers are a WEFs and which are application servers? Does it determine bt type of services running on a system or installation type(complete/WFE)?
Honestly, I usually leave that attribute out. It is optional. I think the default is WebFrontEnd, but I am not competely certain. If you are just doing standard development of features or whatever, I think it is safe to leave out. It will deploy to any server on your farm that is marked as a web front end when you attached it to the farm.
Corey Roth blog: www.dotnetmafia.com twitter: twitter.com/coreyroth
I did the same thing, left that attribute out and the package got deployed in all the servers in my server farm, which I did not want. I wanted that to be deployed only two 2 WFEs ..
What actually I wanted to know is, how the deployment package knows which servers are WFEs and which are application servers?
- 편집됨 Sanban 2009년 4월 14일 화요일 오후 6:04 chnage
Any server that has the Microsoft SharePoint Foundation Web Application service started (on Services on Server page) is considered a Web Front End Server. If you leave that DeploymentServerType attribute blank, it'll deploy on all servers that have that service started.
You might have application tier servers that only run Central Administration and other SharePoint service applications, and you might want to deploy your solution only on those servers (for example Central Administration pages or Custom Actions). In that case, you set the attribute to "ApplicationServer".
The downside, as Eric mentioned, is that if your WSP has features in it, they won't get installed automatically when the solution is deployed, no matter what you set on the Feature in your Visual Studio project. You have to manually run the stsadm or powershell commands to install your feature.