Re: Common application for different database users
Re: Common application for different database users
- Subject: Re: Common application for different database users
- From: Lachlan Deck <email@hidden>
- Date: Wed, 15 Aug 2007 10:51:27 +1000
Hi there,
On 14/08/2007, at 1:16 PM, Cheong Hee (Datasonic) wrote:
I have the same application that is currently used by different
group of
users (or company). I did it in JavaMonitor and gave them different
name
for application instances and initialized them with few own
parameters in
JavaMonitor. So that when each group of them will access through:
www.mydomain.com/aaa after webserver redirection for group "aaa"
etc..
This made me maintains list of application instances.
The other option is to let user go to the common home page, and have a
selector to choose so that to differentiate the group of users.
But this could be an issue, as it means other groups/companies are
exposed
to anyone who go to the common home page.
Is there any better way of design so that the same application
could be used
to access their own database, while not to create list of different
application instances in JavaMonitor?
Here's the approach I took...
1) shared instance(s) for all
2) single-database for all
3) data kept unique via a Company table. All data has a relationship
to company.
4) Company <-->> CompanyDomain etc to identify appropriate company's
data on incoming request.
5) custom components/css can be optionally overridden per primary
domain in an external folder on disk
It's been very flexible...
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden