Zen,
Thanks for the reply. Here are the responses for your questions.
How maintainable it has to be?
>>>wanted to answer with a question..
.. depends on what maintainable means. If we do end up deploying the persistence component inside a container (such as web container) it can monitored & configured fairly easily.
How many web applications/clients will be accessing the persistence component (the torque thing deployed on a separate tomcat)?
>>>around 4-5
is it necessary that the separate persistence component be deployed on a separate machine?
>>>not 'necessary', but we will have 5 web apps & the persistence on same machine. we are looking to distribute the components
are they geographically separated?
>>>No
What are the security concerns?
>>>the persistence will be visible only to intended clients. So do not have big security clients.
How much transaction throughput must the persistence component be able to handle?
>>>the current web app has average response time of around 2-4 secs per page on average.
we are looking to keep this response time as close as possible.
is all client written in Java? Any technology constraint?
>>>4-5 clients will be servlet/jsp web applications; one will be C# based windows application.
TIA,
Raj
[ February 13, 2008: Message edited by: Raj Murthy ]
[ February 13, 2008: Message edited by: Raj Murthy ]