12.2. Adding a Transport Connector to a Standalone Broker

download PDF

Adding a transport connector definition

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.
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:
  1. Connect to the broker using a command console.
  2. Open the broker's PID for editing using the config:editcommand.
    JBossAMQ:karaf> config:edit
    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
  4. 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 the transportConnector element's name attribute.
  5. Save the changes using the config:update command.
    JBossAMQ:karaf> config:update
Red Hat logoGithubRedditYoutubeTwitter


Try, buy, & sell


About Red Hat Documentation

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

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.

© 2024 Red Hat, Inc.