Design Example: A Multinational Enterprise And Its Extranet - Red Hat DIRECTORY SERVER 8.1 - DEPLOYMENT Deployment Manual

Hide thumbs Also See for DIRECTORY SERVER 8.1 - DEPLOYMENT:
Table of Contents

Advertisement

For more information about setting resource limits based on the bind DN, refer to the "User Account
Management" chapter in the Red Hat Directory Server Administrator's Guide.
• They create a password policy which specifies that passwords must be at least eight characters in
length and expire after 90 days.
For more information about password policies, see
• They create an ACI that gives members of the accounting role access to all payroll information.
9.1.7. Local Enterprise Tuning and Optimizations
The company uses the following tactics to optimize its deployment of Directory Server:
• Running the dsktune utility.
The dsktune utility provides an easy and reliable way of checking the patch levels and kernel
parameter settings of the system. For more information about dsktune, refer to the Red Hat
Directory Server Installation Guide.
• Optimizing the entry and database caches.
Example Corp. sets the entry cache size to 2GB entries and the database cache to 250MB to
ensure that all of the indexes fit into RAM, optimizing server performance.
9.1.8. Local Enterprise Operations Decisions
The company makes the following decisions regarding the day-to-day operation of its directory:
• Back up the databases every night.
• Use SNMP to monitor the server status.
For more information about SNMP, refer to the Red Hat Directory Server Administrator's Guide.
• Auto-rotate the access and error logs.
• Monitor the error log to ensure that the server is performing as expected.
• Monitor the access log to screen for searches that should be indexed.
For more information about the access, error, and audit logs, refer to the "Monitoring Server and
Database Activity" chapter in the Red Hat Directory Server Administrator's Guide.
9.2. Design Example: A Multinational Enterprise and Its
Extranet
This example builds a directory infrastructure for Example Corp. International. The Example Corp.
from the previous example has grown into a large, multinational company. This example builds on the
directory structure created in the last example for Example Corp., expanding the directory design to
meet its new needs.
Example Corp. has grown into an organization dispersed over three main geographic locations: the
US, Europe, and Asia. Example Corp. now has more than 20,000 employees, all of whom live and
Local Enterprise Tuning and Optimizations
Section 8.6, "Designing a Password
Policy".
143

Advertisement

Table of Contents
loading

Table of Contents