5.5

7 Browse and select Trusted Root Certification Authorities.
8 Complete the wizard and restart Internet Explorer.
9 Navigate to the Orchestrator server over your SSL connection.
You no longer receive warnings and you do not receive a Certificate Error on the right within the address
bar.
Other applications and systems (such as VMware Service Manager) must have access to the Orchestrator
SOAP and REST APIs over SSL connection.
Change the Certificate of the Orchestrator Appliance Management Site
The Orchestrator Appliance uses light-httpd to run its own management site. You can change the SSL
certificate of the Orchestrator Appliance management site, for example if your company security policy
requires you to use its SSL certificates.
Prerequisites
By default the Orchestrator Appliance SSL certificate and private key are stored in a PEM file, which is
located at: /opt/vmware/etc/lighttpd/server.pem. To install a new certificate, ensure that you export your
new SSL certificate and private key from the Java keystore to a PEM file.
Procedure
1 Log in to the Orchestrator Appliance Linux console as root.
2 Locate the /opt/vmware/etc/lighttpd/lighttpd.conf file and open it in an editor.
3 Find the following line:
#### SSL engine
ssl.engine = "enable"
ssl.pemfile = "/opt/vmware/etc/lighttpd/server.pem"
4 Change the ssl.pemfile attribute to point to the PEM file containing your new SSL certificate and
private key.
5 Save the lighttpd.conf file.
6 Run the following command to restart the light-httpd server.
service vami-lighttp restart
You successfully changed the certificate of the Orchestrator Appliance management site.
Back Up the Orchestrator Configuration and Elements
You can take a snapshot of your system configuration at any moment and import this configuration into a
new Orchestrator instance to back up your Orchestrator configuration. You can also back up the
Orchestrator elements that you modified.
If you edit any standard workflows, actions, policies, Web views, or configuration elements, and then
import a package containing the same elements with a higher version number, your changes to the elements
are lost. To make modified and custom elements available after the upgrade, you must export them in a
package before you start the upgrade procedure.
Each Orchestrator server instance has unique certificates and each vCenter Server plug-in instance has a
unique ID. The certificates and the unique ID define the identity of the Orchestrator server and the
vCenter Server plug-in. If you do not export the Orchestrator configuration or back up the Orchestrator
elements for backup purposes, make sure that you change these identifiers.
Chapter 9 Configuration Use Cases and Troubleshooting
VMware, Inc. 103