Configuring HP DCE Cells

Integrating DCE Services with MC/ServiceGuard

important is that you read and understand the section in Chapter 4 entitled “Writing Network Applications as HA Services” before beginning the planning process.

Hardware Requirements for a DCE-MC/ServiceGuard Configuration

By their very nature, DCE and DCE applications are distributed, and therefore depend heavily on network resources. Each node in the cluster should have multiple redundant LAN cards connected to multiple LANs. Also, all the normal hardware configuration guidelines outlined in Managing MC/ServiceGuard should be followed when planning for your hardware configuration.

Implementation Alternatives for a DCE-MC/ServiceGuard Installation

The basic configuration, which is supported by the templates, is the DCE host failover. In this configuration, ServiceGuard moves an entire DCE host from one physical node to another.

An alternative configuration is the individual core server failover. In this configuration, the DCE cluster includes a primary host and several smaller hosts. Each of the smaller hosts can perform one or more of the functions normally performed by the primary host. In the event of a system failure for the primary host, ServiceGuard moves only the core servers on the smaller hosts from their individual physical nodes to other physical nodes. For example, in a DCE cluster with individual server hosts for the Security Service and the Name Service, ServiceGuard can move the secd or cdsd servers individually to a new host rather than moving the entire primary host to another node.

Another alternative configuration is the redesignation of master servers through ServiceGuard scripts. This approach involves changing the role of the existing replicas, making them the master servers, instead of moving the databases to new locations.

Other alternative configurations are possible, but they are not discussed here. See Managing MC/ServiceGuard (B3936-90003) for more information about alternative configurations.

The remaining sections in this chapter describe the basic configuration only.

Planning and Configuring HP DCE 1.7

5-33

Page 116 Page 118
Page 117
Image 117
HP UX DCE Software manual Hardware Requirements for a DCE-MC/ServiceGuard Configuration
Page 116 Page 118

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