Adding the DM_TOPEND Section


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Doc Home \| TOP END Domain Gateway \| Topic List \| Previous \| Next \| Contents

Using the BEA Tuxedo TOP END Domain Gateway

The DM_TOPEND section defines:

The network addressing information required by domains of TYPE=TOPEND
The BEA TOP END system name for each BEA TOP END local domain (LDOM) and remote domain (RDOM) defined in the DM_LOCAL_DOMAINS and DM_REMOTE_DOMAINS sections

Defining the Required Parameters

The parameters required in this section are listed in the following table.

Required Parameters in DM_TOPEND

Required Parameter
Definition

NWADDR

Specifies the network address associated with a local domain or remote domain.

If you associate the network address with an LDOM, the NWADDR parameter is used to accept connections from BEA TOP END systems.
If you associate the network address with an RDOM, the NWADDR parameter is used to initiate a connection.
If you associate multiple network addresses with an RDOM, the TP_SYSTEM value must be the same on each entry for the RDOM.
Multiple entries for an RDOM define primary and alternate network connections to the same physical node. The number of network addresses for an RDOM is not limited. When the TEDG attempts to make a connection, each network address is tried serially. Configuring too many network addresses or addresses that may not be operational can reduce TEDG performance. Multiple network addresses are not allowed for an LDOM.
Note: Care should be taken when specifying the host address portion of the NWADDR parameter. When a BEA TOP END NI accepts a connection request that was issued from a TEDG, it resolves the network address of the TEDG to a name. The resolved name must match the defined hostname of the TEDG. If the defined hostname of the TEDG and the resolved name differ, including case, the NI connection fails. Such a failure may not be evident from either the GWTOPEND log file or the remote BEA TOP END NI log file. As a general rule, ensure that the hostname definitions match in the DMCONFIG file, the TOP END NI configuration file, the TOP END nodemap file, the TOP END tp_alias file, and the locally configured name resolution facilities. For further information on NI name resolution, refer to the tp_alias(4T) reference page in the BEA TOP END Programmer's Reference Manual.

TP_SYSTEM

Specifies the BEA TOP END system associated with the LDOM or RDOM defined in the DM_LOCAL_DOMAINS and DM_REMOTE_DOMAINS sections.

The parameter accepts a string that corresponds to the BEA TOP END system name. The value of the string must match the value of the TP_SYSTEM environment variable specified in the node manager startup script. This script is described in the nm_script(4T) reference page.

Required Parameter	Definition
NWADDR	Specifies the network address associated with a local domain or remote domain. If you associate the network address with an LDOM, the NWADDR parameter is used to accept connections from BEA TOP END systems. If you associate the network address with an RDOM, the NWADDR parameter is used to initiate a connection. If you associate multiple network addresses with an RDOM, the TP_SYSTEM value must be the same on each entry for the RDOM. Multiple entries for an RDOM define primary and alternate network connections to the same physical node. The number of network addresses for an RDOM is not limited. When the TEDG attempts to make a connection, each network address is tried serially. Configuring too many network addresses or addresses that may not be operational can reduce TEDG performance. Multiple network addresses are not allowed for an LDOM. Note: Care should be taken when specifying the host address portion of the NWADDR parameter. When a BEA TOP END NI accepts a connection request that was issued from a TEDG, it resolves the network address of the TEDG to a name. The resolved name must match the defined hostname of the TEDG. If the defined hostname of the TEDG and the resolved name differ, including case, the NI connection fails. Such a failure may not be evident from either the GWTOPEND log file or the remote BEA TOP END NI log file. As a general rule, ensure that the hostname definitions match in the DMCONFIG file, the TOP END NI configuration file, the TOP END nodemap file, the TOP END tp_alias file, and the locally configured name resolution facilities. For further information on NI name resolution, refer to the tp_alias(4T) reference page in the BEA TOP END Programmer's Reference Manual.
TP_SYSTEM	Specifies the BEA TOP END system associated with the LDOM or RDOM defined in the DM_LOCAL_DOMAINS and DM_REMOTE_DOMAINS sections. The parameter accepts a string that corresponds to the BEA TOP END system name. The value of the string must match the value of the TP_SYSTEM environment variable specified in the node manager startup script. This script is described in the nm_script(4T) reference page.

Note: Do not configure LDOMs, RDOMs, and their network addresses such that more than one TEDG connection between a BEA TEDG node and a BEA TOP END node is activated for a particular TP_SYSTEM name. BEA TOP END network interface protocol does not support multiple connections of this type. As a result, if more than one TEDG connection is active, the TEDG or the BEA TOP END node rejects the duplicate connections. Due to variations in how network addresses can be specified, this type of configuration cannot be fully validated in this configuration file.