7.0

Table Of Contents
Customizing LDAP Data 4
You can use VMware and Microsoft command-line tools to import and export LDAP configuration data to
and from View. These command-line tools import and export LDAP configuration data in LDAP Data
Interchange Format (LDIF) configuration files.
This feature is intended for use by advanced administrators who want to perform automatic bulk
configuration operations. To create scripts to update the View configuration, use View PowerCLI.
This chapter includes the following topics:
n
“Introduction to LDAP Configuration Data,” on page 61
n
“Modifying LDAP Configuration Data,” on page 62
Introduction to LDAP Configuration Data
All View configuration data is stored in an LDAP directory. Each View Connection Server standard or
replica instance contains a local LDAP configuration repository and a replication agreement between each of
the View Connection Server instances. This arrangement ensures that changes to one repository are
automatically replicated to all other repositories.
When you use View Administrator to modify the View configuration, the appropriate LDAP data is
updated in the repository. For example, if you add a desktop pool, View stores information about users,
user groups, and entitlements in LDAP. View Connection Server instances manage other LDAP
configuration data automatically, and they use the information in the repository to control View operations.
You can use LDIF configuration files to perform a number of tasks, including transferring configuration data
between View Connection Server instances and backing up your View configuration so that you can restore
the state of a View Connection Server instance.
You can also use LDIF configuration files to define a large number of View objects, such as desktop pools,
and add those objects to your View Connection Server instances without having to use View Administrator
to perform the task manually.
In View 3.1 and later releases, View performs regular backups of the LDAP repository.
LDAP configuration data is transferred as plain ASCII text and conforms to the Internet Engineering Task
Force (IETF) RFC 2849 standard.
VMware, Inc.
61