Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
33 views14 pages

SAS Notes

Uploaded by

saibharath14787
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views14 pages

SAS Notes

Uploaded by

saibharath14787
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

CLI:- command line interface

GUI:- graphical user interface

SAS SERVER :-
1)METADATA SERVER
2)COMPUTE SERVER
3)WEB TIRE SERVER
METADATA SERVER
# There are two partition
1)home directory
2)configuration directory
# metadata is data above data(it store the data in data)
# port number : 8561 (port number is fixed universal )
# metadata is an server is one of the key technology , all the data will
be stored in metadata server (like SAS-user,lib,programs,SAS-data
assets)
COMPUTE SERVER
# it’s an server inside the server there are multiple servers server’s
available
1)Object spawner
2)Work space
3)Stored process
4)Pooled workspace server
5)Cache locator
1)Object spawner:-
 port number :- 8581
 it’s an listener (communicate to workspace server)
2)Workspace server:-
port number :- 8591
If any developer is working on SAS EG (application) than Object
spawner listen and communicate to work space server so than it will
create Temp Space (allocate Temp space) to perform task.
3)Stored process server:-
it create the storage to store the data.
4)Pooled workspace server:-
processer will utilize the RDB(rational database query)
WEB SERVER
# URL-data uploaded(LASER SERVER –to upload data)
1)JSM – broker :-
connectivity
port number: 61616
2)cache locator :-
port number: 41415
SINGLE AND MULTI TIRE
SINGLE TIRE :-
 single IP address
 single server
 server’s : metadata|compute|web
MULTI TIRE :-
 multiple IP address
 contains multiple servers
 server’s : metadata|compute|web, this multi tire contains
individual servers for each and ever IP address and servers.
CLIENT and WEB application
• CLIENT APPLICATION :-its an desktop application its also called THICK
CLIENT.
Like EG ,EM,DI
EGenterprise guide
EMenterprise management
DIdata integration
WEB APPLICATION :-its an stored processes(web application) its also
called THIN CLIENT.
AXIX  huge database
Data tire – huge pool of data
SAS ACCOUNT CREDENTIALS
(UNIVERSAL)
# INTERNAL ACCOUNT :-
1) sasadm@saspw  internal account(admin use this)
2) sastrust@saspw  while connecting metadata to client application
3) webanon@saspw  URL based(WEB) – anonymous account used
gets login in web server
# EXTERNAL ACCOUNT :-
1) sas  administration  installer account (CREATE ID)
2)sassrv  genral account
3) sasdemo  test account (install EG – installer account – finish –
test working – validation – with sasdemo account)
TERMINAL ARCHITECTURE:
 if the developer write the commend/script it goes through SHELL SCRIPT
and it translates every command which user ran in the terminal
And its translates to KERNAL takes command by shell and send
instructions to the HARDWARE/CPU/RAM and this will give some output.

# permission:
->R(4)
->w(2)
->x(1)
PARTITION :-
# SAS – installation software :

1)METADATA: partition mounting SAS HOME & SAS CONFIG


*2)COMPUTE : partition mounting  SAS HOME , SAS CONFIG , SAS
WORK , SAS DATA
3)WEB: partition mounting  SAS HOME & SAS CONFIG
APPLICARIONS OF SAS
# Administartive Application | Tools :-
1) SAS ‘SMC’  management console (applicarion)
2) SAS environment manager  web URL page
#Desktop Application :-
1)client application  developer
2)SAS enterprise guide(EG)  application
3)SAS data integration(DI) studios
4)SAS environment studios
MECHANISIUM :
 If the user or developer login with userid and password the data will
be read by METADATA it will check the credential’s then only
enterprises guide application will open , the authentication will allow
the user to perform the task to write code and exexute.

run|entering|submitting metadata server


Authorization and
Authentication :
Metadata reads the credentials and allow the user to perform the task
(Application exe) opening of application is called authentication

If user login with details , metadata will verify with SAS management
console then user have been verified
NOTE: the details will stored inside the SAS management console(SMC)
Stoping and Starting SAS
server:
sequences :
1)meta server|tire
2)compute|app server|tire|server
3)mid tire|server
sequences howto start and stop the server:
#stop: meta->compute->MID
#start: MID->compute->meta
NOTE:All ways follow the same order to start and stop , and we can
start the single server stop and start all the servers ,we have to stop
and start the server daily

You might also like