SAS 9.4M9 DEPLOYED ON LINUX - WHAT'S NEXT STEP ON WINDOWS

[AliZiya]

Hello all,
I uninstalled the sas9.4m7 on linux then I have deployed the sas9.4m9 on Linux. Now what should we do on windows? When I entered the windows machine I see sas applications but they are still seen as m7. As far as I know I have to uninstall them first then I have to reinstall them again. Can I use the same sasdepot which I have used for m9 on Linux? Any recommandatitions? 

[LinusH]

I would say the most common ist hat you would have separate depots for different computing environments. The SW order for your depot will tell you the content of the order.

[Kurt_Bremser]

Our depot for SAS on AIX would also contain Windows software (EG, Management Console, Information Map Studio and Cube Studio).

[AliZiya]

Thank you for answer. So, what is the steps for installing windows eg applications? When I look at the documents I saw deployment on windows etc. I think that this is not needed couse I have deployed on Linux and my servers running there. I will use that windows machine for openning the sas applications (Management Console, enterprise guide etc.)

[Kurt_Bremser]

Usually, the depot contains EG in two versions: one for the Deployment Manager, and a standalone installer file  (.exe). What you use depends on how EG was installed initially.

[AliZiya]

Thank you for answer. So, what is the steps for installing windows eg applications? When I look at the documents I saw deployment on windows etc. I think that this is not needed couse I have deployed on Linux and my servers running there. I will use that windows machine for openning the sas applications (Management Console, enterprise guide etc.)

[ronf_sas]

If you Windows machines already have the M7 client software installed from the M7 Linux depot, you can run the SAS Deployment Wizard from the new M9 depot and the SAS Deployment Wizard should go into update mode and update the client software.

[SASKiwi]

BTW in my experience running a different version of the Windows SAS client tools compared to the server software doesn't cause significant problems and everything should still just work. It is still good practice to align versions, but for example where I work we run multiple versions of SAS server software, but only use the latest version Windows SAS client tools with the multiple versions.

[AliZiya]

I have successfully installed clients applications. Now I need to create a connection profile on Management Console. 

[AliZiya]

Everythings is installed. I validated the all servers on  Management console. Now I need to create a data library connection to teradatabase. 

[SASKiwi]

First step is to connect SMC to your SAS metadata server by creating a connection profile like this:

[AliZiya]

Thanks Kiwi, I have created a SMC connection profile with sasadm userid and password. And all the servers are valid. I need to create a data library for teradata in Management Console. 

[ronf_sas]

Here are instructions for creating a Teradata connection: https://documentation.sas.com/doc/en/bicdc/9.4/bidsag/p0trhta7jq1603n1ldzyw5xtmzq6.htm

[AliZiya]

Thank you. We have made the teradata connection. But now we have an other issue. We installed the direct 360 agent. We can start the direct agent successfully.  Then we ran the segments and tasks in ci360 then we got an error in on prem direct log. We had reported the problem sas support. We controlled the many things like certificates etc. Lastly They said this an SSLHandshake problem. You should fix that issue via your internal network team. Have you ever been come across with this issue ?