Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 12. Adding Client Connection Points

Abstract

Message brokers must explicitly create connection points for clients. These connection points are called transport connectors. Red Hat JBoss A-MQ supports a number of transport flavors to facilitate interoperability with the widest possible array of clients.
A message broker communicates with its clients using one or more ports. These ports are managed by the broker's configuration. There are two required components to add a client connection point to a broker:
  • a transportConnector element in the XML configuration template that provides the details for the connection point
  • an entry in the broker's org.fusesource.mq.fabric.server.id PID's connectors property to activate the connection point
The transportConnector element provides all of the details needed to create the connection point. This includes the type of transport being used, the host and port for the connection, and any transport properties needed. The connectors property is a space delimited list that specifies which transport connectors to activate.
Red Hat JBoss Fuse supports a number of different transport flavors. Each transport has its own set of strengths. For more information on the different transports see the Client Connectivity Guide and the Connection Reference.

Adding a transport connector definition
Copy link

To add a transport connector definition:
  1. Open the broker's configuration template for editing.
  2. Locate the transportConnectors element.
  3. Add a transportConnector element as a child of the transportConnectors element.
  4. Add a name attribute to the new transportConnector element.
    The name attribute specifies a unique identifier for the transport connector. It is used in the connectors property to identify the transport to be activated.
  5. Add a uri attribute to the new transportConnector element.
    The uri attribute specifies the connection details used to instantiate the connector. Clients will use a similar URI to access the broker using this connector. For a complete list of the URIs see the Connection Reference.
  6. Save the changes to the configuration template.
Note
The newly added transport connector is not available until it has been activated using the connectors property.

Activating a connector
Copy link

To activate a transport connector in a standalone broker:
  1. Connect to the broker using a command console.
  2. Open the broker's org.fusesource.mq.fabric.server.id PID for editing using the config:editcommand. 
    JBossAMQ:karaf> config:edit org.fusesource.mq.fabric.server.098765
    Copy to Clipboard Toggle word wrap
    Note
    You can use the config:list command to find the id for the broker.
  3. Verify the value of the connectors property using the config:proplist command. 
    JBossAMQ:karaf> config:proplist connector
    Copy to Clipboard Toggle word wrap
  4. Change the value of the connectors property using the config:propset command. 
    JBossAMQ:karaf> config:propset connector "connector1 connector2..."
    Copy to Clipboard Toggle word wrap
    connector1 specifies the name of a transport to activate. The value corresponds the value of the transportConnector element's name attribute.
  5. Save the changes using the config:update command. 
    JBossAMQ:karaf> config:update
    Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top