200 lines
13 KiB
HTML
200 lines
13 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="reference" />
|
||
|
|
<meta name="DC.Title" content="File considerations" />
|
||
|
|
<meta name="abstract" content="The following considerations apply to using the iSeries Access for Web file functions in a Web application server environment." />
|
||
|
|
<meta name="description" content="The following considerations apply to using the iSeries Access for Web file functions in a Web application server environment." />
|
||
|
|
<meta name="DC.subject" content="Files, content-type (MIME-type) mapping" />
|
||
|
|
<meta name="keywords" content="Files, content-type (MIME-type) mapping" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzammhfiles.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2003, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2003, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzammfileconsiderations" />
|
||
|
|
<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>File considerations</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzammfileconsiderations"><a name="rzammfileconsiderations"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">File considerations</h1>
|
||
|
|
<div><p>The following considerations apply to using the iSeries™ Access
|
||
|
|
for Web file functions in a Web application server environment.</p>
|
||
|
|
<div class="section" id="rzammfileconsiderations__mimemapping"><a name="rzammfileconsiderations__mimemapping"><!-- --></a><h4 class="sectiontitle">Content-type (MIME-type) mapping</h4><p>iSeries Access
|
||
|
|
for Web uses the file extension to determine the file content-type (MIME-type).
|
||
|
|
The file content-type is used by the browser to determine how best to render
|
||
|
|
the information. For example, files with an extension of .htm, .html, or .txt
|
||
|
|
are rendered in the browser window. The browser will also attempt to determine
|
||
|
|
what browser plug-in to use for the given file content-type. A file with a
|
||
|
|
.pdf extension will cause the browser to attempt to load the Adobe Acrobat
|
||
|
|
Reader.</p>
|
||
|
|
<p>iSeries Access
|
||
|
|
for Web provides a way to extend or override the included file extension to
|
||
|
|
file content-type mapping. These overrides are done on an instance basis.
|
||
|
|
For each Web application server (WebSphere<sup>®</sup> and ASF Tomcat) instance
|
||
|
|
for which iSeries Access
|
||
|
|
for Web is configured, you can override the included file extension content-type
|
||
|
|
mapping.</p>
|
||
|
|
<p>To override the included mappings, create a file called <samp class="codeph">extension.properties</samp> and
|
||
|
|
place the file in the integrated file system at one of the following locations: </p>
|
||
|
|
<ul><li>(For ASF Tomcat) <samp class="codeph">/QIBM/UserData/Access/Web2/<var class="varname">application_server</var>/<var class="varname">instance_name</var>/config</samp></li>
|
||
|
|
<li>(For the WebSphere environments): <samp class="codeph">/QIBM/UserData/Access/Web2/<var class="varname">application_server</var>/<var class="varname">instance_name</var>/<var class="varname">server_name</var>/config</samp></li>
|
||
|
|
</ul>
|
||
|
|
<p>An example is provided at /QIBM/ProdData/Access/Web2/config/extension.properties
|
||
|
|
that you can copy to your UserData tree.</p>
|
||
|
|
<p>For <samp class="codeph"><var class="varname">application_server</var></samp>,
|
||
|
|
specify: </p>
|
||
|
|
<ul><li><img src="./delta.gif" alt="Start of change" /><samp class="codeph">was60</samp> for WebSphere Application Server V6.0 <img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" /><samp class="codeph">was60nd</samp> for WebSphere Application Server Network
|
||
|
|
Deployment V6.0 for OS/400<sup>®</sup><img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" /><samp class="codeph">was51exp</samp> for WebSphere Application Server - Express
|
||
|
|
for iSeries V5.1
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" /><samp class="codeph">was51base</samp> for WebSphere Application Server for iSeries V5.1
|
||
|
|
(Base and Network Deployment editions)<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li><samp class="codeph">was50base</samp> for WebSphere Application Server for iSeries V5.0
|
||
|
|
(Base and Network Deployment editions) </li>
|
||
|
|
<li><samp class="codeph">was50exp</samp> for WebSphere Application Server - Express
|
||
|
|
for iSeries V5.0
|
||
|
|
</li>
|
||
|
|
<li><samp class="codeph">asftomcat</samp> for a ASF Tomcat configuration</li>
|
||
|
|
</ul>
|
||
|
|
<p>For <samp class="codeph"><var class="varname">instance_name</var></samp>, specify the
|
||
|
|
name of the Web application server instance in which iSeries Access for Web was configured.
|
||
|
|
This Web application server instance was specified on the QIWA2/CFGACCWEB2
|
||
|
|
command when you configured iSeries Access for Web. </p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />For <samp class="codeph"><var class="varname">server_name</var></samp>,
|
||
|
|
specify the name of the application server within the Web application server
|
||
|
|
instance in which iSeries Access for Web was configured. This application
|
||
|
|
server was specified on the QIWA2/CFGACCWEB2 command when you configured iSeries Access
|
||
|
|
for Web. <img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>Some examples of <samp class="codeph">extension.properties</samp> entries
|
||
|
|
are: </p>
|
||
|
|
<ul><li><samp class="codeph">out=text/plain</samp></li>
|
||
|
|
<li><samp class="codeph">lwp=application/vnd.lotus-wordpro</samp></li>
|
||
|
|
</ul>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />For a list of file content-types, see the <a href="www.iana.org/assignments/media-types/ " target="_blank">Internet Assigned
|
||
|
|
Numbers Authority Mime Media Types Web page</a>.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzammfileconsiderations__saveas"><a name="rzammfileconsiderations__saveas"><!-- --></a><img src="./delta.gif" alt="Start of change" /><h4 class="sectiontitle">Forcing a Save As window when downloading
|
||
|
|
files</h4><p>When using Microsoft<sup>®</sup> Internet Explorer and any
|
||
|
|
of the iSeries Access
|
||
|
|
for Web functions to download a file to the browser, many times Internet Explorer
|
||
|
|
will display the file's content in the browser without offering an opportunity
|
||
|
|
to just save the file. Basically, Internet Explorer examines the data in the
|
||
|
|
file and determines that it can display the data in the browser window. Many
|
||
|
|
users do not want this behavior and would prefer to save the file immediately.</p>
|
||
|
|
<p>To
|
||
|
|
get around this issue, iSeries Access for Web can now optionally write a
|
||
|
|
HTTP header that forces Microsoft Internet Explorer and other
|
||
|
|
browsers to display a File Save As window. The HTTP header being written is
|
||
|
|
a Content-Disposition header. The Content-Disposition header that can be written
|
||
|
|
is controlled by creating a <samp class="codeph">disposition.properties</samp> file.
|
||
|
|
Different Content-Disposition headers can be written based on the file content-type
|
||
|
|
(MIME-type) being downloaded.</p>
|
||
|
|
<p>iSeries Access for Web uses the file
|
||
|
|
extension to determine the file content-type (MIME-type) to be sent to the
|
||
|
|
browser. The file content-type is used by the browser to determine how best
|
||
|
|
to render the information. For more information about controlling the MIME-type
|
||
|
|
based on the file extension, see <a href="#rzammfileconsiderations__mimemapping">Content-type
|
||
|
|
(MIME type) mapping</a> in this topic. This topic describes how to map
|
||
|
|
file extensions to different MIME-types.</p>
|
||
|
|
<p>Once the MIME-type mapping
|
||
|
|
setup has been done, you need to create a <samp class="codeph">disposition.properties</samp> file
|
||
|
|
in the iSeries Access
|
||
|
|
for Web UserData tree. For most of the supported Web serving environments,
|
||
|
|
the iSeries Access
|
||
|
|
for Web UserData tree is /QIBM/UserData/Access/Web2/<var class="varname">application_server/instance_name/server_name</var>/config.
|
||
|
|
Replace <var class="varname">application_server</var>, <var class="varname">instance_name</var>,
|
||
|
|
and <var class="varname">server_name</var> with the unique values on your server.</p>
|
||
|
|
<p>The <samp class="codeph">disposition.properties</samp> file
|
||
|
|
needs to contain entries that specify which Content-Disposition header value
|
||
|
|
should be written, based on the MIME-type of the file being downloaded using iSeries Access
|
||
|
|
for Web.</p>
|
||
|
|
<p>The following sample properties files give an example of what
|
||
|
|
would be required to force a File Save As window when downloading a file with
|
||
|
|
a .TXT extension: </p>
|
||
|
|
<p><strong>Example</strong>:</p>
|
||
|
|
<p>The <samp class="codeph">extensions.properties</samp> file
|
||
|
|
needs to contain: <samp class="codeph"> txt=text/plain</samp> </p>
|
||
|
|
<p>The <samp class="codeph">disposition.properties</samp> file
|
||
|
|
needs to contain: <samp class="codeph">text/plain=attachment</samp></p>
|
||
|
|
<p>Changes to
|
||
|
|
the properties file will take effect shortly after the files are changed.
|
||
|
|
The changes do not take effect immediately unless the Web application server
|
||
|
|
is stopped and restarted.</p>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Document Library Services (QDLS) file system enrollment</h4><div class="p">A user must be enrolled in the system directory in
|
||
|
|
order to access the Document Library Services (QDLS) file system with iSeries Access
|
||
|
|
for Web. The steps needed to enroll a user are listed below. If the user has
|
||
|
|
previously been enrolled or does not need access to the QDLS file system,
|
||
|
|
these steps are not necessary. A user can still use the File function of iSeries Access
|
||
|
|
for Web without having access to the QDLS file system.<ol><li>Enter <samp class="codeph">GO PCSTSK</samp> at the iSeries command prompt. This display
|
||
|
|
screen is shown: <div class="fignone"><span class="figcap">Figure 1. Client Access Tasks (GO PCSTSK)</span><pre>#
|
||
|
|
|
||
|
|
+----------------------------------------------------------------------+
|
||
|
|
| PCSTSK Client Access Tasks |
|
||
|
|
| System: SYSTEM1 |
|
||
|
|
| Select one of the following: |
|
||
|
|
| |
|
||
|
|
| User Tasks |
|
||
|
|
| 1. Copy PC document to database |
|
||
|
|
| 2. Copy database to PC document |
|
||
|
|
| |
|
||
|
|
| Administrator Tasks |
|
||
|
|
| 20. Work with Client Access administrators |
|
||
|
|
| <span class="uicontrol">21. Enroll Client Access users</span> |
|
||
|
|
+----------------------------------------------------------------------+</pre>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Select the Enroll Client Access Users option. This display screen is shown:<div class="fignone"><span class="figcap">Figure 2. Enroll Client Access Users display</span><pre>+----------------------------------------------------------------------+
|
||
|
|
| Enroll Client Access Users |
|
||
|
|
| |
|
||
|
|
|Type choices, press Enter. |
|
||
|
|
| |
|
||
|
|
| User profile . . . . . . . . AARON Name |
|
||
|
|
| User identifier: |
|
||
|
|
| User ID . . . . . . . . . AARON Character value |
|
||
|
|
| Address . . . . . . . . . SYSTEM1 Character value |
|
||
|
|
| User description . . . . . . AARON B. |
|
||
|
|
| Add to system directory . . *NO *NO, *YES |
|
||
|
|
+----------------------------------------------------------------------+</pre>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Enter the appropriate information for these values:<dl><dt class="dlterm">User profile</dt>
|
||
|
|
<dd>Name of user</dd>
|
||
|
|
<dt class="dlterm">User ID</dt>
|
||
|
|
<dd>Usually the same as the User profile name</dd>
|
||
|
|
<dt class="dlterm">User address</dt>
|
||
|
|
<dd>Usually the same as the system name</dd>
|
||
|
|
<dt class="dlterm">User description</dt>
|
||
|
|
<dd>A description of the user</dd>
|
||
|
|
<dt class="dlterm">Add to system directory </dt>
|
||
|
|
<dd>Use *YES if you want to use the QDLS file system</dd>
|
||
|
|
</dl>
|
||
|
|
See the online help for a complete description of the entry
|
||
|
|
fields.</li>
|
||
|
|
<li>Repeat the above steps to enroll other users in the Directory Entry Database.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzammhfiles.htm" title="Browse and work with iSeries files and file shares.">File</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|