Skip to main content

Applications used by SAS Admin

We know there are several client application in SAS. SAS Admin does most of his task using SAS Management Console and rarely using SAS Environment Manager. Other tool like SAS Web Administration Console can be used. Let's see a brief detail about what these tools does.

SAS Management Console:
SAS Admin can accomplish most of his/her task using SAS Management Console or SMC in short. Using SMC, admin can manage the metadata (library, table, ACT, user, groups and role) and SAS servers (workspace server, pooled workspace server and stored process server). SAS Admin can do their task by using the plug-ins available in SMC.

Schedule Manger is one of the plug-in in SMC used to schedule SAS jobs. Using this plug-in you can choose the scheduling server.

Image shows list of Plugin in SAS Management Console 9.4
Each plug-in has its own functionality. Other major plug-ins that SAS Admin should be aware are Metadata Manager, Library Manager, authorization plugin, Server Manager and User Manager plugin.

In few organization, SAS Admin will be allowed to do only a specific task, say start or pause a server. In that case he/she will be provided access only to the Server Manager plugin. Only unrestricted user can able to see all the plugin available in SAS Management Console.

A unrestricted user can provide access to specific plugin to SAS Users. Unrestricted user not only manages the plugin that can be seen in SAS Management Console, he/she can also control the plug-in that can be seen in SAS Enterprise Guide and SAS Web Report Studio. This feature is done using the roles option in User Manager plugin. I already covered a article about providing access to Authourization plugin alone in SAS Management Console to a specific article. I have explained them with screenshot, do read the article which will give you broad view about plugins.

SAS Environment Manager:
Using SAS Environment manager, admin can monitor the SAS deployments. There are several plug-ins available which can be used for admin tasks, manage and monitor SAS platform.

SAS Web Administration Console:
This tool can be run using browser. It is a web application primarily used to monitor users activity in SAS web applications. Some of the activity that can be done using SAS Web Administration Console are:

  • Get reports of who logged in and logged off
  • Authorization controls like role, permission and privileges.
  • Can access Content Server Administration Console.
  • Adjust the logs for web application.


Other tools:
Apart from the above tools, SAS Admin should aware of the scripts that comes with SAS Platform. Most of the time it will be executed from OS level. For example: there is script to clean space in work directory called cleanwork. There are many such utilities provided by SAS for its platform. I personally used those script in Linux environment and sure there will be such scripts in Windows.

Batch tools help SAS admin to get information about SAS platform. Admins can use batch tools to do backup and recovery task. For example: the batch command -host host-name will identify host machine for Web Server.

Image Source: support.sas.com


Comments

Popular posts from this blog

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT.  So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log.  Any suggestions? Answer: Please do the following:    1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop  2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`:  if [ -n ""$TKPATH"" ]; then  unset TKPATH  fi   if [ -n ""$TK_PATHLIST"" ]; then  unset TK_PATHLIST  fi    3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start  The above code change in ObjectSpawner.sh should fix the issue.

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...