Windows Dedicate Server

jacklcs

Good day....

I am planned to purchase a Windows Dedicate Server with Windows 2008.I am the main administrator of the server, I can resell the Server to my client too.

From this Server, I can crop the 100 GB for my own company for their web site and email.
From this Server, I can crop the 100 GB for my client "John" for their web site and email. John has the IP Address.
From this Server, I can crop the 100 GB for my client "Peter" for their web site and email. Peter has the IP Address.

After I have build the application for John, when come to Windows Dedicate Server, should I install the AwareIM server to John 100GB Space or install directly to Windows 2008 Server? This application only use by John Company.

Now I build 2nd Application for Peter Company (difference from John Application), should I install the AwareIM Server again to Peter 100GB Space? Otherwise what should I do?

For my own space 100GB, I want to put AwareIM Demo application for the purposes of marketing my application..

Whether I should install my developer license to the Windows Deducate Server will do... then with John.BSV and Peter.BSV. If I do that, how to I separate John and Peter AwareIM database to prevent any corruption in the future..

How John and Peter access the application?

please advice technical issue...

jacklcs

AwareIM support.. can u advice on technical issue? thanks.

aware_support

I am not sure I completely follow the question, but if you are talking about hosting a multi-tenanted application on your server, then there are two ways you can do it:

1) Deploy the same application into separate business spaces - for John, Paul etc. Different users will then access their applications using different URL's (the name of the particular business space will be part of the URL)
This approach is useful if the number of different clients is not big (1 - 50)

Otherwise, you need to:
2) Either build tenant isolation into the application itself using protection rules (in this case you only have one business space) or
3) Use different servers for different clients

jacklcs

1) Deploy the same application into separate business spaces - for John, Paul etc. Different users will then access their applications using different URL's (the name of the particular business space will be part of the URL)
This approach is useful if the number of different clients is not big (1 - 50)

thanks for the reply... If I do that, the AwareIM database only 1 database. It is possible to separate database for each client?
thanks.

aware_support

With method 1) you will have one database, but totally different database tables. If you want separate databases you need separate Aware IM installations.

[deleted]

I am new to AIM but one thing I can say is make sure you think this through.

When there are 2 clients there is always potential for 3,4 or hopefully more. Using a single BSV in multi-tennant config should save you a heap of pain in the long run, especially when it comes to upgrading your solution, licensing costs and if your following Agile development methodologies.

Regards, James

ACDC

I think using a single bsv in a multi tennant application comes with serious risk. Having clients share the same tables could become a nightmare down the road if something goes wrong.

On the other hand, if the application is a very simple basic app, then it could be the answer as long as a very good design is in place that guarantees exclusivity on each record to each client

Using a separate bsv for each client isolates the clients data in their own tables in the same database. This makes more sense as it allows for much more flexibility and agility in meeting a clients custom requirements. Also, if you need to move the clients data to another server, its just of case copying the clients tables to the new server db.

jacklcs

With method 1) you will have one database, but totally different database tables. If you want separate databases you need separate Aware IM installations.

Using a separate bsv for each client isolates the clients data in their own tables in the same database. This makes more sense as it allows for much more flexibility and agility in meeting a clients custom requirements. Also, if you need to move the clients data to another server, its just of case copying the clients tables to the new server db.

Yes. I think using separate BSV is better to isolates the clients data. Moreover, difference client might have differnce requirement for the system.

Assume now I have John.BSV and Peter.BSV... 1 database but difference database tables. What happen the John database table is corrupted, will it affect Peter data?

Assume now John now want their database. How do I copy the database to them without Peter's data inside?

Export the John.BSV and Copy BASDB will do to the New Server?
What is the procedure like to prevent corruption of the data.

Thanks.

aware_support

If Paul's table gets corrupted John will not be affected. In any case you need to do regular backups, so if a table is corrupted you can restore it from the backup.

jacklcs

hi...

Any way to view the table of the BASDB for the John and Peter?

I open the BASDB, there are many files.. I read the Forums talk about "Table"... where to view the table and the data?

thanks.

rocketman

With multilple BSV's the TABLES in BASDB will be easy to differentiates. they will be called:

John_Tablename1
John_Tablename2
Peter_Tablename1
Peter_Tablename2

etc etc etc

I would definitely go for multiple BSV's to avoid corruption issues, but if you have a developer version, you could also create virtual machines on your dedicated server and give each user a compiled version on their VM - having purchased the end user licenses from /awareIM