Core SharePoint 2013 Concepts

CORE SHAREPOINT CONCEPTS
Course: SharePoint 2013 for Administrators and IT Pro's | Akrura Technologies
By : Isha Kapoor
SharePoint MVP, Author, Trainer and Founder
http://www.akruratechnologies.com/
http://www.learningsharepoint.com/ |
@LearningSP
SharePoint

OUTLINE…
• Introduction to SharePoint
• SharePoint Versions
• SharePoint Licensing
• SharePoint Office 365 vs. The Cloud vs. On Site
• SharePoint Architecture
• SharePoint Topology
• Intranet vs Internet sites in SharePoint
• Directory hive in SharePoint.
• SharePoint Hierarchy
• Introduction to SharePoint Central administration and Configuration wizard.
• Introduction to Tools used to Customize SharePoint
• Hardware and Software Requirements

INTRODUCTION TO SHAREPOINT
What Is SharePoint?
SharePoint is a Popular Content Management Tool developed by Microsoft that allows users to share data (like
word documents, Excel etc.) in a web-based collaborative environment.
SharePoint was Introduced by Microsoft in early 2001 and it has since gone through various versions; the latest
being SharePoint 2013, and has also Improved in terms of Collaboration and Integration with other LOB Tools.
SharePoint Today is used in 90% of government organizations across US and Canada and is considered as the
first choice for major banking institutions for their Intranet and Collaboration needs.
Core SharePoint Concepts :
SharePoint is build on two distinct layers –
SharePoint and .Net - The bottom layer SharePoint is built on, is the ASP.NET framework. SharePoint uses
many .Net features including Web Parts, Web Part zones and master pages, security providers, session state
managers, and user controls on ASPX pages. ASP.NET developers can view SharePoint as an extension of a
framework that they already know..
SharePoint and WSS -
The second layer build on top of .Net Framework is the layer called Windows SharePoint Services (WSS).
WSS is a foundation for the ready-to-use collaborative application capabilities that are standard in SharePoint. It
is also the foundation for custom Web-based portal and collaborative business applications.
Continued…

SharePoint and SQL - SharePoint uses SQL server to store all the Content and Configuration that it users. You can think SQL as
a back-end for SharePoint.
12 Hive - Despite of the content, SharePoint saves some of the Pages and resources on the file system (server) itself for fast
retrieval. These Pages or Files which make SharePoint Interface are arranged in a Folder structure which we call as 12 Hive. The
12 hive gets created at location "C:ProgramFilesCommonFilesWeb Server Extensions12" when you install the SharePoint sever
initially.
SharePoint 2007 – 12 hive
What is SharePoint made of? - SharePoint Portal is a made of Web applications (WebSites in .Net), Site Collections (a top level
Site of the Web application) Web Site Pages, Subsites (or child sites of Site collections),Webparts, features and more ... See the
basic definition for all SharePoint Components that you will use during development
Stsadm - It is a Command line tool exclusively for SharePoint. This is was mainly used in SharePoint 2007 for Administrative work.
PowerShell - PowerShell is a Tool used for administrative operations in SharePoint 2010 and SharePoint 2013.
ULS Logs - SharePoint has a powerful Diagnostic and Logging feature. All the activities are logged on the SharePoint server in
ULS Logs directory.

SHAREPOINT VERSIONS AND LICENSES
 SharePoint Team Services 1.0
 WSS 2.0
 SharePoint 2003
 SharePoint 2007
Versions and Editions of SharePoint 2007 :
Windows SharePoint Services (WSS) v3. This is the free/unlicensed version of SharePoint that is built
upon Windows Server 2003/2008, SQL Server 2000/2005, IIS, ASP.Net 2.0, and .NET 2.0/3.0. All you need is
a licensed copy of Windows Server 2003 or Windows Server 2008.
Microsoft Office SharePoint Server (MOSS) 2007. This is the licensed version of SharePoint that is built
upon WSS v3. It has two primary versions: MOSS 2007 Standard and MOSS 2007 Enterprise. There are a
host of other licensing options as well, such as the ability to use Microsoft Search Server 2008 or Microsoft
Search Server 2008 Express with WSS instead of MOSS.
 SharePoint 2010
Versions and Editions of SharePoint 2010 :
SharePoint Foundation 2010. This is the free/unlicensed version of SharePoint. It replaces Windows
SharePoint Services (WSS) 2007. SharePoint Foundation is built upon Windows Server 2008, SQL Server
2008, IIS and .NET 3.5. All you need is a licensed copy of Windows Server 2008. There are no other
licensing costs unless you want the full-fledged version of SQL Server.
Microsoft SharePoint Server 2010. This is the licensed version of SharePoint, offering a business
collaboration platform for the enterprise. It replaces Microsoft Office SharePoint Server (MOSS) 2007

 SharePoint 2013
