Re: IWS Migration from 1.5 to 2.6 SOAP - Save-Restore OK ... Redeploy KO

I just wrote that just only restoring the web service from 1.5 to 2.6 of
IWS seems working ... but I just got a message from the customer:

...
I have only one problem in a specific service's method:
"High order nibble of the byte array offset 820 is not valid. Byte value:
00"
...

I spoke too soon!





Il giorno dom 11 apr 2021 alle ore 21:57 Roberto De Pedrini <
roberto.faq400@xxxxxxxxx> ha scritto:

@Nadir, I'm restoring the web service on a 2.6 IWS (IBM i OS 7.4 with last
PTF for HTTP and Websphere APP Server)
SF99661SF99661 740 WebSphere App Server V8.5 5 INSTALLED
LEVEL IS CURRENT INSTALLED 5
02/12/2021
SF99662SF99662 740 IBM HTTP Server for i 9
INSTALLED LEVEL IS CURRENT INSTALLED 9
01/07/2021

But I've got always the same problem ... if I compare WSDL just after
restoring Webservice and after redeploying it without any change I can see
those differences

WSDL Just after Restore
WSDL After redeploying
--
*xmlns:ns1="http://wspub02.wsbeans.iseries/xsd
<http://wspub02.wsbeans.iseries/xsd>" *
none!
...
xmlns:tns="http://wspub02.wsbeans.iseries/*xsd*";
xmlns:tns="http://wspub02.wsbeans.iseries";
..
targetNamespace="http://wspub02.wsbeans.iseries/*xsd*";
targetNamespace="http://wspub02.wsbeans.iseries";
...
<xs:element...
<xs:element..
name="arg*s*0"
name="arg0"

I tried to upload the WSDL "original" after redeploying web service ...
but it doesn't work anymore

My customer doesn't want to change anything in the client application, I
don't know if he can change only the the WSDL because is an old web app
that consumes the web service. Just restoring the web service on a new 2.6
server seems to work: shame we can't redeploy it!





Il giorno gio 8 apr 2021 alle ore 16:57 Nadir Amra <amra@xxxxxxxxxx> ha
scritto:

Forgot to mention that if you load or have latest HTTP group, you may
need
to restore the web service again with latest PTFs and try redeploy to see
the results, assuming you did the restores without latest HTTP group or
latest IWS PTFs.


"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 04/08/2021
09:49:04 AM:

From: "Nadir Amra" <amra@xxxxxxxxxx>
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxxxxxxxx>

Date: 04/08/2021 09:49 AM
Subject: [EXTERNAL] Re: IWS Migration from 1.5 to 2.6 SOAP - Save-
Restore OK ... Redeploy KO
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>

Hi,

Ensure you have latest HTTP group PTF.

If you do have latest HTTP group, on redeploy you may need to set the

WSDL

namespace to append "/xsd" if it does not have it.

However, given that you have not changed anything, not sure why you are
concerned. And if you do change something and then redeploy, then the

new

WSDL would need to be sent to clients and assuming clients use the new
WSDL then there should not be a problem.

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on

04/07/2021

11:45:33 PM:

From: Roberto De Pedrini <roberto.faq400@xxxxxxxxx>
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxxxxxxxx>

Date: 04/07/2021 11:45 PM
Subject: [EXTERNAL] IWS Migration from 1.5 to 2.6 SOAP - Save-
Restore OK ... Redeploy KO
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>

Hi all from Italy,
I'm trying to help one of my customer to migrate some SOAP web

services

from an IWS 1.5 (on a 7.2 partition) to an IWS 2.6 (on a 7.3

partition).

Following those IBM documents (
https://www.ibm.com/support/pages/how-migrate-your-ibm-integrated-
web-services-iws-server-v13v15-v26
and https://www.ibm.com/support/pages/node/1138636) it seems all

OK:

1 Save WS from IWS 1.5 with saveWebServices.sh
2 Restore WS to IWS 2.6 with restoreWebServices.sh
3 Add rewrite rules on HTTP.CONF and restart the server
4 Test the old client (SOAPui for me) changing only endpoints
5 It works! All ok, no other modification to my old client

But if I stop my web service on IWS 2.6 (7.3), and try only to

redeploying

it without any changes, something change in the WSDL and I got

"Unexpected

wrapper element .../xsd" message from SOAPui "call"


soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
<soap:Body>
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>Unexpected wrapper element {
INVALID URI REMOVED

u=http-3A__wspub02.wsbeans.iseries_xsd-257Ddipendenti-5Flist&d=DwICAg&c=jf_iaSHvJObTbx-

siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-
ew&m=tryHH52YeE5o2jdSKl2WSvf22J3lYlTPdrNE-
CzSv0I&s=gTmm4HnxVRde_mmAm7OiusijianG1gN11bLYNzZ-UZc&e= found.

Expected

{

INVALID URI REMOVED

u=http-3A__wspub02.wsbeans.iseries-257Ddipendenti-5Flist&d=DwICAg&c=jf_iaSHvJObTbx-

siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-
ew&m=tryHH52YeE5o2jdSKl2WSvf22J3lYlTPdrNE-CzSv0I&s=a4gWXvWqresiQ-
C0CJpvxe8xmK8jNUNo4aqczbzF5qc&e= .</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>

wspub02 is my WebService
dipendenti_list is one of the methods (procedures)

Why I can migrate but not redeploying services? Or

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

--
--
Roberto De Pedrini - Faq400 Srl
http://blog.faq400.com/en *A new IBM i Blog from IBM i Italian
Community Faq400*