![]() |
![]() |
e-docs > Tuxedo > File Formats, Data Descriptions, MIBs, and System Processes Reference > Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference |
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.
The entry defines a GWTOPEND domain gateway instance (with its associated GWADM) that is associated with a single, remote BEA TOP END system. The local BEA Tuxedo application communicates with remote domains of type TOPEND that are part of the same BEA TOP END system. The BEA TOP END system name is defined in the DM_TOPEND section.
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 resources (services, queues) with the gateway group. The local resources available through the local domain access point will be available to clients in one or more remote domains.
Required TEDG parameters for the DM_LOCAL section
Optional TEDG parameters for the DM_LOCAL section
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |