Institute of Information Science - University of Miskolc

Create a simple HTML form where users are able to charge their mobile phones with a given amount of money.

 Possible amounts: $10, $30, $50, $100 
 The 3 mobile service providers: "Provider A", "Provider B", "Provider C"
 Mobile phone number: 7 numbers.

Create a servlet which gets the HTTP GET request from the HTML form and checks the validity of the messages. If the message is invalid, then returns an “Invalid data” text, else writes “Ok”.

• Create an inner class within servlet and store these payments in a java ArrayList.
• Create an other method to list the number of payments (with a new HTTP get request).

Create a third client that reads the statistics from the 'colorStatistics' queue and outputs to the console, for example, '10 'RED' messages have been processed'.

Create tests to validate the original functionality

Create an application that simulates temperature monitoring using message queues. This system involves three separate clients for generating, processing, and reporting temperature data.

Component 1: Temperature Generation Client

• Client 1 connects to the temperatureQueue using a point-to-point connection.
• Function: Sends messages with randomly assigned temperature readings (in degrees Celsius) within a normal range (-10 to 40 degrees Celsius) every 3 seconds.

Component 2: Temperature Monitoring Processor

• Message Processor: Exclusively receives temperature readings from temperatureQueue.
• Function: Monitors for abnormal temperature readings. A reading is considered abnormal if it is below -5 or above 35 degrees Celsius.
• Notification: After receiving 5 abnormal readings, the processor sends a notification to the alertQueue, indicating that 5 abnormal temperature readings have been detected.

Component 3: Alert Reporting Client

• Reads from the alertQueue.
• Output: Prints a message to the console, e.g., “5 abnormal temperature readings have been detected.”

Tests to validate:

• The functionality of sending and receiving messages correctly.
• The correct identification of abnormal temperature readings.
• The accurate accumulation and dispatch of alerts after every 5 abnormal readings.

Create an application that simulates monitoring and controlling humidity levels within an environment using message queues. This system will involve three separate clients for generating, processing, and reporting humidity data.

Component 1: Humidity Generation Client

• Client 1: Connects to the humidityQueue using a point-to-point connection.
• Function: Sends messages with randomly assigned humidity readings (expressed as percentages) within a range of 30% to 90% every 4 seconds.

Component 2: Humidity Monitoring Processor

• Message Processor: Receives humidity readings from humidityQueue.
• Function: Monitors for high humidity readings, considered high if they exceed 70%.
• Notification: After receiving 3 consecutive high humidity readings, the processor sends a notification to the alertQueue, indicating that high humidity levels have been detected.

Component 3: Alert Reporting Client

• Client 3: Reads from the alertQueue.
• Output: Prints a message to the console, e.g., “High humidity alert: 3 consecutive readings over 70%.”

Create tests to validate:

• The functionality of sending and receiving messages correctly.
• The correct identification of high humidity readings.
• The accurate accumulation and dispatch of alerts after detecting high humidity conditions.

Create an application that simulates monitoring and controlling air quality levels within an indoor environment using message queues. This system will involve three separate clients for generating, processing, and reporting air quality data.

Component 1: Air Quality Data Generation Client

• Client 1: Connects to the airQualityQueue using a point-to-point connection.
• Function: Sends messages with randomly assigned air quality readings, quantified as Air Quality Index (AQI) values, within a range of 0 (Good) to 300 (Hazardous) every 3 seconds.

Component 2: Air Quality Alert Processor Message Processor: Exclusively receives AQI readings from airQualityQueue. Function: Monitors for poor air quality readings, considered poor if they exceed an AQI of 150. Notification: After receiving 2 consecutive readings above the threshold, the processor sends a notification to the airQualityAlertQueue, indicating that poor air quality levels have been detected.

Component 3: Alert Reporting Client

• Client 3: Reads from the airQualityAlertQueue.
• Output: Prints a message to the console, e.g., “Air quality alert: 2 consecutive readings above 150 AQI.”

Create tests to validate:

• The functionality of sending and receiving messages correctly.
• The correct identification of poor air quality readings.
• The accurate accumulation and dispatch of alerts after detecting poor air quality conditions.