Represents servers that provide NCP transport and session services.
ncpServer
Class Flags |
Setting |
---|---|
Container |
Off |
Effective |
On |
Nonremovable |
On |
Ambiguous Naming |
Off |
Ambiguous Container |
Off |
Auxiliary Class |
Off |
Rule |
Class/Attribute |
Defined For |
---|---|---|
Super Classes |
NCP Server |
|
Containment |
||
Named By |
NCP Server |
Inherited from Top |
Inherited from Server |
---|---|---|
|
NCP Server |
|
---|---|
Inherited from Top |
|
---|---|
Inherited from Server |
|
---|---|
For help in understanding the class definition template, see Reading Class Definitions.
Individual services on an NCP server do not need distinct eDirectory names, since they can all share a common NCP session. However, individual resources on a server may require distinct eDirectory entries. For example, if a server supports file services and queue management services, that server will have only one object in the eDirectory tree for the server itself. Other eDirectory entries would denote the individual queues and the volumes for files.
The Supported Services attribute lists NCP-based services or features available at this network address. It should not be used to list other non-NCP services residing on the same host.
The Operator attribute is used by the NCP server as an ACL. If an object is listed in this attribute, that object is allowed to perform remote-console operations.
The NCP Server class is intended to represent both bindery-based and eDirectory-based NCP servers. The Version attribute (inherited from Server) should distinguish one type of server from the other
The Private Key and Public Key attributes are present if the server is a client of eDirectory authentication services. The Resource attribute contains a list of resources managed by this service.
The User attribute contains a list of objects that are authorized to use this server. The server must determine if the user list is to be maintained by an administrator, or if the list is automatically generated by the server. If the user list is used by the server as an ACL, the administrator usually maintains the list. If the user list is purely informational, reflecting access control information stored elsewhere, the server usually maintains the list.
The LDAP server maps requests for the ncpServer class to this class.