Yes, the configuration is explained here https://sassoftware.github.io/saspy/install.html#iom And, given you use EG, you would be using the Remote IOM connection configuration.
EG doesn't not connect to Jupyter. Rather, Jupyter can execute Python code. saspy is a Python Module you can use to connect Python to the same workspace server as your EG client connects to. That's remote IOM. saspy and EG do not share anything nor interact with each other. They are two different clients which can each connect to workspace servers.
The configuration doc linked to will describe that you need the host name (or IP) of the Object Spawner (not the Metadata Server), and the port number for the workspace server (again, not the metadata server). Your metadata credentials would be the same as EG, probably (if you're connecting to the same server). The rest of the configuration options are documented in that configuration section.
Unlike EG, which uses the .Net IOM client, saspy uses the Java IOM client (as it works on other platforms than just windows) so, as documented, you will need Java (Version 7 or 8 work best). You also need 4 .jar files from your SAS instalation. You may find these jar files in your EG client, and those may work. I occasionally hear from customers that their EG jars didn't work (don't actually contain some classes that are in the copys of those jars in the real SAS deployment). If your EG jars work, then that's fine. Else you can copy the ones from where your workspace server is installed, or any other SAS9 install, to your client machine.
There is also a Troubleshooting Guide that shows all of the usual error you may get when the configuration steps aren't followed, and how to fix them: https://sassoftware.github.io/saspy/troubleshooting.html#iom
Hopefully, you can set up the config file with these and be up and running.
You can always open an issue on the saspy github site also, getting help directly from there if you need further assistance: https://github.com/sassoftware/saspy/issues
And, you can continue to reply here if you like too.
Thanks,
Tom
... View more