Previous Page | Next Page

Operating Your Servers

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 (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 startup parameters for each server, see the documentation references that are provided in Summary of Procedures for Server Operation.

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

You can use scripts to start, stop, pause, or resume the metadata server, an object spawner, an OLAP server, or a table 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:   

  [cautionend]

Follow these steps:

  1. 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).

  2. 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.bat1,2

    UNIX and z/OS: SASMeta/MetadataServer/MetadataServer.sh
    SAS object spawner Windows: ObjectSpawner\ObjectSpawner.bat

    UNIX and z/OS: ObjectSpawner/ObjectSpawner.sh
    SAS OLAP Server Windows: SASApp\OLAPServer\OLAPServer.bat1,2

    UNIX and z/OS: SASApp/OLAPServer/OLAPServer.sh1,2
    SAS Table Server Windows: SASTS\TableServer\TableServer.bat1,2

    UNIX and z/OS: SASTS/TableServer/TableServer.sh1,2
    1 Your installation might have different names for the SASApp directory.

    2 In single-machine installations that were migrated from SAS 9.1.3, the default location for the OLAP server script is SASMain\OLAPServer on Windows and SASMain/OLAPServer on UNIX or z/OS.

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

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

    -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, the OLAP server, or the table server, make sure that the metadata server is running.  [cautionend]

    -stop

    completely stops the server or spawner.

    Note:   

    • Stopping the metadata server stops other components, including object spawners, OLAP servers, table 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.

      [cautionend]
    -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

executes the program backupServer.sas, which is located in your metadata server startup directory. This program pauses the metadata server and copies your metadata repositories, the repository manager, the metadata journal file, and the metadata server's configuration files to a subdirectory called SASBackup in the metadata server's configuration directory. For details about this and other methods of performing backups, see About the Metadata Server Backup and Restore Utilities.

CAUTION:
For production backups and restores, it is highly recommended that you follow the best practices that are provided in Best Practices for Backing Up and Restoring Your System.   [cautionend]
-restore

executes the program restoreServer.sas, which is located in your metadata server startup directory. This program pauses the metadata server and copies your metadata repositories, the repository manager, the metadata journal file, and the metadata server's configuration files from the backup directory to the metadata server configuration directory. For details about this and other methods of performing restores, see About the Metadata Server Backup and Restore Utilities.

Use Individual Scripts to Operate Servers and Spawners

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

  1. 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).

  2. 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):

    Scripts for Operating Servers and Spawners
    Server or Spawner Script Name and Location
    SAS/CONNECT spawner Windows: SASApp\ConnectServer.bat

    UNIX and z/OS: SASApp/ConnectServer.sh
    SAS/SHARE server Windows: SASApp\ShareServer.bat

    UNIX and z/OS: SASApp/ShareServer.sh
    SAS Deployment Tester server Windows: DeploymentTesterServer\DeploymentTesterServer.bat

    UNIX and z/OS: DeploymentTesterServerDeploymentTesterServer.sh

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

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

    -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.

    -stop

    stops the server or spawner.

    -restart

    restarts the server or spawner.

    -status

    displays the current status of the server or spawner.

For more information, see Communications Access Methods for SAS/CONNECT and SAS/SHARE and SAS/SHARE User's Guide.

Starting or Stopping the SAS Services Application

The SAS Services Application deploys a set of services called Remote Services that are used by the SAS Information Delivery Portal, the SAS Stored Process Web application, and other Web applications. This application must be started before you start your Web application server. To start the SAS Services Application:

  1. Make sure that the metadata server is running.

  2. 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).

  3. Use one of the following scripts:

    • On Windows: SAS-configuration-directory\Lev1\Web\
      Applications\RemoteServices\RemoteServices.bat

    • On UNIX or z/OS: SAS-configuration-directory/Lev1/Web/
      Applications/RemoteServices/RemoteServices.sh

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

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

    -install

    installs the SAS Services Application as a Windows service.

    -remove

    removes the SAS Services Application service from Windows.

    -start

    starts the SAS Services Application.

    -stop

    stops the SAS Services Application.

    -restart

    restarts the SAS Services Application.

    -status

    displays the current status of the SAS Services Application.

Previous Page | Next Page | Top of Page

Copyright © 2011 by SAS Institute Inc., Cary, NC, USA. All rights reserved.