Scotland Yard Web Edition Installation Guide
System Requirements
Windows 2003 Server or newer, or a dedicated workstation running Windows XP or newer.
Microsoft .Net Framework 2.x or greater.
Microsoft SQL Server: One of the following is required: SQL Server 2005, SQL Server 2005 Express, SQL Server 2008, or SQL Server 2008 Express. (Note: SQL Server Express editions are free downloads from Microsoft.com).
IIS 5.1 or greater.
Step 1: Create a virtual web site or default web site on your Server
Using IIS on your server create a virtual web site for Scotland Yard. If no other web sites are going to be run on the target server, you can use the default web site.
Step 2: Unzip the syWeb.zip file to your web site folder
The syWeb.zip file contains the web client software and the server software (web service). They both can run in the same folder and for simplicity we
have included them together. Unzip all contents of the syWeb.zip file to the web server folder you created in Step 1. Also included in the zip file
is the scotlandyard.bak file which is the Scotland Yard SQL database backup which you will restore into SQL Enterprize Manager in Step 4.
Step 3: Modify the web.config and config.xml configuration files
The web.config file is used by the server software web service to connect to the SQL data file. The config.xml file is used by the Scotland Yard Web Client and will
contain the URL of your web site.
| File Name |
Description |
| web.config |
.Net configuration file for the web services |
| config.xml |
Configuration file for the client web software |
Step 1: Modify the web.config configuration file.
In the folder where Scotland Yard Web Edition was installed, modify the "connectionString" in the
web.config file. The
web.config file will looks like this:
Use WordPad or an XML editor to edit the file. Change the SERVERNAME to the name of your server that is running SQL Server. Most of the time this may be the same server name as the name of the server where Scotland Yard is installed.
If needed, modify the Integrated Security section to meet your server requirements, including changing it to user name / password.
Step 2: Modify the config.xml configuration file
In the folder where Scotland Yard Web Edition was installed, modify the
config.xml file.
The
config.xml file will looks like this:
Use WordPad or an XML editor to edit the file. Change the "http://192.168.200.104/sy.asmx?WDSL" to the URL of your server that the employee's will be accessing. Do not make the URL "localhost" as this will not work from employee's workstations.
Examples:
webServiceURL value="http://intranet.mycompany.com/scotlandyard/sy.asmx?WSDL"
webServiceURL value="http://192.168.100.101/sy.asmx?WSDL"
After you make the change to the config.xml, cut and paste the value settings (i.e. http://192.168.100.101/sy.asmx?WSDL) into a browser window.
If the Scotland Yard web service page is displayed, you will know that the
config.xml file should be setup correctly.
Step 4: SQL Database setup and Configuration
Step 1: Create the ScotlandYard database in SQL
The Scotland Yard SQL database backup file is included in the syWeb.zip file and will be located where you installed the Scotland Yard files.
The Scotland Yard SQL database file name is
ScotlandYard.bak
Run Micrsoft SQL Management Studio (or the Express version) and create a new database name
ScotlandYard (no spaces in the name). Then select the menu choice Tasks, then Restore, Database....
On the restore form, select "To Database: ScotlandYard". Select "from device" and then browse to the
ScotlandYard.bak file.
The Scotland Yard SQL database will be restored (imported) to your server. It already contains sample data to get your started.
Step 2: Add user access rights to the ScotlandYard database.
Depending on your MS SQL security settings, you may need to assign specific access rights to the Scotland Yard database. See the "
Test Scotland Yard Web Services and Database" below.
If the test succeeds, then you do not need to this step (step 2).
With Microsoft SQL Management Studio still open, we now need to assign the necessary security access to the
ScotlandYard database.
If using "Integrated Security" (our recommendation) for the SQL Connection, then we need to make sure MS SQL allows the
NT AUTHORITY\NETWORK SERVICE user to access the ScotlandYard database.
Follow these steps:
Step 5: Test Scotland Yard Web Services and Database
The following test should be run from the server. Although the web service will be accessible from client workstations your server security settings
will disable the web service "invoke" option which we will need to initially test the web service.
- Open a Web Browser on the server and enter in the URL of the location of the sy.asmx file. This is the connection string parameter in the web.config file you
edited earlier (minus the ?WSDL extention. Examples:
http://intranet.mycompany.com/scotlandyard/sy.asmx
http://192.168.100.101/sy.asmx
- Click on the validateUser method
- Fill out the validateUser form with "demo@demo.com" and "demo" for the LoginEmail and Password.
- Press the invoke button. If data is returned then you know everything is setup correctly.
This is what you should see when the validateUser method is selected:
After pressing the "invoke" button, this is the exepected result to be displayed in another web browser window:
If you get an error after pressing the "invoke" button either the connection string in the web.config is incorrect or you need to add
"NT AUTHORITY\NETWORK SERVICE" user access as documented above in
Step 4.
How to run Scotland Yard
The ScotlandYard database is pre-populated with a sample set of employees.
To run Scotland Yard, run your browser application, then select the IP Address or URL with "scotlandyard.html".
Examples:
http://intranet.mycompany.com/scotlandyard/scotlandyard.html
http://sy.company.com/scotlandyard.html
To login, use the demo employee account information:
Login email: demo@demo.com
password: demo
After logging in, you may customize the departments, status codes, and employees.
Be sure to add additional users with Employee Administration rights before deleting the demo@demo.com user.