This project is read-only.

Installing the framework

In order to run this example you must have access to an IIS 6 or higher and a SQL Server with a test database.

Alternatively you can use Visual Studio 2008+ since it comes with a light version of IIS and a light version of SQLServer called SQLExpress, just open the project by using "File->Open -> Web Site" and skip step 1.

1 - Installing the Website

Copy the contents of the zip file to a directory, like, for example "C:\Inetpub\IndustrialDashboard"

In IIS 6 create a website or add a virtual directory to an existing one and point it to C:\Inetpub\IndustrialDashboard and, in the virtual directory properties, select "Create Application".
Check that ASP.NET version is 2.00 or higher and check that "Web Service Extensions" folder has "ASP.NET v2.0x" and "Active Server Pages" allowed.


Make sure that Authentication Mode in IIS6 is either Windows or Anonymous and that the web.config Authentication section matches this.

In IIS7 create a website or add an application to an existing one and point it to C:\Inetpub\IndustrialDashboard.
Also in IIS7 in order to serve .json files (for the non-database samples) you need to define a new MIME type .json -> application/json. Check that ASP.NET version is 2.00 or higher

In some installations we encountered some permissions problems that we solved by changing the Application Pool of the application

2 - Create sample data and procedures

You will also need to have a running SQL Server and execute the Samples\sample.sql script on a test database called IndustrialDashboard.

If you don't have SQL Server Management studio you might need to use the provided utility osql.exe.

osql.exe -E -S localhost\SQLEXPRESS -d IndustrialDashboard -i sample.sql
The default name of the test database is IndustrialDashboard and is specified in the first line of sample.sql, if you want to use a different database just edit that line and on the next step change the connection string accordingly. The script will create a few tables and stored procedures.

3 - Modifying the connection string

You'll need to modify the connection string in the web.config to match the database created in step 2, below is an example of how it looks like:

		<add name="IndustrialDashboard" 
		connectionString="Data Source=Host\ServerInstance;Initial Catalog=Database;Integrated Security=SSPI;"

Host : Is the computer name of the server where SQL Server is installed, it can be an IP address or simply "localhost"

ServerInstance: If If the SQL Server instance is named, you'll need to specify its name. If you use Visual Studio the instance name would be SQLEXPRESS.

Database:The name of the database where the procedures are stored

4 - Give the application write permissions on Logs directory

The system writes debugging and audit information to logs files using the standard log4net library. In order to make it work the library needs to have write access to the /Logs directory. The location of the Logs directory can be changed in the web.config if needed.

We need to give the application user, usually ASPNET (IIS 6) or IIS_IUSRS (IIS7) permissions to this directory. Right click on the Logs directory and look for Properties->Security to include the application user and give it write permission.

5 - Create Login in SQL and give execute permissions

The best method to authenticate with the database is to use Integrated Security, this will require creating the proper Login (IIS_IUSR or ASPNET) in the SQL Server, create the corresponding user on the sample database and assign the owner role to it (only because this is a test database). When working with your own actual data refer to the Security documentation page to tighten the security and enable only execute permissions to selected stored procedures.

The Log files (located in the directory Logs) will help determine what can be failing if the database can not be accessed.

Additional Information
How to create a Login
How to create a Database User

6 - Checking that everything is installed OK

Open your preferred browser (IE7+, Opera, Chrome , FF) and point to the virtual directory you just created in step 1 : http://localhost/IndustrialDashboard/default.htm and you should see the default.htm page that shows some of the demos installed

7 - Troubleshooting

- Start by looking at the log files (inside the Logs directory)
- If the log file is not being updated, browse the following url: http://yourserver/Industrialdashboard/DALService.svc, the response should be EndPoint Not Defined, if there is an error and you open the url in the server's browser you'll get a detailed response.
- http://yourserver/Industrialdashboard/DALService.svc/CallProcedure might also give you some hints.

Last edited Oct 7, 2010 at 4:42 PM by jcastagnino, version 14


No comments yet.