NOTE: Migration takes place on a single computer. That is, you install the new server on the same system as the old one, and the migration process copies and translates configuration files and prepares the new server to receive content from the old one. You cannot perform migration across a network. Similarly, migrating a server on one operating system of a dual-boot Windows NT system will not migrate to the other operating system.
You must install the Compass Server on the same computer that has the Catalog Server running on it. Because they use different administration servers, you must install the Compass Server in a different server root directory.
Instructions on installing the server are in the Netscape Compass Server
Installation Guide or in the readme file accompanying the server.
If you install the new server to use the same port as the old one, you must not turn on the servers at the same time. Leave the Compass Server off at first, until after the migration process.
The migration process copies information to the Compass Server only from
a Catalog Server. That means that any information held in Resource
Description Servers that has not been imported into the Catalog Server will
not migrate. Therefore, make sure the Catalog Server is as up-to-date as
possible before migrating.
Specifically, this means you should import all available resource
descriptions from all available RDSs into the Catalog Server before starting
the migration process. If you do not, it is possible for your resource
descriptions to get out of synch with configuration files such as the schema
and categories.
NOTE: During the migration process, you will likely see messages that indicate that your Resource Description Servers are not installed, even though they are. What this really means is that there is no information you can migrate from those servers.
readme file.
Do not start the Compass Server.
You will see a form headed "Choose 2.x Server Root to Import From." The
2.x refers to the version number of the administration server used by
Netscape Catalog Server 1.0.
For Unix systems, the default path is
/usr/ns-home. For Windows NT
systems, the default directory is C:\Netscape.
This generates a list of the servers in that server root, including the
Administration Server itself, the Catalog Server, and any other servers
sharing that administration server, possibly including your Resource
Description Servers.
If you have one or more Resource Description Servers installed, they will
appear with a message "Can't import server name, rds not installed." Don't
worry about the message. The migration process does not need to import
from these servers directly.
For the Catalog Server, you'll see a form headed "Import 1.x Catalog Server
Info." By default, the server name, port, and user ID are copied directly
from the Catalog Server.
You can also choose which Resource Description Server to import filter
rules and site information from. You can only migrate the rules and sites
from a single RDS. All resource descriptions from all RDSs should already
have been imported into the Catalog Server prior to migration.
You should see one import agent listed, importing from the Catalog Server.
Last Updated: 02/12/98 13:36:22
Any sample code included above is provided for your use on an "AS IS" basis, under the Netscape License Agreement - Terms of Use