100 lines
6.0 KiB
HTML
100 lines
6.0 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="topic" />
|
||
|
|
<meta name="DC.Title" content="Supported i5/OS file systems for Web content served by HTTP Server" />
|
||
|
|
<meta name="abstract" content="This topic provides information about supported i5/OS file system for Web content." />
|
||
|
|
<meta name="description" content="This topic provides information about supported i5/OS file system for Web content." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiereference.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2002,2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002,2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaiestoringandserving" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Supported i5/OS file
|
||
|
|
systems for Web content served by HTTP Server</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiestoringandserving"><a name="rzaiestoringandserving"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Supported i5/OS file
|
||
|
|
systems for Web content served by HTTP Server</h1>
|
||
|
|
<div><p>This topic provides information about supported i5/OS™ file system
|
||
|
|
for Web content.</p>
|
||
|
|
<div class="important"><span class="importanttitle">Important:</span> Information
|
||
|
|
for this topic supports the latest PTF levels for HTTP Server for i5/OS .
|
||
|
|
It is recommended that you install the latest PTFs to upgrade to the latest
|
||
|
|
level of the HTTP Server for i5/OS. Some of the topics documented here are
|
||
|
|
not available prior to this update. See <a href="http://www-03.ibm.com/servers/eserver/iseries/software/http/services/service.html" target="_blank">http://www.ibm.com/servers/eserver/iseries/software/http/services/service.htm</a> <img src="www.gif" alt="Link outside Information Center" /> for more information. </div>
|
||
|
|
<p>The HTTP Server can serve content from any of the following Integrated
|
||
|
|
File System file systems:</p>
|
||
|
|
<ul><li>root (/)</li>
|
||
|
|
<li>QSYS.LIB</li>
|
||
|
|
<li>QOpenSys</li>
|
||
|
|
<li>QDLS</li>
|
||
|
|
<li>NFS</li>
|
||
|
|
<li>QFileSvr.400</li>
|
||
|
|
<li>QNetWare</li>
|
||
|
|
<li>QNTC</li>
|
||
|
|
<li>QOPT</li>
|
||
|
|
<li>UDFS </li>
|
||
|
|
</ul>
|
||
|
|
<p>A file system provides the support that allows users and applications to
|
||
|
|
access specific segments of storage that are organized as logical units. These
|
||
|
|
logical units are files, directories, libraries, and objects.</p>
|
||
|
|
<p>Each file system has a set of logical structures and rules for interacting
|
||
|
|
with information in storage. These structures and rules may be different from
|
||
|
|
one file system to another. From the perspective of structures and rules,
|
||
|
|
the support for accessing database files and various other object types through
|
||
|
|
libraries can be thought of as a file system. Similarly, you can think of
|
||
|
|
the support for accessing documents (which are really stream files) through
|
||
|
|
the folders structure as a separate file system.</p>
|
||
|
|
<p>As you decide from which file system to serve files, you might want to
|
||
|
|
consider the following:</p>
|
||
|
|
<ul><li>Serving from the root (or /) directory gives you the fastest response
|
||
|
|
times.</li>
|
||
|
|
<li>Will the tools you use to maintain your site be compatible with the file
|
||
|
|
system you choose?</li>
|
||
|
|
<li>How easy must it be to move content from platform to platform?</li>
|
||
|
|
</ul>
|
||
|
|
<p>Remember that any individual server can serve content (CGI scripts; HTML
|
||
|
|
files; graphics such as .jpegs, GIFs, and image maps; and so on) from many
|
||
|
|
file systems at once. You can configure your server to serve content from
|
||
|
|
whatever file systems suit your needs.</p>
|
||
|
|
<p>See <a href="../ifs/rzaaxkickoff.htm">File systems in the integrated file system</a> for more information
|
||
|
|
about the integrated file system.</p>
|
||
|
|
<p>Before you start serving your content from the Integrated File System,
|
||
|
|
you must ensure that the world can access the files that you want to serve.
|
||
|
|
You must grant the QTMHHTTP user profile or *PUBLIC the following authorities
|
||
|
|
and permissions to enable Web serving with IBM<sup>®</sup> HTTP Server for iSeries™:</p>
|
||
|
|
<ul><li>QTMHHTTP or *PUBLIC must have *USE authority to all library system objects
|
||
|
|
that you intend to serve.</li>
|
||
|
|
<li>If you use any of the log directives with any Integrated File System directory
|
||
|
|
name, the directory must exist, and QTMHHTTP or *PUBLIC must have *RWX authority.</li>
|
||
|
|
<li>The QTMHHTTP user profile or *PUBLIC must be granted *RX authority to
|
||
|
|
all objects (HTML pages, graphics, and so on) that you intend to serve.</li>
|
||
|
|
<li>To use CGI programs to access any of the objects you serve, the QTMHHTP1
|
||
|
|
user profile or *PUBLIC needs the same authority to the objects as QTMHHTTP.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> When considering from which file system to serve files, keep in mind
|
||
|
|
that AllowOverride should be None for QDLS. Also, file serving and manipulation
|
||
|
|
from QSYS and other EBCDIC file systems might result in performance bottlenecks.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiereference.htm" title="This topic provides additional reference documentation for HTTP Server and the IBM Web Administration for i5/OS interface.">Reference documentation for HTTP Server</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|