|
| Installer screen | Instructions |
|---|---|
1.  |
Click Next to proceed. |
2.  |
Read the license. You may also read or print it by going to the
MWeb License page.
When you have read the license, click I Agree. |
3.  |
The exact wording of this screen depends on what components you purchased, either Express Installation, Install Main Module, or Install Database Connector. Express Installation installs all MWeb components onto this server. The other two must be installed separately.
If you are installing Database Connectors on more than one server, you will run that installation program on EACH server. Click Next to proceed. |
4.  |
This is the location where MWeb will be installed. You may choose another location by clicking the Browse button. Write down the location before clicking Next to proceed.
|
5.  |
Here is where you enter the Project and Database codes. These should be short, as they are used to make folder names and URLs. These codes are not displayed to users.
For Express Installation we recommend the defaults shown. However, for multiple Databases, give each one a unique Code. Write down the codes before clicking Install to proceed.
|
6.  |
When you see this display, the installation program is creating directories, copying files, and adding the virtual directories to IIS.
During the process, or at the end, messages may be shown about problems the installation program encountered. It is always safe to re-run the installation program. Therefore if you see a message like "Could not configure IIS ...", try that first. You may save yourself having to do manual configuration. If you see a message like "... already exists in IIS ...", then IIS already has a virtual directory with the name that MWeb was planning to use. MWeb creates names based on the Project and Database Codes you entered in the previous step. Unfortunately the installer cannot go back at this point, so do one of these two things: delete the IIS virtual directories if they are no longer needed and rerun the installer; or rerun the installer choosing a different Project or Database Code. |
For Windows Server 2003, the default security does not allow executable programs to run. This needs to be modified:
You must allow the Database Server(s) to accept long URLs. For some MWeb requests, the URL may be 500 characters long or more. If you do not do this, your users will get a 408 message (server timeout) if the URL is longer than allowed.
MWeb Enterprise Databases, Relational Databases, and PastPerfect Export Databases: If your Database uses FoxPro tables, the Microsoft Visual FoxPro ODBC driver requires permissions to write and then delete temporary files. Add these permissions as follows:
The Database(s) to be used by MWeb must be on the server. Please put them there now if they are not already there. Since every Database is different, the installer cannot do this. For some types of database (SQL Server, Oracle, etc.) this may be a complex installation that a technician should do.
A MARC Database is one or more files in the same format and in the same encoding. Simply copy the files to the server. Configuration will be easier if they are all in the same folder, but this is not required. Skip to Installing MARC Databases.
The PastPerfect-Online User's GuideThe PastPerfect-Online User's Guide was written assuming that your database would be hosted on the PastPerfect server. Therefore you may skip some parts of the Guide. Here is what you need to know:
|
| Note: Mapping is performed only the first time you load data from PastPerfect. To make changes to the mapping after the initial load of your data, use MWeb Universal. |
For a PastPerfect Export Database the Database consists of a set of FoxPro tables created by running the web-export wizard from PastPerfect. For help with this process, see the PastPerfect Online User's Guide you received when you purchased the PastPerfect-Online module (more information in the box to the right).
We regret we cannot help with installing databases and database software on your servers except on a consulting basis. It requires specialized knowledge for each database vendor.
The Database Connectors use Open Database Connectivity (ODBC) to access the Database(s) in your Project. This is a nearly universal approach to accessing data. ODBC requires an "ODBC driver", which is just a program developed for data access. In nearly all cases, the vendor of your database software (Microsoft, Oracle, MySQL, IBM, etc.) provides an ODBC driver with the database software.
If the Database already has an ODBC Data Source on the server, you may skip this step, but write down the Data-Source Name.
Each ODBC driver is slightly different. We regret we cannot help with the details of installing and configuring ODBC drivers, except on a consulting basis. However, here are the general steps:
Using the ODBC Administrator on the server, create a "System DSN" as follows:
For PastPerfect Export Databases, click the Free tables radio button.
For Microsoft Visual FoxPro databases, click Options and un-check Fetch data in background.
For Oracle databases, end the Data Source Name with an underscore and the schema name, such as "MWEB_ORACLE_HR", where "HR" is the schema name. Enter both the user ID and password in the User ID box, separated by a slash, such as "joe/Gdk45". If you prefer, you may add the password to the Windows Registry instead. You may set the Data Source to "read-only" for safety, since MWeb does not alter the Oracle database.
For SQL Server databases, after you set up the Data Source, use the SQL Server administration interface to add the IUSR to the valid users of the database. Only the db_datareader and db_datawrite roles are required for this user.
You may now close the ODBC Administrator.
For MARC Databases, it is required that the images be referenced by a complete URL in the 856$u. Therefore, install the images to the locations specified in the 856$u subfields.
Install images by copying them to the udcimages folder on the server, which was created by the MWeb installation program.
Install images by copying them to the udcimages folder on the server, which was created by the MWeb installation program. For PastPerfect Export Databases, image access is configured by the wizard if your images are stored in sub-folders under udcimages like this:
| Images | /udcimages/001/imagefile.jpg |
|---|---|
| Thumbnails | /udcimages/001/thumbs/imagefile.jpg |
You may also have multiple levels of sub-folders in the path, like this:
| Images | /udcimages/objects/gifts/imagefile.jpg |
|---|---|
| Thumbnails | /udcimages/objects/gifts/thumbs/imagefile.jpg |
If you wish to do things differently, you will need to see Databases with Images after you have completed the rest of Project Setup.
Congratulations! The worst is over. There are just a few more steps before you can use your MWeb site.
Before proceeding, you must allow MWeb to set cookies. Cookies are used to store the permissions, last query, and other information. Cookies are not saved between logons.
During installation you assigned your Project a Project Code and its Database a Database Code. In our example we use the defaults: Project Code "Uni" and Database code "UDC".
To begin, in your browser, go to the following address, substituting your domain for www.example.org, and changing "uni" if you changed the default Project Code during installation:
Click images for larger view
http://www.example.org/uni/
(Note that Windows servers are not case-sensitive.) If the installation was successful you will see a display titled "MWeb Universal New Project".
You will be asked provide the following Project-related information:
| Project Name | This will be the name of the Project used as the header of each display, and also as the title in each browser window. (You can change these two independently later.) |
|---|---|
| An Administrator user ID and password |
This will be the ID of the Project Owner. This user will have the highest level of privilege, including the ability to change search parameters, add other users, and generally control the system. Memorize this ID and the password, or write them down and keep them in a safe place. (If you lose your password, see Troubleshooting.)
|
| The Order Number you received when you purchased MWeb |
Enter this Order Number exactly as given to you. (The Order Number is associated with your Project in the Systems Planning Registration Database.)
Note: If you ever upgrade to a later release of MWeb, you will use the Order Number of the upgrade purchase from then on. |
| If you are reusing MWeb for a new Project, enter the previous domain exactly as it was first registered (such as "www.yoursite.org") | WARNING: Your registration will replace the existing one, which will stop working. |
Click the Save button to save the information you entered. You will then be asked to logon using the new Administrator ID and password.
Whenever you logon using the Administrator ID, you will see the Administrator Control Center. This is a display that lets you configure all aspects of the Project. You will see several buttons here, but do not be dismayed! Most of them can be ignored for now.
To add the Database, from the Administrator Control Center, click the Databases button, select the Database Type* to add, then click the Add New Database button. You will see the Add Database form. Fill in the requested information:
| Code | A brief name the users will understand when they see it in the Search Results. It need not be the same as the Database Code you used during installation. |
|---|---|
| Name | A longer name for the Database. This is both for your reference and also displays to the user. |
| Domain | The domain of the Database Server, such as "www.example.org" (do not add "http://"). Do not use "localhost" or "127.0.0.1" as the domain; if you do, your Database will not be visible from the Internet. |
| CGI Path | The virtual directory to the CGI Directory containing the Database Connector (referred to as "udccgi" in the installation instructions). Do not use slashes here. |
| Data-Source Name | The ODBC Data-Source Name for the Database on the Database Server. (This is the name you chose in Step 5.) |
When all fields are filled in, click the Add button to add the Database.
* Database TypeSelecting the Database Type activates the appropriate wizard. Wizards save you the trouble of telling MWeb the structure of your Database. We add a wizard whenever we learn the structure of a widely used Database. Here are the wizards currently available:
Release 2.0 will include a wizard for
We will update this list as we develop more wizards. |
Return to the Administrator Control Center, then click Databases and then the Index button for the Database. Your Project will be ready for use when indexing is complete.
Indexing allows MWeb to find data in your Database without making any changes to it. By default, every word in every field is indexed. As you can imagine, this can take up to several hours for a large Database. The status of the indexing will be updated in your browser every five seconds. Do not cancel the process or MWeb will not work.
If indexing takes too long and you wish to skip the indexing of some fields in future updates, see Configuring Fields.
MWeb Enterprise Databases and PastPerfect-Online Databases do not require indexing.
Starting with Release 1.2, you may use the MySQL 5.0 database system to store MWeb's internal index (instead of the default SQLite database system). This may provide faster indexing and retrieval for large Databases. If you want to use MySQL, follow these steps now:
create user ODBC;
grant all privileges on *.* to 'ODBC'@'%';
flush privileges;
create database MWEB;
(or choose your own name).
When you index your Database, the index will be created in MySQL. If you wish to revert to MWeb's default of using SQLite, restore the MySQL Database setting to its default (blank); you will have to reindex your MWeb Database after that.
We have found no significant difference in speed of indexing or retrieval between MySQL and SQLite. Our largest test so far has been 1.6 million records (80 million keywords, 6 GB filesize). These indexes took about 8 hours to build.
Systems Planning