Tuxedo
0
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

 Previous Next Contents View as PDF  

DM_REMOTE Section

This section, also known as the DM_REMOTE_DOMAINS section, defines one or more remote domain access point identifiers and their characteristics. For TOP END domain gateway (TEDG) definitions, the entries in this section define connections to Network Interface components on nodes of remote BEA TOP END systems.

Entries within the DM_REMOTE section have the following form: 

RemoteAccessPoint required_parameters [optional_parameters]

where RemoteAccessPoint is a remote domain access point identifier (logical name) that you choose to identify each remote domain known to the local BEA Tuxedo application. RemoteAccessPoint must be unique across the local and remote domains involved in a Domains configuration.

Each remote domain access point defines a node in the BEA TOP END system to which the TEDG associated with a local domain access point may have a connection. The TEDG in the local domain communicates with remote domains of type TOPEND that are part of the same BEA TOP END system as the local domain. (The BEA TOP END system name is defined in the DM_TOPEND section.) Because of the BEA TOP END adjacent node routing topology, the services for the BEA TOP END system may reside on several different nodes. Therefore, a TEDG local domain access point may need several remote domain access point entries to define connections to the BEA TOP END nodes where the desired BEA TOP END services reside.

Required TEDG parameters for the DM_REMOTE section

TYPE = identifier

Specifies the type of local domain gateway needed to communicate with the remote domain associated with this remote domain access point. TYPE can be set to one of the following values: TOPEND, TDOMAIN, SNAX, OSITP, or OSITPX.

The TOPEND value indicates that a local instance of the GWTOPEND process will communicate with a remote BEA TOP END system.

The TDOMAIN value indicates that a local instance of the GWTDOMAIN process will communicate with a remote BEA Tuxedo application.

The SNAX value indicates that a local instance of the GWSNAX process will communicate with a remote TP domain via the SNA protocol.

The OSITP value indicates that a local instance of the GWOSITP process will communicate with a remote TP domain via the OSI TP 1.3 protocol.

The OSITPX value indicates that a local instance of the GWOSITP process will communicate with a remote TP domain via the OSI TP 4.0 or later protocol. The OSITPX value is supported only by BEA Tuxedo 8.0 or later software.

ACCESSPOINTID (also known as DOMAINID) = string[1..30]

Used to identify the remote domain associated with this remote domain access point for purposes of security when setting up a connection to the remote domain. For a local domain gateway of type TOPEND, this value is also used by the TEDG (local instance of the GWTOPEND process) as the BEA Tuxedo user ID for incoming requests from the BEA TOP END system on this remote domain access point connection. ACCESSPOINTID must be unique across local and remote domain access points.

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 value of string can be a sequence of characters or a sequence of hexadecimal digits preceded by 0x.

Optional TEDG parameters for the DM_REMOTE section

PRIORITY_TYPE = {LOCAL_RELATIVE | LOCAL_ABSOLUTE | GLOBAL}

INPRIORITY = numeric

Together, the PRIORITY_TYPE and INPRIORITY parameters specify the message priority handling for this remote domain access point. These parameters are supported by BEA Tuxedo 8.0 or later software.

For the PRIORITY_TYPE parameter, the LOCAL_RELATIVE and LOCAL_ABSOLUTE values are valid for all remote domain types; the GLOBAL value is valid only for remote domains of type TDOMAIN. If not set, the PRIORITY_TYPE parameter defaults to LOCAL_RELATIVE.

PRIORITY_TYPE=LOCAL_RELATIVE means that the priority associated with a request from this remote domain access point (for example, via the tpsprio call) is not used by the local domain. Instead, the priority of incoming requests from this remote domain access point is set relative to the INPRIORITY value; this value may be greater than or equal to -99 (lowest priority) and less than or equal to 99 (highest priority), with 0 being the default. The setting of INPRIORITY increments or decrements a service's default priority as follows: up to a maximum of 100 or down to a minimum of 1, depending on its sign, where 100 is the highest priority. For requests to the remote domain access point, the priority associated with a request will accompany the request to the remote domain access point.

PRIORITY_TYPE=LOCAL_ABSOLUTE means that the priority associated with a request from this remote domain access point is not used by the local domain. Instead, the priority of incoming requests from this remote domain access point is set relative to the INPRIORITY value; this value may be greater than or equal to 1 (lowest priority) and less than or equal to 100 (highest priority), with 50 being the default. The setting of INPRIORITY increments or decrements a service's default priority as follows: up to a maximum of 100 or down to a minimum of 1, depending on its sign, where 100 is the highest priority. For requests to the remote domain access point, the priority associated with a request will accompany the request to the remote domain access point.

PRIORITY_TYPE=GLOBAL means that the priority associated with a request from this remote domain access point is adjusted by the local domain. The priority of incoming requests from this remote domain access point is adjusted relative to the INPRIORITY value; this value may be greater than or equal to -99 (lowest priority) and less than or equal to 99 (highest priority), with 0 being the default. If INPRIORITY is set, the priority accompanying the incoming request is added to the INPRIORITY value to create an absolute priority setting for the incoming request. If INPRIORITY is not set or is set to 0, the priority accompanying the incoming request is used as is by the local domain. For requests to the remote domain access point, the priority associated with a request will accompany the request to the remote domain access point.

 

Back to Top Previous Next
dev2devesupporthttp://www.oracle.com/technology/documentation/index.htmlpartner net
Contact e-docsContact BEAwebmasterprivacy