fix: adding sas 9 deploy info

This commit is contained in:
vrh 2020-09-26 16:51:37 +02:00
parent 242956bed6
commit ca88c9e9b0
6 changed files with 287 additions and 286 deletions

View File

@ -1,7 +1,14 @@
---
layout: article
title: DC SAS 9 Deployment
description: How to deploy Data Controller in a production SAS 9 environment
og_image: https://docs.datacontroller.io/img/dci_deploymentdiagram.png
---
# SAS 9 Deployment # SAS 9 Deployment
## Overview ## Overview
Data Controller consists of a frontend app, a set of Stored Processes and a database library. The library can be a SAS Base engine if desired, however this can cause contention (eg table locks) if end users are able to connect to the datasets directly, eg via Enterprise Guide or Base SAS. Data Controller for SAS 9 consists of a frontend, a set of Stored Processes, a staging area, and a database library. The library can be a SAS Base engine if desired, however this can cause contention (eg table locks) if end users are able to connect to the datasets directly, eg via Enterprise Guide or Base SAS.
A database that supports concurrent access is recommended. A database that supports concurrent access is recommended.
## Backend ## Backend
@ -26,8 +33,47 @@ Deploy as follows:
2 - Open the `index.html` file and update the `appLoc` value to the location where the Stored Processes were deployed earlier. 2 - Open the `index.html` file and update the `appLoc` value to the location where the Stored Processes were deployed earlier.
It should now be possible to use the application - simply navigate to `YOURSASWEBLOC.domain/yourRoot/datacontroller` and sign in! It should now be possible to use the application - simply navigate to `YOURSASWEBLOC:port/yourRoot/datacontroller` and sign in!
The next step is to [configure](dcc-tables.md) the tables. The next step is to [configure](dcc-tables.md) the tables.
## Deployment Diagram
The below areas of the SAS platform are modified when deploying Data Controller:
<img src="/img/dci_deploymentdiagram.svg" height="350" style="border:3px solid black" >
### Client Device
Nothing needs to be deployed or modified on the client device. We support a wide range of browsers (the same as SAS). Browsers make requests to the SAS Web Server, and will cache assets such as JS, CSS and images. Some items (such as dropdowns) are kept in local storage to improve responsiveness.
### SAS Mid Tier
The front end is deployed to the SAS Web Server as described [above](/dci-deploysas9/#frontend). This requires making a dedicated public folder in the htdocs directory.
### SAS Application Server
Given the enhanced permissions needed of the system account, a dedicated / secured STP instance is recommended as described [here](/dci-stpinstance).
All deployments of Data Controller also make use of a staging directory. This is used to store CSV and Excel files as uploaded by end users. This directory should NOT be accessible by end users - only the SAS system account (eg sassrv) requires access to this directory.
A typical small deployment will grow by a 10-20 mb each month. A very large enterprise customer, with 100 or more editors, might generate up to 1 GB or so per month, depending on the size and frequency of the Excel EUCs and CSVs being uploaded. Web modifications are restricted only to modified rows, so are typically just a few kb in size.
### SAS Metadata Server
The items deployed to metadata include:
* Folder tree
* Stored Processes
* Library Object & tables
After the installation process (which updates `settings` and removes the `makedata` STP), there are no write actions performed against metadata.
### Databases
We strongly recommend that the Data Controller configuration tables are stored in a database for concurrency reasons, however it is also possible to use a BASE engine library.
We provide the DDL for creating the tables, we have customers in production using Oracle, Postgres, Netezza, SQL Server to name a few.
Data Controller does NOT modify schemas! It will not create or drop tables, or add/modify columns or attributes. Only rows can be modified using the tool.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 49 KiB

After

Width:  |  Height:  |  Size: 87 KiB

File diff suppressed because one or more lines are too long

After

Width:  |  Height:  |  Size: 48 KiB

File diff suppressed because it is too large Load Diff

View File

@ -1,4 +1,4 @@
site_name: Data Controller for SAS® Product Documentation site_name: Data Controller for SAS® Documentation
site_url: https://docs.datacontroller.io site_url: https://docs.datacontroller.io
nav: nav:
- Home: index.md - Home: index.md

View File

@ -15,7 +15,12 @@
<meta property="og:type" content="website" /> <meta property="og:type" content="website" />
<meta property="og:title" content="{{ title }}" /> <meta property="og:title" content="{{ title }}" />
<meta property="og:url" content="{{ page.canonical_url }}" /> <meta property="og:url" content="{{ page.canonical_url }}" />
<meta property='og:image' content='https://www.rawsas.com/wp-content/uploads/2018/07/dc_social.png'/> {% if page and page.meta and page.meta.og_image %}
{% set og_image = page.meta.og_image %}
{% elif page %}
{% set og_image = 'https://www.rawsas.com/wp-content/uploads/2018/07/dc_social.png' %}
{% endif %}
<meta property='og:image' content="{{og_image}}"/>
<meta property="og:image:type" content="image/png" /> <meta property="og:image:type" content="image/png" />