Directory server

You can export your policies to a directory server. Read this topic to see the Lightweight Directory Access Protocol (LDAP) concepts and configuration as well as the quality of service (QoS) schema.

QoS policy configuration can be exported to a directory server, using LDAP version 3.

How to use a directory server

Exporting QoS policies to a directory server makes your policies easier to manage. There are three ways to use the directory server:

The configuration data can be stored on one local directory server for many systems to share.
The configuration data can be configured, stored, and only used by one system (not shared).
The configuration data can reside on a directory server that holds data for other systems, but is not shared between those other systems. This allows you to use a single location to back up and save data for several systems.

Advantages to saving exclusively on your local system

Saving QoS policies on your local system is not as complex. There are a number of advantages to using policies locally:

Eliminate the complexity of LDAP configuration for users who do not need it.
Improve performance, because writing to LDAP is not the fastest method.
Duplicate a configuration between different systems more easily. You can copy the file from one system to another. Because there is no primary or secondary machine, you can tailor each policy directly on the individual systems.

LDAP resources

If you decide to export your policies to an LDAP server, be familiar with LDAP concepts and directory structures before you continue. Within the QoS function in iSeries™ Navigator, you can configure a directory server that is used with your QoS policy.

Keywords
When you configure your directory server, you need to determine whether to associate keywords with each quality of service (QoS) configuration.
Distinguished name
When you want to manage part of your directory, you refer to the distinguished name (DN) or (if you choose) a keyword.

Parent topic:

Concepts