Due to bug#1146710, if the user replaces the ssl certificate in RHEV, all RHEV tools would not work for the customer until some additional configuration is applied. Until the bug is not fixed, the documentation should advise on those additional steps. The relevant section in the Admin Guide [1] should be modified.

Suggested modifications:
1. Make it more clear that apache-ca.pm should contain a certificate chain up to the root (currently stated in step2 in [1]). 
2. Either provide links to the kcs for each tool, or specify in the documentation what files need to be modified.
Log Collector: https://access.redhat.com/solutions/458713
engine-iso-uploader: https://access.redhat.com/solutions/972573
For image-uploader, hosted-engine and host registration I do not have a (good) kcs:
https://access.redhat.com/solutions/1200943
https://bugzilla.redhat.com/show_bug.cgi?id=1254838



[1] 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Administration_Guide/appe-Red_Hat_Enterprise_Virtualization_and_SSL.html#Replacing_the_SSL_certificate_used_by_Red_Hat_Enterprise_Virtualization_Manager_to_identify_itself_to_users_connecting_over_https