User manual NOVELL EDIRECTORY 8.8 SP1 INSTALLATION

[. . . ] Novell eDirectory 8. 8 Installation Guide novdocx (en) 6 April 2007 Novell eDirectory 8. 8 SP1 May 25, 2007 TM www. novell. com INSTALLATION GUIDE novdocx (en) 6 April 2007 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. [. . . ] (Conditional) If you are installing a secondary server, all the replicas in the partition that you install the product on should be in the On state. (Conditional) If you are installing a secondary server into an existing tree as a nonadministrator user, ensure that you have the following rights: Supervisor rights to the container the server is being installed into. Supervisor rights to the partition where you want to add the server. NOTE: This is required for adding the replica when the replica count is less than 3. All Attributes rights: read, compare, and write rights over the W0. KAP. Security object. Entry rights: browse rights over Security container object. All Attributes rights: read and compare rights over Security container object. (Conditional) If you are installing a secondary server into an existing tree as a nonadministrator user, ensure that at least one of the servers in the tree has the same or higher eDirectory version as that of the secondary being added as container admin. In case the secondary being added is of later version, then the schema needs to be extended by the admin of the tree before adding the secondary using container admin. Configuring Static IP Address Refer to "Configuring Static IP Address" on page 12 for more information on configuring static IP addresses. 70 Novell eDirectory 8. 8 Installation Guide novdocx (en) 6 April 2007 4. 3 Hardware Requirements Hardware requirements depend on the specific implementation of eDirectory. Two factors increase performance: more cache memory and faster processors. For best results, cache as much of the DIB Set as the hardware allows. eDirectory scales well on a single processor. However, Novell eDirectory 8. 8 takes advantage of multiple processors. Adding processors improves performance in some areas--for example, logins and having multiple threads active on multiple processors. eDirectory itself is not processor intensive, but it is I/O intensive. The following table illustrates typical system requirements for Novell eDirectory for Solaris. Objects Processor Memory Hard Disk 100, 000 1 million 10 million Sun* Enterprise 220 Sun Enterprise 450 Sun Enterprise 4500 with multiple processors 384 MB 2 GB 2+ GB 144 MB 1. 5 GB 15 GB Requirements for processors might be greater than the table indicates, depending upon additional services available on the computer as well as the number of authentications, reads, and writes that the computer is handling. Processes such as encryption and indexing can be processor intensive. 4. 4 Forcing the Backlink Process to Run Because the internal eDirectory identifiers change when upgrading to Novell eDirectory, the backlink process must update backlinked objects for them to be consistent. Backlinks keep track of external references to objects on other servers. For each external reference on a server, the backlink process ensures that the real object exists in the correct location and verifies all backlink attributes on the master of the replica. The backlink process occurs two hours after the database is open, and then every 780 minutes (13 hours). The interval is configurable from 2 minutes to 10, 080 minutes (7 days). [. . . ] In the case of Win32, slpd. exe runs as a service on the local machine. User agents query the local service agent by sending messages to the loop-back address on a well-known port. A service agent locates and caches directory agents and their supported scope list by sending a DA discovery request directly to potential DA addresses by: 1. Checking all statically configured DA addresses (and adding new ones to the SA's known DA cache). [. . . ]