Extreme Networks EPICenter 6.0, Reference Manual

Page: 245 / 580

Importing Resources
EPICenter Reference Guide
245
If your LDAP directory is organized differently, you can modify the
LDAPConfig.txt
file to meet your
individual needs. This requires that you understand the organizational structure of the directory from
which you want to import data.
The
LDAPConfig.txt
file must include the following entries:
base
: Specifies the LDAP naming context. Leave this blank to use the default LDAP naming context.
This is required.
attributes
: Specifies the attributes that you want to import into the EPICenter database from
entries in the LDAP directory. By default, all imported attributes are considered type Generic.You
can specify an EPICenter attribute type (Generic, IP/subnet, or Netlogin ID) by enclosing both the
attribute name and the EPICenter attribute type in curly brackets, as shown:
{uid {Netlogin ID}}
.
This is required.
uniqueID
: Specifies the attribute that should be used in the EPICenter database as the ID for this
resource. This is required.
scope
: The scope of the search (base, sub, one). This is required.
groupBy
: The attribute that should be used to create EPICenter sub-groups within the imported
group structure. This is optional.
memberNameAttribute
: The attribute that should be used to define the child entry in a group.
resourceName
: The attribute that should be used as the displayed name of the resource within the
EPICenter Grouping Manager. This is required.
filterList
: Defines the search criteria. Because of the limits on the amount of data that a search
returns in one operation, you may need to split your search into multiple operations, as is done in
the example file. This is required.
objectClassMapping
: This maps an LDAP entry to a Grouping Manager resource type based on the
object class of the entry. You will need multiple entries of this type. The name-value pair contains the
EPICenter resource type on the left, and either the LDAP object class specification or an EPICenter
resource type of the right.
For example, the following line specifies that entries whose object class is “organizationalPerson”
should be imported as user resources.
objectClassMapping: user=organizationalPerson person Top
The following line specifies that user resources can be group members.
objectClassMapping: groupmember=user
At least one mapping specification is required. You can comment out resource types that you don’t
need to use in the sample file, or leave them. They are ignored if not defined.
Importing from a File
To import data from a text file, you define the resources you want to import in a tab-delimited text file.
The elements on each line are separated by tabs.
The Import File Format
The simplest way to create this file is to enter it in a spreadsheet program such as Microsoft Excel, and
then export it as tab-delimited text.
The elements on each line are separated by tabs.