[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Calling webservices from ISeries v5r3 Cobol Program
Mike, Scott, any body else,
I've got the message "HTTP/1.1 500 Internal Server Error". Where could
if I find more information about reasons of this returned message ?
Does exist additionnal log in ISeries ? Thank you for your help.
Stif
2007/9/11, kakou kesse <[1]koikesse@xxxxxxxxx>:
Some news,
For my net administrator, problem occurs because of proxy.. I try to
specify in EXAMPLE18 program the calling of
[2]http://proxy:port/www.webservice.net. Unfortunately, our proxy not
able to understand this kind of url...
Finally, i'll try to create my own program for calling an internal
webservice because my first objective is just to validate that this
solution can be used in our ISeries system...
Coming soon for next news.
Stif
2007/9/11, kakou kesse <[3]koikesse@xxxxxxxxx>:
Hi Mike,
I watched DNS parameters return by CHGTCPDMN and only 2 internals DNS
are defined.. I think you're right, an DMZ DNS is missing or perhaps
I've to request an internal DNS modification.. I'll pay a visit to my
colleague..
Stif
2007/9/10, Mike Krebs <[4]mkrebs@xxxxxxxxxxxxxxxxxx>:
You ping from the System i command line (call qcmd)
ping [5]www.webservicex.net
These are the messages that are returned...
Verifying connection to host system [6]WWW.WEBSERVICEX.NET at
address
[7]209.162.186.60 .
PING reply 1 from [8]209.162.186.60 took 103 ms. 256 bytes. TTL
105.
PING reply 2 from [9]209.162.186.60 took 106 ms. 256 bytes. TTL
105.
PING reply 3 from [10]209.162.186.60 took 98 ms. 256 bytes. TTL
105.
PING reply 4 from [11]209.162.186.60 took 106 ms. 256 bytes. TTL
105.
PING reply 5 from [12]209.162.186.60 took 104 ms. 256 bytes. TTL
105.
Round-trip (in milliseconds) min/avg/max = 98/103/106.
Connection verification statistics: 5 of 5 successful (100 %).
>From the QCMD screen, use F10 to see detailed messages. The name
to number
resolution is what we are checking (first line of returned
messages). It is
common that ping may be blocked, but the name resolution needs to
work.
On your system i, you can check the DNS setup by prompting a
CHGTCPDMN
command. In the domain server section, you should have a list of
valid DNS
servers. We list two internal servers and one DMZ server on our
system. If
the servers listed on your system are external, then you need to
check if
port 53 is open (so that your system i can reach those servers). If
you know
how to use NSLOOKUP; you can use it to verify some information
about DNS. It
is on our system I (V5R4).
Mike
-----Original Message-----
From: [13]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[14]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
kakou kesse
Sent: Monday, September 10, 2007 10:54 AM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Calling webservices from ISeries v5r3 Cobol Program
Hello Mike,
Pingging on url or IP doesn't return response (I have to cancel
request). Do
you test it from your home, perhaps this server rejects ping
request ? It's
just to be sure..cause when I'm pingging [15]www.google.com i've
got the same
"no return".
I'll see tomorrow my net administrator for verify... That's stange,
in fact,
for me, all HTTP streams are open in our firewall..
Regards
2007/9/10, Mike Krebs <[16] mkrebs@xxxxxxxxxxxxxxxxxx>:
>
> Sorry, finger check on the ping command.
> PING [17]www.webserviceX.NET
>
>
> -----Original Message-----
> From: [18]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[19]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx ] On Behalf Of
Mike Krebs
> Sent: Monday, September 10, 2007 9:33 AM
> To: 'HTTPAPI and FTPAPI Projects'
> Subject: RE: Calling webservices from ISeries v5r3 Cobol Program
>
> >"host not found" perhaps a firewall problem,
>
> Check to make sure you can resolve DNS.
> PING [20]www.weverviceX.net
>
> Even if the ping can't reach anything, you should see something
like this.
> Verifying connection to host system [21]WWW.WEBSERVICEX.NET at
address
> [22]209.162.186.60.
> The [23]209.162.186.60 is the important part.
>
>
> > what is the port used for webservice communications ?
>
> Port 80 is standard (the traffic is HTTP protocol). I think all
the
> examples use port 80 (there might be some using https so 443 for
> those), but you can use other ports. In addition, Scott has been
> working on proxy support. So, it might be possible to use your
proxy.
>
> Mike Krebs
>
>
-------------------------------------------------------------------
---
> - This is the FTPAPI mailing list. To unsubscribe, please go to:
> [24]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-------------------------------------------------------------------
---
> -
>
>
-------------------------------------------------------------------
---
> - This is the FTPAPI mailing list. To unsubscribe, please go to:
> [25]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-------------------------------------------------------------------
---
> -
>
-------------------------------------------------------------------
----
This is the FTPAPI mailing list. To unsubscribe, please go to:
[26]http://www.scottklement.com/mailman/listinfo/ftpapi
-------------------------------------------------------------------
----
References
1. mailto:koikesse@xxxxxxxxx
2. http://proxy/www.webservice.net
3. mailto:koikesse@xxxxxxxxx
4. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
5. http://www.webservicex.net/
6. http://www.webservicex.net/
7. http://209.162.186.60/
8. http://209.162.186.60/
9. http://209.162.186.60/
10. http://209.162.186.60/
11. http://209.162.186.60/
12. http://209.162.186.60/
13. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
14. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
15. http://www.google.com/
16. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
17. http://www.webservicex.net/
18. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
19. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
20. http://www.wevervicex.net/
21. http://www.webservicex.net/
22. http://209.162.186.60/
23. http://209.162.186.60/
24. http://www.scottklement.com/mailman/listinfo/ftpapi
25. http://www.scottklement.com/mailman/listinfo/ftpapi
26. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------