×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I got it to work now. I turned on the HTTPAPI debug and saw that the
http 500 error that I was receiving was cause by in-correct data being
passed to the web-service.
That HTTPAPI is some cool tool. Thanks Scott.
"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote in message
news:<mailman.10875.1244221850.23468.rpg400-l@xxxxxxxxxxxx>...
This is the first time that I try to access a web-service using Scott
Klement's http_url_post_xml procedure:
Below is what my RPG code looks like:
myRC = http_url_post_xml(
myWebServiceURL
:%addr(mySoap) + 2
:%len(mySoap)
:*null
:%paddr(remUpdateRemedyWithUPSTrackingNumberResponse)
:%addr(myRemResponse)
:HTTP_TIMEOUT
:HTTP_USERAGENT
:'text/xml'
:myWebServiceSoapAction);
In debug, below are values for myWebServiceURL and
myWebServiceSoapAction:
myWebServiceURL =
http://devrem1/arsys/services/ARService?server=devrem1&webService=DalyUp
date
myWebServiceSoapAction = DalyUpdate/OpSet.
http_url_post_xml returns value of 500 upon completion of above
statement.
The URL for the WSDL document is at
http://devrem1/arsys/WSDL/public/devrem1/DalyUpdate
The service tag in the WSDL looks like below:
<service name="DalyUpdateService">
<port binding="s:DalyUpdateSoapBinding" name="DalyUpdateSoap">
<soap:address
location="
http://devrem1/arsys/services/ARService?server=devrem1&webServ
ice=DalyUpdate" />
</port>
</service>
When I ask the web-service provider about http 500 error, she said that
I should post the request to the URL where the WDSL document is located
(
http://devrem1/arsys/WSDL/public/devrem1/DalyUpdate). Is that right?
I thought I'm supposed to post to the URL indicated in the port tag of
the service tag.
Thanks
----------
midrange.com
