http://alonsorobles.com/2007/07/05/189-stsadm-operations/ technology, academia, and other tidbits from the trenches of a boggled mind Fri, 21 Oct 2011 23:32:49 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://alonsorobles.com/2007/07/05/189-stsadm-operations/comment-page-1/#comment-6 Alonso Robles / Creating a SharePoint Solution for an InfoPath Form Template Deployment Thu, 05 Jun 2008 06:19:16 +0000 http://blogs.importchaos.com/alonsorobles/2007/07/05/189-stsadm-operations/#comment-6 [...] Quickly reviewing the commands above, we can see that we changed our working directory to the location of the publish path of the InfoPath form template (and the solution files). Then we generate the WSP file with the MAKECAP utility. Finally, using the STSADM utility we added the solution, deployed it, and activated the feature (for more information STSADM operations see my post on the 189 STSADM Operations).  [...] [...] Quickly reviewing the commands above, we can see that we changed our working directory to the location of the publish path of the InfoPath form template (and the solution files). Then we generate the WSP file with the MAKECAP utility. Finally, using the STSADM utility we added the solution, deployed it, and activated the feature (for more information STSADM operations see my post on the 189 STSADM Operations).  [...]

]]> http://alonsorobles.com/2007/07/05/189-stsadm-operations/comment-page-1/#comment-5 Alonso Robles / Creating Solution Packages for WSS 3.0 and MOSS 2007 Deployments Sat, 17 May 2008 00:00:19 +0000 http://blogs.importchaos.com/alonsorobles/2007/07/05/189-stsadm-operations/#comment-5 [...] But in all seriousness, the deployment of a solution package happens in two stages. In the first stage, or the installation stage, WSS takes the WSP file and copies it to the configuration database. In the second stage, or the deployment stage, WSS takes the WSP file from the configuration database, extracts the content(s), and places the content(s) as specified in the package meta-data. Simple huh? Obviously, a system administrator needs to tell WSS to install and deploy a package. This is easily accomplished by executing three simple STSADM utility commands. [...] [...] But in all seriousness, the deployment of a solution package happens in two stages. In the first stage, or the installation stage, WSS takes the WSP file and copies it to the configuration database. In the second stage, or the deployment stage, WSS takes the WSP file from the configuration database, extracts the content(s), and places the content(s) as specified in the package meta-data. Simple huh? Obviously, a system administrator needs to tell WSS to install and deploy a package. This is easily accomplished by executing three simple STSADM utility commands. [...]

]]>