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.

Components View

Table of Contents
minLevel2
maxLevel3

...

This package contains all configuration entities / items shared between all QMan components.
Those includes both configuration items that are directly under the user control and not-public items used internally to configurate configure (sub) components.
As you can see, the configuration package is a central grouping of components that serve serves the remaining three modules.

Image Added

Configurator

When QMan starts, this component is responsible to build the configuration for that instance. As you can see it uses several built-in builders in order to create and populate the configuration instance.

Configuration

Encapsulates a configuration for a QMan instance. Note that this is a singleton because it must be accessed from everywhere inside QMan sub-modules.

Parser

Active participants of the configuration build process. Basically they are responsible to parse a specific section of the (optional) qman-configuration file that is given at QMan startup. At the moment we have two implementantion of this interface :

  • WorkerManagerConfigurationParser : parses the configuration data of the internal worker manager; It creates a WorkerManagerConfigurationData instance.
  • BrokerConnectionDataParser : parses the connection data of declared brokers; For each configured broker a corresponding BrokerConnectionData instance is created.

WorkerManagerConfigurationData

A value object encapsulating configuration data for the work manager.

BrokerConfigurationData

A value object encapsulating connection data of a remote broker.

AccessModes

A map associating a code with an access mode. At the moment we have three access modes :

  • RO : Read only;
  • RW : Read / Write;
  • RC : Read create;

Message Handlers

Each time a message is received from a remote broker there will be a specific message handler that is responsible for processing that message.
On top of that, message handlers mapping associates an operation code (a character) with a message handler instance.
As you can see, there are two distinct collections of mappings. The first one contains message handlers associates with management queue, while the second one is referred to message handlers associated with method reply queue.

Package domain

Package jmx

...