topic Re: Workspace Server: extended attributes in Administration and Deployment

Workspace Server: extended attributes

MariaD — Mon, 09 Sep 2019 19:35:01 GMT

Hi folks,

We have two SAS groups. Each one need to access specific file path navigation. In order to configure it, we create a second Workspace Server on SAS MC. Both Workspace Server refers to the same script to start workspace defined on COMMAND properties (ex: /sas/config/Lev1/SASApp/WorkspaceServer/WorkspaceServer.sh).

There is any way to, using extended attributes or command line or object server parameters, define different config file for each one? Is it possible to add -CONFIG option in COMMAND line? We need to define a different WORK area for these groups.

Regards,

Re: Workspace Server: extended attributes

SASKiwi — Mon, 09 Sep 2019 23:49:09 GMT

The usual approach is for each workspace server to have its own configuration directory. In your case a second one could use:

/sas/config/Lev2/SASApp2/WorkspaceServer. Then you just make the required changes in the usermods config.

Re: Workspace Server: extended attributes

AnandVyas — Tue, 10 Sep 2019 01:30:49 GMT

Hi @MariaD

You can add a section of IF condition (loops in bash scripting) to evaluate users based on groups and then pass the work parameter dynamically to allocate work directory as per the user group. This can be done in the workspace_usermods.sh file which is read during launch of workspace server.

USERMODS_OPTIONS="-work <full-path-to-work>"

Creating workspace server from SAS MC will only create logical instance of it in metadata referring to same physical location. if you wish to have separate work space servers, then you will have to install it using SAS deployment wizard launched from SAS software depot where in you can then set work directories for respective servers.

Thanks!

Re: Workspace Server: extended attributes

MariaD — Tue, 10 Sep 2019 02:25:40 GMT

Thanks all. Yes, I know is only a logical definition, but it's only to define the correct file path navigation for each group.

We resolve the problem adding a -WORK option directly on command line. So, now each logical workspace server has it owns work area defined.

/sas/config/Lev1/SASApp/WorkspaceServer/WorkspaceServer.sh -WORK "/<group_area>/saswork"

Thanks!