sasjs/adapter
1
0
Fork 0
mirror of https://github.com/sasjs/adapter.git synced 2025-12-15 18:54:36 +00:00
Code Issues Projects Releases Wiki Activity

fix: web approach contextname, upload file: context name and debug parameter

Browse Source
This commit is contained in:
Mihajlo Medjedovic
2021-06-22 13:19:11 +02:00
parent 9b976d48ca
commit 8cc4270e48
4 changed files with 40 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -172,8 +172,8 @@ Configuration on the client side involves passing an object on startup, which ca
* `serverType` - either `SAS9` or `SASVIYA`.
* `serverUrl` - the location (including http protocol and port) of the SAS Server. Can be omitted, eg if serving directly from the SAS Web Server, or in streaming mode.
* `debug` - if `true` then SAS Logs and extra debug information is returned.
* `useComputeApi` - if `true` and the serverType is `SASVIYA` then the REST APIs will be called directly (rather than using the JES web service).
* `contextName` - if missing or blank, and `useComputeApi` is `true` and `serverType` is `SASVIYA` then the JES API will be used.
* `useComputeApi` - Only relevant when the serverType is `SASVIYA`. If `true` the [Compute API](https://github.com/sasjs/adapter#using-the-compute-api) is used. If `false` the [JES API](https://github.com/sasjs/adapter#using-the-jes-api) is used. If `null` or `undefined` the [Web](https://github.com/sasjs/adapter#using-jes-web-app) approach is used.
* `contextName` - Context on which the reqeusts will be called.
The adapter supports a number of approaches for interfacing with Viya (`serverType` is `SASVIYA`). For maximum performance, be sure to [configure your compute context](https://sasjs.io/guide-viya/#shared-account-and-server-re-use) with `reuseServerProcesses` as `true` and a system account in `runServerAs`. This functionality is available since Viya 3.5. This configuration is supported when [creating contexts using the CLI](https://sasjs.io/sasjs-cli-context/#sasjs-context-create).
@@ -184,7 +184,8 @@ In this setup, all requests are routed through the JES web app, at `YOURSERVER/S
```
{
appLoc:"/Your/Path",
serverType:"SASVIYA"
serverType:"SASVIYA",
contextName: 'yourComputeContext'
}
```
@@ -195,7 +196,8 @@ Here we are running Jobs using the Job Execution Service except this time we are
{
appLoc:"/Your/Path",
serverType:"SASVIYA",
useComputeApi: true
useComputeApi: false,
contextName: 'yourComputeContext'
}
```