PURPOSE
dmconfig - TUXEDO System/T ASCII domain
configuration file
DESCRIPTION
dmconfig is the ASCII version of a TUXEDO
System/Domain domain configuration file; it is also referred to
by its environmental variable name: DMCONFIG. The dmconfig
file is parsed and loaded into a binary version by the dmloadcf(1)
utility. The binary configuration file, called the BDMCONFIG
file, contains information used by domain gateways to initialize
the context required for communications with other domains. dmadmin(1) uses
the binary file (or a copy of it) in its monitoring activity.
There will be one BDMCONFIG file for each TUXEDO
System/Domain application that uses the /Domain feature.
A DMCONFIG file, and its binary BDMCONFIG
counterpart, are analogous to the UBBCONFIG and TUXCONFIG
files of a non-/Domain System/T application. The DMCONFIG
file extends the definition of a non-/Domain System/T application
so that the application becomes a domain.
Definitions
A TUXEDO System/Domain Application is defined as
the environment described in a single TUXCONFIG file.
A System/T Application can communicate with another System/T
Application or with another TP Application via a domain gateway
group. In ``TUXEDO System/Domain'' terms, an Application
is the same as a TP Domain.
A Gateway Group is a collection of domain gateway
processes that provide communication services with a specific
type of TP Domain.
A Domain Gateway is a TUXEDO System/Domain process
that relays requests and replies to another TP Domain.
A Local Domain characterizes a part of the
application (set or subset of services) that is made available to
other domains. A Local Domain is always represented by a Domain
Gateway Group, and both terms are used as synonyms.
A Remote Domain is a remote application that is
accessed through a Gateway Group. The remote application may be
another TUXEDO System/Domain application or an application
running under another TP system.
A Remote Service is a service provided by a remote
domain that is made available to the local application through a
Gateway Group.
A Local Service is a service of a local domain that
is made available to remote domains through a Gateway Group.
Configuration File Format
The format of a domain configuration file is as follows:
- The file is made up of eight possible
specification sections. Lines beginning with an
asterisk (*) indicate the beginning of
a specification section. Each such line contains
the name of the section immediately following the
*. Allowable section names are: DM_LOCAL_DOMAINS,
DM_REMOTE_DOMAINS, DM_LOCAL_SERVICES,
DM_REMOTE_SERVICES, DM_ROUTING,
DM_ACCESS_CONTROL and DM_domtype,
where domtype is either OSITP, SNAX
or TDOMAIN. (This manual page
describes only how to configure a domain of type TDOMAIN.
See BEA Connect documentation for information
about how to configure an OSITP or an SNAX
domain) The DM_LOCAL_DOMAINS section
must precede the
DM_REMOTE_DOMAINS
section.
- Parameters are generally specified by: KEYWORD
= value. This sets KEYWORD to value.
Valid keywords are described below within each
section. KEYWORDs are reserved; they can
not be used as values unless they are
quoted.
- Lines beginning with the reserved word, DEFAULT:,
contain parameter specifications that apply to
any 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, standard C
rules are used. An identifier must start
with an alphabetic character or underscore and
contain only alphanumeric characters or
underscores. The maximum allowable length of an
identifier is 30 (not including the terminating
null). An identifier cannot be the same as any KEYWORD.
- A value that is neither an integer number or an
identifier must be enclosed in double quotes.
- Input fields are separated by at least one space
(or tab) character.
- "#" introduces a comment. A
newline 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 newline. Comments can not be continued.
- VERSION=string_value
where string_value can be any value. The field
is not checked by the software; it is provided simply as
a place where the customer can enter a string that may
have some documentation value to the application.
The DM_LOCAL_DOMAINS Section
This section identifies local domains and their associated
gateway groups. The section must have an entry for each gateway
group (Local Domain). Each entry specifies the parameters
required for the domain gateway processes running in that group.
Entries have the form:
LDOM required parameters [optional parameters]
where LDOM is an identifier
value used to locally name each local domain. LDOM must be
unique within a particular configuration. As you will see in the
description of the *DM_LOCAL_SERVICES section, LDOM is the
identifier that connects the local services with a particular
gateway group.
The following are the required parameters:
-
- GWGRP = identifier
- specifies the name of the gateway server group (the name
provided in the TUXCONFIG file) representing
this local domain. There is a one-to-one relationship
between a DOMAINID (see below) and the name of the
gateway server group.
- TYPE = identifier
- is used for grouping local domains into classes. TYPE
can be set to one of the following values: TDOMAIN,
SNAX or OSITP. The TDOMAIN
value indicates that this local domain can only
communicate with another TUXEDO System/Domain. The OSITP
value indicates that this local domain communicates with
another TP Domain via the OSI-TP protocol. The SNAX
value indicates that this local domain communicates with
another TP Domain via SNA protocol.
- DOMAINID = string
- is used to identify the local domain. DOMAINID
must be unique across both local and remote domains. The
value of string can be a sequence of characters
(for example, "BA.CENTRAL01"), or a sequence of
hexadecimal digits preceded by "0x" (for
example, "0x0002FF98C0000B9D6D").
DOMAINID
must be 32 octets or fewer in length. If the value is a
string, it must be 32 characters or fewer (counting the
trailing null).
Optional parameters describe resources and limits used in the
operation of domain gateways:
-
- AUDITLOG = string
- specifies the name of the audit log file for this local
domain. The audit log feature is activated from the dmadmin(1)
command and records all the operations within this local
domain. If the audit log feature is active and this
parameter is not specified, the file DMmmddyy.LOG
(where mm=month, dd=day, and yy=year)
is created in the directory specified by the $APPDIR
environment variable or the APPDIR keyword of
the *MACHINES section of the TUXCONFIG file.
- BLOCKTIME = numeric
- specifies the maximum wait time allowed for a blocking
call. The value sets a multiplier of the SCANUNIT
parameters specified in the TUXCONFIG file.
The value SCANUNIT * BLOCKTIME must be greater
than or equal to SCANUNIT and less than 32,768
seconds. If this parameter is not specified, the default
value is set to the value of the BLOCKTIME
parameter specified in the TUXCONFIG file. A
timeout always implies a failure of the affected request.
Notice that the timeout specified for transactions in the
TUXCONFIG will always be used when the request
is issued within a transaction.
- DMTLOGDEV = string
- specifies the TUXEDO filesystem that contains the Domain
transaction log (DMTLOG) for this machine. The
DMTLOG is stored as a TUXEDO System VTOC table
on the device. If this parameter is not specified, the
domain gateway group is not allowed to process requests
in transaction mode. Local domains running on the same
machine can share the same DMTLOGDEV
filesystem, but each local domain must have its own log
(a table in the DMTLOGDEV) named as specified
by the DMTLOGNAME keyword (see below).
- DMTLOGNAME = identifier
- specifies the name of the domain transaction log for this
domain. This name must be unique when the same DMTLOGDEV
is used for several local domains. If not specified, the
default is the string ``DMTLOG''. The name
must be 30 characters or less.
- DMTLOGSIZE = numeric
- specifies the numeric size, in pages, of the Domain
transaction log for this machine. It must be greater than
0 and less than the amount of available space on the
TUXEDO filesystem. If not specified, the default is 100
pages.
- MAXDATALEN = numeric
- specifies a maximum amount of data (in bytes) that can be
sent to or from any services advertised by this local
domain. There is no limit if this parameter is not
specified.
- MAXRDOM = numeric
- specifies the maximum number of connections (or dialogues
if the domain is of type OSITP) allowed per
gateway. There is no limit if this parameter is not
specified.
- MAXRDTRAN = numeric
- specifies the maximum number of domains that can be
involved in a transaction. It must be greater than 0 and
less than 32,768. If not specified, the default is 16.
- MAXTRAN = numeric
- specifies the maximum number of simultaneous global
transactions allowed on this local domain. It must be
greater than or equal to 0 and less than or equal to the MAXGTT
parameter specified in the TUXCONFIG file. If
not specified, the default is the value of MAXGTT.
- SECURITY = value
- specifies the type of application security to be
enforced. The SECURITY parameter currently has
three valid values: NONE, APP_PW or DM_PW.
The value NONE indicates that no security is
used. This is the default. The value APP_PW
indicates that the application password security is to be
enforced when a connection is established from a remote
domain. The application password should be defined in the
TUXCONFIG file. The value DM_PW
indicates that domain password security is to be enforced
when a connection is established from a remote domain.
Domain passwords must be defined through the dmadmin(1)
command. This option does not apply to domains of type OSITP.
- MTYPE = value
- is used for grouping domains so that encoding/decoding of
messages between domains can be bypassed. If MTYPE
is not specified, the default is to turn
encoding/decoding on. If the value set for the MTYPE
field is the same in both the DM_LOCAL_DOMAINS
and DM_REMOTE_DOMAINS sections of a domain
configuration file, data encoding/decoding is bypassed.
The value set for MTYPE can be any
string value up to 15 characters in length. It is used
only for comparison.
The DM_REMOTE_DOMAINS Section
This section identifies the known set of remote domains and
their characteristics.
Entries have the form:
RDOM required parameters [optional parameters]
where RDOM is an identifier
value used to identify each remote domain known to this
configuration. RDOM must be unique within the
configuration.
The TYPE and DOMAINID parameters are
required:
-
- TYPE = identifier
- is used for grouping remote domains into classes. TYPE
can be set to one of the following values: TDOMAIN,
SNAX, or OSITP. The TDOMAIN
value indicates that this local domain can only
communicate with another TUXEDO System Domain. The OSITP
value indicates that this local domain communicates with
another TP Domain via the OSI-TP protocol. The SNAX
value indicates that this local domain communicates with
another TP Domain via SNA protocol.
- DOMAINID = string
- is used to identify a remote domain. DOMAINID
must be 32 octets or fewer in length. If the value is a
string, it must be 32 characters or fewer (counting the
trailing null). DOMAINID must be unique across
remote domains. The value of string can be a
sequence of characters or a sequence of hexadecimal
digits preceded by "0x".
- MTYPE = value
- is used for grouping domains so that encoding/decoding of
messages between domains can be bypassed. If MTYPE
is not specified, the default is to turn
encoding/decoding on. If the value set for the MTYPE
field is the same in both the DM_LOCAL_DOMAINS
and the DM_REMOTE_DOMAINS section of a domain
configuration file, data encoding/decoding is bypassed.
The value set for MTYPE can be any
string value. It is used only for comparison.
The DM_TDOMAIN Section
This section defines the addressing information required by
domains of type TDOMAIN. This section should have an
entry per local domain if requests from remote domains to local
services are accepted on that local domain (gateway group), and
an entry per remote domain accessible by the defined local
domains.
Entries have the form:
DOM required parameters [optional parameters]
where DOM is an identifier
value used to identify either a local domain (LDOM) or
a remote domain (RDOM) in the *DM_LOCAL_DOMAINS
section or in the *DM_REMOTE_DOMAINS section. The DOM
identifier must match a previously defined LDOM in the
*DM_LOCAL_DOMAINS section or RDOM in the
*DM_REMOTE_DOMAINS section.
The following parameter is required:
-
- NWADDR = string
- This parameter specifies the network address associate
with a local domain or a remote domain. If the
association is with a local domain, the NWADDR
is used to accept connections from other TUXEDO System/T
Domains. If the association is with a remote domain, the NWADDR
is used to initiate a connection. Specifies the network
address to be used by the WSL process as its listening
address. The listening address for a WSL is the means by
which it is contacted by workstation client processes
participating in the application. If string has
the form ``0xhex-digits'' or ``\\xhex-digits'',
it must contain an even number of valid hex digits. These
forms are translated internally into a character array
containing TCP/IP addresses may also be in either of the
following two forms:
"//host.name:port_number"
"//#.#.#.#:port_number"
In the first of these formats, hostname is
resolved to a TCP/IP host address at the time the address
is bound using the locally configured name resolution
facilities accessed via gethostbyname(3c). The "#.#.#.#"
is the dotted decimal format where each #
represents a decimal number in the range 0 to 255. Port_number
is a decimal number in the range 0 to 65535. the
hexadecimal representations of the string specified. This
parameter specifies the network address used by a local
or a remote domain to accept connections from other
TUXEDO System/Domain Domains. If string has the
form ``0xhex-digits'', it must contain an even
number of valid hexadecimal digits.
The following parameters are optional:
-
- NWDEVICE = string
- Specifies the device file name to be used when binding to
the listening address of a local or a remote domain. In
Release 6.4 (or higher) the NWDEVICE parameter
is never required. In prior releases, if the networking
functionality is TLI-based, the device name must be an
absolute pathname. If the networking functionality is
Sockets-based, this parameter does not need to be
specified.
- CMPLIMIT = numeric
- This parameter specifies the compression threshold to be
used when sending data to the remote domain. Application
buffers larger than this size will be compressed. This
attribute defaults to 2,147,483,647.
- MINENCRYPTBITS={0|40|128}
- When establishing a network link for this domain, require
at least this minimum level of encryption. "0"
means no encryption, while "40" and
"128" specify the encryption key length (in
bits). If this minimum level of encryption cannot be met,
link establishment will fail. The default value is
"0".
- MAXENCRYPTBITS={0|40|128}
- When establishing a network link, negotiate encryption up
to this level. "0" means no encryption, while
"40" and "128" specify the encryption
length (in bits). The default value is "128"
Entries associated with a remote domain can be specified more
than once. The first one specified is considered to be the
primary address, which means it is the first one tried when a
connection is being attempted to a remote domain. If a network
connection cannot be established using the primary entry's NWADDR,
the NWADDR associated with the secondary entry is
used.
If this /TDOMAIN is a local domain (that is, if DOM
matches a previously specified LDOM), then NWADDRs
are network addresses to be used to listen for incoming
connections. A secondary entry cannot be used for local domain
entries.
If this /TDOMAIN entry points to a secondary remote domain
(that is, DOM matches a previously specified RDOM ),
then the entry points to a gateway that is only used when a
network connection cannot be established using the primary
entry's NWADDR. The secondary remote gateway must
reside in a different TUXEDO Domain from the primary. However,
the secondary gateway must have the same DOMAINID
defined in its DM_LOCAL_DOMAINS section as the primary
remote gateway; this arrangement is often referred to as a
"mirrored" gateway. This feature is not recommended for
use with transactions or conversations. In addition, the mirrored
gateway is not recommended for use (for example, by local
clients) when the primary gateway is available.
The DM_ACCESS_CONTROL Section
This section specifies the access control lists used by local
domain. Lines in this section are of the form:
ACL_NAME required parameters
where ACL_NAME is a (identifier)
name used to identify a particular access control list and it
must be 15 characters or less in length.
Required parameters are:
- ACLIST = identifier [,identifier]
- where an ACLIST is composed of one or more
remote domain names (RDOM) separated by
commas. The wildcard character (*) can be used to specify
that all the remote domains defined in the
*DM_REMOTE_DOMAINS section can access a local domain.
The DM_LOCAL_SERVICES Section
This section provides information on the services exported by
each local domain. This section is optional and if it is not
specified then all local domains defined in the *DM_LOCAL_DOMAINS
section accept requests to all of the services advertised by the
TUXEDO System/Domain application. If this section is defined then
it should be used to restrict the set of local services that can
be requested from a remote domain.
Lines within this section have the form: service
[optional parameters] where service is the (identifier)
local name of the exported service, and it must be 15 characters
or fewer in length. This name corresponds to a name advertised by
one or more servers running with the local TUXEDO System/Domain
application. Notice that exported services inherit the default or
special properties specified for the service in an entry in the SERVICES
section of the TUXCONFIG file. Some of the special
properties are: LOAD, PRIO, AUTOTRAN,
ROUTING, BUFTYPE, and TRANTIME.
Optional parameters are:
- ACL = identifier
- specifies the name of the access control list (ACL) to be
used by the local domain to restrict requests made to
this service by remote domains. The name of the ACL is
defined in the *DM_ACCESS_CONTROL section. If this
parameter is not specified then access control will not
be performed for requests to this service.
- LDOM = identifier
- specifies the name identifying the local domain exporting
this service. If this keyword is not specified then all
the local domains defined in the *DM_LOCAL_DOMAINS
section will accept requests to this local service.
- INBUFTYPE = type[:subtype]
- restricts the buffer type naming space of data types
accepted by this service to a single buffer type. This
parameter should be defined when the service is going to
be used from an OSITP type gateway that uses
the UDT ASE Application Context. It does not apply to
/TDOMAIN.
- OUTBUFTYPE = type[:subtype]
- restricts the buffer type naming space of data types
returned by this service to a single buffer type. This
parameter should be defined when the service is going to
be used from an OSITP type gateway that uses
the UDT ASE Application Context. The FML
buffer type cannot be used for OSITP type
gateways. It does not apply to /TDOMAIN.
- RNAME = string
- specifies the name exported to remote domains. This name
will be used by the remote domains for request to this
service. If this parameter is not specified, the local
service name is supposed to be the name used by any
remote domain.
The DM_REMOTE_SERVICES Section
This section provides information on services
"imported" and available on remote domains. Lines
within this *DM_REMOTE_SERVICES section have the form: service
[optional parameters] where service is the (identifier)
name used by the local TUXEDO System/Domain application for a
particular remote service. Remote services are associated with a
particular remote domain.
Optional parameters are:
- CONV = { Y | N }
- specifies whether (Y) or not (N)
the remote service is a conversational service. The
default value is N.
- LDOM = identifier
- specifies the name of a local domain in charge of routing
requests to this remote service. The gateway group
associated with the local domain advertises service
in the TUXEDO System/Domain Bulletin Board. If this
parameter is not specified then all the local domains
will be able to accept requests to this remote service.
The service request will be then redirected to a remote
domain of the same type (see RDOM keyword
below).
- INBUFTYPE = type[:subtype]
- restricts the buffer type naming space of data types
accepted by this service to a single buffer type. This
parameter should be defined when the service is going to
be used from an OSITP type gateway that uses
the UDT ASE Application Context. The FML
buffer type cannot be used for OSITP type
gateways. It does not apply to /TDOMAIN.
- OUTBUFTYPE = type[:subtype]
- restricts the buffer type naming space of data types
returned by this service to a single buffer type. This
parameter should be defined when the service is going to
be used from an OSITP type gateway that uses
the UDT ASE Application Context. The FML
buffer type cannot be used for OSITP type
gateways. It does not apply to /TDOMAIN.
- RDOM = identifier
- specifies the name of the remote domain responsible for
the actual execution of this service. If this parameter
is not specified and a routing criteria (see below ROUTING
keyword) is not specified, then the local domain assumes
that any remote domain of the same type accepts this
service and it selects a known domain (a domain to which
a connection already exists) or remote domain from the
&*;DM_REMOTE_DOMAINS section.
- RNAME = string
- specifies the actual service name expected by the remote
domain. If this parameter is not specified, the remote
service name is the same as the name specified in service.
- ROUTING = identifier
- when more than one remote domain offers the same service,
a local domain can perform data dependent routing if this
optional parameter is specified. The identifier
specifies the name of the routing criteria used for this
data dependent routing. If not specified, data dependent
routing is not done for this service. identifier
must be 15 characters or less in length. If multiple
entries exist for the same service name but with
different RDOM parameters, the ROUTING
parameter should be the same for all of these entries.
- TRANTIME = integer
- specifies the default timeout value in seconds for a
transaction automatically started for the associated
service. The value must be greater than or equal to 0 and
less than 2147483648. The default is 30 seconds. A value
of 0 implies the maximum timeout value for the machine.
The DM_ROUTING Section
This section provides information for data dependent routing
of service requests using FML, VIEW, X_C_TYPE,
and X_COMMON typed buffers. Lines within the DM_ROUTING
section have the form: CRITERION_NAME required parameters
where CRITERION_NAME is the (identifier) name of
the routing entry that was specified on the services entry. CRITERION_NAME
must be 15 characters or less in length.
Required parameters are:
- FIELD = identifier
- specifies the name of the routing field. It must be 30
characters or less. This field is assumed to be a field
name that is identified in an FML field table
(for FML buffers) or an FML view
table (for VIEW, X_C_TYPE, or X_COMMON
buffers). The FLDTBLDIR and FIELDTBLS
environment variables are used to locate FML
field tables, and the VIEWDIR and VIEWFILES
environment variables are used to locate FML
view tables. If a field in an FML32 buffer
will be used for routing, it must have a field number
less than or equal to 8191.
- RANGES = string
- specifies the ranges and associated remote domain names (RDOM)
for the routing field. string must be enclosed in
double quotes. The format of string is a
comma-separated ordered list of range/RDOM pairs (see EXAMPLES
below). A range is either a single value (signed numeric
value or character string in single quotes), or a range
of the form ``lower - upper'' (where lower and upper are
both signed numeric values or character strings in single
quotes). Note that ``lower'' must be less than or equal
to ``upper''. To embed a single quote in a character
string value (as in O'Brien, for example), it
must be preceded by two backslashes ('O\\'Brien').
The value MIN can be used to indicate the
minimum value for the data type of the associated FIELD;
for strings and carrays, it is the null string; for
character fields, it is 0; for numeric values, it is the
minimum numeric value that can be stored in the field.
The value MAX can be used to indicate the
maximum value for the data type of the associated FIELD;
for strings and carrays, it is effectively an unlimited
string of octal-255 characters; for a character field, it
is a single octal-255 character; for numeric values, it
is the maximum numeric value that can be stored in the
field. Thus, ``MIN - -5'' is all numbers less
than or equal to -5 and ``6 - MAX'' is all
numbers greater than or equal to 6. The meta-character ``*''
(wild-card) in the position of a range indicates any
values not covered by the other ranges previously seen in
the entry; only one wild-card range is allowed per entry
and it should be last (ranges following it will be
ignored). The routing field can be of any data type
supported in FML. A numeric routing field must
have numeric range values and a string routing field must
have string range values. String range values for string,
carray, and character field types must be placed inside a
pair of single quotes and can not be preceded by a sign.
Short and long integer values are a string of digits,
optionally preceded by a plus or minus sign. Floating
point numbers are of the form accepted by the C compiler
or atof(): an optional sign, then a string of
digits optionally containing a decimal point, then an
optional e or E followed by an optional sign or space,
followed by an integer. When a field value matches a
range, the associated RDOM value specifies the
remote domain to which the request should be routed. A RDOM
value of ``*'' indicates that the request can
go to any remote domain known by the gateway group.
Within a range/RDOM pair, the range is
separated from the RDOM by a ``:''.
- BUFTYPE = ~type1[:subtype1[,subtype2
. . . ]][;type2[:subtype3[, . . . ]]] . . .~
- is a list of types and subtypes of data buffers for which
this routing entry is valid. The types are restricted to
be either FML, VIEW, X_C_TYPE, or X_COMMON.
No subtype can be specified for type FML and
subtypes are required for the other types (``*'' is not
allowed). Duplicate type/subtype pairs can not be
specified for the same routing criterion name; more than
one routing entry can have the same criterion name as
long as the type/subtype pairs are unique. This parameter
is required. If multiple buffer types are specified for a
single routing entry, the data types of the routing field
for each buffer type must be the same.
If the field value is not set (for FML buffers), or
does not match any specific range and a wild-card range has not
been specified, an error is returned to the application process
that requested the execution of the remote service.
FILES
The BDMCONFIG environment variable is used to find
the BDMCONFIG configuration file.
EXAMPLE1
The following configuration file defines a 5-site domain
configuration. The example shows 4 Bank Branch domains
communicating with a Central Bank Branch. Three of the Bank
Branches run within other TUXEDO System/Domain domains. The
fourth Branch runs under the control of another TP Domain and
OSI-TP is used in the communication with that domain. The example
shows the TUXEDO System/Domain Domain configuration file from the
Central Bank point of view. In the *DM_TDOMAIN section
this example shows a mirrored gateway for b01.
# TUXEDO DOMAIN CONFIGURATION FILE FOR THE CENTRAL BANK
#
#
*DM_LOCAL_DOMAINS
# <local domain name> <Gateway Group name> <domain type> <domain id> <log device>
# [<audit log>] [<blocktime>]
# [<log name>] [<log offset>] [<log size>]
# [<maxrdom>] [<maxrdtran>] [<maxtran>]
# [<maxdatalen>] [<security>]
# [<tuxconfig>] [<tuxoffset>]
#
#
DEFAULT: SECURITY = NONE
c01 GWGRP = bankg1
TYPE = TDOMAIN
DOMAINID = "BA.CENTRAL01"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
DMTLOGNAME = "DMTLG_C01"
c02 GWGRP = bankg2
TYPE = OSITP
DOMAINID = "BA.CENTRAL01"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
DMTLOGNAME = "DMTLG_C02"
NWDEVICE = "OSITP"
URCH = "ABCD"
#
*DM_REMOTE_DOMAINS
#<remote domain name> <domain type> <domain id>
#
b01 TYPE = TDOMAIN
DOMAINID = "BA.BANK01"
b02 TYPE = TDOMAIN
DOMAINID = "BA.BANK02"
b03 TYPE = TDOMAIN
DOMAINID = "BA.BANK03"
b04 TYPE = OSITP
DOMAINID = "BA.BANK04"
URCH = "ABCD"
#
*DM_TDOMAIN
#
# []
#
# Local network addresses
c01 NWADDR = "//newyork.acme.com:65432" NWDEVICE ="/dev/tcp"
c02 NWADDR = "//192.76.7.47:65433" NWDEVICE ="/dev/tcp"
# Remote network addresses: second b01 specifies a mirrored gateway
b01 NWADDR = "//192.11.109.5:1025" NWDEVICE = "/dev/tcp"
b01 NWADDR = "//194.12.110.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
#
#<local or remote domain name> <apt> <aeq>
# [<aet>] [<acn>] [<apid>] [<aeid>]
# [<profile>]
#
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_LOCAL_SERVICES
#<service_name> [<Local Domain name>] [<access control>] [<exported svcname>]
# [<inbuftype>] [<outbuftype>]
#
open_act ACL = branch
close_act ACL = branch
credit
debit
balance
loan LDOM = c02 ACL = loans
*DM_REMOTE_SERVICES
#<service_name> [<Remote domain name>] [<local domain name>]
# [<remote svcname>] [<routing>] [<conv>]
# [<trantime>] [<inbuftype>] [<outbuftype>]
#
tlr_add LDOM = c01 ROUTING = ACCOUNT
tlr_bal LDOM = c01 ROUTING = ACCOUNT
tlr_add RDOM = b04 LDOM = c02 RNAME ="TPSU002"
tlr_bal RDOM = b04 LDOM = c02 RNAME ="TPSU003"
*DM_ROUTING
# <routing criteria> <field> <typed buffer> <ranges>
#
ACCOUNT FIELD = branchid BUFTYPE ="VIEW:account"
RANGES ="MIN - 1000:b01, 1001-3000:b02, *:b03"
*DM_ACCESS_CONTROL
#<acl name> <Remote domain list>
#
branch ACLIST = b01, b02, b03
loans ACLIST = b04
EXAMPLE2
This example shows the TUXEDO System Domain
Configuration file required at one of the Bank Branches (BANK01).
#
#TUXEDO DOMAIN CONFIGURATION FILE FOR A BANK BRANCH
#
#
*DM_LOCAL_DOMAINS
#
b01 GWGRP = auth
TYPE = TDOMAIN
DOMAINID = "BA.BANK01"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
*DM_REMOTE_DOMAINS
#
c01 TYPE = TDOMAIN
DOMAINID = "BA.CENTRAL01"
*DM_TDOMAIN
#
b01 NWADDR = "//192.11.109.5:1025" NWDEVICE = "/dev/tcp"
c01 NWADDR = "//newyork.acme.com:65432" NWDEVICE = "/dev/tcp"
*DM_LOCAL_SERVICES
#
tlr_add ACL = central
tlr_bal ACL = central
*DM_REMOTE_SERVICES
#
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 /T domain 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 /T domain 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 specified by the -l option could 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.18
is translated into a hexadecimal number. Thus 155
becomes 9B, 2 becomes 02, and so
on.
SEE ALSO
build_dgw(1),
dmadmin(1),
dmloadcf(1),
dmunloadcf(1)
tmboot(1),
tmshutdown(1),
dmgwopts(5),
GWADM(5),
DMADM(5),
BEA TUXEDO /Domain Guide,
BEA TUXEDO Administrator's Guide