Изменения в SharePoint Server 2007. Что нового?

Article
07/12/2006

Коллеги!

Сразу скажу, что выдержка из документа "Technical Reference" из пакета

2007 Office Resource Kit Beta 2 Planning and Deployment Guides. За более детальной информацией обращайтесь к первоисточнику, но материал мне показался интересным для того, чтобы его вывесить на блоге.

Итак, какие возможности были добавлены, изменены или удалены?

Administration object model

Description: The Administration object model has been replaced.

Reason for change: The new object model is more complete.

Migration path: Developers will need to write new code.

Areas and Listings

Description: The object model, user interface, and architecture of both areas and listings have changed. Areas will now use Microsoft Windows SharePoint Services (version 3) web architecture, so the URLs of sites change. (Bucket webs will be removed during upgrade.) In a clean installation, the user will get portal webs that are named just like new Windows SharePoint Services version 3 webs. SharePoint Services 2.0 listings do not exist in Microsoft Office SharePoint Server 2007. There is a new feature called summary links for displaying links on a page. To preserve data and functionality, upgrading will move listings to a Office SharePoint Server 2007 list and use the content-by-query (CBQ) web part to display the items on a page. However, it is recommended that customers manually move their upgraded data to summary links, because this is the new feature for displaying, sorting, and grouping links on a page.

Migration path: During upgrade, areas will be automatically moved to webs, and bucket web URLs will be removed. Favorites and other externally saved links must be changed. Upgrading automatically moves listings to a Office SharePoint Server 2007 list and a CBQ Web Part. It is recommended that customers manually move the data to the summary links feature to get all of the benefits of easy in-page link editing. To do this, users must add a summary links web part or control to the page, and then manually copy links from the upgraded list to the summary links Web Part.

Controls on administrator pages

Description: The controls that were located on administrator pages have been replaced with new controls.

Migration path: Pages from SharePoint Services 2.0 that users have customized will continue to work, but might have new or deprecated controls on them. Users can remove deprecated controls from the page. New controls will be provided automatically.

Crawl schedules

Description: Previously, crawl schedules could be created and maintained in their own list. Crawl schedules are now completely tied in with content sources. You cannot define a crawl schedule outside of a content source. Customers will no longer find a page on which to manage their crawl schedules. Instead, they will have to specify crawl schedules on the content source page.

Reason for change: This change reduces the confusion caused by having to create content sources in one location and then link them to schedules in another location.

Portal Provisioning

Description: The user interface and object model for the provisioning feature have changed. The area creation user interface has been replaced by the WSS web creation user interface.

Migration path: If users have customized SharePoint Services 2.0 provisioning, their code will continue to work after upgrade, but it is recommended that they rework the code to use the WSS object model.

Query object model

Description: The Query object model has been replaced.

Reason for change: The new object model is more complete.

Migration path: Developers must write new code.

Search: Area alerts

Description: The Area Alerts feature has been removed.

Migration path: Customers will now subscribe to list alerts instead. To simulate the SPS v. 2.0 experience, users can subscribe to all of the lists within the area.

Search: Automatic propagation

Description: In SharePoint Server 2003, index propagation could be set up to execute as soon as a crawl was complete. Customers will no longer be able to set up index propagation in this way. The new continuous propagation feature is intended to be used in those scenarios in which customers previously used automatic propagation. The user will be aware of a change in the Administrator user interface for Search.

Reason for change: Continuous propagation improves functionality for the entire search system. The scenarios that were previously covered by automatic propagation are now covered by continuous propagation. Continuous propagation drastically improves the real-time availability of indexed content in search results.

Migration path: The upgrade process will migrate users who are currently using automatic propagation to continuous propagation.

Search: More Info link

Description: In earlier versions, there was a More Info link in search results. The link led to a page that showed name/value pairs for properties, and that allowed users to pivot on the author name. This link and page are no longer available.

Search: MySite Alerts

Description: The Alerts web part has been removed from MySite. Manage Alerts now happens at the site level instead of being rolled up to MySite.

Search: TIFF filter

Description: In earlier versions, there was a filter for TIFF formatted files. TIFF files would be translated into text with optical character recognition (OCR) software when it was crawled, and the text would be indexed. This feature has been removed.

