AMQP
AMQP Integration enables Manufacturing Connect Edge to connect with an AMQP 0-9-1 broker over TCP or SSL/TLS.
Supported communication
- Outbound (Publish data from Edge to AMQP broker) - Yes
- Inbound (Subscribe data from AMQP broker to Edge) - No
Configurations
Field | Details | Required |
|---|---|---|
Name | Connector instance name. | Yes |
Connection Type | Choose tcp for an unencrypted connection or ssl for a TLS-encrypted connection to the AMQP broker. | Yes |
Hostname | IP Address or hostname of AMQP broker (must be reachable from Edge system). | Yes |
Port | TCP port the AMQP broker listens on. | Yes |
CA Certificate | CA certificate used to verify the server, in PEM format. Can also be installed in the system-wide certificate store. | Yes |
Certificate | Client certificate for mutual TLS authentication with the AMQP broker. Paste the PEM-encoded certificate here. | No |
Private key | Private key corresponding to the client certificate. Must match the certificate provided above. | No |
Virtual host | AMQP virtual host to connect to; it scopes the exchanges and queues this connector uses. | No |
Authentication | Authentication mode: plain logs in with username and password; anonymous connects without credentials (SASL ANONYMOUS, the broker must allow it). | No |
Username | Username for authenticating with the AMQP broker. | No |
Password | Password for authenticating with the AMQP broker. | No |
Exchange | AMQP exchange to publish to and bind subscriptions on; empty uses the default exchange. | No |
Exchange type | Exchange type: direct, fanout, topic or x-custom. | No |
Exchange durable | Declare the exchange as durable. | No |
Exchange auto delete | Delete the exchange when no longer used. | No |
Exchange internal | Declare the exchange as internal. | No |
Exchange no wait | Declare the exchange without waiting for server confirmation. | No |
Routing key | Default routing key for published messages. | Yes |
ISO8601 timestamp | Convert timestamp to ISO8601. | No |
Parallel Publish Count | The number of simultaneously publishing messages. | No |
Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No |
Persistent storage configurations
Field | Details | Required |
|---|---|---|
Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages are retained and eventually sent when the connection is restored. | No |
Persistent storage size limit | Set the size limit for storing persisted data in GB. | No |
Queue mode | Select the sequence of data transfer: FIFO or LIFO. Selecting FIFO (First In First Out) sends the earliest message first. Selecting LIFO (Last In First Out) sends the latest message first. | No |