Files

The BDMCONFIG environment variable is used to find the BDMCONFIG configuration file.

Example 1

The following Domains configuration file defines a five-site Domains configuration. The example shows four Bank Branch domains communicating with a Central Bank Branch. Three of the Bank Branches run within other BEA Tuxedo domains. The fourth Branch runs under the control of another TP domain. OSI TP is used for communication between that domain and the Central Bank. The example shows the Domains configuration file from the Central Bank point of view.

# BEA Tuxedo Domains Configuration File for the Central Bank
#
#
*DM_LOCAL
#
DEFAULT: SECURITY = NONE
 
c01  GWGRP = bankg1
     TYPE = TDOMAIN
     ACCESSPOINTID = "BA.CENTRAL01"
     DMTLOGDEV = "/usr/apps/bank/DMTLOG"
     DMTLOGNAME = "DMTLG_C01"
 
c02  GWGRP = bankg2
     TYPE = OSITP
     ACCESSPOINTID = "BA.CENTRAL02"
     DMTLOGDEV = "/usr/apps/bank/DMTLOG"
     DMTLOGNAME = "DMTLG_C02"
    
#
*DM_REMOTE
#
b01  TYPE = TDOMAIN
     ACCESSPOINTID = "BA.BANK01"
 
b02  TYPE = TDOMAIN
     ACCESSPOINTID = "BA.BANK02"
 
b03  TYPE = TDOMAIN
     ACCESSPOINTID = "BA.BANK03"
 
b04  TYPE = OSITP
     ACCESSPOINTID = "BA.BANK04"
    
*DM_TDOMAIN
#
# local network addresses
c01  NWADDR = "//newyork.acme.com:65432"  NWDEVICE ="/dev/tcp"

# remote network addresses
b01  NWADDR = "//192.11.109.5:1025"  NWDEVICE = "/dev/tcp"
b02  NWADDR = "//dallas.acme.com:65432"  NWDEVICE = "/dev/tcp"
b03  NWADDR = "//192.11.109.156:4244"  NWDEVICE = "/dev/tcp"
 
*DM_OSITP
#
c02  APT = "BA.CENTRAL01"
     AEQ = "TUXEDO.R.4.2.1"
     AET = "{1.3.15.0.3},{1}"
     ACN = "XATMI"
b04  APT = "BA.BANK04"
     AEQ = "TUXEDO.R.4.2.1"
     AET = "{1.3.15.0.4},{1}"
     ACN = "XATMI"
 
*DM_EXPORT
#
open_act ACL = branch
close_act ACL = branch
credit
debit
balance
loan   LACCESSPOINT = c02   ACL = loans
 
*DM_IMPORT
#
tlr_add LACCESSPOINT = c01   ROUTING = ACCOUNT
tlr_bal LACCESSPOINT = c01   ROUTING = ACCOUNT
tlr_add RACCESSPOINT = b04   LACCESSPOINT = c02   RNAME ="TPSU002"
tlr_bal RACCESSPOINT = b04   LACCESSPOINT = c02   RNAME ="TPSU003"
tlr_bal RACCESSPOINT = b02,b03"   LACCESSPOINT = c02

*DM_ROUTING
#
ACCOUNT FIELD = branchid BUFTYPE = "VIEW:account"
   RANGES = "MIN-1000:b01,1001-3000:b02,*:b03"
 
*DM_ACCESS_CONTROL
#
branch ACLIST = "b01,b02,b03"
loans  ACLIST = b04

Example 2

This example shows the BEA Tuxedo Domains configuration file for one of the Bank Branches (BANK01).

#
#BEA Tuxedo Domains Configuration file for a Bank Branch
#
#
*DM_LOCAL
#
b01  GWGRP = auth
     TYPE = TDOMAIN
     ACCESSPOINTID = "BA.BANK01"
     DMTLOGDEV = "/usr/apps/bank/DMTLOG"
 
*DM_REMOTE
#
c01  TYPE = TDOMAIN
     ACCESSPOINTID = "BA.CENTRAL01"
 
*DM_TDOMAIN
#
b01  NWADDR = "//192.11.109.156:4244"  NWDEVICE = "/dev/tcp"
c01  NWADDR = "//newyork.acme.com:65432"  NWDEVICE ="/dev/tcp"
*DM_EXPORT
#
tlr_add   ACL = central
tlr_bal   ACL = central
 
*DM_IMPORT
#
 
OPA001   RNAME = "open_act"
CLA001   RNAME = "close_act"
CRD001   RNAME = "credit"
DBT001   RNAME = "debit"
BAL001   RNAME = "balance"
 
*DM_ACCESS_CONTROL
#
central   ACLIST = c01

Network Addresses

Suppose the local machine on which a TDomain is being run is using TCP/IP addressing and is named backus.company.com, with address 155.2.193.18. Further suppose that the port number at which the TDomain should accept requests is 2334. Assume that port number 2334 has been added to the network services database under the name bankapp-gwtaddr. The address can be represented in the following ways:

//155.2.193.18:bankapp-gwtaddr

//155.2.193.18:2334

//backus.company.com:bankapp-gwtaddr

//backus.company.com:2334

0x0002091E9B02C112

The last of these representations is hexadecimal format. The 0002 is the first part of a TCP/IP address. The 091E is the port number 2334 translated into a hexadecimal number. After that each element of the IP address 155.2.193.12 is translated into a hexadecimal number. Thus the 155 becomes 9B, 2 becomes 02 and so on.

See Also

Setting Up a BEA Tuxedo Application

Administering a BEA Tuxedo Application at Run Time

Using the BEA Tuxedo Domains Component

Programming a BEA Tuxedo ATMI Application Using C

DMCONFIG for GWTOPEND(5)

Name

DMCONFIG for GWTOPEND—Text version of a Domains configuration file for a BEA TOP END domain gateway.

Description

A Domains configuration is a set of two or more domains (business applications) that can communicate and share services with the help of the BEA Tuxedo Domains component. How multiple domains are connected and which services they make accessible to each other are defined in a Domains configuration file for each BEA Tuxedo domain participating in the Domains configuration. The text version of a Domains configuration file is known as the DMCONFIG file, although the configuration file may have any name as long as the content of the file conforms to the format described on this reference page.

Definitions

A BEA Tuxedo domain is defined as the environment described in a single TUXCONFIG file. In BEA Tuxedo terminology, a domain is the same as an application—a business application.

There is one Domains administrative server (DMADM) process running in each BEA Tuxedo domain involved in a Domains configuration. The DMADM is the administrative server for all domain gateway groups running in a particular BEA Tuxedo domain.

A domain gateway group consists of a BEA Tuxedo system gateway administrative server (GWADM) process and a BEA Tuxedo system domain gateway process.

A BEA Tuxedo system domain gateway process provides communication services with a specific type of transaction processing (TP) domain; for example, the GWTOPEND process enables BEA Tuxedo applications to communicate with BEA TOP END applications. A domain gateway relays requests to another domain and receives replies.

A local domain access point is a user-specified logical name representing a set of services of the BEA Tuxedo domain that is made available to other domains (remote domains). A local domain access point maps to a domain gateway group; both terms are used as synonyms.

A remote domain access point is a user-specified logical name representing a set of services of a remote domain that is made available to the local domain. The remote domain may be another BEA Tuxedo application or an application running on another TP system, such as the BEA TOP END system.

Configuration File Purpose

You use a DMCONFIG file to:

Configuration File Format

The DMCONFIG file is made up of the following specification sections:

Lines in a DMCONFIG file beginning with an asterisk (*) indicate the beginning of a specification section. Each such line contains the name of the section immediately following the *. The asterisk is required when specifying a section name. The DM_LOCAL section must precede the DM_REMOTE section.

Parameters are generally specified by: KEYWORD = value; white space (space or tab character) is allowed on either side of the equal sign (=). This format sets KEYWORD to value. Valid keywords are described below within each section.

Lines beginning with the reserved word DEFAULT contain parameter specifications that apply to all lines that follow them in the section in which they appear. Default specifications can be used in all sections. They can appear more than once in the same section. The format for these lines is:

DEFAULT: [KEYWORD1 = value1 [KEYWORD2 = value2 [...]]]

The values set on this line remain in effect until reset by another DEFAULT line, or until the end of the section is reached. These values can also be overridden on non-DEFAULT lines by placing the optional parameter setting on the line. If on a non-DEFAULT line, the parameter setting is valid for that line only; lines that follow revert to the default setting. If DEFAULT appears on a line by itself, all previously set defaults are cleared and their values revert to the system defaults.

If a value is numeric, standard C notation is used to denote the base, that is, 0x prefix for base 16 (hexadecimal), 0 prefix for base 8 (octal), and no prefix for base 10 (decimal). The range of values acceptable for a numeric parameter are given under the description of that parameter.

If a value is an identifier (a string value already known to the BEA Tuxedo Domains component such as TOPEND for the TYPE parameter), standard C rules are typically used. A standard C identifier starts with an alphabetic character or underscore and contains only alphanumeric characters or underscores. The maximum allowable length of an identifier is 30 bytes (not including the terminating NULL).

There is no need to enclose an identifier in double quotes. A value that is neither an integer number nor an identifier must be enclosed in double quotes.

Input fields are separated by at least one space (or tab) character.

"#" introduces a comment. A new line ends a comment.

Blank lines and comments are ignored.

Comments can be freely attached to the end of any line.

Lines are continued by placing at least one tab after the new line. Comments cannot be continued.

Domains Terminology Improvements

For BEA Tuxedo release 7.1 or later, the Domains MIB uses improved class and attribute terminology to describe the interaction between local and remote domains. The improved terminology has been applied to the DMCONFIG(5) and DMCONFIG for GWTOPEND(5) reference pages, section names, parameter names, and error messages, and to the DM_MIB(5) reference page, classes, and error messages.

For backwards compatibility, aliases are provided between the DMCONFIG terminology used prior to BEA Tuxedo 7.1 and the improved Domains MIB terminology. For BEA Tuxedo release 7.1 or later, both versions of DMCONFIG terminology are accepted. The following table shows the mapping of the previous and improved terminology for the DMCONFIG file.

For BEA Tuxedo release 7.1 or later, the dmunloadcf command generates by default a DMCONFIG file that uses the improved domains terminology. Use the -c option to print a DMCONFIG file that uses the previous domains terminology. For example:

prompt> dmunloadcf -c > dmconfig_prev