Transports
transports.conf contains zero or more transport definitions. Each definition begins with the name of a transport, surrounded by square brackets. Subsequent lines set the parameters of the transport.
This table lists the parameters specific to pulsar transports. See transports.conf for the list of parameters common to all transport types.
Note: The common transport parameters
export_headers and export_properties are not applicable for pulsar transports. Jakarta Messaging message headers and properties are always exported when translating EMS messages into Pulsar messages.| Parameter Name | Description |
|---|---|
type |
Required. For all EMS transports for Pulsar, the value must be pulsar.
|
|
pulsar Parameters The syntax and semantics of these parameters are identical to the corresponding parameters in Apache Pulsar clients. For full details, see the Apache Pulsar documentation. |
|
url
|
The URL(s) of the Pulsar broker(s) to connect to. |
Example
These examples from transports.conf illustrate the syntax of EMS transport for Pulsar definitions.
[PULSAR01] type = pulsar url = pulsar://host1:6650