1.1.0
Table Of Contents
- Lifecycle Manager Installation and Configuration Guide
- Contents
- Updated Information
- About This Book
- Understanding LCM
- LCM Installation Process
- Installing and Configuring Orchestrator
- Orchestrator System Requirements
- Install Orchestrator
- Orchestrator Components Setup Guidelines
- Configuring Orchestrator
- Check Configuration Readiness
- Log In to the Orchestrator Configuration Interface
- Change the Default Password
- Configure the Network Connection
- Import the vCenter SSL Certificate
- Configuring LDAP Settings
- Password Encryption and Hashing Mechanism
- Configure the Database Connection
- Server Certificate
- Configure the Default Plug-Ins
- Import the vCenter Server License
- Start the Orchestrator Server
- Export the Orchestrator Configuration
- Import the Orchestrator Configuration
- Configure the Maximum Number of Events and Runs
- Change the Web View SSL Certificate
- Define the Server Log Level
- Maintenance and Recovery
- Controlling Orchestrator Access
- Installing and Configuring LCM
- Installing LCM
- Migrating to LCM 1.1
- Configuring LCM
- Check Configuration Readiness
- Initial Configuration of Lifecycle Manager
- Configure the LCM Web View
- Set Approval Requirements
- Configure Archiving Settings
- Change Authorization Groups
- Change the Naming Convention for Virtual Machines
- Enable Email Notifications
- Configure Email Notification Content
- Configure Currency and Date Formats
- Uninstall LCM and Orchestrator
- Index
3 (Optional) Enter a password to protect the configuration file.
Use the same password when you import the configuration.
4 Click Export.
5 Click Save when prompted.
You can use the vmo_config_
dateReference
.vmoconfig file to clone or to restore the system.
What to do next
For a list of exported configuration settings, see “Orchestrator Configuration Files,” on page 43.
Orchestrator Configuration Files
When you export the system configuration, a vmo_config_
dateReference
.vmoconfig file is created locally. It
contains all the Orchestrator configuration files.
NOTE Some of the configuration files that are created during the export are empty. For example, the server
file is empty because the startup options for the Orchestrator server are individual for each machine where the
Orchestrator server is installed. These empty files must be reconfigured, even when a working configuration
was previously imported.
Table 6-5 contains a list of the settings that are not saved during configuration export.
Table 6-5. Settings Not Saved During Configuration Export
File Description
certificate Certificates are not exported. Most certificates are stored in
the Orchestrator database. However, the vCenter Server
certificate is not stored in the database. You must store it in
a separate location, or import it again when you import an
Orchestrator configuration.
licenses Licenses are not exported. They are stored in the Orchestrator
database.
server The server configuration is reset to Unknown. You must
install the Orchestrator server as a Windows service again.
Table 6-6 contains a list of the settings that are saved during configuration export.
Table 6-6. Settings Saved During Configuration Export
File Description
general The maximum number of completed events and workflows
recorded, and the Web view development and configuration.
network The IP binding address and the TCP ports used by the
different elements of the Orchestrator server.
database The database configuration.
ldap The LDAP server configuration.
log The log settings information.
plug-ins The list of disabled plug-ins and the account name.
mail plug-in The SMTP host, SMTP port, user name, password, sender's
name, sender's address.
vCenter 4.0 plug-in The vCenter 4.0 plug-in configuration.
Chapter 6 Configuring Orchestrator
VMware, Inc. 43