New project: Communicate through a web service to some other outfit to
set up, modify, enable/disable, etc., email and other services. This will
be integrated with our Service Order maintenance application running on our
IBM Power, in ILE-RPG. I've consumed web services before. I can handle
First obstacle: I am told that this is to be done through their "web
service" (quotes intentional), but when I requested access to the WSDL, I
was referred to the care and feeding document. Said document is a PDF
containing descriptions of how to perform various operations through
various snippets of XML. Cool. I asked again where to find the WSDL, and
was told "haven't got one." Oh.
Perhaps I can construct one, and paste in the XML pieces? This web
service (my contact refers to the "app") is not publicly available, which
may explain why they don't have a WSDL. Perhaps this has never been
requested by other clients they've invited to share the app with.
Question: How do I fudge up a WSDL that will include all the necessary
pieces to satisfy WSDL2RPG stub generators?
Second obstacle: I'm still waiting for SysOp to get the updates installed
to allow my access to "Web Administration for i". I suspect there is a
wizard or two there that would help, but I can't get there yet. We are on
7.1 (still waiting for TR7 too).
One of the operations from the care and feeding manual looks like this:
[I do have the URL of where the XML gets sent to, as well as the user and
password referenced in the authenticate tag]
To suspend the user, issue the following command:
So given that I may be rolling my own WSDL by hand, can someone point me
to some useful details? My goal is to have a suitable WSDL to be accessed
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact