Critics to SharePoint resource deployment “stsadm –o copyappbincontent”


When you start to work with localization in SharePoint, I believe that you may end with one of Mikhail Dikov proposal here or here .

Partially I agree with his proposal, to leverage the resource deployment through the UI. However, his strategy may fail when you apply to server farm architecture with multiple Web Front End (WFE).

You have to go to every WFE, and activate/deactivate the feature before you can get it deployed in all WFE. The same concept as standard SharePoint’s stsadm command,

stsadm –o copyappbincontent

That command, instruct local SharePoint server to copy resources, sitemap etc. to web all application folder, except the Central Admin webapps.

And still we have big problem, that we have to run that command in every WFE.

I can say this is a big problem, because it against the concept of centralized deployment of WSP. Imagine, if you’re system administrator who wants to have WSP to automate distribution of artifact – and now you are facing a fact that since the WSP contains resources; you don’t have the centralized deployment concept anymore.
After doing

stsadm –o addsolution

stsadm –o deploysolution

in one of WFE - then you have to go through all WFE to execute

stsadm –o copyappbincontent

to deploy resources to webapps.

I know that some system administrator / production team, so we have to solve this problem. May be change it to stsadm –o copyfarmappbincontent , to perform appbincontent deployment in farm architecture.

Riwut Libinuko
Sr. Cloud Solution Architect

My research interests include distributed robotics, mobile computing and programmable matter.

comments powered by Disqus