Project Description:
Airline Safe Mode Application;
The Airline Safe Mode Application is designed to optimize the boarding process
for airline flights by minimizing the delays in updating passenger boarding details.
By providing real-time information and offering a "safe mode" option, the
application airport agents can efficiently manage flight boarding, even the
presence of network-related Issus .
Generally it takes 1 hour for domestic boarding and 3 hours for international
boarding-to reduce this delay we have implemented some changes in the existing
airline application.
This application across different layers: Web Layer (Presentation Layer),
Controller Layer, and Service Layer.
Web Layer (Presentation Layer):
The front-end interface where users interact with the application.
You've designed views for both Passenger and Client interactions.
Users initiate boarding using a PNR number, which is verified to ensure accurate
details.
Controller Layer:
Contains the code for performing CRUD (Create, Read, Update, Delete)operations.
Manages the business logic for the application, including handling user
interactions and data processing.
Service Layer:
Acts as a database using cache memory to optimize data retrieval.
Implemented to address delays caused by data center issues.
Data stored in cache memory (Extreme Scale Cache) ensures automatic rendering
of current information.
Safe Mode:
When the delay in updating passenger boarding details is detected, the
application prompts the agent to switch to a "safe mode" where the controller
layer connects to the main service layer of the flight to retrieve the necessary
details.
Event Listeners:
The application utilizes two types of event listener classes:
Passenger Information Display System (PIDS):
This event listener class is responsible for monitoring changes in passenger
details. It likely listens for updates related to passenger information, such as seat
assignments, ticketing status, and other relevant data.
Flight Passenger Event System (FPES):
This event listener class is designed to track changes in flight details. It could be
responsible for capturing updates related to flight schedules, departure gates,
boarding times, and other flight-related information.
Light Streamer:
The application employs Light Streamer to facilitate real-time communication
between the server-side and the client-side. Light Streamer is a technology that
enables efficient data streaming and event broadcasting. In this context, Light
Streamer is used to publish events from the server-side (where data updates are
likely processed) to the client-side (where airport agents interact with the
application). This ensures that agents receive real-time updates on passenger and
flight details, enabling them to make informed decisions and respond promptly to
potential delays.
coclusion:
our project aims to enhance the efficiency of the flight boarding process by
addressing delays in updating passenger boarding details. The "Airline Safe Mode"
domain encompasses functionalities such as detecting delays, switching to safe
mode, using event listeners to track changes, and employing Light Streamer for
real-time updates. we have to help airport agents with timely and accurate
information to prevent boarding delays caused by network issues.
Recently Faced issues:
1. In spring boot if we are passing arguments of Array data type but giving a
input as integer then there will be an input mismatch exception occurs then
we have solved this using debugging using log files
2. Another one we will face is during development/deployment there will a
system issue or server issues, we solved this by raising ticket and the
technical support team will solve the errors.
3. And in some cases we are facing an issue because of dependency, if
dependencies are not added properly then we will be having an issue, we
will sort out the [Link] most common issue I can say is security if the
token created is not matching while logging then there will be an issue
again we will sort out.