Using the DCE Configuration Tool

The DCE configurator (called dce_config) is a shell-script-based configuration tool, this enables you to run dce_config from within the MPE/iX POSIX shell.

Check the following preliminary tasks before you enable the DCE configuration main menu:

Ensure that the system network is running (RPC requires network sockets).
Create an MPE/iX group named DCECONFG. At the system prompt, enter:
NEWGROUP DCECONFIG
You must be in an MPE/iX group (that is, your working directory must be an MPE/iX group not a POSIX directory) when you start the POSIX shell that runs dce_config.

Perform the following steps to obtain the DCE Main Menu for configuring cells:

Log on to the console as MANAGER.SYS,DCECONFG. At the system prompt, enter:
HELLO MANAGER.SYS,DCECONFG
Enter the POSIX shell. At the system prompt, enter:
sh.hpbin.sys -L
The shell prompt is displayed (for example, shell/iX>).
Ensure that /usr/bin is in your shell command search path. At the shell prompt, enter:
export PATH=/usr/bin:$PATH
Bring up the DCE cofiguration Main menu. At the shell prompt, enter:
dce_config
The DCE Main Menu as shown in Figure 2-1 “DCE Main Menu” is displayed on the console.

Figure 2-1 DCE Main Menu

From this menu you can configure your system as a DCE client or client system.

Configuring a DCE Client (Client-Only System)

A DCE client can not be configured without a functional DCE cell. In other words, when you configure your machine as a DCE client, the DCE cell that you are going to configure needs to be up and running. You need to know the name of the cell and the names of the systems that the DCE servers (Security, CDS and DTS) reside.

Before preceding with the DCE Client configuration, ensure that the HOSTS.NET.SYS file in your machine contains the IP addresses for the systems that are running as Servers. When complete, follow the description in the "Startup the DCE Configuration" menu to bring up the DCE main menu.

The following steps enable you to add your machine as a DCE client node:

Select "1. Configure Client" from the DCE Main Menu.
Respond to the questions as shown in Figure 2-2 “Security Client”.
Figure 2-2 Security Client
Two DCE daemon jobs (rpcd, dced) are streamed and are running. You are informed that your machine is now a Security client.
Respond to the questions shown in Figure 2-3 “Add CDS Client” to add CDS client configuration to your system:
Figure 2-3 Add CDS Client
Respond to the "...LAN profile..." question as shown in Figure 2-4 “Using LAN Profile Question”.
Figure 2-4 Using LAN Profile Question
One DCE daemon job (cdsadv) is now running and you are informed that this machine is now a CDS client.
To continue configuring the machine as a DTS clerk, DTS local server, or DTS global server, respond to the question shown in Figure 2-5 “Configuring Question”.
Figure 2-5 Configuring Question
Once DTS daemon job (dtsd) is running, you are informed that this machine is now a DTS clerk.
Select 99 to exit from dce_config.




	WARNING! The password for the "`cell_admin none none`" user is a well-known default value. Since this is a security hole, it is recommended that the password be changed immediately after exiting this script by using "dce_login", then the "rgy_edit change" command.

Removing the DCE Cell

To remove a cell, perform the following steps:

Bring up the DCE Main Menu (as described in "Using the DCE Configuration Tool" earlier in this section).
Select "4. REMOVE" from the DCE Main Menu. The dce_config tool displays the message as shown in Figure 2-6 “Remove Message”.
Figure 2-6 Remove Message
A "Yes" response stops all running DCE daemons in that system, removes all remnants of previous DCE configuration and removes all remnants of previous DCE configuration for all components.
NOTE: Existing user credentials will be invalid when DCE daemons are stopped and restarted.

Using the DCE Configuration Tool

Technical documentation

» Table of Contents

» Index

Configuring a DCE Client (Client-Only System)

Removing the DCE Cell