Administering the TEDG During Run Time

This topic includes the following sections:

• Understanding Run-time Administration

• Using the dmadmin Command Interpreter

 

---

Understanding Run-time Administration

The main tools for run-time administration are:

• A command, dmadmin(1), that allows administrators to configure, monitor, and tune domain gateway groups dynamically.

• A Domains administrative server, DMADM(5), that provides the administrative processing required for updating a Domains configuration. This server acts as a back-end to the dmadmin command.

• A gateway administrative server, GWADM(5), that provides the run-time administrative processing required for a specific gateway group. This server also acts as a back-end to the dmadmin command.

Note: The GWTOPEND(5) gateway process provides connectivity to remote gateway processes. Clients and servers send and receive messages between BEA Tuxedo and BEA TOP END systems via the GWTOPEND process. This process is not involved in Domains administration.

The following illustration shows how these tools are used in run-time administration.

Figure 10-1 Domains Run-time Administration

 

See Also

• dmadmin(1) in BEA Tuxedo Command Reference

• DMADM(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference

• GWADM(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference

• GWTOPEND(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference

 

---

Using the dmadmin Command Interpreter

The dmadmin command is an interactive command interpreter for the administration of domain gateway groups defined for a particular BEA Tuxedo application. It is used by application administrators for the interactive administration of the information stored in the BDMCONFIG file and the different gateway groups running within a particular BEA Tuxedo application.

Use dmadmin to:

• Obtain statistics or other information gathered by gateway groups

• Change the gateway group parameters

• Add (or update) information to the BDMCONFIG file

To use dmadmin in configuration mode, execute it in either of two ways:

• Use the -c option as follows.

  dmadmin -c

• Use the config subcommand as follows.

  dmadmin
  >config

Defining a BEA TOP END Password

For the TOP END Domain Gateway, if security is enabled, you need to associate a BEA TOP END password with each local domain of type TOPEND defined in the DM_LOCAL_DOMAINS section of the DMCONFIG file. You assign this password using the dmadmin topendpasswd subcommand as follows.

topendpasswd (tepasswd) [-r] local_domain_name

This command prompts the administrator for a new password for the specified local domain of type TOPEND. The gateway uses this password when sending messages to the BEA TOP END system. The -r option specifies that existing passwords and new passwords should be encrypted using a new key generated by the system. The password is truncated if it is longer than the maximum length of twelve characters.

For details, see dmadmin(1) in the BEA Tuxedo Command Reference.

Run-time Deletions

Run-time deletions to the BDMCONFIG file can be performed only when the changes do not involve an active gateway group.

See Also

• dmadmin(1) in the BEA Tuxedo Command Reference

• topendpasswd(1) in the BEA Tuxedo Command Reference