× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You're welcome...it looks correct to me but as I said, I'm not familiar with the IWS so I can't really help you much on that unfortunately.

Tim.


________________________________
From: WEB400 <web400-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Peter Dow <petercdow@xxxxxxxxx>
Sent: 14 January 2019 20:36
To: web400@xxxxxxxxxxxxxxxxxx
Subject: Re: [WEB400] Using REST service created with IWS

Thanks Nadir and Tim! I was confused about how to specify parameters.
I've only ever used the query parameters; I didn't realize you could
pass parameters as path data.

Now things are making a bit more sense. In the IWS "Deploy New Service"
configuration, when it gets to "Specify resource method information" for
unwrapped parameters, has a drop-down list to select a parameter's
"Input Source"; the list contains

*QUERY_PARAM
*PATH_PARAM
*FORM_PARAM
*COOKIE_PARAM
*HEADER_PARAM
*MATRIX_PARAM
*NONE

What you guys just pointed out is the difference between *QUERY_PARAM
and *PATH_PARAM. If I've got this right, this tells the web service
server where to get the parameter value from so it can pass it in as a
parameter to my service program procedure, so I don't have to do that
work. Is that correct?

So I started over with IWS. Now I have

Base resource URL: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2F1.2.3.4%3A10010%2Fweb%2Fservices%2FRT0200S&amp;data=02%7C01%7C%7C90b4612cc3f541298dbc08d67a578bac%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636830913749425348&amp;sdata=uhENWw6tXyfX%2Fn%2BQnLq4WRTI06LJkp2QZTFxbu6sZcY%3D&amp;reserved=0

Procedure name: GETCASESTATUS
HTTP request method: GET
URI path template for method: /email/{email}/casenbr/{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 Default
Value
PEMAIL char *PATH_PARAM email *NONE
PCASENBR packed *PATH_PARAM casenbr ^[0-9]+$ *NONE

Which as I understand it, means my URL for this should be

https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2F1.2.3.4%3A10010%2Fweb%2Fservices%2FRT0200S%2Femail%2Ftest%40example.com%2Fcasenbr%2F12345&amp;data=02%7C01%7C%7C90b4612cc3f541298dbc08d67a578bac%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636830913749425348&amp;sdata=uz40vDuiMopYLKIfKs%2BHCC97KncZ9stPLV6qmUjKQIs%3D&amp;reserved=0

Is that correct? I'm guessing not, because it returns "HTTP 404 - Not
found".

It would be helpful if IWS showed what it expects the composite URL for
a given method to look like.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.midrange.com%2Fmailman%2Flistinfo%2Fweb400&amp;data=02%7C01%7C%7C90b4612cc3f541298dbc08d67a578bac%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636830913749425348&amp;sdata=Cyv6WlLW1JD9tiY%2FTSgHj4whbTMTFQeHTpyJO3yZXEs%3D&amp;reserved=0
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.midrange.com%2Fweb400&amp;data=02%7C01%7C%7C90b4612cc3f541298dbc08d67a578bac%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636830913749425348&amp;sdata=4MaDYWk4fyYTKDEPbDAfNH%2B1hNM0lK12lMyBQq93eH4%3D&amp;reserved=0.


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-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.