Search: Web parts

Description: Search Web Parts have been deprecated. They will continue to work in SPS v. 3.0, but not in later versions.

Reason for change: The user interface has been improved.

Migration path: Use new web parts.

Shared Services

Description: In SharePoint Server 2003, each portal that was created had its own set of resource-intensive, high-value services. This condition severely restricted scale, so a feature was introduced that allowed all portals that were located within a single farm to share the same set of services. A second introduced feature allowed all portals located within a remote SharePoint Server 2003 farm to also consume services from a parent farm. In both cases, the change was both a substantial and a one-way switch: if the shared services option was chosen, all portals in the affected farms had to participate in the shared services; and once service sharing was turned on, there was no way to turn it off again. In the 2007 Microsoft Office system, the ability to share services is turned on by default, and it has been made flexible enough so that more than one set of services can be made available both within and between farms, and so that portals can move easily between sets of shared services.

Reason for change: This change improves scale, performance, and farm usability. SharePoint Server 2003 was restricted to 15 portals per farm. Customers can now host many more sites on a single set of hardware. Service level administration can now be delegated to power users. Customers can configure their systems to reflect current state (for example, they can move Web programs between sets of shared services to reflect organizational and political changes).

Migration path: Automigrated as part of the server upgrades collection.

Topology Management

Description: The Topology Management user interface has been replaced by a new management feature.

Reason for change: The inclusion of four additional products in Office Server requires a new method of managing the services on servers for ease of use. With the new feature, customers can manage all of the services and servers for all of the Office Server products in a uniform manner.

Windows SharePoint Services version 3 Security Model

Description: The old security model objects (SPRole, SPList.PermissionsMask, and others) have been marked as obsolete to encourage use of the new, role-based security model. There is now a new user interface for list-level permissions. Developers receive warnings if they try to use the obsolete objects in their code.

Reason for change: This change provides scalable security and a more consistent, role-based security model on all scopes: web, list, folder, and item.

Migration path: Users must rewrite custom code. Windows SharePoint Services version 3 performs migration of existing security settings during upgrade. An attempt to compile outdated code generates an error message.

Кроме того, в другом документе (Upgrading to Office SharePoint Server 2007) можно найти дополнительную информацию о сравнении функционала

Comparison of key features

Note This content is preliminary content for a preliminary software release. It might be incomplete and is subject to change.

Many things have changed between Microsoft Office SharePoint Portal Server 2003 and Microsoft Office SharePoint Server 2007. The following tables help you understand some of the key changes to terminology and features that immediately affect the administration and site management process after upgrading. For more information about changes to Office SharePoint Server 2007, see What's New for IT Professionals in Microsoft Office SharePoint Server 2007.

New concepts and terminology

SharePoint Portal Server 2003 concept or term	2nd_OSS_12 concept or term	Comments
virtual server?	Web application	Change in terminology.
Shared services	Shared Service Providers	The architecture behind shared services has changed quite a bit, to allow easier and more flexible sharing of resources. For more information, see (This link is not yet available. It will be available in later versions of this content.).
Areas	Subsites	SharePoint Portal Server 2003 areas are upgraded to subsites in the new version. To manage your site, on the Site Actions menu, click Manage Content and Structure.
Portal Security	Windows SharePoint Services Security	Portal security is now managed using the new Microsoft Windows SharePoint Services (version 3) security model. The groups and users are upgraded to this model. For more information about the new security model, see Chapter overview: Plan site and content security.
Custom authentication	New authentication choices	You can now use ASP.NET authentication methods, such as Forms authentication, with Office SharePoint Server 2007 instead of having to create a completely custom authentication solution. For more information, see (This link is not yet available. It will be available in later versions of this content.).
	Rights management	Now available for documents stored in document libraries.
SharePoint Portal Server 2003 backwards-compatible document libraries	Office SharePoint Server 2007 document libraries	SharePoint Portal Server 2003 backwards-compatible document libraries are not supported for Office SharePoint Server 2007. You can move any content stored in these libraries into standard document libraries in Office SharePoint Server 2007. A tool for migrating this content is under development. For more information, see (This link is not yet available. It will be available in later versions of this content.).

New or changed processes in the server administration experience

