Il 08/05/2026 15:06, Niels Liisberg ha scritto:
The simple but also IMHO most convoluted solution is to wrap your code in a
SQL stored procedure and access it by ODBC or Mapepire.

The more modern approach is to think "separation of concerns" and create a
small service on the IBM i that handles the service request.

I notice Daniel Gross already proposed ILEastic/NoxDb—this is the approach
we are implementing and recommend. You have 100% control over the JSON
layout and can add extra parameters, headers, or security settings.

Regarding your concerns about production readiness: The IceBreak project
stared some 25 year ago and runs core business for the biggest banks and
insurance companies in Europe. ILEastic and NoxDb were carved out from the
IceBreak core and made into open-source projects that also run at
Fortune-100 companies. I know more than 300 sites using the open-source
solution.

Btw - Daniel - the TLS support was just pulled in :)

Niels, thank you so much for your reply. I've read about ILEastic and NoxDB online; they're very interesting projects and products. This time, I chose the IWS approach because, in just a few simple steps, I created the call wrapper and the subsequent response I needed. Total time: 2 half days. But now you've piqued my curiosity to study the two projects a little more.
For example, what's the difference between NoxDB and YAJIL or expat?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.