× 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.  Home
  2. MIDRANGE-L
  3. July 2003

Re: Moving PC files to HTTP server

Alan

Glad to see a convert! ;-)

Libraries are not hierarchical (well, not much, anyway). But there is another part of what is called Integrated File System (IFS) that is hierarchical. The library system is actually kind of a directory within the overall IFS.

The easiest way to move the files is to map a network drive to the root of IFS, then just move through Windows Explorer. You need to have Operations Navigator (also called iSeries Navigator now) on your PC in order to set up the file share on the 400. Navigator is part of Client Access (or iSeries Access now).

If you don't have Client Access installed, you can FTP to the iSeries, just start the ftp server on the 400.

Contact me offlist if you want. I've left out some details.

HTH

Vern

At 09:34 AM 7/9/2003 -0400, you wrote: 
I've been working with my 400's HTTP server and am considering moving all my
Web site files (currently on IIS) to it for security reasons.

What is a good way to transfer my existing .html, .gif, .jpg etc. files to
the 400?

What library are the files placed in?

Since libraries are apparently a linear "bus"-style directory structure how
are hierarchical "folders" managed?

Is there an administration app for all this?

Last but not least. Is there a way to associate MIME types (i.e. .swf files
to Flash player)?

Whew! That's a lot. Any answers are appreciated!

Alan



As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.