Understanding the State of Your System

Overview of the Configuration Directory Structure

Every server-tier and middle-tier host has a configuration directory which is the root of the SAS Intelligence Platform environment. The structure and contents of the directory vary depending on the host operating system, which products are installed, and whether the host machine is a server-tier host or a middle-tier host.

Throughout the SAS Intelligence Platform administration documentation, the variable SAS-configuration-directory is used to designate your configuration directory path. The default paths are as follows:

on Windows systems:

drive:\SAS\deployment-plan-name
on UNIX systems:

usr/local/deployment-plan-name or usr/local/sas

Note:
- In these paths, deployment-plan-name is the name that was specified when the deployment plan was created. If no name was specified, then the default name Config is used.
- You can specify a different path when you run the SAS Deployment Wizard. In UNIX environments, the installer generally overrides the path with the site's preferred location (for example, opt/sas/Config). The installer must have write permission to this path.
on z/OS systems, the directory that is specified in the CONFIG_DIR environment variable

In the configuration directory, the SAS Deployment Wizard builds a directory structure that contains important files for managing your system. Here is an example of the configuration directory structure for a single-machine Windows implementation:

[untitled graphic]

Note: Depending on your operating system and which products you have installed, your site might have different subdirectories. [cautionend]

About the Levn Subdirectory

The Levn subdirectory contains configuration information and other files for a particular installation instance. Lev1 is generally used for production environments. Additional levels, such as Lev2 and Lev3, can be used for environments that you install for purposes such as development and testing. During installation, the SAS Deployment Wizard enables you to specify the level number.

The contents of the Levn directory depend on which components are installed on the machine. Its contents might include the following:

on UNIX and z/OS machines, a script called sas.servers that you can use to start, stop, or restart all of the SAS servers and spawners on the machine in the correct order by using a single command.
an AppData subdirectory, which contains data sets for the SAS Content Server repository. It also contains data that is installed for the use of specific applications (for example, SAS BI Dashboard).
a subdirectory for the application server.
a subdirectory for the metadata server.
subdirectories for other SAS servers and spawners, including the SAS object spawner, the SAS Deployment Tester Server, the SAS Table Server, the SAS/CONNECT spawner, and the SAS/SHARE server.
a Web subdirectory for files related to Web applications .
logs and documents that were created during the installation and configuration process

For more details about the Levn directory, see Contents of the Levn Subdirectory.

About the Application Server Subdirectory

On machines where components of a SAS Application Server are installed, the Levn directory contains an application server subdirectory. A SAS Application Server is a logical entity that contains specific servers (for example, a SAS Workspace Server and a SAS Stored Process Server) that execute SAS code. Application server subdirectories are named as follows:

SASApp is the default name that the SAS Deployment Wizard assigns to directory for the first application server. If you assigned a different name when you ran the SAS Deployment Wizard, then the subdirectory is named accordingly.
If you configure more than one application server, then additional directories are created that correspond to each of the application server names.
If you have a single-machine installation that was migrated from SAS 9.1.3, then the application server subdirectory is typically called SASMain.

The application server subdirectory contains the following items:

a subdirectory for each component of the application server, including the workspace server, the pooled workspace server, the OLAP server, the stored process server, the SAS/CONNECT server, batch servers, and grid servers (if applicable). Each of these subdirectories contains the server's start-up scripts, configuration files, logconfig.xml files to configure logging, and Logs directories to store log files.
a subdirectory for data that is used by the application server.
a SASEnvironment subdirectory to store deployed jobs, job steps, SAS format and informat catalogs, and user-created SAS autocall macros that are needed to perform processing on the application server
configuration files that apply to all components of the application server

For more details about this subdirectory, see Contents of the Application Server Subdirectory (SASApp or SASMain). For information about the server configuration files that are contained in this subdirectory, see Configuration Files for Components of SAS Application Servers.

About the SASMeta Subdirectory

On the machines where the metadata server is installed, the Levn directory includes a subdirectory for the metadata server's files. SASMeta is the name that the SAS Deployment Wizard assigns to the metadata server context and, in turn, to this directory.

The SASMeta directory contains the following items:

configuration files that apply to the SASMeta application server components, which include a workspace server and a DATA step batch server.
a WorkspaceServer subdirectory, which contains files for the SASMeta workspace server. This server is used to execute metadata utilities. The subdirectory contains start-up scripts, configuration files, a logconfig.xml file, and a Logs directory for this server.
a BatchServer subdirectory, which contains files for the SASMeta DATA step batch server. This server is used to schedule backup jobs that are created by the Backup Wizard. The subdirectory contains start-up scripts, configuration files, a logconfig.xml file, and a Logs directory for this server.
SASEnvironment and Data subdirectories that can be used by the workspace server.
a MetadataServer subdirectory, which contains the following:
- the metadata server's start-up and management scripts, configuration files, logconfig.xml files to configure logging, and Logs directories to store log files.
- programs to back up and restore the metadata server (for details, see About the Metadata Server Backup and Restore Utilities).
- a subdirectory called MetadataRepositories, which contains a subdirectory for each metadata repository. These subdirectories contain the SAS data sets that store your metadata.
- a subdirectory call rposmgr, which contains data sets for the repository manager.
  CAUTION:
  The MetadataRepositories and rposmgr directories contain data sets that are critical to the operation of your system.
  To safeguard the integrity of your system:
  - Never move, delete, modify, or directly read the data sets in these directories. These data sets should be accessed only by metadata server processes.
  - Do not place other files in these directories.
  - Back up the contents of these directories regularly, as described in Best Practices for Backing Up and Restoring Your System.
- a directory for the metadata server journal.
- a SASBackup directory that can be used as a destination for backing up the metadata server.

For more information about the metadata server configuration files, see Configuration Files for the Metadata Server. For a complete list of the contents of the MetadataServer subdirectory, see Contents of the Metadata Server Subdirectory (SASMeta).

About the Web Subdirectory

On middle-tier machines (that is, machines with installed Web components), the Lev1 directory contains a subdirectory called Web. For details, see Contents of the Web Subdirectory. For information about administering middle-tier applications and components, see the SAS Intelligence Platform: Web Application Administration Guide.

Top of Page