Pete,
Go ahead and run the the Java component on an external Windows or Linux
server.
You're still running against the "i" so the data is still there and
that's the most important thing for backup and recovery purposes.
Think of the outboard Tomcat Server as a Front-End Processor to the "i".
Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
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: 1
date: Sat, 16 Jan 2010 16:53:27 -0600
from: Pete Hall <pete@xxxxxxxxxxxxxx>
subject: Native tomcat vs external server
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm attempting to put together a web app which includes an instance of
the BIRT viewer. The Java application pieces perform well, however, I've
noticed a severe CPU hit when a BIRT viewer report is requested. It
doesn't seem to occur when I run the app from my development PC. Is
there any compelling reason to host Tomcat on the i? Is Java simply more
efficient when hosted on a dedicated server running another OS and
accessing the i "remotely" from the local network? Tuning on the i is
not optimal. However, I'm reluctant to take on that responsibility
without a good reason. Perhaps I should request a VM to host the BIRT
viewer application? Any opinions gratefully accepted.
midrange.com
