One second doesn't seem to be bad for response time.
If you're writing to a DB and they are reading it maybe all the channels are slowing it down a little.
Would have to know more about the plumbing sequence but it sounds like you're writing to a DB entry and then they are reading it ?
Why not create an RPG based XML URL requestor instead so the XML response is immediate to the java app from the HTTP call to the RPG app. No DB or clob interaction needed.
Then again I don't know the app architecture and 1 second response sounds good to me :-)
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 4
date: Wed, 2 Oct 2013 14:44:20 -0400
from: Tim Wright <Tim.Wright@xxxxxxxxxxxxxxxxxxxxxx>
subject: Pushing XML out to a browser request
In a nutshell, we have a back end home grown RPG ERP system with a J2EE based dealer extranet on top. Part of the function of the dealer interface is the management of warranty claims. The browser requests claim information from the back end and the back end produces an XML document in return. This works great - except - our web comrades complain that it takes over a full second to get the XML back. They do direct SQL hits to the DB and get results in a tenth of the time - so they complain. Do you know of anyone who has struggled with response time related to creating XML via RPG and passing it back to a web interface? We don't know where the bottleneck is. It might be on the browser side, but we can't seem to isolate it.
If anyone has insight about this, I can provide more details to help you answer.
Many thanks!
**************************
This e-mail message may contain confidential or privileged information. If you are not the intended recipient, please delete the message and any attachments and notify the sender by return e-mail. You should not retain, distribute, disclose or use any of the information in this message.
**************************
midrange.com
