Prior to setting up the AMQP integration, confirm that the following prerequisites are satisfied:

RabbitMQ depends on Erlang/OTP and cannot be installed or started without it. RabbitMQ 4.2.5 and Erlang/OTP 28.5 are the versions validated during DeMeter AMQP integration testing.

If RabbitMQ is set up on a different server, these ports need to be open between DeMeter and the broker

• Reliable message delivery
• Decoupled system integration
• Simplified communication between applications

The AMQP communication process follows these steps:

1. A tightening operation is completed and result is sent to the DeMeter.
2. DeMeter creates an AMQP message containing the tightening result.
3. The message is published to the RabbitMQ broker.
4. RabbitMQ receives the message and stores it in the queue defined within setings. (default: DeMeter.TighteningResults)
5. External applications consume messages from the queue whenever they are ready.

AMQP functionality is available starting with DeMeter version 26.1.1.

Earlier versions do not support AMQP export.

The recommended RabbitMQ version is 4.2.5.

This version has been fully tested with DeMeter and is the only version officially validated by Desoutter.

Although newer RabbitMQ versions may also operate correctly, they may require some additional configuration steps. Only version 4.2.5 is officially recommended and guaranteed to work.

3.3 Erlang/OTP

RabbitMQ requires Erlang/OTP to be installed before the broker itself.

The supported and tested version is:

Erlang/OTP 28.5

Newer releases should work but might need some additional configuration.

Download and install Erlang/OTP 28.5 or a newer version. https://www.erlang.org/

RabbitMQ depends on Erlang/OTP and cannot be installed or started without it.

Install RabbitMQ Server 4.2.5. https://www.rabbitmq.com/

During installation:

• the RabbitMQ Windows Service is created,
• the service is configured to start automatically,
• the default AMQP listener is enabled on TCP port 5672.

After installation, verify that the RabbitMQ service is running.

C:\Program Files\RabbitMQ Server\rabbitmq_server-4.2.5\sbin

cd C:\Program Files\RabbitMQ Server\rabbitmq_server-4.2.5\sbin

rabbitmq-plugins.bat enable rabbitmq_management

http://localhost:15672

http://<ServerName>:15672

Username: guest
Password: guest

Create a new user:
Rabbitmqctl.bat add_user user password

Grant administrator privileges:
Rabbitmqctl.bat set_user_tags user administrator

Grant permissions for the default virtual host:
Rabbitmqctl.bat set_permissions -p / user “.*” “.*” “.*”

Rabbitmqctl.bat delete_user guest

For new installations, the default configuration file is located at:

C:\Program Files\Desoutter\DeMeter\appsettings.json

Copy this file to:

C:\ProgramData\Desoutter\DeMeter\API\

Open appsettings.json in your prefered a text editor:

Locate the DataFlowExporter section – it should appear at the bottom of the file.

By default, the exporter is turned off since the IsEnabled property is commented out.

For example:

"DataFlowExporter": {
// "IsEnabled": false,

Remove the leading // and modify the value to:

"DataFlowExporter": {
"IsEnabled": true,

Furthermore, repeat the process for this section:

// "IsTighteningResults": false

so it should be updated to look like this:

"IsTighteningResults": true

// "IsCycles": false

"IsCycles": true

Inside the DataFlowExporter section, locate the nested EndPointAMQP object.

The object itself is present by default, while its configuration parameters are commented out.

To establish a connection with RabbitMQ, uncomment and configure at least the following properties:

By default, RabbitMQ requires a username and password to connect to the broker. However, if needed, it can be configured to accept connections without authentication.

Remove the leading // from each property and specify values appropriate for your environment.

Every operation that is completed produces an AMQP message which is dispatched to the respective RabbitMQ queue.

By default, DeMeter sends messages to the queue DeMeter.TighteningResults for Tightening Results and DeMeter.Cycles for Cycles.

If these queues are absent when DeMeter connects to RabbitMQ, DeMeter will automatically create them.

If you encounter an error similiar to the one below when running RabbitMQ administration commands:

C:\Program Files\RabbitMQ Server\rabbitmq_server-4.2.5\sbin>rabbitmqctl.bat add_user admin admin
Error: unable to perform an operation on node 'rabbit@<hostname>'
Please see diagnostics information and suggestions below.

The problem frequently arises from a discrepancy between the Erlang cookie employed by the RabbitMQ service and the Erlang cookie utilized by the currently logged-in Windows user.

Resolution

1. Disable RabbitMQ if it is currently running.
2. Locate the Erlang cookie utilized by the RabbitMQ Windows service:

C:\Windows\System32\config\systemprofile\.erlang.cookie

Copy the .erlang.cookie file into your user profile directory:

C:\Users\<Username>\

• If a .erlang.cookie file already be present in the user profile directory, substitute it with the file obtained from systemprofile.
• Verify that the file permissions permit access solely to the current user.
• Launch a new Command Prompt as Administrator and attempt the RabbitMQ command again.

Verify that:

• the rabbitmq_management plugin is enabled,
• RabbitMQ is running,
• TCP port 15672 is accessible.

If no messages show up in RabbitMQ following a tightening operation or the completion of a cycle, please check the following:

• Ensure that RabbitMQ is operational and that the RabbitMQ service has started successfully.
• Confirm that the DataFlow exporter is activated in the DeMeter configuration:
• Verify that the AMQP connection parameters are set up correctly:

  Host

  Port

  User

  Password

  TCP port 5672 must be accessible from DeMeter server

  Make sure that the data types you want to export are explicitly enabled (IsTighteningResults, IsCycles)