Using Multiple SAS Application Servers

Which Server is Used?

Preliminary Requirements

Only a SAS Application Server that meets both of the following requirements can be used:
  • The server is registered with the job execution service.
  • The server is visible to the requesting user. (The user must have ReadMetadata access to the server.)

Automatic Selection

In most cases, a server is automatically selected using the following logic:
  1. Use an associated server. For example, for a load request, follow the associations from the target LASR library to its SAS Application Server assignments.
    Note: For a request to start or stop a SAS LASR Analytic Server, follow the associations from the target SAS LASR Analytic Server to its LASR libraries to their SAS Application Server assignments.
    If there is no associated server that is registered with the job execution service and visible to the requesting user, proceed to step 2.
  2. Use the suite-level default server. See va.defaultWorkspaceServer.
    If the suite-level default server is not registered with the job execution service or not visible to the requesting user, proceed to step 3.
  3. Use any server that is registered with the job execution service and visible to the requesting user.

Specific Designation

For the administrator and data builder, users can opt out of automatic selection and instead force the use of a particular server. SeeUser Preference: SAS Application Server.
Note: For example, if you schedule data queries in the data builder, you might need to force the use of a SAS Application Server that includes a SAS DATA Step Batch Server.

Add a New Server

To add a new SAS Application Server, see Managing SAS Application Servers in the SAS Intelligence Platform: Application Server Administration Guide.
The following details are specific to SAS Visual Analytics:
  • You must register the server with the job execution service. See Job Execution Service in the SAS Intelligence Platform: Middle-Tier Administration Guide.
  • To support geo maps in the classic (Flex) applications, include a SAS Stored Process Server within the SAS Application Server. (SAS Visual Analytics uses the stored process server internally to read boundary and lookup data for geo maps.)
  • To support any of the following activities, include a SAS Pooled Workspace Server within the SAS Application Server:
    • Use geo maps. The pooled workspace server loads the geographic lookup data sets.
    • Extract and feed data for administrative reports.
    • Access the Import Data panel in the designer, explorer, or data builder. (The pooled workspace server pre-screens available SAS/ACCESS licenses and then populates the Import Data panel.)
  • To support scheduled queries in the data builder, include a SAS DATA Step Batch Server within the SAS Application Server.
  • To support scheduled report distribution in the designer, include a Java batch server within the SAS Application Server.
  • To support customized formats for data, seeSupporting User-Defined Formats.
  • To support interactions with a SAS LASR Analytic Server, make sure the configured monitoring path exists on the machine that hosts the new SAS Application Server. Either ensure that the standard location exists on that machine, or add an extended attribute to the SAS LASR Analytic Server to specify an alternate location. Seeva.monitoringPath.
Tip
To reduce the need for back-end accounts, consider configuring the workspace server within the new SAS Application Server to use SAS token authentication. SeeShared Accounts for Self-Service Imports.
Last updated: December 18, 2018