The directory service must contain information about servers accessed by your Open Client. Use dscp to modify interfaces and to add servers to an LDAP service.
A directory service identifies a server entry as a directory object. Each directory object has a unique set of attributes, recognized by Client-Library and Server-Library, as shown in Table 5-3:
Attribute |
Description |
|---|---|
Server Object Version |
Symbolic integer code for the version of the object definition. Sybase provides this attribute to identify future changes to the object definition. |
Server Name |
A string value that specifies the server’s name. The name can be any string that is 512 or less bytes long. Do not confuse a server name attribute with the name used to locate the directory entry. The latter is the fully qualified name for the directory entry, expressed in the name syntax of the directory provider. To avoid confusion, administrators should verify that the name attribute at least partially matches the server’s fully-qualified name (for example, the attribute value could be the entry’s common name). |
Server Service |
A string value that describes the service that the server provides. The service value can be any string that is 512 bytes long or less. |
Server Status |
Symbolic integer code that describes the operating status of the server. Valid values are: 1 - Active 2 - Stopped 3 - Failed 4 - Unknown |
Transport Address |
One or more transport addresses for the server. The transport address attribute has two elements:
|
Security Mechanism |
Object identifier strings (OID) that specify the security mechanisms supported by the server. This attribute is optional. If it is omitted, the Open Server allows clients to connect with any security mechanism for which the Open Server has a corresponding security driver. (See “Server-Library and security services” for process details.) See “The objectid.dat file” for more information about object identifier strings. See the [SECMECH] section of $SYBASE/config/objectid.dat for examples. |
