1.2.0
Table Of Contents
- Lifecycle Manager Installation and Configuration Guide
- Contents
- About This Book
- Introducing LCM
- Installing and Configuring Orchestrator
- Orchestrator Components Setup Guidelines
- Install Orchestrator
- Configuring Orchestrator
- Check Configuration Readiness
- Log In to the Orchestrator Configuration Interface
- Change the Default Password
- Revert to the Default Password for Orchestrator Configuration
- Configure the Network Connection
- Change the Default Configuration Ports on the Orchestrator Client Side
- 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
- 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
- Upgrading Orchestrator and LCM
- Uninstall LCM and Orchestrator
- Index
Upgrading to Orchestrator 4.1 and
LCM 1.2 11
If you are using LCM 1.1.x and Orchestrator 4.0.1, you can upgrade to LCM 1.2 and Orchestrator 4.1.
You must upgrade both LCM and Orchestrator. LCM 1.1.x is not compatible with Orchestrator 4.1, and LCM 1.2
is not compatible with Orchestrator 4.0.1.
This chapter includes the following topics:
n
“Backing Up Database Tables,” on page 75
n
“Back Up Modified and Custom Orchestrator Elements,” on page 75
n
“Upgrading an Installation Running on a 32-Bit Machine,” on page 76
n
“Upgrading an Installation Running on a 64-Bit Machine,” on page 77
n
“Upgrading the vCenter Server Environment,” on page 77
Backing Up Database Tables
Before upgrading, you should back up your LCM database table, LCM networking database table, and
Orchestrator database table.
The LCM database table contains virtual-machine-specific data that is managed by LCM, such as when the
virtual machine was created, who created it, and other specifications.
The LCM networking database table contains data related to the management of the IP addresses.
The Orchestrator database table contains all data related to Orchestrator. If you are using a common database
for LCM and Orchestrator, it also contains all data related to LCM.
NOTE Backing up database tables is optional, but you should consider using backup for databases in a
production environment. The backup procedure depends on your database vendor.
Back Up Modified and Custom Orchestrator Elements
When you upgrade Orchestrator, elements with a higher version number silently overwrite the elements stored
in the Orchestrator database. For example, if you have edited any standard workflows, actions, policies, Web
views, or configuration elements and you import a package containing the same elements with 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.
Prerequisites
See the vCenter Orchestrator Administration Guide for details about creating and exporting packages.
Log in to the Orchestrator client application.
VMware, Inc.
75