ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamm_5.4.0.1/rzammcustomizedpage4.htm

86 lines
7.4 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="concept" />
<meta name="DC.Title" content="Customized content" />
<meta name="abstract" content="Portions of the iSeries Access for Web content are retrieved from static HTML files. A style sheet is also used to control aspects of the product's appearance. User-supplied files can be used in place of the default implementations. The following considerations exist for creating these user-supplied files:" />
<meta name="description" content="Portions of the iSeries Access for Web content are retrieved from static HTML files. A style sheet is also used to control aspects of the product's appearance. User-supplied files can be used in place of the default implementations. The following considerations exist for creating these user-supplied files:" />
<meta name="DC.Relation" scheme="URI" content="rzammlogintemplate.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammmyhomepage.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammhcustomize.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammdefaultpg.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammspecialtags.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammhomepage.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammstylesheet.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammmainpage.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammpagetemplate.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammlogintemplate.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="rzammcustomizedpage" />
<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>Customized content</title>
</head>
<body id="rzammcustomizedpage"><a name="rzammcustomizedpage"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Customized content</h1>
<div><p>Portions of the iSeries™ Access for Web content are retrieved from
static HTML files. A style sheet is also used to control aspects of the product's
appearance. User-supplied files can be used in place of the default implementations.
The following considerations exist for creating these user-supplied files:</p>
<ul><li>The default files in /QIBM/ProdData/Access/Web2/html can be used as a
starting point, but they should not be modified directly. These files reside
in the product directory which is only meant for product files. <p>If the
default files are used as a starting point, they should be copied to the /QIBM/UserData/Access/Web2
tree or to another location in the iSeries integrated file system. Modifications
can then be made to the copy of the files.</p>
<p><img src="./delta.gif" alt="Start of change" />Localized versions
of the default files can be found in subdirectories under /QIBM/ProdData/Access/Web2/html.
The subdirectories are named using ISO Language Codes and ISO Country Codes.
These codes are lower-case, two-letter codes as defined by ISO-639 and ISO-3166. <img src="./deltaend.gif" alt="End of change" /></p>
</li>
<li>*PUBLIC, QEJBSVR (for WebSphere<sup>®</sup>), or QTMHHTTP (for ASF Tomcat) must have
at least *RX authority to the user-supplied HTML files and to any files they
reference. This authority is also required for the directories containing
the files.</li>
<li>If the user-supplied HTML file contains image, style sheet, or other external
references with absolute paths, the HTTP server must be configured to serve
the files. If the external references contain paths relative to the path containing
the user-supplied HTML file, no HTTP server configuration is needed.</li>
<li>Image files should not be placed in the /QIBM/ProdData/Access/Web2/html/images
directory. This directory is meant for product image files only.</li>
</ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzammlogintemplate.htm" title="The login template supplies content to display before and after the login form when iSeries Access for Web is configured for form-based, application server authentication.">Login template</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzammdefaultpg.htm" title="iSeries Access for Web generates most of its page content dynamically in response to user actions. The remainder of the content is retrieved from static HTML files. A style sheet is also used to control certain aspects of the content's appearance.">Default page content</a></div>
<div><a href="rzammspecialtags.htm" title="Portions of the iSeries Access for Web content are retrieved from static HTML files. There are default implementations for this content. Alternatively, user-supplied files can be used. A number of special tags can be used within these files. When these tags are encountered, they are replaced with the appropriate content.">Special tags</a></div>
<div><a href="rzammhomepage.htm" title="The home page is displayed when the iSeries Access for Web home page URL is accessed.">Home page</a></div>
<div><a href="rzammstylesheet.htm" title="iSeries Access for Web uses Cascading Style Sheets (CSS) to control certain aspects of the appearance of page content.">Style sheets</a></div>
<div><a href="rzammmainpage.htm" title="The iSeries Access for Web main page is displayed when the main page URL (http://&lt; server_name &gt;/webaccess/iWAMain) is accessed with no parameters.">Main page</a></div>
<div><a href="rzammpagetemplate.htm" title="The iSeries Access for Web page template contains static content to display before and after dynamically generated content on functional pages.">Page template</a></div>
<div><a href="rzammlogintemplate.htm" title="The login template supplies content to display before and after the login form when iSeries Access for Web is configured for form-based, application server authentication. For information on form-based, application server authentication, see Security considerations.">Login template</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzammmyhomepage.htm" title="iSeries Access for Web delivers a default home page that is shown when the home page URL (http://&lt;server_name&gt;/webaccess/iWAHome) is accessed.">My home page</a></div>
<div><a href="rzammhcustomize.htm" title="iSeries Access for Web provides support to tailor the product.">Customize</a></div>
</div>
</div>
</body>
</html>