In Windows operating system, we know that installation files by default get stored in Program Files in C drive. For example, let say I install a Antivirus program, the default location will be C:\\Program Files. SAS installation is similar and it maintains two main directory to store SAS software and configuration files. In SAS we call it as:
Let's see in details about this directories.
SASHOME directory:
SAS Software installation is done using SAS Deployment Wizard. When you do first installation you can provide the desired location in which you want your SAS software to be stored. This will be your default location. However later you can't change the directory unless you do fresh installation. Any new SAS software installation made in the same computer will automatically gets stored in the default location.
The SASHOME directory will holds the installation files of SAS softwares like SAS Addin for MS Office Server Data, SAS BI Portlets, SAS Data Integration Studio Server Data etc.
SAS Configuration directory:
In SAS Platform the config files will be stored under the directory named Lev1. If you add additional server then the configuration of those server get stored in Lev2. Whenever you install new configuration like adding cluster the level gets increases to the next one. However the installation files gets stored in the same SASHome directory. The SASHome directory remains constant whereas config directory changes whenever you add additional config.
What SAS Admins need to know about the configuration directory hierarchy?
Whenever you define a new server in SAS Management Console, the server hierarchy reflects as directory in configuration directory in physical server.
Example: Let's say I define a new Server in SAS Management Console named as NewApp with Lgical Workspace Server, Logical Pooled Workspace Server and Logical Stored Process server. In OS level (physical server), if you navigate to the configuration directory (inside Lev1 directory), you can see a directory called NewApp with Workspace Server, Pooled Workspace Server and Stored Process Server as a sub-directory.
The corresponding directory in physical level or OS level holds the configuration file related to the new server you defined. For example configuration file like logconfig.xml where you define the location of logs to be stored.
Most of the time SAS Admins will do their work in SAS Management Console. If users report that they are not able to access SASApp or any server defined by admin, you should be able to visualize the configuration files path stored in physical server right from SMC. Few organization, won't provide access to physical level to SAS Admin. In that you can direct the OS team to the specific directory by looking at the server hierarchy in Server Manager Plugin.
In this article, I haven't give the exact location of configuration directory. It is not possible because you are allowed to choose any path you prefer. The base directory is based on the organization setup. However, after the main configuration directory Lev1, it will be same across any environment. So the configuration directory of SAS will be
In Linux: /any-base-directory/Lev1
In Windows: any-drive(C or D or E)\any-base-directory\Lev1
- SASHOME directory - Which contains SAS software
- SAS Configuration directory - Which contains configuration files of SAS software
Let's see in details about this directories.
SASHOME directory:
 |
| SASHome directory screenshot taken from Linux |
The SASHOME directory will holds the installation files of SAS softwares like SAS Addin for MS Office Server Data, SAS BI Portlets, SAS Data Integration Studio Server Data etc.
SAS Configuration directory:
In SAS Platform the config files will be stored under the directory named Lev1. If you add additional server then the configuration of those server get stored in Lev2. Whenever you install new configuration like adding cluster the level gets increases to the next one. However the installation files gets stored in the same SASHome directory. The SASHome directory remains constant whereas config directory changes whenever you add additional config.
What SAS Admins need to know about the configuration directory hierarchy?
Whenever you define a new server in SAS Management Console, the server hierarchy reflects as directory in configuration directory in physical server.
Example: Let's say I define a new Server in SAS Management Console named as NewApp with Lgical Workspace Server, Logical Pooled Workspace Server and Logical Stored Process server. In OS level (physical server), if you navigate to the configuration directory (inside Lev1 directory), you can see a directory called NewApp with Workspace Server, Pooled Workspace Server and Stored Process Server as a sub-directory.
The corresponding directory in physical level or OS level holds the configuration file related to the new server you defined. For example configuration file like logconfig.xml where you define the location of logs to be stored.
Most of the time SAS Admins will do their work in SAS Management Console. If users report that they are not able to access SASApp or any server defined by admin, you should be able to visualize the configuration files path stored in physical server right from SMC. Few organization, won't provide access to physical level to SAS Admin. In that you can direct the OS team to the specific directory by looking at the server hierarchy in Server Manager Plugin.
In this article, I haven't give the exact location of configuration directory. It is not possible because you are allowed to choose any path you prefer. The base directory is based on the organization setup. However, after the main configuration directory Lev1, it will be same across any environment. So the configuration directory of SAS will be
In Linux: /any-base-directory/Lev1
In Windows: any-drive(C or D or E)\any-base-directory\Lev1
Comments
Post a Comment