Initiate web server servlet

Scott,

The client configured TCP setting and got TELNET working, they are going to try the EXAMPLE 1 program tomorrow. Thanks alot for that support (re: Host not found thread)!

Now to the real project - the client's iSeries needs to post the following to an internal web server: http://localhost:9080/ClaimsToDW/ClaimsToDWServlet?msg=<data>filedata</data>

where localhost = the IP address for the internal server. This post will initiate a servlet which will send the file data to a message queue:

I'm guessing, based on Example 5, that this can be done with this RPG function:

http_url_post_raw('http://localhost:9080/ClaimsToDW/ClaimsToDWServlet?': %addr(XXXX): %len(%trimr(XXXX)):1: %paddr('INCOMING'))

where XXXX is a variable that contains the text '<data>filedata</data>. This will return a success/failure return code.

Is this correct or am I way off? :-)

BTW I'm very impressed with the support you and others have given with this utility - I appreciate it!

Thanks

-------------- Original message --------------

> Sender: Scott Klement
>
>
> > The client did not do a telnet yet but last night they were able to ping
> > the 10.250.52.45 web server from the iSeries with these results:
> >
> > Verifying connection to host system 10.250.52.45.
> > PING reply 1 from 10.250.52.45 took 3 ms. 256 bytes. TTL 128.
> > PING reply 2 from 10.250.52.45 took 0 ms. 256 bytes. TTL 128.
> > PING reply 3 from 10.250.52.45 took 1 ms. 256 bytes. TTL 128.
> > PING reply 4 from 10.250.52.45 took 1 ms. 256 bytes. TTL 128.
> > PING reply 5 from 10.250.52.45 took 0 ms. 256 bytes. TTL 128.
> > Round-trip (in milliseconds) min/avg/max = 0/1/3.
> > Connection verification statistics: 5 of 5 successful (100 %).
>
> PING basically tests that the IP protocol is working. It doesn't help
> test the TCP protocol (which runs on top of IP), and it certainly doesn't
> test to see if your web server is listening for requests properly.
>
> In order to test this, you need software that uses TCP to make a request
> to port 80 on the server. TELNET can do that. HTTP does that. PING does
> not.
>
> > Does that help you diagnose the problem or does the client need to
> > telnet with port 80? Is there any user id authentication that the HTTP
> > post has to worry about or any authentication issues on the destination
> > server?
>
> There might be, that depends on how the web server is configured. If
> there is, HTTPAPI's EXAMPLE7 shows how to send the userid & password.
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubsribe from the list send mail
>! ; to maj ordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
> -----------------------------------------------------------------------