|
On the AS/400 side, we read the order number from the data queue, then post the order to the production files using the info in the web order order work files.
On the web order side, the program is trying to display an order confirmation screen by reading the information for the order from the production files.
What is happening is that when the web order reads the production files, we haven't finished process the order yet.
What I have been thinking about is to create another data queue (PostedOrd) keyed on order number, and have the AS/400 posting program write the order number just posted to the PostedOrd data queue when the posting is complete.
The web order program would read the keyed PostedOrd data queue by the order number they want to confirm. Their program would just sit there until the AS/400 side writes the order number to the data queue. I am thinking that they could use the AS/400 tool box for Java class KeyedDataQueue
My questions are:1) Can multiple separate web order programs read the keyed data queue PostedOrd for the specific order number they are interested in without conflicting with each other. In other words, if one web order is waiting for his order to be posted, can another web order be waiting for another order to be posted at the same time and can they read asynchronously?
2) If the above works, will there be any lock problems when the AS/400 side writes to the data queue?
Any other suggestions?During the development process, the web order currently keeps checking the production files every 5 seconds for the order they are interested in. After 20 seconds it figures there has been some kind of error. This is not the solution we want to go with
This is not a high volume web site like Amazon, but a company web site where the sales reps can enter their orders.
Thanks Dave Murvin DRM Enterprises, Inc.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.