HP-UX Directory Server 8.1 deployment guide

Table 2-1 Example application data needs
DataClass of dataApplication
Name, email address, phone number, user ID, password,
department number, manager, mail stop.
PeoplePhonebook
User ID, password, group name, groups members, group
owner.
People, groupsWeb server
Name, user ID, cube number, conference room name.People, meeting roomsCalendar server
After identifying the applications and information used by each application, it is apparent that
some types of data are used by more than one application. Performing this kind of exercise during
the data planning stage can help to avoid data redundancy problems in the directory, and show
more clearly what data directory-dependent applications require.
The final decision about the types of data maintained in the directory and when the information
is migrated to the directory is affected by these factors:
The data required by various legacy applications and users
The ability of legacy applications to communicate with an LDAP directory
2.3.2 Identifying data sources
To identify all the data to include in the directory, perform a survey of the existing data stores.
The survey should include the following:
Identify organizations that provide information.
Locate all the organizations that manage information essential to the enterprise. Typically,
this includes the information services, human resources, payroll, and accounting departments.
Identify the tools and processes that are information sources.
Some common sources for information are networking operating systems (Windows, Novell
Netware, UNIX NIS), email systems, security systems, PBX (telephone switching) systems,
and human resources applications.
Determine how centralizing each piece of data affects the management of data.
Centralized data management can require new tools and new processes. Sometimes
centralization requires increasing staff in some organizations while decreasing staff in others.
During the survey, consider developing a matrix that identifies all the information sources in
the enterprise, similar to Table 2-2 “ Example information sources”:
Table 2-2 Example information sources
DataClass of dataData source
Name, address, phone number, department number,
manager.
PeopleHuman resources database
Name, email address, user ID, password, email
preferences.
People, GroupsEmail system
Building names, floor names, cube numbers, access codes.FacilitiesFacilities system
2.3.3 Characterizing the directory data
All the data identified to include in the directory can be characterized according to the following
general points:
Format
Size
Number of occurrences in various applications
20 Planning the directory data