h3. Supported operating systems
* Windows 2000/XP/Vista/7, Windows server 2003/2008, 32 bit and 64 bit, x86 and IA architecture
* Linux, 32 bit and 64 bit, x86, PowerPC and S/390 architecture
* Mac OS X, 32 bit and 64 bit
* Solaris, 32 bit and 64 bit, Sparc and x86 architecture
* AIX, 32 bit and 64 bit, PowerPC architecture
* HP-UX, 32 bit and 64 bit, IA and PARISC architecture
* FreeBSD, 32 bit and 64 bit, x86 architecture
h3. Memory requirement
* 64M minimum, 256M recommended
h3. Installation Steps
# Make sure QuickBuild server is up and running, *login to QuickBuild as administrator* and navigate to _Grid_ tab, follow the _download build agent_ link to download the build agent. Extract downloaded file into the directory where the build agent should be installed. Make sure the user running user agent has *full access rights* to the installation directory.
# Make sure you have *JDK6, JDK7 or JDK8* installed. Download the appropriate JDK version from [http://java.sun.com] if needed.
# Make sure the _java_ command exists in the system path; if not, you will need to modify the file _conf/wrapper.conf_ under the build agent's installation directory, and point the entry _wrapper.java.command_ to path of the java command.
# Optionally run _<agent install dir>/bin/config.bat|sh)_ to configure build agent properties such as IP address, port number, SSL setting, etc.
# Open a command prompt window, switch to folder _<agent install dir>/bin_, and run command _agent.(bat|sh) console_ to start the agent.
{note}
Follow [this guide|Install As System Service] on how to install the agent as system service so that it auto-starts when machine reboots.
{note}
# After the agent starts up, it may complain with the message "This build agent is not authorized to join the grid". Upon this, you need to login to QuickBuild server and authorize the agent to join the grid. Refer to [Working with Build Grid] for how to authorize build agents to join grid.
# If the build agent is connected to QuickBuild server correctly, you will see its entry in active node list of the build grid like below by logging in as administrator:
!active-nodes.png!
h4. Trouble Shooting
If your agent does not connect with server, please make sure that:
# You can telnet to server port from agent machine with below command:
{code}telnet _<server host name>_ _<server port>_{code}
Here _<server host name>_ and _<server port>_ has to be extracted from _serverUrl_ in file _conf/node.properties_ of under agent directory.
# You can telnet to agent port from server machine with below command:
telnet _<agent ip address>_ _<agent port>_
# If auto-detected agent ip reported in server console log is incorrect, specify it explicitly by editing _conf/node.properties_ of the agent to add below property:
{code}ip=_<agent ip address>_{code}
# Recently we found a case where QB agent from other subnets connects to server but then times out during initialization (agents from same subnet works fine), and it turns out that server response package is dropped for some reason (maybe the package content matches some pre-set drop rule) across the gateway, and the problem is solved by connecting to server via ssl port so that server response package is encrypted.
* Windows 2000/XP/Vista/7, Windows server 2003/2008, 32 bit and 64 bit, x86 and IA architecture
* Linux, 32 bit and 64 bit, x86, PowerPC and S/390 architecture
* Mac OS X, 32 bit and 64 bit
* Solaris, 32 bit and 64 bit, Sparc and x86 architecture
* AIX, 32 bit and 64 bit, PowerPC architecture
* HP-UX, 32 bit and 64 bit, IA and PARISC architecture
* FreeBSD, 32 bit and 64 bit, x86 architecture
h3. Memory requirement
* 64M minimum, 256M recommended
h3. Installation Steps
# Make sure QuickBuild server is up and running, *login to QuickBuild as administrator* and navigate to _Grid_ tab, follow the _download build agent_ link to download the build agent. Extract downloaded file into the directory where the build agent should be installed. Make sure the user running user agent has *full access rights* to the installation directory.
# Make sure you have *JDK6, JDK7 or JDK8* installed. Download the appropriate JDK version from [http://java.sun.com] if needed.
# Make sure the _java_ command exists in the system path; if not, you will need to modify the file _conf/wrapper.conf_ under the build agent's installation directory, and point the entry _wrapper.java.command_ to path of the java command.
# Optionally run _<agent install dir>/bin/config.bat|sh)_ to configure build agent properties such as IP address, port number, SSL setting, etc.
# Open a command prompt window, switch to folder _<agent install dir>/bin_, and run command _agent.(bat|sh) console_ to start the agent.
{note}
Follow [this guide|Install As System Service] on how to install the agent as system service so that it auto-starts when machine reboots.
{note}
# After the agent starts up, it may complain with the message "This build agent is not authorized to join the grid". Upon this, you need to login to QuickBuild server and authorize the agent to join the grid. Refer to [Working with Build Grid] for how to authorize build agents to join grid.
# If the build agent is connected to QuickBuild server correctly, you will see its entry in active node list of the build grid like below by logging in as administrator:
!active-nodes.png!
h4. Trouble Shooting
If your agent does not connect with server, please make sure that:
# You can telnet to server port from agent machine with below command:
{code}telnet _<server host name>_ _<server port>_{code}
Here _<server host name>_ and _<server port>_ has to be extracted from _serverUrl_ in file _conf/node.properties_ of under agent directory.
# You can telnet to agent port from server machine with below command:
telnet _<agent ip address>_ _<agent port>_
# If auto-detected agent ip reported in server console log is incorrect, specify it explicitly by editing _conf/node.properties_ of the agent to add below property:
{code}ip=_<agent ip address>_{code}
# Recently we found a case where QB agent from other subnets connects to server but then times out during initialization (agents from same subnet works fine), and it turns out that server response package is dropped for some reason (maybe the package content matches some pre-set drop rule) across the gateway, and the problem is solved by connecting to server via ssl port so that server response package is encrypted.