My guess would be you would modify your bamboo master to use https in your BAMBOO_HOME/bamboo.cfg.xml file..
<property name="bamboo.jms.broker.client.uri">failover:(tcp://server.domain.com:54663?wireFormat.maxInactivityDurat
ion=300000)?initialReconnectDelay=15000&maxReconnectAttempts=10</property>
<property name="bamboo.jms.broker.uri">tcp://0.0.0.0:54663?wireFormat.maxInactivityDuration=300000</property>
For the agent, based on the bamboo.cfg.xml, i would assume you might be able to pass 'bamboo.jms.broker.client.url' as another java.additional in the wrapper.conf
or you might be able to set it in the AGENT_HOME/bamboo-agent.cfg.xml, but i can't really find any documentation on it..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dana The example you provided is the default configuration. It is for tcp port. What I am interested is a HOW-TO article how you can setup Bamboo server where you let agents communicate to it over 54663 (i.e. tcp port) as well as https for jms payload.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am wondering how to setup a Bamboo server (version 5.9.0) that allows broker communication (i.e. JMS payload) over https.
We have Bamboo server located at one of our company locations. Lets call this locationA. We like to run Bamboo agent from a different location. Lets call this locationB. The only ports allowed from locationB to locationA are http and https. The default broker port 54663 is not open at firewall. I am looking for ways to make this work. One idea is to tunnel agent to broker communication happen over https.
I see that Bamboo uses ActiveMQ framework for JMS. ActiveMQ seem to support tcp, ssl as well as https (among others). I don't see any examples how to configure a Bamboo broker to use https transport.
I appreciate any pointers.
Thanks