WSDL for a CDC vendor was provided with a URL using a custom socket (non 443). Everything generated fine, but when making calls to their https:// URL that has their custom port in the URL - no response comes back. The assumption is, their server isn't even processing the request, as Postman does using the custom https://path.to.server:NNNN port in the URL.

Using Cache 2017.2 sever as my target.

I have a x64 Ubuntu client setup going. This is NOT server. Just client.

I have the Linux Ubuntu x64 ODBC driver gzip file.

ODBC-2018.1.5.659.0-lnxubuntux64.tar.gz is all I could find. Someone posted it in another post.

I can connect to a test sever that does NOT use SSL. That works pretty easily.

But I have A server with SSL enabled. With Windows Cache ODBC drivers I can use SSL just fine.

This is what my SSLDefs.ini file on the Windows machines look like and it works just fine.

This article shares analysis in solution cycle for the Open Exchange application TOOT ( Open Exchange application )

The hypothesis

A button on a web page can capture the users voice. IRIS integration could manipulate the recordings to extract semantic meaning that IRIS vector search can then offer for new types of AI solution opportunity.

The first part of this article provides all the background information. It also includes links to the DATATYPE_SAMPLE database, which you can use to follow along with the examples.

In that section, we explored an error type ("Access Failure") that is easy to detect, as it immediately triggers a clear error message when attempting to read the data via the database driver.

Hi Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯ Security - Granular Access Control to Files with Fapolicyd @ Global Summit 2024

https://www.youtube.com/embed/qMJcALKsNVE
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Hi, Community!

Looking to modernize the way you build interoperability screens in InterSystems® products? Take a tour of some recent UI improvements.

Building Integrations: A New User Experience

https://www.youtube.com/embed/zupj1P7Plgo?utm_source=youtube&utm_medium=social&utm_campaign=zupj1P7Plgo
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Real Time FHIR® to OMOP Transformation

Hey Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯ SMART on FHIR: Introduction & FHIR Server Setup

https://www.youtube.com/embed/OHaZ5qiyQ1c
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Developing with InterSystems Objects and SQL – In Person (Boston, MA) March 24-28, 20

Hey Community,

We're excited to invite you to the next InterSystems UKI Tech Talk webinar:

👉SQL Cloud Services

⏱ Date & Time: Thursday, April 24, 2025 14.30-15.30 UK

👨‍🏫 Speaker: @Kinshuk Rakshith, Sales Engineer, InterSystems

HealthShare Patient Index – Virtual February 19-21, 2025 9:00am-5:00pm US-Eastern Time (EST)

I have a general question about HealthShare Provider Directory using Code Tables on disk vs Cache SQL Tables. Why is Provider Directory not using the Cache SQL Tables within the IRIS platform?

Does %OSCertificateStore only check the trusted root folder in windows?

Can it be used for Personal store on servers or is there another condition can be used?

Used it for a first time and writing a function to check specific ones being used for expiry but had one this week that was to be installed in personal rather than the trusted root and didn't know if stating OSCertificateStore or a url otherwise to look in the personal installed certs on the server could be used instead so stuck with the original way (which can get confusing)