Added a script to startup QMan in standalone mode.

Added a man page, and a log4j file.
Modified the Configurator.java to throw an exception if it is unable to load the config file.


git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@719462 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 17 insertions, 0 deletions

diff --git a/qpid/java/management/client/doc/man/qman b/qpid/java/management/client/doc/man/qman
new file mode 100644
index 0000000000..cf4f90845c
--- /dev/null
+++ b/qpid/java/management/client/doc/man/qman
@@ -0,0 +1,17 @@
+.TH qman
+.SH NAME
+qman is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX). Once you run qman you need to start a JMX Console such as JConsole to browse the MBeans exposed by Q-Man.
+.SH SYNOPSIS
+qman
+.SH DESCRIPTION
+For more information on customizing QMan for your own environment please read http://cwiki.apache.org/confluence/display/qpid/Qman+Tool
+.SH Configuration
+.SS Classpath
+By default qman jars will be loaded from /usr/share/java. If you want to load from an alternative location you could specify it using QPID_LIB_PATH var.
+.SS Config file
+qman can be configured to connect to one or more brokers at startup by adding brokers in 
+.I /etc/qman-config.xml
+If you want to load qman with qma-config.xml from a different location, you can specify it using QPID_CONFIG_PATH var.
+.SS log4j configuration
+qman expects qman.log4j file to be in the classpath. By default it will be put in 
+.I /usr/share/java