Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Portals and localhostDNN Portals and localhost
Previous
 
Next
New Post
11/9/2009 11:32 AM
 

I'll try to explain our IIS setup in full. I have a default website with a virtual directory (DotNetNuke) added as per DNN setup instructions that points to the c:\dotnetnuke folder.

I also have a separate website on the same server that I have called DNNDev; this is bound to IP 192.168.168.16 port 81. Its home directory is pointing at c:\dotnetnuke. We have a whole lot of other websites running on this server too, hence my reluctance to restart IIS earlier!

When I type localhost/dotnetnuke I'm assuming it's the virtual directory on the default website that is taking over, and when I type 192.168.168.16:81 it's the website at that IP. However I wouldn't put any money on it as I'm a novice with all this!

Regards,
John

 
New Post
11/9/2009 11:39 AM
 

Hi Jeff, and thanks for your reply.

I could go back and change to www.domain.com:81 again and try to access the site as you describe, however I can't actually access www.domain.com from the server itself, that only works from external to the firewall. Again I have no idea why this should be but I'd imagine that www.domain.com:81/dotnetnuke would not work either, for the same (unknown to me) reason.

I'll go back and try from outside the firewall, maybe.

 
New Post
11/9/2009 12:14 PM
 

Ok, I think I am getting confused.  So you have a Parent Portal (localhost) and then you have added a child (localhost/dotnetnuke) and one or both are not coming up???

 
I am not quite sure on this, so rather than give advice on your setup I will simple explain how I have done this (parent/child portals) in the past… 
 
First we need to cover the Parent Child dynamic and some pros and cons and different options that are available for a multiple portal setup… 
 
First you need to ask yourself/answer the following question:  Why am I setting up multiple portals?
 
If the answer is: “I have multiple Website that I need to run” then review DNN Setup Options 2 and 3 below.  
 
If the answer is: “I need to have a Parent Child relationship because I am use a module(s) that allows me to push content etc to the child portal and that is what I need” then review DNN Setup Option 1 below.  
 
Likewise, if your answer is: “I want to have a bunch of cheap sites I can resell” then review DNN Setup Option 1 below.
 
Finally, if the answer is: “I want to have a bunch or quality sites I can resell” then review DNN Setup Options 2 and 3 below. 
 
Option 1 :: Parent Child Single Install, Single DB
This option is for use in only two scenarios in my opinion, cheap sites for resell through a single host account OR you have a parent child relationship that requires a single DB/Set of tables.
 
Pros: Easy, Cheap, Quick
Cons: If you have to restore a database you end up rolling all sites back unless you do some serious scripting etc.  Can be a major issue if you stomp another sites data… 
 
Step 1: In this option, you would create a Single Website with the DNN Portal in the root as the parent (i.e. localhost).  Then for each child portal that is a “/something” you create a virtual directory in the parent portal website with the name (something) and point it back to the same installation location.  If you want something.localhost (i.e. support.mysite.com - as I would not recommend actually using something.localhost…) then you can just add this alias to your DNS and then move to the next step.   
 
Step 2: Once you have completed step one, log into the parent portal as Host (or other super user) and go to Host > Portals and configure the new portal using the correct names/paths (i.e. localhost/something OR something.localhost as shown above).
 
Step 3: Browse your new Child Portal!
 
Option 2 :: Portal Using Same Database, Different Physical Install Files
This option is ideal if you need to have a single database, but either wants to have more controlled backup and recovery options in the database etc. 
 
Pros: Still easy and gives better database recovery options
Cons: still shared, can still have DB and other issues (not totally isolated)
 
Step 1: In this option, you would create a first portal (i.e. localhost) and during the install you will specify a unique database object qualifier (unique to each site you want to setup).  Then for each additional portal that is a “/something” you create a virtual directory that points to a new folder with a fresh copy of DNN in it.  If you want something.localhost (i.e. support.mysite.com - as I would not recommend actually using something.localhost…) then you can just add this alias to your DNS, create a new site that points to a new install of DNN.  Then during the install (applies to both options above) you would again select the same database as the first portal and again select a unique database object qualifier (allowing unique table names in the db, but still using the single db). 
 
Step 2: Browse your new Portal!
 
Option 3 :: Fully Isolated Portals Using Separate Installs and Databases
This option is the one I suggest unless there is a very specific reason why you cannot (noted above). 
 
Pros: Everything is isolated; they are separate in every way
Cons: Obviously this one can cause a little more work (then just a DNS entry and a alias) and requires multiple databases etc
 
Step 1: Just create a database, setup and folder for the DNN Files, Setup a website in IIS, browse and follow the prompts… 
 
Step 2: Browse the site
 
I hope the two above mirrors your scenario and give you the info you need.

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
11/9/2009 12:30 PM
 

Robert

Thank you for such a long and detailed message. I am going to have to read it several times to take it all on board. However, in reply to the question "Why am I setting up multiple portals?" the actual answer is "I have no idea, I thought that was the way to do it"!

Our requirement is to rework our company website at www.marketingunity.com into a CMS so that non-technical users can update content as they wish. We're looking at DNN as it's evidently a heavyweight and used by thousands of people successfully. We host the website ourselves and also some ASP web applications for our customers. If DNN needs its own dedicated server/IIS then I guess we're going to have to forget about it as the server I've installed onto is currently running about 10 live web apps. I'd hoped I could install it on there and run alongside our existing website in some way until we had completed the transfer and could switch over to the DNN hosted version.

Having said all that I will study your comments and try to get to grips with it again on Wednesday. Thank you very much for taking the time and trouble to help us out, I really do appreciate it.

Best regards
John

 
New Post
11/9/2009 2:08 PM
 

Ok, in that case just focus on Option 3. 

Here is the Step By Step on how I Setup DNN (I do ALL on the server, now local then push)

  1. Create a New Database in SQL Manager (add a user account that has DBO rights to this DB)
     
  2. Create a Folder under Inetpub (or somewhere else)
     
  3. Extract the DNN Install (not source or upgrade) zip into the Folder 
     
  4. Right Click the Folder, Select Properties and Set the Following Rights
    1. Administrators FC
    2. System FC
    3. Network Service FC
    4. ASPNet (if you have one) FC
    5. Users RX
    6. Everyone RX (optional)
       
  5. Open IIS and Create a New Website Pointing to the Folder with DNN in it.
     
  6. Browse the Website via IIS (expand the website, right click default.aspx, select browse)
     
  7. Follow the Wizard Prompts
     
  8. Enjoy the new Portal

This should get you where you want to be.  


Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Portals and localhostDNN Portals and localhost


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out