Versions and Editions of SharePoint 2013
SharePoint Foundation 2013. This is the free/unlicensed version of SharePoint. SharePoint Foundation is
built upon Windows Server 2008/2012, SQL Server 2008, IIS and .NET 4.5. All you need is a licensed copy of
Windows Server 2008 or 2012. There are no other licensing costs unless you want the full-fledged version of
SQL Server.
Microsoft SharePoint Server 2013. This is the licensed version of SharePoint, offering a business
collaboration platform for the enterprise. It replaces Microsoft SharePoint Server 2010.
 SharePoint Online (Cloud SharePoint)
SharePoint Online is a cloud solution provided by Microsoft where the SharePoint server is deployed and
Managed by Microsoft.
SharePoint Online is a part of Office 365 pack.

ON SITE VS. OFFICE 365 (CLOUD) VS. HYBRID
There are three kinds of SharePoint Deployments -
SharePoint On premises - This is a Server deployment that is deployed and managed generally by a Company's IT department.
SharePoint can be Licensed from Microsoft for installation purposes.
SharePoint Online (In-Cloud) - SharePoint Online is cloud solution which is a part of Office 365 package. Office 365 is a subscription
based Cloud service deployed and maintained by Microsoft.
Office 365 currently incorporates SharePoint 2013, Exchange, Lync, SkyDrive Pro and Office Web Apps
SharePoint hybrid environment - Hybrid environments is a natural evolution of both SharePoint "On Premises" and "Online"
deployments. A typical hybrid environment might combine a standard SharePoint 2013 On Premises Intranet (containing documents that
need to remain onsite for example) with an Office 365 collaboration solution.
This type of setup can be perfect for remote teams or external partners. In this way SharePoint 2013 can offer the best of both worlds and
end users need never really know the difference.

SHAREPOINT LICENSING ON PREMISES VS. CLOUD
Note: SharePoint Online Plan 1 and Plan 2 also include Yammer
On Premise Online

SHAREPOINT 2013 FEATURES
Apps
Collaboration
Search
Content Management
Business Intelligence
Business Solutions
App Catalog & Marketplace
Work Management
External sharing
E-discovery, ACM, Compliance
PowerView
SharePoint 2013 Workflow
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●*
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
● ●

SHAREPOINT TOPOLOGY
When considering deployment options for SharePoint, you consider a topology. A SharePoint server Topology is generally
designed by various Roles that you want to add for your SharePoint.
In MOSS 2007, servers have one of three roles:
■ Application Server - This is a Server where SharePoint is installed. This server might include indexing, search, Excel
calculations, project server, and other features.
■ Web Front End (WFE) - This is an additional SharePoint server (with SharePoint bits only) that hosts all Web pages, Web
Parts, and Web services used when your server farm receives a request for processing.
■ Database Server - No SharePoint-specific software is installed (only SQL Server).
Roles aren't assigned directly to a server; instead, a server assumes a specific role in your configuration depending on what
components it has installed, the services it runs, and its location within your server farm.
Single-Server Deployment
A single server hosts all three roles (WFE, application server, and database) on a single machine. This is good for very small
deployments, given that it’s fast and easy.
The major downsides include scalability issues (because there is no room to grow except for expanding things such as
memory and processor) and availability issues (if the server goes down, SharePoint is down). From a logical perspective, all
SharePoint objects are located on this server (content sites, SSPs, Central Administration, and databases).

Two-Server Deployment
In a two-server scenario, one of the servers hosts the WFE and the application server, while the second server hosts the SQL Server
database. This provides a way to manage the database separately but adds complexity without adding scalability or availability. This step
adds a second tier to the deployment. In most organizations, this is the smallest deployment that is
recommended for anything other than a demonstration environment or very small group.
Three-Server Deployment
By adding a server, which acts as an additional WFE/application server to the two-server deployment, we gain scalability (by being able to
service more requests) and availability (by load-balancing requests so that if one server goes down, the system stays up and running on
the other machine). The single point of failure is now the SQL machine.

INTRANET VS INTERNET SITES IN SHAREPOINT
SharePoint Intranet sites
One of the main purposes of On-Premise SharePoint deployment is to create an Intranet portal site for a company. A typical company
would add Company Announcements, upload informational documents and create a company structure in an Intranet portal.
Several Team sites can be provisioned under the main SharePoint Intranet portal. Authentication and administration of an Intranet portal is
overseen by a SharePoint Administrator in a Company.
Internet or Extranet SharePoint sites
An Extranet is a web site accessible to users outside of the corporate network, allowing organizations to share information and collaborate
with external vendors, partners, suppliers and other strategic organizations in a secure and easy to use environment. The Extranet may
be a module added to the Intranet site to allow external users into only specific sub-sites of the Intranet..

