Duration: 17:09 min
Summary: his video continues the Sharepoint 2010 Web Development course. In this video we are going to see an introduction of the Sharepoint 2010 platform. First the Sharepoint Central Administration web site is shown and a new Team Site is created in order to explain how the user interacts with a site hosted in Sharepoint. Then we focus on the components of this platform by demonstrating how the IIS Web Server store the Sharepoint sites. Finally, we briefly show the databases used by Sharepoint and IIS to store the data in a SQL Server Express instance.
Technology used: Windows 7, Sharepoint, SQL Server, IIS
Examples: The video shows the main components of the Sharepoint 2010 platofmr
Keywords: Sharepoint, Web, Development, IIS, SQL Server, Team Site, Site collection
Hello everybody. My name is Mauro Picchiliani and in this session we will
continue the SharePoint 2010 Web Development Course. We will talk about
introduction to the SharePoint 2010 platform in this video. Which we are
going to study the administration tools and also see an overview of the
So, since I have already installed SharePoint 2010 on this windows server
2008, let me show you that we have some icons in the menu. In this case we
have SharePoint 2010 Central Administration, which I am going to open. We
can see that the browser is open and we are asking it about out looking so
that we can start administering [inaudible 00:00:57] SharePoint 2010. So I
am going to use the Administrator login, which is the login that I used
during the installation of SharePoint. Let me insert the password and now I
am in the Central Administration webpage of SharePoint 2010.
All of the SharePoint features hunt in the browser so all you are going to
have to do is work with the tools that are already provided, however, the
final users won't see the Central Administration. Most probably they are
going to use a website created in SharePoint. This website can have many
names such as [inaudible 00:01:43] Document Collections and others, but we
as web developers must know this Central Administration.
What I am going to do over here is create a new tab, to show you that
although the Central Administration was created automatically during the
installation process, we also have a website created in the default address
of the server. So we are going to copy this address, paste it over here and
show to you that in the default 80 part of the E.S. we have a site created
from SharePoint. This site we are going to see over here, has the address
redirected from the V-Class, which is the name of the server. So, in fact,
press "Enter" here, again I have to provide a user.
Now we have this site. This is the default site created by SharePoint
during the installation. This is what the users will be working on. In the
case you have a site that is called a [inaudible 00:02:57] site because it
is created from this template. We can see that we have several features
over here such as calendars, we can go back with this navigation button
over here, we can have the tasks, which are features that allow the users
to work on this type of site. There are many options to work with these
features. We have several links that allow us to work with these [inaudible
00:03:28] for instance, I am here on the tasks like this item and I can
create a new task. We can see that the Silverlight interface assumes so all
of these controls were created and provided by the Silverlight
So, I am not going into further details with this interface, because there
are many options that are useful for the users of the SharePoint website. I
am going to close this window over here and go back to Central
Administration. Now we are going to talk a little bit about how to manage
these websites as a platform. We have many concepts, many terminologies
from SharePoint and on this video we are just going to focus on a platform.
By creating a new website we can see that this website was created
automatically and I will create a new one from the [inaudible 00:04:29]
template, which is the most useful and used template in SharePoint. What I
am going to do is click this link, Application Manager and in this site,
Collections. Which is the name Microsoft uses for sites in SharePoint. I
will show view outside Collections. Here we can see that we have just one
that was created automatically. I am going to go back over here and click
on "Create Site Collections."
Well, we can see that this is a simple page where we have to fill in some
fields to create a new site collection. And I am going to use the most used
template, which is [inaudible 00:05:09]. Note that we can create documents,
workspace, blogs and other template sites. Since this is just an overview
of the platform, I will create a new [team] site website over here and we
will name this team site "My First Team Site." I will not enter a
description and I will change the URL.
We can see that the V-Class is the base and I have this suggestion.
My/personal that we are going to change sites and specify as "My First Team
Site." Here I have several options to choose from, in the case of the
templates and other options. I am just going to leave the default values
and provide the administrator user name for the primary site Collection
Administrator and also for the secular site Collection Administrator.
Right now I am not really interested in all of the details of the security,
I am just creating a new team site for the demonstration of the platform.
Okay. So now I create the team site, SharePoint is copying all of the
necessary files, creating a database, inserting data, it takes the inner
workings outside of our scope. So I have the message that the site was
created, let me click over here and see in a new tab, the new site that was
created. You can see that it is exactly the same as the default site. If we
go back we can see over here, that this is the default site created by the
installation and this is "My First Team Site."
The main difference in this case is the URL address. We can see that they
are different because they created a new team site; however, they have the
same features , calendar, tasks, shared documents and other aspects. Now
that we already created team sites from the template, let us take a look
from the web developer perspective. All of these pages are created
automatically by SharePoint and as a Microsoft product it uses all of the
necessary infrastructure for hosting webpages, which is in this case rely
on the web server called IIS; Internet Information Services.
Since we already installed SharePoint and we have all of the pre-
requirements competed we can see that the SharePoint is using ES and other
aspects. So let us take a look at this code that is behind all of this
pretty interface, we can see that we have not had to program anything so
far but we have several features and some interesting ones.
For instance, let me take a look in the tasks as I already showed you
before and then we created a new item. Here we can see that we have this
gorgeous ribbon with icons, we have several options for simplification of
the user. Also, the user can change the content of the page as he likes if
he has the properties.
So, we have several options here. For instance, we have site options, site
actions, this is a very important menu and we can see on the options "View
Outside Content" all of the features that this team sites has in this case;
docs, announcements, calendar, links, tasks, shared documents and others.
We can also change that over here, but let me go back and show you that if
you want to customize the full webpage for the team site template, we have
the option of site actions, add page. Of course, the user has to have
permissions for that but since I am running as an Administrator I do not
have problems with that.
We can see that the ribbon changed and now we have content to edit all of
the visual aspects of this page. We do not have to understand HML so far,
because this feature is user oriented, not developer oriented. So all the
user has to do is work on the layout as if he or she is working on a Word
document. We have these options, they are very similar to the ribbon of the
Word. We also have options to insert more complex elements, but the user
has the ability to work in this layout as he pleases.
So let me go back over here to the "First Team Site" icon so that the
editing of the page and show you a little bit more about the behind
mechanics of all of this. As I said before, we are using IIS, let me show
you the IIS Manager, and how it represents the options. Oops, I chose the
wrong IIS Manager, let me go back and choose the correct one. Here is the
correct one for IIS 7. We can see that we have the server and on this
interface we have several options to change the configurations settings for
the entire server and now for the site.
When we click this Site icon over here, we can see the application called
'Sites' over here that are hosted in this server. What is interesting for
us is that the [inaudible 00:11:13] website we can see that we have the
application on this website stopped. But we have another one called
SharePoint-80 which is started on the 80 port. You can see that this is the
default http part that contains the site that was created for the
installation. Also we have the Central Administration. You must notice that
we are using a different TCP part, in this case 28858, for the
administration and this is the folder where the files are stored. Let me go
back and expand the sites and expand the Central Administrator to show you
that we have several folders and several options over here. On our sites
they are started on the 80 port. so we can go back over here and check them
out. We can see that we have many properties for this website such as .net
options, IAS options and others. This is the structure that SharePoint uses
in IIS to organize the sites.
Just for curiosity let us take a look at the folder. We can see that if we
open Windows Explorer over here and show you that in the C, drive we have a
folder called INet Pub, let me check, INet Pub, www root, which is the web
folder over here and inside www root we have WSS, let me show you, and then
virtual directories. In this case, on the 80 port, we can see the files
over here, we can see this ASAX file which is a very important file, and
orders. Although we do not change directly these pages over here, these are
where they are stored. Of course they are handled directly by SharePoint,
but it is important to understand where they are located and how they are
Another important aspect of SharePoint as a platform and as a developer, is
the data storage management that is used. Since it is a Microsoft product
it uses the Microsoft SQL Server Database. Although we did not see any
icons here that resemble the SQL Server, only this folder with these two
options, we can see that SharePoint does use SQL Server by checking the
services that were running on this computer. We can see that we have
several .net services, and we can see that we also have several SharePoint
services. But for now we are concerned about the SQL Server. We have the
SQL Server over here, it is an express version of SQL Server and we can see
that it has a name called SharePoint. We cannot manage the database over
here because we do not have any administrative tools, such as, management
tools, however, we have options to manage the database from the SharePoint
Central Administrator if we go with this option "Manage Content Database"
we can see that we have several options for monitoring, back up, restore
Let me show you as a developer, how we can access this database using a
command line tool. Let me open a console over here and rely on the old SQL
to specify the -S parameter to specify the name of the server which is V-
Class/SharePoint. Since we are using a name of the SQL Server Express we
can also specify the [inaudible 00:15:38] E Key to indicate that we are
connecting to the server using the Administrator User, which is the user
that I am currently logging in. We are now connected to SQL Server.
There are several databases we can send this simple select over here, just
to check them out using the [inaudible 00:16:00] database stable and the
"go" command. The "go" command does not have the semicolon. Let us go
again. Now we can see that we have several databases. Although here are the
system databases, we have several databases for SharePoint and we usually
do not work directly with them, although we have to be aware that they are
used and they are stored. So with this we finish this overview of the
SharePoint 2010 platform using this developer perspective. It is important
to know that we are creating websites directly from the templates of
SharePoint. We have all of the IIS infrastructure behind it and also the
SQL Server Express to store all of the necessary data. So this is it. I
hope to see you in the next video of this course. Goodbye.