Support Required – RabbitMQ Integration Challenges

Hello team,

We’d like your support with regards to a suspected RabbitMQ challenge that we are currently experiencing on an integration project within the business.

To provide context at a high level, we are looking to communicate with a 3^rd Party Service Provider via RabbitMQ. We will thus publish a payload of an event in the business to their RabbitMQ instance.

Herewith are some challenges we are currently facing:

1. When trying to add a new RabbitMQ source, we are unable to save the source due to the error in the screenshot below:

2. We then changed the host of the RabbitMQ source, now the URL is specified without https:// and we received a different error in the screenshot below: (Possible DNS issue? - Please note, also unable to save the source)

3. We were able to get around the above challenge by editing the RabbitMQ source file outside of Warewolf in NotePad++.

4. When we continued testing, we saw that we are running into a different challenge at the point of publishing the payload to their RabbitMQ instance, error reflecting in the screenshot below:

5. We also further observed that the service providers is using quorum as a queue type, compared to the normal Classical queue type that we normally use, as represented below:

6. Another difference we observed was that the 3^rd Party was using a / in the name of their Virtual Host.

7.We were successfully able to test via Postman, as per the screenshot below:

Herewith the details used for the RabbitMQ source: (Please obtain password from Elmans)

https://za-rabbitmq.20.87.64.78.sslip.io
5672
UnlimitedStaging
Password – (obtain from Elmans)
/UnlimitedStaging

Looking forward to your feedback.

Regards,

Wynand