Hello,
We are looking for deploying SAS 9.4 ts1m3 on Windows server(x64), it's a 3 servers installation (process,meta,web). Can we have both version running on the same servers ?
Does the setup check for any previous install and take steps to upgrade instead of a full install ?
Thanks!
Laurent
From my experience, installing a SAS maintenance release is painless. It means replacing lots of already installed modules, and no or almost no changes in configuration files. If you followed the rule of putting your modifications in the _usermods files, it will come down to stopping the services, run the update, and restart the services, where stop and restart of web application server(s) will take the longest.
Do it on the Backup/Testing/DR server first, and you'll be good.
When I think of all the hassle you will have with selecting alternate network ports, a parallel install will be a major PITA and not worth it.
(anecdote: when installing 9.2 side-by-side with 9.1.3, I chose a network port of 8083 for one of the jboss interfaces, as 8081 and 8082 were already in use, and netstat showed 8083 to be unused. When the SSN installation wizard tried to start the servers, it always failed, and jboss complained about 8083 being in use. After two weeks of repeated install tries and consternation, I finally found that jboss uses 8083 internally. Would have been nice if the installation wizard had made me aware of this)
On UNIX, I'd give you a clear yes, as it is sufficient to have different SASHOME paths so that different SAS installations don't overwrite each other.
Care has to be taken when selecting network ports for the servers, though.
On Windows I'm not sure if there is sufficient differentiation with the registry entries, if such are used.
Thanks, good to know before we proceed. I imagine we will have to do this on every tier. I'll meet with my Windows server admin et will decide where we will be going with this.
Thansks again
I'd be interested to know why you are planning to install two mantenance releases on the same servers.
I can understand why you would install different versions separately like 9.3 and 9.4, but with maintenance releases upgrading the existing release is more usual.
Well I guess, we are insecure, it is our first maintenance release with SAS EBI and my Windows server admin is really cautious about it. Just the documentation is pretty long to read. As a SAS user before SAS EBI I use to install SAS/pc easily, but since it is on a server I don't have the credential to toy with the installation, I have to go trought a server admin and they have "The power to NO"
I'll have to sharpen my negociation skills.
Thanks for that. The reason I ask is that we will be doing a maintenance release upgrade shortly ourselves.
However we have two SAS environments: Production and a DR (Disaster Recovery) so we are able to apply maintenance to DR and test it without affecting current Production
We too have another environnement for testing... that's why I was really surprise by his request to have a parallele install... I guess some Windows server admin are more fearfull than others...
From my experience, installing a SAS maintenance release is painless. It means replacing lots of already installed modules, and no or almost no changes in configuration files. If you followed the rule of putting your modifications in the _usermods files, it will come down to stopping the services, run the update, and restart the services, where stop and restart of web application server(s) will take the longest.
Do it on the Backup/Testing/DR server first, and you'll be good.
When I think of all the hassle you will have with selecting alternate network ports, a parallel install will be a major PITA and not worth it.
(anecdote: when installing 9.2 side-by-side with 9.1.3, I chose a network port of 8083 for one of the jboss interfaces, as 8081 and 8082 were already in use, and netstat showed 8083 to be unused. When the SSN installation wizard tried to start the servers, it always failed, and jboss complained about 8083 being in use. After two weeks of repeated install tries and consternation, I finally found that jboss uses 8083 internally. Would have been nice if the installation wizard had made me aware of this)
Hello,
One last thing, with ts1m0, SAS studio wasn't available, when we will install ts1m3, will SAS studio be install automatically or is there a procedure to do so ?
Thanks again.
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.