ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaty_5.4.0.1/itdnotice.htm

131 lines
7.9 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="Notices and limitations" />
<meta name="abstract" content="This topic provides a list of known issues and limitations in the IBM Telephone Directory V5.2 application." />
<meta name="description" content="This topic provides a list of known issues and limitations in the IBM Telephone Directory V5.2 application." />
<meta name="DC.Relation" scheme="URI" content="itd.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="itdnotice" />
<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>Notices and limitations</title>
</head>
<body id="itdnotice"><a name="itdnotice"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Notices and limitations</h1>
<div><p>This topic provides a list of known issues and limitations in the IBM<sup>®</sup> Telephone
Directory V5.2 application.</p>
<p>While using IBM Telephone Directory V5.2, you should be aware of the
following notices and limitations.</p>
<div class="section"><h4 class="sectiontitle">Setup</h4><ul><li>The IBM Telephone
Directory V5.2 application can be configured to use an existing base DN from
your <span class="keyword">iSeries™</span> Directory Server
(LDAP) server. If you publish your system directory to your LDAP server using
the inetOrgPerson object class, you can use that directory for the application.
This is done by specifying the base DN you want to use for the IBM Telephone Directory
application during IBM Welcome Page V1.1 installation. However, the password
field is optional in the inetOrgPerson object class. An authorized user needs
to set the password value in the entries if they want the users to update
their own entries.</li>
<li>If system directory publishing is left on/enabled on your system, periodic
updates to the directory will cause changes made to be discarded through the IBM Telephone
Directory application. This is a limitation of directory publishing. It is
recommended to use directory publishing only to do the initial set up of a
directory, then turn it off if directory updates are to be made.</li>
</ul>
</div>
<div class="section"><h4 class="sectiontitle">General usage</h4><ul><li>When searching on a telephone number, there are no implied wildcards.
The IBM Telephone
Directory V5.2 application searches for the exact value you enter. This means
you <span class="uicontrol">must</span> specify the wildcard character (*) if you
want to search for part of a telephone number. <p>For example, you want to
find all users that have the 507 area code. The following search criteria
will do this:</p>
<pre>*507*</pre>
<div class="note"><span class="notetitle">Note:</span> You might receive search
results other than those containing a 507 area code (those users with 507
in the actual telephone number).</div>
</li>
<li>When you are prompted for a user ID and password, the characters entered
must map to the default job CCSID of the IBM HTTP server for <span class="keyword">i5/OS™</span>.
The HTTP server assumes the user ID and password you enter is encoded in the
net CCSID (ASCII) configured for the server and converts them to the server's
job CCSID (EBCDIC). If the characters don't map, sign on fails. For example,
if your user ID or password contains Japanese characters, the HTTP server
must be running with a Japanese net CCSID (such as 943) and a Japanese job
CCSID (such as 5035). If it is not, you will not be able to sign on to the IBM Telephone
Directory application, because the HTTP server is not able to
authenticate your credentials. This limitation does not apply to form input
or display, because all data is encoded in UTF-8. It only applies to sign
on. <p>The following areas are affected:</p>
<ul><li>Registering users during closed enrollment</li>
<li>Updating directory entries</li>
<li>Changing entry passwords</li>
<li>Deleting directory entries</li>
</ul>
<p>The following areas are not affected:</p>
<ul><li>Registering users during open enrollment</li>
<li>Basic search</li>
<li>Advanced search</li>
<li>Detailed entry display</li>
<li>Online help and other forms</li>
</ul>
</li>
</ul>
</div>
<div class="section"><h4 class="sectiontitle">Registering</h4><ul><li>Passwords are not required by default.</li>
<li>If you want to insert a photo into a user entry, it has to be in .jpg
format. The IBM Telephone
Directory application does not support .gif format. The photo size must be
less than the configured value size.</li>
<li>A valid user entry must be created in order for other entries to specify <span class="uicontrol">Manager
Name</span>, <span class="uicontrol">Assistant Name</span>, or <span class="uicontrol">Backup
Name</span> fields. This means you must create a directory using a top-down
process if you want to fill all values in during the initial user entry creation.
Alternatively, you can use the <span class="uicontrol">Update entry</span> function
to enter manager, assistant, or backup values after all user entries have
been created. For example, a manager entry has to be created before his or
her employees can enter Manager Name in their individual entries. If the manager
entry does not exist during the employee entry creation, you must update the
employee entry after the manager has been created.</li>
<li>If you delete an entry (such as a manager) that is used in another entry
(such as an employee having his or her manager listed), the IBM Telephone Directory
application does not remove the manager name from the employee entry. The
same scenario is applicable for the Backup Name and Assistant Name fields.</li>
<li>If a manager, assistant, or backup entry is deleted, links to that entry
are no longer displayed in an associated user entry. If the deleted entry
is recreated (and uses the same CN and user ID values), the links to that
entry automatically reappear. In addition, when a manager entry is deleted,
the Reports-To Chain page (for entries linked to the deleted entry) no longer
work until the manager entry is recreated. However, the Same-Department page
still works, even though the manager's entry is has been deleted.</li>
</ul>
</div>
<div class="section"><h4 class="sectiontitle">Data integrity</h4><ul><li>You are responsible for data integrity in the IBM Telephone Directory application. The application
comes with a limited set of validation rules; however, it is the administrator
or the user who is responsible for the input of correct data.</li>
</ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="itd.htm" title="The IBM Telephone Directory V5.2 application is a part of IBM Business Solutions Version 1.0 (5722-BZ1) and is a Web-based application that provides the ability to search, view, and manage entries in an LDAP directory.">IBM Telephone Directory V5.2</a></div>
</div>
</div>
</body>
</html>