|
|
|
DMSERVER/JOBS_HISTORY_MAXAGE
|
Defines a retention
period, in seconds, for the history items that are generated by batch
and profile job run instances. After the completion of a job, and
after the expiration of the specified time period, the Runtime Server
purges the job's history from memory. The server also deletes any
corresponding log files, statistics files. If the JOBS_KEEP_HISTORY
option is enabled, a history record is also deleted from history database.
The default value of
the MAXAGE option is -1, which specifies that history items are never
purged.
|
|
|
Specifies a separate
directory for job log for jobs run on this server, other than those
that are generated by batch.log.xml. Specifying a separate directory
for these log entries can improve performance when you are using the
SAS Job Monitor to collect job status information.
|
DMSERVER/JOBS_KEEP_HISTORY
|
A value of YES specifies
that the histories of job run instances are retained across server
restarts.
|
|
|
Specifies the maximum
number of orchestration jobs that the server runs simultaneously.
The default is 25. If a new job request exceeds the limit, the request
is placed in a queue.
|
|
|
Controls the size of
each log file or statistics file chunk that is sent back to the requesting
client. For log files, this option controls the number of characters
per chunk. For statistics files, this option controls the number of
bytes per chunk. The default value is 512K.
|
|
|
Specifies the name of
the Runtime Server’s metadata definition in the SAS Metadata
Repository. The server uses the value of this option at start time
to retrieve values for configuration options that are critical to
the interoperation with the SAS Metadata Server.
The value of this option
is specified during installation. Change this value only if you need
to change the name of the Runtime Server in the SAS Metadata Repository.
|
|
|
Specifies whether to
create log subdirectories for each server run instance. The default
value is NO, which specifies that log files are created in separate
subdirectories for each server run instance. The subdirectories are
located under the default server_logs directory or an alternate directory
specified in the DMSERVER/WORK_ROOT_PATH.
This option should be set to YES only in special cases, because it
puts all log files into the same directory. This makes it difficult
to determine which job logs belong to which server run instances and
server log files. Each run instance of each process (Runtime Server,
DFWFPROC) gets its own, unique log file. Therefore, each new server
run instance has to have its own log file, while pre-existing log
files, if any, are renamed.
|
|
|
The value YES enables
local security, and NO disables local security. The value of this
option is maintained in the SAS Metadata Repository. The value is
retrieved from the SAS Metadata Server when you invoke the Runtime
Server.
Note: Do not specify a value for
this option in the local configuration file during normal operation.
|
DMSERVER/SECURE/GRP_ADMIN
|
Specifies the name of
the Runtime Server
administrator group, which must already exist on the SAS Metadata
Server before Runtime Server is started. This option is required.
|
|
|
The value YES enables
SSL, and NO disables SSL. The value of this option is maintained in
the SAS Metadata Repository. The value is retrieved from the SAS Metadata
Server when you invoke the Runtime Server.
Note: Do not specify a value for
this option in the local configuration file during normal operation.
Set these additional
configurations if SSL is configured:
-
DMSERVER/SOAP/SSL/CA_CERT_FILE
-
DMSERVER/SOAP/SSL/CA_CERT_PATH
-
DMSERVER/SOAP/SSL/KEY_FILE
-
DMSERVER/SOAP/SSL/KEY_PASSWD
|
DMSERVER/SOAP/SSL/CA_CERT_FILE
|
Specifies the file where
the Certificates Authority stores trusted certificates. If this configuration
directive is not needed, comment it out.
|
DMSERVER/SOAP/SSL/CA_CERT_PATH
|
Specifies the path to
the directory where trusted certificates are stored. If this configuration
directive is not needed, comment it out.
|
DMSERVER/SOAP/SSL/KEY_FILE
|
Specifies the path to
the key file that is required when the SOAP server must authenticate
to clients. If this configuration directive is not used, comment it
out.
|
DMSERVER/SOAP/SSL/KEY_PASSWD
|
Specifies the password
for DMSERVER/SOAP/SSL/KEY_FILE. If the key file is not password protected,
this configuration should be commented out.
|
DMSERVER/THREADS/COUNT_MAX
|
Specifies the maximum
number of threads that the Runtime Server
can start. The default value is 1026 threads. If the setting is too
low, it is adjusted automatically. There is no setting for an unlimited
number of threads. For optimal performance configure the number of
threads based on the expected number of parallel clients and requests.
|
DMSERVER/THREADS/IDLE_MAX
|
Specifies the maximum
number of idle threads Runtime Server
can keep. The default is 0. If a thread becomes idle, it is terminated.
If it is needed again, it is restarted.
|
DMSERVER/THREADS/IDLE_TIMEOUT
|
Specifies the number
of microseconds before a thread is flagged as idle after it stops
doing work. The default is 0; threads are initially flagged as idle.
|
|
|
Specifies the root directory
under which Runtime Server
work and log subdirectories are created. Each time the server starts,
a new work directory is created for that instance of the server. The
name of this directory contains the server start-up date and time,
as well as the corresponding process ID. The default directory is /var/server_logs.
|