Caveats for Implementing OES 2 Services
63
6.7 eDirectory
Section 6.7.1, “Avoid Uninstalling eDirectory,” on page 63
Section 6.7.2, “Avoid Renaming Trees and Containers,” on page 63
Section 6.7.3, “Default Static Cache Limit Might Be Inadequate,” on page 63
Section 6.7.4, “eDirectory Not Restarting Automatically,” on page 64
Section 6.7.5, “One Instance Only,” on page 64
Section 6.7.6, “Special Characters in Usernames and Passwords,” on page 64
6.7.1 Avoid Uninstalling eDirectory
OES services are tightly integrated with eDirectory and do not function without it.
Although the eDirectory 8.8 documentation describes how to remove and reinstall eDirectory, the
processes described do not cleanly decouple OES services, nor do they restore service connections.
As a result, not only does uninstalling eDirectory break OES services, reinstalling eDirectory does
not restore them.
If you have an issue that you believe can only be resolved by uninstalling eDirectory, make sure you
consult with Novell Technical Services before you attempt to do so.
6.7.2 Avoid Renaming Trees and Containers
The configuration files for many OES services point to configuration data stored within eDirectory.
Although eDirectory tracks all changes internally, OES services do not. Therefore, if you rename
your eDirectory tree or one of the containers below [Root], you should expect that one or more of
your OES services will break.
If you need to rename a container or tree, make sure that you
1. Identify all of the configuration files for your OES services.
2. Assess whether the changes that you are planning impact any of your service configurations.
3. Understand and articulate the changes that are required to restore your services after renaming.
There are no automated tools in OES for resolving the configuration errors and other problems that
are caused by renaming a tree or its containers.
6.7.3 Default Static Cache Limit Might Be Inadequate
The eDirectory install in OES 2 SP3 sets a default static cache of 200 MB if an
_ndsdb.ini
file is
not present in the
dib
directory.
To improve performance, you can adjust the cache parameter in the
_ndsdb.ini
file after the install
to meet your eDirectory performance requirements, depending on the database size and available
system RAM. We recommend setting the cache to 200 MB on a 2 GB RAM system and 512 MB on
4 GB RAM system.
Summary of Contents for OPEN ENTERPRISE SERVER - CONVERSION GUIDE 12-2010
Page 12: ...12 OES 2 SP3 Planning and Implementation Guide...
Page 24: ...24 OES 2 SP3 Planning and Implementation Guide...
Page 50: ...50 OES 2 SP3 Planning and Implementation Guide...
Page 74: ...74 OES 2 SP3 Planning and Implementation Guide...
Page 78: ...78 OES 2 SP3 Planning and Implementation Guide...
Page 80: ...80 OES 2 SP3 Planning and Implementation Guide...
Page 96: ...96 OES 2 SP3 Planning and Implementation Guide...
Page 146: ...146 OES 2 SP3 Planning and Implementation Guide...
Page 176: ...176 OES 2 SP3 Planning and Implementation Guide...
Page 210: ...210 OES 2 SP3 Planning and Implementation Guide...
Page 218: ...218 OES 2 SP3 Planning and Implementation Guide...
Page 226: ...226 OES 2 SP3 Planning and Implementation Guide...
Page 234: ...234 OES 2 SP3 Planning and Implementation Guide...
Page 236: ...236 OES 2 SP3 Planning and Implementation Guide...
Page 244: ...244 OES 2 SP3 Planning and Implementation Guide...
Page 246: ...246 OES 2 SP3 Planning and Implementation Guide...
Page 250: ...250 OES 2 SP3 Planning and Implementation Guide...
Page 254: ...254 OES 2 SP3 Planning and Implementation Guide...
Page 258: ...258 OES 2 SP3 Planning and Implementation Guide...
Page 284: ...284 OES 2 SP3 Planning and Implementation Guide...
Page 286: ...286 OES 2 SP3 Planning and Implementation Guide...
Page 294: ...294 OES 2 SP3 Planning and Implementation Guide...