] }
Use the remote SAS Data Agent (on-premises) server to set a default, as shown in this example:
/opt/sas/viya/home/libexec/admin-plugins/dagentsrv-cli servers set-default dagentsrv-shared-default-test-onprem
Another option is to specify the name of the Data Agent server each time that the CLI is invoked. See “CLI ‘dagentsrv’” on page 101 for additional information.
SAS Data Agent Configuration
Server Registration
During the registration process of SAS Data Agent services in Consul, a short hostname is included as a part of the registered service name. Here is an example:
tenant ID = ted instance = default
hostname = tedhost.ted.domain.com
registered service name = dagentsrv-ted-default-tedhost
The following parameters are not populated during deployment of SAS Data Agent, but are required:
--sasadministratoruser --sasadministratorpassword --secret
You must specify a SAS administrator, password, and secret. Here is an example:
/opt/sas/viya/home/bin/da_reg_server.sh --sasadministratoruser userid --sasadministratorpassword password
--secret secret
/opt/sas/viya/home/bin/da_init_tenant.sh --secret secret
sudo systemctl restart sas-viya-dagentsrv-default
See “Register the SAS Data Agent Server ” in SAS Data Agent for Linux: Deployment Guide.
Configuring Content Root
About Content Root
Content root specifies the location where files such as Base SAS data sets or .csv files used with FILETRANSFER can be stored. By default, path-based data services, specifically Base SAS and File Transfer, are restricted to the location of content root.
You can disable content root or change the default location using the DA_RESTRICT_CONTENT_ROOT environment variable.
The desired default path for a single-tenant deployment is:
/opt/sas/viya/config/data/dagentsrv/default For multi-tenant deployments:
/opt/sas/<tenantID>/config/data/dagentsrv/default
Note: This configuration default option value is new for SAS Data Agent release 2.5.
CAUTION:
Base SAS schemas defined prior to release 2.5 might not work when
CONTENT_ROOT is active. You can remove the restriction or re-create the schema and copy the SAS data set files to a location under the content-root location.
The location of Base SAS schemas is now limited to the directory path set in content root. Here are the actions to take if this presents a problem:
• Modify the Base SAS schemas to point to a location inside content root. The default path is noted above.
• Change the location of content root as shown below.
• To continue using previously defined schemas, set the environment variable, DA_RESTRICT_CONTENT_ROOT to FALSE.
Change Content Root Location
To override the default directory path for content root, add the environment variable with a new directory path (DA_RESTRICT_CONTENT_ROOT=/tmp) to the sysconfig file located in /opt/sas/<deployid>/config/etc/sysconfig/dagentsrv/
default.
Disable Content Root
To override the default setting, add the environment variable
DA_RESTRICT_CONTENT_ROOT=FALSE to the sysconfig file located
in /opt/sas/<deployid>/config/etc/sysconfig/dagentsrv/default.
Connection Pooling
Connection pooling is a reserve of connections that are maintained in the SAS Data Agent services so that connections can be reused as future requests to SAS Data Agent are required. With connection pooling, connections are created and placed into the pool to be used over again so that a new connection to a data source does not have to be reestablished. This practice reduces the amount of time that it takes to establish a connection to a Data Agent server.
• dataSourcePoolMaxIdle: The cap on the number of instances that can be added to each data source pool. The default is 0, no data source pooling. To enable data source connection pooling, set this value to a number larger than 0. The recommended value is 8.
• connectionPoolMaxIdle: The maximum number of connections that can remain idle for each data source connection pool. The default is 0 (no cap). To enable connection pooling for each data source, set this value to a number larger than 0. The
recommended value is 8.
Log on to SAS Environment Manager as an administrator and follow these steps to configure connection pooling:
1. In SAS Environment Manager choose Configuration, All Services.
2. Click on Edit sas.clouddataexchange configuration.
3. To enable or disable connection pooling:
• To enable connection pooling, set dataSourcePoolMaxIdle and connectionPoolMaxIdle to a positive number other than 0.
• To disable connection pooling, set dataSourcePoolMaxIdle and connectionPoolMaxIdle to 0.
4. Click Save.
5. Restart the Data Agent service for the change to take effect. See “Restart Microservices” for the necessary commands.
Environment Variables
Proxy Settings
If you need to set or change proxy server settings for SAS Data Agent, use the configuration file sas‑dagentsrv located in the following directory: /opt/sas/
viya/config/etc/sysconfig/dagentsrv/default/. Add or update the following environment variables with your proxy configurations:
export DA_SERVICES_PROXY_SERVER=my.proxy.server.com export DA_SERVICES_PROXY_PORT=port-number
export DA_SERVICES_PROXY_USER=username export DA_SERVICES_PROXY_PASS=password
SAS Environment
These environment variables are registered during deployment but can be overwritten if needed:
SASDEPLOYID - default value "viya"
SASINSTANCE - default value "default"
SASROOT - default value "/opt/sas/${SASDEPLOYID}"
SASHOME - default value "/opt/sas/${SASDEPLOYID}/home"
SASCONFIG - default value "/opt/sas/${SASDEPLOYID}/config"
SASLOGROOT - default value "${SASCONFIG}/var/log"
SASUSER - default value "sas"
SASGROUP - default value "sas"
SASLICENSEFILE - default value "setinit.txt"
PostgreSQL Database Server
Specify the tenant ID. Also used to specify the ‑‑customerid for a non-tenancy environment. The default value is "shared".
DA_FSNET_PORT default value 25141 DA_DPLY_FSNET_PORT
Value defined in the tenantID_vars.yml named data_agent_fsnet_port is written into this environment variable.
VAULT_HTTP_ADDR
default value "Data Agent Power Users"
DA_PG_SYSCAT_DB
/${DA_PROD_NAME}/default/$(hostname -f).key"
DASSLCERTLOC default value
"${SASCONFIG}/etc/SASSecurityCertificateFramework/tls/certs /${DA_PROD_NAME}/default/$(hostname -f).crt"
DA_SITE_NAME default “private”
DA_CONSUL_TOKEN_FILE default
"../../../../config/etc/SASSecurityCertificateFramework/tokens /consul/${SASINSTANCE}/client.token"
DA_VAULT_TOKEN_FILE
default"../../../../config/etc/SASSecurityCertificateFramework/tokens /dagentsrv/${DA_INSTANCE}/vault.token"
DA_CLIENT_SECRET_KEY
default dagentsrv/dagentsrv-<tenantID>/login/password DASSLPVTKEYPASS
default "cat ${SASCONFIG}/etc/SASSecurityCertificateFramework/private/
${DA_PROD_NAME}/default/dagentsrv_encryption_${DA_INSTANCE}.key"
Locale Support
Cloud Data Exchange supports the English, United States of America (en_US) locale.
The following table outlines the character representations and format used for output.
There are no deviations from these formats:
Character Type Format
Number ddddd.fffffffff
Date yyyy‑mm‑dd
Time hh:mm:ss
Timestamp yyyy‑mm‑dd hh:mm:ss[.ffffffff]
Note: You should configure database drivers and clients to match this behavior to ensure that conversions are handled correctly.