In-Reply-To: <9a668f1bb56f4133b558ca5211b30157@git.apache.org> References: <9a668f1bb56f4133b558ca5211b30157@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [41/51] [partial] qpid-site git commit: Update site for 6.1.1 release of Qpid Java archived-at: Wed, 28 Dec 2016 10:37:29 -0000 http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Channel.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Channel.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Channel.html new file mode 100644 index 0000000..8b9376b --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Channel.html @@ -0,0 +1,156 @@ + + + + + Chapter 6. Management Channels - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

Chapter 6. Management Channels
Prev		Next

Chapter 6. Management Channels

The Broker can be managed over a number of different channels.

HTTP - The primary channel for management. The HTTP interface comprises a Web + Console and a REST API.
AMQP - The AMQP protocols 0-8..0-10 allow for some management of Exchanges, Queue and + Bindings. This will be superseded by AMQP 1.0 Management. It is suggested that new users + favour the Management facilities provided by the Web Console/REST API.

6.1. HTTP Management

6.1.1. Introduction

The HTTP Management plugin provides a HTTP based API for monitoring and control of the + Broker. The plugin actually provides two interfaces:

Web Management + Console - rich web based interface for the management of the + Broker.
REST API - + REST API providing complete programmatic management of the Broker.

The Web Management Console itself uses the REST API, so every function you can perform + through the Web Management Console can be also be scripted and integrated into other + systems. This provides a simple integration point allowing the Broker to monitored and + controlled from systems such as Naoios or BMC Control-M.

6.1.2. Default Configuration

By default, the Broker is shipped with HTTP enabled running port 8080. The HTTP plugin + is configured to require SASL authentication. The port is not SSL protected.

The settings can be changed by configuring the HTTP plugin and/or the port configured + to serve HTTP.

Prev		Next
5.8. Example of JSON 'Initial Configuration'	Home	6.2. Web Management Console

+ +

+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, + Proton, Apache, the Apache feather logo, and the Apache Qpid + project logo are trademarks of The Apache Software + Foundation; All other marks mentioned may be trademarks or + registered trademarks of their respective owners +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Access-Control-Providers.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Access-Control-Providers.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Access-Control-Providers.html new file mode 100644 index 0000000..6a9d064 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Access-Control-Providers.html @@ -0,0 +1,146 @@ + + + + + 7.15. Access Control Providers - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.15. Access Control Providers
Prev	Chapter 7. Managing Entities	Next

7.15. Access Control Providers

An Access Control + Provider governs who may do what within the Broker. It governs both messaging and + management.

See Section 8.3, “Access Control Lists”

Prev	Up	Next
7.14. Group Providers	Home	7.16. HTTP Plugin

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Authentication-Providers.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Authentication-Providers.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Authentication-Providers.html new file mode 100644 index 0000000..56c61c9 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Authentication-Providers.html @@ -0,0 +1,163 @@ + + + + + 7.11. Authentication Providers - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.11. Authentication Providers
Prev	Chapter 7. Managing Entities	Next

7.11. Authentication Providers

+ Authentication + Providers are used by Ports to + authenticate connections.

See Section 8.1, “Authentication Providers”

7.11.1. Types

The following authentication providers are supported: +

Anonymous: allows anonymous connections to the + Broker
External: delegates to external mechanisms such as SSL Client + Certificate Authentication
Kerberos: uses Kerberos to authenticate connections via + GSS-API.
SimpleLDAP: authenticate users against an LDAP + server.
OAuth2: authenticate users against a OAuth2 Authorization + Server.
ScramSha: authenticate users against credentials stored in a + local database
Plain: authenticate users against credentials stored in a local + database.
PlainPasswordFile: authenticate users against credentials stored + in plain text in a local file.
MD5: authenticate users against credentials + stored in a local database.
Base64MD5PasswordFile: authenticate users against credentials + stored encoded in a local file.

The last five providers offer user management facilities too, that is, users can + be created, deleted and passwords reset.

7.11.2. Attributes

Name the authentication provider.

Other attributes are provider specific.

7.11.3. Children

None

7.11.4. Lifecycle

Not supported

Important

When updating an existing authentication provider, changes become effective until + the Broker is restarted.

Prev	Up	Next
7.10. Ports	Home	7.12. Keystores

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Broker.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Broker.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Broker.html new file mode 100644 index 0000000..fe84030 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Broker.html @@ -0,0 +1,171 @@ + + + + + 7.3. Broker - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.3. Broker
Prev	Chapter 7. Managing Entities	Next

7.3. Broker

The Broker is the principal entity. It is + composed of a number of other entities that collaborate to provide message broker + facilities.

