Intermittent Connection Problem with AddOn, please explain the logon process!

[jangroetzner]

I have a problem intermittent errors on AddOn using getDICompany.

I have seen many workarounds here, but nobody deeply analyzed the problem.

Does anyone know

- when ''C:\Program Files (x86)\SAP\SAP Business One DI API\Conf\b1-local-machine.xml' is used (instead of 'C:\Program Files (x86)\SAP\SAP Business One\Conf\b1-local-machine.xml' ? Is connecting via UIAPI connection string doesn't use any of these files?

- when is the entry for LicenseServer used? When is the entry for SLDServer used? Is LicenseServer still in use? Most AddOns are starting without license server service running. But some not. Is there a priority of both entries? s there a timeout if one of the entries does not respond?

- Why sometimes a FQDN in LicenseServer-Entry is not working but a fixed IP-address does? The name-resolution should not be a problem. It is fast.

- Why is the default "localhost" for LicenseServer initially stored b1-local-machine.xml? And most time not working?

- Is there any timeout so that on slow links (like WLAN) or slow computers the connection error is more often then on newer hardware?

-Why DIAPI getCompany is so slow (5-7 Seconds)? What is SAP doing there? It could not be the SQL-Server performance nor the CPU performance. There mostly idle. So maybe it's looking for some unknown Internet-Server or trying to update some certificates?

It would very nice, if someone explains on which kind of connection request what steps are taken to find the license server.

I hate "try this", "try that" and nobody explains why. On the next computer or next customer I will have the problem again.

Or is this "TOP SECRET" from SAP? Might someone leak something here?

Best regards

Jan