Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...To use (and how) or not to use DotNetNuke ?To use (and how) or not to use DotNetNuke ?
Previous
 
Next
New Post
6/29/2013 12:03 PM
 
I need to setup an extranet for 1,500 users, that will mainly check a list of Microsoft Excel files, i.e. each user will only be able to see their own documents.

I would normally implement such a scenario in SharePoint, but the Internet Connector license required is cost-prohibitive for the client, so I am contemplating the idea of using DotNetNuke to implement this project.

Therefore, I would very much appreciate your expert help with the following questions:


Is there an out-of-the-box (OOTB) DotNetNuke feature to quickly enable assignment of files to different users and be absolutely certain that no other user can view files other than their own, no matter how they request the file, i.e. through the browser's URL, through their home page, etc ? This is going to be a repetitive process where 5 files per agent will be replaced/added every night for each user (a total of 7,500 files).

Am I correct to assume that I will not be able to support my user population of 1,500 users with a single DotNetNuke server? I am thinking that I should probably need a web farm of DotNetNuke servers. How many DotNetNuke servers do you think I shall need to support 700 (scenario 1) and/or 1,500 (scenario 2) concurrent users ? What kind of hardware specifications I am looking at for the above two scenarios ? Do I use the Microsoft load balancing software for distributing sessions/requests between the servers in the farm, or a hardware is preferred ?

If I buy multiple server licenses of DotNetNuke Pro and I need to create a farm, I must pay the server license for each server in the farm, correct? What other Microsoft Server/CAL licensing do I need? i.e. server license for Windows Server 2008 R2+, server license for SQL Server 2008 R2+. Do I need any Windows/SQL Server CALs for the users accessing the server ? I think not as the external users are not employees of the client, just external users, but I am not sure. Any thoughts?

Do I need to setup different DotNetNuke server roles for each server? i.e. Search Server, Application Server, Web Server, etc?

Does DotNetNuke allows access through VPN and SSL channels?

Does DotNetNuke 7.0 professional support the creation of 1,500 users and assign them access rights, through an EXCEL file, or I shall need to write custom code to do this ?

These are many questions, but I need to clarify a few things to help me formulate a go/no go decision to implement it using DotNetNuke.

I hope any of you DotNetNuke experts can find the time to help.
Thank you and regards,
 
New Post
6/30/2013 9:55 AM
 
I have no doubt, DNN will be a valuable platform for your needs.

Serving 1500 user should be easily done from a single web server (I have a client with 130.000 users on a single server and even DotNetNuke.com ran on a single machine until about 3 years ago).

None of the DNN packages does include a user import tool out of the box, but there are DNN modules in the store, which provide this feature (e.g. http://store.dotnetnuke.com/home/prod...).

For user files, there are modules like http://userfiles.codeplex.com/ or DMX from www.bring2mind, if you plan to go with DN Community Edition (which should be suitable for your needs).

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/30/2013 10:28 AM
 

Dear Sebastian,

Thank you for taking the time to provide your valuable input.

So, if I got you right, I can use DNN Community Edition for what I need, without resorting to the paid Pro/Enterprise versions.

I appreciate your advice of running a DNN CE portal on a single web server for servicing my 1500 users. However, can I easily add a second web server later, should the need arises? i.e. to create a web farm of DNN CE servers ?

Do you think it is a good idea to keep the SQL Server Standard on a separate box, or have everything altogether put in the same box?

Last but not least, a server configuration with the following hardware specs you think is acceptable for my needs ?

CPU: 2 x 2.8GHz
RAM: 8Gb (16Gb if DNN+SQL Server is put on the same box)
NIC: 2 x 1Gbit network cards
UNC Network Share for storing portal files, documents, etc.

What do you think?

Regards,
P.

 
New Post
6/30/2013 12:33 PM
 
Yes, you should be able to use DNN Community Edition, unless you need one of the additional DNN PE modules.
You may start with a single server (specs look fine) running both SQL Server and IIS, but make sure, SQL Server is not taking all memory, because DNN requires memory for caching as well. You may easily move SQL Server to a dedicated machine, if necessary and extend to a web farm, if necessary (I doubt, it will be). Portal files will be located by default on the web server, you may use an UNC path as mapped folder (using Evotiva Global Storage http://store.dotnetnuke.com/home/prod...)

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/30/2013 1:17 PM
 
The important thing here is NOT the count of users. More users just means more rows in the database which is a trivial cost.

What's important is how many users are active simultaneously and what they are doing. Your original post suggests that every user will have several files chaged each day. If all your 1500 users need to login at 09:00 every day, to get their new files by 09:05 - that's a very different proposition to maybe having a few of them login in occasionally to see if there are new files.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...To use (and how) or not to use DotNetNuke ?To use (and how) or not to use DotNetNuke ?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out