Right. I'm well aware of that. However, are you saying that if we were only running HATS and the part of WebSphere that comes with HATS, that I need no knowledge, what-so-ever of Websphere to make it run fine in a production environment?
The gist(s) of my concerns are: 1. We end up having to support multiple Java platforms. 2. With multiple platforms, come the need to support, installation, maintenance, performance, debugging of multiple platforms. 3. With each platform comes the need (IMHO) of one or more test platforms. 4. And with each flavor of Java platform, we have some licensing fees (product, support, etc) on a per engine basis. In this case, licensing multiple products, that apparently do the same thing, on the same single engine, when there is no "application driven" reason to do so. Am I right about this... That the full blown Websphere, can do: 1. HATS 2. Any in-house developed application that uses Oracle 10g. 3. Any thing that we would have used Jboss for. A second question, other than a cost issue, is there any thing you would use Jboss for that wouldn't work just as well on Websphere? Tom Duerbusch THD Consulting >>> Rich Smrcina <[EMAIL PROTECTED]> 8/28/2007 1:36 PM >>> If Websphere is required for and comes with HATS for the sole purpose of running HATS, then any support for that WebSphere falls under the purview of supporting HATS, NOT WebSphere. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
