Table 2-1 Example application data needs

Application

Class of data

Data

Phonebook

People

Name, email address, phone number, user ID, password,

 

 

department number, manager, mail stop.

Web server

People, groups

User ID, password, group name, groups members, group

 

 

owner.

Calendar server

People, meeting rooms

Name, user ID, cube number, conference room name.

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.2Identifying 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

Data source

Class of data

Data

Human resources database

People

Name, address, phone number, department number,

 

 

manager.

Email system

People, Groups

Name, email address, user ID, password, email

 

 

preferences.

Facilities system

Facilities

Building names, floor names, cube numbers, access codes.

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

Page 20
Image 20
HP UX Direry Server manual Identifying data sources, Characterizing the directory data

UX Direry Server specifications

HP UX Directory Server is a robust and scalable solution designed for managing directory information within enterprise networks. Developed by Hewlett-Packard (HP), this server offers an extensive set of features tailored to meet the needs of organizations that require an efficient way to store, manage, and retrieve identity and access data.

One of the key features of HP UX Directory Server is its ability to handle large directories with significant volumes of data. Built on a highly optimized architecture, it provides excellent performance and can support millions of entries without sacrificing speed or reliability. This capability makes it an ideal choice for large-scale deployments in enterprises that require high availability and responsiveness.

In addition to its scalability, HP UX Directory Server supports a wide range of protocols, including LDAP (Lightweight Directory Access Protocol), which ensures seamless integration with diverse applications and systems across various platforms. The server maintains standards compliance, which facilitates interoperability and simplifies administration tasks.

Security is a top priority for HP UX Directory Server, offering an array of features to protect sensitive information. It supports secure data transmission via TLS/SSL protocols, ensuring encrypted communication between clients and servers. Advanced access controls allow administrators to define fine-grained permissions, helping to safeguard directory data against unauthorized access.

Another salient feature of HP UX Directory Server is its replication capabilities. The server can replicate directory data across multiple instances, ensuring data consistency and availability in distributed environments. This feature is essential for businesses operating across different geographical locations or requiring failover solutions for disaster recovery.

HP UX Directory Server also comes equipped with tools for data management, including an intuitive administration console for configuring and monitoring the server. Additionally, it offers customizable schema capabilities, enabling organizations to tailor the directory structure to fit their specific needs.

Integration with existing identity management solutions is streamlined through connectors and APIs, allowing organizations to extend their directory services and enhance user experience.

In summary, HP UX Directory Server is a powerful directory management solution that combines scalability, security, and integration flexibility. Its support for industry standards, advanced replication, and comprehensive administrative tools makes it an essential asset for organizations seeking to manage identity and access efficiently. By leveraging this technology, businesses can improve their operational efficiency and ensure a secure and organized approach to directory management.