|
(SharePoint 2010)
SharePoint 2010 brings Multitenancy Architecture to share content on the same farm, so instead of setting up the separate harware we can partition data or other services to accomodate multiple tenants.
Multitenancy is tied to site subscription - it is a logical group of site collections that can share settings, features, and service data. Site collections for each tenant are brought together with a subscription ID. The subscription ID is used to map features, services, and sites to tenants and...
(SharePoint 2010)
SharePoint 2010 Site Changes
Role/Rule based Audience Targeting – added rules-based audiences, WSS groups and distribution list membership.
Sites are collection of pages - SharePoint 2010 sites became more page-focused rather than a collection a lists. Sites still contain the same list and libraries as previous versions of SharePoint, but the site is now a collection of pages.
Pages are optimized for Reading – all WCM pages are optimized for the reading, rather than for the writing, ...
(SharePoint 2010)
Search Changes
Three ranges of search– Search Server 2010 (Entry Level), OOTB Seach, (Infrastructure), and FAST Search (high-end). FAST will be licensed through our Enterprise CAL (for internal search) with an additional server
No more 50 millions items limitation- FAST provides powerful capabilities to index hundred millions items, so no more SharePoint 2007 index limitations
Query syntax – can use AND, OR, NOT keywords in search query
Wildcard search - using * in search query
...
(SharePoint 2010)
SharePoint 2010 database model has been changed significantly in the way of distributing data across several databases that makes horizontal distribution of SharePoint 2010 solutions very feasible.
There are three areas of changes - architecutre changes, new databases and new tables.
Architecture Changes
SharePoint 2007 stored all content in large tables (for example lists, site collects end etc were represented as a huge table), and the performance were affected by SQL Server locks, esp...
(SharePoint 2010)
What’s new in Services
SharePoint 2010 provides the new architectural model of services, deprecating the SSP approach completely. Instead of this SharePoint 2010 provides new approach of the isolated set of services that can be easily shared across web applications and site collections
Service Name
Service Description
Access Services
Enables users to view, edit, and interact with Microsoft Access databases in a Web browser.
Application Registry S...
(Tips and Tricks)
By default, Office SharePoint Server 2007 uses all of the front-end Web servers in the server farm to crawl content in the same server farm. The index server sends requests to each WFE server in the farm. The front-end Web servers get the requested content from the SharePoint sites in the farm and forward that content to the index server for indexing.
This works well for small-to-medium-size organizations. Large organizations, however, tend to crawl more content than small organizations. This ...
(Practices)
Question:
>> What are the limitations of SSP?!
Answer:
The major disadvantage of SSP in its architecture, when you configure SSP services and all Web Applications are linked to SSP and services, even if these services are not used by that Web Application. Such situation creates overheading of SSP services.
You also can't link one or any SSP service to specific Web Application - only create new SSP for this purposes
(Tips and Tricks)
SharePoint comes with the list of proprietary controls that you can use in your applications. Controls are splitted between:
User Controls that locates in 12-hive\TEMPLATE\CONTROLTEMPLATES folder - 58 controls
Web Controls in Microsoft.SharePoint.WebControls namespace - about 212 controls (Microsoft.SharePoint.Dll, Microsoft.SharePoint.ApplicationPages.Administration.dll)
Some of these controls with description and screenshots are available there and there.
Knowing these controls pl...
(Tips and Tricks)
SharePoint provides you two models for development – Web Services and API for object model. But very often developers are a bit confused about what to use and when.
SharePoint API provides access to all pillars of SharePoint – advanced functionality via features set and good performance . It’s a preferable solution when code resides on the SharePoint server with the access to server to deploy features and other’s library.
SharePoint Web Services provide almost the same level function...
(Tips and Tricks)
There are several ways to build disconnected systems based on SharePoint. But all of them have pros and cons. The following table shows what each of disconnected scenarios supports.
Feature
File System
Outlook 2007
Groove 2007
Access 2007
Offline documents
Yes
Yes
Yes
No
Offline Lists
No
Yes
No
Yes
More then one document at a time
No
Yes
Yes
N/A
Automatic sync for documents
No
No
Yes
N/A
Two-Way sync
No
Yes (PIM li...
(Tips and Tricks)
When SharePoint creates a Web application the following actions happening behind the scene: Web Ste:
Creates a unique entry in SharePoint configuration DB for the Web App and assign GUID to that entry;
Create and configures a Web application in IIS;
Creates a root folder to store the Web application pages and associated resources;
Creates and configures an IIS application pool;
Configures authentication protocol and encryption settings;
Assign a Default alternate access mapping ...
|