Customizing Your SPD Server Installation

The rc.spds script assumes that you want to keep the logs from messages that are written to STDOUT or STDERR of the spdsnsrv (SPD Server name server) and spdsserv (SPD Server host) processes. The rc.spds script variable LOGDIR= defines the directory where these logs are stored.

If you do not want to keep these logs, change the value for LOGDIR=, and the rc.spds script uses /dev/null. If you want to keep the logs in another location besides "InstallDir"/log, change the value of LOGDIR=.

SPD Server log files can grow very large if there is considerable activity. The log files can be configured to recycle at a given time each day and start a new logfile. The older log files can then be removed or archived.

The DSRVFILE= and DSRVTIME= spdsserv options, NSRVFILE= and NSRVTIME= spdsnsrv options, and SNSFILE= and SNSTIME= spdssnet options have the following default values in the rc.spds script to define the log name and recycle time: If you want SPD Server to disable automatic log filename generation and cycling, change those settings to empty pointers.

The rc.spds script enables you to use the SPD Server audit file facility. The audit file facility is not enabled by default. Use the following script variables to configure the SPD Server audit file facility:

For more information about SPD Server auditing, see SAS Scalable Performance Data (SPD) Server Auditing.

The rc.spds script assumes that you keep your spdsserv.parm parameter file and your SPD Server user password file in the "InstallDir"/site directory. If you do not keep the files in this location, you need to change your ACLDIR= and PARMDIR= assignments.

If you want to access SPD Server through a registered port (name service), add the following service to your /etc/inet/services or /etc/services file (if this service is not already present):

spdsname 5400/tcp # SPDS Name Service

This service defines the port number for the SPD Server name server process. Make sure that this port number matches the port number that you used when you installed SPD Server. If you are running SAS on an existing SPD Server installation, this service name is probably already defined. You can either define another service name for the SAS client to use (for example, sp45name), or you can directly include the SPD Server port number in your SAS statements.

The rc.spds script assumes that you want the spdssnet process running for clients that are accessing SPD Server data via a JDBC client. If you do not support this access, use the -nosnet option with the rc.spds script to disable start-up of the SPD SNET server.

See the section Managing SAS Scalable Performance Data (SPD) Server Passwords and Users for more information about adding users to the SPD Server psmgr database.

SPD Server user passwords can be authenticated by the SPD Server psmgr utility, or by an LDAP server (such as Microsoft Active Directory, Sun Java System Directory Server, or OpenLDAP).

LDAP authentication integrates with the SPD Server password facility and provides a centralized approach to user ID and password management. SPD Server clients that use LDAP authentication should have user accounts that are managed by the authenticating LDAP server. The user ID and password information must be stored on an LDAP server that the SPD Server can access. The user ID must be entered into the SPD Server password database through the psmgr utility or via the SAS Management Console utility. These user ID requirements exist in order to ensure that all SPD Server user information is recorded and properly propagated.

When a client uses LDAP authentication to connect to SPD Server, the LDAP server that is configured in the SPD Server's parameter file performs the authentication. After the client is verified, SPD Server uses the client's password database record for all other SPD Server operations.

For more information about SPD Server LDAP authentication, seeOverview of LDAP Authentication.

To customize configuration of the "Installdir"/site/spdsserv.parm parameter file and the "Installdir"/site/libnames.parm LIBNAME file for your installation, see Part 4, Chapters 6–13, in SAS Scalable Performance Data Server: Administrator’s Guide.