Customizing Your SPD Server Installation :: SAS(R) Scalable Performance Data Server 5.2: Administrator's Guide, Second Edition

Logging

The InstallDir\site\*.bat files for the spdsnsrv, spdsserv, and spdssnet assume that you want to keep the logs from messages that are written to STDOUT or STDERR by the SPD Server name server (spdsnsrv), the SPD Server host (spdsserv), or the SPD Server SNET server (spdssnet). These processes are logged to the InstallDir\log\ directory.

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.

To alter the name, location, or cycle time to generate a new logfile, modify the following start-up parameters for the spdsserv, spdsnsrv, or spdssnet processes in their respective batch files:

-logfile fileSpec

specifies that the logger process automatically creates a server log file. fileSpec specifies a partial pathname or filename specification that is used to generate the complete log file path.

For example, if you specify fileSpec as c:\logs\spdsnsrv, the name c:\logs\spdsnsrv_mmddyyyy_hh:mm:ss.spdslog is generated. The values mmddyyyy and hh:mm:ss indicate the time at which the system created the log file.

-logtime hh:mm

specifies the time of day at which to cycle a new generation of the name server log file. At this time each day, the previous log file is closed and a new log file is opened. For example, -logtime 00:00 cycles the log at midnight.

Audit File Facility

The "Installdir"\site\spdsserv.bat file enables you to use the SPD Server audit file facility. The audit file facility is not enabled by default. Use the following start-up parameters to the spdsserv process to configure the SPD Server audit file facility:

-auditfile fileSpec

enables proxy audit logging for the server, and enables automatic audit log file creation by the audit process. The parameter fileSpec specifies a path or filename that is used to generate the complete audit file path.

For example, if you specify fileSpec as \audit\spds, the generated name will be \audit\spds_mmddyyyy_hh:mm:ss.spdsaudit, where mmddyyyy is the system date when the log file was created.

-sqlauditfile fileSpec

enables SQL audit logging for the server, and enables automatic audit log file creation by the audit process. The parameter fileSpec specifies a path or filename that is used to generate the complete SQL audit file path. For example, if you specify fileSpec as \audit\spdssql, the generated name will be \audit\spdssql_mmddyyyy_hh:mm:ss.spdsaudit, where mmddyyyy is the system date when the log file was created.

-audittime hh:mm

specifies the time of day to cycle a new generation of the audit log file or SQL audit log file. At this time each day, the previous log file is closed and a new log file is opened. For example, -audittime 00:00 cycles the logs at midnight. For more information about SPD Server auditing, see SAS Scalable Performance Data (SPD) Server Auditing.

User Password and Parameter Files

The spdsserv.bat file 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 the following start-up parameters:

-parmfile file-spec

specifies an explicit file path for the SPD Server host's parameter file. This file is mandatory and contains any SPD Server options. If this option is omitted, the SPD Server host assumes that a parameter file named spdsserv.parm is in the process's current working directory.

-libnamefile file-spec

specifies the name of the file that contains the logical LIBNAME domain definitions that the SPD Server host supports.

.

Accessing SPD Server through a Registered Port

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.

Adding Users to the SPD Server psmgr Database

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.

Authenticating SPD Server User Passwords

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.

Customizing SPD Server Configuration

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.

Install SPD Server as a Service

You can use Windows Services to start SPD Server. To install the services that start the SPD Server name server, the SPD Server Data Server, and the SPD Server SNET server, select Start

All Programs

SAS

Utilities

Install SPD 5.1 as a Service.

Select Start

All Programs

SAS

Utilities

Start SPD 5.1 as a Service to manually start the SPD Server service.

Select Start

All Programs

SAS

Utilities

Stop SPD 5.1 as a Service to manually stop the SPD Server service.

After you install SPD Server as a service, you can verify SPD Server services via Windows Services. To open the Windows Services window, select Start

Control Panel

Administrative Tools

Services.

The main panel of Windows Services contains a sortable list of Windows services. Scroll down the Services list to find entries for the SPD Server 5.1 services.

Most users want to configure SPD Server to automatically start and stop when they start and stop Windows. The Automatic setting starts the name server, data server, and SNET server without prompting. The same setting also stops the services without prompting when you close Windows.

Here is how to configure SPD Server to automatically start and stop when users start and stop Windows:

In the Window Services window, scroll down the Services list to find the entry for SPD Server 5.1 Name Server.
Select the name server service in the list, right-click on it, and select Properties. The Properties window appears.
Select Automatic from the Start-up type list. This setting configures the SPD Server Name server service to automatically start and stop with the Windows operating environment. Click OK to apply the changes and close the window.
Repeat this process to change the Start-up type setting for the SPD Server data server and the SPD Server SNET Server. At this point, your name server, data server, and SNET Server services are configured to automatically start and stop with the Windows operating environment.

Note: The first time you set your SPD Server services to Automatic, you need to manually start them by selecting StartAll ProgramsSASUtilitiesStart SPD Server 5.1 Services. After you manually start the services, they will automatically start and stop with Windows.