Reply-To: dev@qpid.apache.org Delivered-To: mailing list commits@qpid.apache.org Received: (qmail 88336 invoked by uid 99); 8 Feb 2018 21:14:50 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Feb 2018 21:14:50 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id CE99BF32D0; Thu, 8 Feb 2018 21:14:49 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: orudyy@apache.org To: commits@qpid.apache.org Date: Thu, 08 Feb 2018 21:15:10 -0000 Message-Id: <41a64e9192ff4a1a8cc060f580b1ba2d@git.apache.org> In-Reply-To: <271a997bf3864edb80636b74e3eba227@git.apache.org> References: <271a997bf3864edb80636b74e3eba227@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [22/32] qpid-site git commit: QPID-8094: Update site for Qpid Broker-J release 7.0.1 http://git-wip-us.apache.org/repos/asf/qpid-site/blob/42d76007/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Authentication-Providers.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Authentication-Providers.html b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Authentication-Providers.html new file mode 100644 index 0000000..4f40f89 --- /dev/null +++ b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Authentication-Providers.html @@ -0,0 +1,163 @@ + + + + + 7.10. Authentication Providers - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.10. Authentication Providers
Prev	Chapter 7. Managing Entities	Next

7.10. Authentication Providers

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

See Section 8.1, “Authentication Providers”

7.10.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.10.2. Attributes

Name the authentication provider.

Other attributes are provider specific.

7.10.3. Children

None

7.10.4. Lifecycle

Not supported

Important

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

Prev	Up	Next
7.9. Ports	Home	7.11. Keystores

+ +

+ + + +

+ 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/42d76007/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Broker.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Broker.html b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Broker.html new file mode 100644 index 0000000..e38fd1f --- /dev/null +++ b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Broker.html @@ -0,0 +1,170 @@ + + + + + 7.2. Broker - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.2. Broker
Prev	Chapter 7. Managing Entities	Next

7.2. 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.2.1. Attributes

Name the Broker. This helps distinguish between Brokers in + environments that have many.
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.2.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.2.3. Children

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

7.2.4. Lifecycle

Not supported

Prev	Up	Next
Chapter 7. Managing Entities	Home	7.3. Virtualhost Nodes

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/42d76007/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Consumers.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Consumers.html b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Consumers.html new file mode 100644 index 0000000..f096908 --- /dev/null +++ b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Consumers.html @@ -0,0 +1,151 @@ + + + + + 7.8. Consumers - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.8. Consumers
Prev	Chapter 7. Managing Entities	Next

7.8. 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.8.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.7. Queues	Home	7.9. Ports

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/42d76007/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Entities.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Entities.html b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Entities.html new file mode 100644 index 0000000..3fa575a --- /dev/null +++ b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Entities.html @@ -0,0 +1,165 @@ + + + + + Chapter 7. Managing Entities - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

Chapter 7. Managing Entities
Prev		Next

Chapter 7. Managing Entities

Table of Contents

7.1. General Description

7.2. Broker

7.2.1. Attributes
7.2.2. Context
7.2.3. Children
7.2.4. Lifecycle

7.3. Virtualhost Nodes

7.3.1. Types< /span>
7.3.2. Attributes
7.3.3. Children
7.3.4. Lifecycle

7.4. VirtualHosts

7.4.1. Types
7.4.2. Context
7.4.3. Attributes
7.4.4. Children
7.4.5. Lifecycle

7.5. Remote Replication Nodes

7.5.1. Attributes
7.5.2. Children
7.5.3. Lifecycle
7.5.4. Operations

7.6. Exchanges

7.6.1. Types
7.6.2. Attributes
7.6.3. Lifecycle

7.7. Queues

7.7.1. Types
7.7.2. Attributes
7.7.3. Lifecycle

7.8. Consumers

7.8.1. Context< /span>

7.9. Ports

7.9.1. Context
7.9.2. Attributes
7.9.3. Children
7.9.4. Lifecycle

7.10. Authentication Providers

7.10.1. Types
7.10.2. Attributes
7.10.3. Children
7.10.4. Lifecycle

7.11. Keystores

7.11.1. Types
7.11.2. Attributes
7.11.3. Children
7.11.4. Lifecycle

7.12. Truststores

7.12.1. Types
7.12.2. Attributes
7.12.3. Children
7.12.4. Lifecycle

