Contains SLP Service objects.
2.16.840.1.113719.1.49.6.1.1
|
Class Flags |
Setting |
|---|---|
|
Container |
On |
|
Effective |
On |
|
Nonremovable |
Off |
|
Ambiguous Naming |
Off |
|
Ambiguous Container |
Off |
|
Auxiliary Class |
Off |
|
Rule |
Class/Attribute |
Defined For |
|---|---|---|
|
Super Classes |
SLP Scope Unit |
|
|
Containment |
SLP Scope Unit SLP Scope Unit SLP Scope Unit SLP Scope Unit |
|
|
Named By |
SLP Scope Unit |
|
SLP Scope Unit |
Inherited from Top |
|---|---|
|
(None) |
|
SLP Scope Unit |
|
|---|---|
|
Inherited from Top |
|
|---|---|
|
Object Name |
Default Rights |
Affected Attributes |
Class Defined For |
|---|---|---|---|
|
[Creator] |
Supervisor |
[Entry Rights] |
Each SLP Scope Unit object contains all the SLP Service objects found in the specified scope or scopes. Since this is an eDirectory container object, it can become its own partition, which can then be replicated and placed on a server in any location that needs service information.
In a typical eDirectory tree, the tree will contain one SLP Scope Unit object with a scope for each geographically separate location (for example, a scope for Provo and a scope for San Jose). The object would be its own partition, and a replica would be placed in Provo and San Jose. The San Jose replica would keep the San Jose services current, and eDirectory would synchronize the For LDAP clients to access this class, the LDAP server must map this class to a name that contains no spaces or colons.information with the Provo replica. The Provo services would be kept current in Provo, and then synchronized with San Jose. Both sites would contain a complete list of available services.
The SLP Directory Agent object obtains its rights to SLP Service objects from the SLP Scope Unit object. The SLP Scope Unit object should have Read, Write, and Browse rights to the objects in its container. The agent control over the SLP Service objects can be restricted by modifying these rights.
For help in understanding the class definition template, see Reading Class Definitions.
For LDAP clients to access this class, the LDAP server must map this class to a name that contains no spaces or colons.