Dot Net Nuke Installation on the Cloud

GoGrid Account Sign-up and Login

Please don't re-use the same password that you provide to ANY other website. People you don't know are literally staying up at night trying to get information and destroy you. Once a hacker figures out your password, it only takes seconds to delete all your servers on GoGrid.
Generate a strong, long password using a passphrase.
Don't worry that you won't remember a random set of 32 characters in upper and lower case and with special characters.
Just copy and paste the password and your browser will remember it for you.
In case you forget or clear your cache (whatever comes first), plug in a removeable USB drive, open up Notepad, copy the account name, the passphrase you used to generate the password, and the password change the font to 32 points, put spaces between each character (because w and vv look the same), then print out 2 copies and put them with the USB drive in your fire-proof safe.
I say 2 copies because when you take one out of that safe, you may not remember to put it back.
Saying "I'll just take it out for a minute and put it right back" is easier said than done.

Login and Adding Servers

Click the Add near the left center of the page.

Architecture Diagram

This page describes this diagram of how DNN operates with different cloud services.

Adding Servers

Instances with "SQL Express" do not require a separate database for development or simple web sites because

Access Sqlexpress on a remote box only after enabling remote connection for Express.

Each server costs a minium of $2 per day. This is because charges apply whether or not the web server is being used.

Within HTML, specifying the SRC of images from another domain than HTML text yields faster load times for visitors.
But GoGrid's cloud doesn't serve files to the public. For that you'd have to use Amazon EC2, where ASP.NET 3.5 is run within a Mono emulator over a Linux OS.
Unlike ThePlanet, which co-locates servers around the world, GoGrid is currently in only in San Francisco (earthquake country).

How Much RAM?

Many people mistakenly think that because a cloud offers "infinite" capacity, no thought is needed about performance or capacity.

But the reality is that GoGrid offers the same machines, just a lot of them and quicker. there is a price to how fast and how much capacity each server holds.

Some have noticed that servers running on GoGrid seem slower. But we dont' know really why.

It also takes a certain amount of time to install and configure a server after GoGrid configures it.

Peformance Benchmarks

I (Wilson Mar) am performing several benchmark runs using "representative" DNN transactions at various sizes of accumulated data.

For realism, I am looking for sample databases to use. So let me know.

I aim to refine my approach as I go such that the performance of services on GoGrid can be compared over time and against other providers (Amazon, Google Grid, Force.com, etc.).

If you'd like to compare speeds with what you're achieving in your environment, let me know!

How Many Servers?

How many servers to activate for your app depends on the combination of several metrics:

How much throughput can an individual server provide?
The impact of using different among of RAM.
The impact of using different operating systems (Windows 2005 vs. 2008 server).
The impact of using different images (with IIS+ASP.NET or not).
The amount of traffic (Hits per second) flowing through the system.

Please leave a comment below or email me on this about your experience.

I'm working on a Capacity Plan for the DNN Database.

Load Balancer Distributing Load

In order to serve more traffic than a single front end web server ("web-head") can handle and to allow a web server to be removed from service without interrupting service for web users browsing the sites, the IIS website root directories of each server in a web farm are mapped to a common UNC share on a remote file server (NAS or SAN) containing the application source code as well as any static content for the individual sites. Additionally, web servers connect to a database server for dynamic application content.

Getting In Windows Servers Using Remote Desktop

GoGrid Windows servers are reached from Windows client machines (such as Windows XP or Vista) using Remote Desktop Connection (RDP) (rather than SHH on Linux machines).

On your Dev. client machine, click Windows Start and type in the "Start Search" field mstsc, Press Enter. This file is in %SystemRoot%\system32\mstsc.exe.

Subsequently, Windows shows Remote Desktop Connection in the list when Start is clicked.

Passwords for GoGrid's servers are shown by clicking Support at the top, then Passwords on the top left tab.

Passwords for GoGrid's servers cannot be copied so they can be pasted in the login form.
By default, RDP displays remote desktops on full screen mode such that your keyboard is only for that session.
To use Ctrl+Tab to switch between the GoGrid password page and the RDP Login page, click on the yellow bar RDP at the top middle to "Restore Down" icon.
"vv" looks the same as "w".

