02-12-2018 04:36 AM
I have been looking around but I could not find this information, maybe you could help me clarify this ...
I have been using SAS either installed on my local machine, Windows based (usually for small developments) and on the server for deploying the solutions.
How does SAS Enterprise Guide submits the code to the SAS environment to be executed? Is there a executable that does the actual running? Where would this be located usually? Or is SAS running as a service?
02-12-2018 04:45 AM
Take a look at the product page:
And the system requirements:
You will note that most of EG is installed on a server, and locally there is a client. Code will be sent to the server for execution.
02-12-2018 10:39 AM
Enterprise Guide uses the so called IOM (Integrated Object Model) Interface to make a connection to a Workspace Server which can be a local or remote SAS Session.
Technically it uses some COM Interfaces.
02-12-2018 05:51 PM
Sample code in C# (and may not be accurate, but gives an idea):
SAS.Workspace ws = new SAS.WorkSpace();
ws.LanguageService lang = new SAS.LanguageService();
It uses the Integration Technologies client for whatever platform and executes it under the covers. Under the hood, it installs as a COM interface.
02-16-2018 04:35 PM
My name is George and I am SAS Technical Support Engineer.
Here is a quick explanation of how SAS Enterprise Guide submits code to a SAS server to be executed.
SAS EG in itself is just a visual client interface that allows you to submit code to a SAS server, but without either a Local connection to SAS or a remote SAS server connection, no processing can occur.
When you are connected to a SAS server via SAS EG, you have established what is called a Workspace Session, which is ultimately tied to an actual running SAS executable. This executable is launched via the Workspaceserver.bat file, which is simply a batch file that calls the SAS process to run with whatever options specified.
Once the code is run and results are generated, they are sent back to SAS EG where the end user can visually see the outcome.
When you connect to a SAS server from EG, you are basically running SAS Foundation on the server. For example, on a Windows SAS Server, you would actually see a sas.exe process tied to each user running EG (that is connected), from the Windows Task Manager.
SAS on the server is not running as a service, however, the SAS Metadata Server and the SAS Object Spawner are services being run behind the scenes.
I hope this helps.