Installing the Destribution Package

Preparing the working directory

mkdir dCache
cd dCache
cp ???/dCache.tar .
tar xf dCache.tar
cd diskCacheV111/jobs
cp dcacheSetup.temp dcacheSetup
<edit>  dcacheSetup

Customizing the dCache

Although dCache allows a variety of possible setups we assume that there is only one Domain (JAVAVM) running per dCache host. This is in so far no restriction as each of these Domains may run any number of dCache services. E.g. multiple pools can be handled within one VM which itself may be the master Domain.

The steering of the startup procedure is exclusively done by a single setup file. On startup, the system searches for this file in the following order :

The setupfile contains a set of key value pairs separated by the '=' sign. The ${<key>} substitution mechanism may be used to reference keys defined before.

Some of these keys, defined in the setupFile, are mandatory to run the system others have reasonable defaults.

Customizable Parameters

The table below summarizes the key settings in the setupfile.
Variable Name Master Pool
java Only if not defined in PATH
dcacheClasses For use with pluggins only
jarDir ${jobs} ${jobs}
keyBase ${jobs} ${jobs}
masterPort/masterHost Only if running with multiple Domains
type master pool
pools Mandatory if pool(s) should run on master as well Mandatory
pnfsMount required or set to 'auto' no
ftpBase/ftpPort yes no
vspPort yes no
sshPort yes no
spyPort For Cell Gui only (spy) no
telnetPort Not recommended Not recommended

Starting the dCache

The dCache processe(s) can be started as soon as the setupfile and the related <PoolListFiles> on the different hosts are configured.
cd ..../jobs
./dcache start
The command has to be executed on each host. The sequence is not significant. It may take up to a minute before all processes could connect to each other.

If the startup has been successful, the master domain will print a list of active cells, the 'pool only' domain will simply acknowledge the successful startup. In case of a problem the startup will present the last n lines of the logfile in the hope that the reason for the failure is reported. In any case, the startup procedure will printout the name of the logfile.

Stopping the dCache

Nothing is yet forseen to allow a graceful shutdown of the dCache. The masterDomain can be stopped by
./dcache stop
In most cases this should work. In some cases the stop command stucks, in others it leaves behind some dangling threads which may prevent the diskcache from being started again. It is always a good idea to check the process list. The pur PoolDomain can only by stopped by sending the TERM signal to the JVM.

Logging into the dCache/Customizing the Pools

The host, the MasterDomain is running on, is the only Gate into the dCache System. Each user on that host will have unrestricted access to the dCache.
cd ..../jobs
./dcache login
For each user, logged in, the dCache creates a private shell to interact with the system. This shell provides commands to communicate with the CellKernel and with all relevent service cells.

Examples

Get a list of active cells
ps -f
Lists a active cells within the masterDomain together with some details about this cell (from left to right) :

Get the routing table

route
Routes to remove domains and cells are displayed.

Talking to a cell

The private login shell can connect to any other cell within the whole system. We distinquesh between three different kinds of cells concerning their accessability.
TypeDescriptionAddress
Local Resides in the same Domain as you login Cell <CellName>
Remote Resides in a remove Domain <CellName>@<DomainName>
Well Known Cell Anywhere <CellName>

Well Known Cells are cells which registered themselfs. Currently the PnfsManager, the PoolManager and all pools are 'well known cells'.
The route command (see above) lists all connected Domains and all cells which are well known.
To connect to a different cells :

On a correctly configured system, this shell is only needed for configuring the PoolCells.