Architecting, installing and maintaining your SAS environment

Question regarding sequence in which one should install and configure SAS IP 9.3 for following architecture: Meta data, Compute and Midtier server each on its own Linux server, and a Windows Client on a Windows Terminal Server client

Reply
Contributor
Posts: 22

Question regarding sequence in which one should install and configure SAS IP 9.3 for following architecture: Meta data, Compute and Midtier server each on its own Linux server, and a Windows Client on a Windows Terminal Server client

Is there a recommended order in which one should install SAS - Servers followed by Client, or Client followed by Servers?

Should we install and configure SAS on the Linux servers first (in order of Install Metadata, install Compute, install Midtier, followed by configure Metadata, configure Compute and compute Midtier) and then install and configure the SAS CLient pieces on our WIndows Terminal Server Client? Or should we do the Client first before we do the Server pieces?

Thanks.

SAS Employee
Posts: 99

Re: Question regarding sequence in which one should install and configure SAS IP 9.3 for following architecture: Meta data, Compute and Midtier server each on its own Linux server, and a Windows Client on a Windows Terminal Server client

The sequence is described in the 9.3 Installation and Configuration Guide.  Here's the relevant section:

http://support.sas.com/documentation/cdl/en/biig/62611/HTML/default/n05002intelplatform00install.htm...

Technically you could do all your installs first, and then come back and do your configurations in the sequence described in the aforementioned link; however, it's usually most convenient to do your installation and configuration together on each machine, again in the sequence described.  The order is essentially metadata->compute->midtier->clients.

Valued Guide
Posts: 3,208

Re: Question regarding sequence in which one should install and configure SAS IP 9.3 for following architecture: Meta data, Compute and Midtier server each on its own Linux server, and a Windows Client on a Windows Terminal Server client

I would surely follow mark's link and take a well note on that segregation on "Ïnstall" and "configure". Those are tow different steps.

The install step in the installation is what commonly is indicated/known as the installation. 

The configuration is different as it can be more seen as System integration - Wikipedia, the free encyclopedia or Configuration design - Wikipedia, the free encyclopedia    

Before doing those steps you can need several desktop clients up and running. And  those clients can be needed to be adjusted after all servers are up and running. (sasenv.ini)

Your question is hitting an area SAS institute is missing the alignment what is happening in the world.

As example Linux Directory Hierarchy: Oriented to the Software Parts is giving the background on folder namings with the ratio why to do that in Linux and the usage of rpm.  (SDW is not aligned to that)

You want to install the SAs clients on a Citrix client. That is also a signal something is going on the desktop side. The SAS java clients are as zero impact to be copied. The challenge with those are the ini- files (xmx limits java runtimes etc). With Eguide, Base  and AMO there is thight MS dependicy by the windows register, the first two are being installable by a MSI approach in 9.4 .  

---->-- ja karman --<-----
Trusted Advisor
Posts: 1,141

Re: Question regarding sequence in which one should install and configure SAS IP 9.3 for following architecture: Meta data, Compute and Midtier server each on its own Linux server, and a Windows Client on a Windows Terminal Server client

As of Mark and Jaap advises, you can follow your initial guess of guideline.

Only a couple of additional remarks, not so important for your question, but can be interesting:

- If you plan to check and install hot fixes, I think it is better to do after installation and before configuration (it saves time and troubles!)

- You can install clients any time, from my point of view. And some clients doesn;t really require configuration. BUT, if you plan to configure also the clients, you will need a metadata server to reach, before the configuration of the clients, of course.

Ask a Question
Discussion stats
  • 3 replies
  • 351 views
  • 1 like
  • 4 in conversation