Suppose you have a bundle like Office Analytics licensed but you are trying to avoid the complexities of a metadata deployment in SAS 9.4M6. Before this change you would have to tell your client they were limited to SAS Studio Basic as their programming environment. Now SAS Enterprise Guide 8.2 is also an option! Use SAS Studio Basic Object Spawner with Enterprise Guide 8.2 Here are the steps I did to confirm this with SAS Studio 3.8 and SAS 9.4M6. Deploy SAS Studio Basic 3.8 as documented in the SAS Studio Basic 3.8 Admin Guide (Chapter 4). https://go.documentation.sas.com/api/docsets/webeditorag/3.8/content/webeditorag.pdf This should result in a deployment URL of something like this: http://sas94vprod.XXXX.com:38080 Provided that you accepted the defaults in the deployment wizard then you also have an object spawner running on sasv94vprod.XXXX.com at port 38591. This is the object spawner that you want to use in the EG server connection dialog. Specify sign-in credentials that match any sign-in credentials that you would use with the SAS Studio Basic web application. Click on "Save" and now you should be able connect to the SAS Studio Basic services with EG. License Issues The main thing to keep in mind is that this only works if you have a license that supports deploying Enterprise Guide with a metadata server. You could do a metadata deployment, but to simplify your deployment you are choosing a metadata-less route. To confirm this run PROC SETINIT. Product expiration dates:
---Base SAS Software 30DEC2020 (CPU A)
---SAS/STAT 30DEC2020 (CPU A)
---SAS/GRAPH 30DEC2020 (CPU A)
---SAS/IML 30DEC2020 (CPU A)
---SAS/CONNECT 30DEC2020 (CPU A)
---SAS Integration Technologies 30DEC2020 (CPU A)
---SAS Enterprise Guide 30DEC2020 (CPU A) The key one is SAS Integration Technologies. That is the key license to enable this support. If you only have: ---SAS Workspace Server for Local Access
30JUN2020 (CPU A) Then you don't have the proper license to connect with Enterprise Guide 8.2. SAS Studio Basic will work fine, but not EG. Another possible issue is that port 38591 may not be open on your SAS server. Your firewall or security policy may block inbound traffic which will prevent Enterprise Guide 8.2 from functioning in this manner. I don't believe the planning documentation references this port for a SAS Studio Basic deployment - only the web port at 38080 or 38443. See https://linuxhint.com/list_open_ports_firewalld/ if you are using firewalld.
... View more