[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Receiving file via HTTP
I've been comfortable with the restrictions normal iSeries security
combined with Sectcp from Easy400 gives us. We aren't open to the
internet, all connections come via VPN. Local users have full access by
IP, external users are restricted to only certain libraries and ifs
paths that all have tight object authority.
[1]http://www.easy400.net/sectcp/start.
[cid:827076083b3e4e94b22d6a33e89fc959] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain
confidential information, belonging to the sender that is legally
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any other
party and is required to destroy the information after its stated need
has been fulfilled. If you are not the intended recipient, or the
employee of agent responsible to deliver it to the intended recipient,
you are hereby notified that any disclosure, copying, distribution or
action taken in reliance on the contents of these documents is STRICTLY
PROHIBITED. If you have received this email in error, please notify
the sender immediately to arrange for return or destruction of these
documents.
__________________________________________________________________
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx on behalf of
elbert@xxxxxxxxxxxxxxx
Sent: Wed 8/28/2013 5:04 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Receiving file via HTTP
I'm sure FTP will work but we have never been able to sufficiently
secure our Iseries FTP server to allow incoming external connections.
Please verify you are happy with your level of FTP security if you are
going to allow external connections
Our FTP server for incoming external connections resided on a stand
alone PC and our Iseries accesses the PC files via /QNTC
For us the least complicated, most secure option was a FTP server
running in a PC
Our outgoing ftp transfers run from our Iseries
On Aug 28, 2013, at 4:38 PM, "Kevin Bucknum"
<Kevin@xxxxxxxxxxxxxxxxxxx> wrote:
> Start the ftp server and let him ftp it to you?
>
> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[[2]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Brian
> Sent: Wednesday, August 28, 2013 3:12 PM
> To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: Receiving file via HTTP
>
> At this time I have the choice as to how they upload it so I'll go
whichever way seems to provide the least complicated solution :)
>
> On 8/28/2013 2:13 PM, Henrik Rützou wrote:
>> Hi Brian,
>> how will the file be uploaded, as an attachement on
>> a multipart/form-data FORM or
>> as parameter in a normal FORM/POST?
>>
>> On Wed, Aug 28, 2013 at 7:41 PM, Brian <[1]belstsrv@xxxxxxxxx>
wrote:
>>
>> Hi Henrik,
>> Do you have any simple examples of setup of powerEXT over HTTP
for
>> receiving a file?
>> Thanks!
>>
>> On 8/28/2013 12:54 PM, Henrik Rützou wrote:
>>
>> Brian,
>> if your partner wants to push a file it can be done with
both
>> CGIDEV2
>> or powerEXT
>> over HTTP (your partner is the HTTP Client and your IBM I
is the
>> server)
>> It can either be done as a multipart/form-data or as a
normal
>> POST
>>
>> On Wed, Aug 28, 2013 at 6:44 PM, Henrik Rützou
>> <[1][2]hr@xxxxxxxxxxxx>
>>
>> wrote:
>> Mike,
>> powerEXT Core is actually only an extension of CGIDEV2 and
has
>> its own
>> version running
>> "under the hood" that comes with the package
>>
>>
>>
[2][3][3]http://184.172.184.159/~servus/pextdrupal/sites/all/themes/the
>> me548/
>>
>> images/powerEXT_Core.png
>> The big difference is really that powerEXT Core is made for
>> generating
>> and READING formats like XML and
>> JSON inline to support WEB 2.0 development. Most CGIDEV2
program
>> will
>> also run on powerEXT Core
>> so you more or less just have to include the powerEXT Core
>> library
>> instead of the CGIDEV2 library and
>> recompile.
>> On Wed, Aug 28, 2013 at 6:04 PM, Mike Krebs
>>
>> <[3][4]mkrebs@xxxxxxxxxxxxxxxxxx> wrote:
>> A few years ago, while playing with CGIDEV2, I created a
"web
>> page"
>> that was a post with a "large FORM field" for data. I
used
>> HTTPAPI
>> to post the document to this "web page". It worked for
the
>> test
>> using small files (that fit into variables). I was
sending
>> small csv
>> files. I looked in our old intranet pages and I couldn't
find
>> my
>> example, but I know I hacked it together using CGIDEV2
on the
>> server
>> side.
>> If your partner can create a HTTPAPI like connection,
that
>> solves
>> two issues for you. One, you will know when the document
is
>> received
>> (a problem with monitoring IFS directories). Two, it is
very
>> easy to
>> create a "web page" that accepts a file. You could use
an
>> actual web
>> page if that works or you could just use the POST url to
have
>> CGIDEV2 process the page directly.
>> Since 2009, it looks like CGIDEV2 now has some extended
>> support for
>>
>> this.
>> [4][5][4]http://www.easy400.net/cgidev/html/exhibiv3.htm
>>
>> More information on another technique:
>>
>> [5][6][5]http://www.easy400.net/fupload/html/page3.htm
>>
>> CGIDEV2 works pretty well and has decent directions on
getting
>> it
>> running quickly. If you have not worked with APACHE
>> directives, it
>> can be frustrating if you want to change where things
are
>> located,
>> but overall, not too hard to setup or use.
>> -----Original Message-----
>>
>> From: [6][7]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> [mailto:[7][8]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On
Behalf Of
>> Brian
>> Sent: Wednesday, August 28, 2013 9:43 AM
>>
>> To: [8][9]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>> Subject: Receiving file via HTTP
>> Hello all,
>> This is not a direct HTTPAPI question, but I am hoping the
list
>> may
>> have
>> some experience or suggestions on this.
>> I have a partner that would like to push a JSON formatted
file to
>> us
>> that we will then parse. I'd like this connection to be
made
>> to our
>> iSeries and the file dropped off to the IFS where we will
pick up
>> and
>> parse the file.
>> I am thinking of using YAJL or powerEXT for the parsing of
the
>> JSON
>> file.
>> What I really need help on is what/how to set up on the
iSeries
>> to
>> accept the connection for the JSON document to be dropped
off to
>> me.
>> Simple to start would be better as we may have a dedicated
>> connection
>> to
>> the partner and not need much/any authentication on the
HTTP
>> connection.
>> If anyone has info on the best/easiest way to set up
something
>> like
>> this, it would be very much appreciated.
>> Thanks all!
>>
>>
>
>
> Kevin Bucknum
> Senior Programmer Analyst
> MEDDATA/MEDTRON
> Tel: 985-893-2550
>
>
-----------------------------------------------------------------------
>> This is the FTPAPI mailing list. To unsubscribe, please
go
>> to:
>>
>>
[9][10][6]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
>>
>>
-----------------------------------------------------------------------
>>
>>
-----------------------------------------------------------------------
>> This is the FTPAPI mailing list. To unsubscribe, please
go
>> to:
>>
>>
>> [10][11][7]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
>>
>>
-----------------------------------------------------------------------
>> --
>> Regards,
>> Henrik Rützou
>>
>>
>> [11][12][8]http://powerEXT.com
>>
>> --
>> Regards,
>> Henrik Rützou
>>
>> [12][13][9]http://powerEXT.com
>>
>> References
>> 1. mailto:[14]hr@xxxxxxxxxxxx
>> 2.
>>
[15][10]http://184.172.184.159/~servus/pextdrupal/sites/all/themes/them
e
>> 548/images/powerEXT_Core.png
>> 3. mailto:[16]mkrebs@xxxxxxxxxxxxxxxxxx
>> 4.
[17][11]http://www.easy400.net/cgidev/html/exhibiv3.htm
>> 5. [18][12]http://www.easy400.net/fupload/html/page3.htm
>> 6. mailto:[19]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> 7. mailto:[20]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> 8. mailto:[21]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>> 9.
[22][13]http://www.scottklement.com/mailman/listinfo/ftpapi
>> 10.
[23][14]http://www.scottklement.com/mailman/listinfo/ftpapi
>> 11. [24][15]http://powerext.com/
>> 12. [25][16]http://powerext.com/
>>
>>
-----------------------------------------------------------------------
>> This is the FTPAPI mailing list. To unsubscribe, please go to:
>> [26][17]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
>>
----------------------------------------------------------------------
>> -
>>
>>
-----------------------------------------------------------------------
>> This is the FTPAPI mailing list. To unsubscribe, please go to:
>> [27][18]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
>>
----------------------------------------------------------------------
>> -
>>
>> --
>> Regards,
>> Henrik Rützou
>>
>> [28][19]http://powerEXT.com
>>
>>
>> References
>>
>> 1. [20]mailto:belstsrv@xxxxxxxxx
>> 2. [21]mailto:hr@xxxxxxxxxxxx
>> 3.
[22]http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme548
/
>> 4. [23]mailto:mkrebs@xxxxxxxxxxxxxxxxxx
>> 5. [24]http://www.easy400.net/cgidev/html/exhibiv3.htm
>> 6. [25]http://www.easy400.net/fupload/html/page3.htm
>> 7. [26]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> 8. [27]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> 9. [28]mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>> 10. [29]http://www.scottklement.com/mailman/listinfo/ftpapi
>> 11. [30]http://www.scottklement.com/mailman/listinfo/ftpapi
>> 12. [31]http://powerEXT.com/
>> 13. [32]http://powerEXT.com/
>> 14. [33]mailto:hr@xxxxxxxxxxxx
>> 15.
[34]http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme548
/images/powerEXT_Core.png
>> 16. [35]mailto:mkrebs@xxxxxxxxxxxxxxxxxx
>> 17. [36]http://www.easy400.net/cgidev/html/exhibiv3.htm
>> 18. [37]http://www.easy400.net/fupload/html/page3.htm
>> 19. [38]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> 20. [39]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> 21. [40]mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>> 22. [41]http://www.scottklement.com/mailman/listinfo/ftpapi
>> 23. [42]http://www.scottklement.com/mailman/listinfo/ftpapi
>> 24. [43]http://powerext.com/
>> 25. [44]http://powerext.com/
>> 26. [45]http://www.scottklement.com/mailman/listinfo/ftpapi
>> 27. [46]http://www.scottklement.com/mailman/listinfo/ftpapi
>> 28. [47]http://powerext.com/
>>
>>
>>
>>
----------------------------------------------------------------------
>> - This is the FTPAPI mailing list. To unsubscribe, please go to:
>> [48]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
----------------------------------------------------------------------
>> -
>>
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [49]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [50]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
References
1. http://www.easy400.net/sectcp/start
2. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
3. http://184.172.184.159/~servus/pextdrupal/sites/all/themes/the
4. http://www.easy400.net/cgidev/html/exhibiv3.htm
5. http://www.easy400.net/fupload/html/page3.htm
6. http://www.scottklement.com/mailman/listinfo/ftpapi
7. http://www.scottklement.com/mailman/listinfo/ftpapi
8. http://powerext.com/
9. http://powerext.com/
10. http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme
11. http://www.easy400.net/cgidev/html/exhibiv3.htm
12. http://www.easy400.net/fupload/html/page3.htm
13. http://www.scottklement.com/mailman/listinfo/ftpapi
14. http://www.scottklement.com/mailman/listinfo/ftpapi
15. http://powerext.com/
16. http://powerext.com/
17. http://www.scottklement.com/mailman/listinfo/ftpapi
18. http://www.scottklement.com/mailman/listinfo/ftpapi
19. http://powerext.com/
20. mailto:belstsrv@xxxxxxxxx
21. mailto:hr@xxxxxxxxxxxx
22. http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme548/
23. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
24. http://www.easy400.net/cgidev/html/exhibiv3.htm
25. http://www.easy400.net/fupload/html/page3.htm
26. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
27. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
28. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
29. http://www.scottklement.com/mailman/listinfo/ftpapi
30. http://www.scottklement.com/mailman/listinfo/ftpapi
31. http://powerext.com/
32. http://powerext.com/
33. mailto:hr@xxxxxxxxxxxx
34. http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme548/images/powerEXT_Core.png
35. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
36. http://www.easy400.net/cgidev/html/exhibiv3.htm
37. http://www.easy400.net/fupload/html/page3.htm
38. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
39. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
40. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
41. http://www.scottklement.com/mailman/listinfo/ftpapi
42. http://www.scottklement.com/mailman/listinfo/ftpapi
43. http://powerext.com/
44. http://powerext.com/
45. http://www.scottklement.com/mailman/listinfo/ftpapi
46. http://www.scottklement.com/mailman/listinfo/ftpapi
47. http://powerext.com/
48. http://www.scottklement.com/mailman/listinfo/ftpapi
49. http://www.scottklement.com/mailman/listinfo/ftpapi
50. 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
-----------------------------------------------------------------------