This page last changed on May 04, 2007 by admin.
The EAR/WAR edition of Bamboo is intended for deployment into an existing J2EE application server. It is assumed that you already know how to deploy a webapp on the application server of choice. If not, it is recommended to install the standalone distribution.
The following instructions are only indicative of the process and examples are based on installing the Bamboo WAR file on Apache Tomcat. Deployment and Configuration will differ based on your webserver.
Step 1. Download the WAR file
- The Bamboo WAR file is available for download here.
Step 2. Deploy onto your Application Server
In Tomcat you can do one of two things
- Place the WAR file directly into the webapps folder of Tomcat. When Tomcat starts it will perform all the necessary extractions.
- Extract the WAR file to your chosen directory in the webapps folder
Windows users avoid Win XP's built in unzip as it doesn't extract all the files. Use a 3rd party zip extractor like WinZip.
Solaris users will need to use GNU tar to handle the long filenames.
By default the WAR file will extract to a folder called Bamboo-<version>. Note: The name of the directory in the webapps folder will form the url required to access Bamboo (eg. Tomcat/webapps/bamboo-1.0/ will become http://host:port/bamboo-1.0/). You may wish to change the directory name for a more concise access url.
Step 3. Setting Bamboo Properties
You will need to set your bamboo home directory. You can do this in one of three ways:
- set the bamboo.home property in the file /WEB-INF/classes/bamboo-init.properties to your chosen bamboo home directory
- pass the bamboo home directory to the application server as a java opt. (eg. -Dbamboo.home=C:/bamboo/bamboo-home)
- set a system property bamboo.home to your bamboo home directory
Bamboo also recommends setting the following java opts on your Application Server.
- -server - Ensures that the jvm starts up in server mode. (This will perform various optimisation tasks, this is beneficial for long running applications.)
- -Xmx512m - Sets the maximum memory recommended for bamboo.
- -XX:MaxPermSize=256m - Sets the maximum permgen memory recommended for Bamboo.
- -Djava.awt.headless=true - For Unix systems. This allows AWT to run in headless mode and is required if running Bamboo in non-graphical environments. For more details visit the Sun Developer Network.
In Tomcat you can set the above java opts as follows
- Windows
1. Find the setenv.bat file.
2. Assign the desired properties to the JAVA_OPTS variable:
set JAVA_OPTS=-server -XX:MaxPermSize=256m -Dbamboo.home=/opt/bamboo/bamboohome -Xmx512m -Djava.awt.headless=true $JAVA_OPTS
- Linux Bases System
1. Find the setenv.sh file
2. Assign the desired properties to the JAVA_OPTS variable:
JAVA_OPTS="-server -XX:MaxPermSize=256m -Dbamboo.home=/opt/bamboo/bamboohome -Xmx512m -Djava.awt.headless=true $JAVA_OPTS"
export JAVA_OPTS
Step 3. Restart Server
- Shut down, and then restart your application server
- Bamboo should now be accessible on http://host:port/bamboo
Step 4. Configure Bamboo
See Running the Setup Wizard.
RELATED TOPICS
Bamboo 1.0 Installation Guide
Bamboo 1.0 Documentation Home
|