6.1

8 Verify or, if necessary, change the port number used for View Composer.
a Edit the configuration for the vCenter Server instance and make sure that the View Composer port
is set to 18443.
The port number must match the port number specified during the View Composer upgrade.
b Supply the vCenter Server password.
c Select the Enable View Composer check box and click OK.
9 Log in to View Administrator and examine the dashboard to verify that the vCenter Server and View
Composer icons are green.
If either of these icons is red and an Invalid Certificate Detected dialog box appears, you must click
Verify and either accept the thumbprint of the untrusted certificate, as described in "What to Do Next,"
or install a valid CA-signed SSL certificate.
For information about replacing the default certificate for vCenter Server, see the VMware vSphere
Examples and Scenarios document.
What to do next
To use a default or self-signed certificate from vCenter Server or View Composer, see “Accept the
Thumbprint of a Default SSL Certificate,” on page 36.
If the upgrade fails on one or more of the View Connection Server instances, see “Create a Replicated Group
After Reverting View Connection Server to a Snapshot,” on page 38.
If the upgrade is successful, upgrade the other View server components. If you use security servers, see
“Upgrade View Security Server,” on page 39.
IMPORTANT If you plan to use enhanced message security mode for JMS messages, make sure that firewalls
allow View Connection Server instances to receive incoming JMS traffic on port 4002 from desktops and
security servers. Also open port 4101 to accept connections from other View Connection Server instances.
If you ever reinstall View Connection Server on a server that has a data collector set configured to monitor
performance data, stop the data collector set and start it again.
Accept the Thumbprint of a Default SSL Certificate
When you add vCenter Server and View Composer instances to View, you must ensure that the SSL
certificates that are used for the vCenter Server and View Composer instances are valid and trusted by View
Connection Server. If the default certificates that are installed with vCenter Server and View Composer are
still in place, you must determine whether to accept these certificates' thumbprints.
If a vCenter Server or View Composer instance is configured with a certificate that is signed by a CA, and
the root certificate is trusted by View Connection Server, you do not have to accept the certificate
thumbprint. No action is required.
If you replace a default certificate with a certificate that is signed by a CA, but View Connection Server does
not trust the root certificate, you must determine whether to accept the certificate thumbprint. A thumbprint
is a cryptographic hash of a certificate. The thumbprint is used to quickly determine if a presented certificate
is the same as another certificate, such as the certificate that was accepted previously.
NOTE If you install vCenter Server and View Composer on the same Windows Server host, they can use the
same SSL certificate, but you must configure the certificate separately for each component.
For details about configuring SSL certificates, see "Configuring SSL Certificates for View Servers" in the View
Installation document.
View Upgrades
36 VMware, Inc.