Step 1 : Prevent users
Prevent users from stopping the SAS platform and its unavailability at least 10 minutes before the operation.
Via email and Hangout group Torrelavega Analytics
Step 2 : Stop service in the correct order on all machines
STEP 2.1 : RDP Web Server Connect to Web Server Tier via RDP, with an account had administrator privileges → Computer : wdcsswd31 → User name : eua\admin_account → Password: ****** → Connect |
|
STEP 2.2 : Services Web Server Check SAS services on Web Server → Stop manually all SAS services in the correct order: - SAS Deployment Agent |
 |
STEP 2.3 : RDP Application Server
Connect to Application Server Tier via RDP, with an account had administrator privileges → Computer : wdcssad31 → User name : eua\admin_account → Password: ****** → Connect |
|
STEP 2.4 : Services Aplication Server Check SAS services on Aplication Server → Stop manually all SAS services in the correct order: - SAS Deployment Agent |
|
Step 3 : SDM Renew SAS Software
STEP 3.1 :Find and launch SDM with admin privilege
Go to SASHome and find sasdm.exe → D:\SAS\software\SASHome\SASDeploymentManager\9.4\ sasdm.exe
→ Run as administrator |
|
STEP 3.2 : User account control
Allow this app → Yes |
|
STEP 3.3 : SDM started
|
|
STEP 3.4 : Choose Language :
→ english
→ OK |
|
STEP 3.5 : SDM initialized with selected language
|
|
STEP 3.6 : Select SAS deployment Manager Task:
→ Renew SAS Software
→ Next |
|
STEP 3.7 : Select License Renewal :
→ Select All
→ Next |
|
STEP 3.8 : Specify SID (SAS Installation Data) File location
→ Select path With new License on the server
→ Next |
|
STEP 3.9 : Summary of STEP and tool update
→ Start |
|
STEP 3.10 : Deployment complete
→ Check if all it's OK
→ Next |
|
STEP 3.11: Additional Resources
→ Finish
|
|
Step 4 : SDM Update SID File in Metadata
STEP 4.1 :Find and launch SDM with admin privilegeon
Go to SASHome and find sasdm.exe → D:\SAS\software\SASHome\SASDeploymentManager\9.4\ sasdm.exe
→ Run as administrator |
|
STEP 4.2 : User account control
Allow this app → Yes |
|
| STEP 4.3 : SDM initialized with selected language |  |
STEP 4.4 : Choose Language :
→ english
→ OK |
|
| STEP 4.5 : SDM initialized with selected language |
|
STEP 4.6 : Select SAS deployment Manager Task
→ Update SID File in Metada
→ Next |
|
STEP 4.7 : Select Configuration Directory/Level
Select Directory: by default → D:\SAS\software\Config
Configuration level → Lev1
→ Next |
|
STEP 4.8 : Specify Connection Information
User ID : → sasadm@saspw
Password : → ******
→ Next |
|
STEP 4.9 : Specify SID (SAS Installation Data) File location
→ Select path With new License on the server
→ Next |
|
STEP 4.10 : Summary of STEP and tool update
→ Start |
|
STEP 4.11 : Deployment complete
→ Check if all it's OK
→ Next |
|
STEP 4.12:
Additional Resources
→ Finish
|
|
Step 5 : Start services in the correct order on all machines
STEP 5.1 : Start Services on Aplication Server Check SAS services on Application server → Start manually all SAS services in the correct order: - SASMeta - Metadata Server or →Reboot Application server | |
STEP 2.2 : Strat Services Web Server Check SAS services on Web Server → Start manually all SAS services in the correct order: - JMS Broker on port 61616 |
|
Step 5 :Launch SAS Lasr Server for SAS Visual Analytics (VA)
When the service Platform restart, it will be necessary to start SAS LASR server for Visual Analytic.
- Open URL VA : http://wdcsswd31.eua.solvay.com/SASLogon/logout?_sasapp=Visual+Analytics+Hub+7.4
- Connect and open Administrator page: SAS Home > Administrator
- Select Tab "LASR Sever" or open it in the menu LASR > Manage Servers
- Check if Servers is started, and if not, select all and start them
Step 6 : Check Platform
- Check SAS Entreprise Guide
- Open SEG and execute a simple code like : proc setinit; run;
- Open VA and check if LASR server are started