The following protocols can be used either for straightforward client-to-broker connections (transport connector) or broker-to-broker connections (network connector). For each wire protocol (that is, on-the-wire message encoding), FUSE Message Broker supports one or more associated transport protocols. Hence, you can configure connections with a wide variety of wire protocol/transport protocol combinations.
Table 1.1 shows the protocol combinations that messaging clients can use to connect directly to the message broker.
Table 1.1. Protocols for Simple Connections
| Wire Protocol | Transport Protocol | Sample URL | Description |
|---|---|---|---|
| OpenWire | TCP | tcp://Host:Port | Connect to the message broker endpoint at This URL is also used to configure the transport connector in a broker. |
| OpenWire | SSL | ssl://Host:Port | Connect to the message broker endpoint at This URL is also used to configure the transport connector in a broker. |
| OpenWire | HTTP | http://Host:Port | Connect to the message broker endpoint at This URL is also used to configure the transport connector in a broker. |
| OpenWire | HTTPS | https://Host:Port | Connect to the message broker endpoint at This URL is also used to configure the transport connector in a broker. |
| Stomp | TCP | stomp://Host:Port | Connect to the message broker endpoint at This URL is also used to configure the transport connector in a broker. |
| Stomp | SSL | stomp+ssl://Host:Port | Connect to the message broker endpoint at This URL is also used to configure the transport connector in a broker. |
| REST | HTTP | http:// | Connect to the message broker endpoint at For example, the sample URL is built up from a Web context name, This URL is not used to configure the REST transport connector in a broker. Use the |
| RESTs | HTTPS | http:// | |
| XMPP | TCP | xmpp://Host:Port | Configure the transport connector in a message broker to accept XMPP
connections on Host:Port (for
example, from an Instant Messaging client). |
| VM | N/A | vm://BrokerName | Configure clients to connect to a broker embedded within the same
Java Virtual Machine (JVM). The BrokerName is
the broker name of the embedded broker. |