Re: Consuming a web service using SQL

I just tried it and it worked for me Jack.

I suspect you are missing the cert(s). Remember that discussion back on Ryver a week or two back where I discovered bugs in Jessie's code and in multiple Db2 components?

The new SQL HTTP routines do not use the same cert store that the old Java routines used - so you either need to run the SQL script IBM supply to copy them all or use Jessie's utility to import to the system store just the certs you need. The alternative is to modify the SQL to tell it not to bother with trusting the certs - I _think_ the option is something like "sslDomainName":"required.domain.name" but since I never used that approach I'm not sure how to specify it.


Jon P.

On Aug 27, 2022, at 10:50 AM, Jack Woehr via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Hi Birgitta --

Was just playing with this :)

On Sat, Aug 27, 2022 at 2:26 AM Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:

Here again the example for accessing the Exchange Rate Web-service of the
European Central Bank

'http://www.ecb.int/vocabulary/2002-08-01/eurofxref',

This page doesn't exist

'http://www.gesmes.org/xml/2002-08-01' AS

The http page doesn't seem to exist, and iACS doesn't seem to like the
LetsEncrypt certificate when https is tried.

--

*JACK WOEHR, IBM Champion 2021-2022
<https://www.credly.com/users/jack-woehr/badges>*

*SENIOR IBM i ENGINEER*

303.847.8442
jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx
stay connected
<https://www.linkedin.com/company/absolute-performance-inc./>

<https://www.absolute-performance.com/>
www.absolute-performance.com

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain

confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further

distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and

delete/destroy all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com