Learn SharePoint In Series - Part Two - Web Application

This article is the second part of Learn SharePoint in Series. You can read the first part here Learn SharePoint In Series-Part One-Introduction. In previous article I have described about the introduction of SharePoint and some basics of SharePoint such as history, choosing between SharePoint and Other technology. So in this article I am moving one more step ahead.

Introduction

This article is the second part of SharePoint series. You can read the first part here at Learn SharePoint In Series-Part One-Introduction. In the previous article, I have described the introduction of SharePoint and some basics of SharePoint such as history, choosing between SharePoint and other technology. So, in this article, I am moving one more step ahead.

In this article, I am going to cover the following topics.

  • Background of SharePoint
  • SharePoint Web Application in Terms of SharePoint on Premises Server
  • SharePoint Web Application in Terms of SharePoint Online
  • Creating Web Application

Background of SharePoint

SharePoint is based on the .NET Framework. SharePoint requires Windows Server Operating System. SharePoint uses SQL Server Database to maintain the contents. In SharePoint terminology, the SQL Server Database is called as Content Database. The users and groups in SharePoint are managed in Active Directory.

SharePoint Web Application in Terms of SharePoint on Premises Server

We know that every .NET web-based applications need an IIS Server for hosting. We create an Application Pool and a Website in IIS to host the .NET Framework web application. In a similar way, when we create a SharePoint Web Application, SharePoint creates an application pool and IIS websites and hosts precompiled website in that IIS under created IIS site. SharePoint Web Application is the entry point for SharePoint.

In single SharePoint Server, we can have only one SharePoint Web Application without port number in the URL (Default port i.e. 80). Example: We can create only one SharePoint Web Application with http(s)://domain. When we create another Web Application it creates with URL such as http(s)://domain:port (5555). However, we can extend SharePoint Web Application to support multiple Web Application on the Port 80.

As per Microsoft Limits and Boundaries description we can have 20 Web Applications per SharePoint Server. However, this is not the hard limit. This is Microsoft Supported limits. We can create more Web Applications but that will affect the performance of the SharePoint if SharePoint Server is not capable of handling the bigger loads.

If we talk in terms of Content Database, then a single SharePoint Web Application can have maximum 500 Content Database. In a case when you have large data, let’s say more than 1000 GB, Microsoft doesn’t recommend you to store all the data in single Content Database. Microsoft recommends 200 GB of contents per content database. So we can divide the contents into various content databases. So in other words, we can say that single Web Application can have more than 1 content database.

As I have specified earlier in this article, Web Application is the starting point to the SharePoint. So there must be some security to the contents. In order to make contents secure, SharePoint provides a very powerful mechanism of security in terms of Authentication and Authorization. For authentication, SharePoint provides various ways to protect the entry to SharePoint. It provides multiple types of Authentication mechanism such as Windows Authentication, Claim Based Authentication, Form-Based Authentications and many more. In other words, you can even enter the SharePoint using your Google, Facebook, LinkedIn etc. If you want to build a public facing website then, in that case, SharePoint also provides Anonymous Authentication in which user can enter into SharePoint without login.

SharePoint Web Application in terms of SharePoint Online

As we all know that SharePoint Online is a cloud-based platform. SharePoint Online only supports Intranet based web application. In SharePoint Online we cannot access without login. When we configure SharePoint Online from Office365 we get a tenant. A single tenant act same as like single Web Application in SharePoint on-premises. The URL of SharePoint Online is always like https://tenantname.sharepoint.com. If you want another Web Application then, in that case, you will need to set up another tenant. In order to access the SharePoint Online, we need to log in. The username to login into SharePoint Online will be like username@tenantname.onmicrosoft.com. Later on, you can remove the onmicrosoft domain and add your custom domain to the user.

Creating Web Application

Creating Web Application in SharePoint on-premises: In order to create Web Application in SharePoint on-premises, we can make use of Central Administration and create and configure new Web Application. For more information about creating SharePoint Web Application, you can refer to the following links.

Creating Web Application in SharePoint Online: In SharePoint Online, in order to create a Web Application, you have to subscribe to Office 365. Detailed steps for creating SharePoint Online Web Application are given below.

Conclusion

Here in this article, I tried to explain the basics of SharePoint Web Application in terms of SharePoint on-premises and SharePoint Online. If you are a SharePoint developer or SharePoint administrator and if think that any of the information provided above is incorrect or misleading then please let me know in the comment section. In my next article, I will be explaining Site Collection and Sites in details in the context of SharePoint Online and SharePoint on Premises.

 My other articles in this series are,