|
From: Peter Dow <petercdow@xxxxxxxxx>4-3A10010_web_services_RT0200S_myemail-40example.com_13245&d=DwICAg&c=jf_iaSHvJObTbx-
To: web400@xxxxxxxxxxxxxxxxxx
Date: 01/14/2019 07:17 PM
Subject: Re: [WEB400] Using REST service created with IWS
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>
You're right. I've been trying things and composing emails and I got my
example wrong.
When the IWS configuration specified
Base resource URL: INVALID URI REMOVED
u=http-3A__1.2.3.
4-3A10010_web_services_RT0200S&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=MdWYExdU-NVGLUI6eHT2ltp8b-YuAkmi74Yn1b_-ORA&e=
Procedure name: GETCASESTATUS
HTTP request method: GET
URI path template for method: /{email}/{casenbr^[0-9]+$}
Input parameter mappings:
Parameter name Data type Input source Identifier
Default Value
PEMAIL char *PATH_PARAM email *NONE
PCASENBR packed *PATH_PARAM casenbr ^[0-9]+$ *NONE
I was trying what you said:
INVALID URI REMOVED.
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-4-3A10010_web_services_RT0200S_email_myemail-40example.com_casenbr_13245&d=DwICAg&c=jf_iaSHvJObTbx-
wRut5byHHrtKJ_1kLM8M8&s=QuV9HHJuttZkM4ZhXOjX_azQhya_6Vzf4-w88urStc4&e=
but when the IWS configuration specified
Base resource URL: INVALID URI REMOVED
u=http-3A__1.2.3.
4-3A10010_web_services_RT0200S&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=MdWYExdU-NVGLUI6eHT2ltp8b-YuAkmi74Yn1b_-ORA&e=
Procedure name: GETCASESTATUS
HTTP request method: GET
URI path template for method: /email/{email}/casenbr/
{casenbr^[0-9]+$}
Input parameter mappings:
Parameter name Data type Input source Identifier
Default Value
PEMAIL char *PATH_PARAM email *NONE
PCASENBR packed *PATH_PARAM casenbr ^[0-9]+$ *NONE
I was trying what I had in that previous email:
INVALID URI REMOVED.
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-4-3A10010_web_services_RT0200S_myemail-40example.com_13245&d=DwICAg&c=jf_iaSHvJObTbx-
wRut5byHHrtKJ_1kLM8M8&s=zMlnHyvbyqWIuV-zkMNcemdmvNh2ZzcYTB2PM373-PQ&e=
as suggested by Tim Fathers. The former appears to be positional
while the latter shows the parameter name in the URL.
I'd be happy to get either one working to the point it calls the
procedure in my service program, but no luck in either case -- both
get HTTP 404 - not found.
Having said all that, I think I see the problem -- PEMAIL is char.
I think if I make that varchar I'll get somewhere. I'll try that
tomorrow and let everyone know one way or the other.
On 1/14/2019 4:55 PM, Jon Paris wrote:
It should just be INVALID URI REMOVEDu=http-3A__1.2.3.
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-4-3A10010_web_services_RT0200S_myemail-40example.com_13245&d=DwICAg&c=jf_iaSHvJObTbx-
wRut5byHHrtKJ_1kLM8M8&s=QuV9HHJuttZkM4ZhXOjX_azQhya_6Vzf4-w88urStc4&e= <
INVALID URI REMOVED.
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-*NONE
wRut5byHHrtKJ_1kLM8M8&s=QuV9HHJuttZkM4ZhXOjX_azQhya_6Vzf4-w88urStc4&e=
I would have thought.including the name of the parms.
Looks to me like you're trying to use a query string type format
use, but to figure out what the IWS configuration translates to in
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Jan 14, 2019, at 7:38 PM, Peter Dow <petercdow@xxxxxxxxx> wrote:
Hi Brad,
Speaking for myself, the problem is not deciding which format to
practice. It seems to do a lot for you, but so far I haven't been
able to go from what I specify in IWS:
u=http-3A__1.2.3.
Base resource URL: INVALID URI REMOVED
4-3A10010_web_services_RT0200S&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=MdWYExdU-NVGLUI6eHT2ltp8b-YuAkmi74Yn1b_-ORA&e=
Default Value
Procedure name: GETCASESTATUS
HTTP request method: GET
URI path template for method: /{email}/{casenbr^[0-9]+$}
HTTP response code output parameter: *NONE
HTTP header array output parameter: *NONE
Allowed input media types: *ALL
Returned output media types: *XML
Input parameter mappings:
Parameter name Data type Input source Identifier
PEMAIL char *PATH_PARAM email
4-3A10010_web_services_RT0200S_email_myemail-40example.com_casenbr_13245&d=DwICAg&c=jf_iaSHvJObTbx-^[0-9]+$ *NONEPCASENBR packed *PATH_PARAM casenbr
understanding was that with the above configuration, I should use
to what URL I have to use to invoke that procedure/method. My
INVALID URI REMOVED.
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-here
wRut5byHHrtKJ_1kLM8M8&s=zMlnHyvbyqWIuV-zkMNcemdmvNh2ZzcYTB2PM373-PQ&e=
will be the time to look at examples.
but I consistently get HTTP 404 - not found.
If I can get past that hurdle, then deciding what flavor to use
--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /
On 1/14/2019 3:52 PM, B Stone wrote:
Booth,
It would do yourself a favor and others new to RESTful requests and
services to search the net for that sort of answer. There are a few
that youfamiliar with it, but there is so much free information out there
RESTfulshould familiarize yourself with first.
Another nice way to look at a LOT of examples is look at Google's
u=https-3A__developers.google.com_calendar_v3_reference_&d=DwICAg&c=jf_iaSHvJObTbx-APIs for all their services. Calendar is one:
INVALID URI REMOVED
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-payload
wRut5byHHrtKJ_1kLM8M8&s=FRUVDzSioOURbW-ftLSMdbwG8uLyMwauT_jTujeooqc&e=
You'll see a lot of options for URI paths, query string options,
docs.options, etc. Especially when you really dig down into some of the
MAILTOOLu=https-3A__www.bvstools.com_mailtool.html&d=DwICAg&c=jf_iaSHvJObTbx-
Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #8 <INVALID URI REMOVED
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=nlpo3Ju9gitYBrUD2LCJbP6tIQPFdP4HHhM7ThkYMkY&e=
: Email Logging
- Each email that is sent out is logged with a delivery status.
wrote:also tracks each of the recipients for each email as well as the
attachment(s) sent along with each email.
On Mon, Jan 14, 2019 at 5:39 PM Booth Martin <booth@xxxxxxxxxxxx>
looks to
Agreed on all of that but in reading Tim Fathers' response, it
That theu=http-3A__1.2.3.me like we should be using queryparm instead of a pathparm?
Like this: INVALID URI REMOVED
4-3A10010_web_services_ftoc-3F90&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=ON7gwQfLefgJaZ19YkTX7rd2xxWgCtDybJvXCyoxub8&e=
- or something
- ???
This has been a long trip for me, and fun every bit of the way.
Nowdiscussion is about style & form tells me thatI finally got there.
morethat I see what IWS is doing I am astonished that there isn't a lot
IWSdiscussion about this awesome product.
On 1/14/2019 5:16 PM, Peter Dow wrote:
Hi Booth,
If you already created the temperature conversion example using
Services"and have it running, then you can use the "Manage Deployed
temperatureurl?u=http-3A__1.2.3.link, select the correct resource from the list and click the
Properties button.
On the General tab that's displayed you'll see
Base resource URL: https://urldefense.proofpoint.com/v2/
4-3A10010_web_services_ftoc&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=1i-
jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=zx6z2YOOcDAmufcwwxQKqE733-B5uQF3XqmSnnVW-Pg&e=
Copy and paste that to a browser's address bar and add the
thread4-3A10010_web_services_ftoc_90&d=DwICAg&c=jf_iaSHvJObTbx-convert, e.g.
INVALID URI REMOVED.
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=pogRhUIFkqXMZDJfCpJMIWUHWFnMDseaSi67zQJmaHQ&e=
The response I get (shown in the browser) is
<CONVERTTEMPResult>
<TEMPOUT>32.22</TEMPOUT>
</CONVERTTEMPResult>
Btw, thanks for all your posts about this subject. Reading that
includedwas a great help in my project.
On 1/14/2019 2:31 PM, Booth Martin wrote:
Walk me through this. The temperature conversion example
Fahrenheiturldefense.proofpoint.com/v2/url?with IWS... The address is https://
u=http-3A__an.iSeries.com_coop_&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=H1crVplQEGDMHi_8U6i2vCLwR-UNRdm2gwt9jUGGOnI&e=
I want to say
F2C and 90, meaning I want the api to convert 90 degrees
theto Celsius. What should that look like?
On 1/14/2019 4:16 PM, Tim Fathers wrote:
While I agree the definition of REST can be pretty flexible and
there are no hard and fast rules, I think it is a fairly well
established rule of thumb that the URL should generally identify
meanresource, not the query parameters. The body (which I think you
notby "standard input") is where the payload should go, and should
whichbe used on on a GET request in any case.
In some APIs the resource is not a "thing" but a function, in
URLcase it is considered ok to pass query parameters to it in the
distancefor a GET or in the body for a POST. The example of this from my
favourite REST book "The RESTful Webservices Cookbook" is a
mailing--calculator. So /calc_distance?from=wiesbaden&to=frankfurt is ok
because "distance" is not a thing but a function.
Tim.
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
u=https-3A__lists.midrange.com_mailman_listinfo_web400&d=DwICAg&c=jf_iaSHvJObTbx-list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: INVALID URI REMOVED
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-u=https-3A__lists.midrange.com_mailman_listinfo_web400&d=DwICAg&c=jf_iaSHvJObTbx-
wRut5byHHrtKJ_1kLM8M8&s=qDR8Av0O3675G4TsUURHszyOMtWZC3MLpUOHKctff1A&e=
u=https-3A__archive.midrange.com_web400&d=DwICAg&c=jf_iaSHvJObTbx-or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at INVALID URI REMOVED
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=awqq7LpeB5rGoCGRuS36o7UPaNVvXv8IXSXsaI3N4Kw&e=.
mailing list--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: INVALID URI REMOVED
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-list
wRut5byHHrtKJ_1kLM8M8&s=qDR8Av0O3675G4TsUURHszyOMtWZC3MLpUOHKctff1A&e=
u=https-3A__archive.midrange.com_web400&d=DwICAg&c=jf_iaSHvJObTbx-or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at INVALID URI REMOVED
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=awqq7LpeB5rGoCGRuS36o7UPaNVvXv8IXSXsaI3N4Kw&e=.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
To post a message email: WEB400@xxxxxxxxxxxxxxxxxxu=https-3A__lists.midrange.com_mailman_listinfo_web400&d=DwICAg&c=jf_iaSHvJObTbx-
To subscribe, unsubscribe, or change list options,
visit: INVALID URI REMOVED
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=qDR8Av0O3675G4TsUURHszyOMtWZC3MLpUOHKctff1A&e=
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at INVALID URI REMOVED
u=https-3A__archive.midrange.com_web400&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=1txuwD0QlHyDFJvVJyRTy-
wRut5byHHrtKJ_1kLM8M8&s=awqq7LpeB5rGoCGRuS36o7UPaNVvXv8IXSXsaI3N4Kw&e=.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
