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

We start the sas 9.4 mid-tier services in the following order.
1.JMS Broker
2.Cache Location
3.SAS Web Server
4.SAS Web Application Server

And we have the other sas web application servers like
SAS BI,SAS CI,SAS EM and SAS VAAR.

I do not think these servers depend on each other. Is there any specific sequence these servers need to be started?

1 ACCEPTED SOLUTION

Accepted Solutions
JuanS_OCS
Amethyst | Level 16

Hello @muni2chandra84,

 

in case you have a multiple web application servers deployment, you need to ensure SASServer1_1 (BI) is started before anyone else, since it includes the basic core, the SAS Web Infrastructure Platform, which includes components such as the SAS Content Server, the SASLogon, and many others. 

 

Besides this dependency, all the others you can start them afterwards. Of course, the more you connect at the same time, the more connections from the pool to SASServer1_1 they will take and will need to wait.

View solution in original post

2 REPLIES 2
JuanS_OCS
Amethyst | Level 16

Hello @muni2chandra84,

 

in case you have a multiple web application servers deployment, you need to ensure SASServer1_1 (BI) is started before anyone else, since it includes the basic core, the SAS Web Infrastructure Platform, which includes components such as the SAS Content Server, the SASLogon, and many others. 

 

Besides this dependency, all the others you can start them afterwards. Of course, the more you connect at the same time, the more connections from the pool to SASServer1_1 they will take and will need to wait.

SangramjitPanda
Obsidian | Level 7

Even the Mid-Tier Services are depenendent on one other and usually they follow a squence while we start or stop the Mid-Tier Services.

 

Path: ~/config/Lev1/

File name: sas.servers.mid

 

If you stop or start or check the status of the mid-tier services, they will follow up a sequence while starting and stopping.

 

Execute the command for more detials: ./sas.servers.mid status/start/stop

Choose one option as per the req.

 

 

 

 

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
  • 2 replies
  • 4222 views
  • 1 like
  • 3 in conversation