BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Babloo
Rhodochrosite | Level 12

How to restart Object Spawner and SAS Workspace server?

1 ACCEPTED SOLUTION

Accepted Solutions
PaulHomes
Rhodochrosite | Level 12

It depends. Workspace Servers are managed by the Object Spawner. Have a read of the pages mentioned above, especially the SAS Management Console page regarding the Server Manager Object Spawner actions: Stop, Quiesce, Refresh Spawner, and Refresh Application Server.  You also have the option to stop individual workspace server processes by navigating Server Manager > SAS Application Server > Logical Workpace Server > Workspace Server > hostname, connecting to the hostname, expanding the host name and then perfoming actions on the individual processes under the host name. See Use SAS Management Console to Connect to Servers and Display Server Monitoring Information.

 

Of course in a load-balanced clustered/grid environment things are a little more complex because you have multiple Object Spawners. You didn't say what type of SAS install you have?

View solution in original post

5 REPLIES 5
PaulHomes
Rhodochrosite | Level 12

You have several choices:

  1. Log onto the server and use the ObjectSpawner.sh or ObjectSpawner.bat script - see Using Scripts to Operate SAS Servers Individually
  2. ... or use SAS Environment Manager - see Using SAS Environment Manager to Operate Servers
  3. ... or use SAS Management Console - see Use SAS Management Console to Operate the SAS Object Spawner or the SAS/CONNECT Spawner
Babloo
Rhodochrosite | Level 12

How about work space server restart?

PaulHomes
Rhodochrosite | Level 12

It depends. Workspace Servers are managed by the Object Spawner. Have a read of the pages mentioned above, especially the SAS Management Console page regarding the Server Manager Object Spawner actions: Stop, Quiesce, Refresh Spawner, and Refresh Application Server.  You also have the option to stop individual workspace server processes by navigating Server Manager > SAS Application Server > Logical Workpace Server > Workspace Server > hostname, connecting to the hostname, expanding the host name and then perfoming actions on the individual processes under the host name. See Use SAS Management Console to Connect to Servers and Display Server Monitoring Information.

 

Of course in a load-balanced clustered/grid environment things are a little more complex because you have multiple Object Spawners. You didn't say what type of SAS install you have?

LinusH
Tourmaline | Level 20
A non-pooled workspace server cannot be restarted since it has no process, it's a logical meta data object.
The instantiated workspace server sessions can't be restarted either, just terminated.
Data never sleeps
anja
SAS Employee

In addition to the great information provided, enclosed some general doc on the SAS server/web server dependencies:

http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#p0d9d5nzmd8i4yn1usv2...

 

This might help to see how the servers "relate" to each other and what they are responsible for.

As you will see, Workspace Server is not listed as it is a process initiated by the Object Spawner (which itself depends on the Metadata Server).

 

Thanks

Anja

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 5 replies
  • 14337 views
  • 5 likes
  • 4 in conversation