Re: Fw: Namespace on IWS v2.6

["Nadir Amra" <amra@xxxxxxxxxx>]

Hi Eric,

The endpoint will be in the WSDL, but it will not allow you to access WSDL 
using it.  This is for users that want to direct clients to some proxy. 
The proxy would have to map it correctly.

The other thing you mention seems to be a bug.  Can you open a PMR against 
Web Admin GUI?  You can revert it back by changing the context root in 
Server->Properties, the Web services tab.





From:   Eric <send2et@xxxxxxxxx>
To:     "Web Enabling the IBM i (AS/400 and iSeries)" 
<web400@xxxxxxxxxxxx>
Date:   05/25/2017 04:31 AM
Subject:        Re: [WEB400] Fw: Namespace on IWS v2.6
Sent by:        "WEB400" <web400-bounces@xxxxxxxxxxxx>



Also I noticed that if depending on what the Java Home configured against
IWS server, the endpoint is different.

JDK 7.0 32 bit
http://111.111.111.111:10092/web/services/ConvertTempService/
ConvertTemp?wsdl

JDK 8.0 64 bit
http://111.111.111.111:10093/web/ConvertTempService/ConvertTemp?wsdl



On 25 May 2017 at 10:05, Eric <send2et@xxxxxxxxx> wrote:

> Hi Nadir,
>
> I did restart the server after editing and changing the static / dynamic
> endpoint.
>
> Strange, because after I've changed it to use static URL and restart the
> server.
> I would expect the WSDL can be retrieved based on the URL I've typed as
> you described, it didn't.
>
> Eric
>
> On 24 May 2017 at 15:48, Nadir Amra <amra@xxxxxxxxxx> wrote:
>
> > Eric,
> >
> > Editing the WSDL would require you to end and restart the server.
> >
> > There is no way to edit the file as it pertains to the namespace.
> >
> > The static/dynamic endpoint allows you to insert a URL that will be 
used
> > in the WSDL. By default, the endpoint host and port is generated
> > dynmically dependent on the host/port the client request used to access
> > the WSDL.  If you enter a static URL, that is the URL that would be 
used.
> > From:   Eric <send2et@xxxxxxxxx>
> > To:     "Web Enabling the IBM i (AS/400 and iSeries)"
> > <web400@xxxxxxxxxxxx>
> > Date:   05/24/2017 04:38 AM
> > Subject:        Re: [WEB400] Fw: Namespace on IWS v2.6
> > Sent by:        "WEB400" <web400-bounces@xxxxxxxxxxxx>
> >
> >
> >
> > Hi Nadir,
> >
> > Thanks for your reply.
> > I did spend a day yesterday fiddling with it and trying all sorts.
> >
> > I got a few questions though.
> >
> > What is the difference between static and dynamic endpoint URL?
> > At first I thought I could manipulate the HTTP URL using that but 
didn't
> > work.
> >
> > Also I noticed that if I edit the .WSDL to instruct it to use the
> > namespace, it also didn't work.
> > After I edit the WSDL, I can see the WSDL has been changed in the IFS 
and
> > the Wizard Edit mode.
> > But when I click the 'View WSDL', I can't see the changes I've made.
> >
> > Eric
> >
> > On 24 May 2017 at 00:54, Nadir Amra <amra@xxxxxxxxxx> wrote:
> >
> > > Hi, There is no way to get around this.  The endpoint you can 
probably
> > get
> > > around by using HTTP URL mappings documented on page 131 of the
> > > administration and programming guide [1].  The namespace cannot be
> > > resolved.  You will have to send your clients the new WSDL.
> > >
> > > [1] https://www.ibm.com/systems/power/software/i/iws
> > >
> > > ----- Original message -----
> > > From: Eric <send2et@xxxxxxxxx>
> > > Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>
> > > To: "Web Enabling the IBM i (AS/400 and iSeries)" 
<web400@xxxxxxxxxxxx>
> > > Cc:
> > > Subject: [WEB400] Namespace on IWS v2.6
> > > Date: Tue, May 23, 2017 4:24 AM
> > >
> > > Hi,
> > >
> > > Our client has upgraded from V7R1 to V7R3 and we noticed a few issues
> > with
> > > the IAS and IWS.
> > > Eg. IAS is no longer supporting v8.1 and no longer supporting Java 6.
> > >
> > > I also noticed that IWS v1.5 no longer exist. It's v2.6 now.
> > >
> > > I've tried recreating the server / service.
> > > After everything is done, I noticed that the XML structure generated 
by
> > > the
> > > WSDL is different.
> > >
> > > The end point is also different because it's using a different 
framework
> > > which is faster.
> > >
> > > Some namespace are no longer there and some has changed.
> > >
> > > We are trying to minimise the impact to the other vendors which have 
to
> > > call the web service.
> > >
> > > Does anyone know whether it would be possible to change the namespace 
so
> > > that we make it the same as what it was before when it was running on
> > > v1.5?
> > > This means only the endpoint which is changed.
> > >
> > > Thanks,
> > > Eric
> > >
> > >
> > >
> > > --
> > > This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) 
mailing
> > > list
> > > To post a message email: WEB400@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/web400
> > > or email: WEB400-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/web400.
> > --
> > This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) 
mailing
> > list
> > To post a message email: WEB400@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/web400
> > or email: WEB400-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/web400.
> >
> >
> >
> >
> >
> > --
> > This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) 
mailing
> > list
> > To post a message email: WEB400@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/web400
> > or email: WEB400-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/web400.