acadon_client.connector
About
One of the disturbing feature limitation of the BC web client, is the missing client side interaction.
With the acadon_client.connector you are still able to run .NET client side on windows systems in RTC, Web Client and the App.
The acadon_client.connector based on two mandatory components.
- The acadon_client.connector application. Ths application can be installed by click once and support Windows 10 and Windows Server.
- The acadon_client.connector extension, which add the interface to the acadon_client.connector application to BC.
How it Works
The acadon_client.connector application starts to the systray and opens the TCP port 5000 and the port 5001 + current windows session id.
The port 5000 will only be opened if the first instance is started on the windows machine. If multiple instances in different windows sessions are opened, like on terminal server, and the first instances closed the next instance take control of port 5000.
Port 5000 works as broker. The acadon_client.connector extension uses a JS Client AddIn to call the url http://localhost:5000 and gets the correct windows session id port ,based on the process windows session id of the calling application (chrome, IE, opera, RTC, Native App, etc.), as result.
A second call checks with a short keep a live time if a acadon_client.connector application instance is running in the current windows session, if not the BC client ask to install or start the application.
The third and last call transmit a LUA script and all needed parameter to the application with a unlimited keep a live time. After execution of the LUA script, the result will be transmitted to the BC JS Client AddIn.