## Simple Connections

### Overview

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.

### Protocols for simple connections

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 `Host``:``Port` using the OpenWire over TCP protocol. 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 `Host``:``Port` using the OpenWire over SSL protocol. 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 `Host``:``Port` using the OpenWire over HTTP protocol (HTTP tunneling). You can use this protocol to navigate through firewalls. 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 `Host``:``Port` using the OpenWire over HTTPS protocol 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 `Host``:``Port` using the Stomp over TCP protocol. 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 `Host``:``Port` using the Stomp over SSL protocol. This URL is also used to configure the transport connector in a broker.
REST | HTTP | `http://`Host`:`Port`/ demo/message/FOO/BAR ?timeout=10000 &type=queue` | Connect to the message broker endpoint at `Host``:``Port` using the REST protocol. The REST endpoint is implemented as a servlet deployed in a servlet engine. For example, the sample URL is built up from a Web context name, `demo`, followed by the servlet name, `message`, followed by a destination name, `FOO/BAR`, and some query options. This URL is not used to configure the REST transport connector in a broker. Use the `<jetty>` tag to configure the REST endpoint in the broker.
RESTs | HTTPS | `http://`Host`:`Port`/ demo/message/FOO/BAR ?timeout=10000 &type=queue` |
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.