Re: [JBoss-user] ASP Model for J2EE?

[Samuel Franklyn]

I think each approach has its advantages and disadvantages. ----- Original Message ----- From: Jeff Campbell To: [EMAIL PROTECTED] Sent: Monday, July 02, 2001 11:18 PM Subject: [JBoss-user] ASP Model for J2EE? I'm stumped...   What is the best approach for using J2EE in an Application Service Provider (ASP) scenario?   Info:  I have a J2EE ear file that I deploy on my JBOSS J2EE container.  I would like to have multiple companies use this application, without sharing data.   Here is a list of possibilities...  (some may be completely WRONG)....  what is the best approach?   1. Give each company their own IP address, JBOSS container, and Database.  Advantages: Best reliability and security. Since each company having their own IP address you could transfer the IP address to other machine in case of disaster.   Disadvantages: Biggest resource spending so this should be done if your customer can be charged premium price.   or   2. Have one IP address, one JBOSS container, multiple Databases and have JBoss some how dynamically switch datasources. (I have no idea how to do this) (This is the method that I would prefer, if it were possible)  Advantages: Reliable and secure enough setup. Less resources needed than previous setup.   Disadvantages: Programming complexity. To be able to implement this you must create a shared data source and custom security. In this shared data source you create customer table which contains each customer specific data source and relate to users table. You need someone with good experience in programming custom security. I think the best people that can do this is the main developers of JBoss like Scott Stark, Rickard Oberg, and friends. or   3. Have one IP address, one JBOSS container, one Database (but have to go through and add a column to each table, and query specifying the company ID) (I would hate to have to do this one). Advantages: This is the most efficient in terms of resources if your database is not to large. This set up is also very valuable when your customers need to interact with each other. The programming is not to complex.   Disadvantages: Although the programming is not complex however the programming effort is large. You have to do a lot more typing :) Any other suggestions would be HELPFUL!   Thanks, Jeff Campbell