Before Installing HP DCE/9000 Version 1.7

Preinstallation Planning

Cell Directory Service Configuration

In configuring CDS servers and clients, pay careful attention to the HP DCE/ 9000 hardware requirements for the DCE product. (See “Hardware and Software Requirements” in this chapter.) Appropriate kernel configuration, memory, disk, and especially swap space are essential to the proper functioning of the CDS subsystem.

Tape backups of the CDS server database are extremely important for recovery from catastrophic problems. HP strongly recommends regular tape back ups of all CDS server databases, especially those containing any master replicas. Tape backups and restorations require the CDS server in question to be temporarily shut down.

Most CDS problems, however, do not require resorting to tape backup. Directory replication provides continuous online backup for most failures, with faster recovery and less stale data. This makes directory replication highly desirable for all DCE cells. Every cell should configure at least two CDS servers, and read-only replicas of all directories should be created on the backup server. In this configuration, backup is continuous, and recovery only involves switching the role of the servers.

Multiple CDS servers can be configured for specific purposes in the cell. Multiple CDS servers with read-only replicas of all directories in the name space should always be present for backup and recovery purposes. Performance considerations may also make the configuration of other CDS servers desirable. For instance, administrators of very busy cells or cells with large numbers of nodes should consider adding additional CDS servers to share the name space processing load. Similarly, administrators of cells with groups of nodes separated by WAN links should consider providing a local CDS server for each group to enhance performance. Administrators with very large cells may want to partition the name space among several CDS servers, replicating only the locally used directories, to distribute the storage overhead of the name space.

Each of these CDS configuration strategies is documented in the OSF DCE Administration Guide — Core Services.

Time Services

A minimum of three DTS servers is recommended for any cell with three or more member systems. If you use an external time provider, you can have only one of these running in a cell.

Planning and Configuring HP DCE 1.7

3-7

Page 72 Page 74
Page 73
Image 73
HP UX DCE Software manual Cell Directory Service Configuration, Time Services
Page 72 Page 74

UX DCE Software specifications

HP UX DCE Software, or Hewlett-Packard UNIX Distributed Computing Environment, represents a significant tool in the realm of distributed system architecture. Designed primarily for enterprise environments, HP UX DCE enhances the reliability, scalability, and manageability of applications over diverse networked systems.

One of the main features of HP UX DCE is its ability to integrate various computing platforms, enabling seamless communication and resource sharing across distributed nodes. This facilitates the creation of complex applications that can operate on a multitude of systems, thus enhancing operational flexibility. DCE employs standardized interfaces, which means applications written for one platform can run on any other platform that supports DCE, promoting cross-platform compatibility.

In terms of technologies, HP UX DCE utilizes Remote Procedure Calls (RPC) as a core feature. This mechanism allows different applications to communicate and invoke procedures on remote systems as if they were local calls. Additionally, DCE includes a robust security model that incorporates Kerberos for authentication, ensuring that communication between nodes remains secure and protected against unauthorized access.

Another significant characteristic of HP UX DCE is its distributed file system, which allows for transparent file access across different machines. The DCE File System (DFS) provides a unified namespace and manages data replication and consistency across distributed storage resources. This reduces the complexity of data management and enhances data availability.

HP UX DCE also supports a variety of programming languages, making it accessible for developers accustomed to different coding environments. This versatility encourages widespread adoption and innovation, as developers can leverage existing skills to create distributed applications.

Furthermore, HP UX DCE is built for high availability, ensuring that critical applications remain responsive even in the face of hardware or network failures. Its inherent component redundancy and fault-tolerant architecture are designed to minimize downtime, which is essential for mission-critical applications in enterprise scenarios.

In conclusion, HP UX DCE Software provides a comprehensive framework for developing, deploying, and managing distributed applications. Its core features such as RPC support, a secure authentication mechanism, a robust file system, and cross-platform compatibility make it a vital resource for organizations aiming to leverage distributed computing effectively. As enterprises evolve, HP UX DCE stands out as an influential solution in the dynamic landscape of distributed environments.
Top Page Image Contents