The Broker can only be managed via the HTTP management channel.

7.3.1. Attributes

Name the Broker. This helps distinguish between Brokers in + environments that have many.
Heartbeating. Enables heartbeats between Broker and Clients. + Heartbeats help discover severed TCP/IP connections in a timely manner.
Confidential configuration encryption provider. The name of the + provider used to encrypt passwords and other secrets within the configuration. See Section 8.4, “Configuration Encryption”.

7.3.2. Context

broker.flowToDiskThreshold Controls the flow to disk feature.
broker.messageCompressionEnabled Controls the message compression .
store.filesystem.maxUsagePercent Maximum percentage of space + that may be utilised on a filesystem hosting a virtualhost's message store before + producer flow control is automatically imposed.
This defaults to 90%.
qpid.broker_default_supported_protocol_version_reply Used + during protocol negotiation. If set, the Broker will offer this AMQP version to a client + requesting an AMQP protocol that is not supported by the Broker. If not set, the Broker + offers the highest protocol version it supports.
+ qpid.broker_msg_auth If set true, the Broker ensures that the user + id of each received message matches the user id of the producing connection. If this + check fails, the message is returned to the producer's connection with a 403 (Access + Refused) error code.
This value can be overridden for each Virtual Host by setting the context value on the Virtual Host or + Virtual Host Node. +
Defaults to false.

7.3.3. Children

+ Virtualhost + nodes +
+ Ports +
Authentication Providers
Key Stores / Trust Stores
Group Providers
Access Control Providers

7.3.4. Lifecycle

Not supported

Prev	Up	Next
7.2. Entity/Management Channel Support Matrix	Home	7.4. Virtualhost Nodes

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Consumers.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Consumers.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Consumers.html new file mode 100644 index 0000000..517e9f7 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Consumers.html @@ -0,0 +1,151 @@ + + + + + 7.9. Consumers - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.9. Consumers
Prev	Chapter 7. Managing Entities	Next

7.9. Consumers

A Consumer represents an application's live subcription to a queue. Its presence + in the model indicates that an application is currently connected to the queue at this moment. +

7.9.1. Context

consumer.suspendNotificationPeriod Governs the length of + time that a consumer may remain suspended before the the Broker begins to + produce SUB-1003 + operational log messages.

Prev	Up	Next
7.8. Queues	Home	7.10. Ports

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Entities-Matrix.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Entities-Matrix.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Entities-Matrix.html new file mode 100644 index 0000000..e85b2e3 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Entities-Matrix.html @@ -0,0 +1,145 @@ + + + + + 7.2. Entity/Management Channel Support Matrix - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.2. Entity/Management Channel Support Matrix
Prev	Chapter 7. Managing Entities	Next

7.2. Entity/Management Channel Support Matrix

This tables indicates which management channels support the creation (C), update (U), or + deletion (D) of different entities within the Broker.

Table 7.1. Entity/Management Matrix

< tr>

Entity	HTTP	AMQP
Broker	U	No
Virtualhost Node	C/U/D	No
Virtualhost	C/U/D	No
Remote Replication Node	U/D	No
Exchange	C/D	C/D
Queue	C/D	C/D
Binding	C/D	C/D
Port	C/U/D	No
Authentication Providers	C/U/D	No
Group Providers	C//D	No
Access Control Provider	C//D	No
Keystores	C//D	No
Truststores	C//D	No
Users	C//D	No
Groups	C//D	No
Loggers	C/U/D	No

Note

It is currently only possible to modify a entity's context using the HTTP channel.

Prev	Up	Next
Chapter 7. Managing Entities	Home	7.3. Broker

+ +

+ + + +

+ + --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org For additional commands, e-mail: commits-help@qpid.apache.org

Project

Messaging APIs

Servers and tools

Resources

Chapter 6. Management Channels

6.1. HTTP Management

6.1.1. Introduction

6.1.2. Default Configuration

Project

Messaging APIs

Servers and tools

Resources

7.15. Access Control Providers

Project

Messaging APIs

Servers and tools

Resources

7.11. Authentication Providers

7.11.1. Types

7.11.2. Attributes

7.11.3. Children

7.11.4. Lifecycle

Important

Project

Messaging APIs

Servers and tools

Resources

7.3. Broker

7.3.1. Attributes

7.3.2. Context

7.3.3. Children

7.3.4. Lifecycle

Project

Messaging APIs

Servers and tools

Resources

7.9. Consumers

7.9.1. Context

Project

Messaging APIs

Servers and tools

Resources

7.2. Entity/Management Channel Support Matrix

Note