You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

User guide

Introduction

QMan is a bridge that enables remote management of one or more brokers.
Depending on your needs, remote management can be exposed using JMX or WS-DM. The difference between two approaches is that in the first one only a Java client is supported, while WS-DM is language independent and therefore the corresponding management entity (client) should only able to speak WS-DM dialect.
As conseguence of that we will divide the following documentation under two perspectives.

In the picture below you can have a big picture about the working environment where QMan runs :

As you can see QMan supports three different clients :

  • a Java (Application) Client which is using Java Management Extensions (JMX) API for interaction; Note that this could be a standalone application client or a JEE application (Web & Business components);
  • a WS-DM enabled management client which could be an application / middleware / command line tool that is able to communicate with WS-DM dialect;
  • the third client (Web Browser) is not really a management client but it refers to administration console of QMan WS-DM. This is part of QMan Web Application and allows administration / management of QMan itself.

QMan Messages

Each log message produced by Qman has the following format :

<DATE> <PRIORITY> <MODULE> <MESSAGE-ID> : <MESSAGE>

Where :

  • <DATE> : The date and time at which the message was added;
  • <PRIORITY> : The priority level. Could be one of the following : DEBUG, WARN, INFO, ERROR, FATAL;
  • <MODULE> : The component which generated the log;
  • <MESSAGE-ID> : A message identifier. Each message has a unique id. It has the following format <QMAN-XXXXXXX>;
  • <MESSAGE> : The log message. Data recorded in this field should be ignored by analysis tools because it could change.

For example :

2009-02-12 15:20:44,971 INFO QMan <QMAN-000019> : Q-Man open for e-business.


Note that the log format described above is not fixed but could be configured using log4j. Obviously what mentioned above is referred to the default configuration shipped with QMan distribution.
The following is a list of all QMan messages divided by priority level.



Be Careful

QMan is under development so the list above could change easily...

  • No labels