Hello community,
at the moment I am checking NWBC version 4 PL 17. If I start the NWBC and open a new transaction, e.g. SE16, the Running Object Table (ROT) looks like this:
Only the SAPGUISERVER object is alive. I think this is the expected behavior.
But if I open the transaction e.g. SMMS (Message Server Monitor) the ROT looks like this:
As you can see, beside the SAPGUISERVER, is also the SAPGUI object alive.
From this point it is not longer possible to differentiate exactly which is the correct object for the session. But if you work with SAP GUI Scripting this is the only criterion, look also here.
Does anybody knows the circumstances why the NWBC creates two objects instead of one as expected?
Is it possible to suppress the instantiation of the SAPGUI class in the context of the NWBC?
If you work with desktop automation mechanisms in the context of SAP GUI Scripting, you have no chance to differentiate. And if you use the same scenario with one SAP system, on the one hand with NWBC and on the other hand with SAP GUI for Windows at the same time, it is not possible to work unambiguously.
Thanks for tips and hints.
Cheers
Stefan