Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Note
titleArchive Content

Please note this page is present for reference only. QMan has been removed and is no longer a released component.

Get me up and running

Table of Contents
minLevel2
maxLevel3

Get me up...

This section describes how to install QMan.

...

First of all, download the distribution from here and then unzip the archive into your chosen directory. Now you should have a directory structure like this :

  • bin : This contains the scripts needed to run QMan (see below for further details).
  • lib : This contains jars needed to run QMan (core libraries and dependencies).
  • log : This will contain the QMan log (see below for further details)

...

WS-DM Bridge

QMan WS-DM Bridge is running as a HTTP server . It includes the JMX core described previously but the JMX interface is not exposed. Instead when running in this mode, it that acts as a WS-DM Adapter and enables broker remote management using this interoperable protocol. Briefly, let's say that broker management interface is exposed as a WS-Resources domain.

...

No Format
2009-01-08 10:04:10,660 INFO  [log] Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
2009-01-08 10:04:10,769 INFO  [log] jetty-6.1.14
2009-01-08 10:04:10,832 INFO  [log] Extract jar:file:/home/pippo/qman/lib.../qman.war!/ to /home/pippo/pluto/paperino.../Jetty_0_0_0_0_8080_qman.war__qman__j84idd/webapp
2009-01-08 10:04:11,925 INFO  [log] NO JSP Support for /qman, did not find org.apache.jasper.servlet.JspServlet
2009-01-08 10:04:11,957 WARN  [log] Unknown realm: default
2009-01-08 10:04:13,191 INFO  [log] Started SelectChannelConnector@0.0.0.0:8080

...

Code Block
...

java -Dqman-config=<complete path to qman-config.xml> ...

If you don't have permission to edit the server startup script please read the User Guide in order to see how to connect QMan with broker(s) at runtime.