I am saying your definition is flawed. There is not a URL that would be
successful the way it is defined. You are specifying:

/{email}{casenbr ^[0-9]+$}

How is IWS server suppose to know when email is suppose to end and case
number is suppose to start?

It is hard for me to determine what URL you are specifying since the
mailing list obfuscates it but if you want the input parameters to be in
the path, then you either need to define the path template by specifying
some sort of delimiter between email and case number, something like:


/{email},{casenbr ^[0-9]+$}


The the URL will need to be something like:

/amra@xxxxxxxxxxx,casenbr-3D1234567



But from the URL you may be specifying, if you want the data to be passed
in as query string data, then you need to define the input source to be
query string data, not path data.



"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 01/14/2019 10:22:36
AM:

From: Peter Dow <petercdow@xxxxxxxxx>
To: web400@xxxxxxxxxxxxxxxxxx
Date: 01/14/2019 10:23 AM
Subject: Re: [WEB400] Using REST service created with IWS
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

I'm not sure what you mean. If the URL is

INVALID URI REMOVED.

4-3A10010_web_services_lab-5Frepair-3Femail-3Daddress-2540example.com-26casenbr-3D1234567&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-

ew&m=uUKcYqXU1ITPviCvJVpFYNwhM2SCFUyAenH5iBUKLig&s=_mIP4VjTHdQ8vxbL5_udQ5_RIJhZ18hy7zq545h2Dvg&e=

the parameter name is right there in the URL.

If that's incorrect, what should the URL look like?



On 1/14/2019 7:11 AM, Nadir Amra wrote:
Hi Peter, yes, I know how the gui figures out the parameters, but
there is
no way to determine the email and the casenbr for any URL specified
the
way you currently define the parameters.

"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 01/11/2019
04:33:00
PM:

From: Peter Dow <petercdow@xxxxxxxxx>
To: web400@xxxxxxxxxxxxxxxxxx
Date: 01/11/2019 04:33 PM
Subject: Re: [WEB400] Using REST service created with IWS
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

Hi Nadir,

Thanks for responding -- this was my first time using IWS and I was
following your article (at least I'm guessing you're the same Nadir
Amra) at
https://www.ibm.com/developerworks/ibmi/library/i-rest-web-services-
server2/index.html.
And I remember wishing you'd had an example with more than one
parameter
:)
I'm guessing it figures it out by the braces - {} as it does not seem
to
have a problem figuring it out. When it shows the parameters for the
method, it separates them in the drop down for the "Identifier"
column
of the Input Parameter Mappings:

Input parameter mappings:
Parameter name Data type Input source Identifier Default
Value
PEMAIL char *PATH_PARAM email *NONE
PCASENBR zoned *PATH_PARAM casenbr ^[0-9]+$ *NONE

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 1/11/2019 11:29 AM, Nadir Amra wrote:
The one thing I am confused about is how the app server is to
determine
when email starts and casenbr begins.

You may need to put some sort of delimiter between the variables.
Like

/{email}-{casenbr ^[0-9]+$}


"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 01/11/2019
01:06:15
PM:

From: Peter Dow <petercdow@xxxxxxxxx>
To: web400@xxxxxxxxxxxxxxxxxx
Date: 01/11/2019 01:08 PM
Subject: [WEB400] Using REST service created with IWS
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

On a v7r3 Power8 box, I used IBM Web Administration for i to create
an
Application server called LAB_REPAIR (v2.6 web services).

It's based on a service program, RT0200S that has 2 procedures,
ADDCASE
and GETCASESTATUS. Right now I'm focused on the latter,
GETCASESTATUS.
It has 2 parameters, email and casenbr. Email is defined as
fixed-length 100a and casenbr is zoned decimal 7.0.

The base resource URL (using ip address for the time being; this is
on a
private LAN only) is

INVALID URI REMOVED.
4-3A10010_web_services_lab-5Frepair&d=DwIGaQ&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-



ew&m=CCNDKmimbua65OnLAg5ajuhqmW1RUNgUU60YIV1cBPE&s=zDfiqyOfNRaGH9IFEeyWioXMwEUqOaDmlMC0Y9of--0&e=
The GETCASESTATUS procedure is associated with the http GET
request:

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 Default
Value
PEMAIL char *PATH_PARAM email *NONE
PCASENBR zoned *PATH_PARAM casenbr ^[0-9]+$
*NONE

The service is created and running, and the question is, what URI
do
I
use to test it?

When I trythe following uri in a browser

INVALID URI REMOVED.



4-3A10010_web_services_lab-5Frepair-3Femail-3Daddress-2540example.com-26casenbr-3D1234567&d=DwIGaQ&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-



ew&m=CCNDKmimbua65OnLAg5ajuhqmW1RUNgUU60YIV1cBPE&s=uK47m9ezZuWUJIH8HkSEyHCGy65_KsLeV_fZGjfUqoo&e=
I get an HTTP 404 response (not found).

I tried using SOAPui and got the same thing.

I'm new at this REST stuff and really new at SOAPUI, but this
really
shouldn't be that hard. What am I missing?

--
--
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: INVALID URI REMOVED



u=https-3A__lists.midrange.com_mailman_listinfo_web400&d=DwIGaQ&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-



ew&m=rcKknnRRUBU8yw9hGaKc042ET2Jq0nTKecodpA1K3Oo&s=o9TNBicq_j5Tf84US2rMycT3iB2BtPXmH-49lTZQBFk&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=DwIGaQ&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-



ew&m=rcKknnRRUBU8yw9hGaKc042ET2Jq0nTKecodpA1K3Oo&s=7bdJ2s1T2LPpqlDUzYtB6MCZShD415W9HB77bnRriZE&e=
.




--
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: INVALID URI REMOVED

u=https-3A__lists.midrange.com_mailman_listinfo_web400&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-
ew&m=uUKcYqXU1ITPviCvJVpFYNwhM2SCFUyAenH5iBUKLig&s=gIn1lT6-
bhmXn6DoEeg1Y7oLJZdB3JE2syU69LT1_0Q&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=uUKcYqXU1ITPviCvJVpFYNwhM2SCFUyAenH5iBUKLig&s=rpRoTyR1-
BO_taouQ6fHThd8_L-jgtdA1o9jcwVcP5s&e=.





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