Addwppack: Stsadm operation (Windows SharePoint Services)
Applies To: Windows SharePoint Services 3.0
Topic Last Modified: 2007-04-20
Operation name: Addwppack
Description
Adds a Web Part package to the server Web Part gallery.
Syntax
stsadm -o addwppack
** -filename <file name>**
**\[-lcid\] \<language\>**
**\[-url\] \<URL name\>**
**\[-globalinstall\]**
**\[-force\]**
**\[-nodeploy\]**
stsadm -o addwppack
** -name <Web Part name>**
**\[-lcid\] \<language\>**
**\[-url\] \<URL name\>**
**\[-globalinstall\]**
**\[-force\]**
Parameters
Parameter | Value | Required? | Description |
---|---|---|---|
filename |
Any one of the following formats:
For example, “C:\WebParts\SampleWebPart.wpp” |
Yes |
Specifies the path to the cabinet file that contains the Web Parts and associated resources. |
lcid |
A valid locale ID, such as "1033" for English |
No |
Specifies a language for the Web Part package. |
url |
A valid URL, such as http://server_name |
No |
Specifies the URL of the virtual server on which to install the Web Parts. To install the Web Parts on every virtual server on a server, omit the url parameter. |
globalinstall |
<none> |
No |
Use to install the Web Parts in the global assembly cache (GAC) rather than in the Bin directories of each virtual server. Assemblies installed in the GAC are available to all applications on the server. |
force |
<none> |
No |
Overwrites an existing Web Part package with a new version. To repair a Web Part package, you must reinstall it. |
nodeploy |
<none> |
No |
Does not deploy any Web Part package from the Web Part gallery. |
name |
A name of a Web Part that has already been installed on another server in a server farm configuration |
Yes |
Installs the Web Part package from the configuration database by using the name parameter provided the Web Part package has already been installed on another server in a server farm configuration. |