The purpose of this work is to create a complete web application for issuing accounts and managing mobile customers. The application includes categories of users such as customers, sellers and application administrators, with different rights and functions for each category of users.
- 3-tier model
- Tomcat
- Java
- Jsp
- Servlets
- HTML
- css
- MySQL
-
The function of the login: Each user has a unique username and unique password which are stored as information in the Database and in particular in the Users panel. These two fields identify the user on the home page of the application. The user password is stored encrypted using the << Encryption.java >> class which contains methods for encrypting using salt and hash.
-
Session management: When the user logs in to the application, his personal information (username) is stored and retained in the session. Regarding the status of the user (Admin, Seller, Client) it is not necessary to maintain this information since different pages have been created for each category of users. The session information "follows" the user as he navigates the application, until he logs off.
-
The logout function: When a user logs out, he is returned to the home page of the application (login page). This clears the cache and cancels the session.
-
Through this login page, all users have the ability to log in to the application and transfer to their respective page depending on their status (Admin, Seller, Client). This page is called << login.jsp >> and is shown below.
- Account View: The view of a user account is implemented through the servlet named << ClientYourBillsServlet.java >> which dynamically creates the page and displays the following.
- Call History View: Call history is viewed through the << ClientsCallAnalysisServlet.java >> servlet which displays the calls that have been made and included in an account.
- Account payment: Account payment is made through the servlet << ClientYourBillsServlet2.java >>.
- Creating a seller: This process is implemented through the static page << admin_register_seller.jsp >> and when you press the << Register >> button the servlet << AdminRegisterSellerServlet.java >> is called.
- Creating a client: This process is implemented through the static page << admin_register_client.jsp >> and when you press the << Register >> button the servlet << AdminRegisterClientServlet.java >> is called.
- Creating an administrator: This process is implemented through the static page << admin_register_admin.jsp >> and when you press the << Register >> button the servlet << AdminRegisterServlet.java >> is called.
- Customizing a seller: This process is implemented through the servlet << AdminSellersViewServlet.java >> and allows you to change some or all of the features of a seller.
- Customizing a client: This process is implemented through the servlet << AdminClientsViewServlet.java >> and allows you to change some or all of the characteristics of a client.
- Deleting a seller: This process is implemented through the servlet << AdminSellerViewDeleteServlet.java >> and allows you to delete a seller.
- Deleting a client: This process is implemented through the servlet << AdminClientsViewDeleteServlet.java >> and it is possible to delete a client.
- Creating new plan: This process is implemented through the static page << admin_create_plan.jsp >> and when you press the << Create >> button the servlet << PlanCreateServlet.java >> is called.
- Plan configuration: This process is implemented through the servlet << PlansViewServlet.java >> and allows the plan to be configured.
- Deleting plan: This process is implemented through the servlet << PlansViewDeleteServlet.java >> and it is possible to delete a plan.
- Seller functions are vary similar with administrators with some restrictions.
- Can't register admin
- Can't edit/delete admin etc.