Configuring HP DCE Cells

Configuring Cells Using dce_config

CHECK_TIME: Set to y to have time checked and possibly synchronized; n otherwise. Default is y. If dce_config is executed with a here-document, CHECK_TIME should be set to n since time checking uses a telnet command that causes input from the here-document to be lost.

CONFIG_PROTSEQ: Communication protocol used for some dce_config operations.This variable is set to ncadg_ip_udp by default for use of the UDP protocol, which works in almost all cases. Change to ncacn_ip_tcp only if TCP protocol routing is available.

DISPLAY_THRESHOLD: Minimum priority log messages from dce_config that are written to stdout. Default is SUMMARY. ERROR and WARNING messages are always displayed. Possible values, in priority order: ERROR, WARNING, SUMMARY, DETAIL, VERBOSE, DEBUG.

LOG_THRESHOLD: Minimum priority log messages from

dce_config that are written to /var/opt/dce/config/dce_config.log. Default: DEBUG (all messages). ERROR, WARNING, and SUMMARY messages are always logged. Possible values, in priority order: ERROR, WARNING, SUMMARY, DETAIL, VERBOSE, DEBUG.

DEFAULT_MAX_ID: Maximum Unix ID value supported by DCE Security Registry. Can be set to any value. Default value is 32767. A value larger than the default prevents accounts with IDs larger than 32767 from accessing DCE cells that use the default. A value smaller than the default prevents foreign accounts with IDs larger than 32767 from accessing the cell.

DEFAULT_PW: Default password used when the registry is created. Used only for logging in the cell administrator for the first time (within dce_config). A cell administrator can change the default by editing the value of DEFAULT_PW in the script. Default is -dce-.

DIR_REPLICATE: Supports replication of additional directories when configuring additional CDS Servers. If set to n, it will not prompt if additional directories need to be replicated.

DO_CHECKS: Set to n to prompt when a non-fatal warning is encountered. Default is y.

DOMAIN_NAME: The name of the host's Internet domain for use in a fully qualified host name. Used as a default when configuring a Kerberos client if /etc/resolv.conf does not already contain a domain

5-26

Planning and Configuring HP DCE 1.7

Page 110
Image 110
HP UX DCE Software manual Configuring Cells Using dceconfig

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.