すべてのバージョン
Bamboo 5.13Bamboo 5.7.x
Bamboo 5.6.x
More...
The Bamboo EAR-WAR distribution is intended for deployment into an existing J2EE application server. It is assumed that you already know how to deploy a web application on the application server of choice. If not, we recommend that you install the Bamboo Standalone distribution.
The following instructions are only indicative of the process and examples are based on installing the Bamboo WAR file on the Apache Tomcat application server. Deployment and configuration will differ from the procedure below if you choose to deploy the Bamboo EAR-WAR distribution on another (unsupported) application server.
On this page:
We also strongly recommend that you do not deploy multiple Atlassian applications in a single Tomcat container for a number of practical reasons. Firstly, you will need to shut down Tomcat to upgrade any application and secondly, if one application crashes, the other applications running in the Tomcat container will be inaccessible.
webapps
folder of Tomcat. Tomcat will perform all the necessary extractions when it starts.<bamboo-install>
)
Extracting the Bamboo WAR
By default, the WAR file will extract to a folder called
Bamboo-<version>
. The name of the directory in the webapps folder will form the URL required to access Bamboo (e.g. 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.
Set your Bamboo Home Directory. You can do this in one of three ways:
bamboo.home
property in the file /WEB-INF/classes/bamboo-init.properties
to your chosen Bamboo home directory.-Dbamboo.home=C:/bamboo/bamboo-home
).
If you are going to use Bamboo remote agents, set the following in the /WEB-INF/classes/bamboo-init.properties
file:
bamboo.jms.broker.uri=tcp://localhost:54663
We recommend that you set the following Java OPTs on your application server:
-server
— Ensures that the jvm starts up in server mode. This will perform various optimisation tasks which are 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
— (Unix systems only) 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:
set JAVA_OPTS=-server -XX:MaxPermSize=256m -Dbamboo.home=/opt/bamboo/bamboohome -Xmx512m -Djava.awt.headless=true $JAVA_OPTS
JAVA_OPTS="-server -XX:MaxPermSize=256m -Dbamboo.home=/opt/bamboo/bamboohome -Xmx512m -Djava.awt.headless=true $JAVA_OPTS" export JAVA_OPTS
If you have extracted the WAR file to a directory other than the default directory (e.g. for a Tomcat application server), you need to deploy <bamboo-install>
by following the steps below:
bamboo.xml
in your Tomcat installation's conf/Catalina/localhost
directory. If you have set up a different hostname for your Tomcat instance, please use your specified hostname instead of localhost
.bamboo.xml
and add the following:
<Context path="/bamboo" docBase="c:/applications/bamboo-war/" debug="0" reloadable="true"> </Context>
<bamboo-install>
absolute path that you noted down earlier.
http://host:port/bamboo
.