Introduction
Here I will explain about uses of 3-Tier architecture and how to create or implement 3-tier architecture for our project in asp.net
Description
1. What is the use of 3-tier architecture and why we go for that architecture?
2. First we need to know what 3-Tier architecture is.
3. How to create 3-Tier architecture for our project?
Uses of 3-Tier Architecture
1. To make application more understandable.
2. Easy to maintain, easy to modify application and we can maintain good look of architecture.
3. If we use this 3-Tier application we can maintain our application in consistency manner.
Basically 3-Tier architecture contains 3 layers
1. Application Layer or Presentation Layer
2. Business Access Layer(BAL) or Business Logic Layer(BLL)
3. Data Access Layer(DAL)
Here I will explain each layer with simple example that is User Registration
Application Layer or Presentation Layer
Presentation layer contains UI part of our application i.e., our aspx pages or input is taken from the user. This layer mainly used for design purpose and get or set the data back and forth. Here I have designed my registration aspx page like this
This is Presentation Layer for our project Design your page like this and double click on button save now in code behind we need to write statements to insert data into database this entire process related to Business Logic Layer and Data Access Layer.
Now we will discuss about Business Access Layer or Business Logic Layer
Business Access Layer (BAL) or Business Logic Layer (BLL)
This layer contains our business logic, calculations related with the data like insert data, retrieve data and validating the data. This acts as a interface between Application layer and Data Access Layer
Now I will explain this business logic layer with my sample
I have already finished form design (Application Layer) now I need to insert user details into database if user click on button save. Here user entering details regarding Username, password, Firstname, Lastname, Email, phone no, Location. I need to insert all these 7 parameters to database. Here we are placing all of our database actions into data access layer (DAL) in this case we need to pass all these 7 parameters to data access layers.
In this situation we will write one function and we will pass these 7 parameters to function like this
String Username= InserDetails (string Username, string Password, string Email, string Firstname, string Lastname, string phnno, string Location)
If we need this functionality in another button click there also we need to declare the parameters likestring Username, string Password like this rite. If we place all these parameters into one place and use these parameters to pass values from application layer to data access layer by using single object to whenever we require how much coding will reduce think about it for this reason we will create entity layer or property layer this layer comes under sub of group of our Business Logic layer
Don’t get confuse just follow my instructions enough
How we have to create entity layer it is very simple
Right click on your project web application—> select add new item —-> select class file in wizard —>give name as BEL.CS because here I am using this name click ok
Open the BEL.CS class file declare the parameters like this in entity layer
Don’t worry about code it’s very simple for looking it’s very big nothing is there just parameters declaration that’s all check I have declared whatever the parameters I need to pass to data access layer I have declared those parameters only
BEL.CS
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
namespace WebApplication3
{
public class BEL
{
#region variables
private string _UserName;
private string _Password;
private string _conPassword;
private string _FirstName;
private string _LastName;
private string _Email;
private string _Phoneno;
private string _Location;
private string _Created_By;
#endregion
public string UserName
{
get
{
return _UserName;
}
set
{
_UserName = value;
}
}
public string Password
{
get
{
return _Password;
}
set
{
_Password = value;
}
}
public string conPassword
{
get
{
return _conPassword;
}
set
{
_conPassword = value;
}
}
public string FirstName
{
get
{
return _FirstName;
}
set
{
_FirstName = value;
}
}
public string LastName
{
get
{
return _LastName;
}
set
{
_LastName = value;
}
}
public string Email
{
get
{
return _Email;
}
set
{
_Email = value;
}
}
public string Phoneno
{
get
{
return _Phoneno;
}
set
{
_Phoneno = value;
}
}
public string Location
{
get
{
return _Location;
}
set
{
_Location = value;
}
}
public string Created_By
{
get
{
return _Created_By;
}
set
{
_Created_By = value;
}
}
}
}
Our parameters declaration is finished now I need to create Business logic layer how I have create it follow same process for add one class file now give name called BLL.CS. Here one point don’t forget this layer will act as only mediator between application layer and data access layer based on this assume what this layer contains. Now I am writing the followingBLL.CS(Business Logic layer)
BLL.CS
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
namespace WebApplication3
{
public class BLL
{
#region insertuserinformationdetails
public void InsertUserDetails(BEL objUserDetails)
{
DAL objUserDAL = new DAL();
try
{
objUserDAL.InsertUserInformation(objUserDetails);
}
catch (Exception ex)
{
throw ex;
}
finally
{
objUserDAL = null;
}
}
#endregion
}
}
and how this method comes
return objUserDAL.InsertUserInformation(objUserDetails);
Here BEL objUserDetails means we already created one class file called BEL.CS with some parameters have you got it now I am passing all these parameters to Data access Layer by simply create one object for our BEL class file
What is about these statements I will explain about it in data access layer
DAL objUserDAL = new DAL();
return objUserDAL.InsertUserInformation(objUserDetails);
this DAL related our Data access layer. Check below information to know about that function and Data access layer
Data Access Layer(DAL)
Data Access Layer contains methods to connect with database and to perform insert,update,delete,get data from database based on our input data
I think it’s to much data now directly I will enter into DAL
Create one more class file like same as above process and give name as DAL.CS
Write the following code in DAL class file
DAL.CS
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Data;
using System.Data.SqlClient;
using System.Configuration;
namespace WebApplication3
{
public class DAL
{
//SQL Connection string
string ConnectionString =
ConfigurationManager.ConnectionStrings["ApplicationServices"].ToString();
#region Insert User Details
public void InsertUserInformation(BEL objBELUserDetails)
{
SqlConnection con = new SqlConnection(ConnectionString);
con.Open();
SqlCommand cmd = new SqlCommand("sp_userinformation", con);
cmd.CommandType = CommandType.StoredProcedure;
try
{
cmd.Parameters.AddWithValue("@UserName", objBELUserDetails.UserName);
cmd.Parameters.AddWithValue("@Password", objBELUserDetails.Password);
cmd.Parameters.AddWithValue("@conPassword", objBELUserDetails.conPassword);
cmd.Parameters.AddWithValue("@FirstName", objBELUserDetails.FirstName);
cmd.Parameters.AddWithValue("@LastName", objBELUserDetails.LastName);
cmd.Parameters.AddWithValue("@Email", objBELUserDetails.Email);
cmd.Parameters.AddWithValue("@PhoneNo", objBELUserDetails.Phoneno);
cmd.Parameters.AddWithValue("@Location", objBELUserDetails.Location);
cmd.Parameters.AddWithValue("@createdby", objBELUserDetails.Created_By);
cmd.ExecuteNonQuery();
con.Close();
}
catch (Exception ex)
{
throw ex;
}
finally
{
cmd.Dispose();
con.Close();
con.Dispose();
}
}
#endregion
}
}
Here if you observe above functionality I am getting all the parameters by simply creating BELobjBELUserDetails. If we create one entity file we can access all parameters through out our project by simply creation of one object for that entity class based on this we can reduce redundancy of code and increase re usability
Observe above code have u seen this function before? in BLL.CS i said i will explain it later got it inDAL.CS I have created one function InsertUserInformation and using this one inBLL.CS by simply creating one object of DAL in BLL.CS.
Here you will get one doubt that is why BLL.CS we can use this DAL.CS directly into our code behind we already discuss Business logic layer provide interface between DAL and Application layer by using this we can maintain consistency to our application.
Now our Business Logic Layer is ready and our Data access layer is ready now how we can use this in our application layer write following code in your save button click like this
USERDETAILS.aspx
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
namespace WebApplication3
{
public partial class userdetails : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
{
BEL objUserBEL = new BEL();
objUserBEL.UserName = TextBox1.Text;
objUserBEL.Password = TextBox2.Text;
objUserBEL.conPassword = TextBox3.Text;
objUserBEL.FirstName = TextBox4.Text;
objUserBEL.LastName = TextBox5.Text;
objUserBEL.Email = TextBox6.Text;
objUserBEL.Phoneno = TextBox7.Text;
objUserBEL.Location = TextBox8.Text;
objUserBEL.Created_By = TextBox9.Text;
BLL objUserBLL = new BLL();
objUserBLL.InsertUserDetails(objUserBEL);
}
}
}
}
Configuration settings:
open web config file and follow this code
<connectionStrings>
<add name="ApplicationServices"
connectionString="Data Source=COMP-43; Catalog=ram;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
Here if you observe I am passing all parameters using this BEL(Entity Layer) and we are calling the methodInsertUserDetails by using this BLL(Business Logic Layer)
Now run your applciation test with debugger you can get idea clearly.
I hope it helps you.
No comments:
Post a Comment