# Class SASjsConfig

Specifies the configuration for the SASjs instance - eg where and how to connect to SAS.

### Hierarchy

- SASjsConfig

### Properties

- appLoc
- contextName
- debug
- httpsAgentOptions
- loginMechanism
- pathSAS9
- pathSASJS
- pathSASViya
- serverType
- serverUrl
- useComputeApi

## Properties

### appLoc

appLoc: string = ""

- Defined in src/types/SASjsConfig.ts:39

The appLoc is the parent folder under which the SAS services (STPs or Job Execution Services) are stored. We recommend that each app is stored in a dedicated parent folder (the appLoc) and the services are grouped inside subfolders within the appLoc - allowing functionality to be restricted according to those groups at backend. When using appLoc, the paths provided in the `request` function should be without a leading slash (/).

### contextName

contextName: string = ""

- Defined in src/types/SASjsConfig.ts:52

The name of the compute context to use when calling the Viya services directly. Example value: 'SAS Job Execution compute context'

### debug

debug: boolean = true

- Defined in src/types/SASjsConfig.ts:47

Set to `true` to enable additional debugging.

### Optional httpsAgentOptions

httpsAgentOptions: https.AgentOptions

- Defined in src/types/SASjsConfig.ts:67

Optional settings to configure HTTPS Agent. By providing `key`, `cert`, `ca` to connect with server Other options can be set `rejectUnauthorized` and `requestCert`

### loginMechanism

loginMechanism: LoginMechanism = LoginMechanism.Default

- Defined in src/types/SASjsConfig.ts:71

Supported login mechanisms are - Redirected and Default

### pathSAS9

pathSAS9: string = ""

- Defined in src/types/SASjsConfig.ts:24

The location of the Stored Process Web Application. By default the adapter will use '/SASStoredProcess/do' on SAS 9.

### Optional pathSASJS

pathSASJS: undefined | string = ""

- Defined in src/types/SASjsConfig.ts:19

The location of the STP Process Web Application. By default the adapter will use '/SASjsApi/stp/execute' on SAS JS.

### pathSASViya

pathSASViya: string = ""

- Defined in src/types/SASjsConfig.ts:29

The location of the Job Execution Web Application. By default the adapter will use '/SASJobExecution' on SAS Viya.

### serverType

serverType: ServerType | null = null

- Defined in src/types/SASjsConfig.ts:43

Can be `SAS9` or `SASVIYA`.

### serverUrl

serverUrl: string = ""

- Defined in src/types/SASjsConfig.ts:14

The location (including http protocol and port) of the SAS Server. Can be omitted, eg if serving directly from the SAS Web Server or being streamed.

### useComputeApi

useComputeApi: boolean | null = null

- Defined in src/types/SASjsConfig.ts:61

If it's `false` adapter will use the JES API as connection approach. To enhance VIYA performance, set to `true` and provide a `contextName` on which to run the code. When running on a named context, the code executes under the user identity. When running as a Job Execution service, the code runs under the identity in the JES context. If `useComputeApi` is `null` or `undefined`, the service will run as a Job, except triggered using the APIs instead of the Job Execution Web Service broker.

Generated using TypeDoc