Page History

...

The processing flow is described as follows:

1. User enters data, The user fills in the web application form, entering data such as first and last name, date of birth, and place of birth, etc, in the web application form.
2. The Web Form needs to submit submits the request to a servlet running in an application server.
3. The servlet JMSServlet creates a record for the submitter in a datbase database table. Let's say the table contains a RECORD ID, USERNAME and TAXID fields.
4. The servlet then responds to the user with a page that has a message and a link. The message says, "Check your email for a message that will contain a link for checking TIN status." It also sends an email to the person with a link that says "Click here to retrieve your record." The link contains the record ID and points to a jsp JSP or servlet that can retrieve the user's record. Initially the TAXID field will say "PENDING".
5. The servlet JMSServlet then publishes the request to the submission topic.
6. The applicationFormReceiver, which is a JMS Binding component that subscribes to the submission topic, receives the request.
7. The applicationFormReceiver sends the data creates a normalized message and sends it to the formProcessor via the NMR.
8. The formProcessor assigns the appropriate TIN to the user. The formProcessor then publishes the response to the result topic.
9. A message driven bean (MDB) is also running in the same application server as the servlet. The MDB is listening on the Result topic for the result from the formProcessor.
10. When the MDB reads the TIN it updates the user's record in the database.
11. Now, when the user clicks the link, the TAXID field will have the TIN and no longer say, "PENDING"

...