How the TEDG Works


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

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

How the TEDG Works

The TOP END Domain Gateway (TEDG) provides interoperability between BEA TOP END systems and BEA Tuxedo Domains. The TEDG consists of two parts: a gateway administrative server and a gateway process.

Part	Description
Gateway administrative server (GWADM)	The gateway group administrative server that registers with the DMADM server to obtain configuration information used by the gateway group.
Gateway process (GWTOPEND)	The gateway process that provides connectivity to remote BEA TOP END systems.

Each GWADM/GWTOPEND pair represents an instance of the TEDG. Multiple instances can be configured by specifying multiple GWADM/GWTOPEND pairs, one pair per BEA Tuxedo group.

A TEDG connects to one or more nodes of a single BEA TOP END system. Connections must be made to each node that provides services required by a BEA Tuxedo application and to each node that uses BEA Tuxedo services. A TEDG can provide access to a BEA Tuxedo application only for connected BEA TOP END nodes.
A TEDG can provide access to a BEA TOP END system for all BEA Tuxedo nodes in the domain or other connected domains.
Multiple TEDG gateways may be configured in a domain or on a node to connect to different BEA TOP END systems.
Multiple TEDG gateways may be configured to connect to a single BEA TOP END system as long as no more than one connection exists between any pair of nodes consisting of a TEDG node and a BEA TOP END node.
The BEA TOP END system can communicate with multiple BEA Tuxedo domains as long as no more than one connection exists between any pair of nodes consisting of a TEDG node and a BEA TOP END node.
Each TEDG is defined as a local domain in the DMCONFIG file that defines all gateways for a domain.

The following illustration shows how the TEDG connects a BEA TOP END system and a BEA Tuxedo domain.

Connecting Systems with the TOP END Domain Gateway

How a BEA Tuxedo User Views the TEDG

From the perspective of a BEA Tuxedo system user, the TEDG:

Is controlled by the BEA Tuxedo system.
Appears as a set of BEA Tuxedo services to the BEA Tuxedo client program.
Allows BEA Tuxedo client programs to make calls to BEA TOP END services as if those services were part of the local domain.
Maps requests from the BEA Tuxedo client programs to the appropriate BEA TOP END services, forwards those requests for processing, and then returns the results as required.
Is viewed by a BEA Tuxedo client as a BEA Tuxedo server, and by a BEA Tuxedo server as a BEA Tuxedo client.

How a BEA TOP END User Views the TEDG

From the perspective of a BEA TOP END system user, the TEDG:

Appears as another Network Interface (NI) in the BEA TOP END system.
Allows BEA TOP END clients to access BEA Tuxedo services.
Maps these requests from the BEA TOP END client programs to the appropriate BEA Tuxedo services, forwards them for processing, and then returns the results as required.
Is viewed by a BEA TOP END client as a BEA TOP END server, and by a BEA TOP END server as a BEA TOP END client.