Allow the ThingWorx Flow installer to accept an external RabbitMQ instance

[Alessio]

The current ThingWorx Flow installer does not have the option to use an existing RabbitMQ instance and provides its own.

There are two problems with this configuration:

1. A customer might need to have multiple RabbitMQ instances running, one used by ThingWorx Flow, the others being those pre-existing the ThingWorx Flow installation   
2. In those systems where RabbitMQ requires a custom installation, ThingWorx Flow cannot be installed

 An example of point 2 above is the following: https://stackoverflow.com/questions/18495874/failed-to-create-cookie-file-rabbitmq-in-windows

This is a known issue with RabbitMQ: on some Windows systems it cannot be installed if the home drive is on a shared location, which causes the .erlang.cookie not being written during RabbitMQ installation.

This RabbitMQ problem can be overcome with a different RabbitMQ installation process, but the ThingWorx Flow installer does not allow changing it. 

[olivierlp]

Economy of resources certainly makes sense.

However, there are performance, reliability and compatibility issues to consider when you take this route.

For example, if RabbitMQ goes down, are you OK with everything it supports going down too?

If one product requires version X of RabbitMQ and the other version Y, do you upgrade it and risk an incompatibility/support probblem or forgo an upgrade to keep things stable and supportable?

This seems to be an ideal application for containerization and or virtualization.

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.