BEA Logo BEA Tuxedo Release 7.1

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

 

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

   Using the BEA Tuxedo TOP END Domain Gateway

Editing the DM_REMOTE_DOMAINS Section

This section identifies the remote domains that can be accessed by clients and servers of this Domains configuration. Entries in this section have the following form.

RDOM required_parameters

where RDOM is an identifier value used to name a remote domain to which a TEDG LDOM (as defined in the DM_LOCAL_DOMAINS section) may have a connection. The LDOM communicates with remote domains of type TOPEND that are part of the same BEA TOP END system as the LDOM. The BEA TOP END system name is defined in the DM_TOPEND section of DMCONFIG.

Note: 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 LDOM may need several RDOM entries to define connections to the BEA TOP END nodes where the desired BEA TOP END services reside.

For a description of the syntax required for parameters specified in this section, see DMCONFIG for GWTOPEND(5) in the BEA Tuxedo File Formats and Data Descriptions Reference.

Defining the Required Parameters

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

Required Parameters in DM_REMOTE_DOMAINS

Required Parameter

Definition

TYPE

Used for grouping remote domains into classes. TYPE can be set to one of the following values: TOPEND, TDOMAIN, SNAX, or OSITP. For the TEDG, set this value to TOPEND.

DOMAINID

Used to identify a remote domain. The TEDG uses the remote domain DOMAINID as the BEA Tuxedo user ID for requests made to the BEA Tuxedo system by the BEA TOP END system on this remote domain. DOMAINID must be unique across remote domains.

See Also