I have a large client that has many smaller companies. I've been setting up the smaller companies with seperate DNN sites and databases. My thoughts are that I'm completely missing the power of the option for parent portals and using one database for this scenario. Can any of you confirm whether doing this is a good idea?

Now the second part.. pending that is a good idea,

I've been completely unsuccessful with creating a parent portal. Child portals work fine but apparently I am missing a step on the parent portal as the alias I put never works.

Would someone be so kinda as to give me a complete idiots instruction on how to make a new parent portal work please. I know how to add it in the host interface, it's the part after it is created that is killing me. The alias I put is not working, I'm assuming I'm supposed to put a physical directory in the IIS server or something? The book and documentation didn't convey any of that to me.

thanks in advance.

 

 

Hello,

This is a good question. There are pros and cons for each method.

Creating a separate installation for each smaller company has the advantage that it is a completely separate installation and if something becomes corrupt on one of your other installations, your site will be fine. If you want to backup and re-install just one company you can also do this easily.

If you create portals you only have 1 installation to look after, so for each portal you create all of your modules / skins are available to all of the other portals.

To backup, you only have to look after one database, so you may think this is easier to maintain.

So both methods have their pros and cons.

For a parent portal, set it up in DNN exactly how you would with a child portal. - The next part is that you need to get your domain name to point to your DNN installation.

- You do this in exactly the same way as you do for any other domain when creating a new installation. Just point the new domain to your DNN installation  folder. - If you are having problems ask support from your hosting provider as they should be able to give you the exact details you need for your setup.

Hope this helps, thanks,

Some hosting providers intervene in the domain name resolution process and require that their server also be told what DNN install is going to receive the domain name request.

Then after the request arrives, the DNNuke install itself again resolves the domain name to select the correct portal. It is handled twice at different times. Both will need to be set up correctly for it all to work.

(not to mention the Domain Registrars DNServer setting if you are using a separate domain registration origanization like Network Solutions or 1and1. who are not actually hosting your DNNuke installs.)