Perhaps you can provide more details as to what you are trying to do exactly and the way the error manifests itself.
For example you say "in cloud" do you mean via the FHIR Server cloud SaaS service?
If so you have to enable External Connections and setup External Rules. See from the Docs here.
Then under the overview page you should be able to see xDBC Details for connecting. See also here.
There is an article by @Iryna Mykhailova about connecting via xDBC to the IRIS Cloud SQL service, which should be very similar/identical.
Per the above a connection refused error might have to do with the TLS setup required for this connection (which the article above does not cover currently, but the service xDBC details in the Overview page does provide detailed instructions for).
Hi Yehuda,
To answer your first question you would probably either use TLS or Kerberos between the Web Gateway and IRIS.
But more to the point, from your second question what you seem to be desiring to accomplish is not securing/encrypting the communication between the Web Server (Web Gateway) and IRIS, but rather between the client (the browser for example) and the Web Server. For this you would define your Web Server (either IIS, apache or nginx for example) to accept TLS-based (HTTPS) connections/traffic.
This configuration is done on the Web Server side, not on the InterSystems IRIS, or InterSystems Web Gateway side. And you can consult the relevant Web Server documentation to do that.
You will also need relevant certificate/s.
For your convenience here are some sample relevant 3rd party documentation references -
- IIS: https://learn.microsoft.com/en-us/iis/manage/configuring-security/how-to...
- Apache: https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html
- Nginx: https://nginx.org/en/docs/http/configuring_https_servers.html
If you use containers, Kubernetes and our Operator (IKO) all of this can be auto-configured by some simple definitions (see for example here).
(Note if you still want to also secure/encrypt the Web Gateway to IRIS communication you can of course do that as well, per the Docs you already looked at)
Thank you, so this is clearer, and it is happening much earlier than I was thinking. You are not trying to connect via xDBC to your FHIR SQL Builder projected tables, but rather just trying to create the first Analysis step.
This error "shouldn't happen", and I recommend you turn to our Cloud Support.
What you could attempt doing before, is opening the browser debugger and see (perhaps under Network and the related HTTP requests you see) if you see some "interesting" error that could shed some light on what is happening.