Minimum Requirements
Thin-client architecture *
Internet Information Server (IIS) & MS .NET Framework 2.0
Browser: MS Internet Explorer 5+
* Thin-client computing refers to multi-tier client
server paradigm where the client (end-user) programs
display in a browser (such as Internet Explorer or Netscape)
but the execution of that user code takes place on a central
web server, not at the desktop PC.
Note - the .NET Data OLE DB Provider requires Microsoft
Data Access Components (MDAC) version 2.6 or later.
Windows 2000 Server SP3 only installs the MDAC
version 2.53.6200. Please visit Microsoft support
website for more details.
About deployment:
-----------------
Deployment is the process of taking the application and installing it in on another machine.
Please note, Scheduling Manager is web based software, developed in ASP.NET.
Deploying ASP.NET applications is very straightforward. You need to copy the application files
you have extracted from our reservenet.exe to the production Web server that will host your application.
Before looking at the different steps involved in deploying our Scheduling Manager Web application,
it is important to understand the Structure of an ASP.NET Web Application.
An ASP.NET application consists of all the Web pages (.aspx and HTML files), handlers, modules,
executable code, and other files (such as images and configuration files) that can be invoked
from a virtual directory and its subdirectories on a Web server.
An ASP.NET application also includes the compiled assembly (the code-behind, .aspx files)
and typically other assemblies that are used to provide functionality for the application. These assemblies
are located in the bin directory underneath the virtual directory of the application.
The assemblies are so comprehensive and self-describing that ASP.NET applications don't need to be registered
with registry.
This means that ASP.NET applications can be installed by simply copying the required files to the target
machine as long as the target machine has the .NET Framework installed.
Scheduling Manager on the Web - Installation Instructions
---------------------------------------------------------
Only 3 steps are required to install the Scheduling Manager.
1. Extract and copy the Scheduling Manager directory to the server.
2. Set the Scheduling Manager directory as virtual rooted application's directory.
3. Modify the Web.Config file so that it contains a valid connection string to your database.
Step 1
Extract the files from Schedulesetup.exe file, supplied by Infocode,
onto your hard disk. The "reservenet" directory with some
subdirectories and files will be created.
Please note, this installation does not provide any component installation on the server.
Copy "reservenet" directory (with all subdirectories and files )
to the MS Internet Information Server (IIS).
Do Step 2 & 3 if you are Webmaster otherwise do Step 4.
Step 2
Set the "reservenet" directory as virtual rooted application's directory.
Walkthrough: Creating an ASP.NET Web Application Root Directory with IIS - visit MS website:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwalkthroughcreatingaspnetwebapplicationrootdirectorywithiis.asp
Please note, the bin directory contains assemblies
(compiled .dll files) that are local to the application.
None of these files need to be registered.
Grant ASP.NET write access to the files - rrinfoitems.xml and rrinfoitems.mdb in subdirectory "database".
Note, if you located database rrinfoitems.mdb to a different directory, grant ASP.NET write access to the database in your directory.
And write access to a directory "excelreports".
To grant ASP.NET write access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab.
Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
Step 3
Update the source path to the database in web.config file.
Use Notepad to open the web.config file in the "reservenet" directory.
Find in Application settings the key name "Connectionstringrritemsole".
Please change the source path to the database "rrinfoitems.mdb"
to that on your server and save the file, close the notepad.
Please remember, an ASPNET user was created when the .NET Framework
was installed. This user needs "Write" permission for the database
directory.
Continue with step 5.
Step 4
If you have any concerns, request the webmaster do it all for you.
Do this if you are not the webmaster - request the following actions from your ISP's webmaster.
a. set the "reservenet" directory as virtual rooted application's directory.
b. check the permissions (write) on the database and on the reservenet directory.
c. request for full source path to the database.
You need to know the full source path to your database ( ?\reservenet\database\rrinfoitems.mdb)
and the webmaster can give it to you.
Where "?" is, there is the missing path name.
EXAMPLE ONLY, say your website address is http://www.mywebsite.com,
the full path will look like this:
g:\inetpub\mywebsite\reservenet\database\rrinfoitems.mdb
Wait until the Webmaster confirms requests a, b and c under step 4 are done
and then do the following.
Use Notepad to open the web.config file in the "reservenet" directory
on your PC hard drive.
Find in Application settings the key name "Connectionstringrritemsole".
Please change the source path to the database "rrinfoitems.mdb"
to that on your server and save the file, close the notepad.
Copy this updated "web.config" file from your PC to the "reservenet" directory
on your web site and replace it with the original one.
With the above example, new connection string would look like this: