This document tells you how to install iPlanet Compass Server. It contains the following sections:
|
||||||||||||||||||||||||||||||
Supported Platforms | ||||||||||||||||||||||||||||||
Please refer to the Release Notes for platform, patch, software and hardware requirements.
|
||||||||||||||||||||||||||||||
Installation Overview | ||||||||||||||||||||||||||||||
iPlanet Compass Server integrates seamlessly with iPlanet Portal Server. You can install Compass Server on
an existing Portal Server or on a separate machine. For a high traffic portal, or a portal where
Compass Server will be heavily used, we recommend dedicating a machine for Compass Server. When you install iPlanet Compass Server, you follow these basic steps:
Install the iPlanet Compass Server plugin. Enable the Compass Server plugin. Configure the Compass Server plugin. Install and configure the Compass Portal Provider.
|
||||||||||||||||||||||||||||||
Installing iPlanet Compass Server | ||||||||||||||||||||||||||||||
To install the Compass Server binaries for Solaris:
If installing from CD-ROM
Once the installation has completed, access the iWS administration panel: The default location is http://your_server:8888 Create a new Web Server instance for which you will be enabling the Compass Server plugin:
Once you have enabled the Compass Server plugin, you can access Compass
Administration via the Preferences/Compass Admin tab in the Web Server Manager.
To configure and add information to Compass Server, please refer to the online documentation at at http://www.iplanet.com/docs, which also includes a Quick Start Guide.
|
||||||||||||||||||||||||||||||
Installing the iPlanet Compass Server Portal Provider | ||||||||||||||||||||||||||||||
The Compass Server Portal Provider allows the integration of Compass Server into the Portal Server. It provides the end user
interface for a channel within the Portal and controls basic Administration information.
Before you begin
b) If you have multiple Portal Servers, you will need to copy the Compass Portal Provider installation
files to each Portal Server machine and repeat a) for each Portal Server.
The Compass Search channel is installed as a default provider. This means that it will automatically be available to users who have not modified their profile. If users have modified their profile, they can add the Compass Provider channel to their portal desktop by clicking on the Content link and checking the Compass Search checkbox. Adding categories to the Compass Provider From the Portal Administration:
Multiple Domain Configuration From the Portal Administration:
If you have inheritance turned off, then the Compass provider may not be displayed from
3 above. If this is the case, and you have already installed the Compass Server provider,
you can manually add the provider to this domain as follows:
Finally, you may have different template directories specified for each domain. The template directory is specified under the Desktop Profile for each domain. If you have different template directories for different domains, you will need to copy the Compass templates to each directory. The Compass template files are installed in the template directory of the domain you selected when you initially installed the Compass Server provider. Simply copy these files to the same relative path under the template directory for each domain.
|
||||||||||||||||||||||||||||||
Migrating from a pre 3.01B Compass Server | ||||||||||||||||||||||||||||||
If you are using an earlier version of Compass Server 3.x, you can follow the steps for migrating from 3.01B below,
but be sure to backup your data before you begin. If you are migrating from an earlier version of Compass or Catalog server, please contact iPlanet support for specific directions.
|
||||||||||||||||||||||||||||||
Migrating from Compass Server 3.01B | ||||||||||||||||||||||||||||||
Turn off your old compass server. You will also need to ensure that the database daemons (db_* processes) are off. For your old Compass Server, from the compass-nick directory, enter the command:
If you currently use the LDAP Local Database for server access control or the My Compass subsystem, or if you intend to use LDAP for your new Compass installation, you will need access to an external iPlanet Directory Server or another LDAP compliant server. We highly recommend that you use iPlanet Directory Server 4.x. The LDAP server does not have to be installed on the same machine as the Compass server, nor does it have to run on the same platform. You can quickly check if you currently use local LDAP. In General Administration:
Note that the URL for iPlanet Directory Server, using the example above is:
You will need iPlanet Web Server and iPlanet Portal server installed before you can install iPlanet Compass Server. We highly recommend that you install the latest versions before you begin the Compass Server install. Latest versions can be downloaded from the iPlanet web site. iPlanet Web Server must be installed on the same machine as iPlanet Compass Server See the above instructions for installing these products. See the above instructions to install iPlanet Compass Server. To continue migration, your new Compass Servers must be turned off. Note that the database daemons (db_* processes) are no longer separate processes, so you only need to turn off the Compass Servers from the Compass Administration.
If you wish to copy your old settings to your new Compass Server, you should copy the following configuration files from your old compass-nick/config directory to your new https-nick/config directory:
IMPORTANT NOTE: If you replace these files, remember to Apply the changes when
you access the new Compass Server's Administration. Failure to do so will result in
these changes being lost when furture admin modifications are applied.
If you wish to maintain the current data in your Compass database, you can move the database to your new Compass Server. Note: You must ensure that the Compass Server is off, the robot is off and the database daemons (old server only) are off for both your old Compass Server and new Compass Server before performing this step. - In your new Compass Server delete the db directory and all files and
subdirectories from https-nick/db
NS-idx-path=d:/netscape/SuiteSpot/compass-nick/db/verity/collections/compass to point to the absolute path of the new Compass Server's index directory, eg: NS-idx-path=d:/Netscape/Server4/https-nick/db/collections/compass NS-idx-path=d:/Netscape/SuiteSpot/compass-nick/db/verity/collections/taxonomy to point to the absolute path of the new Compass Server's index directory, eg: NS-idx-path=d:/Netscape/Server4/https-nick/db/collections/taxonomy This updates the configuration information for the database. If you have difficuly with this process, it is also possible to reindex the database from admin to recreate the search engine index colection (the collections subdirectory). The Compass Server templates have a new look and feel while maintaining consistency with the old templates. If you have modified the Compass Server templates in your old Compass Server, you can safely copy them to the new Compass Server. To do this: - Copy the files in the old Compass Server's compass-nick/templates directory to the new Compass Server's https-nick/templates directory. - In your new Compass Server Administration, go to the End User/Search page and select the same template as you had selected in your old Compass Server. We highly recommend that you inspect the new default templates in case you can take advantage of some of the improvements in your own templates. If your robot accesses sites that use SSL, you need to reconfigure the new server with these settings. Configuring SSL settings is explained in the Compass Server Administration Guide. From the Robots/Crawling tab, click on the Help button and follow the link to Roboting SSL sites. You can safely copy your old Compass Server's certificate and key databases
(cert7.db and key3.db respectively) from the old compass-nick/config directory to the new Compass
Server's https-nick/config directory. Note that if you have configured a password on
your certificate database, you will need to modify your https-nick/config/process.conf file.
Refer to the Help mentioned above for the steps to complete this task.
We recommend that you leave the SSL certificate database password empty if you will be
using My Compass via the Personalized Knowledge Services add on component
and have configured your Compass server to require certificate based
client authentication, or if you wish to import data from other Compass servers configured
for certificate based authentication. This limitation will be removed in future releases.
You can now configure the scheduling in the new Compass Server. In Compass you can schedule:
The server may take some time to respond, as it will perform an integrity check on startup. Your migration is now complete. If you have multiple Compass Server instances on your old Compass Server, simply add new instances to your new Web Server, upgrade the Web Server instance to Compass and repeat steps 5 to 11 above.
|
||||||||||||||||||||||||||||||
Uninstalling Compass Server | ||||||||||||||||||||||||||||||
Compass Server requires a manual uninstall procedure. To revert an installation of iPlanet Web Server to its original condition,
perform the following:
|
||||||||||||||||||||||||||||||