moss工具集相关

● SharePoint Server 2007 SP1
Windows SharePoint Services 3.0 SP1
Office SharePoint Server 2007 SP1
SharePoint Designer 2007 SP1
先安装WSS 3.0 SP1，然后再是MOSS 2007 SP1。SharePoint SDK Online的内容也更新到了最新的2007年12月版本（WSS 3.0 SDK, MOSS 2007 SDK），可下载版本随后会发布。
WSS 3.0 SDK中，专门新增了一个章节，来讲述我之前介绍过的External Storage API。

● 推荐工具：SharePoint Content Deployment Wizard
可以将网站集、网站、列表、列表项数据在站点间（或服务器间）进行复制，使用了SharePont的Content Migration API。
点击查看

● 信息工作者应用与管理系列Webcast
本系列从OBA、Enterprise Search、MOSS、EPM四大专题穿插讲解
址址：http://www.microsoft.com/china/technet/webcasts/class/iw.mspx

● SharePoint工作流(ASP.NET表单版)教学视频
出自Kaneboy大侠之手，其于ASP.net表单的SharePoint工作流资料实在太少，这个视频非常不错，就是声音差了点，不过还是可以看懂，谢谢Kaneboy
http://blog.joycode.com/kaneboy/archive/2007/11/29/112077.aspx


Details:

The SharePoint Content Deployment Wizard is a tool for SharePoint 2007 which provides the means to deploy the following content:

- site collections
- webs
- lists
- folders
- list items (including files)

Content is exported using the Content Migration API (PRIME) as a .cmp file (Content Migration Package) which can be copied to other servers for import. Unlike the out-of-the-box tools, the Wizard allows *granular* selection of content via a treeview.

The two screenshots which probably illustrate the concept of the tool best are:

Export selection screen:



Import settings screen:



N.B. In this beta version, not all possible deployment scenarios have been tested. Please take a backup before performing imports.

More details (taken from readme)

Usage notes

• The tool must be installed locally on the server which hosts the site
• Site URL - enter using format http://source.test.dev
• Import web URL - enter using format http://target.com/targetweb
• See 'permissions' note lower down

Import/Export characteristics

Since the Content Migration API is used, imports/exports have the following characteristics:

• • dependencies of selected content (e.g. referenced CSS files, master pages) are automatically included in the export - check 'Exclude dependencies of selected objects' to disable this
  • all required content types, columns etc. are automatically included in the export
  • in contrast to STSADM export, it is possible to retain GUIDs during deployment (where objects are not being reparented) - check 'Retain object IDs and locations' to enable this
  • no filesystem files (assemblies, SharePoint Solutions/Features etc.) are deployed - these must already be present on the target for the import to succeed)
  • the following content does not get captured by the Content Migration API - alerts, audit trail, change log history, recycle-bin items, workflow tasks/state

Reparenting

Reparenting of objects such as webs and lists is possible with the following usage on the import:

- enter the URL for the target web in the 'Import web URL' textbox
- ensure 'Retain object IDs and locations' is not checked

Permissions

The Content Migration API (PRIME) is used to package the content as a .cmp file, which can be copied to another
server for import. The application MUST be run from the SharePoint server(s), and MUST be run under the context
of an account which has appropriate SharePoint permissions - currently the way to specify an alternative user
to the currently-logged on user is by using the 'Run as..' feature in Windows 2003 (right-click on the .exe and
select 'Run as..').

See my blog post 'Introducing the SharePoint Content Deployment Wizard' for more screenshots and information - http://sharepointnutsandbolts.blogspot.com/2007/12/introducing-sharepoint-content.html

Chris O'Brien
http://feeds.feedburner.com/ChrisObrien