This is fairly easy with the new web proxy. I assume the MiCollab name resolves externally to either on or both mbg's. In each make sure the connectors are enabled for micollab, nupoint , I usually put the MiCollab ip address. I also like to add the micollabe to host names on the mbgs and resolve to the proper address. For the proxy you add 4443 to the single awv. Then in awv you need to set both internal and external ports to 4443 and have the fqdn of the micollab as this server also.
I also hope you resolve a second name also externally to the the mbg usually itself for client deployment. In a simple setup, mgb.fqdn and micollab. fqdn resolve externally to the web proxy which has a certificate that has both the true server and whatever additional alternate names. Micollab certificate only needs itself in most cases when using the web proxy
