Hello, and welcome to this video. My name is James Olorunosebi, and I will be your guide for this video tutorial. Today we will be looking at Understanding Site Collections, and this is the very first part. So, what we have here now is what we call the logical architecture for sites in SharePoint 2013 and other SharePoint flavors. When we say logical, what we actually mean is how the computer, or how the system sees its objects. How does the system perceive all its content? It’s called logical. It is logical because it is internalized, it is not physical. You can’t see it, but the system works in that model. It is real to the system. We have to be able to think lie the system so that we can be able to work together. In the SharePoint logical architecture for building sites, and site collections, and web applications, what you would usually have, as you can see here is that you would have a top level site. This is another top level site. This is the MySite. And this is another top level site. This is MySite, this is Communities, and this is Team. Now that does not mean that you would find this exactly as it is, in SharePoint. It can be anything. This is just to let you know how you can categorize your various SharePoint site collections, under a particular web application. Now this web application is dedicated to MySites. MySites contains all the individual users in your organization, their personal sites where all their documents are stored, their emails (possible with some additional configurations), you can port their email messages to be stored in their MySite. Everything that happens in their user profile, the default save location can be their MySite location in SharePoint.
MCSE Training – Resources (Intense)
For Communities, this is a web application you can create for communities, for collaborations, for forums, where several people come together to pool information, to pool knowledge together. And you can have team sites where members of a particular team working together towards a common goal. It could be the finance team, where everything they do will have to do with finance for the organization. It could be the marketing team, where everything they do in there would have to do with marketing. Only marketing team members, or finance team members, depending on the team that they are. It is possible to have communities that cut across the different departments of the organization, for example you could have a community for finance team, a community for marketing, and you could still have a community for the sales team, and you could have community even for management team members, where management at different cadre can come in and collaborate. The same can also apply for team sites.
If you take the Communities web application for example, you would have under this web application, to be hosting what we would call the top level site. This is what we call an hierarchy or a structure. There will be top level sites, and there would be sub-sites, and there would be sub-sites under further sub-sites. In here for example, this is a top level site, and all this individual sites are underneath. If we were to take that this community belongs to the Sales team. Then in the Sales team, this could be the Sales Team Headquarter, perhaps they are structured across different geographical regions. We could have those in point A, B, C all the way to F, where these alphabets could represent their locations, the states in which they are operating, or their catchment zones. Even within a particular zone we could have it further sub-divided into another classification. And it can go on and on and on, just like what you have in folder structures. So this is what we call the logical architecture for site collections.
So now, all of this could be sitting, everything that we have here, can actually be one single farm. And this farm could possibly be our intranet farm. So what would you do if you are going to have solutions in your organization that is facing the public, that is internet facing, what do you do in this scenario? What you should do is have another farm. So how are you going to have another SharePoint farm? It means to setup an entire farm just as you setup this current SharePoint. You have to setup another one that is going to contain the solutions that is going to be facing the internet. This is the recommended best practice. But there are people who don’t want to do that. There are people who want to cut cost, who want to find alternative, so what they do is to create another web application. In that web application they create the sites and sub-sites that they need and they make that to face the internet. Not the best option but what they usually do is to deploy SSL (Secure Socket Layer) certificate from VeriSign, or Thawte, or DigiCert, or Comodo, or GoDaddy, or any of this internet certificates to secure such web application and the fact that it is facing the internet.
So before you start creating even your very first site in your organization, what you should do is look at your organization and study it, what is the organizational structure like, what is the scale, how big is it really? And you take that organizational structure, you put it to paper, and draw out your SharePoint based on the divisional or team. To do this it is important to consult with the relevant governance team and the relevant authorities within your environment to know how they want their sites to be structured. But basically, you should always plan your site by the organizational hierarchy. Create divisions at the top level sites, create sub-divisions, create departments, create units. And when all of that has been done, you need to have another, what we call a Rollup site where all the information that cut across the various divisions can be easily found. It will often contain sites that are related to the entire overall organizational informational architecture. And you ensure that the rollup site is mapped according to the structure that you have for your divisions.
Thank you for watching this video. In the next part we are going to use PowerShell command lines to create the necessary structures for the site collections.