If this doesn't work, your corporate firewall may be blocking the special default port 3389 RDC uses.

This is

Here are what my automation scripts do to get GoGrid app servers configured the way I like to run DotNetNuke:

The first time the server appears, check "Do not show this window at logon" and click "Close".
Wait a minute for the Server Manager to appear, then click "Close"
Click the Windows Start icon and double-click Computer for the Windows Explorer.
Click Tools > Folder Options > View tab, uncheck "Hide extensions for known file types". Check "Restore previous folder windows at logon". Click "OK".

Domain Name and SSL Certificates

If you plan on doing e-commerce (or care about data security), you will need an SSL certificate for each server. A SSL certificate needs to be purchased for each domain name so that the HTTPS can be used on your site.

I recommend getting sub-domain names such as "mail.mysite.com" for email. This provides you more flexibility in managing server traffic, capacity, and security.

Most large companies also purchase the Top-Level names (.com, .net, .info, .ws, etc.), even country suffixes (such as .de for Germany, etc.)

You then specify to the Registrar's DNS the IP used by a server at GoGrid.

GoGrid automatically assigns each account a "C" range of IP addresses.

The ".1" IP in the range is not listed because that's the Gateway address (specified when setting up a connection to the GoGrid Cloud).

If you have more than one server and a load balancer installed, specify the load balancer's Virtual IP (VIP) address.

Email

GoGrid doesn't want to enable spammers to spam people from their servers.
So GoGrid blocks SMTP traffic by default.

However, since emails are a key part of many applications:

Create a support case at GoGrid asking to enable SMTP.

Go to where you obtained your host name (e.g., GoDaddy) and request:
- A reverse DNS (rDNS) for your email IP to that sub-domain or domain.
Do all this before creating a support case at GoGrid asking to enable SMTP, becaues they will ask you.
GoGrid will also ask the volume of emails expected in/out of your servers.

File Transfers

By default. GoGrid does not enable an FTP service on its servers (largely because they transmit user names and passwords in clear text for anyone to see). So there is no easy way to get files out of the app serve (which is what we want for security reasons).

FTP get can be typed in from the Run command-line interface to retrieve files.

Internet Explorer is available on each server, so you can address it to a webpage where you can click a download link.

This means that development software (Visual Studio) must be installed and run on a GoGrid server vis Remote Desktop (which times out, etc.).
To get files into (but not out of) servers, use IE to download a FTP client such as FileZilla

To get files into and out of the Grid within GoGrid from a server (but not from outside) use either FTP, SCP, or create a network share on the server server. This is unlike Amazon, which offers its cloud to the public internet.

Once generic install files are on one server, copy them to the GoGrid Cloud so that they can be transferred into subsequent new servers. That's what's it's there for.

(As of June 1, 2009) GoGrid does not provide for custom server images. So each server must be established with software and configured before use, which can take a lot of time or a lot of automation. This issue has been posted to the DNN Discussion Forum.
GoGrid's web servers only contain a single hard drive. It would have been better if two are provided (for logs to be written more efficiently).
I recommend the same file folder hierarchy be used on all machines and in the could so that all assets have a designated home.

File Folders

If you install DotNetNuke in the root directory, other .NET applications may fail.

root

DNN3 Training

As with all valuable software developed, assets created for one version need to go through some transformation before being usable in a new version. (which is the reason for having different versions)
For a two-way reference, "Test", "Training", and "Prod" should be added to denote the name of the virtual directory such as "http://localhost/training".

DDN Installer Download