7.13. Group Providers

7.14. Access Control Providers

7.15. HTTP Plugin

7.15.1. Attributes
7.15.2. Children
7.15.3. Lifecycle

This section describes how to manage entities within the Broker. The principles underlying + entity management are the same regardless of entity type. For this reason, this section begins + with a general description that applies to all.

Since not all channels support the management of all entity type, this section commences + with a table showing which entity type is supported by each channel.

7.1. General Description

The following description applies to all entities within the Broker regardless of their + type.

All entities have a parent, and may have children. The parent of the Broker is + called the System Context. It has no parent.
Entities have one or more attributes. For example a name, an + id or a maximumQueueDepth
Entities can be durable or non-durable. Durable entities survive a restart. + Non-durable entities will not.
Attributes may have a default value. If an attribute value is not specified the + default value is used.
Attributes values can be expressed as a simple value (e.g. myName + or 1234), in terms of context variables + (e.g.${foo} or /data/${foo}/).
Each entity has zero or more context variables.
The System Context entity (the ultimate ancestor of all object) has a context too. + It is read only and is populated with all Java System Properties. Thus it can be + influenced from the Broker's external environment. See QPID_OPTS + environment variable.
When resolving an attribute's value, if the value contains a variable + (e.g.${foo}), the variable is first resolved using the entity's own + context variables. If the entity has no definition for the context variable, the + entity's parent is tried, then its grandparent and so forth, all the way until the + SystemContext is reached.
Some entities support state and have a lifecycle.

What follows now is a section dedicated to each entity type. For each entity type key + features are described along with the entities key attributes, key context variables, details + of the entities lifecycle and any other operations.

Prev		Next
6.4. AMQP Intrinstic Management	Home	7.2. Broker

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/42d76007/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Exchanges.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Exchanges.html b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Exchanges.html new file mode 100644 index 0000000..2eb1dd5 --- /dev/null +++ b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Exchanges.html @@ -0,0 +1,150 @@ + + + + + 7.6. Exchanges - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.6. Exchanges
Prev	Chapter 7. Managing Entities	Next

7.6. Exchanges

Exchanges can be managed using the + HTTP or AMQP channels.

7.6.1. Types

Direct
Topic
Fanout
Headers

7.6.2. Attributes

Name of the exchange. Message producers refer to this name when + producing messages.
Type of the exchange. Can be either direct, topic, fanout, or headers.
Durable. Whether the exchange survives a restart.
Durable. Whether the exchange survives a restart.
alternateBinding. Provides an alternate destination that, depending on behaviour + requested by the producer, may be used if a message arriving at this exchange cannot be routed to at least + one queue.
unroutableMessageBehaviour. (AMQP 1.0 only) Default behaviour to apply when a + message is not routed to any queues.

7.6.3. Lifecycle

Not supported

Prev	Up	Next
7.5. Remote Replication Nodes	Home	7.7. Queues

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/42d76007/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Group-Providers.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Group-Providers.html b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Group-Providers.html new file mode 100644 index 0000000..9ca1d4e --- /dev/null +++ b/content/releases/qpid-broker-j-7.0.1/book/Java-Broker-Management-Managing-Group-Providers.html @@ -0,0 +1,144 @@ + + + + + 7.13. Group Providers - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.13. Group Providers
Prev	Chapter 7. Managing Entities	Next

7.13. Group Providers

See Section 8.2, “Group Providers”

Prev	Up	Next
7.12. Truststores	Home	7.14. Access Control Providers

+ +

+ + + +

+ + --------------------------------------------------------------------- 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

7.10. Authentication Providers

7.10.1. Types

7.10.2. Attributes

7.10.3. Children

7.10.4. Lifecycle

Important

Project

Messaging APIs

Servers and tools

Resources

7.2. Broker

7.2.1. Attributes

7.2.2. Context

7.2.3. Children

7.2.4. Lifecycle

Project

Messaging APIs

Servers and tools

Resources

7.8. Consumers

7.8.1. Context

Project

Messaging APIs

Servers and tools

Resources

Chapter 7. Managing Entities

7.1. General Description

Project

Messaging APIs

Servers and tools

Resources

7.6. Exchanges

7.6.1. Types

7.6.2. Attributes

7.6.3. Lifecycle

Project

Messaging APIs

Servers and tools

Resources

7.13. Group Providers