Novell IFOLDER 3.7 - SECURITY ADMINISTRATION, Administration Manual

Page: 109 / 216

Managing an iFolder Enterprise Server 109
no
vd
ocx
(e
n)
13
Ma
y 20
09
The
\fIowner-id\fR
and
\fIcollection-id\fR
are required because
\fIowner-name\fR
and
\fIcollection-name\fR
are not guaranteed to be unique. Using both the name and ID properties
to identify Collections and Collection owners provides a “friendly” name along with the required
unique identifier.
In many configurations, the names of Collections and Collection owners are unique. For example, if
Domain members are obtained from an LDAP directory, it is not likely that two members would
have the same username. Likewise, it would be unusual for an owner to give two iFolders the same
name.
Although a backup application must pass both the name and ID to TSAIF, it might display only the
name to the backup administrator to simplify the user interface. The ID would need to be displayed
to the backup administrator only when two Collections, or two Collection owners, have the same
name and the backup administrator wants to perform an operation on only one of them.
The name of the Collection or Collection owner can be obtained by stripping off the pattern
".????????-????-????-????-????????????"
from the first two components of the path TSAIF returns to the backup application.
Parameter Description
path
iFolder path such as the following:
/
/owner
/owner/collection
/owner/collection/relative-path
owner
owner-name.owner-id
owner-name
Collection owner name ( Simias.Storage.Collection.Owner.Name )
owner-id
Collection owner ID (
Simias.Storage.Collection.Owner.ID
)
collection collection-name.collection-id
collection-name
Collection name ( Simias.Storage.Collection.Name )
collection-id
Collection ID ( Simias.Storage.Collection.ID )
relative-path
Relative path such as
file
subdir
subdir/relative-path
file
name of file on file system
subdir
name of subdirectory on file system