× 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.



1) An RPG string can be up to 64K (not 32K) unless you are on a really old release.

2) If you are on V6+ it can be up to 16Mb.


On 2013-07-09, at 3:49 PM, tegger@xxxxxxxxxxx wrote:



I can create the 2 fields from a form, but the remaining XML file might be a bit much for most RPG fields at 32k.





----- Original Message -----


From: "Peter Connell" <Peter.Connell@xxxxxxxxxx>
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, July 9, 2013 3:46:38 PM
Subject: RE: http_url_post_xml and REST

Looks like it's not a classic xml service which expects just a body containing an xml document.
In this case it looks like a regular HTTP POST with 3 form variables, one of which is a string containing the entire xml document. The api_key is OK since the connection is https://

Peter


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of tegger@xxxxxxxxxxx
Sent: Wednesday, 10 July 2013 7:38 a.m.
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: http_url_post_xml and REST



The example in their documention is a php derived sample. I'm just having one of those moments where I'm not connecting the dots again:





<?php

$urltopost = "https://[ServerName]/orders/api/add_order";;

$datatopost = array (

"code" => "[YOUR CODE]",

"api_key" => "[YOUR KEY]",

"data" => file_get_contents("import.xml"),

);





I have the XML created and am at the point to send it over, but am not really sure how to connect them. The XML file is a pretty good size (190k) and has the potential to be a lot larger on some occasions.



To me, it all looks like a regular everyday POST, but with file_get_contents made me think I probably should go the same route because of the file sizes.



The documentation keeps going on about REST, but I don't see anything unusual about any of the above...





----- Original Message -----


From: "Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx>
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, July 9, 2013 3:25:33 PM
Subject: Re: http_url_post_xml and REST

Hello,

In what format would you like to do this? a POST request allows one "request body" (basically, a stream of bytes to upload). In that body, you can send a raw file, such as an XML file, or you can use some sort of transfer encoding that allows you to put multiple pieces of data together.

XML itself is sometimes used for that. Other methods include multipart/form-data encoding, or the traditional web format of application/x-www-form-urlencoded (which is unusual with web services, but not unheard of.) JSON is also sometimes used for this.

Do you know more about the format of the request body you need to send?

-SK



On 7/9/2013 2:08 PM, tegger@xxxxxxxxxxx wrote:

I have a project that I need to be able to post a rather large XML
file to a web service.

I've looked around for an example to follow that will post the XML
from the IFS and include some basic information on the actual POST.
(In this particular case, I have to post strings that ID our system to
the remote. Kinda of like a user ID/password).

Has anyone tripped across a good example?
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.


#####################################################################################

This correspondence is for the named person's use only. It may contain confidential
or legally privileged information, or both. No confidentiality or privilege is waived
or lost by any mistransmission. If you receive this correspondence in error, please
immediately delete it from your system and notify the sender. You must not disclose,
copy or rely on any part of this correspondence if you are not the intended recipient.
Any views expressed in this message are those of the individual sender, except where
the sender expressly, and with authority, states them to be the views of Veda.
If you need assistance, please contact Veda on either :-
Australia 1300-762-207 or New Zealand +64 9 367 6200
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.