From cc2ba9f942385cd6a45b8c2796617fa2c3e1266c Mon Sep 17 00:00:00 2001 From: Keith Wall Date: Thu, 9 Oct 2014 21:52:34 +0000 Subject: QPID-6108: [Java Broker Documentation] Add HA operational log messages, section related to configuration encryption and SCRAM-SHA providers. git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1630597 13f79535-47bb-0310-9956-ffa450edef68 --- .../concepts/Java-Broker-Concepts-Overview.xml | 77 ++++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 qpid/doc/book/src/java-broker/concepts/Java-Broker-Concepts-Overview.xml (limited to 'qpid/doc/book/src/java-broker/concepts/Java-Broker-Concepts-Overview.xml') diff --git a/qpid/doc/book/src/java-broker/concepts/Java-Broker-Concepts-Overview.xml b/qpid/doc/book/src/java-broker/concepts/Java-Broker-Concepts-Overview.xml new file mode 100644 index 0000000000..f83500e4a7 --- /dev/null +++ b/qpid/doc/book/src/java-broker/concepts/Java-Broker-Concepts-Overview.xml @@ -0,0 +1,77 @@ + + +
+ Overview + The Broker comprises of a number of entities. This section summaries the purpose of + each of the entities and describes the relationships between them. These details are developed + further in the sub-sections that follow. + The most important entity is the Virtualhost. A virtualhost is an + independent namespace in which messaging is performed. A virtualhost exists + in a container called a virtualhost node. A virtualhost node has exactly + one virtualhost. + Ports accept connections for messaging and management. The Broker + supports any number of ports. When connecting for messaging, the user specifies a virtualhost + name to indicate the virtualhost to which it is to be connected. + Authentication Providers assert the identity of the user as it connects + for messaging or management. The Broker supports any number of authentication providers. Each + port is associated with exactly one authentication provider. The port uses the authentication + provider to assert the identity of the user as new connections are received. + Group Providers provide mechanisms that provide grouping of users. A + Broker supports zero or more group providers. + Access Control Provider allows the abilities of users (or groups of + users) to be restrained. A Broker can have zero or one access control providers. + Keystores provide a repositories of certificates and are used when the + Broker accepts SSL connections. Any number of keystore providers can be defined. Keystores are + be associated with Ports defined to accepts SSL. + Truststores provide a repositories of trust and are used to validate a + peer. Any number of truststore provides can be defined. Truststores can be associated with Ports + and other entities that form SSL connections. + Remote Replication Nodes are used when the high availability feature is + in use. It is the remote representation of other virtualhost nodes that form part of the same + group. + These concepts will be developed over the forthcoming pages. The diagrams below also help + put these entities in context of one and other. +
+ Message Flow + + + + + + Message Flow through the Broker + + +
+
+ Broker Structure + + + + + + Broker Structure + + +
+
+ +
-- cgit v1.2.1