Today, I am going to describe complete process of
creating a perfect DotNetNuke Environment or say how would you install DNN Site
(whether install or source version). I am going to use most latest and stable
05.04.00 install version of DotNetNuke.
To download the source/install version you need to
have login/account at official DotNetNuke site. Once you login; you would go to
Download page where you can select “Community” Edition to download. There are 2
variations in DotNetNuke that you would find there. One is Community Edition
and other is “Professional” edition. You can install DotNetNuke via downloading
“Microsoft Web Platform Installer” that is available on the same page. This
installer additionally provides you other valuable resources to install as
well. For more information on Web Platform you would get here - http://www.microsoft.com/web/default.aspx,
Otherwise, you may click on the “Older version” link which would redirect you
to the version track page at “Codeplex” site. You would find the total “Release
Track/History” at the right hand side. I have selected most stable install version
to download.
As I requested – I received the download of “DotNetNuke_Community_05.04.00_Install.zip”
file. Once File get downloaded; you copy the zip file and extract at the particular
place where you want to have the DotNetNuke site physical folder. For sake of simplicity,
I have extracted the zip file under c:\inetpub\wwwroot folder.
Please remember that if you are using Source
version and going to develop custom modules on that application than you need
to first keep the “web.config” (or just rename it something like
web.config.backup) file in backup and rename the “release.config” to “web.config”.
Also, remove the source control information from .sln file via opening the .sln
file in notepad and remove/delete the Global…EndGlobal section.
DNN is using some of Telerik Controls. So, just
make sure that Telerik dll (Telerik.Web.UI.dll) is exist in /bin folder. Other
thing to take care is (I don’t know whether they have corrected this one or
not. But, This problem was THERE in version 05.02.00) – if you are using source
version then Telerik dll was not exist in /bin folder and you have to take it
from the install version.
Once you extracted the zip file you need to create
the “Application Pool” (for OS other than XP) and Virtual Directory for the DNN
Site. Just go to the IIS (inetmgr) and create an “Application Pool” which would
target to proper .Net Framework version.
Remember the “Identity” on which Application Pool
will be running on. On my case – It is “NetworkService” Identity. It will be
require when you are giving proper permission to the extracted folder. You can
also change the Identity via “Advance Setting” of Application Pool.
After creating Application Pool – you need to create
Virtual Directory (Create Application..) under default website. Select the
AppPool that you have created for your DNN Site.
You are now done with IIS. Next is you need to
create a blank database and a sql user account in sql server. Go to Sql
Management Studio and Create a blank database as usual. Create one Sql user (or
you may use the existing “sa” account). Make sure that the user account that
you are selecting must have the proper permission to execute on the blank
database that you have created for DNN installation.
You are now done with Creating Database for the
installation. Move to the physical folder and apply proper permission for the
AppPool Identity user (Network Service in my case) as well as IIS user. This is
required otherwise DNN installation wizard would give you error related with
permission.
After giving permission – you are ready to run the
installation wizard and start installing your DNN Site. To start the wizard,
browse thru http://localhost/dotnetnuke/install/installwizard.aspx
and you would serve with below first stage.
On this step, you would find 3 options to install
the DNN Site.
[1] Custom: The
"Custom" installation method provides you with the ability to
completely customize your DotNetNuke installation. Select this option if you
wish to control which optional components get installed
.
[2] Typical: The "Typical"
installation method makes some "typical" choices for you.
[3] Auto: The "Auto"
installation method bypasses the Wizard completely and uses the legacy
Auto-Install procedure.
You can also browse thru http://localhost/dotnetnuke/install/install.aspx
to start the legacy Auto-Install procedure directly.
For sake of simplicity I am selecting most common “Custom”
option and click next.
On this step DNN Installation Wizard would check
the permission set given to the physical folder and would provide you the appropriate
warning information if permission were not applied correctly. Otherwise it
would pass this stage via giving successful message. Click Next.
On this step above – you will be asked to enter
the database information that you have created earlier in this installation
process. Select proper sql databse, server, name of the database (dotnetnuke in
my case) and give the user and password information (by un-checking the “Integrated
Security” Checkbox, because its better not to use windows authentication).
Select “Run as DB Owner” checkbox option and give the “Object Qualifier” you
wish. This Qualifier would be appended to each table, procedure, view etc.. in
the database installation.
Once database get installed successfully, Click
Next. Here you need to configure the “Host” account detail which is the “super
user” account for your DNN site.
Provide proper information for the Host Account.
Remember the password as it will be the super user which will be used to manage
host and portal sites. It’s preferable if you give correct SMTP details because
this way you would able to identify and come to know the correct activity
whenever any new user gets registered, blocked, or deactivated. DNN Site would
shoot email on important activity or action.
Once you are done with the Host Account
configuration, in next few steps you would be asked to select and install:
[1] Option Modules
[2] Skin and Containers
[3] Language Packs
[4] Authentication System (out of Active
Directory, LiveID and OpenID)
[5] Install Providers
You would be given available options in above
steps via checkbox where you can select the options you wish to install with
your DNN installation procedure. If you don’t select anything out of this step;
you can later do that via “Host Menu” > Module Definition > Install
Extension menu option. You would also find the same option from “Host Menu”
> Extension > Install available Extension link at the bottom of the page.
After above all steps get passed; you would come
across below steps where you would configure Admin account just like you did
for Host Account. Give proper information for admin account.
That’s it!! It’s the final stage where you are
just a single click away to your installed DNN Site. Click on “Start Building
Your New Site” and you are presented with the all new fresh DNN site installed.
Well well well, lets move on and play with it J
I hope this would help novice people in
configuring perfect DNN environment.
Here are few notes that are good to know:
[1] You would require installation templates if
you want to create custom DNN Skin or Dynamic/Simple DNN Custom Modules. You
would find these visual studio templates at the official DotNetNuke site
itself.
[2] Once you are done with the site installation
and you redirected to installed DNN site. You may face IIS error saying “The
Web server is configured to not list the contents of this directory” or you can
notice the address of the site in address bar something like http://localhost/dotnetnuke/install/.
In this case only you need to do is > Go to the Database and open the “PortalAlias”
table. You would find the portal alias of the site configured incorrectly. Just
correct it to “localhost/dotnetnuke” instead of “localhost/dotnetnuke/install”.
Reset the IIS (iisreset) or recycle the App Pool and you are Done!.
Have a Nice Day!!