From 3ba71456ec65fe69e351ec6ced57b69dd8f1d48e Mon Sep 17 00:00:00 2001 From: Alex Rudyy Date: Thu, 9 May 2013 15:04:59 +0000 Subject: QPID-4685: Update documentation to reflect changes to configuration git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1480672 13f79535-47bb-0310-9956-ffa450edef68 --- .../src/java-broker/Java-Broker-Concepts-Ports.xml | 24 ++++++++++++++++++++++ 1 file changed, 24 insertions(+) (limited to 'qpid/doc/book/src/java-broker/Java-Broker-Concepts-Ports.xml') diff --git a/qpid/doc/book/src/java-broker/Java-Broker-Concepts-Ports.xml b/qpid/doc/book/src/java-broker/Java-Broker-Concepts-Ports.xml index afbb612bc4..d3ef268f52 100644 --- a/qpid/doc/book/src/java-broker/Java-Broker-Concepts-Ports.xml +++ b/qpid/doc/book/src/java-broker/Java-Broker-Concepts-Ports.xml @@ -22,5 +22,29 @@
Ports +Port is a named broker entity serving as a communications end-point +and providing the AMQP transport layer over the given TCP port. The particular AMQP protocols can be configured on the Port. +As result, different Ports can support different protocols. Any number of Ports +can be configured on the Broker. + + The following AMQP protocols are currently supported by the Broker: + + AMQP 0.8 + AMQP 0.9 + AMQP 0.9.1 + AMQP 0.10 + AMQP 1.0 + + +Ports are also responsible for the authentication of all incoming connections +by mean of Authentication Provider configured on the Port. +Each Port can have its own Authentication Provider. +Both TCP and SSL transports are supported and can be configured on the Ports. +AMQP ports also support Client Certificate Authentication. + +Besides AMQP ports HTTP and JMX ports can be configured for use by management plugins. +They can be configured by specifying HTTP and RMI/JMX_RMI protocols respectively. + +Configuration details for the Ports are covered in .
-- cgit v1.2.1