Show Table of Contents
12.2. Adding a Transport Connector to a Standalone Broker
Adding a transport connector definition
To add a transport connector definition:
- Open the broker's configuration template for editing.
- Locate the
transportConnectorselement. - Add a
transportConnectorelement as a child of thetransportConnectorselement. - Add a
nameattribute to the newtransportConnectorelement.Thenameattribute specifies a unique identifier for the transport connector. It is used in the connectors property to identify the transport to be activated. - Add a
uriattribute to the newtransportConnectorelement.Theuriattribute 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. - 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
To activate a transport connector in a standalone broker:
- Connect to the broker using a command console.
- Open the broker's
io.fabric8.mq.fabric.server.idPID for editing using the config:editcommand.JBossAMQ:karaf>config:edit io.fabric8.mq.fabric.server.098765NoteYou can use the config:list command to find the id for the broker. - Verify the value of the connectors property using the config:proplist command.
JBossAMQ:karaf>config:proplist connector - Change the value of the connectors property using the config:propset command.
JBossAMQ:karaf>config:propset connector "connector1 connector2..."connector1 specifies the name of a transport to activate. The value corresponds the value of thetransportConnectorelement'snameattribute. - Save the changes using the config:update command.
JBossAMQ:karaf>config:update

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.