BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
SDV
Obsidian | Level 7 SDV
Obsidian | Level 7

We have SAS Studio deployed in a SAS Grid environment that uses grid launched workspace server sessions.  I read in the admin guide that interactive mode uses multiple workspace server sessions and that webwork is the default library used for interactive mode. 

 

Does this mean that the webwork library needs to be configured to reside on a shared file system accessible from each grid node?  I think it does, but can someone confirm?

1 ACCEPTED SOLUTION

Accepted Solutions
SDV
Obsidian | Level 7 SDV
Obsidian | Level 7

Webwork needs to be set to a location that is shared to each grid node when using grid launched workspace servers.

 

Just FYI, here is some more information on webwork.

 

It is the default library when using Studio's interactive mode.  In interactive mode, each program gets a workspace server session, and all of the workspace server sessions from your Studio session share the webwork.  In a SAS grid when using grid launched workspace server sessions the workspace sessions can run on any of the grid nodes, therefore the directory used for webwork needs to be in a shared location accessible from each grid node.

 

See this blog entry for further information:  http://blogs.sas.com/content/sgf/2016/09/21/sas-studio-tips-for-sas-grid-manager-administrators-wher... 

View solution in original post

5 REPLIES 5
Kalind_Patel
Lapis Lazuli | Level 10

Hi @SDV;

 

You can save your intermediate results in the WEBWORK library. WEBWORK library is automatically assigned at start-up and is shared across all workspace server sessions.

 

For more clarification,

Please refer this document:

http://support.sas.com/resources/papers/proceedings16/SAS6422-2016.pdf

 

 

Thanks,

Kalind

SDV
Obsidian | Level 7 SDV
Obsidian | Level 7

Thank you @Kalind_Patel.

 

Yes, I am aware that webwork is available across workspace server sessions.  So, if you have multiple workspace server sessions in a SAS grid, then webwork will need to point to a physical directory that all grid nodes can access because workspace server sessions could start on any node.  Is that correct?

Kalind_Patel
Lapis Lazuli | Level 10

Yes @SDV;

 

All grid nodes can access that location,

and This is the main advantage of WEBWORK library, so if you start the multiple workspace server sessions,

this shared library (WEBWORK) assigned to all the workspace server sessions at startup (Check the more details on page no:12, of the link which i have shared with you in last reply) ,

 

And to make this functionality, we have to make sure that all grid node can access the physical location of WEBWORK library, without any prompt;

 

I hope this will clear your doubts Smiley Happy

 

Thanks,

Regards
 

 

SDV
Obsidian | Level 7 SDV
Obsidian | Level 7

Webwork needs to be set to a location that is shared to each grid node when using grid launched workspace servers.

 

Just FYI, here is some more information on webwork.

 

It is the default library when using Studio's interactive mode.  In interactive mode, each program gets a workspace server session, and all of the workspace server sessions from your Studio session share the webwork.  In a SAS grid when using grid launched workspace server sessions the workspace sessions can run on any of the grid nodes, therefore the directory used for webwork needs to be in a shared location accessible from each grid node.

 

See this blog entry for further information:  http://blogs.sas.com/content/sgf/2016/09/21/sas-studio-tips-for-sas-grid-manager-administrators-wher... 

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 5 replies
  • 1515 views
  • 1 like
  • 3 in conversation