put manifest Method
The put manifest method deploys a manifest on the specified site.
Syntax
method=put manifest:server_extension_version
&service_name=/&options=(first pass|second pass)
&prefix=url[&url_renames=key-value_pairs]
[&guidmap=key-value_pairs]&filelist=names
Parameters
Decoded
POST /site_url/_vti_bin/_vti_aut/author.dll HTTP/1.0
.
.
.
method=put+manifest:6.0.n.nnnn
&service_name=/&options=first+pass
&prefix=url
&filelist=names
[manifest]
Remarks
The put manifest method is called twice by the Microsoft SharePoint Migration Tool (smigrate.exe) during migration of a SharePoint site. In the first pass the put manifest method is used to apply, for example, the site template to the site and to restore the lists and list data. After the first pass, the put document method is used to upload files to the new site. Then, in the second pass, the put manifest method is used once again to apply, for example, the discussions and alerts to the site.
In the first pass, the put manifest method performs the following actions:
- Applies the site template to the site.
- Restores general site settings.
- Restores lists and list data.
- Restores security groups and users (when migrating from SharePoint Team Services from Microsoft v1).
- Creates the directory structure and 0-byte temporary files for document library files.
In the second pass, the put manifest method performs the following actions:
- Performs link repair in documents.
- Finalizes navigation structure.
- Restores Web Parts.
- Restores home page views (when migrating from SharePoint Team Services from Microsoft v1).
- Restores discussions.
- Restores alerts.
Note The guidmap and url_renames parameters are used by smigrate.exe only in the second pass of the put manifest method.
To run code that uses the put manifest method to migrate sites, the user must be a member of the Administrator site group. To run code that uses this method to deploy Microsoft Office FrontPage 2003 Web Packages, the user must be a member of the Web Designer site group.
Return Value
Success
Returns a list of URLs to skip, a mapping of URLs to rename, a mapping of URLs to move, a list of messages to consider "successes", a list of messages to consider "failures", and the prefix to which the manifest is deployed.
The following table lists and describes the sections returned by this method.
| Section | Description |
|---|---|
| skip urls | The server passes back a list of files that it automatically generates and that should not be uploaded by the client. |
| renamed urls | The server recommends that these files and folders be renamed. These files and folders should be uploaded from the client computer using the new recommended names. If the same file name is listed in the skip urls and renamed urls sections, the client should not upload the file. Note that this section is used by the url_renames parameter during the second pass. |
| moved urls | The server assigns a new location for these files. The file should be uploaded from the client computer to the new location specified. |
| guidmap | The server assigns new IDs for items in the site according to this map. Note that this section is passed as the guidmap parameter during the second pass. |
| successes | The server returns a list of messages to the client computer indicating individual successes during the operation. The client computer can display these messages to the user or record them in a log file for later review. |
| failures | The server returns a list of messages to the client computer indicating individual errors during the operation. The client computer can display these messages to the user or record them in a log file for later review. |
Error
Returns an error message in standard format. For more information, see Error Message Format for FrontPage 2002 Server Extensions from Microsoft.