The following is an example parameter file for a command line import operation from an LDAP directory. In this example, users in the LDAP directory are all stored in a single container, ou=employees; Account Import derives their position in the LDAP hierarchy by concatenating these LDAP attributes: Division, Department and Team. This example also imports e‑mail addresses and various LDAP attributes. Account Import writes these details to each CA DataMinder user account.
|
Example parameters |
Resulting action |
|---|---|
/ca |
These define the import actions: create new CA DataMinder user accounts; reorganize the existing CA DataMinder user hierarchy; and update the account attributes for CA DataMinder users. |
/re |
|
/at |
|
/sv UNI-HARDY-XP |
These specify the LDAP host server and use previously cached credentials to log on to LDAP. |
/ec |
|
/dn unipraxis.com |
These specify the LDAP root (or source container) for the import operation. |
/lr ou=employees |
|
/me |
Existing CA DataMinder users not present in the LDAP directory will be moved to an exceptions group called ‘Non‑LDAP users’. Note the use of double quotes. |
/eg "Non-LDAP users" |
|
/pd UNIPRAXIS |
User names for new CA DataMinder accounts will be prefixed with ‘UNIPRAXIS\’. The backslash is added automatically. |
|
|
|
/ua attribute6 |
Defines the ‘anchor’ LDAP attribute. This example specifies CA DataMinder user attribute 6. |
/ga Division,Department,Team |
Defines the target group for imported users, based on hierarchy from this list of LDAP attributes. |
/ml mail /ml proxyAddresses /ml legacyExchangeDN |
Updates CA DataMinder email address attributes. |
/al EmployeeID /al Department /al Team,,Rank |
Updates CA DataMinder user attributes. These /al instances write LDAP attributes to UserAttribute1 through UserAttribute3 and to UserAttribute5. Note: You cannot include ‘empty’ /al parameters; to specify non-consecutive user attributes, you must use comma delimiters. |
|
Copyright © 2014 CA.
All rights reserved.
|
|