For instance, if it takes a single robot three full days to completely traverse
a network and index all its resources, you might instead install six robots,
each assigned to a particular portion of the network. Working in parallel,
they could complete the indexing in half a day, and you could import the
results into a central database.
Keep in mind that the resource descriptions generated by AutoCatalog are
not as rich as those generated by the Compass Server robot. For internal
sites, you might choose to bypass the AutoCatalog and send the robot to
locate and describe resources anyway.
For example, say a company runs three local sites, one in Europe, one in
Asia, and one in North America. Each of those sites can generate an index
of its contents locally, and a centralized Compass Server at any of those
sites can import the results from the others. That way, instead of hundreds
or thousands of intercontinental network contacts, the servers can have a
few, longer import sessions.
In general, an import agent contains parameters that tell it where to go to import resource descriptions, what to ask for when it gets there, and some other information that fine-tunes the way it goes about the job. For more details, see Editing an Import Agent.
The Import Agents form shows a list of all the currently defined import agents. If there are none currently defined, the list includes only a New button, used to create new import agents. If you have defined one or more import agents, there will be several other buttons below the list of import agents. When you run import agents, whether manually or automatically, the Compass Server runs all enabled import agents. An enabled import agent has the On button checked beside it in the list. Newly created import agents are enabled by default. You can enable or disable any of the defined import agents by clicking the On/Off buttons next to the desired items in the import agent list. A disabled import agent does nothing. You can also perform the following import tasks once you have defined at least one import agent:
The fields are described below.
The Delete Import Agents form shows a list of all existing import agents much like that on the Import Agents form, but instead of the On/Off option, there is a checkbox in front of each import agent.After you delete import agents, you return to the updated Import Agents form.
Running Import Agents Manually
In general, you need to run import agents manually only when you create a completely new Compass Server that needs an initial set of resource descriptions, when you have added new import agents to an existing Compass Server, or when you know that the source associated with an import agent has a large number of changes you want to incorporate into your database.
To run import agents manually, do the following:
WARNING: Do not close this import agent status window. Closing the window will cancel the import operation. You can minimize the window to get it out of your way, but do not close it or open another URL in the window until the import agent finishes its job.Note that by default an import agent imports all resource descriptions added to the source or changed since the last time it imported from that source. If you rerun an import agent immediately, it might appear to "fail," because it will not find any new or changed resource descriptions.
The Schedule task form indicates whether you currently have an automatic
schedule activated and shows the day(s) and time of scheduled import
agent runs, if any.
The schema is essentially a master data structure for resource descriptions in the database. Depending on how you define and index the fields in that data structure, users will have varying degrees of access to the resources.
WARNING:
The schema is intimately tied to the structure of the files used by the Compass
Server and its robot. You should only make changes to the data structure by
using the schema tools in the Netscape Server Manager for your Compass
Server. You should never edit the schema file (schema.rdm
) directly, even
though it is a text file.
The schema appears in outline form on the left side of the applet. The right
side shows the attributes of the selected field. The attributes are described
in the table below.
Example: Adding a Searchable Attribute
When the robot encounters a META
tag in a document, it converts the tag into a field in the resource description. If there is already an item in the schema with a corresponding name, it places the META
tag contents in that field. If there is no predefined field with that name, it adds one, and assigns the value.
There are two key facts here:
META
tag information is included in the resource description. Even obscure or unique tags are included in the resource description. For
example, suppose a document contains the following tag:
<META NAME="Sauce" CONTENT="cranberry">
When the robot indexes the document, it will create a schema attribute
called Sauce and assign it the value cranberry. Even though this word is not
visible in the document, users will be able to search for the term cranberry
and retrieve the document.
To continue with the preceding example, the Advanced Search does not
provide the ability to search for the word cranberry (or any other particular
value) in the field called Sauce. If you want to enable users to search for
terms in particular fields, you must define those fields in the schema and
make them indexable, as shown in the following example.
META
tag called PlaneType that contains the names of the planes covered. The Compass Server administrator wants to enable users to search for documents concerning those particular types of planes. These are the steps to do so:
This creates a new schema item named New, with the name selected.
META
tags from a document into schema fields, the document controls the names.
The Compass Server deals with these by allowing you to define schema conversions, which are mappings of external schema names into valid names for fields in your database. You define your schema conversions on the Schema Conversion form.
To convert incoming schema field names, do the following:
You can add more conversions by clicking More. If you want to delete the last conversion in the list, click Fewer.
Note that the Compass Server does not check to ensure that the pathname
is valid. If you type an invalid pathname, the operation will fail.
This creates the path if needed, redistributes the database records to take
advantage of the new space, and reindexes the database.
The Compass Server moves the partition to its new location, then reindexes
the database.
NOTE: One specialized use of the RD Editor is to assign categories to resource descriptions when the robot fails to do so. This is described in Handling Unassigned Resources.
WARNING: For whatever reason you want to delete the database, the procedure is the same. You should not simply delete database files from the disk. Doing so will likely result in your having to reinstall the Compass Server.To delete the entire resource database, do the following:
Similarly, the robot and all import agents should not be running when you
delete the database, as they rely on the database being there. They will
crash if you delete the database with them running.
The Compass Server rebuilds the index files for all partitions in the
database.
Last Updated: 02/12/98 13:34:06
Any sample code included above is provided for your use on an "AS IS" basis, under the Netscape License Agreement - Terms of Use