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
3 Define the User lookup base.
This is the LDAP container (the top level domain name or organizational unit) where Orchestrator searches
for potential users.
a Click Search and type the top-level domain name or organizational unit.
Searching for company returns dc=company,dc=org and other common names containing the search
term. If you type dc=company,dc=org as a search term, no results are found.
b Click the LDAP connection string for the discovered branch to insert it in the User lookup base text
box.
If no matches are found, check your LDAP connection string in the main LDAP page.
NOTE You can connect to the Global Catalog Server through port 3268. It issues LDAP referrals which
Orchestrator follows to find the account or group in a subdomain.
4 Define the Group lookup base.
This is the LDAP container where Orchestrator looks up groups.
a Click Search and type the top-level domain name or organizational unit.
b Click the LDAP string for the discovered branch to insert it in the Group lookup base text box.
5 Define the vCO Admin group.
This must be an LDAP group (like Domain Users) to which you grant administrative privileges for
Orchestrator.
a Click Search and type the top-level group name.
b Click the LDAP string for the discovered branch to insert it in the vCO Admin group text box.
6 Click the Test Login tab and type credentials for a user to test whether they can access the Orchestrator
smart client.
After a successful login, the system checks if the user is in the Orchestrator Administrator group.
What to do next
Define the LDAP search options and apply your changes.
Define the LDAP Search Options
You can customize the LDAP search queries and make searching in LDAP more effective.
Procedure
1 Log in to the Orchestrator configuration interface as vmware.
2 Click LDAP.
3 In the Request timeout text box, enter a value in milliseconds.
This value determines the period during which the Orchestrator server sends a query to the service
directory, the directory searches, and sends a reply. If the timeout period elapses, modify this value to
check whether the timeout occurs in the Orchestrator server.
4 (Optional) For all links to be followed before the search operation is performed, select the Dereference
links check box.
Sun Java System Directory Server does not support reference links. If you are using it, you must select the
Dereference links check box.
Chapter 6 Configuring Orchestrator
VMware, Inc. 37










