Join Ron Davis for an in-depth discussion in this video Creating a web application and a collection, part of SharePoint 2013 Site and Collection Administration.
- View Offline
- We're going to create a web application and a site collection, and what you want to see here is, I'm up here right now I'm running in Central Administration, and if you'll look in here in the URL you'll see it says myserver, which is the name of my server, and then a colon, and it's running on port 45688. If I go to Lynda's Home Team, which is a site collection that we created then you'll see it's running, and it doesn't have any ports in there.
As a matter of fact, if I trim that on back, and just hit the enter key it's going to come right back immediately without the port. That means it's running on the default port, which is 80, now that's important here, we'll show you in just a second. I moved over to Central Administration, and if I go into Application Management, by the way, ignore this little yellow bar, SharePoint's constantly checking itself, and it's normal in SharePoint to have some kind of a minor issue, so the yellow bars we pretty much ignore.
There's always something going on in SharePoint. If you have a red bar don't ignore that one. We go into Application Management, Manage web applications, and there's SharePoint 80 which we just looked at, which is Lynda's home site. The other application we have is Central Administration running on 45688, so let's go through and create a new web application. I'm going to just click New, and I get my popup to fill out this information sheet.
We're going to Create a new IIS web site, and it'll by default it'll just pick a Port number for us, and if we want to change that, let's say I'm going to change that to 35000, so if you have a certain Port you want to use then you can just change it right in here, and here's the Path, pretty much self-explanatory. For my app for access security, Allow Anonymous or not, and I'm not going to allow Anonymous access to this site, and whether or not I wanted to use SSL, which would be https Yes or No.
I'm going to use Windows Authentication Integrated, because I am on a domain, and if I come down there there's my URL. The Default Zone that's that stuff in Internet Explorer, so it's going to put it into Default Zone. Down here I'm going to Create a new application pool, and it's going to name it by default after the name of the web application that I created which is SharePoint 35000. I'm going to have the account run under the existing MYCORP Administrator, and Database Server is going to be the standard server, and here's the name of the Database.
It would create the content collection Database. I don't like this assigned number in here, because I believe it is easier for Database maintenance to give it some kind of a descriptive name so that we can quickly look in using the Database Tool SQL Server Management Studio, go in and look at these databases and know which database we're working with. We'll use Windows authentication, correct. Here's the different Service Applications that we have, the different things that we can do.
This is going to by default bring in what we set up initially. If we want something other than that we would go into Custom and just go through and put checkmarks next to whatever it is you wanted to do. We're going to just go with the default, and I don't care about the Customer Experience Improvement Program for this little demonstration site, and we'll say OK, and we'll let the Web Application create.
Now close. I'm going to refresh the display here, and now there's my new site. If I come in, now here's the URL to the site. Let's take a look at that, I'm going to copy it. I'm going to open a New Tab, I'll paste it in here, and we'll put the slash in, and I'm going to hit enter. Okay, if you'll noticed there she is, and it returned The webpage cannot be found. The reason is there is no webpage.
We have a web application, we do not have a website, important concept. Let's go back over here, and get this running. Now, let's go back to Central Administration, and in Central Administration we're going to Create a site collection. Now, see the Web Application's by default selected. If it's not selected, which is not exceptional, then you just go in here and Select the Web Application, and we're going to select, we're already selected, and we're okay here, so you'd select the correct Web Application.
Let's give this a name, First Site Collection. Down here the URL you'll notice is set on root which is correct that's the /, the root. If I pulled this down I could change it over to sites, but we're creating the / collection. The experience 2010 or 2013, whichever one you're trying to set your feature level for. Here's your templates, your templates this selection in here is going to look different if you're on Foundation, SharePoint, or if you're on Enterprise.
We are on Enterprise, and you see we have all these other really cool different templates we can use, but we'll stick with collection down here, and let's create a Blog because we already have a Team Site. Down here for a User name for my Primary Site Collection Administrator, so what I'm going to enter down here is sa1, which is a user that I created in Active Directory, and verify it. I've got the underscore, by the way if you want to find it you click this, and then you go into Active Directory, and say what you want to look for sa1, and down here search.
It's a little bit of a different interface, if you're used to working with Active Directory Users and Computers. There I found it, and I'll cancel out of that because we already know it found it, it placed the underscore. Now, I'm not going to create a Secondary Administrator down here, though I would suggest you always have a Secondary Administrator, and this is also where you set your Quota with the subject of another video. We should be okay and we'll click OK. If we didn't make any errors it will go into the process.
Now, once it went into Working on it that meant our input sheet that we just created down there did not have any errors in it. Otherwise, it would of came back in, and showed us something that we had done incorrectly. Say I had entered a user and I didn't verify it by clicking on the little icon, and the user didn't exist then it would just come back and give me a little red information, and would say no such user found or something like that, some kind of an error. Okay, created the site now this you don't have to do, but what I like to do is I'm going to select the site in here, and I want to have it open, so I'm going to right click it, and I'm going to tell it to Open in a new tab.
Frankly, in the 2013 release this almost always works. In previous iterations of SharePoint it would come through and tell you that the site was created successfully. However, it didn't actually instantiate the site, so we would always go in and start it just to make sure that it really worked. By the way, if you ever come through, and I'll look our site should be up. There's my Welcome to my blog! First Site Collection. If you ever do this, and when you go over to the site it will not come up for some reason, if it's a top level site or whatever I would suggest you just go back through, and delete everything.
Go into Application Management and just delete it, delete out the Content Database, assuming it's the only site in the Content Database, and just start again life will be easier that way. We've created the site, and let's go back over to Central Administration, and let's create another one. We're going to create another site collection. It's still on my server and down here if I pull down this list here, now I cannot get back to root, because that root's already taken, so we're going to call this My Second Site, really should be Collection.
There's My Second Site Collection, and I'm going to copy that, and paste it down here, and I'm going to get rid of the white space because I don't like white space, delete, okay that looks good. Let's do this one as a Community Site. Again, I'm going to need to put in a user name, and again we'll go with sa1, and let's just show you this. Let's put in sa3, there is no such account, so if I say OK, see here's that error that I'm telling you, so if you make some kind of a configuration mistake it will come through and help you.
Now OK, so it liked the input sheet, and it's going to create the second site collection. Now remember we're creating a separate site collection, but it is still in the same content database that we created when we created the application, so that one content database is now holding the content from two site collections. Again, I'll right click and I'll Open in new tab, and we'll let this come up.
Okay, and the site's up. Here's my second site collection in here based on the template that we selected. Now, it's important that when you're creating these that you make sure that you provision your SharePoint correctly, that is the correct amount of site collections and sites etcetera. To help you, you'll want to go in and search for SharePoint 2013, Software boundaries and limits, which I have right here, and we'll see if we can get this to open.
Okay, in this if you just scroll down through it, it will give you your different limits. Here's Limits by hierarchy, and here's for example, your Content database, and if you come in and look at the Content databases, per farm, the size of it, Content database, different usage scenarios. This will give you guidelines as far as what to create where, and if you don't exceed your guidelines, and you have proper hardware, you're going to get excellent performance out of SharePoint.
Let's real quick pop back over to Central Administration, and let's go into Central Administration, and again we go down here and we go Application Management, and if we Manage web applications there's our three web applications. Down here in this Site Collections we can Create a site collection, and if I go delete, I would come here, and if I wanted to delete a Site Collection, Change Site Collection's in here, and I would come through, and you see the Web Application is picked up in here, and I can pick that which is /, or there's my second site collection, and I could go through and I could delete these site collections without deleting my web application.
I'll cancel out of it, and that's how you would do that.
- Navigating the SharePoint architecture
- Handling blocked files and locks
- Working with quotas
- Backing up and restoring the content database
- Creating and modifying site libraries and lists
- Adding site pages and Web Parts
- Branding your SharePoint site with Design Manager