7.2

Model Manager Server Specifications
Specify the Model Manager server name by using a fully qualied domain name (FQDN). Do not use an IP
address to specify the server.
Security
vRealize Automation uses SSL to ensure secure communication among components. Passphrases are used
for secure database storage.
For more information see “Certicate Trust Requirements in a Distributed Deployment,” on page 63.
Certificates
vRealize Automation uses SSL certicates for secure communication among IaaS components and instances
of the vRealize Automation appliance. The appliances and the Windows installation machines exchange
these certicates to establish a trusted connection. You can obtain certicates from an internal or external
certicate authority, or generate self-signed certicates during the deployment process for each component.
For important information about troubleshooting, support, and trust requirements for certicates, see
VMware Knowledge Base article 2106583.
You can update or replace certicates after deployment. For example, a certicate may expire or you may
choose to use self-signed certicates during your initial deployment, but then obtain certicates from a
trusted authority before going live with your vRealize Automation implementation.
Table 2‑9. Certificate Implementations
Component
Minimal Deployment (non-
production) Distributed Deployment (production-ready)
vRealize
Automation
Appliance
Generate a self-signed certicate
during appliance conguration.
For each appliance cluster, you can use a certicate from an
internal or external certicate authority. Multi-use and
wildcard certicates are supported.
IaaS Components During installation, accept the
generated self-signed certicates or
select certicate suppression.
Obtain a multi-use certicate, such as a Subject Alternative
Name (SAN) certicate, from an internal or external certicate
authority that your Web client trusts.
Certificate Chains
If you use certicate chains, specify the certicates in the following order.
n
Client/server certicate signed by the intermediate CA certicate
n
One or more intermediate certicates
n
A root CA certicate
Include the BEGIN CERTIFICATE header and END CERTIFICATE footer for each certicate when you
import certicates.
Extracting Certificates and Private Keys
Certicates that you use with the virtual appliances must be in the PEM le format.
The examples in the following table use Gnu openssl commands to extract the certicate information you
need to congure the virtual appliances.
Installing vRealize Automation
30 VMware, Inc.