Some changes to the code.kx docs, https://code.kx.com/q/interfaces/solace/, are currently in the works. These specificities are mentioned in the readme/etc on github.
You can see in the White Paper that they use Kdb+ running on an ec2 instance ‘ip-172-31-70-197.ec2.internal’ and it connects to Solace broker running on ‘mr2ko4me0p6h2f.messaging.solace.cloud’
As long as your network settings are setup so that the 2 hosts can communicate over the needed ports then you will be successful.
Great question! Here is the feedback I received when I investigated this internally:
"If broker is installed in a container, and client is on the host , then it should be possible to communicate as long as the chosen port is exposed to a port on the host.
If using solace broker container, they are normally listed in solace PubSubStandard_singleNode.yml.
Note: these are Solace queries rather than KX queries, and may be better directed to Solace for a better explanation, and it can be beneficial to try with the solace client examples first (directing any problems/queries/etc to Solace). The KX interface uses the same solace C APIs."
Thanks for the link. it gave me a hint about using the q script to init connection.
I try to do something totally different. my goal is to create “software” type solace instance
on my local machine (windows 10 x64). I installed docker instance of solace.
how can I find the connection parameters described on the white paper (Messaging), see attached screenshot - the UI when I surf to my docker software solace page.