User guide

ExtremeWare EPICenter Software Installation and User Guide 8-33
Importing Resources
The first line simply defines the version of the import syntax:
#SYNTAX VERSION:1.0
Enter this exactly as specified.
The second line defines the mapping of the data in the file to EPICenter resources:
Resource_UniqueName <tab> Resource_Type <tab> Resource_Name [<tab> attribute ...]
• Thefirstthreeitemsarerequired,
—
Resource_UniqueName specifies that the first field maps to the unique ID.
—
Resource_Type specifies that the second field defines the resource type (user, host,
group, device, or port).
—
ResourceName specifies that the third field maps to the resource name. This is the
name that will appear as the name of the resource in the Grouping Manager.
• The remaining items on the line define the attributes that can be included for each
resource. The names you specify here will be used as the attribute names in the
Grouping Manager.
The third line defines the type of each attribute (Generic, IP/subnet, or DLCS ID).
<tab> <tab> <tab> (<attribute_type>)[<tab> (<attribute_type>)...]
Each type specifier must be enclosed by parenthesis, and separated from the preceding
type specifier by a tab. Three tabs must precede the first type specifier.
• The items in this line define the type of each attribute defined in line two. You must
include a type specification for every attribute included in line two.
• Thefirst three items in line two do not require a type (as they are predefined). You skip
these by including the three tabs before the first type specifier.
Resource Definitions
The remaining lines in the first section define the resources to be imported. Each resource
must include the uniqueID, the resource type, and a name. Attribute values are optional,
and will be assigned in the order presented on the line (separated by tabs). These lines are
formatted as follows:
uniqueID1 <tab> <resource_type> <tab> resource_name1 <tab> {attribute <tab> ... }
uniqueID2
<tab> <resource_type> <tab> resource_name2 <tab> {attribute <tab> ... }
...
uniqueIDn
<tab> <resource_type> <tab> resource_nameN <tab> {attribute <tab> ... }