Installation and Getting Started

Prerequisites

• Unix or Unix style operating system on all systems - Solaris and Linux has been tested
• Select the user for running Faban - The user running Faban must be the same user name and user id on all the sysstems
  
• JDK1.5 or later - The JDK needs to be installed on the same path on all systems. This avoids having to configure a separate JDK path on each system.
• Download the Faban kit - you'll need either faban-bundle.tar.gz or faban-server.tar.gz for the master, and faban-client.tar.gz on all other systems.

Installation

1. Login using the selected user on all the systems.
   
   
2. Choose one of the machines not part of the SUT to be the master. Note that the master driver may or may not actually drive the load.
   
   
3. Untar faban-server.tar.gz or faban-bundle.tar.gz in any chosen directory on the master system. This will create a sub-directory named faban. We will refer to this directory as FABAN_HOME. For instance, if you choose to untar the tar file in /home/faban directory (assuming the user name is faban), then "/usr/faban/faban" is going to be the FABAN_HOME.
   
   Use the following command to untar the files:
   $ gunzip -c <filename> | tar xvf -
   
   Linux and some other Unix systems use gnu tar which automatically recognizes gzip-compressed files. If your system uses gnu tar, you can alternatively use the following command:
   $ tar xvf <filename>
   
   
4. Untar faban-client.tar.gz in the same directory on all the other systems in the rig. This will create a sub-directory named faban. FABAN_HOME should be the same path on all systems (symbolic links are OK on all systems but the master). Note that this step applies to all the systems including the systems part of the SUT.
   

Network Setup

1. Make sure you’ve configured all the systems so that they can talk to one another.
2. Edit the .rhosts file of the selected user so that Faban can rsh to all the systems that are part of the setup without being prompted for a password. You just need to add '+' character in the /.rhosts file. Note that this step applies to all the systems but the master, including all systems part of the SUT.

Tests

1. Verify that the master can “ping” all other systems.
   
   
2. Check that the master and other clients can “rsh <hostname> ls” each other without being prompted usually saves some time. This command will ensure that the harness can startup, shutdown, and reconfigure services on all systems.

Starting the Faban Harness

1. You may need to set the JAVA_HOME environment variable to a JDK1.5 installation.
   
   
2. Bring up the Faban harness on the master driver machine: $FABAN_HOME/master/bin/startup.sh
   
   
3. Access the harness interface from a browser window. Point your browser to http://<hostname>:9980/

Next Steps

Now you got the Faban harness up and running. But still, you do not have a benchmark deployed in the harness. So the next step is to deploy a benchmark into Faban before you can make any runs. Click next or the next page arrow below for the section on Benchmark deployments.