[CONF] Apache Qpid: qmf_architecture (page edited)

[confluence]

Page Edited : qpid : qmf_architecture qmf_architecture has been edited by Ted Ross (Jul 02, 2008). (View changes) Content: Architectural Framework Components Management Broker The management broker has the following responsibilities: Manage the object-id space used to uniquely identify all manageable objects. Route agent commands from a console to the appropriate agent. Cache schema information provided by agents for the use of consoles. Management Agent The management agent consists of two parts. The first part is a component of the Qpid Management Framework and provides an API interface for the second part. The second part is specific to the software system being managed and is developed by the same team that develops the target system. The management agent is responsible for the following: Defining and owning the management schema for the target system. Maintaining manageable objects that are associated with physical or logical objects in the target system. Executing schema-defined method requests on object under its care. Management Console The management console consists of two main parts: The framework-supplied access API and the user-defined application built on the API. The user application is typically a CLI utility or a Graphical/Browser user interface but can take any other form as well. Other examples of console applications are: Event and audit storage applications Event correlation applications Two-tiered management servers (for web-based UIs) Bridges to other management protocols Automated monitoring and control applications that react to changes in the managed infrastructure Test harnesses Custom-built applications for any purpose Interfaces Console Interface Console | Framework --------+---------------------------------------------------- | | +------------+ | +----------------- | | | | reply-queue <--------| amq.direct | | +----------------- | | | +------------+ | | +-----------------+ | +----------------- | | | | topic-queue <--------| qpid.management | | +----------------- | | | | | | agent commands | | | --------------------------->| | | | | | +-----------------+ | Agent Interface Features Redundant components and paths Single point of entry Old Text There are two primary interfaces defined in the management architecture: The Management Console Interface is used by management clients (CLIs, GUIs, console servers, etc.) to remotely access management data. The Extension Interface is used by software components (not necessarily related to the QPID infrastructure) to provide access to their managed objects. +---------+ +---------+ +---------+ | | | | | | | CLI/GUI | | Console |<======>| CLI/GUI | | | | Server | | | +---------+ | | +---------+ ^ +---------+ | ^ | | v v +---------------------------------+ | | | Managed QPID Infrastructure | | | +---------------------------------+ ^ | v +------------+ | |-+ | Management | |-+ | Extensions | | | | | | | +------------+ | | +------------+ | +------------+ Both management interfaces are based on the AMQP protocol and its type system.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences