BEA Logo BEA Tuxedo Release 8.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

   Tuxedo Documentation   |   Using the BEA Tuxedo TOP END Domain Gateway   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents

 


Communicating with BEA TOP END Systems Using Extended Node Names

BEA TOP END Release 3.0 provides a feature called Extended Node Names that allows the use of external node names that are longer than eight characters. With the Extended Node Name feature, node names can be up to 255 characters long, while the internal node ID is an eight-byte opaque data structure used within the BEA TOP END system to identify nodes.

The mapping between node IDs and node names is established through a simple text file called the nodemap file. For details on creating the nodemap file, see Getting Started with BEA TOP END. The format of the file is described in the BEA TOP END nodemap(4T) reference page.

On BEA TOP END nodes, the nodemap file is installed in the following directories.

Platform

Directory

UNIX

$TOPENDDIR/etc

Windows 2000

%TOPENDDIR%\etc


 

If you have configured the TEDG to communicate with BEA TOP END nodes that have node names longer than eight characters, the nodemap file must be available to the TEDG. Before running the TEDG, copy the nodemap file from the BEA TOP END system to the following directories on the BEA Tuxedo system.

Platform

Directory

UNIX

$TUXDIR/udataobj

Windows 2000

%TUXDIR%\udataobj


 

The nodemap file also allows the administrator to map multiple node names to a BEA TOP END node identifier. This helps the TEDG, at incoming connection time, obtain a consistent node identifier for the NI running on a machine on which multiple network cards are installed.

See Also

 

back to top previous page next page