Yes, if you're using a pure JMS client you can use the http transport w/out having to deal with REST or AJAX. For example, if you're using the JNDI, you can place the following brokerURL in your jndi.properties file.
connection.httpConnectionFactory.brokerURL = http://host01:61616 >From your JMS client, you would then lookup the connection factory called, 'httpConnectionFactory'. In the broker XML file, you'll have to setup a http transport as follows: <transportConnector name="http" uri="http://host01:61616"/> The following jar files are required in the CLASSPATH for clients: $ACTIVEMQ_HOME/activemq-all-<version>.jar $ACTIVEMQ_HOME/lib/optional/commons-httpclient-<version>.jar $ACTIVEMQ_HOME/lib/optional/xstream-<version>.jar $ACTIVEMQ_HOME/lib/optional/xmlpull-<version>.jar You'll have to use the keytool for setting up the https and ssl transports. http://activemq.apache.org/how-do-i-use-ssl.html http://activemq.apache.org/ssl-transport-reference.html Joe www.ttmsolutions.com Brian Munroe-2 wrote: > > I'm interested in configuring ActiveMQ to use the HTTP(S) transport, > but I'm getting a bit cross-eyed regarding REST, HTTP(S) transports > and AJAX. > > From what I understand, if I only have pure JMS clients, I can safely > use the HTTP(S) transports without having to deal with REST or AJAX? > I'm very new to both JMS and ActiveMQ, so I need some serious hand > holding. > > I think I can figure out how to set up the HTTP(S) transports, but how > would I modify my clients to use them? I'm trying to use the examples > ProducerTool.java and ConsumerTool.java (provided in > $ACTIVEMQ_HOME/examples/src) as my basis, but if someone has simpler > examples, by all means, fire away. > > I know these are driven off of the build.xml, but I was just going to > try and hard code the URLs for now. > > thanks > > -- brian > > -- View this message in context: http://www.nabble.com/JMX-over-HTTP---How-to--tp15810985s2354p15811506.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
