Using Scripts to Operate SAS Servers Individually

About Using Scripts to Operate Servers

The configuration directory for each SAS server and spawner contains a script that enables you to operate the server or spawner individually from a command line.

On Windows machines, depending on the options that were selected during installation, the SAS Deployment Wizard might have also added shortcuts to your Start menu to enable you to start, stop, pause and resume servers and spawners.

On UNIX and z/OS systems, you can use the sas.servers script to start and stop servers with a single command. For more information, see Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers. On z/OS systems, SAS recommends operating servers as started tasks. See Starting and Stopping SAS Servers on z/OS.

For information about the start-up parameters for each server, see the documentation references that are provided in Summary of Procedures for Server Operation.

Note: If you need to customize a server script, do not directly update the script. Instead, add your customizations to the corresponding file that is named server-name_usermods_.bat or server-name_usermods.sh. Use of these files prevents your customizations from being overwritten when a new SAS release is installed.

Use Individual Scripts to Operate the SAS Metadata Server, SAS Object Spawner, SAS OLAP Server, and SAS SAS Framework Data Server

You can use scripts to start, stop, pause, or resume the metadata server, an object spawner, an OLAP server, or a framework data server from the DOS command line, the UNIX console, or the z/OS console. The scripts also enable you to install or remove a server or spawner as a Windows service and to display the server or spawner's current status.

Note: The following

The metadata server must be running before you can start an object spawner or an OLAP server.
Before using scripts to operate the metadata server, see About SAS Metadata Server States.

Follow these steps:

On Windows, log on as a user who is a member of the host operating system's Administrators group. On UNIX or z/OS, log on as the SAS Installer user (for example, sas).

Use one of the following scripts, which are located in the path SAS-configuration-directory/Lev1:

Scripts for Operating Servers and Spawners

Server or Spawner	Script Name and Location
SAS Metadata Server	Windows: `SASMeta\MetadataServer\MetadataServer.bat`1 UNIX andz/OS: `SASMeta/MetadataServer/MetadataServer.sh`1
SAS object spawner	Windows: `ObjectSpawner\ObjectSpawner.bat` UNIX andz/OS: `ObjectSpawner/ObjectSpawner.sh`
SAS OLAP Server	Windows: `SASApp\OLAPServer\OLAPServer.bat`2 UNIX and z/OS: `SASApp/OLAPServer/OLAPServer.sh`2
SAS Framework Data Server	Windows: `FrameworkServer\dffedsvrcfg\dffedsvrcfg.bat` UNIX and z/OS: `FrameworkServer/dffedsvrcfg/dffedsvrcfg.sh`
1In single-machine installations that were migrated from SAS 9.1.3, the directory name might be SASMain instead of SASMeta.
2Your installation might have a different name for the SASApp directory.

You can use any of the following arguments with these scripts:

Note: The hyphen in front of each argument is optional.

-install

installs the server or spawner as a Windows service.

-remove

removes the server or spawner service from Windows.

-start

starts the server or spawner.

Note: Before you start the object spawner or the OLAP server, make sure that the metadata server is running.

-stop

completely stops the server or spawner.

Note:

Stopping the metadata server stops other components, including object spawners, OLAP servers, SAS/CONNECT spawners, and SAS/SHARE servers.
Before you stop an OLAP server, you should first stop the active sessions, as follows:
1. In SAS Management Console, expand the Monitoring node and the SAS OLAP Server Monitor node.
2. Right-click the name of the logical SAS OLAP Server, and select Connect.
3. In the dialog box that appears, enter your user name and password and click OK.
4. Right-click the name of each session that you want to close, and select Close Session.

-restart

stops and then starts a running server or spawner.

-pause

causes the server or spawner to finish processing all active client sessions and to stop accepting new requests.

When this option is used with the metadata server, the server is placed in the Offline state.

-resume

resumes the server or spawner process when it is in the paused state.

When this option is used with the metadata server, the server is returned to the Online state if the current state is Offline or Administration.

-status

displays the current status of the server or spawner.

The metadata server script has two additional options:

-backup

uses the metadata server’s backup facility to copy all of your metadata repositories, the repository manager, and the contents of the metadata server's configuration directory to the configured backup location. The backup process executes in a separate thread while the metadata server is running. Therefore, the server does not need to be paused. For more information, see Backing Up and Recovering the SAS Metadata Server.

CAUTION:

For production backups, it is highly recommended that you follow the best practices that are provided in this guide.

See Best Practices for Backing Up and Restoring Your SAS Content.

-optimizeIMDB

optimizes the usage of memory on the metadata server. This option analyzes the handling of character variables, checking for items such as unnecessary indexes, long character variables that can be stored as variable-length strings, and duplicate strings. To apply the results of the analysis, you must pause and resume (or restart) the server after executing this command option. For more details, see Using optimizeIMDB to Optimize and Report on Metadata Server Memory Usage.

Use Individual Scripts to Operate the SAS/CONNECT Spawner, SAS/SHARE Server, and SAS Deployment Tester Server

To use an individual script to operate the SAS/CONNECT spawner, SAS/SHARE server, and SAS Deployment Tester server, follow these steps:

On Windows, log on as a user who is a member of the host operating system's Administrators group. On UNIX and z/OS, log on as the SAS Installer user (for example, sas).

Use one of the following scripts, which are located in the path SAS-configuration-directory/Lev1 (your installation might have a different name for SASApp subdirectory):