[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Receiving file via HTTP
There are several problems with FTP
- It is batch oriented
- You need to monitor directories and have mechanisms that ensure you
that a transmission has ended
- You need to have mechanisms that echo back to the sender that you
received the data and the receiver
� �has to hav mechanisms to monitor that
- You have to build tight security around it
- It dosn't transfer data in the right CCSID to the IFS
HTTP and webservices (even bilatteral) can be build without these
drawbacks�
On Thu, Aug 29, 2013 at 5:23 PM, Walker Powell
<[1]Walker.Powell@xxxxxxxxx> wrote:
Then that means that your profile has all object authority.
wP
-----Original Message-----
From: [2]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[3]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Elbert
Cook
Sent: Thu, Aug 29, 2013 9:51 AM
To: 'HTTPAPI and FTPAPI Projects'
Subject: RE: Receiving file via HTTP
I need to look at SECTCP.
Anytime I've played with FTP connections to our Iseries, I've been able
to CD to any directory (anywhere) on our Iseries regardless of any ifs
path authority restrictions I've created.
-----Original Message-----
From: Kevin Bucknum [mailto:[4]Kevin@xxxxxxxxxxxxxxxxxxx]
Sent: Thursday, August 29, 2013 9:05 AM
To: HTTPAPI and FTPAPI Projects; HTTPAPI and FTPAPI Projects
Subject: 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.
[5]http://www.easy400.net/sectcp/start.
________________________________
From: [6]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx on behalf of
[7]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"
<[8]Kevin@xxxxxxxxxxxxxxxxxxx>
wrote:
> Start the ftp server and let him ftp it to you?
>
> -----Original Message-----
> From: [9]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[10]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Brian
> Sent: Wednesday, August 28, 2013 3:12 PM
> To: [11]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][12]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][13]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][14]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][15]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][16]http://www.easy400.net/cgidev/html/exhibiv3.htm
>>
>> � � � � � � More information on another technique:
>>
>> � � � � � � � [5][6][17]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][18]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> � � � � �[mailto:[7][8][19]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On
>> Behalf
Of
>> � �Brian
>> � � � � �Sent: Wednesday, August 28, 2013 9:43 AM
>>
>> � � � � �To: [8][9][20]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: [21]985-893-2550
>
>
----------------------------------------------------------------------
> -
>> � � � � �This is the FTPAPI mailing list. � To unsubscribe,
please go
>> � �to:
>>
>> � � � � � �[9][10][22]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
>>
>>
>>
---------------------------------------------------------------------
>> --
>>
>>
-----------------------------------------------------------------------
>> � � � � �This is the FTPAPI mailing list. � To unsubscribe,
please go
>> � �to:
>>
>>
>> [10][11][23]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
>>
>>
-----------------------------------------------------------------------
>> � � � � �--
>> � � � � �Regards,
>> � � � � �Henrik Rützou
>>
>>
>> � � � � � �[11][12][24]http://powerEXT.com
<[25]http://powerext.com/>
>>
>> � � � � � �--
>> � � � � � �Regards,
>> � � � � � �Henrik Rützou
>>
>> � � � � � �[12][13][26]http://powerEXT.com
<[27]http://powerext.com/>
>>
>> � � �References
>> � � � � � �1. mailto:[14][28]hr@xxxxxxxxxxxx
>> � � � � � �2.
>> � � �[15][29]http://184.172.184.159/~servus/pextdrupal/sites/all/themes/th
eme
>> � � �548/images/powerEXT_Core.png
>> � � � � � �3. mailto:[16][30]mkrebs@xxxxxxxxxxxxxxxxxx
>> � � � � � �4.
[17][31]http://www.easy400.net/cgidev/html/exhibiv3.htm
>> � � � � � �5.
[18][32]http://www.easy400.net/fupload/html/page3.htm
>> � � � � � �6.
mailto:[19][33]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> � � � � � �7.
mailto:[20][34]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> � � � � � �8. mailto:[21][35]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>> � � � � � �9.
[22][36]http://www.scottklement.com/mailman/listinfo/ftpapi
>> � � � � � 10.
[23][37]http://www.scottklement.com/mailman/listinfo/ftpapi
>> � � � � � 11. [24][38]http://powerext.com/
>> � � � � � 12. [25][39]http://powerext.com/
>>
>>
-----------------------------------------------------------------------
>> � �This is the FTPAPI mailing list. � To unsubscribe, please go
to:
>> � �[26][40]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
>>
---------------------------------------------------------------------
>> -
>> -
>>
>>
-----------------------------------------------------------------------
>> � �This is the FTPAPI mailing list. � To unsubscribe, please go
to:
>> � �[27][41]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
>>
---------------------------------------------------------------------
>> -
>> -
>>
>> � �--
>> � �Regards,
>> � �Henrik Rützou
>>
>> � �[28][42]http://powerEXT.com <[43]http://powerext.com/>
>>
>>
>> References
>>
>> � �1. mailto:[44]belstsrv@xxxxxxxxx
>> � �2. mailto:[45]hr@xxxxxxxxxxxx
>> � �3.
[46]http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme548
/
>> � �4. mailto:[47]mkrebs@xxxxxxxxxxxxxxxxxx
>> � �5. [48]http://www.easy400.net/cgidev/html/exhibiv3.htm
>> � �6. [49]http://www.easy400.net/fupload/html/page3.htm
>> � �7. mailto:[50]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> � �8. mailto:[51]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> � �9. mailto:[52]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>> � 10. [53]http://www.scottklement.com/mailman/listinfo/ftpapi
>> � 11. [54]http://www.scottklement.com/mailman/listinfo/ftpapi
>> � 12. [55]http://powerEXT.com/
>> � 13. [56]http://powerEXT.com/
>> � 14. mailto:[57]hr@xxxxxxxxxxxx
>> � 15.
[58]http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme548
/images/p
owerEXT_Core.png
>> � 16. mailto:[59]mkrebs@xxxxxxxxxxxxxxxxxx
>> � 17. [60]http://www.easy400.net/cgidev/html/exhibiv3.htm
>> � 18. [61]http://www.easy400.net/fupload/html/page3.htm
>> � 19. mailto:[62]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> � 20. mailto:[63]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> � 21. mailto:[64]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>> � 22. [65]http://www.scottklement.com/mailman/listinfo/ftpapi
>> � 23. [66]http://www.scottklement.com/mailman/listinfo/ftpapi
>> � 24. [67]http://powerext.com/
>> � 25. [68]http://powerext.com/
>> � 26. [69]http://www.scottklement.com/mailman/listinfo/ftpapi
>> � 27. [70]http://www.scottklement.com/mailman/listinfo/ftpapi
>> � 28. [71]http://powerext.com/
>>
>>
>>
>>
---------------------------------------------------------------------
>> -
>> - This is the FTPAPI mailing list. �To unsubscribe, please go to:
>> [72]http://www.scottklement.com/mailman/listinfo/ftpapi
>>
---------------------------------------------------------------------
>> -
>> -
>>
>
>
----------------------------------------------------------------------
> - This is the FTPAPI mailing list. �To unsubscribe, please go to:
> [73]http://www.scottklement.com/mailman/listinfo/ftpapi
>
----------------------------------------------------------------------
> -
>
----------------------------------------------------------------------
> - This is the FTPAPI mailing list. �To unsubscribe, please go to:
> [74]http://www.scottklement.com/mailman/listinfo/ftpapi
>
----------------------------------------------------------------------
> -
-----------------------------------------------------------------------
This is the FTPAPI mailing list. �To unsubscribe, please go to:
[75]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
________________________________
This message may contain confidential information and is intended
only for the individual to whom it is addressed. If you are not the
named addressee, you should not use, disseminate or copy this
e-mail. Please notify the sender immediately by e-mail if you have
received this e-mail by mistake and delete this e-mail from your
system. E-mail transmission cannot be guaranteed to be secure or
free from errors or viruses. The sender therefore does not accept
liability for problems with this message that arise out of e-mail
transmission.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. �To unsubscribe, please go to:
[76]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
--
Regards,
Henrik Rützou
� [77]http://powerEXT.com
�
References
1. mailto:Walker.Powell@xxxxxxxxx
2. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
3. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
4. mailto:Kevin@xxxxxxxxxxxxxxxxxxx
5. http://www.easy400.net/sectcp/start
6. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
7. mailto:elbert@xxxxxxxxxxxxxxx
8. mailto:Kevin@xxxxxxxxxxxxxxxxxxx
9. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
10. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
11. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
12. mailto:belstsrv@xxxxxxxxx
13. mailto:hr@xxxxxxxxxxxx
14. http://184.172.184.159/~servus/pextdrupal/sites/all/themes/the
15. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
16. http://www.easy400.net/cgidev/html/exhibiv3.htm
17. http://www.easy400.net/fupload/html/page3.htm
18. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
19. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
20. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
21. tel:985-893-2550
22. http://www.scottklement.com/mailman/listinfo/ftpapi
23. http://www.scottklement.com/mailman/listinfo/ftpapi
24. http://powerEXT.com/
25. http://powerext.com/
26. http://powerEXT.com/
27. http://powerext.com/
28. mailto:hr@xxxxxxxxxxxx
29. http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme
30. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
31. http://www.easy400.net/cgidev/html/exhibiv3.htm
32. http://www.easy400.net/fupload/html/page3.htm
33. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
34. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
35. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
36. http://www.scottklement.com/mailman/listinfo/ftpapi
37. http://www.scottklement.com/mailman/listinfo/ftpapi
38. http://powerext.com/
39. http://powerext.com/
40. http://www.scottklement.com/mailman/listinfo/ftpapi
41. http://www.scottklement.com/mailman/listinfo/ftpapi
42. http://powerEXT.com/
43. http://powerext.com/
44. mailto:belstsrv@xxxxxxxxx
45. mailto:hr@xxxxxxxxxxxx
46. http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme548/
47. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
48. http://www.easy400.net/cgidev/html/exhibiv3.htm
49. http://www.easy400.net/fupload/html/page3.htm
50. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
51. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
52. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
53. http://www.scottklement.com/mailman/listinfo/ftpapi
54. http://www.scottklement.com/mailman/listinfo/ftpapi
55. http://powerEXT.com/
56. http://powerEXT.com/
57. mailto:hr@xxxxxxxxxxxx
58. http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme548/images/powerEXT_Core.png
59. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
60. http://www.easy400.net/cgidev/html/exhibiv3.htm
61. http://www.easy400.net/fupload/html/page3.htm
62. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
63. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
64. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
65. http://www.scottklement.com/mailman/listinfo/ftpapi
66. http://www.scottklement.com/mailman/listinfo/ftpapi
67. http://powerext.com/
68. http://powerext.com/
69. http://www.scottklement.com/mailman/listinfo/ftpapi
70. http://www.scottklement.com/mailman/listinfo/ftpapi
71. http://powerext.com/
72. http://www.scottklement.com/mailman/listinfo/ftpapi
73. http://www.scottklement.com/mailman/listinfo/ftpapi
74. http://www.scottklement.com/mailman/listinfo/ftpapi
75. http://www.scottklement.com/mailman/listinfo/ftpapi
76. http://www.scottklement.com/mailman/listinfo/ftpapi
77. http://powerext.com/
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------