Rick
We have VB.net talking to our websphere services in production mode. All
you need for the two to talk to each other is the location of the WSDL.
Once a service is implemented in production we take the URL to the service
and append a ?wsdl at the end. This is sent to the VB team to use for
creating a client.
There is one issue that I am aware of: For a VB.net client to successfully
communicate with a Websphere service the version of VB.net must be 2.0.
Version 1.10 could not talk to the service. We got around that by creating
a 2.0 proxy to the Websphere services.
Regards
Faizulla Khan
Information Services
Grand Circle Travels
617-346-6058
<Rick.Chevalier@a
mericredit.com>
Sent by: To
wdsci-l-bounces@m <wdsci-l@xxxxxxxxxxxx>
idrange.com cc
Subject
02/21/2008 02:51 Re: [WDSCI-L] Accessing locally
PM published web service on test
server
Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>
Thanks Shannon. I got the VB project to see the WSDL file finally. Now
it's complaining about the format of the XML. Either missing or
incorrect SOAP information. I didn't have a chance to follow up on it
and it looks like it will be at least tomorrow before I can get back to
it.
I'm not sure my previous post asked my question clearly. I have been
through several of the tutorials in WDSC and have performed many Google
searches for information on web services. It seems as though there is
something missing though. WDSC shows me how to use the tools but the
details are hidden. The web searches seem to find hits that assume a
higher level of knowledge than I have (beginner) with web services.
What I'm looking for is something to bridge the gap and explain how the
connections are made between the client and server and what is required
on each side. That would help me understand where to look when issues
arise and determine what might have gone wrong. Does a book or web site
exist that would do this?
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Shannon ODonnell
Sent: Friday, February 15, 2008 7:59 PM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] Accessing locally published web service on test
server
Rick,
If you developed your web service in WDSC, then use the explorer in
WDSC and go to the Web Content, directory of your project, drill down
to the WDSL directory and open the wsdl file. Look at the source view.
Scroll all the way to the bottom of the file. Your web service location
will be found there.
If you moved it to a different WAS server than your local test
environment server, then replace "localhost:9080" with whatever the name
of your system/ip address where the other WAS server is, and the port
that you installed the web service EAR file onto.
If this is all still in your WDSC test environment and you have not
published it anywhere else, then you should leave it as localhost:9080
in the WSDL location.
If you are trying to access your test service from VB, while it is
running inside of your test environment...I don't even know if that's
possible. If it was, however, it would still be that localhost:9080
value.
If you want to copy and paste that line from your WSDL in WDSC for this
service, then email it to this list, I can probably give you the exact
location, using your own project/service names.
HTH
Shannon O'Donnell
Privileged and Confidential. This e-mail, and any attachments there to, is
intended only for use by the addressee(s) named herein and may contain
privileged or confidential information. If you have received this e-mail
in error, please notify me immediately by a return e-mail and delete this
e-mail. You are hereby notified that any dissemination, distribution or
copying of this e-mail and/or any attachments thereto, is strictly
prohibited.
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
midrange.com
