Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Unlike SAS^® 9.1.3, SAS 9.2 uses the pooled workspace server by default for SAS Information Map Studio and Web applications such as SAS Web Report Studio. The primary purpose of pooling is to enhance performance by avoiding the time penalty that is associated with launching all workspace servers on demand. In pooling, a set of workspace servers are made available to process certain types of query requests. In general, pooling is used when a relational information map is queried, processed, opened, or used indirectly (through a report).

For a pooled workspace server, the object spawner launches process instances under a designated service account. That account is called a launch credential and is specified as part of the server's metadata definition. For example, in the initial configuration, the SAS Spawned Servers account (sassrv) is the only designated launch credential.

If you prefer to have processes launched under the requesting user's ID, then you must use a standard workspace server. The only way to convert to a standard workspace server is to block access to the pooled workspace server. If the pooled workspace server is not accessible, then the standard workspace server is used.

Note: For more information about why you might want to prevent use of a particular server, see Hiding Server Definitions .

CAUTION: Performance will likely be adversely affected when pooling is disabled. Before making any changes, review the information in Server Configuration, Data Retrieval, and Risk.

To restrict access to the pooled workspace server, perform these tasks in SAS^® Management Console.

1. Log on as an unrestricted user such as sasadm@saspw.
2. Navigate to Server Manager ► SASApp - Logical Pooled Workspace Server.
3. Right-click and select Properties.
4. On the Authorization tab, make sure that SAS Administrator has an explicit grant for all permissions, and then add an explicit denial on all permissions for PUBLIC.

Note: If explicitly denying access to PUBLIC does not prevent users from accessing the pooled workspace server, then make sure you have not explicitly granted access to SASUSERS or any other user or group.

Operating System and Release Information