The new $system.external interface (aka "InterSystems External Servers") is used to call/integrate with external language code/libraries, it replace the old gateways (for example Java gateway) that required the import of proxy objects.
For the old Java and .NET gateways Caché included two test/sample classes:
%Net.Remote.DotNet.Test
%Net.Remote.Java.Test
This classes are still included in IRIS as of 2023.1.1, but the documentation of the old gateways has been removed.
The idea is implementing THE SAME FUNCTIONALITY using the same .NET and Java external code/classes but using the new $system.external interface.
This would be an extremely useful source of information on how use/implement $system.external.
Unfortunately with the current available documentation it is not possible to implement that, so this would be possible only for someone within InterSystems using privileged access to information not available to us customers.
Thank you for submitting the idea.
This idea was implemented by InterSystems.
Enrico, thank you for your idea!
This idea was created based on the following discussion in the Developer Community:
https://community.intersystems.com/post/new-systemexternal-interface
This idea was implemented by InterSystems employees, samples are available here:
https://openexchange.intersystems.com/package/samples-dynamicgateway-dotnet
https://github.com/intersystems-community/samples-dynamicgateway-java
Dan Pasco and Summer Myerson thank you for the implementation of this idea!