Download the zip file into the appropriate "DNNx" folder (where "x" is replaced with the version number).
This way, when you extract it, the folder created will match.
To download from a browser, type in Address: dotnetnuke.com
- At the Information Bar confirmation, check "Don't show this message again" and Click "Close".
- Click the "X" to the right of the yellow "ActiveX controls" warning.
Login or Register.
At the Security Alert pop-up, check "In the future, do not show this warning" and click "OK".
Add to the Enhanced Security Configuration pop-up URL "https://www.dotnetnuke.com".
If you choose Live ID, also all URL "http://login.live.com".
Scroll down the page or press the "Download" icon on the web page.
Click on the "Professional" or "Community Edition" from URL "http://dotnetnuke.codeplex.com".
(This uses "http://m.webtrends.com")
If you get the pop-up error "Your current security settings do not allow this file to be downloaded." you may have to obtain the file another way (such as via FTP).

Download Custom Files

The Core Mods folder would contain files which replace or add to the folder structure of the default DNN install.

In the root (where web.config also resides) create an app_offline.htm to display to users when the website is down.
The app_offiline.htm is shown instead of the "This site is unavailable" displayed by the UnderConstruction.htm file in the DNN default Install folder. DNN dislays this page automatically during upgrades.
Copy in custom work in a zip files stored in the Install folder so that they can be installed once DNN is up (by invoking URL http:// ... /Install/Install.aspx?mode=InstallResources).
This converts html files into .ascx files and copies skins into the Portal/_default/Skins folder.
Changes to core code is necessary in order to use standards-compliant CSS coded to automatically adjust for mobile and large personal computer screens.

File Permissions

Those hosting on a 3rd party data center usually need to make a request to reset permissions on folders.

If you have total admin control (such as on GoGrid web servers), you can/need to set file permissions yourself.

Within Windows Explorer, to change file permissions:
Right-click on the file, Security tab. Click the "Edit" button, then "Add" and specify the following before clicking "Check Name".
Copying files into a folder changes permissions. To reset permissions,
uncheck and re-check the "Full Control" permission for the file.

NOTE: Setting permissions on the parent folder before creating any file under it propagates to child folders and files and you'll never have to worry about it.

On Windows 2003, add NETWORK SERVICE. (Previously on IIS5 the ASPNET server machine account was added).

Check "Full Control" (to Allow Modify, Read & Execute, List Folder Contents, Read, Write.)

Click "OK" to dismiss the pop-up.

Also, within Windows Explorer, highlight the folder and select Tools > Folder Options, View tab. Scroll down to uncheck "Use simple file sharing".

Virtual Directories

Add a virtual directory by running inetmgr to open IIS Manager (going to folder properties "Web Sharing" tab).
Click "View Virtual Directories" > "Add Virtual Directory".

Permissions in machine.config

Trust levels need to be change from from default because:

DNN cannot run in low trust because it needs SQL client.
Full trust is needed if DNN is run using OLEDB sources such as MS/Access.

To make this change within the machine.config file.

If machine.config contains allowOverride="false" (which stops individual web.config file overriding on shared host machines), the change cannot be made.

Otherwise, uncomment <trust level="Medium">. This overrides permission levels granted by the <SecurityPolicy> <trust> at systemroot/Microsoft.NET/Framework/versionNumber/CONFIG.

Database and Web.Config

As with any ASP.NET web application, the web.config XML file for each application contains configuration settings such as:

connection strings ( SiteSqlServer )
machine keys ( validationKey and decryptionKey )
objectQualifier (custom prefix to each database table name)

Each new DNN installer also comes with a release.config file which is merged into localized settings in the existing web.config file.

Within Windows Explorer copy file Web.config to make a copy.
Using Notepad or other text editor, edit file Web.config. Do not use the ASP.NET Configuration Tool to edit this file will result in the addition of a line at the top of the file that caused DNN4 to fail installation.

There are TWO places to specify the database each DNN application server references.

    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      providerName="System.Data.SqlClient" />
	</connectionStrings>
	<appSettings>
		<!-- Connection String for SQL Server 2005 Express - 

kept for backwards compatability - legacy modules -->
	<add
		  name="SiteSqlServer"
		  connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
		  providerName="System.Data.SqlClient" />
		<!-- Connection String for SQL Server 2000/2005
    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      providerName="System.Data.SqlClient" />
   -->

NOTICE: The string specifying SQL Server 2005 Express is not commented out, but specs for SQL Server are commented out.

KEY: There can only be one "SiteSqlServer" entry!

If using SQL Server Express 2005 database, nothing needs to be done because it doesn't have the user controls of SQL Server.

If using SQL Server:

Comment out the string for SQL Express
Uncomment the string below "SQL Server 2000/2005".
Within connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
- Change "(local)" to the name of your server (copied from Start > right-click Computer Properties).
When an application presents credentials to connect to databases, it is industry best security practice for application software to NOT use the "sa" (System Administor) account which has unlimited priviledges.
Instead, create a new "service account" related to the web application and grant it only what it needs to support a specific application.

In Start > All Programs > Microsoft SQL Server 2005/2008 > SQL Server Management Studio, connect to server as Administrator.
In the Object Explorer, right-click on "Databases" to "Add New Database", and type in a name such as "DotNetNuke_Community_04.09.04_Prod1" which matches the folder name of the app which references this database.
Specify the Initial Size and Autogrowth parameters according to the capacity plan for the database. Click "Add" to add additional files if it's part of the plan. click "OK".
In the Object Explorer, expand "Security", right-click Logins to select New Login.
Specify the service account login (such as "DotNetNuker1") after the TWO "uid=" markers in the web.config file, then press Ctrl+Esc and paste it in the SQL Server dialog.
Specify the Password (such as "DotNetNuker1rocks") after the TWO "pwd=" markers in the web.config file, then press Ctrl+Esc and paste it in the SQL Server dialog.
Uncheck "Enforce password policy".
Specify the DNN database (such as "DotNetNuke_Community_04.09.04_Prod1" from above).
Right-click on the new user to select Properties.
Click "User Mapping" and in the Map column check the database (such as "DotNetNuke_Community_04.09.04_Prod1").
Check "db_owner" in the "Database role membership" list.
Click "OK" to exit.

This page notes that the <appSettings> element is maintained for backwart compatibility for DNN modules versions prior to 2.0.

Hosted Database Config

If you are operting in a hosted environment, hosting admins usually are the ones to run Member Role install scripts against the database before DNN installation occurs.

This means that the web.config InstallMemberRole setting should be changed to "False".

Other Web.Config Settings

While you have the web.config file open, there are a few other settings.

To have the application show a custom error page rather than the techy .NET defaul page so common to the internet now,

add this line within the web.config <system.web> section
<customErrors mode="RemoteOnly" defaultRedirect="customepage.htm"/>

The <system.web> section also defines where the sectionGroups above will be implemeted.

In the <appSettings> section, avoid unintended upgrades by setting from default "true" to
<add key="AutoUpgrade" value="false"/>

Deployment

Assets for each website are contained in a .zip file. Within this are packages created, packaged, and deployed independently:

skins.zip holds an About.htm file describing that skin.
containers.zip holds the Actions control which ties content module functionality to the portal framework by exposing content module functionality.

These are referenced by Pane level skinning specs.

DNS Entry

Go to whoever registered your domain name and set their DNS to point to GoGrid's DNS servers.

Run Cmd "ipconfig /all" to see GoGrid's DNS server IPs.

Modules - Extensions - Plug-ins - Add-ons

Automatic installation of Modules occur from a binary .resource file for each module in folder Install\Module when the "Install Additional Extensions" link is clicked.

Notice that each module has its own version number.

TIP: Rename .resource to .zip and the module can be installed manually by clicking the "Install New Module" link.

Backup and Recovery

One of the great things about a cloud service is that servers can be created easily.

So now we don't have any good excuse to verify that our backup files can indeed be restored to another server ... quickly.

Many astute customers now ask for proof that this can be done. This is a key part of "disaster recovery planning".

As of this writing, GoGrid has not automated the start-up of entire servers. So a lot of the backup and restore is manual at this point.

Reference

This page was created to present informaton on these pages in an updated, more concise way.

How to Install DotNetNuke 4.3.x from DNN Creative magazine

DNN Installation on the Cloud