SharePoint Portal Server 2003 process	2nd_OSS_12 process
Create IIS Web sites using IIS tools	Create and configure IIS Web sites in Central Administration instead.
Difficult to change server topology	Use the topology management features in Central Administration to easily add, reassign, or remove servers from the farm.
Difficult to know which tasks are high priority and must be performed first	New Task List in Central Administration directs you to high priority tasks that must be completed before you proceed to create or configure sites.

New or changed features for searching

For more information, see Understand how search features are affected by upgrade.

SharePoint Portal Server 2003 feature	2nd_OSS_12 feature	Comments
“This Portal”/"Non-Portal" content sources	Default content source	Scope has changed from Portal Administration to Shared Service Provider.
Custom content sources	Content sources	Scope has changed from Portal Administration to Shared Service Provider.
Best bets	Best bets	Scope has changed from Portal Administration to Site.
Schedules	Content sources	Scope has changed from Portal Administration to Schedules.
Indexes	Indexes	In Office SharePoint Server 2007, there is only one index per farm, rather than multiple indexes with aggregated results as in SharePoint Portal Server 2003.
SharePoint Portal Server 2003 administrative object model		The SharePoint Portal Server 2003 administrative object model has been deprecated in Office SharePoint Server 2007. This means that any custom applications that rely on the Customers SharePoint Portal Server 2003 administrative object model will have to be rewritten to use the new object model in Office SharePoint Server 2007.

New or changed features in the authoring and site management experience

SharePoint Portal Server 2003 feature	2nd_OSS_12 feature	Comments
Listings Web Part	Content by Query Web Part or Summary Links Web Part	By default, Listings are upgraded to the Content By Query Web Part. This Web Part uses a query to display items in a Links list. The query is configured through Web Part properties. For more authoring and presentation control, consider manually moving Listings links to the Summary Links Web Part after upgrade.
Targeting Areas	Targeting Pages	To target a site after upgrade, you must enable targeting on the Welcome page of a site. For more information about targeting, see (This link is not yet available. It will be available in later versions of this content.).
Site Directory	Site Directory	The site directory has new pages after upgrade in order to show organizational categories.
	Pages	Pages are a new construct in Office SharePoint Server 2007. Pages are stored in a list called Pages. You can schedule, approve, and publish pages. For more information about site content management, see (This link is not yet available. It will be available in later versions of this content.).
Area Details Web Part	Contact Web Part, Title control, Description control	Office SharePoint Server 2007 splits the components of the Area Details Web Part into separate Web Parts. You can now move these Web Parts independently on a page.
News Listings	Links list items and pages	News listings are upgraded to Links lists or pages.
Welcome pages	Welcome pages	The way that welcome pages are handled has changed in the new version. If you had a site that was set to a welcome page outside of the current site (such as an external URL), the page is reset to default.aspx during upgrade. After upgrade, you can either change the navigation and add the external URL or use the redirect page to redirect default.aspx to the external URL.

Changes to areas

Change	Comments
Areas are now subsites	During upgrade, areas are converted to subsites of the portal. The home area becomes the top-level site in the site collection, and the next-level areas become subsites of that site, and so on. This changes the logical navigation for the portal, and also affects the URLs, as discussed below.
Portal URLs may have changed	URLs for sites and subsites in Office SharePoint Server 2007 follow the logical navigation structure. So rather than seeing https://portal_name/c2/area_name, you'll see https://portal_name/area_name or https://portal_name/sites/site_name.

Other changes

Change	Comments
Portal URLs may have changed	URLs for sites and subsites in Office SharePoint Server 2007 follow the logical navigation structure. So rather than seeing https://portal_name/c2/area_name, you'll see https://portal_name/area_name or https://portal_name/sites/site_name.
Client applications have trouble with the redirects	The Microsoft Office client application, do not work with the 302 redirects used to redirect users from an old URL to the new URL. So if a user attempts to open a document, for example, directly from their Word application, but are using an old URL, they may not be successful. The browser works with the 302 redirects, so if a user is having trouble with the client applications, have them use the browser to retrieve the file they need instead.
My sites have new look, features	During upgrade, the My Sites are upgraded to include the new look and new features available in Office SharePoint Server 2007.

Share via