A cloud based alumni portal website using JSP with Continous Integration.

Table of Contents

• About this project
• Developers
• Architecture Diagram
• Technology Stack and Environment used
  1. Frontend
  2. Backend
  3. Environment
  4. Session Management
  5. Database
  6. Dependency Resolver and Packaging
  7. Continous Integration and Delivery
  8. Other services
• Directory Structure

About this project:

We have built a sample web application for Alumni portal using Java Servlets, JSP, Java Beans, html, css, js. Industry practices and standards are followed in both development and deployment.

This project is built and deployed end-to-end in cloud using Amazon Web Services. Proper continous integration and continous deivery techniques are followed.

Developers

1. Thanga Manickam M - CB.EN.U4CSE17161
2. R Kailash - CB.EN.U4CSE17123
3. S Prathiba - CB.EN.U4CSE17141
4. Sreeramji K S - CB.EN.U4CSE17153

Architecture Diagram

Technology Stack and Environment used

The following tools and services are used in this project.

Frontend

Html, CSS, java script are used to render frontend page from serverside. Form validations are done using js as client side scripting. Bootstrap is used as primary CSS framework. JSTL (JavaServer Pages Standard Tag Library) and EL (Expression Language) are used to improve the usability and readability of JSP code.

Backend

The application is end to end server side scripted using Java servlets and Java Server Pages (JSP). The server is deployed in an Apache Tomcat 8.5 server which renders the dynamic JSP pages. Communication between pages is carried out using Java Beans classes.

Environment

• SDK : Java Correto 11
• Packager : Maven
• Server : Apache Tomcat 8.5
• Deployed Environment : 64bit Amazon Linux 2/4.1.3

Session Management

We have used http sessions to keep track of user login and session validation on serverside.

Database

A MySQL server deployed in AWS RDS is used as database to store application data.

Dependency Resolver and Packaging

Maven is used to resolve the dependencies in the project, build the code and package the war files.

Continous Integration and Delivery

To reduce the time on integration and deployment, we have used Continous Integration and Continous Delivery in this project. An AWS codepipeline is setup which gets triggered whenever a code is pushed to this repo. AWS codebuild runs the maven packaging to create war file. This war file is deployed in an AWS Elastic Bean stalk environment with Apache Tomcat 8.5 server in it.

Other services

We have used AWS S3 to store profile pictures and build articrafts. We have also used AWS Simple Email Service (SES) to send automated emails when user fills the query form.

Directory Structure

• src\main\java\Model: All helper java classes
• src\main\java\ServletPackage: All the servlets used in application
• pom.xml: Maven Dependencies and packaging
• src\main\webapp\WEB-INF\web.xml: Server version, configuration and session properties
• buildspec.yml: Contains the codebuild instructions.
• src\main\webapp: Jsp, Css, js, static images

AWS References

• https://docs.aws.amazon.com/codebuild/latest/userguide/sample-elastic-beanstalk.html#sample-elastic-beanstalk-codepipeline
• https://docs.aws.amazon.com/rds/index.html
• https://docs.aws.amazon.com/ses/index.html
• https://docs.aws.amazon.com/s3/index.html