Thunder.Sun

这些天闲暇无事，将BPIO解决方案中最受好评的解决方案文档管理解决方案修改了一下，使之能够在MOSS英文环境中应用，感兴趣的同学们可以下载回去部署实验。具体部署流程如下：

1. 部署Kaneboy的用户控件包装器，并在所需要的web应用程序虚拟目录中的Web.config里设置trustLevel=Full.

2. 将Layouts_Images目录下的图片拷贝到如下文件夹：

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES

3. 将treeMenu文件夹拷贝到如下文件夹：

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS, 并为treeMenu创建虚拟目录，在IIS的站点的_layouts虚拟目录下.

4. 将VirtualDirectoryBin文件夹下的dll文件拷贝到web应用程序虚拟目录下的Bin目录中

例如：C:\Inetpub\wwwroot\wss\VirtualDirectories\80\bin

5. 将wpresources文件夹下的文件拷贝到web应用程序虚拟目录下的wpresources目录中

例如：C:\Inetpub\wwwroot\wss\VirtualDirectories\80\wpresources

6.将templates文件夹中的所有stp文件上载到站点中

7. 创建网站，之后，按照之前上载的模板分别创建好文档库以及相关列表

1. 使用AllDocuments的文档库模板创建名字为All Documents的文档库

2. 使用SortListE的自定义列表模板创建名字为SortList的自定义列表

3. 使用TreeTypeE的自定义列表模板创建名字为TreeType的自定义列表

4. 使用StatdocumentE的自定义列表模板创建名字为Stat document的自定义列表

7、 创建一个页面(User Page），加入QuickPart的Provider webpart，点击修改共享web部件, 选好需要显示的User Control，如 ，这一个是供用户使用的treeview User Control，点击Apply, 再点击Modify shared webpart，这时可以定制用户需要使用的树的类型属性，如点击OK。生成好的Tree如图：

 

 

 

之后再按照之前的操作过程，创建一个新页面放置tree management user control，如图：

 

然后，我们再回到之前创建的第一个页面，选择放置Document List User Control

在页面上放置一个consumer类型的Quick Part，之后在其中选择放置DocumentList User Control 放置成功之后，如图

之后，选择Tree View为Documents List 提供数据

如图

完成之后，显示效果如下：

部署包：下载

今天摆了一个弱智大乌龙，客户生产环境中有一个月报表，期望按照2个person and group列对当前用户进行过滤，并且有3项指标其中之一在70%以上的时候显示。俺自信满满的答应客户100%能实现，结果发现DataViewWebPart的筛选条件最多就能有10个，俺的那个view却怎么算都不止10个……

众所周知，在MOSS中，应用Search功能的时候。都是用login帐户的权限来决定Search结果，这在AD验证的时候，不会出什么岔子。基本上不必劳神。但是当Form验证的时候，问题就来了。Form认证的帐户，是没办法做这个工作的。那么如何来配置Search帐户，来保证Search工作正常运行且Search结果符合用户的权限呢？ 一个最简单的方式就是在AD验证的基础之上扩展出Form验证。这样，将扩展出来的Form认证的site的URL添加进搜索范围，就好了，得到的结果跟AD验证的Site完全一样。当然，首先你要打上SP1补丁包。以下是微软官方的原文:

 

Crawling Content

The crawl process for Microsoft Office SharePoint Server (MOSS) 2007 and Windows SharePoint Services 3.0 content (in this article series, collectively referred to as SharePoint Products and Technologies) is designed to use Windows authentication. When Office SharePoint Server 2007 was released, it was not able to crawl content that was secured with forms authentication. In Service Pack 1, SharePoint Products and Technologies include the ability to set special crawl rules that describe cookie-based authentication so those sites can be crawled. However, it does a simple crawl of the content only, and does not capture security information or the kind of rich metadata that the crawler can gather when using the native SharePoint protocol handler.

 

For those reasons, whether or not you have applied Service Pack 1, it is recommended that you crawl SharePoint sites protected by forms authentication by using the native SharePoint protocol handler. If your Web application already includes a zone that is secured with Windows authentication, in most cases you can use that zone for crawling. If your Web application has only a single zone and it is secured with forms authentication, you need to extend it into a new zone by using Windows authentication to support the native protocol handler. For more information, see Prepare to Crawl Host-Named Sites That Use Forms Authentication.

 

When you extend the Web application into a new zone, remember the following rules:

 

If you are using only Windows SharePoint Services, the Default zone must be secured with Windows authentication. If the Default zone is secured with forms authentication and a secondary zone uses Windows authentication, the crawler will not be able to index it.

 

If you are using MOSS 2007, the Default zone can be secured with Windows authentication, but it does not have to be. You can use forms authentication for the Default zone and extend a separate zone for Windows authentication. However, you must change the start address in the default content source to the URL for the Windows authentication zone. When a new Web application is created, a start address is automatically added that uses the URL for the Default zone. MOSS 2007 gives you the flexibility to change the values in the list of start addresses, but Windows SharePoint Services does not.

 

To change the start address

Open your browser and navigate to the Shared Services Provider (SSP) Web site.

 

Click the Search Settings link.

 

Click the Content sources and crawl schedules link.

 

Click the Local Office SharePoint Server sites link.

 

In the Edit Content Source page that opens, in the Start Addresses section, edit the addresses in the box.

 

Click OK to save your changes.

 

 

正如大家所期盼的。Microsoft Office SharePoint Server 2007 Administrator's Companion的翻译工作，最快可能在年末结束。这次有幸跟伟大的涂曙光同学，以及陈曦，赵琦峰，柴晓伟等各位高人一起来做这件工作。期望能尽快结束，让这部曾经是最厚的MOSS巨著中文版早日面世！（我会祈求出版社隐瞒我翻译的具体章节，以避免鸡蛋和西红柿主宰我今后的生活……  -_______-bb  ）

以前都是写写让人牙倒的抒情文章骗骗小姑娘。最近终于发现，没有一个专属的技术博客，屡屡的遭到大家的怀疑，已经到了没办法再装一个技术专家的地步，遂在博客园开了个地盘。继续龌混如此这般……    大家多多捧场哦……