Previous Page | Next Page

Operating Your Servers

Using SAS Management Console to Operate SAS Servers


Obtain the Appropriate User Credentials, and Clear Cached Credentials (If Necessary)

To connect to a server or spawner in SAS Management Console, you must have the appropriate user credentials. Membership in the SAS Administrators group typically provides sufficient rights and permissions. For details, see Who Can Do What in the Server Manager Plug-in.

If you attempt to connect to a server or spawner and you are denied access, make sure you have the appropriate credentials. After your credentials are updated, be sure to clear the credentials cache before you try to connect again. To clear the credentials cache, click File [arrow] Clear Credentials Cache in SAS Management Console.


Use SAS Management Console to Stop, Pause, Resume, or Reset the SAS Metadata Server

You can use SAS Management Console to stop, pause, or resume the SAS Metadata Server. You can also use SAS Management Console to reset the metadata server in order to recover memory on the host machine.

Note:   Before using these features to operate the metadata server, see About SAS Metadata Server States.  [cautionend]

Follow these steps:

  1. Log on to SAS Management Console as a user with the appropriate credentials.

  2. On the Plug-ins tab, expand the Metadata Manager node, and right-click the Active Server node.

  3. Select one of the following actions:

    Stop

    completely stops the metadata server.

    Note:   

    • Stopping the metadata server stops other components, including object spawners, OLAP servers, table servers, SAS/CONNECT spawners, and SAS/SHARE servers.

    • To start the metadata server after stopping it, you must use a script. If you want to be able to resume processing without using a script, use Pause [arrow] Offline instead.

      [cautionend]
    Pause [arrow] Offline

    pauses the metadata server to the Offline state. In the Pause Comment dialog box, you can enter a comment that provides information about the pause action. When a client attempts to read or write metadata, the comment is appended to the appropriate message and displayed as follows:

    Error accessing metadata: The GetMetadataObjects request failed because the server is paused for OFFLINE use. The reason for the server pause is comment.

    Pause [arrow] Administration

    pauses the metadata server to the Administration state. In the Pause Comment dialog box, you can enter a comment that provides information about the pause action. When a user who is not in the Metadata Server: Unrestricted role attempts to read or write metadata, the comment is appended to the appropriate message and displayed as follows: Error accessing metadata: The GetMetadataObjects request failed because the server is paused for ADMINISTRATION use. The reason for the server pause iscomment.

    Resume

    returns the metadata server to the Online state (if the current state is Offline or Administration). The metadata server resumes accepting client requests to read and write metadata and re-opens repository containers as clients request metadata from them.

    Reset

    unloads from memory and closes the containers of all registered repositories in order to recover memory on the metadata server host. The metadata server then re-opens repository containers as clients request metadata from them. This option is useful if the host computer experiences an out-of-memory condition.

To start the metadata server, see Running Servers as Windows Services and Using Scripts to Operate SAS Servers Individually. For information about metadata server startup parameters, see Options for the Metadata Server Invocation Command.


Use SAS Management Console to Stop, Pause, Resume, Quiesce, or Refresh the SAS Object Spawner

You can use SAS Management Console to stop, pause, resume, quiesce, or refresh the object spawner. Follow these steps:

  1. Log on to SAS Management Console as a user with the appropriate credentials.

  2. On the Plug-ins tab, expand the Server Manager node and the Object Spawner node.

  3. Right-click the object spawner instance that you want to administer, and click Connect.

  4. After you are connected, you can select any of the following actions:

    Refresh

    updates the SAS Management Console display with current information about the spawner.

    Disconnect

    discontinues your current connection to the spawner.

    Stop

    stops the spawner process, including any active client requests.

    Note:   If you want active requests to be completed first, use Quiesce.  [cautionend]

    Pause

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

    Resume

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

    Quiesce

    stops the spawner process after the spawner has finished processing all active client requests.

    Refresh Spawner

    re-initializes the spawner. During re-initialization, the spawner stops any spawned servers that are currently running, rereads the metadata in the spawner definition, and applies any new options that have been set.

    Note:   If the spawner is in a paused state when the Refresh Spawner action occurs, the spawner remains paused after it is re-initialized.  [cautionend]

To start the object spawner, see Running Servers as Windows Services and Using Scripts to Operate SAS Servers Individually. For information about startup options for the object spawner, see Spawner Invocation Options in the SAS Intelligence Platform: Application Server Administration Guide.


Use SAS Management Console to Stop, Pause, Resume, Quiesce, or Refresh the SAS OLAP Server

You can use SAS Management Console to stop, pause, resume, quiesce, or refresh the SAS OLAP Server. Follow these steps:

  1. Log on to SAS Management Console as a user with the appropriate credentials.

  2. On the Plug-ins tab, expand the Server Manager node, the application server node (for example, SASApp), and the node for the logical OLAP server.

  3. Right-click the OLAP server instance that you want to administer, and click Connect.

  4. After you are connected, you can select any of the following actions:

    Refresh

    updates the SAS Management Console display with current information about the OLAP server.

    Disconnect

    discontinues your current connection to the OLAP server.

    Stop

    stops the OLAP server process, including any active client requests.

    Note:   If you want active sessions to be completed first, use Quiesce.  [cautionend]

    Pause

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

    Resume

    resumes the OLAP server process when it is in the paused state.

    Quiesce

    stops the OLAP server process after the server has finished processing all active sessions.

    Note:   To start the OLAP server after quiescing it, you must use a script. If you want to be able resume processing without using a script, use Pause instead.  [cautionend]

To start the OLAP server, see Running Servers as Windows Services and Using Scripts to Operate SAS Servers Individually. For information about OLAP server startup parameters, see System Options for Application Server Components in the SAS Intelligence Platform: Application Server Administration Guide.


Use SAS Management Console to Control Processes on Servers

You can use SAS Management Console to stop, pause, resume, or quiesce a process on a workspace server, pooled workspace server, or stored process server. Follow these steps:

  1. Log on to SAS Management Console as a user with the appropriate credentials.

  2. On the Plug-ins tab, expand the Server Manager node and the application server node (for example, SASApp).

  3. Expand the node for the logical server that is running the process, and then expand the node for the server instance that is running the process. The server's available connections are displayed in the server tree and in the right pane.

  4. Highlight the appropriate host machine name, as shown in this example.

    [Host machine selected]

    Right-click the mouse, and click Connect. For each process that is active for that connection, the right pane displays the process ID, the process owner, and the port, as shown in this example:

    [Active processes in Server Manager tree]

  5. In the Server Manager tree, expand the node for the connection that you are working with. The active processes for the connection are displayed in the tree.

  6. Highlight the process that you want to stop, pause, resume, or quiesce, as shown in this example:

    [Process highlighted in Server Manager tree]

    In the right pane, the following tabs become active: Clients, Options, and Loggers. For pooled workspace servers and stored process servers, the Sessions and Log tabs also become active.

    Note:   If some tabs are disabled, then you need additional user credentials. See Who Can Do What in the Server Manager Plug-in. For details about the tabs, see Use the Server Manager Tabs to Obtain Monitoring Information and to Adjust Logging Levels (If Needed).  [cautionend]

    .
  7. Right-click the mouse and select one of the following actions:

    Stop

    stops the server process, including any active client requests.

    Note:   

    • If you want active requests to be completed first, use Quiesce.

      [cautionend]
    Pause

    causes the server process to finish processing all active client requests and to stop accepting new requests.

    Resume

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

    Quiesce

    stops the server process after the server has finished processing all active client requests.

Previous Page | Next Page | Top of Page