Click on the Append, Add or Edit buttons to modify the table. Clicking on one of these buttons will produce a a dialog box that looks like (if you choose edit, the fields may be filled out already):

Fill out or edit the fields as follows:

Token - The token element identifies each entry when reporting Web Access Management usage, such as setting up a statistical filter. Tokens must be unique and contain at least three, but no more than eight, characters. Tokens are case-sensitive (e.g., "forbes" and "Forbes" are considered to be different tokens). NOTE: These are not the same "tokens" associated with Web OPAC.

IP Address/Host Name - This is the IP address or host name of the remote server to the database the patron may access. If the host name of the server is used, the Web server must be able to resolve it using a domain name server.

If you are using the Innovative Proxy Server to access this remote server, you may include "wildcards" in the host name (e.g., *. umi.com or 12.2.34. *). They may be used, for example, to access remote databases or services mounted on more than one physical machine.

Service Level - The minimum Service Level required to access the remote server from the Innovative Web server. This service level is compared to the service level of the login that is using the Innovative Web server, e.g., webpac, webremote (for more information on Web OPAC logins, see the Limit Network Access page of this tutorial. If the login's Service Level is less than this value, the login will not be allowed to access the remote server.

For additional information, refer to the Innovative Guide and Reference Manual, Page # 101722: Login Administration

Verify - This element indicates whether Web Access Management performs patronverification (' y ') or not (' n '). Alternatively, the value of this element can be a Service Level (a number from 0-9); if the login's Service Level is less than the Verify value, the Web server requires patron verification; otherwise, verification is not required.

Valid Patron Types - Enter the range of Patron Type codes that are allowed to access this database. The range can be specified as a single number (e.g., 1), a list of numbers separated by commas (e.g., 1,2,5,15), a range of numbers (e.g., 1-34), or a combination of the two (e.g., 1,3,5-12,34,37,51-63). If you want to allow all patrons to forward requests to this server, enter 0-255.

Valid Patron Home Libs - Your library can restrict access based on the Home Library field in a patron record ("Patron Home Libs"). If your organization does not use the "Patron Home Libs" field, then leave this field blank.

Database Identifier - If a database vendor offers more than one database on a single server, a database identifier will be provided to you by that vendor for each database to which your library subscribes. An example of this is OCLC's First Search, which has access to Eric, PsychInfo, etc. Your library may decide to limit access for each of these databases separately, based on the login's service level or the value of the PTYPE field in the patron's record.

If a Web OPAC user selects the a database link, Web Access Management will use the data in the this field entry to validate the patron's service level and patron type and then forward the connection to the remote server. Similarly, if the user selects another database link, a different entry will be used.

When there are multiple Forward Table entries with the same information in the IP Addr/Host Name element, the entry without a database ID must appear after those that do use database IDs. This would mean that the entries for the different databases within First Search (ERIC, PsychInfo, GPO, etc) would go above a generic entry for First Search. This is because Web Access Management reads the Forward Table from the top to the bottom and uses the first entry that matches the URL. An entry with a blank database ID element matches every URL with an ID in this element.

Database Name - The database name can be a maximum of 30 alphanumeric characters and is used to report statistics.

Logging Type - This entry accepts two possible values:

• N - If logging type is 'N', don't log anything for that database
• Y - If logging type is 'Y', apply category filters to each request for that database and do one of the following:
  • If match a filter with category label "X", then don't log that request
  • If match a filter with any category label other than "X", then log with that category label
  • If no match found, then log without any category label