Good afternoon Everyone,
I have been doing the leg work to get Eclipse running and hopefully adopted by our team. In doing so I have had to work with our administrators to enable the appropriate roles and upgrade our kernel to allow debugging. Everything is working smoothly except for a small road block that I am hoping other experts can shed light on.
Our environment is setup so that new sessions are launched through the launch pad and all subsequent instances of that session need to be created using the "New Session" icon in SAPGUI. In other words, multiple sessions cannot be initiated from the launch pad. I am not sure of the exact reasoning for this, but I am told that this is because of;
1) Licensing
2) To prevent a few users from hogging resources
The problem then becomes, when a new embedded session is started in Eclipse, it tries to log the user into the system in a similar manner as if we were opening SAPGUI from the launch pad. If SAPGUI is already open in an Eclipse tab or in Windows, it will fail saying that a session already exists (See the screenshot below).
My question is:
1) What is the appropriate/best practice login configuration to solve this issue?
2) Does changing the configuration affect licensing and does it pose significant resource impact?
Thank you in advance for your responses.
