File Formats, Data Descriptions, MIBs, and System Processes Reference
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This section, also known as the DM_LOCAL_DOMAINS
section, defines one or more local domain access point identifiers and their associated gateway groups. The section must have a local domain access point entry for each active gateway group defined in the UBBCONFIG
file. Each entry specifies the parameters required for the domain gateway process running in that group.
Entries within the DM_LOCAL
section have the following form:
LocalAccessPoint
required_parameters
[optional_parameters
]
where LocalAccessPoint is the local domain access point identifier (logical name) that you choose to represent a particular gateway group defined in the UBBCONFIG
file. LocalAccessPoint must be unique across the local and remote domains involved in a Domains configuration. As you will see in the description of the DM_EXPORT
section, you use the local domain access point to associate local services with the gateway group. The local services available through the local domain access point will be available to clients in one or more remote domains.
Specifies the name of the domain gateway group (the name provided in the GROUPS
section of the TUXCONFIG
file) representing this local domain access point. There is a one-to-one relationship between a local domain access point and a domain gateway group.
Specifies the type of domain gateway associated with this local domain access point. TYPE
can be set to one of the following values: TDOMAIN
, SNAX
, OSITP
, or OSITPX
.
The TDOMAIN
value indicates that this local domain access point is associated with a GWTDOMAIN
gateway instance and therefore can communicate with another BEA Tuxedo application.
The SNAX
value indicates that this local domain access point is associated with a GWSNAX
gateway instance and therefore can communicate with another TP domain via the SNA protocol.
The OSITP
or OSITPX
value indicates that this local domain access point is associated with a GWOSITP
gateway instance and therefore can communicate with another TP domain via the OSI TP protocol. The OSITP
value indicates the use of the OSI TP 1.3 protocol, and the OSITPX
value indicates the use of the OSI TP 4.0 or later protocol. The OSITPX
value is supported only by BEA Tuxedo 8.0 or later software.
Domain types must be defined in the DMTYPE
file: %TUXDIR%\udataobj\DMTYPE
for Windows or $TUXDIR/udataobj/DMTYPE
for UNIX.
Used to identify the domain gateway group associated with this local domain access point for purposes of security when setting up connections to remote domains. ACCESSPOINTID
must be unique across all local and remote domain access points.
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, "0x0002FF98C0000B9D6
"). ACCESSPOINTID
must be 30 bytes or fewer in length. If the value is a string, it must be 30 characters or fewer (counting the trailing NULL).
The following optional parameters for the DM_LOCAL
section describe resources and limits used in the operation of domain gateways:
AUDITLOG
=
string
[1..256] (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Specifies the name of the audit log file for this local domain access point. The audit log feature is activated from the dmadmin(1) command and records all the operations for this local domain access point. If the audit log feature is active and this parameter is not specified, the file DM
mmddyy
.LOG
(where mm
=month, dd
=day, and yy
=year) is created in the directory specified by the $APPDIR
environment variable or the APPDIR
parameter of the MACHINES
section of the TUXCONFIG
file.
Specifies the maximum wait time allowed for a blocking call for this local domain access point. The value is a multiplier of the SCANUNIT
parameters specified in the RESOURCES
section of 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 is set to the value of the BLOCKTIME
parameter specified in the RESOURCES
section of the TUXCONFIG
file. A blocking timeout condition implies that the affected service request has failed.
Be aware that interdomain transactions generate blocking timeout conditions when transaction duration exceeds BLOCKTIME
. That is, for an interdomain transaction, if the BLOCKTIME
value is less than (a) the TRANTIME
timeout value specified in the SERVICES
section of the TUXCONFIG
file or (b) the timeout value passed in a tpbegin()
call to start the transaction, the timeout for the transaction is reduced to the BLOCKTIME
value. In contrast, for intradomain transactions (that is, transactions handled within a single BEA Tuxedo domain), the BLOCKTIME
value specified in the RESOURCES
section of the TUXCONFIG
file has no effect on the timeout of an intradomain transaction.
CONNECTION_POLICY
=
{ON_DEMAND
| ON_STARTUP
| INCOMING_ONLY
}
Specifies the conditions under which the domain gateway associated with this local domain access point tries to establish connections to remote domains. Supported values are ON_DEMAND
, ON_STARTUP
, or INCOMING_ONLY
. This parameter applies only to domain gateways of type TDOMAIN
.
A connection policy of ON_DEMAND
means that a domain gateway attempts to establish a connection with a remote domain only when requested by either a client request to a remote service or a dmadmin(1)
connect
command. The default for CONNECTION_POLICY
is ON_DEMAND
. Connection retry processing is not allowed when the connection policy is ON_DEMAND
.
A connection policy of ON_STARTUP
means that a domain gateway attempts to establish a connection with its remote domains at gateway server initialization time. If CONNECTION_POLICY
is set to ON_STARTUP
, the remote services for a particular remote domain (that is, services advertised by the domain gateway) are advertised only if a connection is successfully established to the remote domain. Thus, if there is no active connection to the remote domain, the remote services are suspended. By default, this connection policy retries failed connections every 60 seconds, but you can specify a different value for this interval using the RETRY_INTERVAL
parameter. Also, see the MAXRETRY
parameter.
A connection policy of INCOMING_ONLY
means that a domain gateway does not attempt an initial connection upon startup and that remote services are initially suspended. The domain gateway is available for incoming connections from remote domains, and remote services are advertised when the domain gateway receives an incoming connection or an administrative connection (using the dmadmin(1)
connect
command) is made. Connection retry processing is not allowed when the connection policy is INCOMING_ONLY
.
Specifies the number of times that the domain gateway associated with this local domain access point tries to establish connections to remote domains. This parameter applies only to domain gateways of type TDOMAIN
and is valid only when the CONNECTION_POLICY
parameter for this local domain access point is set to ON_STARTUP
. For other connection policies, automatic retries are disabled.
The minimum value for MAXRETRY
is 0, and the maximum value is MAXLONG
(2147483647). MAXLONG
, the default, indicates that retry processing will be repeated indefinitely, or until a connection is established. Setting MAXRETRY=0
turns off the automatic retry mechanism.
Specifies the number of seconds that the domain gateway associated with this local domain access point waits between automatic attempts to establish a connection to remote domains. This parameter applies only to domain gateways of type TDOMAIN
and is valid only when the CONNECTION_POLICY
parameter for this local domain access point is set to ON_STARTUP
. For other connection policies, automatic retries are disabled.
The minimum value for RETRY_INTERVAL
is 0, and the maximum value is 2147483647. The default is 60. If MAXRETRY
is set to 0, setting RETRY_INTERVAL
is not allowed.
Specifies the connection principal name identifier, which is the principal name for verifying the identity of the domain gateway associated with this local domain access point when establishing a connection to a remote domain. This parameter applies only to domain gateways of type TDOMAIN
running BEA Tuxedo 7.1 or later software.
The CONNECTION_PRINCIPAL_NAME
parameter may contain a maximum of 511 characters (excluding the terminating NULL character). If this parameter is not specified, the connection principal name defaults to the ACCESSPOINTID
string for this local domain access point.
For default authentication plug-ins, if a value is assigned to the CONNECTION_PRINCIPAL_NAME
parameter for this local domain access point, it must be the same as the value assigned to the ACCESSPOINTID
parameter for this local domain access point. If these values do not match, the local TDomain gateway process will not boot, and the system will generate the following userlog(3c) message: ERROR: Unable to acquire credentials
.
DMTLOGDEV
=
string
[1..256] (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Specifies the BEA Tuxedo filesystem that contains the Domains transaction log (TLOG
) for this local domain access point. The TLOG
is stored as a BEA Tuxedo system VTOC table on the device. If this parameter is not specified, the domain gateway group associated with this local domain access point is not allowed to process requests in transaction mode. Multiple local domain access points for the same machine can share the same BEA Tuxedo filesystem, but each local domain access point must have its own log (a table in the DMTLOGDEV
) named as specified by the DMTLOGNAME
parameter.
Specifies the name of the TLOG
for this local domain access point. This name must be unique when the same BEA Tuxedo filesystem (as specified in DMTLOGDEV
) is used for several local domain access points. If this parameter is not specified, the default is the string DMTLOG
. The name must be 30 characters or less.
Specifies the numeric size, in pages, of the TLOG
for this local domain access point. It must be greater than 0 and less than the amount of available space on the BEA Tuxedo filesystem. If this parameter is not specified, the default is 100 pages.
Specifies the maximum number of domains that can be involved in a transaction for this local domain access point. It must be greater than 0 and less than 32,768. If this parameter is not specified, the default is 16.
Specifies the maximum number of simultaneous global transactions allowed for this local domain access point. It must be greater than or equal to 0 and less than or equal to the MAXGTT
parameter specified in the RESOURCES
section of the TUXCONFIG
file. If MAXTRAN
is not specified, the default is the value of MAXGTT
.
Used for grouping domains so that encoding/decoding of messages can be bypassed between the machine associated with this local domain access point and the machines associated with the remote domain access points. This parameter applies only to domain gateways of type TDOMAIN
.
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
and the DM_REMOTE
section of a DMCONFIG
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.
Specifies the type of application security to be enforced for this local domain access point. The SECURITY
parameter currently has three valid values for domain gateways of type TDOMAIN
: NONE
, APP_PW
, or DM_PW
. The value NONE
(the default) indicates that no security is used. 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 is defined in the TUXCONFIG
file. The value DM_PW
indicates that Domains password security is to be enforced when a connection is established from a remote domain; Domains passwords are defined through the dmadmin(1) command.
The SECURITY
parameter does not apply to domain gateways of type OSITP
. For gateways of type OSITPX
, the values NONE
or DM_PW
can be used. For gateways of type SNAX
, the values NONE
or DM_USER_PW
can be used.
The following DM_LOCAL
section parameters do not apply to domain gateways of type TDOMAIN
but are included here for completeness:
BLOB_SHM_SIZE
=
numeric
— applicable to domain gateways of type SNAX
MAXACCESSPOINT
(also known as MAXRDOM
) =
numeric
— applicable to domain gateways of type OSITP
MAXDATALEN
=
numeric
— applicable to domain gateways of type OSITP
For detailed descriptions of SNAX
and OSITP
parameters, see BEA eLink Documentation .
![]() ![]() |
![]() |
![]() |