We need to do this since we will have multiple web & non-web clients accessing the business/persistence layer.

One approach is to wrap the torque based business/persistence component as a REST service and deploy it in a separate tomcat instance or as separate web-app.

How maintainable it has to be? How many web applications/clients will be accessing the persistence component (the torque thing deployed on a separate tomcat)? is it necessary that the separate persistence component be deployed on a separate machine? are they geographically separated? What are the security concerns? How much transaction throughput must the persistence component be able to handle? is all client written in Java? Any technology constraint? ... e t c

without more info, the best I can say is that your current setup will work. Not sure if it will work well for your need or not

Regards, Zen.

Raj Murthy

Greenhorn

Posts: 14

posted 8 years ago

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.