Application Purpose:
The application addresses delays in updating passenger boarding details due to
network issues to avoid flight boarding delays. It does this by notifying agents to
switch to a safe mode that connects to the main service layer of the flight.
Components and Interactions:
Controller Layer: Handles interactions with the user interface.
Service Layer: Main business logic layer that connects to the flight service.
Event Listeners:
PIDS (Passenger Information Display System): Monitors and displays passenger
information.
FPES (Flight Passenger Event System): Manages flight-related events.
Lightstreamer: Publishes real-time events from the server to the client.
JMS (Java Messaging System): Communicates changes from client to server.
IBM WebSphere eXtreme Scale (Extreme Scale): Stores cache memory for efficient
boarding processes.
Delay Indicator: Detects delays and notifies Lightstreamer.
Flow of Operation:
When there's a delay due to network issues, the delay indicator detects it.
The delay indicator notifies Lightstreamer about the delay.
Lightstreamer communicates with clients (agents) and informs them to switch to
safe mode.
In safe mode, agents interact with the controller layer, which connects to the main
service layer of the flight.
PIDS displays passenger information, while FPES manages flight-related events.
JMS ensures synchronization between client-side and server-side changes.
IBM WebSphere eXtreme Scale stores cache memory for the current flight,
optimizing the boarding process.
As soon as a delay is detected, the delay indicator communicates with
Lightstreamer, which in turn informs the users to switch to safe mode.
Benefits:
Efficiently handles delays caused by network issues, reducing boarding delays.
Real-time communication through Lightstreamer keeps agents informed.
JMS synchronizes changes between client and server.
Extreme Scale caching optimizes the boarding process.
Considerations:
Detailed implementation of event listeners (PIDS, FPES) and their interactions.
Configuration and setup of Lightstreamer and JMS for seamless communication.
Proper integration and configuration of IBM WebSphere eXtreme Scale for
caching.
Handling of error scenarios, security, and data consistency.
Passenger Information Display System (PIDS) Event Listener:
The PIDS event listener monitors changes in passenger information.
When passenger data is updated (e.g., seat changes, delays), the PIDS event
listener detects the change.
It triggers an action to display the updated passenger information on screens
visible to agents.
Flight Passenger Event System (FPES) Event Listener:
The FPES event listener tracks flight-related events, such as delays, gate changes,
or boarding announcements.
When a flight event occurs, the FPES event listener detects the event.
It triggers an action to notify agents and possibly update displays with relevant
flight event information.
Lightstreamer Event Listener:
Lightstreamer itself acts as a real-time event listener.
It listens for updates published from the server side to specific streams.
When a server-side change occurs (e.g., safe mode activated), Lightstreamer
notifies connected agents on the client side.
JMS (Java Messaging System) Event Listener:
The JMS event listener is used to synchronize changes between the client and
server sides.
When a client-side change occurs (e.g., passenger information update), the client-
side JMS event listener detects the change.
It sends a message to the server-side JMS event listener, informing the server of
the change.
The server-side JMS event listener processes the message and takes necessary
actions based on the change.