For users installing Chili!Soft ASP to shared file systems such as NFS or AFS (Andrew File System), or who are setting up a shared, multi-machine installation of Chili!Soft ASP, use the following instructions to relocate the system files. If you are not doing any of the above, it is recommended that you not alter the locations of the Chili!Soft ASP system files. For more information about multi-machine Chili!Soft ASP, see "Setting up Multi-machine Chili!Soft ASP" in this chapter.
Important Note
If you make any changes described in this section--such as to the registry or Chili!Soft configuration files--without prior authorization from Chili!Soft Customer support, you might void your eligibility for technical support.
Most of the configuration settings described in this section are easily accessed from the Chili!Soft ASP Administration Console. Because you can create serious problems with your system by configuring your computer in the manner described in this section, it is highly recommended that you use the Administration Console whenever possible, as described in "Using the Administration Console" in this chapter.
One of the key Chili!Soft ASP system files, the registry file (registry.bin), must be located on a local file system that supports file locking to ensure proper operation. During Chili!Soft ASP installation, the installer creates a script named chsetup.sh in the Chili!Soft ASP installation directory (the default is /opt/casp). Contained within this file is a line of code that resembles the following:
MWREGISTRY=[path name]/registry.bin
where [path name] is the current location of the registry file.
To relocate the registry file, use the following procedure.
To relocate the registry file
1. Write down the current value of [path name].
2. Create the new directory where you wish to relocate the registry file. This directory must reside on the local machine where the file system supports file locking. For the following steps, this new directory will be referred to as <new path name>.
3. Edit chsetup.sh with a text editor such as vi and change the following line:
MWREGISTRY=[path name]/registry.bin
to
MWREGISTRY=[new path name]/registry.bin
4. Copy the registry file from its old location ([path name]/registry.bin) to its new location (i.e., [new path name]/registry.bin).
Note
If you are setting up multi-machine Chili!Soft ASP, you need to have a separate copy of registry.bin on each machine running Chili!Soft ASP. Also, each local file system must have the identical local path to the location of the registry.bin file (i.e., /path/to/registry/file must exist on each machine.)
For users who want to install Chili!Soft ASP to a shared file system, but move write-able Chili!Soft ASP files to a local file system, Chili!Soft ASP provides a mechanism to allow for this. For single machine Chili!Soft ASP installations, this is not required, but has the added benefit that it may decrease network congestion. For multi-machine Chili!Soft ASP installations, the process ID (PID) files cannot be shared by Chili!Soft ASP engines and must be relocated. For more information about multi-machine Chili!Soft ASP, see "Setting up Multi-machine Chili!Soft ASP" in this chapter.
There are three attributes of importance in the casp.cnfg file (which is contained under each asp-<server>-<port> directory). These are the hashobj_pid and logfile attributes (located in the [machines] section), and the caspd_pid attribute (located in the [default machine] section). These attributes allow you to specify the locations of the two PID files. If you need to relocate these files, remember these two important facts:
· If you have several Chili!Soft ASP installations on a single physical server (with separate asp-<server>-<port> directories), then the casp.cnfg file in each directory may point to common directories for the PID and log files, but must point to different file names for the PID and log files.
· If you have a multi-machine installation of Chili!Soft ASP, then each machine that is hosting the Chili!Soft ASP engine must have its own copy of the PID files. Because the casp.cnfg file must be identical for each machine in a multi-machine installation, the directories and filenames for the PID and log files specified in casp.cnfg must exist on each machine’s local file system.
For example, suppose the [machines] and [default machine] sections of your current casp.cnfg file resemble the following.
[machines]
count=1
machine1=127.0.0.1
portnumber=3000
logfile=/opt/casp/logs/server-3000
mtengine=0
disablerestart=0
hashobj_pid=/opt/casp/logs/asp-apache-3000/hashobj.pid
[default machine]
caspd_pid=/opt/casp/logs/asp-apache-3000/caspd.pid
maxprocesses=1
inherit_user=1
#user=nobody
#group=nobody
In this situation, to relocate all of your files off of the shared /opt directory to a /usr/local/casp directory, use the following procedure.
To relocate all files
1. Create the destination directory(ies), for example:
mkdir -p /usr/local/casp/pids
mkdir -p /usr/local/casp/logs
2. Edit the casp.cnfg file to resemble the following example:
[machines]
count=1
machine1=127.0.0.1
portnumber=3000
logfile=/usr/local/casp/logs/server-3000
mtengine=0
disablerestart=0
hashobj_pid=/usr/local/casp/pids/hashobj-3000.pid
[default machine]
caspd_pid=/usr/local/casp/pids/caspd-3000.pid
maxprocesses=1
inherit_user=1
#user=nobody
#group=nobody
3. Copy the server log file and the PID files to the directories you created.
Note
If you are creating a multi-machine installation of Chili!Soft ASP, remember to copy the log file and PID files to each machine running Chili!Soft ASP. Also, each local file system must have the identical local path to the location of the log and PID files (i.e. according to the above example, /usr/local/casp/logs and /usr/local/casp/pids must exist on each machine).
Copyright 2001 Sun Microsystems, Inc. All rights reserved. Legal Notice.