You must provide certain information during the installation process. The Installation Planning Worksheet provides you with a convenient place to concisely record that information ahead of time for reference during the installation process.
For an overview of the installation process, see Section 5.1, Preparing for Core Driver Installation.
For a detailed explanation of the items on the Installation Planning Worksheet, see Items on the Installation Planning Worksheet.
This section describes each of the items on the Installation Planning Worksheet
Record Census Search object names and attributes. These describe how the Census is to be populated.
The fully distinguished name of each Census Search object.
A Census Search object can be a User object, a Group object, an Organizational Role object, an Organization container object, or an Organizational Unit container object.
Whether or not User objects covered by this Census Search object are added to the Census.
Whether or not Group objects covered by this Census Search object are added to the Census.
Whether or not users who are members of Group objects or occupants of Organizational Role objects covered by this Census Search object are added to the Census.
Whether or not Alias objects covered by this Census Search object are added to the Census. The user or group object that is represented by an alias object is provisioned to platforms.
For container Census Search objects only: Indicate how many steps down the directory tree hierarchy beyond the Census Search object the driver searches for users and groups to add to the Census. Zero causes the search to stop at the container Search object.
The users to grant rights to administer the driver and the types of functions you will allow them to perform. For details, see Rights Required for Web Application Use.
Establish UID/GID set names and reserved ranges.
The common name to give each UID/GID set in the ASAM System container.
The low and high bounds of the range to reserve for the system administrator to use locally on the platform. The driver does not assign UID/GID numbers in the reserved range.
A Platform Set provides the relationship between the Search objects that describe a collection of users and groups, and one or more platform systems that share the same users and groups.
The name to give each Platform Set configuration object in the ASAM System container.
The name of a previously defined UID/GID Set that is to be used to assign UID numbers and GID numbers for Linux/UNIX users and groups associated with the Platform Set.
Leave this option empty to use the PosixAccount and posixGroup uidNumber and gidNumber attributes.
Search objects identify the users and groups to be used to populate the platforms that you add to this Platform Set.
A Platform Set Search object can be a User object, a Group object, an Organizational Role object, an Organization container object, an Organizational Unit container object, or a Dynamic Group object.
Include for each individual platform.
The common name to give the Platform Configuration object in the ASAM System container.
The name of the Platform Set this platform is to belong to.
Whether or not requests for password replication information from eDirectory are honored for this platform.
The IP address or DNS name of the platform to be used for TCP/IP communications with other driver components. If your platform uses more than one network interface, list all of the addresses.