72 lines
4.7 KiB
HTML
72 lines
4.7 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="Keywords" />
|
||
|
|
<meta name="abstract" content="When you configure your directory server, you need to determine whether to associate keywords with each quality of service (QoS) configuration." />
|
||
|
|
<meta name="description" content="When you configure your directory server, you need to determine whether to associate keywords with each quality of service (QoS) configuration." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8ldap.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8tree.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8direct_server.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzak8keyword" />
|
||
|
|
<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>Keywords</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8keyword"><a name="rzak8keyword"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Keywords</h1>
|
||
|
|
<div><p>When you configure your directory server, you need to determine
|
||
|
|
whether to associate keywords with each quality of service (QoS)
|
||
|
|
configuration.</p>
|
||
|
|
<p>The keyword fields are optional and can be ignored. The following information
|
||
|
|
helps explain the keyword concept and why you might want to use keywords.</p>
|
||
|
|
<p>In the QoS Initial Configuration wizard, you can configure a directory
|
||
|
|
server. You can specify whether the server you configure is a primary system
|
||
|
|
or a secondary system. The server that you maintain all your QoS policies
|
||
|
|
on, is known as the primary system.</p>
|
||
|
|
<p>Keywords are used to identify configurations created by primary systems.
|
||
|
|
Although created on the primary system, keywords are really for the benefit
|
||
|
|
of the secondary system. They allow secondary systems to load and use configurations
|
||
|
|
created by a primary system. The following descriptions help explain how to
|
||
|
|
use keywords on each system.</p>
|
||
|
|
<dl><dt class="dlterm">Keywords and primary systems</dt>
|
||
|
|
<dd>Keywords are associated to QoS configurations created and maintained by
|
||
|
|
a primary system. They are used, so that secondary systems can identify a
|
||
|
|
configuration created by a primary system.</dd>
|
||
|
|
<dt class="dlterm">Keywords and secondary systems</dt>
|
||
|
|
<dd>Secondary systems use keywords to search for configurations. The secondary
|
||
|
|
system loads and uses configurations created by a primary system. When you
|
||
|
|
configure a secondary system, you can select specific keywords. Depending
|
||
|
|
on the keyword selected, the secondary system loads any configurations associated
|
||
|
|
with the selected keyword. This allows the secondary system to load multiple
|
||
|
|
configurations created by multiple primary systems.</dd>
|
||
|
|
</dl>
|
||
|
|
<p>When you begin to configure the directory server in iSeries™ Navigator, use the QoS task help
|
||
|
|
for specific instructions.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak8ldap.htm" title="You can export your policies to a directory server. Read this topic to see the advantages of using or not using a directory server, Lightweight Directory Access Protocol (LDAP) concepts and configuration, as well as the quality of service (QoS) schema.">Directory server</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzak8tree.htm" title="When you want to manage part of your directory, you refer to the distinguished name (DN) or (if you choose) a keyword.">Distinguished name</a></div>
|
||
|
|
<div><a href="rzak8direct_server.htm" title="QoS policy configurations can be exported to an LDAP directory server.">Configure directory server</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|