Manually Starting ProfileUnity Cluster Node Services-Order of Operations

Product: ProfileUnity-FlexApp

Product Version:  6.7

Updated: Sept 5, 2017



In the event that the ProfileUnity console can not be accessed after a major disaster recovery situation, the cluster node may need to have services started manually.


The following services should be started in the listed order to manually bring the node back online.

  1. RabbitMQ


  1. MongoDB


  1. Liquidware Labs ProfileUnity Service


  1. Liquidware Labs FlexDisk Service
Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request


Article is closed for comments.