The main role of a JMS broker such as ActiveMQ is to provide a communication
Infrastructure for client applications. For that reason, ActiveMQ provides connectors,
A connectivity mechanism that provides client-to-broker communications (using
Transport connectors) as well as Broker-to-broker communications (using network
Connectors). ActiveMQ allows client applications to connect using a variety of protocols,
But also allows other brokers to create communication channels and to
Build complex networks of ActiveMQ brokers.
The primary role of a JMS proxy, such as ACTIVEMQ broker, is to provide a communication mechanism for the client program. To do this, ACTIVEMQ provides a connection mechanism that
This connection mechanism uses the transport connector (transport Connector) to communicate between the client and the agent (Client-to-broker);
Use network connector to implement agent-to-agent communication.
We start this chapter by explaining connector URIs, which is used to address the
Broker. After that, we'll dig into transport connectors and explain what protocols clients
can use to connect to the ActiveMQ broker.
In this chapter, we start by parsing the URI of the connector used to locate the broker (broker), and then dive into the transport connector (transport Connector)
The protocol used by the client to connect to the ACTIVEMQ agent (broker) is also resolved.
NOTE We Use the Terms Connector and protocol interchangeably. Protocols
is general-purpose concepts and connectors are activemq-specific mechanisms,
But every ActiveMQ connector, as you'll see, implements a specific
Protocol and is named after it. It should is clear from the context whether
We ' re talking about a protocol in general or a specific ActiveMQ connector.
Note: We use the term Connector (connector) and the Connection Protocol (Protocol) to be interchangeable.
The protocol mentioned here is a generic concept, and the connector (connector) is a unique mechanism of ACTIVEMQ.
You will see that each ACTIVEMQ Connector (connector) implements a specific protocol that is named after the protocol.
The context should be able to determine whether we are talking about a generic protocol or a ACTIVEMQ-specific connector (connector).
This chapter covers
? A description and demonstration of ActiveMQ connector URIs
? How to connect your clients to ActiveMQ using transport
Connectors
? How to create a cluster of ActiveMQ message brokers using
Network
The contents of this chapter include:
(1) Introduction and parsing of URIs for ActiveMQ connectors (connector)
(2) How the client connects to ActiveMQ using a transport connector (ActiveMQ Connector)
(3) How to create a ACTIVEMQ message agent (broker) cluster
We ' ll first explain how to configure transport connectors and demonstrate it by adapting
The stock portfolio example for use over different connectors, so we can demonstrate
them later on. Then we'll be ready for move on to specific connectors. The
Various transport connectors that allow you to connect to ActiveMQ would be discussed
including TCP, SSL, and HTTP. Next, embedded brokers using the VM protocol would be
Introduced.
First, we'll modify the code for the stock portfolio instance, using a different connector to illustrate how to configure
Transport Connector (transport Connector), which will be explained later in the various transport connectors (transport Connector).
Then we can turn to the introduction of various specific connectors (connector), which can be used to connect to the ACTIVEMQ of various connectors including:
TCP connectors, SSL connectors, and HTTP connectors.
Next, we'll also discuss the embedded proxy (embedded broker) that uses the VM protocol.
Finally some basic concepts of ActiveMQ clustering using network connectors would be
Covered. We ' ll demonstrate how can create static networks of brokers using the
Static protocol and how clients can reliably connect to the network of brokers using
The failover protocol. Dynamic networks using such protocols as multicast and discovery
would also be covered. This section would only introduce basic concepts and protocols
Used for networks of brokers, whereas + information on them can is found in
Chapter 10.
Finally, this chapter will discuss some of the basic concepts of configuring ACTIVEMQ clusters using Network Connector connector.
We will discuss how to create a static proxy network using static protocols (net of brokers), and how the client uses
The Fault Tolerant Protocol (failover protocol) is reliably connected to the proxy network (net of brokers). This chapter also discusses
Use a dynamic network with multicast. This section focuses on some of the basic concepts of the agent network, brokers
More information about the network of brokers will be presented in chapter tenth.
ACTIVEMQ actual combat two connected to the activemq-connecting to ACTIVEMQ