![]() |
![]() |
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_REMOTE_SERVICES section, provides information on services imported and available to the local domain through remote domain access points defined in the DM_REMOTE section. If the DM_IMPORT section is absent, or is present but empty, no remote services are available to the local domain.
A remote service is a service made available to the local domain through a remote domain access point and a local domain access point.
Entries within the DM_IMPORT section have the following form:
service [optional_parameters]
where service is the identifier name advertised by the local BEA Tuxedo application for a particular remote service; it must be 15 characters or fewer in length. A remote service may be imported from one or more remote domains.
A remote BEA Tuxedo service made available to the local domain inherits many of its properties from the SERVICES section of the remote TUXCONFIG file, or their defaults. Some of the properties that may be inherited are LOAD, PRIO, AUTOTRAN, ROUTING, BUFTYPE, and TRANTIME.
Optional parameters for the DM_IMPORT section
identifier1[,identifier2][,identifier3]
Non-TDomain parameters for the DM_IMPORT section
The following DM_IMPORT section parameters do not apply to domain gateways of type TDOMAIN but are included here for completeness:
For detailed descriptions of TOPEND parameters, see DMCONFIG for GWTOPEND(5). For detailed descriptions of SNAX, OSITP, and OSITPX parameters, see BEA eLink Documentation .
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |