What Is a DMCONFIG File


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Doc Home \| TOP END Domain Gateway \| Topic List \| Previous \| Next \| Contents

Using the BEA Tuxedo TOP END Domain Gateway

A Domains configuration for the TEDG consists of at least one local BEA Tuxedo domain and at least one BEA TOP END system that can communicate and share services with the help of the BEA Tuxedo Domains feature. In a Domains configuration using the TEDG, a BEA TOP END system should be considered a "remote domain." How a BEA Tuxedo domain and a BEA TOP END system (remote domain) are connected and which services they make accessible to each other are defined in a Domains configuration file for the TEDG domain and the BEA TOP END system definition on the BEA TOP END system. The text version of a Domains configuration file is known as the DMCONFIG file after the environment variable used to hold the name of the actual file used.

A DMCONFIG file defines the following:

The remote domains with which the local domain can communicate
The local resources (such as services and queues) accessible to remote domains
The remote resources accessible to the local domain
Which local and remote resources are accessible through which gateways

The DMCONFIG file is parsed and loaded into a binary version, called BDMCONFIG, by the dmloadcf(1) utility. The dmadmin(1) command uses BDMCONFIG (or a copy of it) for monitoring the run-time application.

One BDMCONFIG file is required on each domain in a multi-domain configuration in which the Domains feature is being used.

The DMCONFIG and BDMCONFIG files are analogous to the UBBCONFIG and TUXCONFIG files used to define a BEA Tuxedo application.

A DMCONFIG file for a TEDG must contain five required sections and may contain one or two optional sections. The required sections are:

DM_LOCAL_DOMAINS
DM_REMOTE_DOMAINS
DM_TOPEND
DM_LOCAL_SERVICES
DM_REMOTE_SERVICES

The optional sections are:

DM_ROUTING
DM_ACCESS_CONTROL

Domains Terminology Improvements

In this release, some of the Domains terminology is changing. The Domains MIB uses improved class and attribute terminology to describe the interaction between local and remote domains. While this improved terminology is more accurate than previous domains terminology, the scope of changes to domains-related documentation and error messages is limited in this release. The improved terminology has been applied to the DM_MIB classes, reference page, and error messages, the DMCONFIG file syntax, and various DMCONFIG error messages.

For backwards compatibility, aliases are provided between the DMCONFIG terminology used prior to this release and the improved Domains MIB terminology. In this release, DMCONFIG accepts both versions of the terminology. For details, see Domains Terminology Improvements in BEA Tuxedo File Formats and Data Descriptions Reference.