From f83677056891e436bf5ba99e79240df2a44528cd Mon Sep 17 00:00:00 2001 From: "Stephen D. Huston" Date: Fri, 21 Oct 2011 14:42:12 +0000 Subject: Merged out from trunk git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/QPID-2519@1187375 13f79535-47bb-0310-9956-ffa450edef68 --- java/management/client/doc/man/qman-jmx | 17 ----------------- 1 file changed, 17 deletions(-) delete mode 100644 java/management/client/doc/man/qman-jmx (limited to 'java/management/client/doc') diff --git a/java/management/client/doc/man/qman-jmx b/java/management/client/doc/man/qman-jmx deleted file mode 100644 index 064c00eae5..0000000000 --- a/java/management/client/doc/man/qman-jmx +++ /dev/null @@ -1,17 +0,0 @@ -.TH qman-jmx -.SH NAME -qman-jmx 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-jmx 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 qman-config.xml from a different location, you can specify it using QPID_CONFIG_FILE 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 -- cgit v1.2.1