This section defines the network-specific information for BEA TOP END domain gateways. The DM_TOPEND section should have an entry per local domain access point if requests from remote domains to local resources are accepted through that local domain access point, and an entry per remote domain access point if requests from the local domain to remote resources are accepted through that access point.

Entries within the DM_TOPEND section have the following form:

AccessPoint required_parameters [optional_parameters]

where AccessPoint is an identifier value used to identify either a local domain access point or a remote domain access point. The AccessPoint identifier must match a previously defined local domain access point in the DM_LOCAL section or a previously defined remote domain access point in the DM_REMOTE section.

Local and remote domain access points and their network addresses must be configured such that no more than one BEA TOP END gateway connection to a BEA TOP END node is activated for a particular TP_SYSTEM name at run-time. The BEA TOP END network interface protocol does not support multiple gateway connections. If an attempt is made to activate more than one connection, run-time errors occur in the TEDG or on the BEA TOP END node, and all connections except one are rejected. Due to variations in how network addresses can be specified, this type of configuration cannot be fully validated in the DMCONFIG file.

Required parameters for the DM_TOPEND section

Optional parameters for the DM_TOPEND section

Multiple entries for the same access point in the DM_TOPEND section

If this DM_TOPEND entry is a local domain access point (as specified in the DM_LOCAL section), its NWADDR is a network address to be used to listen for incoming connections. Entries associated with a local domain access point can be specified more than once in the DM_TOPEND section, to allow for migration of the resources associated with a local access point to another machine in the BEA Tuxedo domain.

Entries associated with a remote domain access point (as specified in the DM_REMOTE section) can also be specified more than once in the DM_TOPEND section. The first entry is considered to be the primary address, which means its NWADDR is the first network address tried when a connection is being attempted to the remote domain access point. The second entry is considered to be the secondary address, which means its NWADDR is the second network address tried when a connection cannot be established using the primary address. The network addresses of subsequent entries are used if the network addresses of all previous entries have failed. A connection attempt fails when all configured network addresses have been tried. Entries associated with a remote domain access point can be specified an unlimited number of times. Configuring too many network addresses or addresses that may not be operational can degrade performance.

If this DM_TOPEND entry is another occurrence of a remote domain access point, the entry is used only when a network connection cannot be established using the NWADDR of the primary entry (and any prior secondary entries). For every secondary entry:

Secondary remote gateway definitions are not recommended for use with TOP END domain gateways.

Note: For multiple entries of a local or remote domain access point in the DM_TOPEND section, only the multiple instances of the NWADDR parameter are read by the Domains software. For multiple instances of any other parameter, only the first instance of the parameter is read by the Domains software; all other instances are ignored.