AMQP Connector: Configuration

How to create the configuration file

Right-click on the name of the project in the Projects view.
A dialog window opens.
Wählen Sie New > .amqp. The configuration file with the extension .amqp has now been created at the main level of the project.

The file has the following structure:

CODE

<?xml version="1.0" encoding="UTF-8"?>
<AmqpConfiguration>
	<threadPoolSize>10</threadPoolSize> 
	<broker server = "localhost:5672"> 
		<client id="1">
			<topic filter="topic1" qos="AT_LEAST_ONCE"></topic>
			<process url="Processes/data.wrf"></process>
			<pubSubExchange>example</pubSubExchange>
			<isQueueDurable>true</isQueueDurable>
		</client>
	</broker>
</AmqpConfiguration>

The following attributes and elements are contained in the configuration file:

Element / Attribute	Description
`AmqpConfiguration`	Root element of the configuration file
`threadPoolSize`	Number of usable threads Possible values: Integer
`broker server`	Host and port of the broker Possible values: Host and port of the broker, separated by a semicolon
`client ID`	ID of the client with which the message is published Possible values: Any integer
`topic`	Topic that can be subscribed to in order to receive the published message. It has the following attributes: `filter`: Name of the topic filter `qos`: Quality of service
`qos`	A quality of service (QOS) can be set for topics. There are three possible QOS. This can be set in the configuration file as follows: `AT_LEAST_ONCE`: The message is delivered at least once. This is the safest option. `AT_MOST_ONCE`: There is no guarantee that the message will be delivered. The fastest option. `EXACTLY_ONCE`: The message is delivered or not delivered exactly once. Guarantees that no duplicates are delivered.
`process url`	Specifies the process in which the received data is to be used. The received data is written to the process as XML. Possible values: Path to the process Example: `"Processes/data.wrf"`
`pubSubExchange`	The parameter `pubSubExchange` contains the name of the exchange (exchange location on the broker) on publisher side, i.e. where the message has been published to. The value of this parameter must be identical in the configuration file and in the adapter parameter. Possible values: Any string
`isQueueDurable`	The parameter `isQueueDurable` defines the behavior of the subscriber queue. If the parameter is set to `true`, the subscriber queue is retained when the broker is restarted. Otherwise, all queues will be deleted when the server is restarted. Possible values: `true` `false` (default)