Change from sample object names into meaningful object names

Some audit events go missing and aren't stored in the bean

Admin console -
Create startup servlet which listens for auditing events and stores into non-persistent bean

The console application for this assignment will record an event when it is started. When executing, it should expose a SOAP web service over HTTP called
‘processPaymentService’. This web service will expose two methods – processCard(String cardNo) used for credit card payments using the bank; and processPaypal(String paypalID) used for PayPal payments. When this method is called, an event will be logged recording the card number or PayPal Identifier as appropriate to System.out.

Leave the ‘back-end Paypal or bank payment application’ as a WAR package executing under a local Glassfish instance. Remove the web service created in assignment 2.

Instead, replace the integration between the ‘online website application’ and the ‘back-end Paypal or bank payment application’ with a REST client call to the REST service created above.

You will need to create a background Thread, which starts on application startup and then regularly polls the REST service hosted by the ‘online website application’

Enhance the online website application such that after a user successfully logs in they can provide either a credit card number or PayPal Identifier (but not both). Trigger a payment by having the online website application call the new back-end system via its web service. For the purpose of this assignment, you can assume the web service is running on ‘localhost’. You will need to configure your second Glassfish instance to listen on TCP port 8081 (so that all URLs in the WSDLs are consistent, to assist with marking).

Need to start the assignment, easiest way would be to create 3 base projects

Online shop needs to be migrated to app engine

Refer to assignment sheet

finish all documentation for assignment 2

Current implementation is hacky

Create two basic HTTP servlets or JSPs that implement a login page for the online shopping website.

Add a new REST interface to the ‘online website application’, which will be used by the ‘back-end Paypal or bank payment application’ to poll for payments waiting to be processed. Update the ‘online website application’ to store Paypal or bank transactions on a Pull Task Queue for later retrieval through the REST interface. You can find examples on how to use Pull Tasks Queue’s on the Google API website - https://developers.google.com/appengine/docs/java/taskqueue/overview-pull

ATM not passing json, a post encoded string is being passed and parsed

Create communication topic and connection

Connection Factory: jms/myConnectionFactory
Topic: jms/seng4400ass2PS

Validate the user credentials against a static username/password pair, which you can store hardcoded in the code. Whenever a login is attempted the software will record if it was successful or failed.

• An updated system diagram
• A high-level description of this diagram
• Any additional information the assessor may need to install, run and mark your submission.

doGet() needs to throw error in Pay.java servlet

Add more meaningful logging

Make the beans actual beans and not publicly accessible objects

Add in JUL in its place

Admin Console -
Servlet to view last 50 records stored in bean

Remove the polling/empty messages that are being printed to the console once per second