Running the Toolkit Administration Tool
In this section, we will create a database and then take a look around to see how things are placed on the disk.
To create a database, we run the administration tool at
Start | Programs | Community Toolkit | Administration Tool
This is the main start page for the program. There is on-line documentation under Help.
Each database has a Long Name (descriptive) and a short name (used to make files and URLs).
In this example, we set the long name to A Test Library and the short name
To create a database, we press Add Database. After some machinations, it should add
a DSN called ctk_test, a database file called test.mdb,
and four .asp files. As the last step, it will prompt you for an administrator password for the database.
See the help file for more detail on what this tool can do.
To enhance security, the database files are not stored in the web-accessible part of the hierarchy. In this example, we use C:\InetPub\databases\community\ as the directory for the databases. The first database you create will cause the directory to be created. You will not get this prompt for the second and following databases.
There is no reason that all the databases need to be in the same directory.
Please, Please, Please backup this directory
(and when you don't, and you lose the hard disk the data is simply gone)
The last step of database creation is to set the password for the admin account.
You can also use this utility later to reset the admin password or unlock the admin account if too many bad password attempts were done by the admin account.
This is what it should look like when complete. It has added a database, a DSN, and
four ASP files.
The toolkit administration tool actually does some pretty basic things. In a sense
all of its tasks could be done by hand. To help you get an idea of where things are stored (in case you have to do some debugging),
we will look around to see what the tool has actually done.
First we will look for the DSN information. Go to
Start | Settings | Control Panel | ODBC32
Look under System DSN. Select ctk_test and press Configure
to see how the DSN is put together.
A System DSN is basically a mapping from a name to a file on disk with an indication of what drivers to use to access the file. Don't make any changes here - simply notice that the proper file name has been placed here by the administration tool.
If we navigate to C:\InetPub\database\community, we see the test.mdb file. It has the default icon because Access is not installed on our server. If we had Access, we could open and examine the file. Be very careful making modifications to the tables in this database.
A good general rule is never to change the schema and spend most of your time in the Events table. It would be quite natural for you to import events from other sources and place them in the file if you had Access skills. Be very conservative if you do this and test anything very thoroughly.
The administrator tool also created five ASP files in the web server hierarchy. These are the files necessary to set the session variables and launch the proper ASP files to initialize each distinct calendar.
The files in this example are stored in the directory
C:\InetPut\wwwroot\Community\start\. They all appear on
the web server as http://www.blah.net/Community/start/zzz.asp. The files are:
- test.asp - Goes to the main page, giving the user the choice to go into calendar, forums, or administration.
- test-admin.asp - Goes directly to the administration page for the this database
- test-calendar.asp - Goes directly to the calendar for this database using the default view for this database
- test-forum.asp - Goes directly to the forum page for this database
- expire.htm - This is used when the ASP Session variables time-out after 2 minutes. The ASP scripts redirect the user to this file. It contains a very simple index to all of the databases stored on the server. This file is re-built every time you add or remove a database. You can also rebuild the file using the button provided.
You may want to hand edit some of these files. You may want to copy a file to index.asp so there is a default page when the user simply types http://www.blah.net/community/start.
This is the contents of the test.asp. As you can see it is a rather short file, setting some session variables and redirecting the user to another file. The most important value is the ConnectionString value which links this (and other) ASP file(s) to the proper system DSN. It is this value which allows many databases to be used with this software.
If you get tricky (say by trying to use SQL Server), you should only have to edit these files to get the ODBC connection properly set up.
This tutorial walks you through the toolkit administration tool. It does a rather simple but important set of tasks in the overall scheme of things. To run this tool, you must be physically on the server. This is necessary for security reasons.
Up next, we will do a brief walkthrough on using the toolkit software. We will set up a database, enter an event and view the events.