How karan19/internet-banking works
Project Type and Purpose
• This is a monolithic Java EE web application packaged with Maven and deployed to an OpenShift Tomcat (jbossews) cartridge.
• It provides online banking features: user registration, login, account opening, profile management, fund transfers (with OTP via SMS/email), and transaction history.
File-Structure Analysis
• src/main/java: core JavaBeans (OtpBean, SendOtpBean, SendSmsBean) and any custom action classes.
• src/main/webapp: JSP views organized by feature (login, register, account, fundtransfer, profile, include).
• WEB-INF/lib: third-party libraries (MySQL JDBC, JavaMail, Plivo SDK).
• pom.xml: Maven build, dependencies, packaging as a WAR.
• .openshift/: OpenShift configuration (Tomcat server.xml, context, cron jobs for scheduled tasks).
Readme Insights
• No in-depth architecture description – points to OpenShift Tomcat cartridge guide, confirming server platform.
• Cron directory suggests scheduled background jobs (e.g., nightly reports or OTP cleanups).
Main Components
a. Presentation Tier (Browser)
• Users interact via a web browser over HTTP/HTTPS.
b. Web Container (Tomcat on OpenShift)
• JSP pages (views)
• JavaBeans and Servlets (controllers/business logic)
• Cron-configured scheduled jobs (background tasks)
c. Database (MySQL)
• Stores user profiles, account details, transactions, OTP records.
d. External Services
• Plivo SMS API for OTP SMS delivery
• JavaMail (SMTP) for OTP email delivery
e. Build & Deployment
• Maven build (pom.xml) produces WAR
• .openshift scripts deploy WAR to Tomcat, apply configuration, schedule cron jobs
Relationships and Data Flows
• Browser → HTTP Request → Tomcat (Servlet/JSP)
• Servlet/JSP → Bean → JDBC → MySQL (CRUD)
• Bean → Plivo REST API (send SMS)
• Bean → JavaMail SMTP server (send email)
• Cron jobs → internal tasks → DB or external APIs
• Tomcat logs & metrics → OpenShift logging/monitoring
Architectural Patterns & Principles
• MVC-style separation: JSP “views” + JavaBeans/Servlets “controllers” + DB “model.”
• Monolithic deployment: all components in one WAR on a single Tomcat container.
• Use of scheduled jobs (cron) for asynchronous or periodic operations.
• Externalized configuration via OpenShift (.openshift/config/*.xml).
Essential Details to Capture
• Configuration layer (.openshift/config) feeding into Tomcat
• Libraries in WEB-INF/lib enabling external integrations