dc/docs.datacontroller.io
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

another commit

Browse Source
This commit is contained in:
Allan Bowe 2021-02-21 16:34:15 +01:00
parent ef95bc0a9d
commit 1077f239b9
2 changed files with 2980 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/dci-evaluation.md
View File

@ -10,10 +10,10 @@ A free version of Data Controller is available for evaluation purposes. Compiled
### Deployment
#### Import
Simply import the SPK (using SAS Management Console or Data Integration Studio) to the desired location in the metadata tree. During the import (step 5 of the wizard), be sure to change the location of the library (BASE engine) to a **directory folder** to which the Stored Process system account (eg `sassrv`) has **write access**.
Simply import the SPK (using SAS Management Console or Data Integration Studio) to the desired location in the metadata tree. During the import (step 5 of the wizard), be sure to change the location of the library (BASE engine) to a physical **directory folder** to which the Stored Process system account (eg `sassrv`) has **write access**.
#### Permissions
Be sure that the user account you will use in the [configuration(#Configuration) step below has WRITE METADATA (WM) on the `/DataController/Admin` and `/DataController/Data` folders, and that anyone who will use the app has READ.
Be sure that the user account you will use in the [configuration](#configuration) step below has WRITE METADATA (WM) on the `/DataController/services/admin` and `/DataController/Data` folders, and that anyone who will use the app has READ.
### Configuration
@ -26,10 +26,12 @@ Navigate to the web application (eg `https://[YOURHOST]/SASStoredProcess?_action
This displays a screen with a choice of SAS Metadata Groups (to which your account belongs) can be chosen. Selecting any of these groups will build / rebuild all the configuration tables (placing logs in a subfolder of the previously configured library location) and provide the chosen group with **unrestricted** access to the tool.
If you do not see any groups, then it is possible your Stored Process is running from a different metadata repository to the location of your SAS users (eg Foundation). To fix this, re-run the configuration stp with the `&dc_repo_users=YOURMETAREPO` url parameter.
![evaltree](img/dci_evalconfig.png)
!!! note
"Unrestricted access" is provided by code logic. Once installed, Data Controller does not ever update or modify metadata. During installation, the services in the `/Admin` folder are updated (configuration) or removed (to prevent accidental reinstall). Also the tables are registered in the `/Data` folder using `proc metalib`.
"Unrestricted access" is provided by code logic. Once installed, Data Controller does not ever update or modify metadata. During installation, the services in the `/services/admin` folder are updated (configuration) or removed (to prevent accidental reinstall). Also the tables are registered in the `/Data` folder using `proc metalib`.
## Usage
@ -46,8 +48,10 @@ The demo version has been optimised for a rapid install, and should not be consi
2) Requires BASE engine for config tables, with high risk of table locks
3) Not licenced for commercial (or production) use, and not supported
3) Interface is not licenced for commercial (or production) use, and not supported
4) The embedded HandsOnTable library is not licenced for commercial use without a licence key
4) Underlying macros are not licensed for re-use on other (internal) projects
5) The embedded HandsOnTable library is not licenced for commercial use without a licence key
Contact Macro People support for a full-featured, fully licenced, scalable and supported deployment of Data Controller at your earliest convenience!

2976
docs/licences.md
View File

File diff suppressed because it is too large Load Diff