You do not have to configure SSL certificates for View Transfer Server if you are installing View 5.1 or later.

A default, self-signed certificate is installed with View Transfer Server that View Connection Server uses to handle secondary connections to View clients.

When you add View Transfer Server to View, View Connection Server establishes a trust relationship with View Transfer Server. Communications between View Connection Server and View Transfer Server use Java Message Service (JMS). Messages containing sensitive data are encrypted.

When a View client requests a data transfer operation, which requires connecting to View Transfer Server, View Connection Server sends the thumbprint of the View Transfer Server certificate to the client. When the client connects to the Apache server that is associated with View Transfer Server, View Client verifies that the thumbprint passed from View Connection Server matches the certificate thumbprint on the Apache server.

Replacing the default certificate for View Transfer Server with a certificate that is signed by a CA would not significantly affect the secure communications between View Transfer Server, View Connection Server, and View clients.

In View 5.0.x and earlier versions, you did have to configure an SSL certificate for View Transfer Server.

If you are upgrading from View 5.0.x or earlier to View 5.1 or later, and you want to continue to use a certificate that is signed by a CA on the upgraded version of View Transfer Server, you must back up the certificate, upgrade View Transfer Server, and configure the signed certificate for the new View Transfer Server version.

If you configured a self-signed certificate for the old View Transfer Server, or you do not intend to use an existing CA-signed certificate on the upgraded server, you do not have to configure a certificate again. During the upgrade, a valid, self-signed certificate is installed with View Transfer Server.

For more information, see the VMware Horizon View Upgrades document.