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

updating wording

Browse Source
This commit is contained in:
Allan Bowe
2018-12-30 22:30:14 +02:00
parent de0cdd96f4
commit 0d3e91ac79
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/dci-backend.md
View File

@@ -5,17 +5,17 @@ The backend for Data Controller consists of a set of Stored Processes, a macro l
## Regular Deployment ## Regular Deployment
1 - Import datacontroller.spk using SAS Management Console. The location in which this is deployed should be added to the `metadataRoot` value in the `h54s.config` file as per [frontend](dci-frontend.md#details) deployment. 1 - Import `/sas/import.spk` using SAS Management Console. Make a note of the root location in which this was deployed - as this will be added to the `metadataRoot` value in the `h54sConfig.json` file in the [frontend](dci-frontend.md#details) deployment.
2 - Create a physical staging directory. This will contain the data submitted by editors and awaiting approval. The SAS Spawned Server account (eg `sassrv`) will need write access to this location. 2 - Create a physical staging directory. This folder will contain the logs and CSV files generated by Users. The SAS Spawned Server account (eg `sassrv`) will need write access to this location.
3 - Register a library in metadata for the control database. The libref should be `DATACTRL`. If this is not possible, then an alternative libref can be used, simply specify it in the configuration component. 3 - Register a library in metadata for the control database. The libref should be `DATACTRL`. If this is not possible, then an alternative libref can be used, simply specify it in the configuration component.
4 - Update the configuration component (imported in the SPK) with the following attributes: 4 - Update the configuration component (imported in the SPK) with the following attributes:
* `dc_staging_area` - location of staging directory as per step 2 * `dc_staging_area` - location of staging directory as per step 2
* `dc_libref` - if you were unable to use the `DATACTRL` libref in step 3, then use the updated libref here
* `dc_admin_group` - enter the name of a metadata group (eg SASAdministrators) that should be given unrestricted access to the tool * `dc_admin_group` - enter the name of a metadata group (eg SASAdministrators) that should be given unrestricted access to the tool
* `dc_libref` - if you were unable to use the `DATACTRL` libref in step 3, then use the updated libref here
5 - Deploy the data model. For this, simply compile and run the `mpe_build()` macro. 5 - Deploy the data model. For this, simply compile and run the `mpe_build()` macro.