Skip to main content

SharePoint 2013 - Create a Web Application and Site Collection in SharePoint 2013


Creating our first SharePoint 2013 Web Application

Let’s begin by navigating to the SharePoint 2013 Central Administration > Application Management page.



You will notice that the UI is fairly similar to that we have been accustomed to in SharePoint 2010.



The first thing we need to do is create our first Web Application to host our Site Collections and its sub sites.

Under the heading “Web Applications” click on Manage web applications.



Click on New

The below splash screen is unexpected from Microsoft, but it is notifying us in a somewhat candid way that the page is about to load.  I wonder if this will be deprecated in the final release of SharePoint 2013.



You will finally be greeted with the all familiar “Create New Web Application” modal dialog window with a few subtle additions.  I will post separate screen captures depicting our settings as we scroll down the modal dialog box presented and will explain each of these settings in some detail.





 



We will click on Register new managed account.  We will not be utilizing the sp_farm account and register our sp_webapp domain account that we created earlier.



Click OK

Unfortunately, after clicking OK, our previous entries made are erased (same behaviour in SharePoint 2010), so you will need to begin from the top again)

Ensure you have selected the sp_webapp account as your Application Pool ID.

Ensure your Database Name and Authentication method is correct.



 



IIS Web Site:

Create a new IIS web site

Name: SharePoint – intranet.corp.gkhalil.com (Always best practice to create a new IIS website for each new SharePoint Web Application.)

Port: 80

Host Header: Leave Blank or specify a preferred host header. (If you specify a host header, the alternate access mapping will be created for you automatically.  Please ensure that you also create the relevant A record in DNS. e.g. intranet.dev.com which we have done above.

Path: Leave default C:\inetpub\wwwroot\wss\VirtualDirectories\80 (This is usually determined by Port number and or Host Header Input)

 

Security Configuration

Allow Anonymous: No

Use Secure Sockets Layer (SSL): No

Claim Authentication Types

Enable Windows Authentication: Integrated Windows authentication (NTLM)

Sign in Page URL

Default Sign In Page – selected

Public URL: e.g. http://intranet.Dev.com:80

Zone: Default

Application Pool

Create new Application pool: SharePoint -intranet.corp.gkhalil.com80

Configurable: CORP\sp_webapp (register the newly created service account as a managed account)

Database Name and Authentication

Specify your Database Server, Database Name and keep Windows authentication selected which is recommended.

Failover Server

This was first introduced in SharePoint 2010 providing you with the ability to specify a second SQL server that is participating in database mirroring, allowing you to easily failover if the primary SQL server fails. This was and still is a welcome addition providing a means of high availability.

Service Application Connections:

Edit the following group of connections: default

Note, SharePoint 2013 as was the case in SharePoint 2010 allows you to connect a web application to all service applications available in a farm or a subset that you define.  This can be changed at any time.

Customer Experience Improvement Program

Enable Customer Experience Improvement Program: Yes or No

Click OK

 



 



Click OK

Our newly created Web Application will now be listed along side our SharePoint Central Administration Web Application under Central Administration > Application Management > Manage web applications



 Creating our first SharePoint 2013 Site Collection

We are now ready to create our first site collection.  Navigate to Central Administration > Application Management > Create Site Collections

Ensure that the newly create Web Application is selected.

Enter a Title for your Site.



Select your Template.  You will notice that there is a 2013 and 2010 Template experience version on offer.  I am selecting 2013 and the all so common Team Site.

Enter your primary and secondary site collection administrators

Then Click OK



 

Our first site collection is up and running and as you can see from above, the procedure in doing so is identical to that in SharePoint 2010.



Click OK.

 

Comments

Popular posts from this blog

Accordion "Left Navigation" (Quick Launch) for SharePoint 2013

For Expand/collapse "Left Navigation (Quick Launch) for sharepoint 2013 Copy the below code and paste in Master page jQuery(document).ready(function () {  /*set dynamic css logic*/  if($('#sideNavBox .menu-item.selected').length){   //propagates the selected class, up the three.   $('li.static').removeClass('selected');   $('#sideNavBox .menu-item.selected').parents('li.static').addClass('selected');   //collapses top siblings of selected branch   $('#sideNavBox .menu-item.selected').parents('li.static').last().siblings()    .find('> ul').hide();  }  else $('#sideNavBox .root.static > li.static > ul').hide();  /*set accordion effect*/  $('#sideNavBox .root.static > li.static').each(function(){   if($(this).find('ul').length){    $(this).addClass('father').click(function(){     if($(this).children('ul').css('display')...

Modifying the second level navigation arrow image

Open your master page. Switch to Code View. Search for "TopNavigationMenu". This should take you to the global navigation (top nav) instance of AspMenu. Using Intellisense in the code view, or using the Properties pane, add the following property to the AspMenu tag: DynamicPopOutImageUrl="insert image URL/path here"So your code should look like: Runat="server" DataSourceID="topSiteMap" DynamicPopOutImageUrl="/images/myimage.gif" >