DIRECTORY HIVE IN SHAREPOINT
The SharePoint Hive is a term that refers to the installation location of the SharePoint product on your server. The Hive contains
folders that hold the SharePoint binary files, site definitions, feature definitions, page layouts, ULS and upgrade logs, and
localization files.
The Hive is installed within the Common Files folder, which in nearly every Windows installation is located at C:Program
FilesCommon Files. The environment variable %CommonProgramFiles% points to the Common Files folder no matter where it
resides.
The complete path to the hives is - %CommonProgramFiles%Microsoft SharedWeb Server Extensions##
## - is the hive number.
Knowing a SharePoint hive is very important as it tells about how and where the files of SharePoint are deployed.
Each SharePoint Version has its own hive. For example, SharePoint 2007 has 12 hive (a directory named “12”) and SharePoint
2010 has 14 hive that contains all SharePoint files for that versions.
Take a look at the detailed chart of various versions and their hives below.

Version Products Full Path
60
SharePoint 2003
SharePoint Portal Server 2003
Windows SharePoint Services 2.0
%CommonProgramFiles%Microsoft SharedWeb Server
Extensions60
C:Program FilesCommon FilesMicrosoft SharedWeb Server
Extensions60
12
SharePoint 2007
Microsoft Office SharePoint Server 2007
Windows SharePoint Services 3.0
Extensions12
Extensions12
14
SharePoint 2010
SharePoint Server 2010
SharePoint Foundation 2010
Extensions14
Extensions14
15
SharePoint 2013
SharePoint Server 2013
SharePoint Foundation 2013
Extensions15
Extensions15
SharePoint 2013 also maintains a 14 hive for backwards
compatibility for SharePoint 2010 customizations

SHAREPOINT HIERARCHY
 Farm - The highest entity in a SharePoint server is a SharePoint Farm. It’s a name given to a collection of SharePoint
servers that are provisioned for a single purpose. Logically, a farm is a top space in SharePoint hierarchy where Central
administration and SharePoint is installed.
 Web Application - In IIS, a Web application is composed of an Internet Information Services (IIS) site with a unique
application pool. You can think of a Web application as a URL such as http://my.intranet.com. A SharePoint Web application
is provisioned in Central admin of a SharePoint and is added in IIS automatically.
 Site Collection - A site collection consists of a top-level site and its subsites. It is a logical unit for administration—there
are settings that can only be configured at the site collection level which are different from Web application. Each Web
application can host many site collections.
 SitesSub siteswebs - A site consists of a data repository, visual elements, administration, and almost every other
core element of the functionality and experience for the user. Visually, a site is represented as one or more Web pages, lists,
and Web parts.
 Lists - Lists are a data repository that can hold columns of data and/or documents. Visually, a list is represented by a
Web part. Its like a record keeping table with a better UI.
 Items - Items in SharePoint are actual records of data (like a data entry) or a document (word, Excel etc.) that is added to
a SharePoint List or Library.

INTRODUCTION TO SHAREPOINT CENTRAL
ADMINISTRATION AND CONFIGURATION WIZARD
Configuration wizard – It’s a wizard that you can run after the Installation of SharePoint on the server. A Central admin site is
provisioned when a SharePoint configuration wizard is run for the first time.
Central Administration – This is one of the main sites from where a SharePoint farm is Configured. This website has all the
settings to provision Web applications and site collections in a farm. All Farm level and Site collection level settings can be
change from here.
Central Administration is essentially a Web application that is auto provisioned by SharePoint. This Web application also has its
Content database stored in SQL like all others.

INTRODUCTION TO TOOLS USED TO CUSTOMIZE
SHAREPOINT
• SharePoint Designer
• Infopath
• Front page

WEB & APPLICATION SERVERS | SINGLE SERVER FARMS
64-bit, four cores 64-bit, four cores
4 GB for developer or evaluation use
8 GB for production use in a single
server or multiple server farm
4 GB for developer or evaluation use
8 GB for production use in a single
server or multiple server farm
80 GB for system drive
Maintain twice as much free space as you
have RAM for production environments.
Maintain twice as much free space as you
have RAM for production environments.

DATABASE SERVERS | MINIMUM HARDWARE
REQUIREMENTS
64-bit, four cores for small
deployments
64-bit, eight cores for medium
Deployments
64-bit, four cores for small
deployments
64-bit, eight cores for medium
Deployments
8 GB for small deployments
16 GB for medium deployments
8 GB for small deployments
16 GB for medium deployments
Hard disk space is dependent on the size
of your SharePoint content
Hard disk space is dependent on the size
of your SharePoint content

SOFTWARE REQUIREMENTS
Dependencies and prerequisites

SOFTWARE REQUIREMENTS
HardwareandsoftwarerequirementsforSharePointServer2013 http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx)

WE ARE HERE TO
HELP.
Questions?

Core SharePoint 2013 Concepts

More Related Content

What's hot

Similar to Core SharePoint 2013 Concepts

More from Learning SharePoint

Recently uploaded

Core SharePoint 2013 Concepts