Initial Directory Structure

the root directory for the configuration environment. The configuration environment identifies an entire set of related information such as production levels, SAS application servers, scripts, utilities, and documentation. The name of this directory is site-specific.

the production level directory. Some projects also contain Lev2 (testing level) and Lev3 (development level) directories.

the name of the SAS application server on the machine that hosts the SAS Metadata Server. The SAS application server is a logical framework in which SAS applications execute. A SAS application server provides a place to locate libraries, schemas, directories, and other resources that are available to SAS servers, regardless of the type of server. Because this framework is separate from the launching mechanism, the administrator can deploy applications in several modes and ensure that the applications will execute properly in that mode.

the physical directory that corresponds to the object spawner definition in a SAS Metadata Repository. The object spawner instantiates SAS Workspace Servers and SAS Stored Process Servers. Typically, the spawner is started as a service in Windows.

The ObjectSpawner directory contains these items:

• the logs subdirectory, which stores any log files generated by the object spawner

• OMRConfig.xml, which contains the metadata server connection information

• startup scripts and configuration scripts

Note:   During the deployment process, you are given the option to install and configure the spawner. However, if you are installing SAS Workspace Servers or SAS Stored Process Servers, then the spawner is automatically installed because those servers must be started by a spawner.  

the physical directory that corresponds to the SAS OLAP Server definition in the SAS Metadata Repository. It contains these items:

• the sasuser subdirectory, which is a SAS library that contains SAS catalogs that enable you to tailor features of SAS for your needs. SAS assigns the SASUSER library at invocation

• the logs subdirectory that stores any log files generated by the SAS OLAP Server invocation

• the work subdirectory, which stores temporary work files

• any other utility files that are used to manage the server

the physical directory that corresponds to a server definition in a SAS Metadata Repository. This server executes stored processes. A stored process is a SAS program that is stored on a server and can be executed as required by requesting applications. This directory contains these items:

• a sample SAS application named LoadPlannedStoredProcessSamples.sas that can be used to load stored process samples into the metadata repository

• the logs subdirectory, which stores any log files generated by this server invocation

• any other utility files that are used to manage the server

the physical directory that corresponds to a server definition in a SAS Metadata Repository. This server fulfills client requests for specific SAS sessions. This directory contains these items:

• the logs subdirectory, which stores any log files generated by this server invocation

• any other utility files that are used to manage the server

contains information related to deploying Web applications, including policy files, service configuration files, and service deployment files.

contains the Web applications archive (WAR) files for your Web applications, such as SAS Information Delivery Portal. These WAR files are actually JAR files that contain all of the files that comprise the Web application, including servlets, JavaServer Pages, and HTML documents.

Note:   If you are using the Tomcat servlet container to execute your Web applications, then the SAS Configuration wizard has already copied these WAR files to Tomcat's webapps directory. If you are using a J2EE application server for this purpose, then you must manually deploy these files to your server's webapps directory. Follow the instructions in your vendor's documentation for deploying an application.