Now that you’re up and running, you’re ready to get into some serious development. Before we start looking at each of the functional areas in depth, let’s spend a bit of time getting to know the fundamentals of the Server Object Model and the SharePoint product in general.
Creating a Web Application
On the SharePoint platform, sites are provisioned on a farm according to a hierarchy. At the top level of the hierarchy is the web application. A web application is a web site in Internet Information Services 7 (IIS7), and web applications are automatically provisioned on all front-end servers within a farm. SharePoint content is stored in a content database, and when attached at the web application level, multiple content databases can exist within a single web application. Within a SharePoint farm, most farm level configuration is performed using a Central Administration web site. As part of the SharePoint 2010 installation process, this web application will be provisioned using a random port number. However, to make it easy to find, a shortcut will be placed in the Start menu in the Microsoft SharePoint 2010 Product folder.
Creating a Site Collection
The next step in the site provisioning hierarchy is the site collection. This collection of sites exists mainly as an administrative container. Each site collection can make use of a single content database, although more than one site collection can exist in the same content database. As a result, each web application can contain many site collections spread across a number of content databases. From a backup and restore perspective, the site collection is the lowest level of granularity.
Follow these steps to create a site collection:
Creating a Site
The final item in the provisioning hierarchy is the site. When creating a site collection, one or more sites are automatically provisioned. Each site collection must have a root site, but you can add more sites to a site collection if they are required. Furthermore, sites can also contain child sites. Although the site collection is the lowest level of granularity in terms of backup and restore functionality, you can import or export an individual site.
While import/export appears to achieve the same results as backup/restore, there are differences between these options, and backup/restore is the recommended approach when it comes to handling a significant volume of data. Although we use the Central Administration web site to create web applications and site collections, creating web sites is performed from the root site of a site collection or via SharePoint Designer. We’ll see the SharePoint Designer method in various examples in this; for now, we’ll use the root site method.
Share Point 2010 Related Interview Questions
|Web Services Interview Questions||XML Interview Questions|
|Share Point 2010 Interview Questions||ASP.NET Interview Questions|
|Share Point Administration Interview Questions||BizTalk Admin Interview Questions|
|Microsoft Office SharePoint Server (MOSS) Interview Questions||Biztalk Server Interview Questions|
|Asp Dot Net Mvc 4 Interview Questions||Biztalk Esb Toolkit Interview Questions|
|InfoPath Interview Questions|
Share Point 2010 Tutorial
The Microsoft Sharepoint 2010 Platform
Developing With Sharepoint 2010
Presentation Layer Overview
Client Object Model
Infopath Forms Services
Enterprise Content Management
User Interface Customization
Application Services Overview
Service Application Framework
Word Automation Services
Data Access Overview
Linq To Sharepoint And Spmetal
Business Connectivity Services
User Profiles And Social Data
Packaging And Deployment Model
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.