Step 1: Download and install Druid packages

Download the latest Druid release packages from Codeplex.

• HyperCrunch Druid (Required)

About: This package provides the core Druid Rule Engine functionality.

Extension Type: DotNetNuke Library

Pre-requisites: ASP.NET 3.5, DotNetNuke 6.x

IMPORTANT: This package modifies your web.config file by adding an HttpModule element. If you prefer to do this manually, you can unzip the package and manually modify web.config as indicated in the manifest (file with .dnn extension).

When this package is successfully installed you will see no difference in the functionality of your site if <compilation debug="false" /> in web.config. If <compilation debug="true" /> you will see debug information similar to the image below at the bottom of every page on the site.

• HyperCrunch Druid Mobile (Optional)

About: This package provides the Druid Mobile App Engine functionality.

Extension Type: DotNetNuke Library

Pre-requisites: ASP.NET 4.0, DotNetNuke 6.x, HyperCrunch Druid

• HyperCrunch Druid Sample (Optional)

Extension Type: DotNetNuke Module

Pre-requisites: ASP.NET 4.0, DotNetNuke 6.x, HyperCrunch Druid, HyperCrunch Druid Mobile

This package is a must-have for developers wishing to learn how to create mobile apps using Druid. It contains the source code for a mobile app built on Druid. You can see the app in action here.

Step 2: Test Druid

Druid looks for a file named "druid.config" in the Portal Home folder (example: ~/Portals/0/druid.config) and in the Host folder (~/Portals/_default/druid.config). The portal file is optional, but the Host file is required (even if there are no rules). Rules from each are combined and then enumerated against each incoming request. (In the future, Druid Studio will enable you to manage rule configuration files with a user interface. For now, you will need to have access to your website's folder on the web server (either through FTP, RDP or hosting control panel) in order to create/edit rule configuration files.)

The first time you load a page on your site after Druid is installed, it automatically creates a "druid.config" file with some sample rules. One of these rules is a test rule to verify that Druid is correctly installed. The rule displays a dialog on the site if the URL contains a querystring variable named "hellodruid" (example: http://www.yoursite.com/Default.aspx?hellodruid=1). 

Once you have installed Druid, test its functionality by navigating to any page of your site and appending "?hellodruid=1" to the URL. If Druid is correctly installed you will see a dialog with the Druid logo.

Congratulations! You have a working Druid installation.

Now learn how you can use it for maximum benefit --

For Portal Administrators: Learn about the Druid Rule Engine

For Developers: Learn about the Druid Mobile App Engine