One Applicaiton Server, Multiple Databases #3230
Replies: 3 comments 5 replies
-
You would have to customize the build to build two different EARs, referring different Data Sources:
and specifying different context Roots for included web application. But it's not tested and so I can't give any support. Last 15 years, people moved away from bundling multiple deployments into one application server to separating services running in separate containers. |
Beta Was this translation helpful? Give feedback.
-
What "costs" you refer for running one archive container for each hospital? |
Beta Was this translation helpful? Give feedback.
-
BTW, using one DB for multiple hospital, you still can isolate the archive content for each hospital by using hospital specific Issuer of Patient IDs and/or Universal Entity IDs for Patient IDs and configuring Access control based on Archive AEs |
Beta Was this translation helpful? Give feedback.
-
Hi, there,
I check the WIKI, but not sure how to config the system to get this done:
Suppose I have A hospital and B hospital, I wolud like both of them have their own database but share one application server. That is, I could easily unmount A or B in a clean way if necessay. Also, If possible, I could easily mount a new hospital say, C, without touching the original A and B databases .
L.B.
Beta Was this translation helpful? Give feedback.
All reactions