SAS Safety Scalable Performance Data Server 4.5 Manual Do Utilizador

If no distinguished name is specified in the spdsserv.parm file, SPD Server uses the LDAP
Server host's domain name to generate values for

, 

, and 

. The SPD Server

user ID becomes the value for 

. The resulting value becomes the default user location

for LDAP database members.

For example, suppose the LDAP host machine is sunhost.unx.sun.com and the user ID is
sunjws. The resulting default distinguished name is the following:

"uid=sunjws, dc=unx, dc=sun, dc=com".  

The distinguished name is used to locate the user sunjws. Then the sunjws user password
is compared to the password that is stored in the LDAP database. If there is a specific
location for SPD Server users in your LDAP database, be sure to specify it using
LDAPBINDDN.

See the LDAP Server administrator for your site if you need more information about LDAP
parameters for your spdsserv.parm file. To use the default value for any LDAP parameter,
omit the parameter specification from the spdsserv.parm file. Undeclared parameters
automatically assume default values.

Note: Entering the LDAP_HOST value for LDAPSERVER can cause SPD Server to fail

during start-up.

The SPD Server administrator performs the maintenance and configuration functions for
SPD Server. Here are some guidelines for administrators:

The SPD Server administrator needs a UNIX login ID on the SPD Server machine. Other
SPD Server users do not need UNIX login IDs. You can control their access to SPD Server
data resources using the SPD Server password facility without giving them specific login
accounts. This adds a measure of security and control and SPD Server users are permitted
physical access to the SPD Server machine.

You should add the 

 directory to your PATH using your shell's login

script. ksh users should modify .profile or .kshrc files. csh users should modify .login
or .cshrc files, depending on where they currently set the PATH environment variable. This
makes invoking the various SPD Server utility programs much easier.

SAS recommends that you run your SPD Server environment using the same UNIX user
ID that was used to install SPD Server on the server machine. The user ID should also be
the SPD Server administrator's user ID. The common user ID minimizes potential problems
with file ownership and system access permissions on the server machine. You add SPD
Server access controls to the resources created with SPD Server by using SPD Server user
IDs and SPD Server ACLs. The SPD Server user IDs and ACLs provide fine-grained access
controls to the SPD Server data resources.

Regardless of how the SPD Server run-time environment is configured, SPD Server
processes always run with some UNIX user ID. That UNIX user ID owns all of the files
that the SPD Server process creates. The UNIX user ID is governed by UNIX file access
permissions. Remember this when starting SPD Server processes and running SPD Server
administrator utilities! Otherwise, it is possible to create files with ownership and
permissions that deny required access to the SPD Server processes. Performing all SPD
Server installation and administration tasks from the same UNIX user ID makes subsequent
SPD Server use much easier.