The configuration of the DataFlux Data Management Server
is specified in the server definition on the SAS Metadata Server,
and in the following configuration files:
The configuration files are stored in the server’s
etc directory.
It is important to note
that all of the configuration options in these local files override
(or replace) any other option value that might be set elsewhere. The
precedence of local option values is of primary importance with regard
to the files dmserver.cfg and app.cfg.
The app.cfg file contains
values that pertain to the execution of jobs and services. Jobs and
services are developed and tested in DataFlux Data Management Studio,
and then uploaded to the server for execution. Both DataFlux Data
Management Studio and DataFlux Data Management Server maintain their
own instances of app.cfg. It is important to maintain the same app.cfg
file on the DataFlux Data Management Server and on all instances of
DataFlux Data Management Studio that supply jobs to that server. When
you maintain a consistent app.cfg file, you help ensure that jobs
and services run on the server in the same way that they were developed
and tested.
The dmserver.cfg file contains options that are also specified in the server definition
on the SAS Metadata Server. The server definition includes configuration settings
for host name, port,
SSL, and security. The values in dmserver.cfg override any different values that are
provided by the SAS Metadata Server. For this reason, it is important that the values
in the server definition are the same as those in dmserver.cfg.
The configuration files
(batch.cfg, macros.cfg, and service.cfg) are used to configure connections
from network clients, as described elsewhere in this document. The
values in these files might be expected by clients, but these files
do not override values that were set elsewhere.