Previous Page | Next Page

Installing and Configuring Your SAS Software

Validate the SAS 9.2 Servers

There are a few simple steps required to confirm that the various SAS servers you have deployed are running properly. The following table summarizes server validation information:

Validation Summary for the SAS Server Tier
Server Validation Method
Metadata server Successful login using the SAS Management Console.
Metadata utility (SASMeta) workspace server The metadata utility workspace server can be used only by those members of the SAS Administrators group who have an external account that is known to the server's host and is associated with their SAS identity. If the server is on Windows and uses credential-based host authentication, the account must have the Log on as a batch job user right.

Right-click the validate command in SAS Management Console using external account credentials that meet the criteria described above. Default path:

Server Manager [arrow] SASMeta [arrow] Logical Workspace Server.
Object spawner If either the stored process server or one of the workspace servers validates (see below), then the object spawner is running.
OLAP server Right-click the validate command in SAS Management Console. Default path:

Server Manager [arrow] SASApp  [arrow] Logical OLAP Server.1
Pooled workspace server Right-click the validate command in SAS Management Console. Default path:

Server Manager [arrow] SASApp [arrow] Logical Pooled Workspace Server.1
Stored process server Right-click the validate command in SAS Management Console. Default path:

Server Manager [arrow] SASApp [arrow] Logical Stored Process Server.1
Workspace server Right-click the validate command in SAS Management Console using external account credentials. Default path:

Server Manager [arrow] SASApp [arrow] Logical Workspace Server.1
DATA step batch server Successful launch of SAS when running the sasbatch script (Windows and UNIX).

On z/OS, use the Schedule Manager's Deploy SAS DATA Step Program to browse the appserver_autoexec_usermods.sas file created in the AppServer context.
Grid server Successful launch of the grid test program found on the SAS Scalability and Performance focus area: http://support.sas.com/rnd/scalability/grid/gridfunc.html#testprog. For more information, see Verifying SAS Job Execution in Grid Computing in SAS.
1 Use the value you entered during the deployment for the server context name. The default is SASApp.

This procedure is meant to provide validation for an out-of-the-box, basic deployment. For more complex server configurations, please refer to the appropriate SAS documentation for the server in question.

To validate the SAS server tier that has been deployed using the SAS Deployment Wizard, follow these steps:

  1. Log on to the machine hosting one or more SAS servers.

  2. Start SAS Management Console, using the following command for the appropriate operating system:

    • Windows:

      Start menu [arrow] Programs  [arrow] SAS [arrow] SAS Management Console 9.2

    • UNIX:

      Type the following command:

      sas-installation-directory/sasmc

      For example:

      /opt/sas/SASManagementConsole/9.2/sasmc

    • z/OS:

      Use a Windows or UNIX machine on which SAS Management Console is installed and connect to the z/OS machine(s) where the SAS 9.2 server tier is running.

  3. Log on to the metadata server using a set of valid credentials, such as for the SAS Administrator.

  4. In SAS Management Console, on the Plug-ins tab, expand the Server Manager node.

  5. Expand the SAS Application Server node. (The default name is SASApp.)

  6. Highlight the server you want to validate, such as the SASApp - Logical OLAP Server.

  7. Right-click the highlighted server, and select Validate.

    You should see the following message:

    Validation Successful!

  8. Repeat steps 6 and 7 for the other SAS servers:

    • pooled workspace server

    • stored process server

    • workspace server

  9. When validating the workspace server, if you are prompted for credentials, we suggest that you enter the credentials for the SAS Spawned Servers account (sassrv). Alternatively, you can enter a user ID and password that meet all of these requirements:

    • The account is known to the host of the workspace server.

      (An ID that ends in @saspw does not meet this requirement.)

    • The account has the Windows right Log on as a batch job (if the server is on Windows).

    • The account has a corresponding metadata identity.

  10. To validate the DATA step batch server on Windows and UNIX, SAS should successfully launch when you run the following command, appropriate for the server host operating system:

    • Windows:

      Start menu [arrow] Run [arrow] sas-configuration-directory\sasbatch.bat

      For example:

      Start menu [arrow] Run [arrow] C:\SAS\AllServers\Lev1\SASApp\BatchServer\sasbatch.bat

    • UNIX:

      Type the following command:

      sas-configuration-directory/SASApp/BatchServer/sasbatch.sh

      For example:

      /opt/sas/AllServers/Lev1/SASApp/BatchServer/sasbatch.sh

  11. To validate the DATA step batch server on z/OS, use the Schedule Manager's Deploy SAS DATA Step Program to browse the appserver_autoexec_usermods.sas file created in the AppServer context. When the JCL pane comes up and contains JCL, then the deployment of the batch server is successful.

    1. From SAS Management Console, right-click the Schedule Manager plug-in (Plug-ins tab) and choose Deploy SAS DATA Step Program.

    2. Click Browse and navigate to the appserver_autoexec_usermods.sas file under a server context such as SASApp (for example, SAS-configuration-directory/Levn/SASApp).

    3. You should see JCL in the bottom list box.

  12. To verify that your grid servers are operational, follow the steps located in, Verifying SAS Job Execution in Grid Computing in SAS.

  13. Repeat these steps on each machine in your deployment plan on which you have deployed one or more SAS servers.

Previous Page | Next Page | Top of Page

Copyright © 2011 by SAS Institute Inc., Cary, NC, USA. All rights reserved.