Hi SAS Admins.
I want to update my licenses on SAS9.4 running on Windows Server 2012 R2 Standard, just wanna know if anyone knows the order to stop the services , I have attached a screenshoot:
Middle tier
Compute
Metadata
Thanks a lot.
If you're just stopping everything, the order doesn't really matter a huge amount. The order for restarting is more important. Here's the order we use (we have all of those, plus a few others):
SAS [Config-Lev1] SASMeta - Metadata Server
SAS [Config-Lev1] Web Infrastructure Platform Data Server
SAS [Config-Lev1] Object Spawner
SAS Connect Spawner
SAS[config-Lev1]DIPJobRunner
SAS [Config-Lev1] JMS Broker on port 61616
SAS [Config-Lev1] Cache Locator on port 41415
SAS[Config-Lev1]httpd-WebServer
SAS [Config-Lev1] SASServer1_1 - WebAppServer
SAS [Config-Lev1] SAS Environment Manager
SAS [Config-Lev1] SAS Environment Manager Agent
SAS Deployment Agent
If you really want to adhere to a stopping order, just reverse this.
Interested that you don't have a SASServer2_1 Web Application Server? Our system uses that for SAS Studio and Environment Manager.
If you're just stopping everything, the order doesn't really matter a huge amount. The order for restarting is more important. Here's the order we use (we have all of those, plus a few others):
SAS [Config-Lev1] SASMeta - Metadata Server
SAS [Config-Lev1] Web Infrastructure Platform Data Server
SAS [Config-Lev1] Object Spawner
SAS Connect Spawner
SAS[config-Lev1]DIPJobRunner
SAS [Config-Lev1] JMS Broker on port 61616
SAS [Config-Lev1] Cache Locator on port 41415
SAS[Config-Lev1]httpd-WebServer
SAS [Config-Lev1] SASServer1_1 - WebAppServer
SAS [Config-Lev1] SAS Environment Manager
SAS [Config-Lev1] SAS Environment Manager Agent
SAS Deployment Agent
If you really want to adhere to a stopping order, just reverse this.
Interested that you don't have a SASServer2_1 Web Application Server? Our system uses that for SAS Studio and Environment Manager.
So what about the ?
SAS PC Files Server service?
I'm sorry @SASJR1, hadn't noticed the OLAP or PC Files Server services. I don't know about them because they aren't in our environment. At a guess, they won't be dependent on any others (especially PCFF) so chances are you could just put them in anywhere. After Metadata anyway, and possibly after the Object and Connect Spawners? @AndyForeman might be able to give you an answer? He's been working on a brilliant wee Powershell script for starting and stopping services in the correct order.
Hi Nigel_Pain,
Will this be the correct order to start when I include "sas olap server service" and "Pc files services" or these don't matter.
SAS [Config-Lev1] SASMeta - Metadata Server
SAS [Config-Lev1] Web Infrastructure Platform Data Server
SAS[SAS-APP] SAS OLAP server
SAS [Config-Lev1] Object Spawner
SAS Connect Spawner
SAS[config-Lev1]DIPJobRunner
SAS [Config-Lev1] JMS Broker on port 61616
SAS [Config-Lev1] Cache Locator on port 41415
SAS[Config-Lev1]httpd-WebServer
SAS [Config-Lev1] SASServer1_1 - WebAppServer
SAS [Config-Lev1] SAS Environment Manager
SAS [Config-Lev1] SAS Environment Manager Agent
SAS Deployment Agent
Pc files services
This order looks sensible to me. PC Files Server can start/stop at any time.
OLAP should start with other Compute-tier services... per official documentation, start after Web Infrastructure Platform Data Server but before Object Spawner.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.