Forums Register Login

Best way to structure an enterprise application

+Pie Number of slices to send: Send
I'm wondering what the best way to set up an enterprise app is. For example, say i'm developing an application for a hospital clinic. As part of this application, i determine that i need a scheduling component, a patient management component, an employee management component, and a web client. Each of the components is deployed as an ejb-jar with a session facade. If i want to reuse some of the functionality in one or more of the components in another application (e.g. use the employee component for a payroll application), what is the best way to deploy this application? Should i put all of the components, as well as the web client, in an .ear file, then bundle the same components in the second application's .ear file, deploying the same beans with different jndi names? Or should i keep these reusable components out of the application's ear and deploy each of them on their own, so there is only one version of each living on the server? Is there a best practice for this kind of situation?

Thanks,
Brent
Ever since I found this suit I've felt strange new needs. And a tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 620 times.
Similar Threads
Deploying servlet in tomcat
long post IBM.158
Passed 700,701 and 340 last Thursday
Integrating Jforum with other application but within a single ear
Integrating JForum into another application
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 03:58:25.