chore: docs

docs/deploy-viya.md

@@ -8,7 +8,7 @@ og_image: https://docs.datacontroller.io/img/dci_deploymentdiagramviya.png
 # SAS Viya Deployment
 
 ## Overview
-Data Controller for SAS Viya consists of a static web frontend, a set of Viya Jobs, a staging area (physical directory), a Compute Context, and a Library.  
+Data Controller for SAS Viya consists of a static web frontend, a set of Viya Jobs, a staging area (physical directory), a Compute Context, and a Library.
 
 ## Prerequisites
 
@@ -17,7 +17,7 @@ Data Controller for SAS Viya consists of a static web frontend, a set of Viya Jo
 Data Controller makes use of a system account for performing backend data updates and writing to the staging area.  This needs to be provisioned in advance using the Viya admin-cli.  The process is well described here:  [https://communities.sas.com/t5/SAS-Communities-Library/SAS-Viya-3-5-Compute-Server-Service-Accounts/ta-p/620992](https://communities.sas.com/t5/SAS-Communities-Library/SAS-Viya-3-5-Compute-Server-Service-Accounts/ta-p/620992)
 
 ### Library
-Currently, all of our customers are using the standard BASE engine library for the control tables.  However it is possible to use a database instead.   To migrate the control library to a database, first perform a regular deployment, and afterwards you can generate the DDL. For this, use the DDL exporter as described [here](/admin-services/#export-database).  If you need a flavour of DDL that is not yet supported, [contact us](https://datacontroller.io/contact/). 
+Currently, all of our customers are using the standard BASE engine library for the control tables.  However it is possible to use a database instead.   To migrate the control library to a database, first perform a regular deployment, and afterwards you can generate the DDL. For this, use the DDL exporter as described [here](/admin-services/#export-database).  If you need a flavour of DDL that is not yet supported, [contact us](https://datacontroller.io/contact/).
 
 Make sure the system account (see above) has full read / write access.
 
@@ -41,10 +41,10 @@ The below areas of the SAS Viya platform are modified when deploying Data Contro
 ## Deployment
 Data Controller deployment is split between 2 deployment types:
 
-* Streaming (web content served from SAS Drive) 
+* Streaming (web content served from SAS Drive)
 * Separated (web content served from dedicated web server)
 
-For most customers, the streaming approach is preferred, as it makes the deployment much simpler.  
+For most customers, the streaming approach is preferred, as it makes the deployment much simpler.
 
 
 There are several parts to this proces:
@@ -124,7 +124,7 @@ Now the services are deployed (including the service which creates the staging a
 * Compute Context - the context configured in Step 1
 
 
-### 5.  Optmisation
+### 5.  Optimisation
 
 At this point, every DC request will read the `services/public/settings.sas` file to get the DC library (and other) settings.  To avoid these API calls (which will speed up the app) we can simply move this code to the autoexec.  Steps as follows:
 
@@ -151,3 +151,10 @@ To explain each of these lines:
 * The final libname statement can also be configured to point at a database instead of a BASE engine directory (contact us for DDL)
 
 If you have additional libraries that you would like to use in Data Controller, they should also be defined here.
+
+
+## Visual Analytics
+
+It is possible to embed a Data Controller table within SAS Visual Analytics by simply pasting the URL.
+
+To make the portlet more visually appealing, the Data Controller title bar can be removed by adding `?embed=true` to the URL.  When opening in a new window, the title bar will be gone.